Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-10 Thread George Reese
gabe.westm...@rackspace.com wrote: The biggest problem with this is that either json or XML ends up feeling second class. -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep: +1.207.956.0217 enStratus: Enterprise Cloud

Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-10 Thread George Reese
On Aug 10, 2012, at 2:52 PM, Jay Pipes jaypi...@gmail.com wrote: On 08/09/2012 11:05 PM, George Reese wrote: On Aug 9, 2012, at 8:14 PM, Doug Davis d...@us.ibm.com mailto:d...@us.ibm.com wrote: Situations like this are always interesting to watch. :-) On the one hand its open-source, so

Re: [Openstack] Removing support for KVM Hypervisor ...

2012-08-10 Thread George Reese
You're just trying to give me a heart attack :) Sent from my iPhone On Aug 10, 2012, at 15:32, Sandy Walsh sandy.wa...@rackspace.com wrote: Sorry George, couldn't resist. :) ___ Mailing list: https://launchpad.net/~openstack Post to :

Re: [Openstack] Setting Expectations

2012-08-10 Thread George Reese
/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep: +1.207.956.0217 enStratus: Enterprise Cloud Management - @enStratus - http://www.enstratus.com

Re: [Openstack] [openstack-dev] [nova] Call for Help -- OpenStack API XML Support

2012-08-09 Thread George Reese
around some people, the more I like my dog. George Reese george.re...@imaginary.com 08/09/2012 07:02 PM Please respond to OpenStack Development Mailing List openstack-...@lists.openstack.org To OpenStack Development Mailing List openstack-...@lists.openstack.org cc openstack

Re: [Openstack] Angry People and OpenStack

2012-08-02 Thread George Reese
deployments. In the mean time, I know people on this list heaping plenty of public praise on OpenStack who are actively pushing people in private towards alternatives. Yeah, that'll work really well. -George -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.com

[Openstack] Suspend/Stop VM

2012-07-30 Thread George Reese
I must be missing something, but I can't find any docs on how to suspend or stop a VM via API. Any pointers, please? :) -George -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep: +1.207.956.0217 enStratus

Re: [Openstack] Suspend/Stop VM

2012-07-30 Thread George Reese
a sudo virsh list --all, it will list all the running instances even if nova cannot see it for some reason. And then you can kill all the ghost instances by sudo virsh shutdown id. Hope this helps. PJ On Mon, Jul 30, 2012 at 10:50 AM, George Reese george.re...@enstratus.com wrote: I

Re: [Openstack] Suspend/Stop VM

2012-07-30 Thread George Reese
...@redhat.com wrote: On Mon, 2012-07-30 at 10:50 -0500, George Reese wrote: I must be missing something, but I can't find any docs on how to suspend or stop a VM via API. Any pointers, please? :) Try 'nova --debug pause $instance' Shows e.g. POST /v2/$tenant/servers/$instance

Re: [Openstack] Suspend/Stop VM

2012-07-30 Thread George Reese
) def suspend(self, server): Suspend the server. self._action('suspend', server, None) def resume(self, server): Resume the server. self._action('resume', server, None) -- George Reese - Chief Technology Officer

Re: [Openstack] Openstack JAVA SDK

2012-07-18 Thread George Reese
___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comSkype: nspollution

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-16 Thread George Reese
of the community believe this tipping point was the Essex release. It is also inevitable that development will slow down by some measures as the cost of regressions rises and what George Reese called technical debt has to be repaid. Going forward, and this may be controversial, I think

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-13 Thread George Reese
of OpenStack interoperability and compatibility, and others are still interested in just paying it lips service. We'll see what wins out come GA of Folsom, won't we? -George On Jul 13, 2012, at 10:47 AM, Stefano Maffulli wrote: On 07/12/2012 03:54 PM, George Reese wrote: This community

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-12 Thread George Reese
-client can use either one. Vish ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-12 Thread George Reese
, 2012, at 9:32 AM, George Reese wrote: This community just doesn't give a rat's ass about compatibility, does it? -George On Jul 11, 2012, at 10:26 AM, Vishvananda Ishaya wrote: Hello Everyone, Now that the PPB has decided to promote Cinder to core for the Folsom release, we need

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-12 Thread George Reese
shoveling. -George On Jul 12, 2012, at 12:22 PM, Jay Pipes wrote: On 07/12/2012 12:32 PM, George Reese wrote: This community just doesn't give a rat's ass about compatibility, does it? a) Please don't be inappropriate on the mailing list b) Vish sent the email below to the mailing list

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-12 Thread George Reese
impact on operations and he broader ecosystem that bases its efforts on assumptions established at the start of a release cycle, rather than on changes introduced late in the cycle. Cheers Chris Sent from my iPad On Jul 12, 2012, at 2:24 PM, George Reese george.re...@enstratus.com

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-12 Thread George Reese
, not *talking* about things. I'm just asking you to contribute code or design help rather than slanderous commentary. Brian Offensive Waldon On Jul 12, 2012, at 11:59 AM, George Reese wrote: You evidently have not had to live with the interoperability nightmare known as OpenStack in the same way I

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-12 Thread George Reese
in any of the community discussions. Moving forward, I wish you would share your expertise in a constructive manner. Keep in mind this list reaches 2200 people. Let's not waste anyone's time. WALDON On Jul 12, 2012, at 12:14 PM, George Reese wrote: So if Im not coding, I should shut up

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-12 Thread George Reese
. That is simply not effective and makes semi-neutral folks (like me) tend to discard your point of view (which I assume is not your objective). -Jon From: George Reese george.re...@enstratus.com Date: Thursday, July 12, 2012 10:14 AM To: Brian Waldon brian.wal...@rackspace.com Cc: Openstack

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-12 Thread George Reese
: George Reese george.re...@enstratus.com Date: Thursday, July 12, 2012 12:47 PM To: Jon Mittelhauser jon.mittelhau...@nebula.com Cc: Brian Waldon brian.wal...@rackspace.com, Openstack (openstack@lists.launchpad.net) (openstack@lists.launchpad.net) openstack@lists.launchpad.net Subject: Re

Re: [Openstack] [nova] [cinder] Nova-volume vs. Cinder in Folsom

2012-07-12 Thread George Reese
. -George -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep: +1.207.956.0217 enStratus: Enterprise Cloud Management - @enStratus - http://www.enstratus.com To schedule a meeting with me: http://tungle.me/GeorgeReese

Re: [Openstack] OpenStack Java API

2012-02-11 Thread George Reese
: 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 -- George Reese

Re: [Openstack] Compute API Versioning

2011-12-20 Thread George Reese
I was getting all worried that we hadn't covered this lately. -George -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeReesep: +1.207.956.0217 enStratus: Enterprise Cloud Management - @enStratus - http://www.enstratus.com

Re: [Openstack] Nova EC2 API Team

2011-11-08 Thread George Reese
chuck ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer

Re: [Openstack] Push vs Polling (from Versioning Thread)

2011-10-28 Thread George Reese
in trying to figure out a way to scale work that is almost entirely pointless work. There's a reason you see the cloud management tools pushing push. We've seen this IaaS polling across a bunch of clouds. It sucks. -George -- George Reese - Chief Technology Officer, enStratus e: george.re

Re: [Openstack] Push vs Polling (from Versioning Thread)

2011-10-28 Thread George Reese
, at 8:11 AM, George Reese wrote: Push notifications don't make your core system any more complex. You push the change to a message queue and rely on another system to do the work. The other system is scalable. It has no need to be stateless and can be run in an on-demand format using agents

Re: [Openstack] Push vs Polling (from Versioning Thread)

2011-10-28 Thread George Reese
There are ways around that without guaranteed message delivery. Sent from my iPhone On Oct 28, 2011, at 11:41, Bryan Taylor btay...@rackspace.com wrote: On 10/28/2011 10:33 AM, George Reese wrote: There's no reason in this scenario to guarantee message delivery. Usage, billing, support all

Re: [Openstack] API Versioning and Extensibility

2011-10-27 Thread George Reese
require them in a URL unless you are pulling it from the URL bar of a browser, which is NOT an API use case and b) doesn't help you deal with the core functionality of the API that is now OVER A YEAR BEHIND where it should be. -George -- George Reese - Chief Technology Officer, enStratus e

Re: [Openstack] API Versioning and Extensibility

2011-10-27 Thread George Reese
that the use case is extraneous or imaginary, in fact, I presented two APIs that use the technique, today in production, at scale. In the netflix case, I'm simply pointing out that they go out of their way to support variants, precisely to support the browser case. -jOrGe W. -- George

Re: [Openstack] API Versioning and Extensibility

2011-10-27 Thread George Reese
tool for interacting with the HTTP protocol and should not be the boundary of what an API should support. On Oct 27, 2011, at 10:59 AM, Bryan Taylor wrote: On 10/27/2011 08:56 AM, George Reese wrote: THE API SHOULD NOT BE SERVING ATOM CONTENT!!! What!? Atom is a fine way to represent

Re: [Openstack] Push vs Polling (from Versioning Thread)

2011-10-27 Thread George Reese
Sent from my iPhone On Oct 27, 2011, at 11:26, Bryan Taylor btay...@rackspace.com wrote: On 10/27/2011 10:36 AM, George Reese wrote: #3 Push scales a hell of a lot better than having tools polling a cloud constantly. It doesn't matter whether it is polling the API, polling a feed

Re: [Openstack] OpenStack API Versioning Conventions

2011-10-12 Thread George Reese
On Oct 12, 2011, at 11:26 AM, Soren Hansen wrote: 2011/10/11 George Reese george.re...@enstratus.com: See EC2 for someone doing it damn well. I've never had to write new code to talk to them unless I want to take advantage of new functionality. Now I'm confused. EC2 includes the API

Re: [Openstack] OpenStack API Versioning Conventions

2011-10-12 Thread George Reese
On Oct 12, 2011, at 11:23 AM, Soren Hansen wrote: 2011/10/11 George Reese george.re...@enstratus.com: It's wildly inappropriate to equate a thing with its representation. I didn't say I was right in doing so :) It's a discussion that gets philosophical rather quickly: Should we consider

Re: [Openstack] OpenStack API Versioning Conventions

2011-10-12 Thread George Reese
The extension has nothing to do with representation in HTTP. It's the content type (in the headers). Sent from my iPhone On Oct 12, 2011, at 17:15, Bryan Taylor btay...@rackspace.com wrote: On 10/11/2011 10:28 AM, George Reese wrote: It's wildly inappropriate to equate a thing with its

Re: [Openstack] OpenStack API Versioning Conventions

2011-10-11 Thread George Reese
-- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comt: @GeorgeReesep: +1.207.956.0217f: +1.612.338.5041 enStratus: Governance for Public, Private, and Hybrid Clouds - @enStratus - http://www.enstratus.com To schedule a meeting with me: http://tungle.me

Re: [Openstack] OpenStack API Versioning Conventions

2011-10-11 Thread George Reese
will respond with a 302 and a v2 client with a 404. A v1 client can then query /instances/1234 and get the version 1 xml or json. A v2 client querying /instances/1234 gets version 2 xml or json. -George On Oct 11, 2011, at 3:11 PM, Soren Hansen wrote: 2011/10/11 George Reese george.re

Re: [Openstack] OpenStack API Versioning Conventions

2011-10-11 Thread George Reese
://www.ubuntu.com/ OpenStack Developer | http://www.openstack.org/ -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comt: @GeorgeReesep: +1.207.956.0217f: +1.612.338.5041 enStratus: Governance for Public, Private, and Hybrid Clouds - @enStratus - http

Re: [Openstack] OpenStack API Versioning Conventions

2011-10-11 Thread George Reese
. We also couldn't guarantee that the entity returned from the latest version (like v5) looks anything like that defined in the requested version (like v1). On Oct 11, 2011, at 10:46 AM, George Reese wrote: In the example you use, the proper HTTP behavior is for the API should allow

Re: [Openstack] OpenStack API Versioning Conventions

2011-10-11 Thread George Reese
HTTP methods are well defined and the system should behave in accordance with those definitions. Otherwise, even saying the word REST is a joke. On Oct 11, 2011, at 9:10 PM, Caitlin Bestler wrote: George Reese wrote: No, not at all. The object is /servers/1234 regardless

Re: [Openstack] Standardizing External APIs

2011-09-07 Thread George Reese
to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comt: @GeorgeReesep: +1.207.956.0217f: +1.612.338.5041 enStratus: Governance

Re: [Openstack] Standardizing External APIs

2011-09-07 Thread George Reese
See: http://broadcast.oreilly.com/2011/04/proposal-for-cloud-state-notifications.html and http://broadcast.oreilly.com/2010/02/towards-event-driven-cloud-apis.html On Sep 7, 2011, at 7:52 AM, Sandy Walsh wrote: +1 From: George Reese [george.re

Re: [Openstack] API Spec

2011-08-27 Thread George Reese
sounding excuses(?) ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer

Re: [Openstack] API Spec

2011-08-27 Thread George Reese
CERN ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer

Re: [Openstack] API Spec

2011-08-27 Thread George Reese
and integration, not whether feature X is in the latest API. Tim. - Reply message - From: George Reese george.re...@enstratus.com To: Tim Bell tim.b...@cern.ch Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Subject: [Openstack] API Spec Date: Sat, Aug 27, 2011 20:47

Re: [Openstack] API Spec

2011-08-26 Thread George Reese
: https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comt: @GeorgeReesep: +1.207.956.0217f: +1.612.338.5041 enStratus: Governance for Public, Private, and Hybrid Clouds

Re: [Openstack] Cross-zone instance identifiers in EC2 API - Is it worth the effort?

2011-07-11 Thread George Reese
/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re

Re: [Openstack] Cross-zone instance identifiers in EC2 API - Is it worth the effort?

2011-07-09 Thread George Reese
/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comt: @GeorgeReesep: +1.207.956.0217f: +1.612.338.5041 enStratus: Governance for Public, Private, and Hybrid Clouds - @enStratus - http

Re: [Openstack] Cross-zone instance identifiers in EC2 API - Is it worth the effort?

2011-07-08 Thread George Reese
://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comt: @GeorgeReesep: +1.207.956.0217f

Re: [Openstack] Cross-zone instance identifiers in EC2 API - Is it worth the effort?

2011-07-08 Thread George Reese
@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comt: @GeorgeReesep: +1.207.956.0217f: +1.612.338.5041 enStratus: Governance for Public

Re: [Openstack] Cross-zone instance identifiers in EC2 API - Is it worth the effort?

2011-07-08 Thread George Reese
This ship may have sailed, but given what I have seen across a wide variety of cloud APIs and what I are here, I strongly question the value of supporting an EC2 API. I think you overestimate the value of supporting existing tools. Sent from my iPhone On Jul 8, 2011, at 19:32, Lorin

Re: [Openstack] XML and JSON for API's

2011-06-03 Thread George Reese
://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comt: @GeorgeReesep: +1.207.956.0217f: +1.612.338.5041 enStratus: Governance for Public, Private, and Hybrid Clouds - @enStratus - http://www.enstratus.com To schedule a meeting with me

Re: [Openstack] Feedback on HTTP APIs

2011-06-02 Thread George Reese
: https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comt: @GeorgeReesep: +1.207.956.0217f: +1.612.338.5041 enStratus: Governance for Public, Private, and Hybrid Clouds

Re: [Openstack] Feedback on HTTP APIs

2011-06-02 Thread George Reese
I understand they are large integer fields. But for consideration of portability, they are strings. Sent from my iPhone On Jun 2, 2011, at 21:14, Jorge Williams jorge.willi...@rackspace.com wrote: On Jun 2, 2011, at 12:18 PM, George Reese wrote: I hate UUIDs with a passion

Re: [Openstack] XML and JSON for API's

2011-06-02 Thread George Reese
+1 Sent from my iPhone On Jun 2, 2011, at 22:20, Jorge Williams jorge.willi...@rackspace.com wrote: It's not just about the service itself validating it, its as Joseph said, making sure that the data structures themselves are documented in detail to the client. To my knowledge there is

Re: [Openstack] Notifications proposal

2011-05-09 Thread George Reese
Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comt: @GeorgeReesep: +1.207.956.0217f: +1.612.338.5041 enStratus: Governance for Public, Private, and Hybrid

Re: [Openstack] OS API server password generation

2011-03-03 Thread George Reese
___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- George Reese - Chief Technology Officer, enStratus e: george.re...@enstratus.comt

Re: [Openstack] OS API server password generation

2011-03-03 Thread George Reese
: On Mar 3, 2011, at 8:40 AM, George Reese wrote: Any mechanism that requires an agent or requires any ability of the hypervisor or cloud platform to inject a password creates trust issues. In particular, the hypervisor and platform should avoid operations that reach into the guest. The guest

Re: [Openstack] OS API server password generation

2011-03-03 Thread George Reese
=citrix@lists.launchpad.net [mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net] On Behalf Of George Reese Sent: 03 March 2011 15:36 To: Ed Leafe Cc: Openstack; Mark Washenberger Subject: Re: [Openstack] OS API server password generation I don't agree with this approach

Re: [Openstack] OS API server password generation

2011-03-03 Thread George Reese
opt for the more intrusive option? -George On Mar 3, 2011, at 1:22 PM, Rick Clark wrote: On 03/03/2011 12:40 PM, George Reese wrote: So why don't we give the provider root access to our machines? to be fair, a provider owns the hypervisor and storage, I would always assume providers have