[Openstack] ImportError: CRITICAL nova [-] No module named urlmap

Hi All, I am running openstack nova services on single node from diablo3 series. I am not able to lauch nova-api service, I am getting this error. "ImportError: CRITICAL nova [-] No module named urlmap" I am able to run other services such as glance_api, glance-reg, object store, compute, network,

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

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 and should be machine generated. Whatever solution we ad

[Openstack] What I have to install on the image to mount a volume?

Hi, is there something I have to install on my images to mount a volume? I have a volume and I can mount it on ubuntu oneiric UEC image (we can download from Internet, the gziped file). All work fine! But, I have some images with ubuntu server that I've created. When I try to attach a volume to

Re: [Openstack] describing APIs for OpenStack consumers

All, Thanks to the generosity of Oxygen in supporting open source projects, you can edit XML within the Oxygen Author or Editor by downloading a copy of the software from http://www.oxygenxml.com/. Send an email to support @ oxygenxml dot com requesting the license extension beyond the 30-day trial

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

On Wed, Oct 26, 2011 at 1:06 AM, Mellquist, Peter wrote: > The topic of when an API should be defined is also important. Do we define an > API / WADL 1) up front before the service is implemented, 2) in parallel with > the impl, 3) or after the impl? I am an advocate of #1 or perhaps #2 but not

Re: [Openstack] ImportError: CRITICAL nova [-] No module named urlmap

Hi Praveen! Please report bugs and/or questions like this on Launchpad's Bugs or Answers areas for Nova: https://bugs.launchpad.net/nova https://answers.launchpad.net/nova Looks to me like you may not have Paste installed. Try installing the python-paste package. cheers, -jay On Wed, Oct 26, 2

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

I don't mind generating a WADL so long as we have a good expressive tool for doing so. I haven't found one yet. There was a project a while back for doing so called "Rest Described and Compile" that seemed to be heading in the right direction, but it hasn't been worked on in a while. http://to

Re: [Openstack] describing APIs for OpenStack consumers

On Tue, Oct 25, 2011 at 6:34 PM, Caitlin Bestler wrote: > WADL sounds like a wonderful validation tool. > > But shouldn’t our primary goal be finding a consistent way to describe the > APIs for *application developers*. > > Syntax tools, whether ancient notations like BNF or the latest XML > conco

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

++Totally agree with that approach. Looking forward to looking over the Images 2.0 API :-) -jOrGe W. On Oct 26, 2011, at 10:23 AM, Jay Pipes wrote: > On Wed, Oct 26, 2011 at 1:06 AM, Mellquist, Peter > wrote: >> The topic of when an API should be defined is also important. Do we define >> an

Re: [Openstack] describing APIs for OpenStack consumers

On Tue, 2011-10-25 at 15:30 -0700, Joseph Heck wrote: > It sounds like even though most of us hate WADL, it's what we're > expending effort after to make a consolidated API set. So unless Nati > and Ravi want to switch to using Swagger (or something else), WADL is > the direction we're heading. I t

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

That's still human generated, just with nicer tools. I'm thinking WADL from implementation code. -S From: Jorge Williams Sent: Wednesday, October 26, 2011 12:29 PM To: Sandy Walsh Cc: Mellquist, Peter; Joseph Heck; openstack@lists.launchpad.net Subject:

Re: [Openstack] describing APIs for OpenStack consumers

On Wed, Oct 26, 2011 at 11:48 AM, Kevin L. Mitchell wrote: > On Tue, 2011-10-25 at 15:30 -0700, Joseph Heck wrote: >> It sounds like even though most of us hate WADL, it's what we're >> expending effort after to make a consolidated API set. So unless Nati >> and Ravi want to switch to using Swagge

Re: [Openstack] describing APIs for OpenStack consumers

On Wed, 2011-10-26 at 12:14 -0400, Jay Pipes wrote: > That's fine for generating a WADL for existing APIs that are already > implemented. Not so good for proposed APIs ;) Oh, certainly, but there the auto-generation could be used to verify that the code implements the proposed API :) -- Kevin L.

Re: [Openstack] describing APIs for OpenStack consumers

To answer this, yes, it's possible. Rails does it already, in some fashion. They have some convention for generating all routes, which I think is one of the most important take aways here, and they provide a DSL for implementing other routes very easily. From there, one could readily generate the m

Re: [Openstack] describing APIs for OpenStack consumers

Hi, Seems to me there are two different use cases out there. Auto-generated docs should be complete/exhaustive "reference" material for what the API has to offer. Experienced developers will eventually use this only (quick check of syntax for example). Reference material does not negate the nee

Re: [Openstack] describing APIs for OpenStack consumers

On Oct 26, 2011, at 10:48 AM, Kevin L. Mitchell wrote: > On Tue, 2011-10-25 at 15:30 -0700, Joseph Heck wrote: >> It sounds like even though most of us hate WADL, it's what we're >> expending effort after to make a consolidated API set. So unless Nati >> and Ravi want to switch to using Swagger (

Re: [Openstack] SystemUsageData in Diablo via notification system?

Have you been testing and/or working with a specific hub from the list on that wiki page (http://code.google.com/p/pubsubhubbub/wiki/Hubs)? What I'm wondering is how we could set up a notification system that would be highly available (i.e. two nodes or a failover mechanism) that wouldn't loose

[Openstack] Fwd: SystemUsageData in Diablo via notification system?

I answered Roe Lee's question via email, but I figured some other folks on the list might want to know as well... Begin forwarded message: Date: October 26, 2011 12:21:34 AM CDT To: Roe Lee mailto:hrlee...@gmail.com>> Subject: Re: SystemUsageData in Diablo via notification system? Hello! Yes,

Re: [Openstack] API Versioning and Extensibility

On 10/24/2011 11:20 PM, Mark Nottingham wrote: > tl;dr Much omitted, since it's long... I agree strongly with 98% of what you are saying. I'll focus on the variants here. I'd rather just get rid of them. > GET /servers.v1.json vs > http://api.example.com/v1/foo I agree with you that the latter

Re: [Openstack] Donabe meetings on Wed 2pm (and cancelling this week's)

For others outside of California, that's 2PM Pacific time. :-) Glen Campbell • Cloud 2.0 Architect glen.campb...@rackspace.com • (210) 446-9990 On Oct 26, 2011, at 2:07 PM, Debo Dutta (dedutta) wrote: Hi Lots of people had expressed interest but they were

[Openstack] Donabe meetings on Wed 2pm (and cancelling this week's)

Hi Lots of people had expressed interest but they were not aware of the meeting times (we did send out emails but maybe we should have re-sent a few times). We meet at 2pm on Wed, @#openstack-meetings . Please join us and help us make Donabe better. Also we are canceling this wee

Re: [Openstack] Donabe meetings on Wed 2pm (and cancelling this week's)

Apologies Thanks Glen for the clarifications. debo From: Glen Campbell [mailto:glen.campb...@rackspace.com] Sent: Wednesday, October 26, 2011 12:12 PM To: Debo Dutta (dedutta) Cc: Subject: Re: [Openstack] Donabe meetings on Wed 2pm (and cancelling this week's) For others outsid

[Openstack] Nova Essex Blueprint Targeting and Assignment

Hello Everyone, I've (finally managed) to get all of the blueprints organized and assigned to essex. I've assigned any that had no user assigned to them to the subteams. From here on I will need help from the subteam leads to: a) Assign blueprints to the individual(s) that will be implementin

Re: [Openstack] SystemUsageData in Diablo via notification system?

We've used the standard google ref. hub. The Yagi app stores notifications (with an optional expiry) in Redis, and generates feeds from the items in redis. Redis can be clustered. Yagi is composed of two parts, the yagi-event daemon which reads from the AMQP queue, stores notifications in re

[Openstack] Essex Blueprints Links

Hello Again, I intended to post a link to the essex blueprints. Here it is: https://blueprints.launchpad.net/nova/essex Also, I've moved a number of blueprints into a sort of backlog. These are blueprints that seem to be stalled out, or that are good ideas but don't have anyone particular to

Re: [Openstack] API Versioning and Extensibility

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 variants! "Here's my usage stats for 2009... http://usage.api.acme.com/v1.0/jorgew/2009/usage.pdf"; You mean to tell me that I can't sen

Re: [Openstack] API Versioning and Extensibility

Clickability is irrelevant. An API is an APPLICATION programming interface. It's about enabling applications to interact with it. -George On Oct 26, 2011, at 4:45 PM, Jorge Williams wrote: > > On Oct 26, 2011, at 1:19 PM, Bryan Taylor wrote: > >> So no pdfs or excel spreadsheets without conne

Re: [Openstack] describing APIs for OpenStack consumers

So you would do a diff if the generated WADL against the expected WADL. That would mean we use both. I think that's a reasonable approach. On Oct 26, 2011, at 12:31 PM, "Monsyne Dragon" wrote: > > On Oct 26, 2011, at 10:48 AM, Kevin L. Mitchell wrote: > >> On Tue, 2011-10-25 at 15:30 -0700,

[Openstack] service iscsitarget can't start

manage volumes after command: sed -i ‘s/false/true/g’ /etc/default/iscsitarget service iscsitarget start return service started but when "ps -ef |grep iscsitarget" ,i can't see the service iscsitarget, i think it's stoped i think the process ietd has some problem who can te

Re: [Openstack] service iscsitarget can't start

Maybe cause the daemon name is "iscsitgtd" ... ? 2011/10/26 aliex_liu > ** > manage volumes > after command: > sed -i ‘s/false/true/g’ /etc/default/iscsitarget > service iscsitarget start > return service started > but when "ps -ef |grep iscsitarget" ,i can't see the servic

Re: [Openstack] ImportError: CRITICAL nova [-] No module named urlmap

Thanks Jay... I had installed paste package it is coming up now. --Thanks and regards, Praveen GK. On Wed, Oct 26, 2011 at 8:47 PM, Jay Pipes wrote: > Hi Praveen! > > Please report bugs and/or questions like this on Launchpad's Bugs or > Answers areas for Nova: > > https://bugs.launchpad.net/n

Re: [Openstack] API Versioning and Extensibility

On 27/10/2011, at 5:19 AM, Bryan Taylor wrote: > On 10/24/2011 11:20 PM, Mark Nottingham wrote: >> tl;dr > Much omitted, since it's long... I agree strongly with 98% of what you are > saying. > > I'll focus on the variants here. I'd rather just get rid of them. I think there's a discussion to

[Openstack] How to Backup Instance?

Hi, all. I run command: nova --version 1.0 backup . for example) # nova --version 1.0 backup 30 "backup_test" daily 3 So, novaclient make a snapshot image and upload to glance server. # nova image-list a# nova image-list ++-++ | ID | Name| Sta

Re: [Openstack] API Versioning and Extensibility

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 variants! Reports and spreadsheets are presentation layer resources that should come f

Re: [Openstack] API Versioning and Extensibility

On 10/26/2011 11:19 PM, Mark Nottingham wrote: My problem with indicating the media type versioning in the root of the URI is that /v1/ style URIs typically indicate the versioning of the *whole* API, not just the media types being used. To be completely honest, I'd