For reference, the current list of objects and actions used by commands in
the OSC repo are at
Also note that while the OSC team may have multiple opinions on what fits
well and does not in plugins, the plugins are owned by
To summarize. I believe we have 3 decisions from my original email but I
have also uncovered some more problems.
1. replication controller instead of rc
Adrian, regarding rc and replication controller. The OSC uses verbose
commands including multi words. This includes availability zone, volume
I have outlined in the blueprint (
the object and actions mappings that are currently available in the
I have separated the list of actions that are presently used and actions
that are not for review and
I think the “update” action is definitely appropriate to use, since it is not
specific to magnum (Heat and Ironic use it as well). By looking through the
existing list of actions , it looks the start/stop actions fits into the
openstackclient resume/suspend actions. The “execute”
Thanks for taking the initiative on this! Remarks in-line...
On May 24, 2015, at 11:20 AM, Ronald Bradford
I have outlined in the blueprint
Thanks for asking first, as more folks are adopting OSC plugins for their
respective clients we should probably streamline this a bit, but the ML
works for now.
Just 2 remarks...
I'd actually prefer 'replication controller' (which you prefer) instead of
'rc' (as adrian