Re: [Openstack] OSAPI and Zones

2011-11-15 Thread Doude
Thanks a lot for your answers.

But why do you want to move the Zone code into the extension part ?
It's a core part of OpenStack, why it doesn't stay in the core code ?

Another question about extensions. I had understand that an extension
will be integrated to the core OSAPI when it will be mature, is that
true ? The extension mechanism is like an incubator for OSAPI
functionalities ?

Regards,
Édouard.

 On Mon, Nov 14, 2011 at 7:09 PM, Sandy Walsh sandy.wa...@rackspace.com 
 wrote:
 Jorge is correct. The zones stuff was added before the API was finalized and
 before the extensions mechanism was in place. We simply haven't taken the
 time to convert it yet.

 -S
 
 From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net
 [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf
 of Anne Gentle [a...@openstack.org]
 Sent: Monday, November 14, 2011 12:25 PM
 To: Doude
 Cc: openstack@lists.launchpad.net
 Subject: Re: [Openstack] OSAPI and Zones

 Hi Édouard -

 I believe zones are documented in the Developer docs in
 http://nova.openstack.org/devref/zone.html. The howto scenarios are
 documented using the nova python client only currently (probably due to the
 refactoring Jorge mentions).

 When you run into these gaps, please do log a bug against either nova or
 openstack-manuals (http://bugs.launchpad.net/openstack-manuals). The
 nova-docs team is small and working through a backlog of such items, and
 bugs definitely help with prioritization and tracking.

 Thanks,

 Anne


 On Mon, Nov 14, 2011 at 9:49 AM, Doude doudou...@gmail.com wrote:

 Hi all,

 I'm trying to understand the multi-zone architecture of OpenStack.
 I saw zone commands (list, show, select ...) have been added to the
 OSAPI v1.1 (not as an extension but as a core component of the API)
 but I cannot find any documentations in the OSAPI book:

 http://docs.openstack.org/trunk/openstack-compute/developer/openstack-compute-api-1.1/content/

 Where I can find this documentation ? In OpenStack wiki ? Where I can
 open a bug about this lack of documentation ?

 Regards,
 Édouard.

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to     : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] OSAPI and Zones

2011-11-15 Thread Jorge Williams
Inline:

On Nov 15, 2011, at 3:36 AM, Doude wrote:

 Thanks a lot for your answers.
 
 But why do you want to move the Zone code into the extension part ?
 It's a core part of OpenStack, why it doesn't stay in the core code ?

If something is in core then it's guaranteed to be available always.  A client 
should be able to count on the functionality in core for a particular version 
of an API.  Zone's offer admin level functionality that may not be available to 
all users.  I don't think that Rackspace will expose Zones to it's customers 
right away, for example. By having Zones as an extension a client can detect 
whether zone support is available or not.

 
 Another question about extensions. I had understand that an extension
 will be integrated to the core OSAPI when it will be mature, is that
 true ? The extension mechanism is like an incubator for OSAPI
 functionalities ?

Yes, the extension mechanism can be used as an incubator for functionality.   
But, not all extensions are destine to make it to the core.  Some extension for 
example will cover niche functionality that may be useful for a small set of 
users. Other extension may cover functionality that would set the bar high for 
folks deploying OS clouds. Other extension may expose functionality that's 
applicable to a specific hypervisor etc.

That said, at the end of the day, the PTL decides which of these extensions 
make it to core and which stay as extensions.

I've got a draft of a write up to explain extensions in some detail here:

https://github.com/RackerWilliams/OpenStack-Extensions/blob/master/apix-intro.pdf

Nothing there is set entirely in stone, but it drafts the concept as we're 
currently thinking of  it.  I'm in the process of setting up an extension 
registry and documenting a number of extensions. These certainly inform the doc 
above -- so expect some changes.  As soon as things stabilize I'll publish the 
doc in our doc site.

-jOrGe W.


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] OSAPI and Zones

2011-11-15 Thread Ed Leafe
On Nov 15, 2011, at 7:18 AM, Jorge Williams wrote:

 But why do you want to move the Zone code into the extension part ?
 It's a core part of OpenStack, why it doesn't stay in the core code ?
 
 If something is in core then it's guaranteed to be available always.  A 
 client should be able to count on the functionality in core for a particular 
 version of an API.  Zone's offer admin level functionality that may not be 
 available to all users.  I don't think that Rackspace will expose Zones to 
 it's customers right away, for example. By having Zones as an extension a 
 client can detect whether zone support is available or not.

It was my understanding that zones would be transparent to the user; in 
fact, we went to great pains to ensure that zone information was *not* 
available to the user. Clients would not need to detect if zones exist.


-- Ed Leafe


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] OSAPI and Zones

2011-11-14 Thread Jorge Williams
Last time I had a conversation about this, I believe the goal was to refractor 
and document Zone support as an extension to the core API.  We're just not 
there yet.

-jOrGe W.

On Nov 14, 2011, at 9:49 AM, Doude wrote:

 Hi all,
 
 I'm trying to understand the multi-zone architecture of OpenStack.
 I saw zone commands (list, show, select ...) have been added to the
 OSAPI v1.1 (not as an extension but as a core component of the API)
 but I cannot find any documentations in the OSAPI book:
 http://docs.openstack.org/trunk/openstack-compute/developer/openstack-compute-api-1.1/content/
 
 Where I can find this documentation ? In OpenStack wiki ? Where I can
 open a bug about this lack of documentation ?
 
 Regards,
 Édouard.
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] OSAPI and Zones

2011-11-14 Thread Anne Gentle
Hi Édouard -

I believe zones are documented in the Developer docs in
http://nova.openstack.org/devref/zone.html. The howto scenarios are
documented using the nova python client only currently (probably due to the
refactoring Jorge mentions).

When you run into these gaps, please do log a bug against either nova or
openstack-manuals (http://bugs.launchpad.net/openstack-manuals). The
nova-docs team is small and working through a backlog of such items, and
bugs definitely help with prioritization and tracking.

Thanks,

Anne


On Mon, Nov 14, 2011 at 9:49 AM, Doude doudou...@gmail.com wrote:

 Hi all,

 I'm trying to understand the multi-zone architecture of OpenStack.
 I saw zone commands (list, show, select ...) have been added to the
 OSAPI v1.1 (not as an extension but as a core component of the API)
 but I cannot find any documentations in the OSAPI book:

 http://docs.openstack.org/trunk/openstack-compute/developer/openstack-compute-api-1.1/content/

 Where I can find this documentation ? In OpenStack wiki ? Where I can
 open a bug about this lack of documentation ?

 Regards,
 Édouard.

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] OSAPI and Zones

2011-11-14 Thread Sandy Walsh
Jorge is correct. The zones stuff was added before the API was finalized and 
before the extensions mechanism was in place. We simply haven't taken the time 
to convert it yet.

-S

From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net 
[openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of 
Anne Gentle [a...@openstack.org]
Sent: Monday, November 14, 2011 12:25 PM
To: Doude
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] OSAPI and Zones

Hi Édouard -

I believe zones are documented in the Developer docs in 
http://nova.openstack.org/devref/zone.html. The howto scenarios are 
documented using the nova python client only currently (probably due to the 
refactoring Jorge mentions).

When you run into these gaps, please do log a bug against either nova or 
openstack-manuals (http://bugs.launchpad.net/openstack-manuals). The nova-docs 
team is small and working through a backlog of such items, and bugs definitely 
help with prioritization and tracking.

Thanks,

Anne


On Mon, Nov 14, 2011 at 9:49 AM, Doude 
doudou...@gmail.commailto:doudou...@gmail.com wrote:
Hi all,

I'm trying to understand the multi-zone architecture of OpenStack.
I saw zone commands (list, show, select ...) have been added to the
OSAPI v1.1 (not as an extension but as a core component of the API)
but I cannot find any documentations in the OSAPI book:
http://docs.openstack.org/trunk/openstack-compute/developer/openstack-compute-api-1.1/content/

Where I can find this documentation ? In OpenStack wiki ? Where I can
open a bug about this lack of documentation ?

Regards,
Édouard.

___
Mailing list: 
https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack
Post to : 
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Unsubscribe : 
https://launchpad.net/~openstackhttps://launchpad.net/%7Eopenstack
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp