OpenStack Heat

HEAT::HA::Restarter': Restarter should us OS:: namespace

Bug #1100242 reported by Steven Hardy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Low
Steven Hardy
OpenStack Heat 2013.1 "grizzly"
Grizzly
Fix Released
Low
Steven Hardy
OpenStack Heat grizzly-3 "g3"

Bug Description

We seem to have adopted the OS:: namespace for our non-AWS openstack native resources (ref all the OS::Quantum resources), so we should probably change the HEAT::HA::Restarter resource to be OS::HA::Restarter

Steven Hardy (shardy)
Changed in heat:
status: New → Triaged
importance: Undecided → Low
Steven Dake (sdake)
Changed in heat:
milestone: none → grizzly-3
Steven Hardy (shardy)
Changed in heat:
assignee: nobody → Steven Hardy (shardy)
Revision history for this message
Zane Bitter (zaneb) wrote :

How about OS::Heat::HARestarter? On the principle that the second-level of the OS:: namespace should be the name of the service.

Revision history for this message
Steven Hardy (shardy) wrote :

> OS::Heat::HARestarter

Sounds good - my main concern was the fragmentation of the first level of the identifier, so sticking to Provider::Service::Resource makes sense

Steven Hardy (shardy)
Changed in heat:
status: Triaged → In Progress
Revision history for this message
Steven Hardy (shardy) wrote :

Fix committed but I forgot the bug number in the commit message:

https://review.openstack.org/#/c/20251/

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: grizzly-3 → 2013.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.