Re: [Openstack] Bug fixes and test cases submitted against stable/diablo

<> Hi Mark, Thank you for your sharing discussion. # hmm, If I could create new instance of me, problem will be fixed. I understand your point. Stop QAing stable/diablo and focus on Essex. Ideally, we should focus on upstream branch. Ideally, we can start use the code after release out. Howeve

Re: [Openstack] Bug fixes and test cases submitted against stable/diablo

Hi Mark Thank you for your sharing discussion. # hmm, If I could create new instance of me, problem will be fixed. I understand your point. Stop QAing stable/diablo and focus on Essex. Ideally, we should focus on upstream branch. Ideally, we can start use the code after release out. However the

Re: [Openstack] Bug fixes and test cases submitted against stable/diablo

Hi Mark Thank you for your sharing discussion. # hmm, If I could create new instance of me, problem will be fixed. I understand your point. Stop QAing stable/diablo and focus on Essex. Ideally, we should focus on upstream branch. Ideally, we can start use the code after release out. However the

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

Hi Joe - Here are some additional responses and comments inlineŠ On 10/25/11 3:48 PM, "Joseph Heck" wrote: > >On Oct 25, 2011, at 12:54 PM, Jesse Andrews wrote: > >> I'm not an expert ... adding some comments >> >> On Tue, Oct 25, 2011 at 12:05 PM, Joseph Heck wrote: >>> I've just dropped in

[Openstack] Openstack in GIS

anyone have glue with GIS here? can u share ur work related to GIS i am in middle of FOSS4G conference in osaka/tokyo -- Frans Thamura (曽志胜) Chief of Advisory Meruvian. Integrated Hypermedia Java Solution Provider. Mobile: +628557888699 Blog: http://blogs.mervpolis.com/roller/flatburger (id) FB

Re: [Openstack] the format of disk.local

Hi, You should to modify nova.virt.libvirt.connection._create_image. This is source code about make a local disk. 959 local_gb = inst['local_gb'] 960 if local_gb and not self._volume_in_mapping( 961 self.default_local_device, block_device_info): 962 fn

[Openstack] Draft API specifications

Hi all - We have three projects that need to have draft API docs (for a new API version) published for feedback and consumption during the Essex timeframe. (Quantum 1.0>1.1, Glance 1.1>2.0, and Nova 1.1>2.1) I'd like to get ideas about where those should be published and some of the requirements

[Openstack] Nova Reviews!

Hey Nova Core. It is that time again. We've fallen behind on reviews. I know everyone is extremely busy, but we can't make progress on merging patches if we don't have people doing reviews. Here are the stats on the number of different change sets each person in nova core has reviewed in the

Re: [Openstack] Nova EC2 API Team

I'd also recommend documenting the version of the EC2 API supported by the project. That can then become a reference for a true standard, instead of the moving non-standard from AWS. -George On Nov 8, 2011, at 3:38 PM, Chuck Short wrote: > Hi, > > At the last Openstack Design Summit we had a

[Openstack] Nova EC2 API Team

Hi, At the last Openstack Design Summit we had a session about how we can take care of the EC2 API more affectively. One of the outcomes of this session was to create an EC2 API team, that will help take care of the EC2 API in Nova. Today I would like to announce the formation of the Nova EC2 API

Re: [Openstack] dashboard running error since of "NameError: name '_' is not defined" in glance code

FYI, this is a duplicate of this bug: https://bugs.launchpad.net/bugs/885529 The fix for the bug is under review. Cheers! -jay 2011/11/8 Joseph Heck : > That's almost always a reference to gettext - the module used for > internationalization. In this case, it's a bug where accessing that method

Re: [Openstack] [Openstack-poc] proposal for policy around and management of client libraries

On 11/08/2011 09:03 AM, John Dickinson wrote: > > On Nov 8, 2011, at 10:54 AM, Thierry Carrez wrote: >> >> With solution (2), if you look at the issue from Gerrit, GitHub, >> Launchpad or Jenkins, those will be separate projects though. The >> fact that they share the same PTL is not enough to

Re: [Openstack] [Openstack-poc] proposal for policy around and management of client libraries

John Dickinson wrote: > > On Nov 8, 2011, at 10:54 AM, Thierry Carrez wrote: >> >> With solution (2), if you look at the issue from Gerrit, GitHub, >> Launchpad or Jenkins, those will be separate projects though. The fact >> that they share the same PTL is not enough to make them "one". For >> exa

Re: [Openstack] dashboard running error since of "NameError: name '_' is not defined" in glance code

That's almost always a reference to gettext - the module used for internationalization. In this case, it's a bug where accessing that method isn't also getting a few lines that import gettext lined up into it. import gettext gettext.install("glance", unicode=1) I've filed it for you as bug 8876

[Openstack] Bug fixes and test cases submitted against stable/diablo

Hi Nati (Restarting our offline discussion here ...) I see you've proposed a stack of changes to Nova. Nice work! Kudos! https://review.openstack.org/#q,status:open+project:openstack/nova+branch:stable/diablo+owner:nati,n,z However, they shouldn't be submitted against the stable/diablo branc

Re: [Openstack] [Openstack-poc] proposal for policy around and management of client libraries

On Nov 8, 2011, at 10:54 AM, Thierry Carrez wrote: > > With solution (2), if you look at the issue from Gerrit, GitHub, > Launchpad or Jenkins, those will be separate projects though. The fact > that they share the same PTL is not enough to make them "one". For > example, they will have separate

Re: [Openstack] [Openstack-poc] proposal for policy around and management of client libraries

Monty Taylor wrote: > > On 11/08/2011 01:55 AM, Thierry Carrez wrote: >> There are two ways of doing this. >> >> 1. You can include the client code in the main core project, and produce >> two tarballs from it (one project, two release deliverables) much like >> what we'll need to do for Horizon (

Re: [Openstack] [Openstack-poc] proposal for policy around and management of client libraries

On 11/08/2011 01:55 AM, Thierry Carrez wrote: > There are two ways of doing this. > > 1. You can include the client code in the main core project, and produce > two tarballs from it (one project, two release deliverables) much like > what we'll need to do for Horizon (django module + ref impl).

Re: [Openstack] [Openstack-poc] proposal for policy around and management of client libraries

On 11/08/2011 08:13 AM, Dan Wendlandt wrote: > > > On Tue, Nov 8, 2011 at 1:55 AM, Thierry Carrez > wrote: > > There are two ways of doing this. > > 1. You can include the client code in the main core project, and produce > two tarballs from it (one

Re: [Openstack] [Openstack-poc] proposal for policy around and management of client libraries

On Tue, Nov 8, 2011 at 1:55 AM, Thierry Carrez wrote: > There are two ways of doing this. > > 1. You can include the client code in the main core project, and produce > two tarballs from it (one project, two release deliverables) much like > what we'll need to do for Horizon (django module + ref i

Re: [Openstack] Weird behaviour regarding nova image-create

It is linux problem, it never sync the same time and return just write into system cache. But FreeBSD does not ,so I like BSD :) 非淡泊無以明志，非寧靜無以致遠 On Nov 8, 2011, at 11:15 PM, Razique Mahroua wrote: > Thanks to praefect, > I figured that was related to the pending I/O > > so before creating th

Re: [Openstack] Weird behaviour regarding nova image-create

Thanks to praefect, I figured that was related to the pending I/O so before creating the image, into the instance, run a $ sync which forces the pending I/O to be written to disk The novaclient dev. did an awesome job to make it possible so easily , compared to the old way (euca-bundle; etc

[Openstack] Weird behaviour regarding nova image-create

Hi guys, looks like a gremlins is living into my instance. I'm playing with the creation-from-a-running-instance image. Better than explanations : instance: $ ls g01-static-tests.sh pouet razique ssh-host-dss-key.pub ssh-host-rsa-key.pub ssh_key_gen.sh

[Openstack] Reminder: OpenStack team meeting - 21:00 UTC [!]

Hello everyone, Our general meeting will take place at 21:00 UTC this Tuesday in #openstack-meeting on IRC. PTLs, if you can't make it, please name a substitute on [2]. We shall branch essex-1 at the end of the day, so most of the focus will be on identifying essex-1-blocking stuff. With the US

[Openstack] Does live migration/ block-migration works with Diablo

Hi guys, It looks like the HA migration doesn't work at all, I've setup the shared storage, here are the logs : http://paste.openstack.org/show/3157/ Part 1 : the host which runs the instance Part2 : the host which should receive the instance I use qemu on both servers, and migration is impleme

Re: [Openstack] [Openstack-poc] proposal for policy around and management of client libraries

There are two ways of doing this. 1. You can include the client code in the main core project, and produce two tarballs from it (one project, two release deliverables) much like what we'll need to do for Horizon (django module + ref impl). 2. You can add the new client project as a separate core

[Openstack] the format of disk.local

hi all if i create an instance flavor of m1.large(4u,8GRAM.80G disk),at floder here /var/lib/nova/instances/instance-006 will have two img：disk and disk.local they format is same，qcow2 or raw what i want is the "disk" (instance os disk) format is qcow2,and the disk.local's format is raw,beca