Re: [Openstack] Feature Freeze status

2011-03-28 Thread Sandy Walsh
+1 From: Ewan Mellor [ewan.mel...@eu.citrix.com] Blueprints should be regarded in the same way as docstrings. Sure, you can write the code faster without docstrings, and the code will work just as well, but it will take everyone else twice as long

Re: [Openstack] core dev

2011-03-25 Thread Sandy Walsh
+1 for the Sprinkle-laden Trey Bucket. From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of Trey Morris [trey.mor...@rackspace.com] Sent: Thursday, March 24, 2011

Re: [Openstack] Instance IDs and Multiple Zones

2011-03-24 Thread Sandy Walsh
+1 Great discussion and not anything that should be blocking distributed scheduler. -S From: Eric Day [e...@oddments.org] Ok. :) The original statement felt like it was written with negative connotations, and I just wanted to say I think it's all

Re: [Openstack] A single cross-zone database?

2011-03-24 Thread Sandy Walsh
separate caching schemes; and easy to layer on to the existing solution. Certainly a great topic for the design summit, imho. -S From: Andy Smith [andys...@gmail.com] Sent: Wednesday, March 23, 2011 10:23 PM To: Sandy Walsh Cc: openstack@lists.launchpad.net Subject

Re: [Openstack] Instance IDs and Multiple Zones

2011-03-23 Thread Sandy Walsh
Good conversation guys. Certainly something we need to get settled out sooner than later. On naming: No matter how we shake it out (prefixes, mac address, time, etc), we're essentially fabricating our own form of UUID ... trying to pick some unique qualifier(s) to avoid collisions. I think

Re: [Openstack] Instance IDs and Multiple Zones

2011-03-23 Thread Sandy Walsh
Pvo brought up a good use case for naming a little while ago: Migrations. If we use the instance id (assume UNC) to provide hints to the target zone, this means the instance id would need to change should the instance move locations. That's a no-no by everyone's measure. So, now I'm thinking

Re: [Openstack] Instance IDs and Multiple Zones

2011-03-23 Thread Sandy Walsh
(sorry Eric, meant to send to the list) -S From: Eric Day [e...@oddments.org] Do we want this namespace per zone, deployment, resource owner, or some other dimension? Good question. We can prevent collisions at the zone level and within a deployment (single provider / multi-zone). But hybrid

Re: [Openstack] Instance IDs and Multiple Zones

2011-03-23 Thread Sandy Walsh
From: Eric Day [e...@oddments.org] On Thu, Mar 24, 2011 at 12:23:42AM +, Sandy Walsh wrote: Regardless of how we delineate it or which ID scheme we use, we have no way of detecting collisions. Why not? Some schemes such as the ID.DNS name + ssl cert check I mentioned before allow us

Re: [Openstack] OpenStack API - Where do I find ?

2011-03-23 Thread Sandy Walsh
Hi Sheshadri, Openstack compute (nova) supports both the Amazon EC2 API and the Rackspace 1.0 API currently. The RS API spec is available here: http://docs.rackspacecloud.com/servers/api/v1.0/cs-devguide-20110112.pdf There is a python client library available here:

[Openstack] A single cross-zone database?

2011-03-16 Thread Sandy Walsh
Hi y'all, getting any sleep before Feature Freeze? As you know, one of the main design tenants of OpenStack is Share Nothing (where possible). http://wiki.openstack.org/BasicDesignTenets That's the mantra we've been chanting with Zones. But it does cause a problem with a particular Use Case:

Re: [Openstack] A single cross-zone database?

2011-03-16 Thread Sandy Walsh
Yup, that's a fair assessment. That said, even without SDB and caching it's going to be tight for Cactus anyway. There are lots of little issues that are cropping up once I got down to 100'. -S From: Justin Santa Barbara

Re: [Openstack] Queue Service Implementation Thoughts

2011-03-08 Thread Sandy Walsh
I'm sure you've seen this: http://nichol.as/benchmark-of-python-web-servers?source=g -S From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of Eric Day

Re: [Openstack] Crazy Idea for API Formats

2011-03-07 Thread Sandy Walsh
[m...@openstack.org] Subject: Re: [Openstack] Crazy Idea for API Formats On Mar 4, 2011, at 10:55 PM, Sandy Walsh wrote: Interesting ... do I get back an instance object or just a key/value dict? I'm thinking an actual instance object. And we would provide code for that. Like, if someone

Re: [Openstack] Multiple Versions in Openstack API

2011-03-04 Thread Sandy Walsh
I agree that, while it's a pain, supporting old versions of the API is the best way to grow adoption. For many shops, simply supporting OpenStack API is a large engineering effort ... having to revisit it every version update might bust the camels back. Easy to see why Amazon goes back so far.

Re: [Openstack] server affinity

2011-03-02 Thread Sandy Walsh
I think these additional/optional request parameters (aka metadata) should just be part of the context that is created when a command is issued and passed around for all services to use as needed. So I guess that would be a vote for #2 -S From: Jorge

Re: [Openstack] server affinity

2011-03-01 Thread Sandy Walsh
Was just speaking with dabo about this and we agree that metadata is a bad name for this capability. I don't really care about what we call it, but metadata has some preconceived notions/meanings. Perhaps Criteria? Currently we have *some* criteria for creating a new instance on the Openstack

Re: [Openstack] Novatools ...

2011-02-28 Thread Sandy Walsh
Thanks Thierry for summarizing the concerns. I have a new version in https://github.com/rackspace/python-novatools This does the following: 1. Renames the cmdline tool to nova. The package is still python-novatools 2. Ups the version # to 2.1 3. Changes the license to Apache for 2.1+. Prior

Re: [Openstack] Novatools ...

2011-02-24 Thread Sandy Walsh
, 2011 1:05 PM To: Sandy Walsh; Andy Smith; so...@openstack.org; Rick Clark Cc: Paul Voccio; Matt Dietz; Josh Kearney; openstack@lists.launchpad.net Subject: RE: Novatools ... Including ttx and the mailing list. It seems as if the API experience for OpenStack is going to be a hierarchical stack

Re: [Openstack] Novatools ...

2011-02-24 Thread Sandy Walsh
Perfect. Objections? (naming bun-fights discouraged ;) -S From: John Purrier Sent: Thursday, February 24, 2011 1:39 PM To: Sandy Walsh; Andy Smith; so...@openstack.org; Rick Clark Cc: Paul Voccio; Matt Dietz; Josh Kearney; openstack@lists.launchpad.net Subject

Re: [Openstack] Novatools ...

2011-02-24 Thread Sandy Walsh
Thanks Eric, I agree. It would be great to do 'bzr branch lp:nova' and have all the client tools we need. Especially given the fact that the client tools are now required by the system itself. I suspect it will also be needed for integration testing. This also prevents more PPA administration.

Re: [Openstack] Novatools ...

2011-02-24 Thread Sandy Walsh
Jay, I totally see your argument. Are you proposing a more plug-in type mechanism like nova-manage/django-admin (but uses the public API)? Or, perhaps, similar to the Citrix 'xe' umbrella? Is this part of the longer term discussion (as we still need something now)? -S

Re: [Openstack] Burrow (queue service)

2011-02-24 Thread Sandy Walsh
Let me know if there are any questions I didn't answer thoroughly enough. Looks like a fun project Eric. I only got caught up on the ML this weekend and I'm behind again already. Some questions that I jotted down from the previous discussions were: 1. Will broadcast queues be supported? 2.

Re: [Openstack] Novatools ... where to place in /nova/?

2011-02-24 Thread Sandy Walsh
Yup, this looks like the super tool that jay was talking of earlier (odd too, since that's something I'm using accused of being) I kind of like it as well, since it permits swift, nova and glance to have their own client tools, but fit within the larger umbrella (and tab-completion/hints work

Re: [Openstack] Novatools ... where to place in /nova/?

2011-02-24 Thread Sandy Walsh
Hmm, that's a little tricky since oscompute will be contain the cmdline tool and the client tool to the REST API (cmdline is just a shell interface over the client). It would mean splitting things up and the setup.py would get complicated. To Eric's point .../clients/python/*

Re: [Openstack] Novatools ...

2011-02-24 Thread Sandy Walsh
Some great discussion going on here folks but, in an attempt to prevent this turning into a full-on Painting the Bike Shed debate, here are the assumptions I'm proceeding with: 1. Eventually there will be a super tool to aggregate the various services. It will be built/named later by someone.

Re: [Openstack] Novatools ... where to place in /nova/?

2011-02-24 Thread Sandy Walsh
I, mistakingly, changed the subject so I could focus on the install directory. Sorry for creating a rift. Hopefully, I'm going to move it in such a way that we don't need to mess with the python path for nova and a user can still install it if desired. -S

Re: [Openstack] Novatools ...

2011-02-24 Thread Sandy Walsh
Thanks Jay. Yes, to the best of my knowledge nothing should have changed to keep novatools from working with cloudservers/RS API. This was the situation right up to the rebranding. Now, a merge would be much harder. -S *If* Sandy's minimal changes were merged, then python-cloudservers would

Re: [Openstack] Novatools ...

2011-02-24 Thread Sandy Walsh
But will he continue to pull merges on a rapidly changing series of patches up to RC on April 14th and beyond? -S So we have perhaps a decent chance of getting things rolling there? I think it is worth pursuing. --andy Confidentiality Notice: This e-mail message (including any attached or

Re: [Openstack] Review days for nova-core members

2011-02-17 Thread Sandy Walsh
I'll throw my hat in the ring for core if deemed worthy. Soren's point about 1 review day per # core developers was refreshing. I had previously held back from applying because I was afraid all my time would be tied up with reviews. ? From:

[Openstack] Proposal to be a member of Nova Core ...

2011-02-17 Thread Sandy Walsh
I'd like to help out on the review process as per http://wiki.openstack.org/Governance/Approved/CoreDevProcess I like quiet walks in the park and black and white movies. -Sandy Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the

[Openstack] Multi-Cluster/Zone - Devil in the Details ...

2011-02-16 Thread Sandy Walsh
Hi y'all Like they say The devil is in the details. I'm at the stage where the parent zones will talk to the child zones and there are some interesting implementation issues: Problem 1. I'd like to pass the incoming HTTP Request object along to the Scheduler so I don't have to remarshall the

Re: [Openstack] Multi-Cluster/Zone - Devil in the Details ...

2011-02-16 Thread Sandy Walsh
Thanks for feedback Ed. Comments in [] below ... From: Ed Leafe [e...@leafe.com] On Feb 16, 2011, at 10:26 AM, Sandy Walsh wrote: Isn't the instance name usually supplied by the user/originator? [Sorry, yes the instance name is passed

Re: [Openstack] Multi-Cluster/Zone - Devil in the Details ...

2011-02-16 Thread Sandy Walsh
Thanks Dragon! Had another conversation with Jay on this as well. I think the caching with the smart use of instance/customer naming will go a long way to helping the search. More comments below ... -S From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net

Re: [Openstack] Allowing clients to pass capability requests through tags?

2011-02-11 Thread Sandy Walsh
Phew. I was thinking this was going to be an overloaded capability on the zone name. Carry on. Nothing to see here. -S From: Eric Day [e...@oddments.org] Sent: Friday, February 11, 2011 1:36 PM To: Sandy Walsh Cc: Justin Santa Barbara; openstack

Re: [Openstack] Multi Clusters in a Region ...

2011-02-10 Thread Sandy Walsh
. Keep it coming! -Sandy _ ___ From: Eric Day [e...@oddments.org] Sent: Wednesday, February 09, 2011 1:17 PM To: Sandy Walsh Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] Multi Clusters in a Region ... Hi Sandy, Replying via email since it seems

Re: [Openstack] Allowing clients to pass capability requests through tags?

2011-02-10 Thread Sandy Walsh
Agreed. Ed Leafe (dabo) is slated to work on the scheduler plugins that make the decisions for which zone to use. https://blueprints.launchpad.net/nova/+spec/bexar-distributed-scheduler https://blueprints.launchpad.net/nova/+spec/bexar-distributed-schedulerYou might want to review that one as

[Openstack] Do these commands belong in the API or nova-manage?

2011-02-08 Thread Sandy Walsh
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?

Re: [Openstack] Pondering multi-tenant needs in nova.

2011-02-07 Thread Sandy Walsh
+1 From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of Eric Day [e...@oddments.org] Sent: Monday, February 07, 2011 1:35 AM To: Jay Pipes Cc:

Re: [Openstack] Multi Clusters in a Region ...

2011-02-07 Thread Sandy Walsh
] on behalf of Sandy Walsh [sandy.wa...@rackspace.com] Sent: Monday, January 31, 2011 3:26 PM To: openstack@lists.launchpad.net Subject: [Openstack] Multi Clusters in a Region ... Hi y'all, Now that the Network and API discussions have settled down a little I thought I'd kick up the dust again. I'm

Re: [Openstack] Pondering multi-tenant needs in nova.

2011-02-03 Thread Sandy Walsh
Sounds very LDAP. Would it make sense to have a plug-in so we could mimic a pre-existing corp LDAP structure? -S From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf

Re: [Openstack] Pondering multi-tenant needs in nova.

2011-02-03 Thread Sandy Walsh
There's no good reason for Nova to have to model an organization internally; it certainly wouldn't match all the possible org structures available. +1 From: Devin Carlen devin.car...@gmail.commailto:devin.car...@gmail.com Date: Thu, 3 Feb 2011 12:02:38 -0800 To: Monsyne Dragon

[Openstack] Multi Clusters in a Region ...

2011-01-31 Thread Sandy Walsh
Hi y'all, Now that the Network and API discussions have settled down a little I thought I'd kick up the dust again. I'm slated to work on the Multi Cluster in a Region BP for Cactus. This also touches on Zone/Host Capabilities and Distributed Scheduler, so feedback is important.

Re: [Openstack] [RFC] OpenStack API

2011-01-08 Thread Sandy Walsh
, it is currently the Rackspace Cloud API. Version 1.1 of that API (in Cactus) should have an Openstack namespace and extensibility. [...] Developing an Open Stack Cloud System-level CLI might be a good start ... As part of the above spec, Sandy Walsh has a new python-cloudservers library (and accompanying

[Openstack] Free PyCharm license for Openstack Developers ...

2011-01-06 Thread Sandy Walsh
The nice folks at JetBrains were kind enough to grant OpenStack developers a free license to PyCharm. So, if you care to give it a try ... -S IMPORTANT: THIS IS TO CERTIFY THE RIGHT TO USE THE JETBRAINS SOFTWARE PRODUCT, GRANTED BY JETBRAINS S.R.O. UNDER THE TERMS AND CONDITIONS OF THE

<    1   2   3