Hi Ronald,

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 [1], it looks the start/stop actions fits into the 
openstackclient resume/suspend actions. The “execute” action looks to be 
magnum-specific, and it is rarely used. We could either skip adding it to 
openstackclient or propose a new action in here.


[1] http://docs.openstack.org/developer/python-openstackclient/commands.html

From: Ronald Bradford [mailto:m...@ronaldbradford.com]
Sent: May-24-15 2:14 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [openstackclient] [magnum] Review of object and 
actions for magnumclient implementation

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 discussion. Specifically These actions DO NOT match.

bay [ update ]
container [ execute | start | stop ]
pod [ update ]
replication controller [ update ]
service [ update ]

I would appreciate feedback on if these actions "update", "execute", "start" 
and "stop" are appropriate to use.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to