- 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
Most of the changes are in the integration cookbook, they consist of
- Setup a nano flavor to avoid Not Host Available issues
- Run just smoke and in serial to avoid out of memory issues
- Setup a floating ip range
- Disable volume snapshot
- dont install python virtualenv
Share the local-net to allow tempest to use it as well.
Create volumes per pass to avoid collisions.
Depends-On: I42216a174930b17a4771e78c639da54e170a288c
Change-Id: Ia988fd4a8aec84d3e4dd8c45a4f49eb401875504
* 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
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
- This is a StackForge project now, it should be reflected such
- Cleanup references to OpenStack (and associated projects)
- Sundry cleanup
Change-Id: I26b0900badeb2a1770a8159f2c16745404887548
To eliminate one more step in the process of running our repo steps,
added create_key task and made the test task depend upon it.
The other manual step is to run the berk_vendor task, but I hesitate
to include that in the test tasks as most developers are always messing
around with the code and would not like it blown away all the time.
Change-Id: I57c4fd8118c289386552e0ed1087959883724ec4
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
This will helpful for beginners to know the basic workflow of
openstack-chef-repo, and it's a good start for beginners to deploy
OpenStack environment through Chef.
Change-Id: I28c01ecb0fafa46fcf73ef8176eabe6806be207f
The README still included references to Opscode sites
The references were updated to point to correct Chef sites
Change-Id: I15f68d7a6946e51a4e82ee4b4b6af0f9f5fc3b19
Berkshelf 3.x has been out of beta for a while and the install
command is no longer supported. This is a quick update to the
documentation to make the bootstrap commands work.
Change-Id: I777a95d868ff51bc26ca40a314fa86df01beb660
From the other environment file, the convention seems to be dashes
instead of underscores in Chef names. This patches matches the
object name with the filename for the zero-demo environment.
Change-Id: I3ecf2b07f1ac6d54943fed7b2fbf85a049fe3092
Recent commit e3db2693b50d9d950adc6119135403eb235335ab created the
'ceilometer' user. A 'monitoring' user is left over and being created
but it isn't being used. This patch removes a reference to it in the
documentation.
Change-Id: I503b7e3d2d6484126f8e798a36fb47f6f717e17a
When you don't use the developer_mode you need to have crypted databag to store the openstack password.
This patch explain all the items you need and add some example of the items schema.
Change-Id: I67d6bfecb9df2da92af064793ad6d3676f93bbc8
Closes-Bug: #1282457
Berksfile.lock is not updated so points to old versions of each of the
stackforge cookbooks. Removing this file ensures that a user gets the
most recent stackforge cookbooks when installing with berkshelf.
Add Berksfile.lock to .gitignore so that another version isn't
committed.
Update Readme with note about Berksfile.lock
Change-Id: I8ea3223e98ac4dbab94e45f2323c6dcea2b54504
set openstack-image::identity_registration recipe after
openstack-image::api and openstack-image::registry,
so that identity endpoint can be registered.
Change-Id: I524434a23328046c2b0e28d6b62a45ef31b11ef1
The Vagrant box is the default 12.04 and 13.04 provided by Opscode's Bento
project. It uses the Vagrant plugins vagrant-berkshelf, vagrant-cachier,
vagrant-chef-zero and vagrant-omnibus. Unfortunately Chef Zero does not
understand .rb files yet, so we're using the recipes directly in the run
list. This also means that searching by roles is broken so this needs to be
fixed ASAP.
Change-Id: I5fe8b175f15c4a21c16de46bc05ec6a0c27cfdaa
* Adds instructions for using Vagabond to test the
Chef repository.
* Add a new testing environment file that is specific
to Vagabond
* An ops, compute controller and compute worker node
added to the vagabond environment
Change-Id: Id15201b9b870c51d337d8d07fca5e42ca8aaf385