[orchestration]Use openstackclient instead of heat-keystone-setup-domain tool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack + Chef |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Now we using heat-keystone-
https:/
execute 'heat-keystone-
environment 'OS_USERNAME' => admin_user,
command "heat-keystone-
end
But it's not recommended, and this tool may removed in the future.
It's better using openstackclient to create HEAT_DOMAIN and HEAT_DOMAIN_ADMIN for heat.
tags: | added: client heat |
tags: |
added: orchestration removed: heat |
Changed in openstack-chef: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in openstack-chef: | |
milestone: | none → liberity-rc1 |
Changed in openstack-chef: | |
status: | Fix Committed → Fix Released |
Base fix for this should go into the new client cookbook and then have the heat cookbook take advantage of that.
Here are the related blueprints on this:
https:/ /blueprints. launchpad. net/openstack- chef/+spec/ domain- support /blueprints. launchpad. net/openstack- chef/+spec/ decouple- lwrp-from- image-cookbook /blueprints. launchpad. net/openstack- chef/+spec/ identity- registration- cleanup /blueprints. launchpad. net/openstack- chef/+spec/ identity- registration- refactor /blueprints. launchpad. net/openstack- chef/+spec/ nova-network- lwrp
https:/
https:/
https:/
https:/