> -----Original Message----- > From: Edward Leafe [mailto:e...@leafe.com] > Sent: 05 May 2016 04:32 > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [nova][osc] Use of openstack client for admin > commands > > On May 4, 2016, at 3:53 PM, Jay Pipes <jaypi...@gmail.com> wrote: > > > My position is that if it's an HTTP API (as opposed to something like a > sqlalchemy-migrate sync command) then it belongs in a client that speaks the > OpenStack HTTP APIs. That is OSC as far as I can tell. I don't see a > difference > between "admin" commands and "standard" commands. > > Exactly. If it's an admin command and you're not an admin, you get an error. > No need for a separate client. >
And more to the point, as far as I can tell it's only a statement in policy that determines which role can use the command. Any operator can change the policy and suddenly any division between clients becomes pure nonsense. > > -- Ed Leafe > > > > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
