VMware not supported since Fuel 10. So we should stop test it.
Change-Id: I5996520ded3419fd2ce2cb1e76056eed157bfffb
Implements: blueprint remove-vmware
Right now there is legacy selection of slaves RAM size based on
OS release; its useless because we are using only ubuntu-based releases.
Pin 3.5GB RAM to all slaves by default.
Change-Id: Ic2e91d435a3509f0d4302cb44707d2872de7a9d3
* 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)
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
V3 plugin is deprecated in 9.1 and contains dropped tasks - it's
impossible to use in for testing - replacing the plugin.
Change-Id: Id25a324d490144556938c80b1b6931ce361dd237
Closes-bug:1621105
In upgrade chain scenario we can stuck in release fetching
because after restore of master node we have 3 releases which contains
"Ubuntu 14.04" substrings.
In previous implementation the first matched release is taken (which is Kilo
in upgrade 7-8-9 case instead of Mitaka)
Reusing of RELEASE_VERSION allow us to tune selection process.
Change-Id: Iac2b15fba774b3055016a67528528d8b851dfe16
Partial-bug:1620978
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
Right now this var is used only for octane installation and
misleading people with other proposed-related variables.
Change-Id: Ie3611482c87e7d183c85fba39cde3daaf2489ab4
Now, whether use sudo mode or not, "sudo" parameter
has to be passed to SSHManager methods with default state:
do not change.
Process flag in context manager
(flag will be reverted to the original state after command)
Default sudo mode settings could be changed by environment variables:
ENV_FUEL_SUDO
ENV_SLAVE_SUDO
Partial-Bug: #1566377
Change-Id: Id298a396867eae74a6d86ba370edd33040f15911
Right now the tool does not working from the middle after re-launch.
We have to specify the step for each run of tests
Change-Id: I7203b597c8320d68b5cd412e99c84dfb29249ba5
Since we are not testing detach-db plugin its time to switch to example plugin
- Move plugin test to separate file
- Replace detach-db plugin with example_v3 plugin
- Download the plugin by URL passed via EXAMPLE_V3_PLUGIN_REMOTE_URL env var
Change-Id: I99217686be856acd8e69e93e5dd3ae40cbb1f15b
Closes-bug:1603415
Replaces https://review.openstack.org/#/c/348833 because it
also adds default for UBUNTU_SERVICE_PROVIDER
blueprint: mos-xenial
Change-Id: Ie5a708b108f73a5800406eb258e7b88a1b65231f
1. Replace ceph-all service check
jewel in xenial doesn't provide ceph-all meta-service,
this commit replaces it with checks of particular services.
2. Update another ceph-related service management command.
blueprint: mos-xenial
Change-Id: I8fcc1e763c2da984fad96cc58ebcd72d5de53ee3
Rignt now we can't bump release name for OPENSTACK_RELEASE_* vars so
making it configurable via env vars is less harmful way to unlock
development.
Change-Id: If7bd57693890f76022e15a77ad63243cd993e144
Closes-bug:1607653
For executing chain Fuel upgrades and reusing of existing code we need to
create some tool for configurable upgrade. For now it configures via
env variables but later it can be tuned via yaml files.
Change-Id: I4fc2281801ad2a02c63dc0eb92941aadca8b9d33
For enhancement of development and testing process it is necessary
to add an ability to patch octane code inside fuel from gerrit review.
Change-Id: Id9ed02930d84a0c7ba8f42d5dced77c86ca84d00
1) Need to use fuel-devops >=3.0.0
2) Need to use centos_master.yaml devops template
3) export CENTOS_MASTER=True environment variable
4) provide path to CENTOS_CLOUD_IMAGE_PATH, FUEL_RELEASE_PATH and
EXTRA_DEB_REPOS
Change-Id: I1542c2238abc364713f02e4bca6ec7646883bf78
Closes-Bug: #1592419
- Add test for basic Murano validation in plugin installation
- Fix test names in Murano-related box-install tests since Murano
using GLARE backend as default now.
- Turn off SSL deployment for Murano due bug: #1590633
Change-Id: Iac71f4706db4b8eb67a7f98b2932fbb31032bc9f
Related-Bug: #1584791
Targets: blueprint murano-fuel-plugin
This change allow to install any
additional packages from any additional
repository during install master-node.
Related-Bug: #1526544
Change-Id: I4b10ff432b385824595c0ac65b5282a2b81c859c
In case SEPARATE_SERVICE_HAPROXY_PLUGIN_PATH is set without
MULTIPLE_NETWORKS we got local variable 'load_yaml' referenced before assignment
Since this variable is added for all plugin tests it breaks them
Partial-bug: 1589914
Change-Id: I8e2dc6f6074db6c3d45d73a102b5d9f9e9671f25
- 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
- Do not use RH_* variables for images
- Make some methods paramerized to be used in different tests
- Add basic deployment test with OL compute
Change-Id: I86e616640ff4a162b74ee0da74917f06105b7a39
Related-Bug: #1569374
In case we export parameters, they are operated as strings, while
we are working with them as integer
Change-Id: I75090beaa250617087c5bf160625516ffbdb60aa
Closes-Bug: #1579955