VMware is no longer supportes, thus we have no attributes use_vcenter
in the cluster attributes.
Change-Id: I90de98d736227c913fddfb27cefd186f29b3fb1b
Closes-Bug: #1666835
Implements: blueprint remove-vmware
Provide support for SR-IOV and DPDK through new API version
for NICs.
Change-Id: I1a927c0e7333a422f94dd2937638f8d2ca38512f
Implements: blueprint nics-and-nodes-attributes-via-plugin
Use nailgun settings for determine mode,
if development mode enabled -> allow log
Closes-bug: #1546551
Change-Id: I280ca46547aaa382aa001387ae017025da227aa7
Scenario:
1. Create a new security group (if it doesn`t exist yet).
2. Create router
3. Create network
4. Create subnet
5. Uplink subnet to router.
6. Create new flavor with huge pages
7. Create an instance using the new flavor, security group
in created subnet. Boot it on compute with enabled DPDK.
8. Create a new floating IP
9. Assign the new floating IP to the instance.
10. Check connectivity to the floating IP using ping command.
11. Check that public IP 8.8.8.8 can be pinged from instance.
12. Disassociate server floating ip.
13. Delete floating ip
14. Delete server.
15. Delete flavor
16. Remove router.
17. Remove subnet
18. Remove network
Change-Id: I86c43896a6b7ff0e55f72dd7ffce02487ac7299e
Closes-Bug: #1567439
Reasons:
- 'use_vcenter' is not declared in option list of ComputeGroup
but assigned later in _parse_cluster_attributes()
Changes:
- Added option 'use_vcenter' to ComputeGroup
Change-Id: I066b59b46413701233c9723a60645edfe1f1f7fb
Closes-Bug: 1575646
That fix is intented to fix swarm tests.
Further investigation required to find out why
there were no sriov keys
Change-Id: Iaa3cbe7a6a0717e8e027d43795fda8c93394ec09
Closes-bug: #1575566
+Add corresponding test
+Add _create_port
+Add _cleanup_ports
+Add sriov deployment tag if computes with SR-IOV enabled interface
are present and unit-tests for ostf-adapter
+Add sriov_enabled physnets to cluster config
Change-Id: I487c0dc0f4756b893af5d5c59ea85ba0d47faa5c
Closes-Bug: #1566906
Implements: blueprint test-sriov-support
* this change replaces occurrences of
`traceback.format_exc()` with the appropriate version of
`LOG.exception()` in fuel-ostf
* removes importing `traceback` module.
* incorporated review comments from fuel-dev team
Change-Id: I7055aeafdcb109bd3566f118379196ea6ca6037d
Closes-Bug: #1457397
Signed-off-by: Anil Belur <askb23@gmail.com>
python-nova 13.0.0~b3-0ubuntu1~cloud0 no longer reports
incorrect services as being available and down.
This reverts commit 1bccfe65f6.
Change-Id: I51369ee54ae8519c266f577b4abb6767ba7e52d0
nova service-list shows osapi_compute and metadata
services as down, when these are APIs, not RPC receivers,
which should not be reported by this command. The bug is
fixed upstream and in Fuel, but not in UCA Trusty packages.
blueprint deploy-with-uca-packages
Change-Id: I632051fb77d713cd8584bba398486f70cb8901d5
In case 'force_https' is turned on for fuel we must disable ssl cert
verification for code that performs http requests inside fuel
infrastructure (e.g. requests to nailgun). The verification is
meaningless by itself as we use self signed cert.
Change-Id: Ic47d91d1a59ef2741bfab8709ff0b0985fb1919d
Closes-Bug: #1538977
Force OSTF and OpenStack clients to use cluster public
VIP instead of Keystone public VIP for authentification
if SSL is enabled for endpoints, because by design SSL
is configured only for public VIP.
Change-Id: I53e54918b893f507cbac7d716300546a825467ea
Closes-bug: #1533306
To be sure that OSTF works fine with SSL,
switch to use public endpoints without
validation of certificate
Change-Id: I87a625899c1eb4b80376c8bdb5aca4fce3d8ad66
Closes-Bug: #1486056
Related-Bug: #1524850
Try to authorize in Keystone using HTTP proxy
on all online controllers.
If Keystone is not available via all proxies
then raise 'SetProxy' exception.
If authorization failed via all alive proxies
then raise 'InvalidCredentials' exception.
Change-Id: I62681f3eb26c23edba3683842860c19eb4ddd4b6
Closes-bug: #1515516
The format of VIPs description in 7.0 was changed.
Special nailgun API serializer for compatiblity with current OSTF should removed in 8.0
It is required to fix VIPs format in OSTF
Closes-Bug: #1476174
Change-Id: I259ebb1e43db399283f2bf3715905172d9b6c170
Private network name "net04" should now use
customizable value configured in nailgun.
If this value is not present in nailgun, it
defaults back to "net04".
Change-Id: I66b7cde820c114b9c447fc4c169a51d3a63d0bea
Partial-Bug: #1349702
Add 10 seconds timeout for Keystone client initialization
during HTTP proxy check, because otherwise it could hang
forever.
Also check that find_proxy returns IP address before
using it.
Change-Id: I4fabe0f5fee3d2acc3e7e2387ac858b2c56493c7
Closes-bug: #1499415
In case if horizon runs over https, step:
login in horizon will not be run until
https://bugs.launchpad.net/fuel/+bug/1486056 in progress
Change-Id: Ia9997ae2b7180c4b3a52d9c6f501a6cbef27ba5b
Related-Bug: #1486056
- Since all clusters share the same ostf instance
we can face problems after upgrade when 7.0 tests
don't work with old release clusters. Add check that
if release is before 7.0 - use controllers in HA tests
Change-Id: I4d37c8f1ef4a7c3ae607f39450c122c34bec43ac
Closes-Bug: #1489462
To enable granular deployment of keystone, we need to know
precisely where keystone will be configured, as we dont have
such API in nailgun, we need to invent some convention.
Important to remember that we also need proxy on port 8888 configured
on a node that consumes configured vip.
Related-Bug: #1470927
Related bp ostf-separate-services-refactor
Change-Id: Ie497bca8818cd0f24eb40df32df227152254a69d
- Methods to get hiera values and create amqp
connections were fixed
- Test on rabbitmq availability was rewritten
to use rabbit nodes instead of controllers
Change-Id: I72a1abf71a36ea4bc3bd962d0eab0914e8207a3f
Implements: blueprint ostf-separate-services-refactor
Not used variables was deleted.
SSH connetction in test 'Check usage of default credentials on master node' use credentials of master node.
Change-Id: I0ea2852f1d643690fb8cdf8dcd2231be42b5b7b2
Closes-Bug: 1470910
This test checks that default keystone credentials were changed on master node.
Implements: blueprint default-fuel-master-password
Change-Id: Ic06e4f5ba7de2e3f9913e128e1e3919ed6dd2aa8
Get pacemaker resources from all online controller, ensure that
the resources are the same on each controller and are running
only on allowed nodes.
Change-Id: I21ab4b4ad5a0bfa698fffe6b650584cdb5f357df
Related-Bug: #1383247
Motivation:
* avoid issues described in 1466399
* we my have ssl enabled on public endpoints
So replace usage of public_vip to management_vip
Closes-Bug: #1466399
Change-Id: I32e5a2da2d92de2359ebae789c746335e1c90e7e
Append test "Create volume and attach it to instance" for cinder-vmware role.
Added BoolOpt 'cinder_vmware_node_exist' and it processing.
Added img_name and **kwargs args for _create_boot_volume function in
SmokeChecksTest class.
Added img_name arg for _create_server function in SmokeChecksTest class.
Closes-bug: #1431321
Implements: blueprint cinder-vmdk-role
Change-Id: I9205b9200e9f3cfe293c734b6e76dc4be4a54f87
Next checks were added:
* Check crm status for rabbit resources
* Check Master is live
* list channels
* create connection to each member of the qurum
* create queue
* publish message
* consume message and assert it content
Change-Id: Ie28f541acb14d1afac1a8463aa35a606a7c5f329
Implements: blueprint ostf-rabbit-replication-tests
Added use_vcenter deployment tag
Added img_name parameter to get_image_from_name and _create_server
functions
Created new smoke tests for vcenter in test_vcenter.py
Change-Id: I3f9f8fd07ad597e500144185002890a9593b7f49
Implements: blueprint vmware-dual-hypervisor
Andreas Jaeger