[Openstack] Rabbitmq always throw exception

I can log in the instance,and its status is running but the rabbitmq.log always throw exception some of the log: =INFO REPORT 27-Oct-2011::18:02:55 === accepted TCP connection on 0.0.0.0:5672 from 192.168.1.10:49119 =INFO REPORT 27-Oct-2011::18:02:55 === starting TCP connection <0.4209.0>

[Openstack] live_migration Permission denied

control node: 011-10-27 17:57:41,819 CRITICAL nova [-] UnboundLocalError local variable 'filename' referenced before assignment [u'Traceback (most recent call last):\n', u' File "/usr/lib/pymodules/python2.6/nova/rpc.py", line 188, in _receive\nrval = node_func(context=ctxt, **node_args)\n'

Re: [Openstack] +1, All services should have WADLs

On 26/10/2011, at 11:17 PM, Sandy Walsh wrote: > As discussed at the summit, I agree there should be some form of IDL (WADL > being the likely candidate for REST), I think manually crafting/maintaining a > WADL (or XML in general) is a fools errand. This stuff is made for machine > consumption

Re: [Openstack] API Versioning and Extensibility

Response inline: On Oct 27, 2011, at 12:50 AM, Bryan Taylor wrote: > On 10/26/2011 04:45 PM, Jorge Williams wrote: >> >> On Oct 26, 2011, at 1:19 PM, Bryan Taylor wrote: >> >>> So no pdfs or excel spreadsheets without conneg. >> >> But PDFs and excel spreadsheets are precisely why you want var

Re: [Openstack] API Versioning and Extensibility

On 27/10/2011, at 3:19 PM, Mark Nottingham wrote: >> I floated the idea a while back that we get rid of variants altogether and >> instead use an HTML representation to offer the user a choice of how to view >> the information that includes elements with JSON and XML formatted >> text. It cou

Re: [Openstack] +1, All services should have WADLs

I think that would be ideal. The key to API adoption will come not only from ease-of-use but from availability of language bindings. Manually creating and maintaining the Python binding is well and good, but having to create and maintain bindings for Java, C#, C++, C, Ruby, PHP, etc is going to

Re: [Openstack] +1, All services should have WADLs

On 28/10/2011, at 12:31 AM, Sandy Walsh wrote: > I think that would be ideal. > > The key to API adoption will come not only from ease-of-use but from > availability of language bindings. Manually creating and maintaining the > Python binding is well and good, but having to create and maintain

Re: [Openstack] API Versioning and Extensibility

On Oct 27, 2011, at 8:11 AM, Jorge Williams wrote: > Response inline: > > On Oct 27, 2011, at 12:50 AM, Bryan Taylor wrote: > >> On 10/26/2011 04:45 PM, Jorge Williams wrote: >>> >>> On Oct 26, 2011, at 1:19 PM, Bryan Taylor wrote: >>> So no pdfs or excel spreadsheets without conneg. >>>

Re: [Openstack] +1, All services should have WADLs

Sounds awesome! I've done an application like this in the past where an entire web UI was data driven using a custom IDL. It had to have presentation hints associated with it (acceptable values, display widget, etc). Not something WADL supports inherently I'm sure. But, I know from experience t

Re: [Openstack] API Versioning and Extensibility

On Oct 27, 2011, at 8:56 AM, George Reese wrote: On Oct 27, 2011, at 8:11 AM, Jorge Williams wrote: Response inline: On Oct 27, 2011, at 12:50 AM, Bryan Taylor wrote: On 10/26/2011 04:45 PM, Jorge Williams wrote: On Oct 26, 2011, at 1:19 PM, Bryan Taylor wrote: So no pdfs or excel spreadshe

[Openstack] nova-compute often stop since of libvirt-bin

I have found nova-compute often stopped that no update info in log and service status is XXX. Then I restart nova-compute, but it is still stop in "DEBUG nova.virt.libvirt_conn [-] Connecting to libvirt: qemu:///system from (pid=31811) _get_connection /data/nova/nova/virt/libvirt/connection.py:2

Re: [Openstack] API Versioning and Extensibility

+11 On Thu, Oct 27, 2011 at 8:56 AM, George Reese wrote: > > Version and content desired belong in the headers for request and response. > The imaginary crap you are dealing with a) don't require them in a URL > unless you are pulling it from the URL bar of a browser, which is NOT an API > use ca

Re: [Openstack] API Versioning and Extensibility

On Oct 27, 2011, at 8:56 AM, George Reese wrote: > There's a nasty habit within the OpenStack community of trying to boil the > ocean. And here we are navel gazing over feeds and crap when the API can't > yet support the most basic of functionality. +1 -- Ed Leafe __

Re: [Openstack] +1, All services should have WADLs

It would be great if we could do some kind of transform of the IDL to generate (some of) the human-consumable REST API documentation that lives at docs.openstack.org. That would simplify the task of keeping those docs up to date. Lorin -- Lorin Hochstein, Computer Scientist USC Information Scie

[Openstack] starting a service with reporting updates to the db

I noticed that in the Nova Service start method the now=False seem to wait and update heartbeat of the services after the first interval. I was curious is there a reason for this? It looks like this would not matter too much but the fact that the option is available to update now i would think this

Re: [Openstack] API Versioning and Extensibility

On 10/26/2011 11:19 PM, Mark Nottingham wrote: To be truly RESTful at the level of the Fielding article (which I actually think is the best description of HATEOAS there is) you shouldn't have these variants at all. I worry about us trying to put lipstick on the pig -- all these variants are a cr

Re: [Openstack] API Versioning and Extensibility

The complete lack of evolution of the OSAPI combined with the irrational resistance to the EC2 API has struck a nerve with me. #1 Feature coverage in the OSAPI is atrocious. And I don't get the feeling there's anyone seriously doing anything about it. Of course, you can always say, "George, it'

Re: [Openstack] nova-compute often stop since of libvirt-bin

I haven't seen this happen. Sounds like it may be a libvirt bug. On Oct 27, 2011, at 7:48 AM, mao weijie wrote: > I have found nova-compute often stopped that no update info in log and > service status is XXX. Then I restart nova-compute, but it is still stop in > "DEBUG nova.virt.libvirt_conn

Re: [Openstack] +1, All services should have WADLs

Yeah, that's what I've been poking at and the original start of this rather lengthy thread. Unfortunately, WADL, while it appears complete, is rather obnoxious for pulling out data. Or more accurately, I haven't fully understood the WADL specification in order to write a WADL parser to allow me

Re: [Openstack] API Versioning and Extensibility

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 a collection. Especially one that is append only. There's a nasty habit within the OpenStack community of trying to boil the ocean. And here we are navel gazing

Re: [Openstack] API Versioning and Extensibility

You know what it has to do with API versioning? It has to do with people proposing bad versioning ideas to support esoteric stuff WHEN THE BASIC STUFF AIN'T THERE YET. curl is the appropriate mechanism for manually interacting with an API for development purpose. A browser is a very limited to

Re: [Openstack] Keystone "Why does it? What does?" questions

On Oct 27, 2011, at 9:19 AM, Vishvananda Ishaya wrote: > On Oct 25, 2011, at 12:05 PM, Joseph Heck wrote: >> Q: What's the keystone-manage command for "credential add" do? There's also >> no corresponding delete or disable - is this password update for the >> passwords that are set on "keystone-m

Re: [Openstack] Keystone "Why does it? What does?" questions

On Oct 25, 2011, at 12:05 PM, Joseph Heck wrote: > > Q: What's the keystone-manage command for "credential add" do? There's also > no corresponding delete or disable - is this password update for the > passwords that are set on "keystone-manage user add"? If not, how are those > passwords upd

[Openstack] Push vs Polling (from Versioning Thread)

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, or polling a message queue. Polling is one of the most unscalable things you can do in any distributed

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

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 >> feed, or polling a message qu

Re: [Openstack] Keystone "Why does it? What does?" questions

See the current trunk of devstack which creates the creds and has an 'openrc' file that is sourceable and allows euca2ools to work again. There is also a bit of code in nova-manage to export users projects and keys to keystone which uses it. We don't really do anything with them in the nova code

Re: [Openstack] API Versioning and Extensibility

On 10/27/2011 11:04 AM, George Reese wrote: You know what it has to do with API versioning? It has to do with people proposing bad versioning ideas to support esoteric stuff WHEN THE BASIC STUFF AIN'T THERE YET. Dude. Calm down. The fact that somebody proposed something you don't agree with do

Re: [Openstack] Keystone "Why does it? What does?" questions

Perfect, thanks! -joe On Oct 27, 2011, at 9:38 AM, Vishvananda Ishaya wrote: > See the current trunk of devstack which creates the creds and has an 'openrc' > file that is sourceable and allows euca2ools to work again. There is also a > bit of code in nova-manage to export users projects and ke

Re: [Openstack] nova-compute often stop since of libvirt-bin

What version of libvirt bin/d/python are you running? on debian/ubuntu do: dpkg -l | grep libvirt On Thu, Oct 27, 2011 at 8:49 AM, Vishvananda Ishaya wrote: > I haven't seen this happen. Sounds like it may be a libvirt bug. > On Oct 27, 2011, at 7:48 AM, mao weijie wrote: > > I have found n

Re: [Openstack] Keystone "Why does it? What does?" questions

Hi Joe - The place I've found this credential add is in the keystone data script in devstack. See: https://github.com/cloudbuilders/devstack/blob/master/files/keystone_data.sh lines 42 and 43. Anne *Anne Gentle* a...@openstack.org my blog | my book

Re: [Openstack] +1, All services should have WADLs

As I stated in previous emails, we are pulling data from the WADL to grab human-consumable REST API docs that live at docs.openstack.org today. We can certainly expand that capability to create a unified API documentation set rather than individual guides. A lot of

Re: [Openstack] describing APIs for OpenStack consumers

Hi folks I tried to generate WADL from nova code. I could get all resource URI and method from Routes object. However, I could not get input parameters from code. (The api method accesses body argument directly. This is also bad for input validation QA effort.) But If we use some annotations, it

Re: [Openstack] +1, All services should have WADLs

Jorge - It's way back the beginning of this thread - A consolidated single website with API docs as HTML pages that is easy for developers to consume. I'm looking forward to seeing the WADL parser, already on that thread with David Cramer directly. I can wait until he's got it in github, which

Re: [Openstack] describing APIs for OpenStack consumers

On Thu, 2011-10-27 at 10:50 -0700, Nati Ueno wrote: > I tried to generate WADL from nova code. > I could get all resource URI and method from Routes object. > However, I could not get input parameters from code. > (The api method accesses body argument directly. This is also bad for > input validat

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

On Oct 27, 2011, at 11:38 AM, George Reese wrote: > 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

Re: [Openstack] +1, All services should have WADLs

Ah yes, API reference pages that span all the projects. That's totally doable, I know we had plans for doing such a thing, but not sure where those plans are. We were planing on using WADL for that. Maybe we should get together with some of the doc folks Anne, David to come up with a strateg

Re: [Openstack] describing APIs for OpenStack consumers

We may need to change the way the implementations are written to require explicit keyword parameters. No more sneaking into the . This may also mean that something more robust than the routes library may be needed? Sadly, annotations of some form are probably going to be needed since we can't i

[Openstack] OpenStack Dashboard Cactus tag

Hello all, When we transitioned from Launchpad to Github, we didn't carry over the tag for Cactus. I've had a few people express interest lately in continuing to use it, so we have retagged for Cactus. You can grab it here if you need: > https://github.com/4P/horizon/zipball/2011.2 Devin

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

+1 Dragon From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of Monsyne Dragon [mdra...@rackspace.com] Sent: Thursday, October 27, 2011 4:14 PM To: George Rees

Re: [Openstack] describing APIs for OpenStack consumers

Generating WADL (or anything else) from code is fine, as long as we have the processes / tools (e.g., CI) in place to assure that a trivial code change doesn't make a backwards-incompatible change in what we expose to clients. Do we? (really, we should have these in place regardless of how thin

Re: [Openstack] +1, All services should have WADLs

FWIW, a long time ago* I wrote an XSLT to generate HTML docs from WADL -- see: https://github.com/mnot/wadl_stylesheets I haven't maintained them in some time; however, if there's enough interest, I can dust them off / update / etc. Cheers, * They went into github in 2009, but were written i

Re: [Openstack] API Versioning and Extensibility

On 28/10/2011, at 2:39 AM, Bryan Taylor wrote: > On 10/26/2011 11:19 PM, Mark Nottingham wrote: >>> To be truly RESTful at the level of the Fielding article (which I >>> actually think is the best description of HATEOAS there is) you >>> shouldn't have these variants at all. I worry about us try

[Openstack] Request for review - Keystone RBAC calls

Hi Stackers, Keystone has an RBAC prototype on its roadmap for e-1 and we'd like to get your feedback on the blueprint for it (https://blueprints.launchpad.net/keystone/+spec/rbac-keystone). OS-RBAC, a keystone extension, will allow Nova, Swift, Glance, and Dashboard to manage c

Re: [Openstack] +1, All services should have WADLs

Example output at: http://mnot.github.com/wadl_stylesheets/ Cheers, On 28/10/2011, at 9:55 AM, Mark Nottingham wrote: > FWIW, a long time ago* I wrote an XSLT to generate HTML docs from WADL -- see: > https://github.com/mnot/wadl_stylesheets > > I haven't maintained them in some time; howe

Re: [Openstack] API Versioning and Extensibility

On 28/10/2011, at 2:36 AM, George Reese wrote: > The complete lack of evolution of the OSAPI combined with the irrational > resistance to the EC2 API has struck a nerve with me. > > #1 Feature coverage in the OSAPI is atrocious. And I don't get the feeling > there's anyone seriously doing anyt

Re: [Openstack] +1, All services should have WADLs

Hi Mark This is cool! Could you apply this for OpenStack WADL? Could you generate parameter list from XSD with XSLT? 2011/10/27 Mark Nottingham : > Example output at: >  http://mnot.github.com/wadl_stylesheets/ > > Cheers, > > > On 28/10/2011, at 9:55 AM, Mark Nottingham wrote: > >> FWIW, a long

Re: [Openstack] +1, All services should have WADLs

I ran it against Nova's; needs some tweaking, but should be doable. If you think you'll use it, I'll page it back in (like I said, it's been a long time) and fix it up. Of course, at some point it's going to be easier to re-implement (e.g., in Python), but if it looks like it's 80-90% of the way

Re: [Openstack] nova-compute often stop since of libvirt-bin

hi,it's my libvirt-bin version: dpkg -l | grep libvirt ii libvirt-bin 0.9.2-4ubuntu15 the programs for the libvirt library ii libvirt0 0.9.2-4ubuntu15 library for interfacing with different virtualization systems ii python-libvirt 0.9.2-4ubuntu15 libvirt Python bindings 2011/10/28 Jesse Andrews

[Openstack] virtio for VM NICs

Is there a reason that libvirt_use_virtio_for_bridges is not set to True by default? Without virtio the network performance in kvm is ridiculously slow.. Thanks, Yun ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launch

Re: [Openstack] Keystone versioning and tarballs

I think I'm close to figuring this out. You can take a look at the devstack scripts. In particular, https://github.com/cloudbuilders/devstack/blob/master/files/keystone_data.sh Then you can source openrc to get the EC2_* environment variables. However, it only works for euca-describe-instances, e

[Openstack] Compute API schema docs now available

All, You can now browse through the Compute API 1.1 schemas here: http://docs.openstack.org/api/openstack-compute/1.1/xsd/ If other APIs would like to provide schemas, we can use the xslt transforms to create these pages for browsing for other APIs. The source files are located in http://github.

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

Just to be clear we are talking about APIs fit for customer consumption here, not internal integrations where both ends are under our control. On 10/27/2011 11:38 AM, George Reese wrote: I disagree. The web was designed specifically to solve the distributed scaling problem and it's based on HT

[Openstack] deploying java in openstack

hi all anyone see GAE (Google App Engine), Azure, AMazon, CloudFoundery , Heroku, have faeture to deploy Java apps /container in their cloud i am seeking java solution that can deploy in OpenSTack this blog may be can give a glue http://blog.heroku.com/archives/2011/08/25/java/ -- Frans Thamu

[Openstack] OpenSTack Minimum Spec

hi all i am writing specification for polytechnics related for lab, the regulator said, 1 PC must be for 1 student and several polytechnics have limited budget can share all? i have Pentium 4, run in single node :) but i think multicore processor are better, so for play around i recommend i7,

Re: [Openstack] +1, All services should have WADLs

I am concerned about some of the implications that are being discussed. 1) A WADL is part of documentation of an API. Nobody is going to object to more documentation. 2) Being an open-source project, if somebody wants to commit to creating and maintaining a WADL for a particular part of Opensta

Re: [Openstack] virtio for VM NICs

This probably goes back to when there were problems with certain kernels that would lock up when attaching volumes with virtio enabled. There still may be issues with Windows images that don't have the right drivers installed. -todd[1] On Thu, Oct 27, 2011 at 9:33 PM, Yun Mao wrote: > Is there