[Openstack] how to connect to private network with cloudpipe?

I am using VLANManager mode for nova-network,it seems I need cloudpipe to connect to the instances from internet.. I try to deploy cloudpipe with http://nova.openstack.org/devref/cloudpipe.html but I don't understand all the step of it; In the step of Create a Cloudpipe Image, I don't really kn

Re: [Openstack] eventlet weirdness

Excerpts from Monsyne Dragon's message of 2012-03-02 16:10:01 -0500: > > On Mar 2, 2012, at 9:17 AM, Jay Pipes wrote: > > > On 03/02/2012 05:34 AM, Day, Phil wrote: > >> In our experience (running clusters of several hundred nodes) the DB > >> performance is not generally the significant factor,

Re: [Openstack] eventlet weirdness

First I agree that having blocking DB calls is no big deal given the way Nova uses mysql and reasonably powerful db server hardware. However I'd like to point out that the math below is misleading (the average time for the nonblocking case is also miscalculated but it's not my point). The number t

Re: [Openstack] eventlet weirdness

On Mar 2, 2012, at 2:11 PM, Duncan McGreggor wrote: > On Fri, Mar 2, 2012 at 4:10 PM, Monsyne Dragon wrote: >> >> >> Has anyone thought about switching to gevent? It's similar enough to >> eventlet that the port shouldn't be too bad, and because it's event loop is >> in C, (libevent), ther

Re: [Openstack] eventlet weirdness

On Mar 2, 2012, at 12:50 PM, Jay Pipes wrote: > > We are not using multiprocessing, no. > > We simply start multiple worker processes listening on the same socket, with > each worker process having an eventlet greenthread pool. > > You can see the code (taken from Swift and adapted by Chris Be

[Openstack] OpenStack Community Newsletter –March 2, 2012

OpenStack Community Newsletter –March 2, 2012 HIGHLIGHTS * OpenStack Governance Elections Spring 2012: remember to vote if you have received the ballot. Results will be announced tomorrow with a blog post. At 2:00pm PST this is the voter’s turnout: * PPB: 104

Re: [Openstack] RHEL 5 & 6 OpenStack image archive...

On 03/02/2012 05:30 PM, John Paul Walters wrote: > David, > > We're currently in the process of building Essex-3/Essex-4 RPMs locally > at USC/ISI for our heterogeneous Openstack builds. When I looked at the > EPEL testing repo, it looked like the packages that are currently > available are right

Re: [Openstack] RHEL 5 & 6 OpenStack image archive...

Hi David and John, I am not sure if we are talking about the same, It seems that Marc needs base RedHat images to be used on his OpenStack deployment. It seems that you are talking on some kind of RedHat distribution with OpenStack already installed, if not please clarify and let us know what

[Openstack] Doc Day March 6th - the plan the plan

Hi all - Please consider this your invitation to take the day on Tuesday to work on docs, for any audience, but with special attention to the top priority gaps for Essex. I've started an Etherpad to work through the priorities list for Doc Day, feel free to edit as you see fit. http://etherpad.op

Re: [Openstack] RHEL 5 & 6 OpenStack image archive...

David, We're currently in the process of building Essex-3/Essex-4 RPMs locally at USC/ISI for our heterogeneous Openstack builds. When I looked at the EPEL testing repo, it looked like the packages that are currently available are right around Essex-1. Are there any plans to update to the mor

Re: [Openstack] eventlet weirdness

On Fri, Mar 2, 2012 at 4:10 PM, Monsyne Dragon wrote: > > On Mar 2, 2012, at 9:17 AM, Jay Pipes wrote: > >> On 03/02/2012 05:34 AM, Day, Phil wrote: >>> In our experience (running clusters of several hundred nodes) the DB >>> performance is not generally the significant factor, so making its call

Re: [Openstack] eventlet weirdness

Why has the ship-sailed? This is software we are talking about right, there is always a v2 (X-1) ;) On 3/2/12 12:38 PM, "Caitlin Bestler" wrote: Duncan McGregor wrote: >Like so many things that are aesthetic in nature, the statement above is >misleading. Using a callback, event-based, def

Re: [Openstack] eventlet weirdness

It could be over-complicated (ie an example), but its a design that lets the program think in what tasks need to be accomplished and how to order those tasks and not have to think about how those tasks are actually ran (or hopefully even what concurrency occurs). Ideally there should be no concu

Re: [Openstack] eventlet weirdness

On 03/02/2012 04:10 PM, Monsyne Dragon wrote: Has anyone thought about switching to gevent? It's similar enough to eventlet that the port shouldn't be too bad, and because it's event loop is in C, (libevent), there are C mysql drivers (ultramysql) that will work with it without blocking. Y

Re: [Openstack] eventlet weirdness

On Mar 2, 2012, at 9:17 AM, Jay Pipes wrote: > On 03/02/2012 05:34 AM, Day, Phil wrote: >> In our experience (running clusters of several hundred nodes) the DB >> performance is not generally the significant factor, so making its calls >> non-blocking gives only a very small increase in proces

Re: [Openstack] RHEL 5 & 6 OpenStack image archive...

We currently have openstack available in EPEL testing repo, help in testing is appreciated. Sent from my iPhone On 2 Mar 2012, at 18:13, "Edgar Magana (eperdomo)" wrote: > Hi Marc, > > I ended up creating my own RHEL 6.1 image. If you want I can share it with > you. > > Thanks, > > Edga

Re: [Openstack] eventlet weirdness

On 03/02/2012 03:38 PM, Caitlin Bestler wrote: Duncan McGregor wrote: Like so many things that are aesthetic in nature, the statement above is misleading. Using a callback, event-based, deferred/promise oriented system is hard for *some*. It is far, far easier for>others (myself included).

Re: [Openstack] eventlet weirdness

On 03/02/2012 01:35 PM, Joshua Harlow wrote: Does anyone else feel that the following seems really “dirty”, or is it just me. “adding a few sleep(0) calls in various places in the Nova codebase (as was recently added in the _sync_power_states() periodic task) is an easy and simple win with prett

Re: [Openstack] eventlet weirdness

On 03/02/2012 02:27 PM, Vishvananda Ishaya wrote: On Mar 2, 2012, at 7:54 AM, Day, Phil wrote: By "properly multi-threaded" are you instead referring to making the nova-api server multi-*processed* with eventlet greenthread pools in each process? i.e. The way Swift (and now Glance) works? Or

Re: [Openstack] eventlet weirdness

On Fri, Mar 02, 2012, Duncan McGreggor wrote: > On Fri, Mar 2, 2012 at 2:40 PM, Johannes Erdfelt wrote: > > Twisted has a much harder programming model with the same blocking > > problem that eventlet has. > > Like so many things that are aesthetic in nature, the statement above > is misleading.

Re: [Openstack] eventlet weirdness

On Fri, Mar 2, 2012 at 3:38 PM, Caitlin Bestler wrote: > Duncan McGregor wrote: > >>Like so many things that are aesthetic in nature, the statement above is >>misleading. Using a callback, event-based, deferred/promise oriented system >>is hard for *some*. It is far, far easier for >others (myse

Re: [Openstack] eventlet weirdness

Duncan McGregor wrote: >Like so many things that are aesthetic in nature, the statement above is >misleading. Using a callback, event-based, deferred/promise oriented system is >hard for *some*. It is far, far easier for >others (myself included). >It's a matter of perception and personal pref

Re: [Openstack] eventlet weirdness

Hi Phil, I'm a little confused. To what extend does sleep(0) help? It only gives the greenlet scheduler a chance to switch to another green thread. If we are having a CPU bound issue, sleep(0) won't give us access to any more CPU cores. So the total time to finish should be the same no matter what

[Openstack] Essex-3 : Nova api calls with keystone doubt

Hi openstack list. Sorry to ask this, but i have a strong doubt on how the "endpoint" config in keystone actually works when you make a nova api call (we are using Essex-3) First, let me setup a use case : user1 -> tenant1 -> zone1 (private nova endpoint) user2 -> tenant2 -> zone2 (p

Re: [Openstack] eventlet weirdness

On Fri, Mar 2, 2012 at 2:40 PM, Johannes Erdfelt wrote: > On Fri, Mar 02, 2012, Armando Migliaccio > wrote: >> I agree, but then the whole assumption of adopting eventlet to simplify >> the programming model is hindered by the fact that one has to think >> harder to what is doing...Nova could've

Re: [Openstack] eventlet weirdness

> > I agree, but then the whole assumption of adopting eventlet to simplify the > programming model is hindered by the fact that one has to think harder to > what is doing...Nova could've kept Twisted for that matter. The programming > model would have been harder, but at least it would have be

Re: [Openstack] eventlet weirdness

Ok - I'll work with Jay on that. -Original Message- From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] Sent: 02 March 2012 19:27 To: Day, Phil Cc: Jay Pipes; openstack@lists.launchpad.net Subject: Re: [Openstack] eventlet weirdness On Mar 2, 2012, at 7:54 AM, Day, Phil wrote: >>

Re: [Openstack] eventlet weirdness

On Fri, Mar 02, 2012, Armando Migliaccio wrote: > I agree, but then the whole assumption of adopting eventlet to simplify > the programming model is hindered by the fact that one has to think > harder to what is doing...Nova could've kept Twisted for that matter. > The programming model would hav

Re: [Openstack] eventlet weirdness

That sounds a bit over complicated to me - Having a string of tasks sounds like you still have to think about what the concurrency is within each step. There is already a good abstraction around the context of each operation - they just (I know - big just) need to be running in something that ma

Re: [Openstack] eventlet weirdness

On Mar 2, 2012, at 7:54 AM, Day, Phil wrote: >> By "properly multi-threaded" are you instead referring to making the >> nova-api server multi-*processed* with eventlet greenthread pools in each >> process? i.e. The way Swift (and now Glance) works? Or are you referring to >> a different approa

Re: [Openstack] eventlet weirdness

On Fri, Mar 2, 2012 at 10:35 AM, Joshua Harlow wrote: > Does anyone else feel that the following seems really “dirty”, or is it > just me. > Any feeling of dirtiness is just due to it being called "sleep," all you are doing is yielding control to allow another co-routine to schedule itself. Bloc

Re: [Openstack] eventlet weirdness

So a thought I had was that say if the design of a component forces as part of its design the ability to be ran with threads or with eventlet or with processes. Say if u break everything up into tasks (where a task would produce some output/result/side-effect). A set of tasks could complete som

Re: [Openstack] eventlet weirdness

> -Original Message- > From: Eric Windisch [mailto:e...@cloudscaling.com] > Sent: 02 March 2012 19:04 > To: Joshua Harlow > Cc: Armando Migliaccio; Jay Pipes; openstack > Subject: Re: [Openstack] eventlet weirdness > > The problem is that unless you sleep(0), eventlet only switches conte

Re: [Openstack] eventlet weirdness

I didn't say it was pretty - Given the choice I'd much rather have a threading model that really did concurrency and pre-emption all the right places, and it would be really cool if something managed the threads that were started so that is a second conflicting request was received it did some p

Re: [Openstack] eventlet weirdness

The problem is that unless you sleep(0), eventlet only switches context when you hit a file descriptor. As long as python coroutines are used, we should put sleep(0) where-ever it is expected that there will be a long-running loop where file descriptors are not touched. As noted elsewhere in

Re: [Openstack] eventlet weirdness

It's not just you On Mar 2, 2012, at 10:35 AM, Joshua Harlow wrote: > Does anyone else feel that the following seems really “dirty”, or is it just > me. > > “adding a few sleep(0) calls in various places in the > Nova codebase (as was recently added in the _sync_power_states() > periodic task)

Re: [Openstack] eventlet weirdness

Looks like a textbook example of a "leaky abstraction" to me. Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com On Mar 2, 2012, at 1:35 PM, Joshua Harlow wrote: > Doe

Re: [Openstack] eventlet weirdness

Does anyone else feel that the following seems really "dirty", or is it just me. "adding a few sleep(0) calls in various places in the Nova codebase (as was recently added in the _sync_power_states() periodic task) is an easy and simple win with pretty much no ill side-effects. :)" Dirty in that

Re: [Openstack] Test Dependencies

On 03/01/2012 08:12 PM, Maru Newby wrote: Is there any interest in adding unittest2 to the test dependencies for openstack projects? I have found its enhanced assertions and 'with self.assertRaises' very useful in writing tests. I see there have been past bugs that mentioned unittest2, and a

Re: [Openstack] RHEL 5 & 6 OpenStack image archive...

Hi Marc, I ended up creating my own RHEL 6.1 image. If you want I can share it with you. Thanks, Edgar Magana CTO Cloud Computing From: openstack-bounces+eperdomo=cisco@lists.launchpad.net [mailto:openstack-bounces+eperdomo=cisco@lists.launchpad.net] On Behalf Of J. Marc Ed

Re: [Openstack] eventlet weirdness

I knew you'd say that :P There you go: https://bugs.launchpad.net/nova/+bug/944145 Cheers, Armando > -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: 02 March 2012 16:22 > To: Armando Migliaccio > Cc: openstack@lists.launchpad.net > Subject: Re: [Openstack] eventl

Re: [Openstack] eventlet weirdness

On 03/02/2012 10:54 AM, Day, Phil wrote: By "properly multi-threaded" are you instead referring to making the nova-api server multi-*processed* with eventlet greenthread pools in each process? i.e. The way Swift (and now Glance) works? Or are you referring to a different approach entirely? Ye

[Openstack] RHEL 5 & 6 OpenStack image archive...

Can someone tell me where these base images are located for use on my OpenStack deployment? Kind regards, Marc -- J. Marc Edwards Lead Architect - Semiconductor Design Portals Nimbis Services, Inc. Skype: (919) 747-3775 Cell: (919) 345-1021 Fax: (919) 882-8602 marc.edwa...@nimbisservices.com w

Re: [Openstack] eventlet weirdness

On 03/02/2012 10:52 AM, Armando Migliaccio wrote: I'd be cautious to say that no ill side-effects were introduced. I found a race condition right in the middle of sync_power_states, which I assume was exposed by "breaking" the task deliberately. Such a party-pooper! ;) Got a link to the bug

Re: [Openstack] eventlet weirdness

> By "properly multi-threaded" are you instead referring to making the nova-api > server multi-*processed* with eventlet greenthread pools in each process? > i.e. The way Swift (and now Glance) works? Or are you referring to a > different approach entirely? Yep - following your posting in here

Re: [Openstack] eventlet weirdness

> -Original Message- > From: openstack-bounces+armando.migliaccio=eu.citrix@lists.launchpad.net > [mailto:openstack- > bounces+armando.migliaccio=eu.citrix@lists.launchpad.net] On Behalf Of Jay > Pipes > Sent: 02 March 2012 15:17 > To: openstack@lists.launchpad.net > Subject: Re:

Re: [Openstack] eventlet weirdness

On 03/02/2012 05:34 AM, Day, Phil wrote: In our experience (running clusters of several hundred nodes) the DB performance is not generally the significant factor, so making its calls non-blocking gives only a very small increase in processing capacity and creates other side effects in terms o

Re: [Openstack] Essex-4 horizon error

darkfower wrote: > i get horizon(essex-4) software package from > https://launchpad.net/horizon/essex/essex-4/+download/horizon-2012.1%7Ee4.tar.gz, > > but i tar xf horizon compress package after, when i exec python setup.py > install emerge error , as follows: > > Traceback (most recent ca

[Openstack] The road to Essex release (a.k.a. what is RC1?)

Hello everyone, With E4 out of the door, here is some explanation on how we'll collectively handle the last 5 weeks before release. The idea for each project is to come up, in the weeks before final release, with a release candidate that they are happy with. On April 5 we'll release all those cand

Re: [Openstack] Essex-4 milestone available for Keystone, Glance, Nova and Horizon

On Fri, 2 Mar 2012 10:45:36 +0800 Shake Chen wrote: > Hi > > In ubuntu 12.04, pool seem not update . > > the package still is old, like keystone: > http://archive.ubuntu.com/ubuntu/pool/universe/k/keystone/ > > # apt-cache policy keystone > keystone: > Installed: (none) > Candidate: 2012.

Re: [Openstack] Essex-4 milestone available for Keystone, Glance, Nova and Horizon

> You mean syncing swift with O-S milestones ? > Well, I'm not sure it needs to be "fixed". Yes. > Reason: Swift is useful without other components. > (Assuming stable API and conservative release cycle.) I can also use Glance without the other components, it's also included in the release cycle

Re: [Openstack] Essex-4 milestone available for Keystone, Glance, Nova and Horizon

On Fri, Mar 2, 2012 at 10:23 AM, Christian Berendt wrote: >> Swift does not follow the common milestones. The latest release is >> 1.4.6, and tha last release available will be included in OpenStack >> 2012.1 common release. > We'll this be fixed in the future? IMO I don't see it as a bug as swif

Re: [Openstack] Essex-4 milestone available for Keystone, Glance, Nova and Horizon

Christian Berendt wrote: > Hi ttx. > > On 03/02/2012 11:18 AM, Thierry Carrez wrote: >> Swift does not follow the common milestones. The latest release is >> 1.4.6, and tha last release available will be included in OpenStack >> 2012.1 common release. > > We'll this be fixed in the future? I wou

Re: [Openstack] Essex-4 milestone available for Keystone, Glance, Nova and Horizon

> On 03/02/2012 11:18 AM, Thierry Carrez wrote: >> Swift does not follow the common milestones. The latest release is >> 1.4.6, and tha last release available will be included in OpenStack >> 2012.1 common release. > > We'll this be fixed in the future? You mean syncing swift with O-S milestones ?

Re: [Openstack] eventlet weirdness

In our experience (running clusters of several hundred nodes) the DB performance is not generally the significant factor, so making its calls non-blocking gives only a very small increase in processing capacity and creates other side effects in terms of slowing all eventlets down as they wait

Re: [Openstack] Essex-4 milestone available for Keystone, Glance, Nova and Horizon

Hi ttx. On 03/02/2012 11:18 AM, Thierry Carrez wrote: > Swift does not follow the common milestones. The latest release is > 1.4.6, and tha last release available will be included in OpenStack > 2012.1 common release. We'll this be fixed in the future? Bye, Christian. -- Christian Berendt Linu

Re: [Openstack] Essex-4 milestone available for Keystone, Glance, Nova and Horizon

Alexey Eromenko wrote: >> https://launchpad.net/keystone/essex/essex-4 >> https://launchpad.net/glance/essex/essex-4 >> https://launchpad.net/nova/essex/essex-4 >> https://launchpad.net/horizon/essex/essex-4 > > Great news, indeed ! > > I would like to ask about "openstack-manuals-M4" and "swift-

Re: [Openstack] problem with uploading virtual image

Hi Mahdi,how did you set them ? Via env variables or into your bashrc (or any sourceable file)Thanks Nuage & Co - Razique Mahroua razique.mahr...@gmail.com Le 2 mars 2012 à 09:39, Mahdi Njim a écrit :Hi I want to upload an image to openstack, but even after I set the proper credentials, when I use

[Openstack] problem with uploading virtual image

Hi I want to upload an image to openstack, but even after I set the proper credentials, when I use uec-publish-tarball I this error message: cert must be specified. private key must be specified. user must be specified. ec2cert must be specified. when I tape euca-describe-image or nova list it work