walsh=rackspace@lists.launchpad.net[openstack-bounces+sandy.walsh=
> rackspace@lists.launchpad.net] on behalf of Thierry Carrez [
> thie...@openstack.org]
> Sent: Wednesday, January 05, 2011 4:38 AM
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] [RFC] OpenStack
On Jan 8, 2011, at 9:47 AM, Sandy Walsh wrote:
> Hi!
>
> I just read the EasyAPI BP and, from a technical perspective, seems rational
> and sound. The challenge, of course, are the implications for the business
> side of the house. I realize it doesn't make sense to strive for backward
> comp
k.org]
Sent: Wednesday, January 05, 2011 4:38 AM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] [RFC] OpenStack API
ksan...@doubleclix.net wrote:
> I have added a new blue print
> https://blueprints.launchpad.net/nova/+spec/open-stack-api and
> associated wiki page to capture an
_
From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net
[openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of
ksan...@doubleclix.net [ksan...@doubleclix.net]
Sent: Wednesday, January 05, 2011 12:39 PM
To: Thierry Carrez
Cc: openstack@lists.launchpad.net
Subj
ld be happy to work with Sandy - always better to enhance what is already there. Moreover, RackSpace Cloud API is a good start.d) This topic might be a good discussion point at the next design summit, here in Santa Clara.Cheers
Original Message ----
Subject: Re: [Openstack] [RFC]
ksan...@doubleclix.net wrote:
> I have added a new blue print
> https://blueprints.launchpad.net/nova/+spec/open-stack-api and
> associated wiki page to capture and make some progress.I have a
> launchpad account from my Ubuntu days.
Hey ksankar,
We already have a blueprint to cover the Openstack
with the component level and ogress upwards towards more granular abstractions, as needed.Developing an Open Stack Cloud System-level CLI might be a good start ...Cheers
Original Message
Subject: Re: [Openstack] [RFC] OpenStack API
From: Erik Carlin <erik.car...@rackspace.c
011 05:00:56 +
To: "mailto:ksan...@doubleclix.net>>"
mailto:ksan...@doubleclix.net>>
Cc: "mailto:openstack@lists.launchpad.net>>"
mailto:openstack@lists.launchpad.net>>
Subject: Re: [Openstack] [RFC] OpenStack API
I think I agree with most of what
nStack
Framework Model thread.
Cheers
P.S : Do we already have a blueprint for this ?
-------- Original Message
Subject: Re: [Openstack] [RFC] OpenStack API
From: Jorge Williams
mailto:jorge.willi...@rackspace.com>>
Date: Tue, January 04, 2011 1:39 pm
To: Vishvananda Ishaya mailto:
penStack Framework Model thread. CheersP.S : Do we already have a blueprint for this ?
Original Message
Subject: Re: [Openstack] [RFC] OpenStack API
From: Jorge Williams <jorge.willi...@rackspace.com>
Date: Tue, January 04, 2011 1:39 pm
To: Vishvananda Ishaya <vishvana
sts.launchpad.net] On Behalf Of
ksan...@doubleclix.net<mailto:ksan...@doubleclix.net>
Sent: Tuesday, January 04, 2011 12:37 PM
To: Vishvananda Ishaya
Cc: openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>
Subject: Re: [Openstack] [RFC] OpenStack API
Good point - thi
nt: Tuesday, January 04, 2011 12:37 PM
> To: Vishvananda Ishaya
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] [RFC] OpenStack API
>
> Good point - this was my concern on "REST API for developers" in the other
> thread. Relative stability, versioning, pu
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf Of
ksan...@doubleclix.net
Sent: Tuesday, January 04, 2011 12:37 PM
To: Vishvananda Ishaya
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [RFC] OpenStack API
Good point - this was my concern on "REST AP
te it should probably
interact with the official versioned openstack api.
>
> If there are two distinct constituents, with clear cut requirements and
> interfaces, we can work through programming models and appropriate APIs.
>
> Cheers
>
> Original Message
&
d appropriate APIs. Cheers
Original Message ----
Subject: Re: [Openstack] [RFC] OpenStack API
From: Vishvananda Ishaya <vishvana...@gmail.com>
Date: Tue, January 04, 2011 9:32 am
To: Ed Leafe <e...@leafe.com>
Cc: openstack@lists.launchpad.net
Sure. DevAPI perhaps?
Another point that migh
Sure. DevAPI perhaps?
Another point that might help clarify: Each component of Nova exposes an "api"
to the other components in the system via python methods. You could refer to
these as the "internal api" for that component. Both the OS api and the EC2
api use this internal api, for example
On Jan 3, 2011, at 8:32 PM, Vishvananda Ishaya wrote:
> I feel very strongly that we need to keep the code easy to extend and
> prototype, without forcing developers to go through the process of api specs
> and versioning. I don't think this is going to happen through the
> OpenStack/Rackspace
nstack@lists.launchpad.net
> [mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf
> Of Jay Pipes
> Sent: Friday, December 31, 2010 5:29 AM
> To: Thierry Carrez
> Cc: openstack@lists.launchpad.net
> Subject: Re: [Openstack] [RFC] OpenStack API
>
&
John Purrier wrote:
> Sounds like we need to update the blueprints for Bexar (quickly) to include
> the OpenStack API 1.0 command line tools. I believe Sandy Walsh is working
> on these.
Then I encourage Sandy to quickly create a blueprint, use it to describe
briefly his plan and ping me about it
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf Of
Jay Pipes
Sent: Friday, December 31, 2010 5:29 AM
To: Thierry Carrez
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [RFC] OpenStack API
On Fri, Dec 31, 2010 at 4:22 AM, Thierry Carrez wrote:
> John Purrier wr
in Cactus.
Thanks,
-John
From: Christopher MacGown [mailto:ign...@gmail.com]
Sent: Thursday, December 30, 2010 5:28 PM
To: John Purrier
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [RFC] OpenStack API
Hi guys,
It is clearly important to establish a viable OpenStack
+john=openstack@lists.launchpad.net
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf
Of Thierry Carrez
Sent: Saturday, January 01, 2011 4:06 AM
To: Jorge Williams
Cc:
Subject: Re: [Openstack] [RFC] OpenStack API
Jorge Williams wrote:
> Right. API extensions are par
Jorge Williams wrote:
> Right. API extensions are part of the OpenStack compute API 1.1. Step 4
> states that that's not in the roadmap until Cactus. Step 1 is an
> implementation of the existing Cloud Servers API 1.0 as it exists today --
> without extension support, the idea is that this sho
On Dec 31, 2010, at 5:28 AM, Jay Pipes wrote:
> On Fri, Dec 31, 2010 at 4:22 AM, Thierry Carrez wrote:
>> John Purrier wrote:
>>> 1. Bexar will present a version 1.0 OpenStack API based on the 1.0
>>> Rackspace Cloud Servers API. The OpenStack namespace will be set up and
>>> published, an
e@lists.launchpad.net] on behalf of
Jay Pipes [jaypi...@gmail.com]
Sent: Friday, December 31, 2010 7:28 AM
To: Thierry Carrez
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [RFC] OpenStack API
On Fri, Dec 31, 2010 at 4:22 AM, Thierry Carrez wrote:
> John Purrier wrote:
>
On Fri, Dec 31, 2010 at 4:22 AM, Thierry Carrez wrote:
> John Purrier wrote:
>> 1. Bexar will present a version 1.0 OpenStack API based on the 1.0
>> Rackspace Cloud Servers API. The OpenStack namespace will be set up and
>> published, and tools will be available that manipulate Nova via the
John Purrier wrote:
> 1. Bexar will present a version 1.0 OpenStack API based on the 1.0
> Rackspace Cloud Servers API. The OpenStack namespace will be set up and
> published, and tools will be available that manipulate Nova via the
> OpenStack API. Any functionality that is not yet implement
John
From: Sandy Walsh [mailto:sandy.wa...@rackspace.com]
Sent: Thursday, December 30, 2010 3:27 PM
To: John Purrier;
openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>
Subject: RE: [Openstack] [RFC] OpenStack API
Thanks John. That's a good summary of the plan. I still
On Dec 30, 2010, at 1:59 PM, John Purrier wrote:
Jorge, you will need to let folks see the proposed updates to the OpenStack API
for version 1.1.
Absolutely, I will post the spec once we settle on the new set of API
features. The API extension mechanism and the transition to the OpenStack
n
From: Sandy Walsh [mailto:sandy.wa...@rackspace.com]
Sent: Thursday, December 30, 2010 3:27 PM
To: John Purrier; openstack@lists.launchpad.net
Subject: RE: [Openstack] [RFC] OpenStack API
Thanks John. That's a good summary of the plan. I still have a few
questions, if you could
Thanks John. That's a good summary of the plan. I still have a few questions,
if you could indulge me ...
Seems like there are two issues being debated, one customer-facing, one
Nova-developer-facing:
Customer-facing:
Will OS 1.1 remain backward compatible with 1.0? In other words, is 1.1 truly
31 matches
Mail list logo
