The traffic from ironic slave is untagged, we can't use
vlan with simulated environment.
Closes-Bug: #1675673
Change-Id: I89f5b59448dbab11ad4f398b6a879ab4c4f606c8
The parameter's name was changed and not updated by cherry-pick
from mitaka branch - lets update multipath template
Change-Id: I1bf20ae4636c6a7683a3610edd2eb3c961809b13
(cherry picked from commit 8af1622d21)
Current templates contains several errors:
- no role for ironic-slave-2
- fuel-qa requires role "ironic" instead of "ironic_slave"
- gate's template does not contains driver
Change-Id: I7bfadbabf897ff28d5db5e33a0f8229ad30a421c
fuel-qa requires nodes with explicit role 'ironic_slave'
for testing
Change-Id: If1b63c2e7114d6b85dc069f15442cb90ad160ec5
(cherry picked from commit 060417ff25)
Now devops3 does not contains all needed hardcode for adding baremetal
network and nodes with it; instead of this, we can prepare and use the
template
Change-Id: I74c4276908231a1651ee2768b3d618d4b3dfa824
Partial-bug:1669762
(cherry picked from commit 80b97af7ab)
Tag is deprecated in fuel_devops. Also we do need vlan_start and vlan_end
for nailgun to work correctly
Closes-bug:1670405
Change-Id: I60e12e65ef3cfb73c9ff78401a785def2e54403d
(cherry picked from commit 59c03f8712)
VMware not supported since Fuel 10. So we should stop test it.
Change-Id: I5996520ded3419fd2ce2cb1e76056eed157bfffb
Implements: blueprint remove-vmware
To calculate space to filling on root partition to activate rabbit
alarm need to calculate left space on root and take away additional 6M.
If calculated valute less than 0 - skip this action.
Change-Id: I901833d4211789672b6cedd12db80ac8a92f8d5d
Closes-Bug: #1631928
* Increase timeout for creation instances
* Fix DVS parameters for scale tests
* CERT_BYBASS value should be boolean
* PROGRESS_TO_STOP value should be integer
Change-Id: I56e955bd1925f9280e2c54957b4c8a6b50e1bcc5
(cherry picked from commit aaca57a4d6)
self.d_env.admin_net = 'admin'
'nat_interface' = ''
This patch is reduces warnings amount during
tests run on fuel-devops 3.0.3+
Change-Id: I2bf54952bff79b9483c121a78383e136bcd2a351
Add two tests with the following steps:
Deploy environment with enabled DMZ network for API.
Scenario:
1. Revert snapshot with ready master node
2. Create new environment
3. Run network verification
4. Deploy the environment
5. Run network verification
6. Run OSTF
7. Reboot cluster nodes
8. Run OSTF
9. Create environment snapshot deploy_env_with_public_api
Check that security rules are properly applied for DMZ network
Scenario:
1. Revert snapshot from previous test
2. Run instance
3. Try to access horizon from instance
4. Remove instance
Implements: blueprint test-separate-public-floating
Change-Id: I70474b5cab324aa4f4a042127d4e6961c95010bf
In order to optimize resources on labs we can use yaml
template for devops environment. Typically we deploy
env with 3 controllers and several other nodes with
vmware-related roles. Controller nodes use more
resources than other nodes, so we can set different
memory size and amount of cpu for different nodes to
optimize resource utilization.
Change-Id: I492c74aea6696de11ea1871e9a026f74e1873981
Closes-bug: #1616476
Test cases:
1. Reset and redeploy cluster with vCenter after succesfull deployment
2. Stop and redeploy cluster with vCenter with new parameters
3. Redeploy cluster with vCenter after failed deployment
Closes-Bug: #1612578
Change-Id: Ia0de031e9c6d7a72f126a28b8e150496350c5a87
SingletonMeta class is exists in fuel-devops: deprecate copy
all imports has been changed to devops side
Announce drop of deprecated and already unused helpers.
Change-Id: I98311de2c4fc579b8d6095bf5decd28940a00f88
(cherry picked from commit ef37f0d)
As running resources on controller may be not equal as at beginning
of the test, let's use 'Check pacemaker status' sanity OSTF test.
Change-Id: I6ad59702fb04d5f7b2fb97cc257b763c53ee2fc7
Closes-Bug: #1584097
- added waiters for node status
- removed redundant try/except/assert
Related blueprint: fuel-qa-failure-reason-grouping
Change-Id: I06ccac42856712d1f9afe64402d34aeba3c07af6
- Add test with external load balancer. Controllers are
from different racks and haproxy is from rack-3
- Separate devops config with appropriate networks
assigned to nodes is used
- Local repos for cluster are used because public networks
are routed without internet connection
- OSTF isn't running because it's not implied to use
separate haproxy
Closes-Bug: #1583530
Change-Id: I0d3647c8eb13159c27e64ddf5925467f451b610c
Andreas Jaeger