Re: [openstack-dev] [Infra][Solum][Mistral] New class of requirements for Stackforge projects

Ok, I submitted and abandoned a couple of reviews[1][2] for a solution aimed to meet my goals without adding a new per-project requirements file. The flaw with this approach is that pip may install other requirements when installing the one(s) loaded from the fallback mirror, and those may conf

Re: [openstack-dev] [Neutron ML2] Potential DB lock when developing new mechanism driver

Hi, I'm trying this code and I can't get it to throw that exception. How are you triggering it? See my code here: https://review.openstack.org/#/c/102715/1/neutron/plugins/ml2/drivers/mech_bigswitch/driver.py On Wed, Jun 25, 2014 at 8:49 PM, Li Ma wrote: > Sorry, I was thought that the code w

[openstack-dev] [nova][vmwareapi] minesweeper status

Hi Folks - Minesweeper ran into some trouble about a week ago with some checkins on tempest, devstack, and some internal issues. We were down off and on for a week - mostly off. Going forward I'll be more proactive about informing you all of these types of issues. Currently minesweeper is up

Re: [openstack-dev] [cinder][volume/manager.py] volume driver mapping

This seems cool. Does it mean the storage vendors write their new drivers & just map it from cinder.conf ? Does it involve any changes to devstack as well ? Regards, Amit *CloudByte Inc.* On Wed, Jun 25, 2014 at 7:22 PM, Duncan Thomas wrote: > That's easy; you don

Re: [openstack-dev] [QA] Questions about test policy for scenario test

There's a spec in progress related to this, I'd love to see your comments in there: https://review.openstack.org/#/c/94741/ Andrea Sent from my tiny device Daryl Walleck wrote I really like this option, especially if it leaves a generic hook available for validation. This could a

Re: [openstack-dev] [Keystone] Token invalidation in deleting role assignments

Dolph, Thank you so much. I understand that using OS-REVOKE Extension will solve these issues. Regards, Takashi Natsume NTT Software Innovation Center Tel: +81-422-59-4399 E-mail: natsume.taka...@lab.ntt.co.jp From: Dolph Mathews [mailto:dolph.math...@gmail.com] Sent: Thursday, June 26, 2014 12

Re: [openstack-dev] [Openstack] How can I enable operation for non-admin user

Hi Chen, > I’m not an experienced developer, so , could you explain more about > “Perhaps the live_migrate task is passing the incorrect context in for > this database query?” ? > Sorry, I should have clarified that that question was for the developers *out there*. (cc's the dev list now). I'm n

[openstack-dev] [sahara] team meeting June 26 1800 UTC

Hi folks, We'll be having the Sahara team meeting as usual in #openstack-meeting-alt channel. Agenda: https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meeting&iso=20140626T18 -- Sincerely yours, Sergey Lukjanov

Re: [openstack-dev] [QA] Questions about test policy for scenario test

I really like this option, especially if it leaves a generic hook available for validation. This could allow for different types of compute validators such as hypervisor specific or 3rd party compute validators to be implemented. From: Fei Long Wang mailto:feil...@catalyst.net.nz>> Reply-To: "Op

Re: [openstack-dev] [Neutron] DVR SNAT shortcut

Another approach would be to use a single IP address per router per compute node. This avoids the multi-tenant issue mentioned above, at the cost of consuming more IP addresses, potentially one default SNAT IP address for each VM on the compute server (which is the c

Re: [openstack-dev] [Neutron ML2] Potential DB lock when developing new mechanism driver

Sorry, I was thought that the code was straightforward to understand. I can explain what I wanna do. I try to use postcommit to dynamically set some specific port attribute into port binding when a certain port is created. So, I write an example to see whether it is working or not. But, def cre

Re: [openstack-dev] Creating new python-client

On Wed, Jun 25, 2014 at 10:18 PM, Aaron Rosen wrote: > I'm looking at creating a new python-client and I was > wondering if there was any on going effort to share code between the > clients or not? I've looked at the code in python-novaclient and > python-neutronclient and both of them seem to ha

Re: [openstack-dev] Creating new python-client

On Wed, Jun 25, 2014 at 10:18 PM, Aaron Rosen wrote: > Hi, > > I'm looking at creating a new python-client and I was > wondering if there was any on going effort to share code between the > clients or not? I've looked at the code in python-novaclient and > python-neutronclient and both of them se

[openstack-dev] Creating new python-client

Hi, I'm looking at creating a new python-client and I was wondering if there was any on going effort to share code between the clients or not? I've looked at the code in python-novaclient and python-neutronclient and both of them seem to have their own homegrown HTTPClient and keystone integration

[openstack-dev] [Neutron]One security issue about floating ip

Hi folks, After we create an SSH connection to a VM via its floating ip, even though we have removed the floating ip association, we can still access the VM via that connection. Namely, SSH is not disconnected when the floating ip is not valid. Any good solution about this security issue? Thanks

Re: [openstack-dev] [Neutron][Swift][third-party] Most Third Party CI's failing

On Wed, Jun 18, 2014 at 12:22 PM, Kashyap Chamarthy wrote: > On Sat, Jun 14, 2014 at 09:39:50PM -0700, Sukhdev Kapur wrote: > > Oppss...sorry wrong link... please use this > > http://paste.openstack.org/show/84073/. > > Just a friendly note -- pastebins usually expire, and if someone looks > at t

[openstack-dev] [Neutron]VM associated with two ports caused by HTTP request resending

Hi folks, When we create many VMs at the same time (more than 100 VMs), Neutron server will be busy handling port creation requests sent by Nova via HTTP. One issue we met was that HTTP request timed out because Neutron didn't response in time, the same HTTP request was sent again and finally VM w

Re: [openstack-dev] Virtual Interface creation failed

The link does not work for me! Edgar From: "tfre...@redhat.com" mailto:tfre...@redhat.com>> Organization: Red Hat Reply-To: "tfre...@redhat.com" mailto:tfre...@redhat.com>>, "OpenStack Development Mailing List (not for usage questions)" ma

Re: [openstack-dev] [Infra][Solum][Mistral] New class of requirements for Stackforge projects

On Jun 26, 2014 12:12 PM, "Angus Salkeld" wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 25/06/14 15:13, Clark Boylan wrote: > > On Tue, Jun 24, 2014 at 9:54 PM, Adrian Otto wrote: > >> Hello, > >> > >> Solum has run into a constraint with the current scheme for requirements ma

Re: [openstack-dev] [Barbican] Barebones CA

On 06/25/2014 02:42 PM, Clark, Robert Graham wrote: > > Ok, I’ll hack together a dev plugin over the next week or so, other work > notwithstanding. Where possible I’ll probably borrow from the dog tag > plugin as I’ve not looked closely at the plugin infrastructure in Barbican > recently. My un

Re: [openstack-dev] [swift] [trove] Configuration option descriptions

On Wed, Jun 25, 2014 at 7:32 PM, Nikhil Manchanda wrote: > > Hi Anne: > > Thanks for bringing this to our attention! This is definitely something > that we need to fix. > > I've filed https://bugs.launchpad.net/trove/+bug/1334465 to track this > issue, and I'm hoping we'll be able to get to it du

Re: [openstack-dev] [Neutron ML2] Potential DB lock when developing new mechanism driver

What is in the variable named 'query' that you are trying to merge into the session? Can you include the full create_port_postcommit method? The line raising the exception ends with "{'port_id': port_id})" and that doesn't matching anything included in your sample. On Wed, Jun 25, 2014 at 6:53 PM

Re: [openstack-dev] Fwd: [nova] How can I obtain compute_node_id in nova

Thx! I will pay close attension to this patch. On Wed, Jun 25, 2014 at 11:59 PM, Sylvain Bauza wrote: > Hi Afe, > > Le 25/06/2014 12:01, afe.yo...@gmail.com a écrit : > > Any help will be greatly appreciated! > > -- Forwarded message -- > From: afe.yo...@gmail.com > Date: W

Re: [openstack-dev] [Infra][Solum][Mistral] New class of requirements for Stackforge projects

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 25/06/14 15:13, Clark Boylan wrote: > On Tue, Jun 24, 2014 at 9:54 PM, Adrian Otto > wrote: >> Hello, >> >> Solum has run into a constraint with the current scheme for requirements >> management within the OpenStack CI system. We have a proposal

[openstack-dev] Fwd: [Openstack] Glance - and the use of the "project_id:%(project_id)" rule

? -- Forwarded message -- From: Michael Hearn Date: Fri, May 2, 2014 at 9:21 AM Subject: [Openstack] Glance - and the use of the "project_id:%(project_id)" rule To: "openst...@lists.openstack.org" Having played with the policies and rules within glance's policy.json file I have

Re: [openstack-dev] [Neutron ML2] Potential DB lock when developing new mechanism driver

Here's a code sample which can raise db lock wait exception: def create_port_postcommit(self, context): port_id = ... with session.begin(subtransactions=True): try: binding = (session.query(models.PortBinding). filter(models.PortBinding.port_id.startswith(port_id)).

Re: [openstack-dev] [Neutron] DVR SNAT shortcut

On Wed, Jun 25, 2014 at 10:29 PM, McCann, Jack wrote: > > >> If every compute node is > > >> assigned a public ip, is it technically able to improve SNAT packets > > >> w/o going through the network node ? > > It is technically possible to implement default SNAT at the compute node. > > One appro

Re: [openstack-dev] [swift] [trove] Configuration option descriptions

Hi Anne: Thanks for bringing this to our attention! This is definitely something that we need to fix. I've filed https://bugs.launchpad.net/trove/+bug/1334465 to track this issue, and I'm hoping we'll be able to get to it during juno-2 (or beginning of juno-3 at the latest). Once we've got a pa

Re: [openstack-dev] [QA] Questions about test policy for scenario test

Good to know. I think it's a good idea to implement a common compute verifier after instances booted. Maybe we can define different checking levels so that it can be leveraged by different test cases. I will see what I can do. On 24/06/14 22:27, Sean Dague wrote: > On 06/24/2014 01:29 AM, Fei Long

[openstack-dev] [Neutron][LBaaS] Weekly Standup

Hey LBaaS folks, This is your friendly reminder to update the weekly standup etherpad so that everyone is aware of what everyone is working on. Here is the link ==> https://etherpad.openstack.org/p/neutron-lbaas-weekly-standup. Thanks! Cheers, --Jorge __

Re: [openstack-dev] [Nova] Spec Review Day Today!

On 06/25/2014 05:23 AM, John Garbutt wrote: > As previously (quietly) announced, today we are trying to do a push on > nova-specs reviews. > > https://review.openstack.org/#/q/status:open+project:openstack/nova-specs,n,z > > The hope is we get through some of the backlog, with some interactive >

Re: [openstack-dev] [Barbican] Barebones CA

Ok, I’ll hack together a dev plugin over the next week or so, other work notwithstanding. Where possible I’ll probably borrow from the dog tag plugin as I’ve not looked closely at the plugin infrastructure in Barbican recently. Is this something you’d like a blueprint for first? -Rob On 25/0

Re: [openstack-dev] [Neutron][QA] Enabling full neutron Job

On Tue, Jun 24, 2014 at 02:14:16PM +0200, Salvatore Orlando wrote: > There is a long standing patch [1] for enabling the neutron full job. > Little before the Icehouse release date, when we first pushed this, the > neutron full job had a failure rate of less than 10%. However, since has > come by,

Re: [openstack-dev] [Neutron ML2] Potential DB lock when developing new mechanism driver

I'm not sure what you mean about it being 'truly committed' even though the transaction has ended. When would it be committed? There are not more calls to sqlalchemy after that. The only way it wouldn't be committed is if another transaction was started before calling create_port. Regardless, a db

[openstack-dev] [Horizon][Sahara] Question about PanelGroups and Panels in subdirectories of a given dashboard

Here is the scenario: We are looking to merge the Sahara (Data Processing) dashboard into horizon. The 9 panels will live in a PanelGroup under "Project" called "Data Processing". In the spirit of code organization, it was suggested that I put all 9 of the data processing panels into a subdir

Re: [openstack-dev] [Nova] 0 byte image is created with instance snapshot if instance is booted using volume

This sounds like something which should be reported as a bug. You do that at https://bugs.launchpad.net/nova/+filebug Cheers, Michael On Thu, Jun 26, 2014 at 1:43 AM, Agrawal, Ankit wrote: > Hi All, > > > > When I boot an instance from volume and the take snapshot of that instance > it creates a

Re: [openstack-dev] [nova] tempest failure on image creation time out

On Wed, Jun 25, 2014 at 4:16 PM, Manickam, Kanagaraj < kanagaraj.manic...@hp.com> wrote: > > > While building the patch in Jenkins, following exception reported in > tempest. > > > > > > 2014-06-25 19:09:19.009 >

[openstack-dev] [nova] tempest failure on image creation time out

While building the patch in Jenkins, following exception reported in tempest. 2014-06-25 19:09:19.009 | 2014-06-25 19:09:19.010

[openstack-dev] DVR and FWaaS integration

All, During last summit, we were talking about the integration issues between DVR and FWaaS. After the summit, I had one IRC meeting with DVR team. But after that meeting I was tight up with my work and did not get time to continue to follow up the issue. To not slow down the discussion, I'm forwar

Re: [openstack-dev] [Neutron][LBaaS] Should TLS settings for listener be set through separate API/model?

Hi Stephen, The associations table name is consistent with the rest of neutron's table names, as is not breaking the table name words up by an underscore. I think this stems from the sqlalchemy models getting the table name for free because of inheriting from a base model that derives the table

Re: [openstack-dev] Jenkins faillure

Yes, the wrong mailing list. Sorry for the noise. Édouard. On Wed, Jun 25, 2014 at 6:18 PM, Anita Kuno wrote: > On 06/25/2014 12:07 PM, Édouard Thuleau wrote: > > Hi, > > > > I got a jenkins failure on that small fix [1] on OpenContrail. > > Here the last lines console output: > > > > 2014-06-

Re: [openstack-dev] [sahara] Upgrade of Hadoop components inside released version

Team - Please see in-line for my thoughts/opinions on the topic: >> From: Andrew Lazarev >> Subject: [openstack-dev] [sahara] Upgrade of Hadoop components inside >> released version >> Date: June 24, 2014 at 5:20:27 PM EDT >> To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

Le 2014-06-25 14:26, Day, Phil a écrit : -Original Message- From: Sean Dague [mailto:s...@dague.net] Sent: 25 June 2014 11:49 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

Re: [openstack-dev] [cinder][glance] Update volume-image-metadata proposal

From: Brian Rosmaita [mailto:brian.rosma...@rackspace.com] >Or you can just use it as the basis of a Cinder property protection config >file, >because I wonder whether in the general case, you'll always want volume >properties protected exactly the same as image properties. If not, the new >API c

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On Wed, Jun 25, 2014 at 11:26 AM, Day, Phil wrote: > > -Original Message- > > From: Sean Dague [mailto:s...@dague.net] > > Sent: 25 June 2014 11:49 > > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [nova] should we have a stale data > in

Re: [openstack-dev] [hacking] rules for removal

On 06/24/2014 09:51 PM, Steve Kowalik wrote: On 25/06/14 07:26, Mark McLoughlin wrote: There's two sides to this coin - concern about alienating non-english-as-a-first-language speakers who feel undervalued because their language is nitpicked to death and concern about alienating english-as-a-fi

Re: [openstack-dev] [TripleO] [Heat] Reminder: Mid-cycle Meetup - Attendance Confirmation

On 25/06/14 18:20 +, Carlino, Chuck (OpenStack TripleO, Neutron) wrote: Is $179/day the expected rate? Thanks, Chuck Yes, that's the best rate available from both of the downtown (walkable) hotels. -- Jordan O'Mara Red Hat Engineering, Raleigh pgpq2YbXSIITm.pgp Description: PGP signatu

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

> -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: 25 June 2014 11:49 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [nova] should we have a stale data indication in > "nova list/show"? > > On 06/25/2014 04:28 AM, Belm

Re: [openstack-dev] [TripleO] [Heat] Reminder: Mid-cycle Meetup - Attendance Confirmation

Is $179/day the expected rate? Thanks, Chuck On Jun 25, 2014, at 2:34 AM, Jaromir Coufal wrote: > Thanks a lot for your help. > > Just a side note - we need to fill in the number of requested rooms, so that > we don't get charged for extra cost - we have a group discount price. > > So for ev

Re: [openstack-dev] [Barbican] Barebones CA

I think the plan is to create a Dogtag instance so that integration tests can be run whenever code is checked in (both with and without a Dogtag backend). Dogtag isn't that difficult to deploy, but being a Java app, it does bring in a set of dependencies that developers may not want to deal with f

Re: [openstack-dev] [nova] Distributed locking

Could u expand on this and how it would work. I'm pretty skeptical of new ad-hoc locking implementations so just want to ensure it's flushed out in detail. What would the two local locks be, where would they be, what would the 'conducting' being doing to coordinate? -Original Message- Fr

Re: [openstack-dev] [Neutron][LBaaS] Consolidated metrics proposal

Hey Andres, Sorry for the late reply. I was out of town all last week. I would suggest continuing the email thread before we put this on a wiki somewhere so others can chime in. Cheers, --Jorge From: , Andres mailto:andres.buras...@intel.com>> Reply-To: "OpenStack Development Mailing List (no

Re: [openstack-dev] [TripleO] Use MariaDB by default on Fedora

On 06/16/2014 11:14 PM, Clint Byrum wrote: Excerpts from Gregory Haynes's message of 2014-06-16 14:04:19 -0700: Excerpts from Jan Provazník's message of 2014-06-16 20:28:29 +: Hi, MariaDB is now included in Fedora repositories, this makes it easier to install and more stable option for Fedo

Re: [openstack-dev] [Barbican] Barebones CA

Rob, RedHat is working on a backend for Dogtag, which should be capable of doing something like that. That's still a bit hard to deploy, so it would make sense to extend the 'dev' plugin to include those features. Jarret On 6/24/14, 4:04 PM, "Clark, Robert Graham" wrote: >Yeah pretty much. >

[openstack-dev] [qa][infra] etherpad on elastic-recheck testing improvements

Sean asked me to jot some thoughts down on how we can automate some of our common review criteria for elastic-recheck queries, so that's here: https://etherpad.openstack.org/p/elastic-recheck-testing There is some low-hanging-fruit in there I think, but the bigger / more useful change is actua

Re: [openstack-dev] Jenkins faillure

On 06/25/2014 12:07 PM, Édouard Thuleau wrote: > Hi, > > I got a jenkins failure on that small fix [1] on OpenContrail. > Here the last lines console output: > > 2014-06-25 07:02:55 > RunUnitTest(["build/debug/bgp/rtarget/test/rtarget_table_test.log"], > ["build/debug/bgp/rtarget/test/rtarget_tab

[openstack-dev] Jenkins faillure

Hi, I got a jenkins failure on that small fix [1] on OpenContrail. Here the last lines console output: 2014-06-25 07:02:55 RunUnitTest(["build/debug/bgp/rtarget/test/rtarget_table_test.log"], ["build/debug/bgp/rtarget/test/rtarget_table_test"]) 2014-06-25 07:02:56 /home/jenkins/workspace/ci-contr

Re: [openstack-dev] Fwd: [nova] How can I obtain compute_node_id in nova

Hi Afe, Le 25/06/2014 12:01, afe.yo...@gmail.com a écrit : > Any help will be greatly appreciated! > > -- Forwarded message -- > From: *afe.yo...@gmail.com * > mailto:afe.yo...@gmail.com>> > Date: Wed, Jun 25, 2014 at 5:53 PM > Subject: [nova] How can I

[openstack-dev] [Nova] 0 byte image is created with instance snapshot if instance is booted using volume

Hi All, When I boot an instance from volume and the take snapshot of that instance it creates a volume snapshot and also an image of 0 byte. I can boot a new instance using this 0 byte image, but I am not sure why this image with 0 byte is created here? Can someone please help me to understand

Re: [openstack-dev] [Keystone] Token invalidation in deleting role assignments

This is a known limitation of the token backend and the token revocation list: we don't index tokens in the backend by roles (and we don't want to iterate the token table to find matching tokens). However, if we land support for token revocation events [1] in the auth_token [2] middleware, we'll b

[openstack-dev] [swift] [trove] Configuration option descriptions

Hi swift and trove devs, In working on our automation to document the configuration options across OpenStack, we uncovered a deficit in both trove and swift configuration option descriptions. Here's an example: http://docs.openstack.org/trunk/config-reference/content/container-sync-realms-configur

Re: [openstack-dev] Tripleo, Ironic, the SSH power driver, paramiko and eventlet fun.

Awesome news! Chris On Wed, Jun 25, 2014 at 3:23 AM, wrote: > On Tue, 24 Jun 2014, j...@ioctl.org wrote: > > > There's a bug on this: > > https://bugs.launchpad.net/ironic/+bug/1321787?comments=all > > > We've got a potential eventlet fix here: > > https://github.com/jan-g/eventlet/tree/

Re: [openstack-dev] [Neutron] One performance issue about VXLAN pool initiation

Hi everyone, A new change (https://review.openstack.org/101982) has been proposed to improve vxlan pool initiation with an improvement on delete of obsolete unallocated vnis using a unique delete SQL command. I've tested performance with the following (delete only) scenario: vxlan range is change

Re: [openstack-dev] [Openstack] [nova] How can I obtain compute_node_id in nova

You should probably email the openstack-dev mailing list (openstack-dev@lists.openstack.org) or better yet, ask for help in #openstack-nova on IRC. Regards, Steve Martinelli Software Developer - Openstack Keystone Core Member Phone: 1-905-413-2851 E-mail: steve...@ca.ibm.com 8200 Warden Ave

[openstack-dev] [OSSG][OSSN] Nova Network configuration allows guest VMs to connect to host services

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nova Network configuration allows guest VMs to connect to host services - --- ### Summary ### When using Nova Network to manage networking for compute instances, instances are able to reach network services running on the host system. This may be a se

Re: [openstack-dev] [Neutron] DVR SNAT shortcut

> >> If every compute node is > >> assigned a public ip, is it technically able to improve SNAT packets > >> w/o going through the network node ? It is technically possible to implement default SNAT at the compute node. One approach would be to use a single IP address per compute node as a defaul

Re: [openstack-dev] [Keystone] Announcing Keystone Middleware Project

On Wed, Jun 25, 2014 at 6:56 AM, Sergey Lukjanov wrote: > Are there any API changes that will make projects need to fix? > > There aren't any API changes. The code was just copy-pasted to the new package. The changes to the projects are just 1) update the requirements and 2) change the auth_token

[openstack-dev] [QA] Meeting Thursday June 26th at 22:00 UTC

Hi everyone, Just a quick reminder that the weekly OpenStack QA team IRC meeting will be tomorrow Thursday, June 26th at 22:00 UTC in the #openstack-meeting channel. The agenda for tomorrow's meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to ad

Re: [openstack-dev] [cinder][volume/manager.py] volume driver mapping

That's easy; you don't. The mappings are their because we moved some drivers round during a code cleanup and didn't want old config files to break during an upgrade. The old names have been deprecated since Falsom and finally now removed; new drivers don't need to do any mapping at all. On 25 June

Re: [openstack-dev] [Neutron] validation of input against column-size specified in schema

On Jun 25, 2014, at 12:26 AM, Manish Godara wrote: > Hi, > > Is there any way in current neutron codebase that can be used to validate > the length of a string attribute against the max column size specified in > the schema for that attribute. > > E.g. , in models_v2.py > > class Network(model

Re: [openstack-dev] [cinder][glance] Update volume-image-metadata proposal

Thanks for the response, I'll be there this Thursday. Having the file in more than one place could me a nightmare if we have to maintain consistency between them. It could be good if we want to protect different properties than Glance. Thanks, Facundo From: Brian Rosmaita [mailto:brian.rosma...

Re: [openstack-dev] [neutron][nova] nova needs a new release of neutronclient for OverQuotaClient exception

On Tue, Jun 24, 2014 at 10:32 PM, Angus Lees wrote: > On Tue, 24 Jun 2014 02:46:33 PM Kyle Mestery wrote: >> On Mon, Jun 23, 2014 at 11:08 AM, Kyle Mestery >> >> wrote: >> > On Mon, Jun 23, 2014 at 8:54 AM, Matt Riedemann >> > >> > wrote: >> >> There are at least two changes [1][2] proposed to N

[openstack-dev] [cinder][volume/manager.py] volume driver mapping

Hi All, I am observing a bit difference in manager.py file between these branches stable/icehouse and master. In stable/icehouse various driver mapped in manager.py but it is not in master. Please guide me, where i have to map my driver. *Thanks & Regards*, Yogesh Prasad. _

Re: [openstack-dev] [containers][nova][cinder] Cinder support in containers and unprivileged container-in-container

> > > I’m reasonably sure that nobody wants to intentionally relax compute host > security in order to add this new functionality. Let’s find the right short > term and long term approaches > >From our discussions, one approach that seemed popular for long-term support was to find a way to gracefu

Re: [openstack-dev] [hacking] rules for removal

On 06/25/2014 07:53 AM, Martin Geisler wrote: > Sean Dague writes: > >> On 06/25/2014 03:56 AM, Martin Geisler wrote: >>> >>> In the Mercurial project we accept contributions sent as patches >>> only. There it's common for the core developers to fix the commit >>> message locally before importing

Re: [openstack-dev] [hacking] rules for removal

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 25/06/14 12:59, Sean Dague wrote: > On 06/25/2014 03:56 AM, Martin Geisler wrote: >> Mark McLoughlin writes: >> >>> On Tue, 2014-06-24 at 13:56 -0700, Clint Byrum wrote: Excerpts from Mark McLoughlin's message of 2014-06-24 12:49:52 -0

Re: [openstack-dev] [Keystone] Announcing Keystone Middleware Project

Are there any API changes that will make projects need to fix? On Wed, Jun 25, 2014 at 7:25 AM, Morgan Fainberg wrote: > I expect that we will be releasing the 1.0.0 shortly here (or at the very > least an alpha so we can move forward) to make sure we have time get the new > package in use during

[openstack-dev] [devstack][Manila][docs] Setting up Devstack with Manila on Fedora 20

Hi List, I have created a new wikipage with the goal to document the steps needed to setup DevStack with Manila on F20. Added some troubleshooting tips based on my experience. https://wiki.openstack.org/wiki/Manila/docs/Setting_up_DevStack_with_Manila_on_Fedora_20 Pls have a look and provide

Re: [openstack-dev] [hacking] rules for removal

Sean Dague writes: > On 06/25/2014 03:56 AM, Martin Geisler wrote: >> >> In the Mercurial project we accept contributions sent as patches >> only. There it's common for the core developers to fix the commit >> message locally before importing a patch. That makes it quick to fix >> these problems

Re: [openstack-dev] [hacking] rules for removal

On 06/25/2014 03:56 AM, Martin Geisler wrote: > Mark McLoughlin writes: > >> On Tue, 2014-06-24 at 13:56 -0700, Clint Byrum wrote: >>> Excerpts from Mark McLoughlin's message of 2014-06-24 12:49:52 -0700: >>> >>> However, there is a debate, and thus I would _never_ block a patch >>> based on this

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On 06/25/2014 04:28 AM, Belmiro Moreira wrote: > I like the current behavior of not changing the VM state if nova-compute > goes down. > > The cloud operators can identify the issue in the compute node and try > to fix it without users noticing. Depending in the problem I can inform > users if in

[openstack-dev] [Trove] Meeting Wednesday, 25 June @ 1800 UTC

Just a quick reminder for the weekly Trove meeting. https://wiki.openstack.org/wiki/Meetings#Trove_.28DBaaS.29_meeting Date/Time: Wednesday, 25 June - 1800 UTC / 1100 PDT / 1300 CDT IRC channel: #openstack-meeting-alt The Meeting Agenda can be found at https://wiki.openstack.org/wiki/Meetings/Tro

Re: [openstack-dev] [Neutron] DVR SNAT shortcut

On Wed, Jun 25, 2014 at 5:42 PM, Yongsheng Gong wrote: > Hi, > for each compute node to have SNAT to Internet, I think we have the > drawbacks: > 1. SNAT is done in router, so each router will have to consume one public IP > on each compute node, which is money. SNAT can save more ips than wasted

Re: [openstack-dev] [Murano] environment deletion

Hi Steve, The initial implementation of environment deletion (before 'destroy' method was introduced in MuranoPL) was to deploy environment with empty application list. So the code that deletes Heat stack was in 'deploy'. And it is still there. Environment's 'destroy' will be executed only in case

Re: [openstack-dev] Tripleo, Ironic, the SSH power driver, paramiko and eventlet fun.

On Tue, 24 Jun 2014, j...@ioctl.org wrote: > There's a bug on this: > https://bugs.launchpad.net/ironic/+bug/1321787?comments=all We've got a potential eventlet fix here: https://github.com/jan-g/eventlet/tree/wip ... testing it now. Certainly seems hopeful in the face of a 'multiple threa

Re: [openstack-dev] [Neutron ML2] Potential DB lock when developing new mechanism driver

Hi Kevin, Thanks for your reply. Actually, it is not that straightforward. Even if postcommit is outside the 'with' statement, the transaction is not 'truly' committed immediately. Because when I put my db code (reading and writing ml2-related tables) in postcommit, db lock wait exception is sti

Re: [openstack-dev] [Nova] [ironic]nova scheduler and ironic

I think there’s a bit more to it that just having an aggregate: - Ironic provides its own version of the Host manager class for the scheduler, I’m not sure if that is fully compatible with the non-ironic case. Even in the BP for merging the Ironic driver back into Nova it still looks

Re: [openstack-dev] [nova] Why is there a 'None' task_state between 'SCHEDULING' & 'BLOCK_DEVICE_MAPPING'?

Looking at this a bit deeper the comment in _start_buidling() says that its doing this to “Save the host and launched_on fields and log appropriately “. But as far as I can see those don’t actually get set until the claim is made against the resource tracker a bit later in the process, so thi

Re: [openstack-dev] [DevStack] neutron config not working

On Wed, Jun 25, 2014 at 01:36:02PM +0530, Kashyap Chamarthy wrote: > On Tue, Jun 24, 2014 at 06:59:17PM -0400, Rob Crittenden wrote: [. . .] > Examining my install log[2], I only see 3 ERRORs that looked legitimate: > > (1) A fatal error about 'yaml.h' header file not found: > ---

[openstack-dev] Fwd: [nova] How can I obtain compute_node_id in nova

Any help will be greatly appreciated! -- Forwarded message -- From: afe.yo...@gmail.com Date: Wed, Jun 25, 2014 at 5:53 PM Subject: [nova] How can I obtain compute_node_id in nova To: openst...@lists.openstack.org I found a bug recently and reported it here https://bugs.launchp

Re: [openstack-dev] [Neutron] DVR SNAT shortcut

Hi, for each compute node to have SNAT to Internet, I think we have the drawbacks: 1. SNAT is done in router, so each router will have to consume one public IP on each compute node, which is money. 2. for each compute node to go out to Internet, the compute node will have one more NIC, which connec

Re: [openstack-dev] [nova] Do any hyperviors allow disk reduction as part of resize ?

On 24 June 2014 16:40, Jay Pipes wrote: > On 06/24/2014 07:32 AM, Daniel P. Berrange wrote: >> >> On Tue, Jun 24, 2014 at 10:55:41AM +, Day, Phil wrote: -Original Message- From: John Garbutt [mailto:j...@johngarbutt.com] Sent: 23 June 2014 10:35 To: OpenStack D

Re: [openstack-dev] [Fuel] [OSTF] OSTF stops working after password is changed

It is possible to change everything so username, password and tenant fields Also this way we will be able to run tests not only as admin user On Wed, Jun 25, 2014 at 12:29 PM, Vitaly Kramskikh wrote: > Dmitry, > > Fields or field? Do we need to provide password only or other credentials > are

Re: [openstack-dev] [nova] Why is there a 'None' task_state between 'SCHEDULING' & 'BLOCK_DEVICE_MAPPING'?

Hi WingWJ, I agree that we shouldn’t have a task state of None while an operation is in progress. I’m pretty sure back in the day this didn’t use to be the case and task_state stayed as Scheduling until it went to Networking (now of course networking and BDM happen in parallel, so you have to

Re: [openstack-dev] [TripleO] [Heat] Reminder: Mid-cycle Meetup - Attendance Confirmation

Thanks a lot for your help. Just a side note - we need to fill in the number of requested rooms, so that we don't get charged for extra cost - we have a group discount price. So for everybody, please, go forward and book your room here: http://tinyurl.com/redhat-marriott -- Jarda On 2014/24/

Re: [openstack-dev] [Fuel] [OSTF] OSTF stops working after password is changed

Dmitry, Fields or field? Do we need to provide password only or other credentials are needed? 2014-06-25 13:02 GMT+04:00 Dmitriy Shulyak : > Looks like we will stick to #2 option, as most reliable one. > > - we have no way to know that openrc is changed, even if some scripts > relies on it - os

Re: [openstack-dev] [Nova] Timeline for the rest of the Juno release

Discussing at the meet-up if fine with me > -Original Message- > From: Michael Still [mailto:mi...@stillhq.com] > Sent: 25 June 2014 00:48 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Nova] Timeline for the rest of the Juno release > >

Re: [openstack-dev] [TripleO] Time to break backwards compatibility for *cloud-password file location?

On 25/06/14 10:52, James Polley wrote: > Until https://review.openstack.org/#/c/83250/, the setup-*-password scripts > used to drop password files into $CWD, which meant that if you ran the > script from a different location next time, your old passwords wouldn't be > found. > > https://review.ope

[openstack-dev] [Nova] Spec Review Day Today!

As previously (quietly) announced, today we are trying to do a push on nova-specs reviews. https://review.openstack.org/#/q/status:open+project:openstack/nova-specs,n,z The hope is we get through some of the backlog, with some interactive chat on IRC in #openstack-nova If someone has better stat

Re: [openstack-dev] [Nova] Timeline for the rest of the Juno release

Seems like we all agree on the basic idea here, which is great. I think just not concentrating on nova-spec reviews is fine, at least, it is the simplest way to implement the freeze (as Russell pointed out). I so worry about setting the right expectations for the poor souls who's specs might stic

  1   2   >