- include Artful instead of Zesty to keep up with the times
- update cirros references to 0.4.0
- remove stale repo reference
Change-Id: I8b63581849d9c7e9d67d56e16619191703868755
Implements: blueprint modern-chef
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I820c9462836bb3c6830d4c2246505482c0c4c455
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 user the
role intended for their 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 glance 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 glance user is to be
created in the Default domain).
Change-Id: I07086d9ab65581cdcd77d402fe0d513b03a0af69
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: I6d98e0603cc4d8fa2dd21cd402adbbe888fbe4f3
- Removed ancient Gemfile
- Style and lint fixes to support newer chefdk
- Rewrote metadata.rb for readability
Change-Id: Ie61ae3ca685738fe1de98fc9223d3e39535ce000
- 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
- added domain to image-upload
edited resource / provider
Change-Id: If7b4d6e563081a0be9957353d73ef61a9688df56
Depends-On: I0f8955f05de9b33711c54b9a198f45018cceb8e1
Since glance could be used to upload images,
make sure it's restarted immediately within the recipe.
Change-Id: Ie4a742a2a8aaeeec2886fcc0513e654d0237997c
I think it's more correct to use a normal user, admin,
to upload images, instead of using the service accounts.
Change-Id: Ifb1411a4392d04cd9a5e867ffc95327adf4ea4ea
On recent test machines, curl isn't available anymore, so use wget
instead. Piping directly into bash isn't that great anyway.
Change-Id: Ie8dc2c9dacbd5f64fbad47b176a88e053e2e8ae5
* endpoint type (admin, internal, public) and service (identitiy, network etc.)
was switched during refactoring, this patch reverts this unintended switching
* edited bind_service service type from public,internal,admin to 'all'
for default binding to just one service
* use bind_address method from common
Change-Id: I4f97b659361dabd7fac216305d2aad2f1bb98f51
Depends-On: Iec485deaf415e4187a323435cce2b6bbadfc5d42
Depends-On: Ia5bddfc5e2fd77cd6e9e855c680b079f78fc1c3f
* removed rubocop exceptions in recipes and regenerated the
.rubocop_todo.yaml containing all remaining exceptions
* removed fedora, suse as supported platform
* adapted optimized endpoint logic
* moved endpoints from openstack-common to default attr
* bumbed openstack-common and identity to higher version
due to refactoring
* moved version up to 13.0.0
* adapt the specs (unit tests) to work again
* added new logic into templates/default/glance-*.conf.erb
* refactored attributes throughout all recipes that were connected to
the attributes used for the glance-*.conf.erb template to adapt the new
template attribute syntax
* moved all attibutes/default.rb that were used in glance-*.conf.erb to
attributes/glance_*_conf.rb
* removed all attributes from default.rb and glance-*.conf.erb which are set
as default in attributes, openstack doc and used to render the template
* seperated filestore config and deployment from default api recipe and made it
optional (e.g. swift_store)
* removed service config templates in favor of openstack-service.conf.erb from
common cookbook
* removed default support for most filestore backends in favor of an easily
wrappable cookbook structure which allow the configuration of filestore
backends in wrappers
Depends-On: I3262b2e6f792f37c32a446e6567790b82bdd4613
Depends-On: I0547182085eed91d05384fdd7734408a839a9a2c
Implements: blueprint cookbook-refactoring
Change-Id: Ifa5a7f4e1df47a3961976e64f654224864c3dcb4
--is-public is now --visibility
--location is not support, need to redirect from stdin
Change-Id: Ie8d62b449ec272f5cb7a06acdd54b3437aa57f98
Closes-Bug: #1502204
Add missing gate integration task, but use the one from
Common cookbook to make future updates easy.
Change-Id: Ieeb59c9cd51b26300366944dcd30cdc207f90bd7
Depends-On: I4834e9557b07db05591b78d28ef27a6046e4c0f0
* current logic with 'directory ::File.dirname node.attr' will create resources
with the same name 'directory '/var/cache/glance', but different parameters
(so only the first one will be executed) (recipes/api and /registry)
* fixed logic and specs to actually use the full node attributes and create the
two caching directories
Change-Id: I6289bf7a8b7b1a998ad4cefef04021ec02fe4172
The format of the default chef banner is not considered as a comment in
json file. The comment for json file should start with "//" or "/* */".
This patch remove the chef banner in glance metadata template.
Change-Id: I70d3f3d5d03704880c66a850a38441084154a62e
Closes-Bug: #1485893
After this path has been merged : https://review.openstack.org/#/c/190265/
The compute service has the ability to copy the image data from the mountpoint
directly which can save image download time.
This patch make the metadata file can be generated automatically if user
specify the id and mountpoint.
Change-Id: Ibd4cc2d15a97f8018fc7f0aa19e4f2c9d1da285c
The ['openstack']['image']['ssl']['enabled'] was being used for
both the API/Regsitry services AND the APIs internal connection
to the registry.
Need to allow for separate control for enabling SSL for API and Registry.
Added attributes to cover this.
And the APIs internal connection to the registry needs to be
configured correctly based upon the Registry's internal endpoint scheme
(http or https).
Change-Id: Ieed28ad891192d81356c0d40ba48d70517087950
Closes-Bug: #1462388
In order to allow components to better handle and respond to mq failures,
oslo has some heartbeat options that are useful.
Change-Id: I41b3fc4699a4f285e9fcb066da55bb8a7f1361a2
Partial-Bug: #1462438
OpenDev Sysadmins