Commit Graph

9 Commits

Author SHA1 Message Date
Andreas Jaeger 08db3ad05f Retire repository
Fuel (from openstack namespace) and fuel-ccp (in x namespace)
repositories are unused and ready to retire.

This change removes all content from the repository and adds the usual
README file to point out that the repository is retired following the
process from
https://docs.openstack.org/infra/manual/drivers.html#retiring-a-project

See also
http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011647.html

Depends-On: https://review.opendev.org/699362
Change-Id: I37b6a82c9c3c3893bb4b9b6a4c4b5a83a6d8193c
2019-12-18 09:50:01 +01:00
Igor Gajsin a0838e91a9 remove vmware
VMware not supported since Fuel 10. So we should stop test it.

Change-Id: I5996520ded3419fd2ce2cb1e76056eed157bfffb
Implements: blueprint remove-vmware
2017-02-15 11:03:42 +03:00
Dmitry Tyzhnenko 4e11179097 Migrate group thread_1 to pytest scope
Implements blueprint migrate-fuel-qa-from-proboscis-nose-frameworks

Change-Id: I23231967b722dc8c1fe2cf2faa303f8c4a9df871
2016-06-02 13:14:06 +03:00
vrovachev 4154f0c732 Replace env for nova-compute packages
Replaces environment for check nova-compute packages
to env without some extra parameters.

Partially implements: blueprint mos-patching-tests

Change-Id: I145dfb5df03bd1d3d9334bcfb0a8924558a6569e
2015-07-06 18:00:12 +04:00
Artem Panchenko 2d1b708a07 Check both master and env repos for packages
In tests with Ubuntu for environment operation
system some packages on master node (CentOS)
could be updated, so tests must search packages
in both repositories types.

Also copy master node packages to 'deb' section,
because they are needed to determine package
installation target.

Change-Id: I96edc27278229d525da20c9b1237ebded34acaf7
Implements: blueprint mos-patching-tests
2015-06-18 18:11:24 +03:00
asledzinskiy 619c7ada17 Add test plans for main openstack components
- Add test plans for nova, neutron, ceph, cinder,
glance, swift

Change-Id: Idbd0d5378fb0ef6dfde28bd71e8be33f74af92e0
Implements: blueprint mos-patching-tests
2015-06-04 18:10:00 +03:00
asledzinskiy 359519dd29 Add test for master patching
- Add tests to patch master node with existing environment,
reset and delete cluster and then deploy new cluster

Change-Id: I972848ede2a8cc6f5c33044b111dcd90e30d2e1b
Implements: blueprint mos-patching-tests
2015-04-21 10:49:15 +03:00
Artem Panchenko e8937fa42a Add tests configuration files for packages
Add configuration files 'packages.yaml' for 'deb'
and 'rpm' in system tests, which will be used for
packages testing (including patching).

Implements: blueprint mos-patching-tests

Change-Id: I038b7d31ecc6f9ae640e4e288c90aca5eac00380
2015-03-23 14:03:39 +00:00
NastyaUrlapova 17d34057c7 Create tests for patching feature
Add first test for patching environment, which
deploys some cluster and apply patches on it.
Environment configuration (deployment test) is chosen
automatically based on packages tags.
Tests require errata.yaml which should include scenarios
for applying/verifying patches.
Additional variables required by patching tests:
 * PATCHING_MIRRORS - list of repositories with patched
   packages;
 * PATCHING_WEB_DIR - directory on master node which is
   available via HTTP (used for new repository);
 * PATCHING_BUG_ID - bug ID which is going to be fixed;
 * PATCHING_PKGS_TESTS - local path or URL to destination
   where test plans for packages are stored;
 * PATCHING_APPLY_TESTS - local path or URL which should
   be used to get test plans for bugs (using bug ID);
 * PATCHING_PKGS - list of patched packages; if empty -
   list is gotten from test plan (errata.yaml) or from
   repository.

Implements: blueprint mos-patching-tests

Change-Id: Ic696a49bd12504c9e045cf824248ff09bb7d53cb
2015-03-23 14:12:54 +02:00