Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

On 05/09/2012 03:17 PM, Tihomir Trifonov wrote: > Hi Doug, > > not sure if you've hit the same problem, but I've spent some time on > that when I started using RabbitMQ. As I see from the example, you've > provided: > > queue = Queue(name='notifications.info', > > exchange=Exch

Re: [Openstack] Keystone client, user belongs to many tenants?

I think this use case underscores one of the key differences between the fat Keystone (Diablo - E3) and KSL (Essex final). In fat Keystone, users and tenants are loosely coupled. They are bind together by role assignments. In KSL, users and tenants are tightly coupled, and IMHO very inflexible.

[Openstack] Improving Xen support in the libvirt driver

Hi, I've been tinkering with improving Xen support in the libvirt driver and wanted to discuss a few issues before submitting patches. Even the latest upstream release of Xen (4.1.x) contains a rather old qemu, version 0.10.2, which rejects qcow2 images with cluster size > 64K. The libvirt drive

Re: [Openstack] [Metering] Meeting agenda for today 16:00 UTC (May 3rd, 2012)

A question/comment about the scope of the schema or maybe the architecture. Assuming the services will provide the instrumentation to populate the raw metric data, it seems likely that you will need to define an interface between the services/agents that are providing the data and the metering syst

Re: [Openstack] 'nova flavor-list' fails with "ERROR: string indices must be integers, not str", but 'nova-manage flavor list' succeeds.

That's the traceback from novaclient. If you're getting a 503, there's likely a traceback in the nova-api service logs. - Chris On May 9, 2012, at 5:38 PM, James R Penick wrote: > Sorry, forgot to include that: > > bash-4.1$ nova —debug image-list > connect: (127.0.0.1, 5000) > send: 'POST /

Re: [Openstack] [Metering] External API definition

Is it your assumption that there will be one metering service per "installation" or one per service (i.e swift, nova)? My assumption would be a single metering service, so the API would need to handle some additional use cases: -list services supported -list metrics for a service type -get metric d

Re: [Openstack] [Swift] swift news and plans

2012/5/4 John Dickinson : > TL;DR: removing code from swift, associated projects doc, swift 1.5.0 This is interesting stuff. Where was this discussed? -- Soren Hansen             | http://linux2go.dk/ Senior Software Engineer | http://www.cisco.com/ Ubuntu Developer         | http://www.ubuntu.c

Re: [Openstack] [QA] Aligning "smoke" / "acceptance" / "promotion" test efforts

On 05/03/2012 10:54 PM, Maru Newby wrote: The rest api is the default interface, and the client tools target that interface. Since the clients are cli more than python api, they can be used by any language that can use a shell. What exactly does reimplementing the clients for the sake of testing

Re: [Openstack] [QA] Aligning "smoke" / "acceptance" / "promotion" test efforts

On 05/03/2012 03:54 PM, Daryl Walleck wrote: So my first question is around this. So is the claim is that the client tools are the default interface for the applications? Sorry, perhaps a better term would have been "the most common interface to OpenStack Compute"... > While that works for

Re: [Openstack] Keystone client, user belongs to many tenants?

On May 9, 2012, at 4:46 PM, Joshua Harlow wrote: > A question, > > I am using anvil to setup the keystone roles/users/tenants. > > It seems like the python keystone client has the following command: > > client.users.create > > Which seems to take in the following: > > create(self, name, pas

Re: [Openstack] 'nova flavor-list' fails with "ERROR: string indices must be integers, not str", but 'nova-manage flavor list' succeeds.

Sorry, forgot to include that: bash-4.1$ nova —debug image-list connect: (127.0.0.1, 5000) send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 127.0.0.1:5000\r\nAccept-Encoding: identity\r\nContent-Length: 101\r\ncontent-type: application/json\r\naccept: application/json\r\nuser-agent: python-novaclient\

Re: [Openstack] 'nova flavor-list' fails with "ERROR: string indices must be integers, not str", but 'nova-manage flavor list' succeeds.

Is there a traceback from nova-api? ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp

Re: [Openstack] questions on the dynamic loading of virt drivers in nova

No this is mostly just legacy stuff that was never refactored. Vish On May 9, 2012 3:33 PM, "Sean Dague" wrote: > I'm familiarizing myself with the nova code and trying to reconcile that > while there is dynamic class based loading in ComputeManager using > import_utils in __init__() there is al

Re: [Openstack] Keystone client, user belongs to many tenants?

The tenant_id field on user creation is the "default tenant" for the user. Adding a user to additional tenants is done by granting the user one or more roles on those tenants. All the best, - Gabriel From: openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net [mailto:opens

[Openstack] Beyond the Usergroups wiki page

Hello folks, if you manage a user group or want to create one or you're simply interested in OpenStack User Groups I would suggest to join this conversation: https://lists.launchpad.net/openstack-community/msg00081.html I'd like to gather the specifications for a system to keep a better dire

Re: [Openstack] Keystone client, user belongs to many tenants?

The user create command is actually creating discrete users, each with a "default tenant" reference. While that's fine for a lot of simple use cases, it doesn't directly support a user accessing multiple tenants at all. Instead, create a role, and grant that role to a user-tenant pair, creating

Re: [Openstack] ERROR: Malformed request url (HTTP 400)

Hrm, good catch! I see no problems with that request at all... -Dolph Mathews On May 9, 2012, at 5:58 PM, "Kevin L. Mitchell" wrote: > On Wed, 2012-05-09 at 15:32 -0500, Dolph Mathews wrote: >> It also just occurred to me that perhaps you're using a *very* old >> novaclient against a more rece

Re: [Openstack] Keystone client, user belongs to many tenants?

users are defined as globally unique in keystone what's anvil? -joe On May 9, 2012, at 1:46 PM, Joshua Harlow wrote: > A question, > > I am using anvil to setup the keystone roles/users/tenants. > > It seems like the python keystone client has the following command: > > client.users.create >

[Openstack] 'nova flavor-list' fails with "ERROR: string indices must be integers, not str", but 'nova-manage flavor list' succeeds.

Hey Folks, Any idea why 'nova flavor-list' (among other things) would fail with a 503 but 'nova-manage flavor list' succeeds? bash-4.1$ sudo nova-manage flavor list Password: m1.medium: Memory: 4096MB, VCPUS: 2, Root: 10GB, Ephemeral: 40Gb, FlavorID: 3, Swap: 0MB, RXTX Factor: 1.0 m1.large: Mem

Re: [Openstack] ERROR: Malformed request url (HTTP 400)

On Wed, 2012-05-09 at 15:32 -0500, Dolph Mathews wrote: > It also just occurred to me that perhaps you're using a *very* old > novaclient against a more recent version of keystone? Actually, if you look a little more closely: > $ nova --debug image-list > connect:

Re: [Openstack] [Metering] schema and counter definitions

I agree. Do you have any plans how to coordinate our efforts ? On Wed, May 9, 2012 at 11:11 PM, Doug Hellmann wrote: > > > On Wed, May 9, 2012 at 3:07 PM, Tomasz Paszkowski wrote: >> >> On Wed, May 9, 2012 at 8:02 PM, Doug Hellmann >> wrote: >> > >> > Nice! >> > >> > For production code I thi

Re: [Openstack] [QA] Aligning "smoke" / "acceptance" / "promotion" test efforts

Hi Daryl, Unfortunately I'll be unable to attend the QA meeting this week, but would like to talk about it with you sometime. I have spent almost no time on negative tests and would like to hear about the issues you are facing there. I know some corner cases dealing with auth in particular can

Re: [Openstack] Instances can't access eachother via external (floating) ips?

On 05/09/2012 02:09 PM, Steven Dake wrote: Read more details here: https://github.com/heat-api/heat/wiki/Configuring-Floating-IPs Is there a reason this is on a GitHub wiki versus on the official OpenStack wiki and/or the documentation? Seems like some great information that really should be

Re: [Openstack] [Metering] schema and counter definitions

On Wed, May 9, 2012 at 3:07 PM, Tomasz Paszkowski wrote: > On Wed, May 9, 2012 at 8:02 PM, Doug Hellmann > wrote: > > > > Nice! > > > > For production code I think we are going to want to separate collection > from > > storage, aren't we? We don't want each compute node to require access to > th

Re: [Openstack] [Metering] Bootstrapping, first counter implementation

On Wed, May 9, 2012 at 11:13 AM, Julien Danjou wrote: > Hi there, > > I've added a first script that's able to connect to the AMQP > notification queue using Nova RPC module. Later it will be able to treat > them when we'll know what to do with them. > > https://review.stackforge.org/#/c/26/ > h

Re: [Openstack] Nova Core Cleanup

On Wed, 2012-05-09 at 19:58 +, Matt Dietz wrote: > The problem here is there are two opposing points: the idea that there are > too many core reviewers, and the idea that patches aren't being reviewed > "fast enough." > > *Drags a yak into the room* Beyond that, what makes 20 better than 25,

Re: [Openstack] [Netstack] About python versions that we are planning to support

On Wed, May 09, 2012, Robert Kukura wrote: > I'm very concerned about the potential of this XenServer/XCP requirement > to interfere with making the various Quantum agents first-class > OpenStack services by utilizing current and future openstack-common > facilities for configuration, logging, DB,

[Openstack] Keystone client, user belongs to many tenants?

A question, I am using anvil to setup the keystone roles/users/tenants. It seems like the python keystone client has the following command: client.users.create Which seems to take in the following: create(self, name, password, email, tenant_id=None, enabled=True): I would assume a user name

[Openstack] questions on the dynamic loading of virt drivers in nova

I'm familiarizing myself with the nova code and trying to reconcile that while there is dynamic class based loading in ComputeManager using import_utils in __init__() there is also a defaulting to the nova.virt.connection.get_connection function. That's actually got a big if / else statement o

Re: [Openstack] ERROR: Malformed request url (HTTP 400)

It also just occurred to me that perhaps you're using a *very* old novaclient against a more recent version of keystone? -Dolph On Wed, May 9, 2012 at 3:30 PM, Dolph Mathews wrote: > The request URL is actually fine, but the request body is quite malformed: > > {"tenantName": "labSpaceDemo",

Re: [Openstack] ERROR: Malformed request url (HTTP 400)

The request URL is actually fine, but the request body is quite malformed: {"tenantName": "labSpaceDemo", "passwordCredentials": {"username": "adminUser", "password": "lfplhfgthvf"}}} What's there would be just fine if it were wrapped in an "auth" element (see http://keystone.openstack.org/ap

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

On 05/09/2012 01:57 PM, Doug Hellmann wrote: > Is that the preferred way to do it, rather than attaching another queue > to the existing exchange with the same routing key? I would just do what you're doing now, which is to use the existing exchange. That lets the message broker do the work of du

Re: [Openstack] Nova Core Cleanup

The problem here is there are two opposing points: the idea that there are too many core reviewers, and the idea that patches aren't being reviewed "fast enough." *Drags a yak into the room* Beyond that, what makes 20 better than 25, or 15, especially in light of the fact that we're not happy wit

Re: [Openstack] Floating IPs don't get dissociated after delete

This definitely sounds like a bug. Floating Ips should be automatically disassociated on delete Vish On May 9, 2012, at 8:26 AM, Steven Dake wrote: > On 05/09/2012 07:20 AM, Bilel Msekni wrote: >> Hi , >> >> I am having this problem just like many others. >> >> Each time I delete a VM, the f

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

On Wed, May 9, 2012 at 3:17 PM, Tihomir Trifonov wrote: > Hi Doug, > > not sure if you've hit the same problem, but I've spent some time on that > when I started using RabbitMQ. As I see from the example, you've provided: > > queue = Queue(name='notifications.info', > > exchange=

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

Hi Doug, not sure if you've hit the same problem, but I've spent some time on that when I started using RabbitMQ. As I see from the example, you've provided: queue = Queue(name='notifications.info', exchange=Exchange(name='nova'... So you set explicitly a name for the queue.

Re: [Openstack] Instances can't access eachother via external (floating) ips?

On 04/25/2012 01:03 PM, Calvin Walton wrote: > On Mon, 2012-04-23 at 06:45 -0700, Mike Scherbakov wrote: >> Hi Calvin, > Sorry I didn't respond earlier, the email temporarily got lost :) > >> show us iptables -nL -t nat | grep NAT on the node with nova-network. > > (192.168.0.101 is the nova-netw

Re: [Openstack] [Metering] schema and counter definitions

On Wed, May 9, 2012 at 8:02 PM, Doug Hellmann wrote: > > Nice! > > For production code I think we are going to want to separate collection from > storage, aren't we? We don't want each compute node to require access to the > database server (that's an issue with nova that they are trying to fix >

Re: [Openstack] [Netstack] About python versions that we are planning to support

I'm concerned about a need to support python 2.4 as well, especially if it would have a ripple effect into openstack-common, which otherwise does not have that requirement. With XenServer, nova-compute actually runs in a service VM (which is running a modern version of python). I believe Salvator

Re: [Openstack] Nova Core Cleanup

On Wed, 2012-05-09 at 11:34 +0100, Mark McLoughlin wrote: > I rarely -2, because I see it as a strong veto which blocks the patch or > later revisions of the patch until I remove the -2. Maybe it's just the > fact that I know I'm likely to be slow to come back and review later > revisions of a pat

[Openstack] ERROR: Malformed request url (HTTP 400)

Hi all from sunny Kiev! Have the problem below: $ nova image-list ERROR: Malformed request url (HTTP 400) $ nova --debug image-list connect: (192.168.1.71, 5000) send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 192.168.1.71:5000\r\nContent-Length: 117\r\ncontent-type: application/json\r\naccept-encodi

Re: [Openstack] [Metering] schema and counter definitions

On Wed, May 9, 2012 at 12:42 PM, Tomasz Paszkowski wrote: > Here is the simplified version of my code (without ampq support, > counter stored directly to mysql db). > > https://github.com/ss7pro/rescnt > > Code is started from main.py which is constantly collecting counters > from libvirt and sto

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

Is that the preferred way to do it, rather than attaching another queue to the existing exchange with the same routing key? On Wed, May 9, 2012 at 1:46 PM, Craig Vyvial wrote: > You can allow nova to send notifications to multiple topics by setting > this option in your nova.conf. > > ## (Li

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

You can allow nova to send notifications to multiple topics by setting this option in your nova.conf. ## (ListOpt) AMQP topic used for Nova notifications notification_topics="notifications,metering,monitoring" This will allow you to consume all the messages from a different service. On Wed,

Re: [Openstack] [Metering] Bootstrapping, first counter implementation

On 05/09/2012 05:38 PM, Doug Hellmann wrote: > What is the difference between review.stackforge.org > and review.openstack.org > and why aren't we using the latter? There is no technical difference (to my knowledge ;-). Only review.sta

Re: [Openstack] Swift on Webob-1.2 anyone?

On Wed, 9 May 2012 16:14:48 +0100 Chmouel Boudjnah wrote: > The challenge if you are taking a stab at it would probably be to > support webob 1.1* and 1.2 at the same time in the code. I noticed that too. 1.1.1 made some intermediate choices that are difficult to reconcile, namely throwing warni

[Openstack] Fwd: ceilometer (java implementation)

Forgot to copy the list -- Forwarded message -- From: Luis Gervaso Date: Wed, May 9, 2012 at 7:14 PM Subject: Re: [Openstack] ceilometer (java implementation) To: Doug Hellmann I asked for these fields in my previous email, they are not clear enough. After analyze the problem,

Re: [Openstack] [Metering] Bootstrapping, first counter implementation

Ah, got it. Thanks! On Wed, May 9, 2012 at 12:45 PM, heut2008 wrote: > stackForge is a Gerrit review and Jenkins CI setup similar to that of > the main OpenStack project but for use with projects that are not > under the main OpenStack umbrella. > > Any project can be added to StackForge as long

Re: [Openstack] dimenssion of vnc console window

On May 9, 2012, at 6:06 AM, Staicu Gabriel wrote: > Hi, > > I found a way to change the dimenssion of the window image for the vnc > console. > The file to be changed is: > /usr/share/pyshared/horizon/dashboards/nova/templates/nova/instances_and_volumes/instances/_detail_vnc.html. > The parame

Re: [Openstack] ceilometer (java implementation)

That's fantastic! What I mind is that the counters only should gather event info. Maybe multiple counters listening, collecting info about the system. But only one persist the event. Other process agreggates the data and creates different views/reports/billing, this should be outside of openstac

Re: [Openstack] [Metering] Bootstrapping, first counter implementation

stackForge is a Gerrit review and Jenkins CI setup similar to that of the main OpenStack project but for use with projects that are not under the main OpenStack umbrella. Any project can be added to StackForge as long as it is related to OpenStack in some way. 2012/5/9 Doug Hellmann : > What is

Re: [Openstack] [Metering] External API definition

Doug Hellmann wrote: >On Wed, May 9, 2012 at 11:27 AM, Nick Barcet >wrote: > >> On 05/08/2012 08:27 AM, Nick Barcet wrote: >> [..] >> >> Thinking about this, I think we need to expend the API a bit to >reflect >> the evolutions of the schema that we decided last week. Here are my >> proposals:

Re: [Openstack] [Metering] schema and counter definitions

Here is the simplified version of my code (without ampq support, counter stored directly to mysql db). https://github.com/ss7pro/rescnt Code is started from main.py which is constantly collecting counters from libvirt and storing them in a mysql database. On Mon, May 7, 2012 at 9:25 PM, Tomasz

[Openstack] route problem in multi-host enviroment

there are two zone with fix IP: Zone1 10.8.0.0/23 Zone2 10.9.0.0/23 there are some network host in each zone, and the vm in same zone can own different gateway. if i need to route VMs in zone1 with VMs in Zone2, how can set it? -- 彭勇 (Peng Yong)

Re: [Openstack] Swift on Webob-1.2 anyone?

On 05/09/2012 05:45 AM, Pete Zaitcev wrote: I ran .unittests on a box with python-webob-1.2b3 and it throws left and right: errors=72, failures=6. I'm wondering if anyone is working on adapting Swift for WebOb 1.2 and if a patch is available somewhere. I see Ionut fixed lp:984042, but clearly it

Re: [Openstack] [Netstack] About python versions that we are planning to support

[I'm moving this thread to the openstack list because it potentially impacts openstack-common.] On 05/07/2012 11:53 PM, Maru Newby wrote: > Hi, > > Python 2.4 compatibility is required, but only for agent code. Agent > code needs to be deployable on Xen dom0, which uses CentoOS 5.5 and only > su

Re: [Openstack] Translation and Internationalization in OpenStack

On 05/08/2012 09:56 PM, Thierry Carrez wrote: > Gabriel Hurley wrote: >> Having worked with all three tools, I would strongly suggest Transifex, >> particularly given that we as a community have to do almost no work to >> maintain it, it's the only tool that supports OpenStack as a "project hub

Re: [Openstack] [Metering] External API definition

On Wed, May 9, 2012 at 11:27 AM, Nick Barcet wrote: > On 05/08/2012 08:27 AM, Nick Barcet wrote: > [..] > > Thinking about this, I think we need to expend the API a bit to reflect > the evolutions of the schema that we decided last week. Here are my > proposals: > > > * Requests allow to > > GE

Re: [Openstack] [Metering] External API definition

On 05/09/2012 08:36 AM, Doug Hellmann wrote: > > > On Tue, May 8, 2012 at 8:43 PM, Nick Barcet > wrote: > > On 05/08/2012 11:39 AM, Doug Hellmann wrote: > [..] > > * Requests must be authenticated (separate from keystone, or > only linked >

Re: [Openstack] [Metering] Bootstrapping, first counter implementation

What is the difference between review.stackforge.org and review.openstack.org and why aren't we using the latter? On Wed, May 9, 2012 at 11:13 AM, Julien Danjou wrote: > Hi there, > > I've added a first script that's able to connect to the AMQP > notification queue using Nova RPC module. Later it

Re: [Openstack] [Metering] External API definition

On Tue, May 8, 2012 at 8:43 PM, Nick Barcet wrote: > On 05/08/2012 11:39 AM, Doug Hellmann wrote: > [..] > > * Requests must be authenticated (separate from keystone, or only > linked > > to accounting type account) > > > > > > What is the motivation for authenticating with a service other

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

On Wed, May 9, 2012 at 6:42 AM, Kiall Mac Innes wrote: > Kinda! The queue has a name, but that name has no bearing on the set of > messages received. > If you create a queue called "MyCustomNotificationQueue", you can bind > that to the "notifications" exchange using the "notifications.info" >

Re: [Openstack] ceilometer (java implementation)

On Tue, May 8, 2012 at 7:19 PM, Luis Gervaso wrote: > Hi, > > I have uploaded a toy version of ceilometer (java implementation). > > It does implement the first two counters (instance : rabbitmq listener and > cpu : polling from libvirt) > > i need more clarification on the meaining: > > counter_

Re: [Openstack] [Metering] External API definition

On 05/08/2012 08:27 AM, Nick Barcet wrote: [..] Thinking about this, I think we need to expend the API a bit to reflect the evolutions of the schema that we decided last week. Here are my proposals: > * Requests allow to > GET account_id list change to: GET [user_id|project_id|source] list >

Re: [Openstack] Floating IPs don't get dissociated after delete

On 05/09/2012 07:20 AM, Bilel Msekni wrote: > Hi , > > I am having this problem just like many others. > > Each time I delete a VM, the floating IP doesn't get automatically > dissociated, has anyone encountred this problem and solved it ? > > > ___

Re: [Openstack] Swift on Webob-1.2 anyone?

Hi Pete, On Wed, May 9, 2012 at 4:45 AM, Pete Zaitcev wrote: > on adapting Swift for WebOb 1.2 and if a patch is available somewhere. > I see Ionut fixed lp:984042, but clearly it wasn't enough. > If nobody's done it yet, I suppose I could take a swing at it. New webob I started doing that somet

[Openstack] [Metering] Bootstrapping, first counter implementation

Hi there, I've added a first script that's able to connect to the AMQP notification queue using Nova RPC module. Later it will be able to treat them when we'll know what to do with them. https://review.stackforge.org/#/c/26/ https://review.stackforge.org/#/c/27/ https://review.stackforge.or

Re: [Openstack] Munin plugins for essex (nova, keystone, glance)

Very useful ! Thanks, Jérôme On Wed, May 9, 2012 at 11:58 AM, Razique Mahroua wrote: > Amazing work > congratulations and thank you. > > I'm myself working on zabbix templates. Maybe we could share our effort > and create a monitoring repo for openstack (bash scripts, monitoring > templates, etc

[Openstack] Floating IPs don't get dissociated after delete

Hi , I am having this problem just like many others. Each time I delete a VM, the floating IP doesn't get automatically dissociated, has anyone encountred this problem and solved it ? ___ Mailing list: https://la

Re: [Openstack] Pending review

Yes, it should. I'll tag it for essex back-port once this review is approved and code is merged to master. -Mandar -Original Message- From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net [mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf Of

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

Kinda! The queue has a name, but that name has no bearing on the set of messages received. If you create a queue called "MyCustomNotificationQueue", you can bind that to the "notifications" exchange using the "notifications.info" routing key. (I'm guessing some of the names here.. I know AMQP, an

Re: [Openstack] Nova Core Cleanup

On Tue, 2012-05-08 at 15:44 -0700, Vishvananda Ishaya wrote: > The -2 issue is a good point. I personally treat a -1 (or +1) from the > author of a given piece of code quite strongly when I do reviews, but > you're right that the -1 could be more trivially overridden. Coincidentally, dprince and

Re: [Openstack] Pending review

On Wed, May 09, 2012 at 05:38:44AM +, Vaze, Mandar wrote: > https://review.openstack.org/#/c/6829/ > > Kevin Mitchell has reviewed as "Looks good to me" > Additional reviews and approval required This looks like it should also go to stable/essex, once it got merged to master? Best Christoph

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

OK, get that so far - so both consumers need to declare and use the same exchange. But If I understand the next step right, to get multiple consumers of info notification messages they would all need to create separate "notifications.info" queues into that exchange.And isn't that exactly w

Re: [Openstack] Swift Object Storage

On 09/05/12 04:02, Sid Sudhi wrote: > > I am trying to write a script to upload large sized files. I am > encountering the following limitations - can some one shed some light if > they can help me over come the issue? > > When files are big and they uploaded with chunks these chunks do not > del

[Openstack] dimenssion of vnc console window

Hi, I found a way to change the dimenssion of the window image for the vnc console. The file to be changed is: /usr/share/pyshared/horizon/dashboards/nova/templates/nova/instances_and_volumes/instances/_detail_vnc.html. The parameters are: width="1280" height="900" Regards, Gabriel _

Re: [Openstack] Munin plugins for essex (nova, keystone, glance)

Amazing workcongratulations and thank you.I'm myself working on zabbix templates. Maybe we could share our effort and create a monitoring repo for openstack (bash scripts, monitoring templates, etc..)what you guys think ? Nuage & Co - Razique Mahroua razique.mahr...@gmail.com Le 9 mai 2012 à 11:31

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

Your own queue listener should attempt to declare the exchange, using the same settings as Nova does. If the exchange exists, its a noop. Otherwise it's created for you. After that, if you start up Nova, it will do the same and reuse your exchange. Obviously this works both ways, and either nova

[Openstack] Munin plugins for essex (nova, keystone, glance)

Hi, I have recently updated and created some munin plugin for nova, keystone, glance of the essex release. The following metrics are retrieved: - glance: total/used size by tenant - glance: number of images per status - keystone: number of tenant enabled and total tenants - nova: total/allocat

Re: [Openstack] [nova] why does notification use a "topic" exchange instead of "fanout"?

Hi Doug, > I think you missed my main point, which was that a topic exchange does > not impose a limitation that only one client can consume a given > notification. That's only true if each client is consuming from the > same queue bound to the exchange. So just to be clear, if I understand you

Re: [Openstack] nova-manage network documentation

The flags can be viewed using the --help command (see below). Dan danwent@ubuntu:~/nova$ bin/nova-manage network --help --help does not match any options: create delete list modify quantum_list danwent@ubuntu:~/nova$ bin/nova-manage network create --help Usage: nova-manage network create [op

Re: [Openstack] nova-manage network documentation

ok, done here: https://bugs.launchpad.net/openstack-manuals/+bug/996970 cheers, michaël Michaël Van de Borne R&D Engineer, SOA team, CETIC Phone: +32 (0)71 49 07 45 Mobile: +32 (0)472 69 57 16, Skype: mikemowgli www.cetic.be, rue des Frères W

Re: [Openstack] nova-manage network documentation

Hi Michaël,would you please fill a bug here https://bugs.launchpad.net/openstack-manualsSo the team could check/ update the doc Regards,Razique Nuage & Co - Razique Mahroua razique.mahr...@gmail.com Le 9 mai 2012 à 09:40, Michaël Van de Borne a écrit :Hi all,I might be missing something, but I can

[Openstack] nova-manage network documentation

Hi all, I might be missing something, but I can't find any comprehensive documentation of the 'nova-manage network' subcommand. The only doc entries I find about this are examples, but no list of flags, neither in 'man nova-manage', nor in 'nova-manage --help' nor in http://nova.openstack.or