change_vip_manually test failed with Vip with name public wasn't found

[Andrey Sledzinskiy]

fuel version - 9.0-275

Steps:
1. Install fuel
2. Create any cluster
3. Try to get info about possible vip's
http://<ip>:8000/api/clusters/1/network_configuration/ips/vips

Expected - data with possible vips is present
Actual - empty list is returned

We rely on this data in tests, we get possible vips, change its ip and upload changes

[Artem Roma (aroma-x)]

This is an expected behavior in current design. Before cluster is deployed there are no VIPs in data base; so response from VIP related API is empty. VIPs are auto-allocated when deployment starts.

User now can create custom VIPs by sending http POST request on http://<ip>:8000/api/clusters/1/network_configuration/ips/vips. There are patch under the review [1] which add fuel client wrapper for this operation. In the request's payload user must supply following attributes: ip_addr (IP address for the VIP, string), network (id of the network group in which the VIP will be allocated, integer), vip_name (name of the VIP, string); in addition vip_namespace (string) can be supplied.

Name for new VIP must conform with those defined in network metadata for the cluster. For the sake of helping the user VIP info is included into network configuration returned by request to /api/v1/clusters/<cluster_id>/network_configuration/<net_provider>, or by corresponding fuel client command. There are dedicated 'vips' field in the response data, which gives representations of VIPs that will be created at deployment start. This info may then be used to create custom VIPs. However, please note, cluster must have assigned to it nodes in order to serialize VIP information.

[1]: https://review.openstack.org/#/c/312571/

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/314962
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=c0536ee4aeb8dc68ed8bf66ed6d1a4ff6478f64e
Submitter: Jenkins
Branch: master

commit c0536ee4aeb8dc68ed8bf66ed6d1a4ff6478f64e
Author: asledzinskiy <email address hidden>
Date: Wed May 11 13:38:13 2016 +0300

    Fix manual vip allocation tests

    - Now vips are not allocated before deployment so
    change tests logic to send manually formed vip

    Change-Id: I37f3d714a52a42203bedca8f1546e995cc737436
    Closes-Bug: #1578697

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/318088

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/318088
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=eda47dc572a3935e13e88069de4fb737f6fcaf08
Submitter: Jenkins
Branch: stable/mitaka

commit eda47dc572a3935e13e88069de4fb737f6fcaf08
Author: asledzinskiy <email address hidden>
Date: Wed May 11 13:38:13 2016 +0300

    Fix manual vip allocation tests

    - Now vips are not allocated before deployment so
    change tests logic to send manually formed vip

    Change-Id: I37f3d714a52a42203bedca8f1546e995cc737436
    Closes-Bug: #1578697

[Dmitry Belyaninov (dbelyaninov)]

[root@nailgun ~]# shotgun2 short-report
cat /etc/fuel_build_id:
 460
cat /etc/fuel_build_number:
 460
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0

There are no VIPs allocated after cluster creation but before deployment.

http://<ip>:8000/api/clusters/1/network_configuration/ips/vips returns "[]"

[Dmitry Belyaninov (dbelyaninov)]

https://product-ci.infra.mirantis.net/view/All/job/9.0.acceptance.ubuntu.change_vip_manually/
passed