This updates all references of let(:chef_run) to cached(:chef_run) to
speed up tests. By doing this, we have to create a new cached(:chef_run)
block whenever we need to adjust node attributes for testing.
Speed was improved from 5 minutes 36 seconds to 48.07 seconds
Change-Id: I4e88431d863450b6f41d6711612bfb12d4024683
This provides a collection of fixes required to converge properly:
- fog-openstack-1.x already appends "auth/tokens" so we no longer need
to do that
- Remove references to deprecated
node['openstack']['api']['auth']['version'] attribute
- Remove creation of admin deprecated endpoints
- Add python-heat to common packages on Debian system so that the
heat-manage binary is available
- Remove and refactor use of deprecated identity_uri_transform function
Change-Id: Idfd9aed09ccd5c3871cac71dbe0b51c921f1ec0e
Signed-off-by: Lance Albertson <lance@osuosl.org>
This patch grants heat_domain_admin the admin role in the heat domain
(rather then in the service project).
We use :grant_domain instead of :grant_role, because we are setting a
role in a domain, not in a project.
Note that for the user to actually exist in the heat domain, a
sufficiently recent openstackclient cookbook is required -- otherwise
the domain_name attribute is ignored during user creation.
Also, we remove the user_name attribute (gets ignored by resource
action).
Change-Id: I747e2dedbc517cc3deb2675590fb982459c560a0
This patch removes the openstack_user resource with :grant_domain
action. A user is always created within a specific domain; such a
membership cannot be tacked on later. This resource gave the heat user
the role intended for its project for the domain (i.e., for the Default
domain instead of for the service project).
We add the domain_name attribute that creates the heat user in the
desired domain. Note that this change needs a sufficiently recent
openstackclient cookbook -- otherwise the domain_name attribute is
ignored (which does not matter as long as the heat user is to be created
in the Default domain).
Change-Id: Ifa3d344a3d9094dd1272b126a4dc9ab951c00972
This patch removes the role_name when using openstack_user's :create
action (it gets ignored by the target method).
Note that the spec test would still pass if only the line in
identity_registration.rb (but not the test) were changed, because the
code that actually does grant the role to the resource is executed right
after user creation and before any tests check the resource for the
existence of the role_name attribute. In other words: if the argument
were required in a call but only supplied in another call, the spec
tests would not catch it. Something to watch out for.
Change-Id: Ic45dd42453d9f8ae2a8c4d04f830cff67740cac6
- currently non-admin user aren't able to create stacks with i.e.
Resource OS::Heat::SoftwareDeployment
- added heat domain
heat domain_admin
heat_stack_owner and user role
- added missing configuration options
- fixed some smaller ruby /cookstyle offenses
Change-Id: I6ae544dcc6260050304e66e227383e0e944a6bb6
- Switched default linter to cookstyle
- Renamed rake tasks to better conform with Chef conventions
- Normalized template banner
Change-Id: Icc3eca4b2d17a6d1ef66c1c7e75513de0ee3cac9
- Now use cookbook-openstackclient to create endpoints role service and
user
- added domain creation and access granting
- added values to work with identity_v3
- rewrote specs to work again
- updated readme
Change-Id: If5c3758c786b2d11cec6d64dc57530367acd2976
Depends-On: I0f8955f05de9b33711c54b9a198f45018cceb8e1
* use new logic for heat.conf template
* move all attributes that are used in heat.conf to
attributes/heat_conf.rb
* remove all attributes that are just setting default values
* add new default attributes so that the authorisation setup will be
functional again
* refactored endpoint and bind_service logic to fit the new common
cookbook
* adapt specs accordingly
* removed qpid as a messaging option (can be included in a wrapper)
* removed fedora as supported platform
* removed deprecated Gemfile
* removed logic for setting up a dedicated domain for Heat, should be
done in a wrapper
* update README.md accordingly (still incomplete)
Implements: blueprint cookbook-refactoring
Change-Id: I16a29e28068d106f0edcbe04cb529aabbbed1ac5
- deprecated Gemfile
- updated TESTING and README
- updated Rakefile to use chef exec instead of bundle exec
- replaces Runner by SoloRunner in specs
Change-Id: Idb2180fb0cfd48b2c2c22e531b1f1320a0ab247b
Now that admin_endpoint, public_endpoint, and internal_endpoint
in the common library are working, these are the changes to use
them in the openstack-orchestration recipes.
Partial-Bug: 1412919
Change-Id: Ib89150c12ea833137b5f96c8ac5443c8aac364b4
Recently commit https://review.openstack.org/#/c/131698/ have
added some security related attributes. Add them into the recipe.
This command could also work under default configurations.
Change-Id: I0aa806874dabe040a395e96ecb2a6f62f658a6ec
To setup heat for template defined users, several identity registration
steps need to happen. The first is creating the role for it.
This can be done with the current identity registration provider.
The next three steps (doc in the code as todo) deal with the domain and
requires keystone v3 (bug-1267137). These are handled by a script shipped
with heat, heat-keystone-setup-domain.
Change-Id: I74154ccae609526ec92b916bac4ff8bc60aed170
Related-Bug: #1369654
https://review.openstack.org/73108
The original change does not work for the case where the api-cfn recipe
is included from within another recipe.
This revert does not cause any harm, it justs registers
api-cfn with identity unnecessarily.
The real solution is probably a refactoring of the common identity recipe.
Created blueprint identity-registration-cleanup for this future work.
Change-Id: I43646182a7465cdddd55b1f840764ba1b147451e
Closes-Bug: #1309123
- Set ['openstack']['orchestration']['region'] to equal ['openstack']['region']
- Add tests for endpoint creation, to confirm region is set.
Change-Id: Ie882f6da89f8e6a4324f7f19d3c9582671610629
Addresses: blueprint uniform-region
When the heat cloud formation (api-cfn recipe) is not needed and
not used, the identity recipe still creates service and endpoint
identity registrations for it. I added a check to see if the
api-cfn recipe is in the run_list, suggestions welcome for better
ways to approach this.
Change-Id: I5f326a66f005f0553aecd8cea798a224d76f57c4
Closes-bug: 1279577
It appears orchestration was missing in the rubocop blueprints. Bringing it
up to par with the other cookbooks.
- Update rubocop config to include spec/**
- Update specs to comply with rubocop
- Delete unused default spec file
Change-Id: Ie96c16fc82a4ca2c04e20fc7db2b036937f0ba04
This new cookbook supports the installation and configuraiton for heat services.
More pedantic patches will follow to make Rubocop happy.
Implements: blueprint heat-support
Change-Id: I8b734b7124c49190a68acc4d0da28a31da03ac57
Ghanshyam Mann