Implement system test to verify Openstack in case if master node is gone out

[Tatyanka]

Implement system test to verify Openstack in case if master node is gone out

[Oleg S. Gelbukh (gelbuhos)]

Guys, I see many such things added as bugs. In fact, they are not. They are rather feature requests, and should be registered as blueprints, according to OpenStack and Launchpad practice. Please, consider registering blueprints for such requests.

[Mike Scherbakov (mihgen)]

Oleg, I disagree in this particular case. See https://wiki.openstack.org/wiki/Blueprints:

Blueprints are not always required. Blueprints are used for tracking significant development efforts. In general, small and/or straight forward cleanups do not need blueprints. A blueprint should be filed if:

it impacts the release notes (would a user care?)
A feature has been added, removed, or changed ... For example, changes to:
configuration options
glance or cinder metadata properties that Nova consumes
public APIs
Affects deployments or upgrades ... For example, changes to:
how you migrate the DB schema
services that must be running
other upgrade procedures
it covers significant internal development or refactoring efforts

In this particular case this is very small internal feature, which is too small for a blueprint. As launchpad doesn't have such thing as Task (we had User Stories == blueprints in Jira and Tasks), we have to use bugs for tracking such things. Looks like it works pretty well so far.. let me know if you see any disadvantages.

[Matthew Mosesohn (raytrac3r)]

Moving to 4.1. I don't think we can get this in 4.0 release cycle.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/69435

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/69435
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=46bd199eb77b02c9e5552cc18446e53c7db62583
Submitter: Jenkins
Branch: master

commit 46bd199eb77b02c9e5552cc18446e53c7db62583
Author: TatyanaLeontovich <email address hidden>
Date: Mon Jan 20 18:56:22 2014 +0200

    Add test that OS is operation after master fail

    Test verifies that openstack is operational
    after master node is failed. Scenario:
    * Deploy simple nova flat
    * verify that deployment is successful
    * run ostf
    * destroy admin node
    * verify openstack

    Closes-bug: #1259460
    Change-Id: I9e1d1fb2f3c6f642c23a509ac41580e5c53bf952