.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
>
You're just trying to give me a heart attack :)
Sent from my iPhone
On Aug 10, 2012, at 15:32, Sandy Walsh wrote:
>
> Sorry George, couldn't resist. :)
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.ne
On Aug 10, 2012, at 2:52 PM, Jay Pipes wrote:
> On 08/09/2012 11:05 PM, George Reese wrote:
>> On Aug 9, 2012, at 8:14 PM, Doug Davis > <mailto:d...@us.ibm.com>> wrote:
>>> Situations like this are always interesting to watch. :-)
>>>
>>> On th
, 2012, at 8:14 AM, Gabe Westmaas 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:
__
> STSM | Standards Architect | IBM Software Group
> (919) 254-6905 | IBM 444-6905 | d...@us.ibm.com
> The more I'm around some people, the more I like my dog.
>
>
> George Reese
> 08/09/2012 07:02 PM
> Please respond
rld 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...@en
(self, server):
> """
> Unlock the server.
> """
> self._action('unlock', server, None)
>
> def suspend(self, server):
> """
> Suspend the server.
> """
>
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'
>
> Show
es. Do 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 ".
>
> Hope this helps.
>
> PJ
>
>
> On Mo
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
enSt
go about
> installing them?
>
> Thanks much,
> Jyothsna
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListH
ators to change them. Obviously some members 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
y the lack 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 w
> Please refrain from adding more of your references to excrements and
> help the community make a decision.
>
> /stef
>
>
> On 07/12/2012 12:14 PM, George Reese wrote:
>> So if Im not coding, I should shut up?
>>
>> I think you answered your own question.
>&g
perability of OpenStack deployments. I can only
assume that's because you can't actually defend it, yet you nevertheless have
your head stuck in the sand.
-George
--
George Reese - Chief Technology Officer, enStratus
e: george.re...@enstratus.comSkype: nspollutiont: @GeorgeR
ed (which is what
> Vish's email was opening discussion about)?
>
> Or…??
>
> -Jon
>
> From: George Reese
> Date: Thursday, July 12, 2012 12:47 PM
> To: Jon Mittelhauser
> Cc: Brian Waldon , "Openstack
> (openstack@lists.launchpad.net) (opensta
n it to us.
>
> You are complaining without offering a counter proposal. 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
&
u seem to have
> strong opinions on how things should be done, but I don't see your voice 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 was
. 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 w
ate about changes that may
> have 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
>
the community just keeps 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
t; Have a great day!
> Brian Waldon
>
> On Jul 12, 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:
>
> _______
> 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 Techno
>>
>>
>> --
>>
>> Luis Alberto Gervaso Martín
>> Java EE Architect & Instructor
>> C/ Cuenca 4A, 2ºB
>> Getafe (Madrid)
>> SPAIN
>> mobile: (+34) 627983344
>> l...@woorea.es <mailto:l...@woorea.es>
>>
>>
>&g
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.enstratu
g.
>
> If you have any questions please let me know.
>
> Regards
> chuck
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
There are ways around that without guaranteed message delivery.
Sent from my iPhone
On Oct 28, 2011, at 11:41, Bryan Taylor wrote:
> On 10/28/2011 10:33 AM, George Reese wrote:
>
>> There's no reason in this scenario to guarantee message delivery.
>
> Usage, billi
You are describing an all-purpose system, not one that supports the narrow
needs of IaaS state notifications.
There's no reason in this scenario to guarantee message delivery.
Sent from my iPhone
On Oct 28, 2011, at 10:09, Jorge Williams
wrote:
On Oct 28, 2011, at 8:11 AM, George
le
the polling from their end.
Both sides are thus engaged 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 suc
Sent from my iPhone
On Oct 27, 2011, at 11:26, Bryan Taylor 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
>&g
mited 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
flix 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 Reese - Chief Technology Officer, enStratus
e: george.re...@enstratus.comt: @GeorgeReesep: +1.207.956.
grasp on how cloud APIs get consumed, what people have done right, what people
have done wrong, and where we need innovation.
We need innovation in pushing data to API consumers.
We don't need people re-inventing API design best practices to suit extraneous
use cases.
Version and content desired be
gt;
> That seems silly to me, we're missing an important feature, the ability to
> click.
>
> -jOrGe W.
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
&
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 wrote:
> On 10/11/2011 10:28 AM, George Reese wrote:
>> It's wildly inappropriate to equate a thing with
gt;> More help : https://help.launchpad.net/ListHelp
>> This email may include confidential information. If you received it in
>> error, please delete it.
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@
On Oct 12, 2011, at 11:23 AM, Soren Hansen wrote:
> 2011/10/11 George Reese :
>> 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
On Oct 12, 2011, at 11:26 AM, Soren Hansen wrote:
> 2011/10/11 George Reese :
>> 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
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/1
a painful thing to have to do. 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 yo
/
> Ubuntu Developer| http://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, an
lient 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 :
>&
a single major version, as I do not want to define a spec that
> resides above all major versions of our api.
>
> Waldon
>
>
> On Oct 11, 2011, at 9:14 AM, George Reese wrote:
>
>> Versioning should not be included in the URI. It belongs in the headers. A
Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>> This email may include confidential information. If you received it in
>>
to get this right, so I'm
> looking forward to everybody's feedback!
>
> Thanks!
> Brian Waldon
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://l
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:
gt; 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: @GeorgeReese
t my deployment testing with v1.1. The limiting factor is not
>> v1.1 vs v1.x for most sites. It is packaging, user exits and integration,
>> not whether feature X is in the latest API.
>>
>> Tim.
>>
>> - Reply message -
>> From: "George R
get Diablo out and deployable first.
>
> Tim Bell
> CERN
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More hel
ectural decision that people are living
> with - so, why not admit that and make it a priority to change?
>
> --
> Kind regards,
> Michael
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad
gaining traction around the
> OpenStack API.
>
>
>
> Devin
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
eem very cool.
>
>
> --
> Soren Hansen| http://linux2go.dk/
> Ubuntu Developer| http://www.ubuntu.com/
> OpenStack Developer | http://www.openstack.org/
>
> ___
> Mailing list: https://launchpad.net/~opensta
l may include confidential information. If you received it in error,
> please delete it.
>
>
> _______
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.
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 Hochstein
; client tools to a different API?
>
> --
> Soren Hansen| http://linux2go.dk/
> Ubuntu Developer| http://www.ubuntu.com/
> OpenStack Developer | http://www.openstack.org/
>
> ___
> Mailing list: https://launchpad.net/~openst
he reasons for choosing UUID's to begin with are moot.
>
> --
> Soren Hansen| http://linux2go.dk/
> Ubuntu Developer| http://www.ubuntu.com/
> OpenStack Developer | http://www.openstack.org/
>
> _______
> Mailing list: https://launchpad.net/~openstack
>
t;> -jay
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launch
+1
Sent from my iPhone
On Jun 2, 2011, at 22:20, Jorge Williams 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 no accepted schema language
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 wrote:
>
> On Jun 2, 2011, at 12:18 PM, George Reese wrote:
>
>> I hate UUIDs with a passion.
>>
>
stHelp
>
>
>
> 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 confident
ncerns are very much welcomed!
>> Matt Dietz
>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More h
ture for making PSHB work
> belongs in Nova. We can then follow all of the other rules of PSHB(feed
> discovery and subscriptions, callbacks etc.)
>
> Does this make sense?
>
> Matt
>
> From: George Reese
> Date: Mon, 9 May 2011 23:17:29 -0500
> To: Jorge Williams
the concept
>>> of categories. I realize you kinda get that with the event type
>>> "compute.create_instance" but there are always going to be messages that
>>> may belong to multiple categories. Also, ISO timestamps with a T :
>>> "2011-05-0
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 al
gt;
>> -Original Message-
>> From: openstack-bounces+ewan.mellor=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
>>
eafe wrote:
> 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 operat
that to the VM, and disables SSH, so that your
> instances are created with the security scheme that you want.
>
>
>
> -- Ed Leafe
>
>
>
>
> ___
> Mailing list: https://launchpad.net/~openstack
> Post to : ope
gt; Unsubscribe : https://launchpad.net/~openstack
>>> More help : https://help.launchpad.net/ListHelp
>>>
>>
>> ___
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@lists.launchpad.net
&
68 matches
Mail list logo
