Re: [openstack-dev] [nova][neutron] New BP for live migration with direct pci passthru

Hi, Ian, Thanks a lot for your reply. >In general, while you've applied this to networking (and it's not the first >time I've seen this proposal), the same technique will work with any device - >PF or VF, networking or other: >- notify the VM via an accepted channel that a device is going to be

[openstack-dev] [Octavia] [Tempest] Tempest tests using tempest-plugin

Hi, We are trying to implement tempest tests for Octavia using tempest-plugin. I am wondering whether we can import *tempest* common files and use them as a base to support Octavia tempest tests rather than copying everything in Octavia tree. I am in favor of importing files directly from tempest

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On Sat, Feb 6, 2016 at 2:14 AM, Cody A.W. Somerville < cody.somervi...@gmail.com> wrote: > > I'd like to suggest we tightly scope this discussion and subsequent > decision to Poppy exclusively. The reason for this is two fold. The first > is so that a timely resolution and answer can be

[openstack-dev] Help regarding openstack error to set method value and it's plugin in keystone.conf

Hi, I have to configure openstack as a service provider for SAML authentication ,I am not able to set methods value in keystone.conf, when I am adding saml2 and mapped in methods valuefor saml2 authentication where saml2= "keystone.auth.plugins.saml2.Saml2" mapped =

Re: [openstack-dev] [Neutron] - DVR L3 data plane performance results and scenarios

Hi Swami, Thanks for the reply, is there any detailed links that describe this that we can look at? (Of course that having results without the full setup (hardware/ NIC, CPU and threads for OVS and so on..) details and without the full scenario details is a bit hard, regardless however i hope it

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On Wed, Feb 17, 2016 at 1:20 PM, Jay Pipes wrote: > On 02/17/2016 09:30 AM, Doug Hellmann wrote: > >> Excerpts from Mike Perez's message of 2016-02-17 03:21:51 -0800: >> >>> On 02/16/2016 11:30 AM, Doug Hellmann wrote: >>> So I think the project team is doing everything

Re: [openstack-dev] [nova] A prototype implementation towards the "shared state scheduler"

On 02/17/2016 06:59 AM, Chris Dent wrote: The advantage of a centralized datastore for that information is that it provides administrative control (e.g. reserving resources for other needs) and visibility. That level of command and control seems to be something people really want

[openstack-dev] What's Up, Doc? 19 Feb 2016

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, This week I've been focusing on general housekeeping duties as we prepare to rush headlong into the release. I've cleaned up the blueprints list, and also been burning through the oldest bugs in our queue. I'm very pleased to report

Re: [openstack-dev] [glance]one more use case for Image Import Refactor from OPNFV

Hi, Jay, >From exactly definition, it's not full "independent" concept. The KeyStone services will be distributed into each data center, so if one data center failed, the identity management especially token validation can work still in other data centers. That's one case studied in OPNFV

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 18 February 2016 at 08:41, Sean M. Collins wrote: > This week's update: > > Armando was kind enough to take a look[1], since he's got a fresh > perspective. I think I've been suffering from Target Fixation[1] > where I failed to notice a couple other failures in the logs.

Re: [openstack-dev] [Horizon][Trove][Sahara] Horizon-Trove/Sahara External Repository

Hi, > Horizon still have some things we need to tidy up on our end to make sure we > have full support for testing and localization for external plugins. I am pleased to announce that translations of trove-dashboard and sahara-dashboard now work for the master branch. We have the parity to

Re: [openstack-dev] [glance]one more use case for Image Import Refactor from OPNFV

On 02/18/2016 08:34 PM, joehuang wrote: Hello, Glad to know that the “Image Import Refactor” is the essential BP in Mitaka. One more use case from OPNFV as following: In OPNFV, one deployment scenario is each data center will be deployed with independent OpenStack instance, but shared identity

Re: [openstack-dev] [all] Please do *not* use git (and specifically "git log") when generating the docs

On 02/18/2016 04:39 PM, Dolph Mathews wrote: On Thu, Feb 18, 2016 at 11:17 AM, Thomas Goirand > wrote: Hi, I've seen Reno doing it, then some more. It's time that I raise the issue globally in this list before the epidemic spreads to the

[openstack-dev] [ironic] Midcycle summary part 6/6

Hi all, As our midcycle is virtual and split into 6 "sessions" for the sake of timezones, we'll be sending a brief summary of each session so that folks can catch up before the next one. All of this info should be on the etherpad as well. Session 6/6 was February 19, -0400 UTC. This will be

Re: [openstack-dev] [puppet] how to run rspec tests? r10k issue

Well, since we need to manually run "bundle install", we can pass the path to where we want the gems but always require an extra argument is not the best way. 2016-02-18 22:48 GMT-03:00 Matt Fischer : > I ended up symlinking the r10k binary I have installed to the place it

Re: [openstack-dev] [nova][all] Deprecation policy between projects

Hi Gordon, Thank you for the advice, that is very useful for me now :-) Thanks Ken Ohmichi --- 2016-02-15 18:35 GMT-08:00 gordon chung : > > > On 14/02/2016 8:32 AM, Ken'ichi Ohmichi wrote: >> Hi, >> >> Do we have any deprecation policies between projects? >> When we can remove

Re: [openstack-dev] Questions regarding image "location" and glanceclient behaviour ...

> > > But this procedure will force me to download all images in advance, > which I > > can not do. > > > > I NEED the previous behavior, where Glance download the images by itself, > > on demand. > > > > How to do this with V2 ? > > You can use glance image-create without passing it any image

Re: [openstack-dev] [puppet] how to run rspec tests? r10k issue

I ended up symlinking the r10k binary I have installed to the place it wants it to be and it worked. I do have that in my Gemfile. Question is, can we make this work without manual steps? On Thu, Feb 18, 2016 at 4:57 PM, Alex Schultz wrote: > > > On Thu, Feb 18, 2016 at

[openstack-dev] [glance]one more use case for Image Import Refactor from OPNFV

Hello, Glad to know that the "Image Import Refactor" is the essential BP in Mitaka. One more use case from OPNFV as following: In OPNFV, one deployment scenario is each data center will be deployed with independent OpenStack instance, but shared identity management. That means there will be

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

It might be good to consider the scale that's needed too. For us, some of our clouds are on an internal network and its highly non desirable for an external cdn to be used. But to have the api work internally and scale out to at least the organization, so the same app templates can be used

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On 2016-02-18 17:20:35 -0600 (-0600), Ian Cordasco wrote: [...] > Presently, I think we need a F/OSS CDN but it isn't going to > happen until the infrastructure for a CDN is something any > OpenStack consumer would want to manage. [...] Probably an unusual use case and stretching the definition

Re: [openstack-dev] [nova] Update on scheduler and resource tracker progress

On 02/18/2016 07:16 PM, Clint Byrum wrote: Excerpts from Jay Pipes's message of 2016-02-18 11:33:04 -0800: I'm talking about the destination host selection process too, but I was just assuming you'd need compound indexes to make this really efficient, and I assumed that would mean more indexes

Re: [openstack-dev] [nova] Update on scheduler and resource tracker progress

Excerpts from Jay Pipes's message of 2016-02-18 11:33:04 -0800: > On 02/12/2016 01:47 PM, Clint Byrum wrote: > > Excerpts from Jay Pipes's message of 2016-02-11 12:24:04 -0800: > >> Hello all, > >> > >> Performance working group, please pay attention to Chapter 2 in the > >> details section. > >>

Re: [openstack-dev] [puppet] how to run rspec tests? r10k issue

On Thu, Feb 18, 2016 at 3:26 PM, Matt Fischer wrote: > Is anyone able to share the secret of running spec tests since the r10k > transition? bundle install && bundle exec rake spec have issues because > r10k is not being installed. Since I'm not the only one hopefully this

Re: [openstack-dev] [openstack-ansible] network question and documentation

  -Original Message- From: Fabrice Grelaud Reply: OpenStack Development Mailing List (not for usage questions) Date: February 17, 2016 at 09:02:49 To: openstack-dev@lists.openstack.org

Re: [openstack-dev] Questions regarding image "location" and glanceclient behaviour ...

-Original Message- From: Martinx - ジェームズ Reply: OpenStack Development Mailing List (not for usage questions) Date: February 17, 2016 at 23:18:11 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

-Original Message- From: Flavio Percoco Reply: Flavio Percoco , OpenStack Development Mailing List (not for usage questions) Date: February 18, 2016 at 10:10:18 To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [puppet] how to run rspec tests? r10k issue

Hi Matt, when the r10k is not installed I use gem install or bundle install passing the directory that should have the gem. I'll search. Tomorrow i'll try to find the command in my env and post. Em 18/02/2016 19:27, "Matt Fischer" escreveu: > Is anyone able to share the

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On Feb 12, 2016, at 14:49, Jay Pipes wrote: > This would be my preference as well, even though it's technically a > backwards-incompatible API change. > > The idea behind get-me-a-network was specifically to remove the current > required complexity of the nova boot command

[openstack-dev] [puppet] how to run rspec tests? r10k issue

Is anyone able to share the secret of running spec tests since the r10k transition? bundle install && bundle exec rake spec have issues because r10k is not being installed. Since I'm not the only one hopefully this question will help others. +

Re: [openstack-dev] [neutron][dnsmasq]DNS redirection by dnsmasq

On Tue, Feb 16, 2016 at 11:55 PM, Zhi Chang wrote: > DNS redirection is our customer's needs. Customer has their own CDN. They > want to save traffic in CDN so that they can cost less money. > So they let us hijack some domain names. We used dnsmasq "--cname" option to >

Re: [openstack-dev] [all] Please do *not* use git (and specifically "git log") when generating the docs

On Fri, Feb 19, 2016 at 01:17:08AM +0800, Thomas Goirand wrote: > Hi, > > I've seen Reno doing it, then some more. It's time that I raise the > issue globally in this list before the epidemic spreads to the whole of > OpenStack ! :) > > The last occurence I have found is in oslo.config (but

Re: [openstack-dev] [all] Please do *not* use git (and specifically "git log") when generating the docs

On 02/18/2016 11:17 AM, Thomas Goirand wrote: > Hi, > > I've seen Reno doing it, then some more. It's time that I raise the > issue globally in this list before the epidemic spreads to the whole of > OpenStack ! :) > > The last occurence I have found is in oslo.config (but please keep in > mind

Re: [openstack-dev] [all] Please do *not* use git (and specifically "git log") when generating the docs

On Thu, Feb 18, 2016 at 11:17 AM, Thomas Goirand wrote: > Hi, > > I've seen Reno doing it, then some more. It's time that I raise the > issue globally in this list before the epidemic spreads to the whole of > OpenStack ! :) > > The last occurence I have found is in oslo.config

Re: [openstack-dev] [nova][neutron] How would nova microversion get-me-a-network in the API?

On 2/15/2016 1:41 AM, Gary Kotton wrote: Yes, you could consider Neutron as a proxy for this. It creates the network, subnet, router… To be honest I think that we should maybe consider ofering a template that can be created by Neutron and then the template ID passed from Nova or wherever. This

[openstack-dev] [ironic] Midcycle summary part 5/6

Hi all, As our midcycle is virtual and split into 6 "sessions" for the sake of timezones, we'll be sending a brief summary of each session so that folks can catch up before the next one. All of this info should be on the etherpad as well. Session 5/6 was February 18, 1500-2000 UTC. * Discussed

Re: [openstack-dev] [nova][neutron] Update on os-vif progress (port binding negotiation)

Thanks, Sean. I'll try to keep you and everybody informed about progress on those. 2016-02-18 20:20 GMT+03:00 Sean M. Collins : > Jay Pipes wrote: > > From our Mirantis team, I've asked Sergey Belous to handle any necessary > > changes to devstack and project-config (for a

[openstack-dev] [release][openstack] os-client-config 1.15.0 release (mitaka)

We are satisfied to announce the release of: os-client-config 1.15.0: OpenStack Client Configuation Library This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/os-client-config With package available at:

Re: [openstack-dev] [Neutron] - DVR L3 data plane performance results and scenarios

Hi Gal, We do have DVR testing results on 200 nodes for both VXLAN and VLAN configurations. We plan to publish them in performance-docs repository. Thanks Georgy On Thu, Feb 18, 2016 at 6:06 AM, Gal Sagie wrote: > Hello All, > > We have started to test Dragonflow [1] data

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

On 02/18/2016 02:00 PM, Morgan Fainberg wrote: Adam, CORS shouldn't need catalog integration ever. CORS is a layer above anything in the service catalog and doesn't provide extra security except signalling to the javascript vm it can access resources outside of it's current domain; something

Re: [openstack-dev] [Neutron] - DVR L3 data plane performance results and scenarios

Hi Gal Sagie, Yes there was some performance results on DVR that we shared with the community during the Liberty summit in Vancouver. Also I think there was a performance analysis that was done by Oleg Bondarev on DVR during the Paris summit. We have done lot more changes to the control plane

Re: [openstack-dev] [nova] Update on scheduler and resource tracker progress

On 02/12/2016 01:47 PM, Clint Byrum wrote: Excerpts from Jay Pipes's message of 2016-02-11 12:24:04 -0800: Hello all, Performance working group, please pay attention to Chapter 2 in the details section. Chapter 2 - Addressing performance and scale

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

Excerpts from Sean Dague's message of 2016-02-18 12:55:02 -0500: > On 02/18/2016 12:22 PM, Michael Krotscheck wrote: > > On Thu, Feb 18, 2016 at 9:07 AM Doug Hellmann > > wrote: > > > > > > If the deployer is only ever supposed to set

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

Adam, CORS shouldn't need catalog integration ever. CORS is a layer above anything in the service catalog and doesn't provide extra security except signalling to the javascript vm it can access resources outside of it's current domain; something that can be worked around in many ways including

Re: [openstack-dev] [mistral] More attention to PostgreSQL

We already have a non-voting gate that runs our unit tests on top of Postgres. The thing is that it’s not really stable now and it runs for a long time because there’s no parallelism in it (it can be done but requires more work). So we just need to keep improving it. Renat Akhmerov @ Mirantis

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

On 18 February 2016 at 17:58, Sean Dague wrote: > On 02/18/2016 12:17 PM, Michael Krotscheck wrote: >> Clarifying: >> >> On Thu, Feb 18, 2016 at 2:32 AM Sean Dague > > wrote: >> >> Ok, to make sure we all ended up on the same page at the

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

On 02/18/2016 12:17 PM, Michael Krotscheck wrote: Clarifying: On Thu, Feb 18, 2016 at 2:32 AM Sean Dague > wrote: Ok, to make sure we all ended up on the same page at the end of this discussion, this is what I think I heard. 1) oslo.config

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

On Thu, Feb 18, 2016 at 9:58 AM, Sean Dague wrote: > On 02/18/2016 12:17 PM, Michael Krotscheck wrote: > > Clarifying: > > > > On Thu, Feb 18, 2016 at 2:32 AM Sean Dague > > wrote: > > > > Ok, to make sure we all ended up on the same

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On Wed, Feb 10, 2016, at 09:52 AM, Sean M. Collins wrote: > Ihar Hrachyshka wrote: > > Also, I added some interface state dump for worlddump, and here is how the > > main node networking setup looks like: > > > >

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

On 02/18/2016 12:17 PM, Michael Krotscheck wrote: > Clarifying: > > On Thu, Feb 18, 2016 at 2:32 AM Sean Dague > wrote: > > Ok, to make sure we all ended up on the same page at the end of this > discussion, this is what I think I heard. > >

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

On 02/18/2016 12:22 PM, Michael Krotscheck wrote: > On Thu, Feb 18, 2016 at 9:07 AM Doug Hellmann > wrote: > > > If the deployer is only ever supposed to set the value to the default, > why do we let them change it at all? Why isn't

[openstack-dev] [release][cinder] os-brick 1.0.0 release (mitaka)

We are pumped to announce the release of: os-brick 1.0.0: OpenStack Cinder brick library for managing local volume attaches This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/os-brick With package available at:

[openstack-dev] [Openstack-operators] OpenStack rolling upgrade

Hi all, We are discussing the creation of a tool to perform a scripted rolling upgrade of OpenStack from the Liberty to Mitaka release. We would like your input on which of the following feature areas are most important to you. Here’s small questionnaire http://goo.gl/forms/C5NXOxhLPU

[openstack-dev] [all] Please do *not* use git (and specifically "git log") when generating the docs

Hi, I've seen Reno doing it, then some more. It's time that I raise the issue globally in this list before the epidemic spreads to the whole of OpenStack ! :) The last occurence I have found is in oslo.config (but please keep in mind this message is for all projects), which has, its

Re: [openstack-dev] [nova][neutron] Update on os-vif progress (port binding negotiation)

Jay Pipes wrote: > From our Mirantis team, I've asked Sergey Belous to handle any necessary > changes to devstack and project-config (for a functional test gate check > job). I'll keep an eye out in my DevStack review queue for these patches and will make sure to review them promptly. -- Sean

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

On Thu, Feb 18, 2016 at 9:07 AM Doug Hellmann wrote: > > If the deployer is only ever supposed to set the value to the default, > why do we let them change it at all? Why isn't this just something the > app sets? There was a specific request from the ironic team to not

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

Clarifying: On Thu, Feb 18, 2016 at 2:32 AM Sean Dague wrote: > Ok, to make sure we all ended up on the same page at the end of this > discussion, this is what I think I heard. > > 1) oslo.config is about to release with a feature that will make adding > config to paste.ini not

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

On Wed, Feb 17, 2016 at 2:29 PM Doug Hellmann wrote: > > That change only affects sample files and documentation. It has been > possible for applications to override config defaults for ages. Were we > blocked on making effective use of that because of the doc issue for a

Re: [openstack-dev] [cinder] adding a new /v3 endpoint for api-microversions

On Thu, Feb 18, 2016 at 03:38:39PM +, D'Angelo, Scott wrote: > Cinder team is proposing to add support for API microversions [1]. It came up > at our mid-cycle that we should add a new /v3 endpoint [2]. Discussions on > IRC have raised questions about this [3] > > Please weigh in on the

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On 16/02/16 19:17 +, Sean M. Collins wrote: Doug Hellmann wrote: Is there? I thought the point was OpenCDN isn't actually usable. Maybe someone from the Poppy team can provide more details about that. That is certainly a problem. However I think I would lean on Sean Dague's argument about

Re: [openstack-dev] [fuel] Supporting multiple Openstack versions

On Thu, Feb 18, 2016 at 4:00 AM, Aleksandr Didenko wrote: > > Given the requirements to be able to use new features in fuel, with an > older version of OpenStack, what alternative would you propose? > > For example, it's possible to use existing "release" functionality in

[openstack-dev] [cinder] adding a new /v3 endpoint for api-microversions

Cinder team is proposing to add support for API microversions [1]. It came up at our mid-cycle that we should add a new /v3 endpoint [2]. Discussions on IRC have raised questions about this [3] Please weigh in on the design decision to add a new /v3 endpoint for Cinder for clients to use when

[openstack-dev] [nova][neutron] Update on os-vif progress (port binding negotiation)

Hello Stackers, Apologies for the delay in getting this update email out to everyone. tl;dr - We are making good progress on the os-vif library and plugin system. We have immediate goals for Mitaka, all of which are in progress and on track to complete by Feature Freeze. details

Re: [openstack-dev] [trove] Start to port Trove to Python 3 in Mitaka cycle?

Great, so in response to your email (below) and Flavio's email [1], I submit to you that the way to handle this is as we had discussed at earlier meeting(s) and that is to wait for Newton. Thanks, -amrith [1] http://openstack.markmail.org/thread/4uksb3kmhnagoc5a > -Original Message-

Re: [openstack-dev] [ironic] midcycle voice channel is 7777

is working for the Thursday midcycle session so we are moving back to that channel. Sam On 17/02/2016 15:19, "Jim Rollenhagen" wrote: >So, someone has injected their hold music into 7778. We've now moved to >7779, sorry for the trouble :( > >// jim > >On Wed, Feb

Re: [openstack-dev] [all] [cinder] [glance] tenant vs. project

Not all clients are fully v3 compatible, this is the effort to move to session, from keystone client.session to keystone auth.session, and os-client-config. Since this work has been slow, we are not 100% there yet, but as Henrique said, OpenStack client does support both consistently. If devstack

Re: [openstack-dev] [trove] Start to port Trove to Python 3 in Mitaka cycle?

Le 18/02/2016 14:15, Amrith Kumar a écrit : Let's definitely discuss this again once you have all the changes that you feel should be merged for Mitaka ready. I don't like working on long patch series. In my experience, after more than 4 patches, it's more expensive to maintain the patch

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

Excerpts from Sean Dague's message of 2016-02-18 05:29:44 -0500: > Ok, to make sure we all ended up on the same page at the end of this > discussion, this is what I think I heard. > > 1) oslo.config is about to release with a feature that will make adding > config to paste.ini not needed (i.e. >

Re: [openstack-dev] [Fuel] Wildcards instead of

Hey Kyrylo, As it was mentioned in the review: you're about to break roles defined by plugins. That's not good move, I believe. Regarding 'exclude' directive, I have no idea what you're talking about. We don't support it now, and, anyway, there should be no difference between roles defined by

Re: [openstack-dev] [kolla][infra] Re: Patch submission for Kolla

On 2016-02-18 13:47:33 + (+), Steven Dake (stdake) wrote: > I recommend contacting #openstack-infra on irc with your question. > They are the folks that can get this solved for you. Note I think > the best way to update contact information is to login to > openstack.org, and fill out your

[openstack-dev] [Neutron] - DVR L3 data plane performance results and scenarios

Hello All, We have started to test Dragonflow [1] data plane L3 performance and was wondering if there is any results and scenarios published for the current Neutron DVR that we can compare and learn the scenarios to test. We mostly want to validate and understand if our results are accurate and

Re: [openstack-dev] [trove] Start to port Trove to Python 3 in Mitaka cycle?

On 18/02/16 13:15 +, Amrith Kumar wrote: Victor, thanks for the changes and the patch sets. TL;DR: We've discussed this a couple of times already, once at a Trove meeting[1], once at length at the midcycle, and concluded that post-Mitaka is the right time to merge changes relative to

[openstack-dev] [Kuryr] - IRC Meeting (2/23) - 0300 UTC (#openstack-meeting-4)

Hello All, We will have an IRC meeting on 2/23 at 0300 UTC in #openstack-meeting-4 Please review the expected meeting agenda here: https://wiki.openstack.org/wiki/Meetings/Kuryr You can view last meeting action items and logs here:

[openstack-dev] [kolla][infra] Re: Patch submission for Kolla

Sebastien, Cool that will be a nice feature :) I recommend contacting #openstack-infra on irc with your question. They are the folks that can get this solved for you. Note I think the best way to update contact information is to login to openstack.org, and fill out your contact information

Re: [openstack-dev] [openstack-ansible] : Steps to upgrade the current setup from Kilo to Liberty

On 02/18/2016 04:02 AM, Sharma Swati6 wrote: > I have followed the following steps- > ./Scripts/teardown.sh > Git checkout 12.0.6 (liberty) > ran setup-hosts.yml*(FACING ISSUES HERE)* Hello Sharma, Could you give us the exact command you ran the error output that you received? That

Re: [openstack-dev] [trove] Start to port Trove to Python 3 in Mitaka cycle?

Victor, thanks for the changes and the patch sets. TL;DR: We've discussed this a couple of times already, once at a Trove meeting[1], once at length at the midcycle, and concluded that post-Mitaka is the right time to merge changes relative to Python 3. Once you have all the changes that you

Re: [openstack-dev] [all] [cinder] [glance] tenant vs. project

Hi Sean, I don't think they're supposed to work with that. Both of those clients have their python API compatible with those variables you've commented. But the CLI should be used through OpenStack client. Just for an example, keystoneclient CLI does not support it, but OpenStack client supports

[openstack-dev] [trove] Start to port Trove to Python 3 in Mitaka cycle?

Hi, When I began to work on porting Trove to Python 3, I was blocked by MySQL-Python which is not compatible with Python 3. I tried a big change replacing MySQL-Python with PyMySQL, since other OpenStack services also moved to PyMySQL. But tests fail and I'm unable to fix them :-/

Re: [openstack-dev] [all] [cinder] [glance] tenant vs. project

On 02/12/2016 07:01 AM, Sean Dague wrote: > Ok... this is going to be one of those threads, but I wanted to try to > get resolution here. > > OpenStack is wildly inconsistent in it's use of tenant vs. project. As > someone that wasn't here at the beginning, I'm not even sure which one > we are

Re: [openstack-dev] [fuel] Supporting multiple Openstack versions

> Given the requirements to be able to use new features in fuel, with an older version of OpenStack, what alternative would you propose? For example, it's possible to use existing "release" functionality in Fuel (release contains granular tasks configuration, puppet modules and manifests,

[openstack-dev] [Fuel] Wildcards instead of

Hello, We are about to switch to wildcards instead of listing all groups in tasks explicitly [0]. This change must make deployment process more obvious for developers. However, it might lead to confusion when new groups are added either by plugin or fuel team in future. As mention by Bogdan, it

Re: [openstack-dev] [heat] intrinsic function bugfixes and hot versioning

On Wed, Feb 17, 2016 at 7:54 PM, Steven Hardy wrote: > Hi all, > > So, Zane and I have discussed $subject and it was suggested I take this to > the list to reach consensus. > > Recently, I've run into a couple of small but inconvenient limitations in > our intrinsic function

Re: [openstack-dev] [Kuryr] will we use os-vif in kuryr

On Thu, Feb 18, 2016 at 09:01:35AM +, Liping Mao (limao) wrote: > Hi Kuryr team, > > I see couple of commits to add support for vif plug. > https://review.openstack.org/#/c/280411/ > https://review.openstack.org/#/c/280878/ > > Do we have plan to use os-vif? >

Re: [openstack-dev] [oslo] upgrade implications of lots of content in paste.ini

Ok, to make sure we all ended up on the same page at the end of this discussion, this is what I think I heard. 1) oslo.config is about to release with a feature that will make adding config to paste.ini not needed (i.e. https://review.openstack.org/#/c/265415/ is no longer needed). 2) ideally

Re: [openstack-dev] [infra][neutron] publish and update Gerrit dashboard link automatically

On 02/17/2016 07:17 PM, Doug Wiegley wrote: Results, updated hourly (bookmarkable, will redirect to gerrit): http://104.236.79.17/ http://104.236.79.17/current http://104.236.79.17/current-min Nice, thanks a lot for looking into this!!

Re: [openstack-dev] [release][stable][oslo] oslo.service 0.9.1 release (liberty)

Hi, Le 17/02/2016 19:29, no-re...@openstack.org a écrit : > We are chuffed to announce the release of: > > oslo.service 0.9.1: oslo.service library > (...) > > Changes in oslo.service 0.9.0..0.9.1 > > > 8b6e2f6 Fix race condition on handling signals >

Re: [openstack-dev] [fuel][nailgun][volume-manager][fuel-agent] lvm metadata size value. why was it set to 64M?

Hi Alexander, I was trying to trace the change and found 3 year old commit, yes it's hard to recover the reason [0]. So what we should ask is what is a right way to calculate lvm metadata size and change this behaviour. I would suggest at least explicitly set metadata size on Nailgun side to the

[openstack-dev] [openstack-ansible] : Steps to upgrade the current setup from Kilo to Liberty

Hi All, Can anyone please guide me with the steps to upgrade my current openstack-ansible setup from Kilo to Liberty. I have followed the following steps- ./Scripts/teardown.sh Git checkout 12.0.6 (liberty) ran setup-hosts.yml (FACING ISSUES HERE) Thanks & Regards Swati Sharma

Re: [openstack-dev] [nova] A prototype implementation towards the "shared state scheduler"

On 02/15/2016 09:27 AM, Sylvain Bauza wrote: > > > Le 15/02/2016 06:21, Cheng, Yingxin a écrit : >> >> Hi, >> >> >> >> I’ve uploaded a prototype https://review.openstack.org/#/c/280047/ >> to testify its design goals >> in accuracy, performance,

Re: [openstack-dev] [Openstack-i18n] [stable][i18n] What is the backport policy on i18n changes?

hmm, I think the policy should depends on projects. For projects which don't have active translations, I think it's OK to backport. For projects which have active translations, "Exception procedure" of StringFreeze could help. Translators need to be notified for the changes. If you don't know

Re: [openstack-dev] [stable][i18n] What is the backport policy on i18n changes?

On 02/18/2016 01:16 AM, Matt Riedemann wrote: I don't think we have an official policy for stable backports with respect to translatable string changes. I'm looking at a release request for ironic-inspector on stable/liberty [1] and one of the changes in that has translatable string changes to

[openstack-dev] [Kuryr] will we use os-vif in kuryr

Hi Kuryr team, I see couple of commits to add support for vif plug. https://review.openstack.org/#/c/280411/ https://review.openstack.org/#/c/280878/ Do we have plan to use os-vif? https://github.com/openstack/os-vif Regards, Liping Mao

[openstack-dev] Tempest initialization failure while installing devstack.

Hi All, I have been trying to install devstack on my Ubuntu machine but while initializing tempest I am getting the below error. I have tried for 4-5 times but still facing the same issue. 2016-02-18 08:17:00.403 | venv create: /opt/stack/new/tempest/.tox/venv 2016-02-18 08:17:10.731 |

[openstack-dev] [devstack] Installing devstack with multi-region setting fails

2016-01-29 03:26:29.317 | + source /home/stack/devstack/userrc_early 2016-01-29 03:26:29.317 | ++ export OS_IDENTITY_API_VERSION=3 2016-01-29 03:26:29.317 | ++ OS_IDENTITY_API_VERSION=3 2016-01-29 03:26:29.318 | ++ export OS_AUTH_URL=http://192.168.56.101:35357 2016-01-29 03:26:29.318 | ++

Re: [openstack-dev] [fuel] Supporting multiple Openstack versions

On 17.02.2016 18:23, Bogdan Dobrelya wrote: >> So we'll have tons of conditionals in composition layer, right? Even if >> some puppet-openstack class have just one new parameter in new release, >> then we'll have to write a conditional and duplicate class declaration. Or >> write complex

[openstack-dev] [vitrage] Vitrage Demo - Alarms Use Case

Hi, We are happy to share with you all our second Vitrage demo, showing alarms imported from Nagios in Vitrage horizon UI. Here it is: https://www.youtube.com/watch?v=w1XQATkrdmg For more details about Vitrage, please visit our wiki here: https://wiki.openstack.org/wiki/Vitrage Thanks,