Open Stack

Hey Ronald,

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 suggested). The reason for this is that in OSC we try not 
to abbreviate when possible. 

Also, instead of 'update', is this analogous to user update or volume 
update? We've been using the key term 'set' instead wherever possible.

For a complete list of current commands in vanilla OSC: 
http://docs.openstack.org/developer/python-openstackclient/command-list.html 
(see the lack of update :))

Thanks,

Steve Martinelli
OpenStack Keystone Core

Adrian Otto <adrian.otto at rackspace.com> wrote on 05/24/2015 10:35:12 PM:

> From: Adrian Otto <adrian.otto at rackspace.com>
> To: "OpenStack Development Mailing List (not for usage questions)" 
> <openstack-dev at lists.openstack.org>
> Date: 05/24/2015 10:35 PM
> Subject: Re: [openstack-dev] [openstackclient] [magnum] Review of 
> object and actions for magnumclient implementation
> 
> Thanks for taking the initiative on this! Remarks in-line...
> 
> On May 24, 2015, at 11:20 AM, Ronald Bradford <me at ronaldbradford.com> 
wrote:

> I have outlined in the blueprint  (https://blueprints.launchpad.net/
> python-openstackclient/+spec/magnum-support) the object and actions 
> mappings that are currently available in the magnumclient.
> 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 ]
> Ok.
> container [ execute | start | stop ]
> Consider using exec instead of execute. This would more closely 
> match the docker CLI, and improves usability. Consider patching this
> in the API and python-magnumclient to keep it consistent. This will 
> tighten up the user experience for those using both Magnum through 
> OSC and Docker natively on Docker Swarm bays.
> 
> Start and stop are ok.
> pod [ update ]
> Ok.
> replication controller [ update ]
> Use "rc" here so we do not have a two word noun.
> service [ update ]
> Ok.
> 
> Thanks,
> 
> Adrian
> I would appreciate feedback on if these actions "update", "execute",
> "start" and "stop" are appropriate to use.
> Regards
> Ronald
> 
__________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
__________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150525/4a445ce0/attachment.html>