openstack team mailing list archive

[Sandy Walsh <sandy.walsh@xxxxxxxxxxxxx>]

k, admin-only OpenStack API it is ... thanks for the prompt feedback guys!

-S

________________________________________
From: Jay Pipes [jaypipes@xxxxxxxxx]
Sent: Tuesday, February 08, 2011 7:09 PM
To: Devin Carlen
Cc: Sandy Walsh; openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] Do these commands belong in the API or nova-manage?

On Tue, Feb 8, 2011 at 6:07 PM, Devin Carlen <devin.carlen@xxxxxxxxx> wrote:
> Yep, you're right. I misread.  There is still a longer conversation to be had about admin API in general.  All the functions in the ec2 admin api will need to be available in the openstack admin api at some point.

Yeah, agreed. Or at least, the ones that make sense :)

These new multi-cluster/zone admin commands for the OpenStack API are
*kinda* like the EC2 regions commands, but different...

-jay

> On Feb 8, 2011, at 5:01 PM, Jay Pipes wrote:
>
>> I think you are confusing the EC2 admin API with what Sandy was
>> talking about, which is the OpenStack admin API commands, which has
>> been in Nova for months now. See /nova/api/openstack/__init__.py,
>> lines 74 through 81.
>>
>> -jay
>>
>> On Tue, Feb 8, 2011 at 5:58 PM, Devin Carlen <devin.carlen@xxxxxxxxx> wrote:
>>> Only place for it to go now is the ec2 admin extension api (nova/api/ec2/admin.py).
>>>
>>> Until we get the OpenStack API out in the open, we can't add anything to it.
>>>
>>> The goal is to move the admin functions to the OpenStack API when that becomes an option, but I'm guessing that won't be until diablo.
>>>
>>> On Feb 8, 2011, at 4:54 PM, Jay Pipes wrote:
>>>
>>>> On Tue, Feb 8, 2011 at 5:09 PM, Sandy Walsh <sandy.walsh@xxxxxxxxxxxxx> wrote:
>>>>> Quick question ...
>>>>> For multi-cluster/zones I have a bunch of commands that need to be exposed
>>>>> to administrators:
>>>>> 1. CRUD child zones
>>>>> 2. CRUD hosts to a zone
>>>>> 3. CRUD zone & host capabilities to a zone
>>>>> Do you think these belong in the admin-only OpenStack API or only available
>>>>> via nova-manage?
>>>>
>>>> Admin-only OpenStack API, since they won't have anything to do with
>>>> EC2 API, and at this point, nova-manage is very EC2-centric, and
>>>> adding it to nova-manage could potentially be extremely confusing.
>>>>
>>>> Since this functionality is mostly going to be used by service
>>>> providers, most of which have their own set of custom management tools
>>>> (see: python-novatools, etc..), I think it's best to stick it only in
>>>> the admin API for now.
>>>>
>>>> My 1.5 cents,
>>>> -jay
>>>>
>>>>> Perhaps just the (R)ead operations are available via the API and CUD via
>>>>> nova-manage?
>>>>> Opinions?
>>>>> -Sandy
>>>>>
>>>>> Confidentiality Notice: This e-mail message (including any attached or
>>>>> embedded documents) is intended for the exclusive and confidential use of
>>>>> the
>>>>> individual or entity to which this message is addressed, and unless
>>>>> otherwise
>>>>> expressly indicated, is confidential and privileged information of
>>>>> Rackspace.
>>>>> Any dissemination, distribution or copying of the enclosed material is
>>>>> prohibited.
>>>>> If you receive this transmission in error, please notify us immediately by
>>>>> e-mail
>>>>> at abuse@xxxxxxxxxxxxx, and delete the original message.
>>>>> Your cooperation is appreciated.
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~openstack
>>>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~openstack
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Mailing list: https://launchpad.net/~openstack
>>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~openstack
>>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>
>


Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace. 
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@xxxxxxxxxxxxx, and delete the original message. 
Your cooperation is appreciated.