This adds support for testing CentOS 8.
- Update documentation
- Add references to CentOS 8
- Update genealogy to include latest releases
- Update minimum Chef requirement
- Add Bare Metal to list of cookbooks when creating a stable branch
- Include memcached in identity role
- Update InSpec tests for CentOS 8
- Ensure we install the yum package on rpm distros (required by Chef to
run properly and is missing on the default image)
- Remove yum-epel attributes in integration since it breaks on EL8
Change-Id: Ie648432021325150fdd2fd7ab7f1af10bc69b655
Signed-off-by: Lance Albertson <lance@osuosl.org>
Changed:
- Temporarily disable voting during development
- Update git URI for bind cookbook to use upstream master
- Renamed .kitchen.yml -> kitchen.yml
- Genealogy updated
Fixed:
- Idempotency with use of apt_update resource
- InSpec tests to work with Train
- Cookstyle
Added:
- Data bag for placement service
- Set deprecations_as_errors to true in kitchen.yml
Removed:
- Unused statsd cookbook in Berksfile
- Unused .rubocop.yml
Deprecated:
- LBaaS recipes and tests. This has been deprecated upstream.
Change-Id: I53a28de6aad000a246ff8f610b64dd5201c03b27
Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: Ied3bb008208231bd4c9b6c2e86c716eac66267aa
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Remove obsolete sections from setup.cfg
- Update requirements, no need for python_version anymore
- Cleanup */source/conf.py to remove now obsolete content.
- Use newer openstackdocstheme version
Change-Id: I5f6aabc271e21fe8edbf2aadd2f78f8bdc407e80
- Update references from Rocky to Stein.
- Switch to using chef-workstation
- Exclude integration group from Berksfile. This is to ensure ChefSpec tests
should always work regardless if we're working on integration related
cookbooks that don't interact with those tests.
- Temporarily disable voting for integration tests due to cookbook version
conflicts
- Add tests for openstack-common::etcd and openstack-common::completions
- Update tests for Stein
- Update OVS port to check
- Add tests for lbaas but only for kitchen, not for CI pipeline
- Add suite and tests for integration-test
Change-Id: Id451b08e361acc709879a65d0d92b35640a5dba9
Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
Change-Id: Id4ba8fdf54276ce53601337b3006728724831084
Seems that since we are a deployment project, we should produce a
deployment guide rather than an installation guide. Using
what OpenStack-Ansible did as a guide.
Change-Id: I9740b7dbc8cf48c47e5bbc5d261f8736b00ee068
OpenStack Rocky is only supported on Ubuntu Bionic, so we no longer can
run any sensible tests on Xenial.
- Update default mariadb version to 10.1
Depends-On: https://review.openstack.org/645119
Depends-On: https://review.openstack.org/645162
Change-Id: Ifcf73e49a77e497b19700566a3a13ebfc9ca9741
Invalid HTTPS link was introduced in https://review.openstack.org/617749
Mailinglists have been updated. Openstack-discuss replaces openstack-dev
Change-Id: I2d77aad54d7021eb2ce4b1eec2be18aee3525f22
This change removes the markdown documentation in favor of a set of
rST documents generated with OpenStack branding.
Change-Id: I364ef53e24aed5f4721c5f3d56cc1d63966b4e88
- corrects grammatical flows
- updates for the current master release
- aligns documentation with local provisioning changes
- rewrites multinode doc to reflect network node
Change-Id: I820266b0f2885629211a917858ca7ea35f5f08d3
bridge interface can now be overriden using an environment variable
but will try common interface names if not entered.
Change-Id: I11cbac1044dc493ba20a8ae7fb300545c12df73f
* added new test scenarion allione (and all the needed files for it)
* removed old test scenarios aio-nova and aio-neutron as well as multi-neutron
and multi-node and the related files since they will not work with the
refactored cookbooks
* removed databag items for currently untested service cookbooks
* modified Rakefile to use new test scenarios for local and jenkins integration
testing
* adapted README and docs to fit new test setup and explain the new
attributes/template logic (with TODO)
* adapted Berksfile to use the master apache2 cookbook to comply with the
dependencies in identity and dashboard
* removed image_upload recipe since this is already done in the
integration-test::setup one
* moved recipe integration-test to a different chef_run to allow all services to
be restarted in delayed actions of first run before using them
* removed heat from the testing stack until refactored
* removed tempest unit tests 'run_tests.sh' from integration testing scenarion,
since there is no need to run tempests unit tests in our deployment
Depends-On: I0547182085eed91d05384fdd7734408a839a9a2c
Depends-On: I3262b2e6f792f37c32a446e6567790b82bdd4613
Depends-On: I80ed8a7892b59f7fd582505445a31b0df8d68752
Depends-On: Ia7fd927f42f4a1e484e8f2d34c52b1dc6d0ce6dd
Depends-On: Ifd11f86c576d7dbb709bdd302d41e39e900e1b74
Depends-On: Ida408a025f1a3e6a632108a9a32877026e286116
Depends-On: Idadc97bd7380d6c4f9f6f33d9c6b1215a5f24772
Depends-On: I9ac9eeb29ab27f31394830e4b6f999d5870cc0e4
Depends-On: Ifa5a7f4e1df47a3961976e64f654224864c3dcb4
Depends-On: I9cc1b5cc069987ac83e064322c2291772505ff5f
Implements: blueprint cookbook-refactoring
Change-Id: Icf0921229e9473a842d7ce5706027d56229e11d4
Added a list of possible interfaces for which the
vagrant provisioner will choose the first one that
is available. No more editing the test recipes.
Cleaned up the os selection to hide the
version specific stuff to be consistent with the
environment logic.
Fixed up some file modes.
Forced the chef client config directory as it can search
in bad places in some scenarios.
Change-Id: I38a7a86b58893b912af99fabf04ca9052f914346
It seems there are some changes that the local creation of aio-neutron
need to be updated with. This will fix and get aio-neutron working again.
Change-Id: I25881480e1fec261b5113a7b22d8cdc17bc286ac
We've had some people ask how to change the password from `mypass` these
are the steps to make that happen.
Change-Id: I5804186277b154c7120e9390dedfb328d78482a3
This tool allows a single patch to be tested against the chef repo.
It will to do job of cloning the repo, merging in the patch(s),
setting up the test and running it, basic queries and tempest.
Also enhanced the Berksfile to allow for easy local development.
Usage: chef exec ruby test_patch.rb help test
Change-Id: I32ba57c29f2f5caee0391ea791ffe10fe06caceb
Use a env var instead of manually editing repo files to use
centos. This also makes it easy for new tools like, test-patch
to switch between the platforms.
Next step will be to allow REPO_DEVICE= to easily
setup the network interfaces in the multi node cases.
I think env vars are a simple way to handle this, but we could also
consider an user config file ~/openstack-chef-repo.cnf. Thoughts?
Change-Id: I82e82b35b51e08ff503fdb10fa1ce041c4be4af2
The new testing suite is based upon Chef 12, Chef DK and
Chef Provisioning. It supports all in one and multi node
environments. It will be used as the base for future gate
integration testing. There's is more work to as noted in
the TODO list at the botton of the readme.
Note: to get this thru the existing gate, had to keep the existing
Gemfile. Added a Gemfile-Provisioning for new stuff and updated
readme with some notes on that. When we make the switch to kilo
rake gates, we can decide what type of gates the repo needs. I think
it's ready for rubocop at least and maybe continue with something
like spiecweasel to look at the role and environment syntax.
Added draft bootstrap and test default to rubocop to rakefile to
allow for easy integration with new gate rake jobs.
Change-Id: I187df8b78c4cecfb783ab26a6b66b8e8dd6745bd
Ghanshyam Mann