Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

+1 under the condition that there will be a path of migration from "old" Liberty to the "new" Liberty. At least in form of documentation. If that wouldn't require any downtime of VM-s (except the Docker upgrade, of course) and can be achieved just by running playbooks and some script for

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

+1 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

It may not be best practice what we did here even this time is o.k. On Tue, Mar 29, 2016 at 5:10 PM, Yipei Niu wrote: > Hi, all, > > I follow the advice given by Zhiyuan, and it works. For the port error, > somebody removes the line "iniset $NOVA_CONF DEFAULT network_api_class

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

+1 No doubt he is good at review and also helpful to guide newbies joining kolla. -Original Message- From: Swapnil Kulkarni [mailto:m...@coolsvap.net] Sent: Wednesday, March 30, 2016 9:14 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev]

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

Hi Yipei, Segment id is not correctly assigned to the bridge network so you get the "None is not an interger" message. What version of neutron and tricircle you use? Neutron moves network segment table definition out of ML2 code tree and tricircle has adapted this change. BTW, I updated

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

On Wed, Mar 30, 2016 at 9:03 AM, Michał Jastrzębski wrote: > I think that it goes without saying that I'm +1 > > On 29 March 2016 at 22:27, Steven Dake (stdake) wrote: >> Dear cores, >> >> inc0 has been investigating our backport options for 1.1.0 and they

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

On Tue, Mar 29, 2016 at 9:37 PM, Steven Dake (stdake) wrote: > Hey folks, > > Consider this proposal a +1 in favor of Vikram joining the core reviewer > team. His reviews are outstanding. If he doesn’t have anything useful to > add to a review, he doesn't pile on the review

Re: [openstack-dev] [Neutron] Evolving the stadium concept

Hi Armando, We want to add the support for a new ML2 driver. Can you please guide what is the step moving forward? Thanks Vikram On Fri, Mar 4, 2016 at 12:39 AM, Armando M. wrote: > Hi folks, > > Status update on this matter: > > Russell, Kyle and I had a number of patches

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

I think that it goes without saying that I'm +1 On 29 March 2016 at 22:27, Steven Dake (stdake) wrote: > Dear cores, > > inc0 has been investigating our backport options for 1.1.0 and they look > bleak. At this time we would have to backport heka because of changes in > Docker

[openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

Dear cores, inc0 has been investigating our backport options for 1.1.0 and they look bleak. At this time we would have to backport heka because of changes in Docker 1.10.z which are incompatible with the syslog dev file. We had originally spoken about just taking Mitaka and placing it in

Re: [openstack-dev] [neutron] OVSDB native interface as default in gate jobs

I'm not aware of any issues. Perhaps you can propose a patch to just change the default in Neutron to that interface and people can -1 if there are any concerns. On Tue, Mar 29, 2016 at 4:32 PM, Inessa Vasilevskaya < ivasilevsk...@mirantis.com> wrote: > Hi all, > > I spent some time researching

Re: [openstack-dev] [ptl][kolla][release] Deploying the big tent

On 03/29/2016 04:46 PM, Emilien Macchi wrote: > On Mon, Mar 28, 2016 at 9:16 PM, Steven Dake (stdake) > wrote: >> >> >> On 3/27/16, 2:50 PM, "Matt Riedemann" wrote: >> >>> >>> >>> On 3/26/2016 11:27 AM, Steven Dake (stdake) wrote: Hey fellow

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

Hi all, I have already booted two VMs and successfully created a router with Neutron. But I have some trouble with attaching the router to a subnet. The error in q-svc.log is as follows: 2016-03-29 15:41:04.065 ^[[01;31mERROR oslo_db.api [^[[01;36mreq-0180a3f5-e34c-4d4c-bd39-3c0c714b02de

Re: [openstack-dev] [magnum] Discuss the blueprint "support-private-registry"

Hi Hongbin Thanks for starting this thread, I initial propose this bp because I am in China which is behind China great wall and can not have access of gcr.io directly, after checking our cloud-init script, I see that lots of code are *hard coded* to using gcr.io, I personally though this

Re: [openstack-dev] [nova][neutron] What to do about booting into port_security_enabled=False networks?

On 3/29/2016 4:44 PM, Armando M. wrote: On 29 March 2016 at 08:08, Matt Riedemann > wrote: Nova has had some long-standing bugs that Sahid is trying to fix here [1]. You can create a network in neutron with

[openstack-dev] [puppet] managed gems dependencies in a centralized way

How many times did we have broken Gem dependencies, for different reasons? A lot, maybe too much. It's time to find a way to centralize Gems dependencies, like other OpenStack project already do with openstack/requirements and Python dependencies. So I submitted this patch:

Re: [openstack-dev] [all] Service Catalog TNG work in Mitaka ... next steps

On 3/29/2016 2:30 PM, Sean Dague wrote: At the Mitaka Summit we had a double session on the Service Catalog, where we stood, and where we could move forward. Even though the service catalog isn't used nearly as much as we'd like, it's used in just enough odd places that every change pulls on a

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

+1 On Wed, Mar 30, 2016 at 8:25 AM, Angus Salkeld wrote: > +1 > > > On Wed, Mar 30, 2016 at 6:45 AM Michał Jastrzębski > wrote: > >> +1 >> >> On 29 March 2016 at 11:39, Ryan Hallisey wrote: >> > +1 >> > >> > - Original Message

Re: [openstack-dev] [neutron] unit test failures due to new release of Routes package (v2.3)

Ah, thanks Henry! I went ahead and filed a bug too, marked it as duplicate of the one you linked. \-- Aditya On Mar 29 2016, at 6:06 pm, Henry Gessau hen...@gessau.net wrote: > https://launchpad.net/bugs/1563028 https://review.openstack.org/298855 > > Aditya Vaja

Re: [openstack-dev] [neutron] unit test failures due to new release of Routes package (v2.3)

https://github.com/bbangert/routes/pull/65 On Tue, Mar 29, 2016 at 9:04 PM, Henry Gessau wrote: > https://launchpad.net/bugs/1563028 > https://review.openstack.org/298855 > > Aditya Vaja wrote: >> Hi, >> >> I'm seeing unit test failures when I test

[openstack-dev] [tricircle]weekly meeting of Mar. 30

Hi, IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. Agenda: # Cross OpenStack L2 networking # pod scheduling # Reliable aync. Job # Link: https://etherpad.openstack.org/p/TricircleToDo If you have other topics to be discussed

Re: [openstack-dev] [neutron] unit test failures due to new release of Routes package (v2.3)

https://launchpad.net/bugs/1563028 https://review.openstack.org/298855 Aditya Vaja wrote: > Hi, > > I'm seeing unit test failures when I test locally after a fresh git clone of > neutron master. > > $ ./run_tests.sh -V -f > > log excerpt:

[openstack-dev] [neutron] unit test failures due to new release of Routes package (v2.3)

Hi, I'm seeing unit test failures when I test locally after a fresh git clone of neutron master. $ ./run_tests.sh -V -f log excerpt: http://paste.openstack.org/show/492384/ I update the requirements.txt to use 'Routes2.0,=1.12.3' and all the tests work fine. I see there was a

Re: [openstack-dev] [TripleO] tripleo-quickstart import

On 03/29/2016 08:30 PM, John Trowbridge wrote: > Hola, > > With the approval of the tripleo-quickstart spec[1], it is time to > actually start doing the work. The first work item is moving it to the > openstack git. The spec talks about moving it as is, and this would > still be fine. > >

[openstack-dev] [TripleO] tripleo-quickstart import

Hola, With the approval of the tripleo-quickstart spec[1], it is time to actually start doing the work. The first work item is moving it to the openstack git. The spec talks about moving it as is, and this would still be fine. However, there are roles in the tripleo-quickstart tree that are not

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

+1 On Wed, Mar 30, 2016 at 6:45 AM Michał Jastrzębski wrote: > +1 > > On 29 March 2016 at 11:39, Ryan Hallisey wrote: > > +1 > > > > - Original Message - > > From: "Paul Bourke" > > To: openstack-dev@lists.openstack.org >

[openstack-dev] [searchlight] Add Nova Keypair Plugin

Hi Lakshmi, Thank you for your advice. I'm trying to index the public keys. I'm gonna try to discuss in searchlight-specs before starting development. Thanks Hiroyuki. 差出人: Sampath, Lakshmi [lakshmi.samp...@hpe.com] 送信日時: 2016年3月29日 2:03 宛先: OpenStack

Re: [openstack-dev] [puppet-keystone] Setting additional config options:

On 03/29/2016 06:21 PM, Rich Megginson wrote: On 03/29/2016 04:19 PM, Adam Young wrote: Somewhere in here: http://git.openstack.org/cgit/openstack/puppet-keystone/tree/spec/classes/keystone_spec.rb spec is for the rspec unit testing. Do you mean

Re: [openstack-dev] [puppet-keystone] Setting additional config options:

On 03/29/2016 07:43 PM, Emilien Macchi wrote: On Tue, Mar 29, 2016 at 6:19 PM, Adam Young wrote: Somewhere in here: http://git.openstack.org/cgit/openstack/puppet-keystone/tree/spec/classes/keystone_spec.rb I need to set these options: admin_project_name

Re: [openstack-dev] [TripleO] gnocchi backport exception for stable/mitaka

+1 I think this is a good exception for the same reasons. On 03/29/2016 12:27 PM, Steven Hardy wrote: > On Tue, Mar 29, 2016 at 11:05:00AM -0400, Pradeep Kilambi wrote: >> Hi Everyone: >> >> As Mitaka branch was cut yesterday, I would like to request a backport >> exception to get gnocchi

Re: [openstack-dev] [puppet-keystone] Setting additional config options:

On Tue, Mar 29, 2016 at 6:19 PM, Adam Young wrote: > > Somewhere in here: > > http://git.openstack.org/cgit/openstack/puppet-keystone/tree/spec/classes/keystone_spec.rb > > I need to set these options: > > > admin_project_name > admin_project_domain_name > >

[openstack-dev] [election] [tc] TC Candidacy

I would like to announce my candidacy for election to the Technical Committee. You may know me from being the Horizon PTL for the past five releases and a member of the OpenStack community since 2012 as an operator, contributor and PTL. Over my tenure, I helped guide the Horizon team through

Re: [openstack-dev] [tripleo] Policy Managment and distribution.

On Tue, Mar 29, 2016 at 6:18 PM, Adam Young wrote: > Keystone has a policy API, but no one uses it. It allows us to associate a > policy file with an endpoint. Upload a json blob, it gets a uuid. Associate > the UUID with the endpoint. It could also be associated with a

[openstack-dev] [neutron] OVSDB native interface as default in gate jobs

Hi all, I spent some time researching the current state of native ovsdb interface feature, which has been fully implemented and merged since Liberty [1][2]. I was pretty much impressed by the expected performance improvement (as per spec [1], some interesting research on ovs-vsctl + rootwrap also

[openstack-dev] [magnum] Discuss the blueprint "support-private-registry"

Hi team, This is the item we didn't have time to discuss in our team meeting, so I started the discussion in here. Here is the blueprint: https://blueprints.launchpad.net/magnum/+spec/support-private-registry . Per my understanding, the goal of the BP is to allow users to specify the url of

Re: [openstack-dev] [all] Austin Design Summit track layout

On Thursday, I'd like to proposed swapping Swift's 1:30pm session with Fuel's 2:20pm session. This will give Swift a contiguous time block in the afternoon, and Fuel's session would line up right after their full morning (albeit after the lunch break). I have not had a chance to talk to anyone

[openstack-dev] [kolla] IRC channel renamed to #openstack-kolla

See Subject. Note #kolla automatically redirects to openstack-kolla now, so if folks have #kolla in their client list, they will join #openstack-kolla if they have a recent IRC client. If your already in the channel leave and rejoin or restart your client and you will be connected with the

[openstack-dev] [puppet-keystone] Setting additional config options:

Somewhere in here: http://git.openstack.org/cgit/openstack/puppet-keystone/tree/spec/classes/keystone_spec.rb I need to set these options: admin_project_name admin_project_domain_name http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/config.py#n450

Re: [openstack-dev] [puppet-keystone] Setting additional config options:

On 03/29/2016 04:19 PM, Adam Young wrote: Somewhere in here: http://git.openstack.org/cgit/openstack/puppet-keystone/tree/spec/classes/keystone_spec.rb spec is for the rspec unit testing. Do you mean http://git.openstack.org/cgit/openstack/puppet-keystone/tree/manifests/init.pp ? I

[openstack-dev] [tripleo] Policy Managment and distribution.

Keystone has a policy API, but no one uses it. It allows us to associate a policy file with an endpoint. Upload a json blob, it gets a uuid. Associate the UUID with the endpoint. It could also be associated with a service, and then it is associated with all endpoint for that service unless

Re: [openstack-dev] [Neutron]Relationship between physical networks and segment

My answers below are from the perspective of normal (non-routed) networks implemented in ML2. The support for routed networks should build on this without breaking it. On 3/29/16 3:38 PM, Miguel Lavalle wrote: Hi, I am writing a patchset to build a mapping between hosts and network

Re: [openstack-dev] [nova][neutron] What to do about booting into port_security_enabled=False networks?

On 29 March 2016 at 08:08, Matt Riedemann wrote: > Nova has had some long-standing bugs that Sahid is trying to fix here [1]. > > You can create a network in neutron with port_security_enabled=False. > However, the bug is that since Nova adds the 'default' security

Re: [openstack-dev] [TripleO] gnocchi backport exception for stable/mitaka

+1 for me, Gnocchi is bringing great features to improve Ceilometer deployments at scale. It would be a first iteration and brings interesting feedback by having it. Go for it! On Tue, Mar 29, 2016 at 11:05 AM, Pradeep Kilambi wrote: > Hi Everyone: > > As Mitaka branch was cut

Re: [openstack-dev] [ptl][kolla][release] Deploying the big tent

On Mon, Mar 28, 2016 at 9:16 PM, Steven Dake (stdake) wrote: > > > On 3/27/16, 2:50 PM, "Matt Riedemann" wrote: > >> >> >>On 3/26/2016 11:27 AM, Steven Dake (stdake) wrote: >>> Hey fellow PTLs and core reviewers of those projects, >>> >>> Kolla at

Re: [openstack-dev] [TripleO] gnocchi backport exception for stable/mitaka

On Tue, Mar 29, 2016 at 12:27 PM, Steven Hardy wrote: > On Tue, Mar 29, 2016 at 11:05:00AM -0400, Pradeep Kilambi wrote: >> Hi Everyone: >> >> As Mitaka branch was cut yesterday, I would like to request a backport >> exception to get gnocchi patches[1][2][3] into stable/mitaka.

[openstack-dev] [election][tc] TC Candidacy for Shamail Tahir

Hi everyone, I would like to announce my candidacy for OpenStack Technical Committee member for the upcoming term. I am currently an offering manager for OpenStack initiatives at IBM and I have been involved in the OpenStack community since 2013. I spend most of my time[1] in our working groups

Re: [openstack-dev] [all] Austin Design Summit track layout

On 3/29/2016 2:48 AM, Thierry Carrez wrote: Matt Riedemann wrote: I see one problem. The single stable team fishbowl session is scheduled for the last slot on Thursday (5pm). The conflict I have with that is the nova team does it's priority/scheduling talk in the last session on the last day

Re: [openstack-dev] [Neutron]Relationship between physical networks and segment

On Tue, Mar 29, 2016 at 1:38 PM, Miguel Lavalle wrote: > I am writing a patchset to build a mapping between hosts and network > segments. The goal of this mapping is to be able to say whether a host has > access to a given network segment. I am building this mapping assuming

Re: [openstack-dev] [all] Austin Design Summit track layout

> On Mar 28, 2016, at 6:28 AM, Thierry Carrez wrote: > > Hi everyone, > > Please find attached in PDF the proposed layout for the various tracks at the > Design Summit in Austin. I tried to take into account all the talk conflicts > and the constraints that you

Re: [openstack-dev] [release][all][ptl] release process changes for official projects

Kirill, This is prep for Newton. So definitely not rocking the boat when we have a week left. -- Dims On Tue, Mar 29, 2016 at 4:08 PM, Kirill Zaitsev wrote: > My immediate question is — when would this be merged? Is it a good idea to > alter this during the final RC week

Re: [openstack-dev] [magnum] Generate atomic images using diskimage-builder

In multiple occasions in the past, we have had to use version of some software that's not available yet in the upstream image for bug fixes or new features (Kubernetes, Docker, Flannel,...). Eventually the upstream image would catch up, but having the tool to customize let us push forward

Re: [openstack-dev] [Neutron] Segments, subnet types, and IPAM

On Tue, Mar 29, 2016 at 12:12 PM, Carl Baldwin wrote: > I've been playing with this a bit on this patch set [1]. I haven't > gotten very far yet but it has me thinking. > > Calico has a similar use case in mind as I do. Essentially, we both > want to group subnets to allow

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

+1 On 29 March 2016 at 11:39, Ryan Hallisey wrote: > +1 > > - Original Message - > From: "Paul Bourke" > To: openstack-dev@lists.openstack.org > Sent: Tuesday, March 29, 2016 12:10:38 PM > Subject: Re: [openstack-dev] [kolla][vote] Nominating

Re: [openstack-dev] [magnum] Generate atomic images using diskimage-builder

So the advantages I can see with diskimage-builder are: - we reuse the same tooling that is present in other openstack projects to generate images, rather than relying on an external image - it improves the control we have on the contents of the image, instead of seeing that as a black box. At

[openstack-dev] [magnum][kuryr] Shared session in design summit

Hi all, As discussed before, our team members want to establish a shared session between Magnum and Kuryr. We expected a lot of attendees in the session so we need a large room (fishbowl). Currently, Kuryr has only 1 fishbowl session, and they possibly need it for other purposes. A solution is

Re: [openstack-dev] [magnum] Generate atomic images using diskimage-builder

Steve, I will defer to the experts in openstack-infra on this one. As long as the image works without modifications, then I think it would be fine to cache the upstream one. Practically speaking, I do anticipate a point at which we will want to adjust something in the image, and it will be

Re: [openstack-dev] [fuel] Component Leads Elections

On Tue, Mar 29, 2016 at 03:19:27PM +0300, Vladimir Kozhukalov wrote: > > I think this call is too late to change a structure for now. I suggest > > that we always respect the policy we've accepted, and follow it. > > > > If Component Leads role is under a question, then I'd continue the > >

Re: [openstack-dev] [release][all][ptl] release process changes for official projects

My immediate question is — when would this be merged? Is it a good idea to alter this during the final RC week and before mitaka release, rather than implement this change early in the Newton cycle and let people release their final release the old way? --  Kirill Zaitsev Murano Team Software

[openstack-dev] [tripleo][fuel] puppet-pacemaker: collaboration is starting now

A few months ago, we moved redhat/puppet-pacemaker to openstack/puppet-pacemaker for some reasons: * We wanted to take benefits from OpenStack Infra (Gerrit, Zuul, Jenkins jobs) and improve testing coverage. Result: we succeed in here, changes in puppet-pacemaker no longer break TripleO HA jobs,

Re: [openstack-dev] [all] Cross Project Session Day Planning

A gentle reminder that we're continuing to collect suggestions in the etherpad for the remainder of the week. As of this email there are '8' suggestions so far. We look forward to many more over the course of the week. Thanks again, -Sean On 03/23/2016 07:02 AM, Sean Dague wrote: > On

Re: [openstack-dev] [magnum] Generate atomic images using diskimage-builder

Adrian, Makes sense. Do the images have to be built to be mirrored though? Can't they just be put on the mirror sites fro upstream? Thanks -steve On 3/29/16, 11:02 AM, "Adrian Otto" wrote: >Steve, > >I¹m very interested in having an image locally cached in glance

[openstack-dev] [election][tc] Annoouncing candidacy for the technical committee election

All My Peers, TL;DR - I will increase adoption of OpenStack by removing governance RED TAPE and mentoring individuals interested in these objectives. A brief history of time: I started my journey in OpenStack by doing a gap analysis of AWS to OpenkStack at my previous employer Red Hat,

Re: [openstack-dev] [Congress] New bug for Mitaka: Glance authentication fails after token expiry

Thanks for bringing this up Eric! On 3/29/16 4:01 PM, Eric K wrote: > I just discovered a bug that¹s probably been around a long time but hidden > by exception suppression. https://bugs.launchpad.net/congress/+bug/1563495 > When an auth attempt fails due to token expiry, Congress Glance driver >

[openstack-dev] [tripleo] The Future of Service Orchestration with Puppet & Pacemaker

Some TripleO folks are currently working hard on making automation for upgrading TripleO between major OpenStack releases. One of the biggest challenges is how to deal with Puppet who usually notify Services when configuration change and Pacemaker who actually manage the services. Currently, we

Re: [openstack-dev] [release][puppet] Puppet OpenStack 8.0.0 release (mitaka)

Congratulations to everyone involved :D 2016-03-29 16:32 GMT-03:00 Emilien Macchi : > On Tue, Mar 29, 2016 at 3:14 PM, Qasim Sarfraz > wrote: > > Awesome. > > > >> > Neutron: > >> > * Support of LBaaSv2 > >> > * More SDN integrations: OpenDayLight,

Re: [openstack-dev] [release][puppet] Puppet OpenStack 8.0.0 release (mitaka)

On Wed, Mar 30, 2016 at 12:32 AM, Emilien Macchi wrote: > On Tue, Mar 29, 2016 at 3:14 PM, Qasim Sarfraz > wrote: > > Awesome. > > > >> > Neutron: > >> > * Support of LBaaSv2 > >> > * More SDN integrations: OpenDayLight, PlugGrid, Midonet > >> > * Use

[openstack-dev] [Neutron]Relationship between physical networks and segment

Hi, I am writing a patchset to build a mapping between hosts and network segments. The goal of this mapping is to be able to say whether a host has access to a given network segment. I am building this mapping assuming that if a host A has a bridges mapping containing 'physnet 1' and a segment

Re: [openstack-dev] [release][puppet] Puppet OpenStack 8.0.0 release (mitaka)

On Tue, Mar 29, 2016 at 3:14 PM, Qasim Sarfraz wrote: > Awesome. > >> > Neutron: >> > * Support of LBaaSv2 >> > * More SDN integrations: OpenDayLight, PlugGrid, Midonet >> > * Use modern parameters for Nova notifications > > Just a minor correction, the SDN vendor is PLUMgrid

Re: [openstack-dev] [neutron][nova][stable][sr-iov] Status of physical_device_mappings

Hi jay, There was no ability to setup this configuration WITH Neutron SR-IOV ML2 agent in Liberty. That what you pointed out and you’re totally correct. But in Liberty, you’re not required to use Neutron SR-IOV ML2 agent to get this functionality works. And if you configure only nova-compute

[openstack-dev] [all] Service Catalog TNG work in Mitaka ... next steps

At the Mitaka Summit we had a double session on the Service Catalog, where we stood, and where we could move forward. Even though the service catalog isn't used nearly as much as we'd like, it's used in just enough odd places that every change pulls on a few other threads that are unexpected. So

Re: [openstack-dev] [release][puppet] Puppet OpenStack 8.0.0 release (mitaka)

Awesome. > Neutron: > > * Support of LBaaSv2 > > * More SDN integrations: OpenDayLight, PlugGrid, Midonet > > * Use modern parameters for Nova notifications > Just a minor correction, the SDN vendor is PLUMgrid here. -- Regards, Qasim Sarfraz

[openstack-dev] [Congress] New bug for Mitaka: Glance authentication fails after token expiry

I just discovered a bug that¹s probably been around a long time but hidden by exception suppression. https://bugs.launchpad.net/congress/+bug/1563495 When an auth attempt fails due to token expiry, Congress Glance driver obtains a new token from keystone and sets it in Glance client, but for some

Re: [openstack-dev] [Ironic]Nova resource tracker is not able to identify resources of BM instance when fake_pxe driver used

> On Mar 29, 2016, at 08:39, Senthilprabu Shanmugavel > wrote: > > Thanks Jim. WA did the trick. Very well explained. > > Should I raise a bug for fake driver's power state?. That would be great, thanks in advance! :) // jim > >> On Tue, Mar 29, 2016 at 5:30

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

Excerpts from Thomas Goirand's message of 2016-03-29 13:37:14 +0200: > On 03/29/2016 11:56 AM, Neil Jerram wrote: > > On 29/03/16 09:38, Thomas Goirand wrote: > >> On 03/23/2016 04:06 PM, Mike Perez wrote: > >>> Hey all, > >>> > >>> I've been talking to a variety of projects about lack of install

Re: [openstack-dev] [Neutron] Segments, subnet types, and IPAM

I've been playing with this a bit on this patch set [1]. I haven't gotten very far yet but it has me thinking. Calico has a similar use case in mind as I do. Essentially, we both want to group subnets to allow for aggregation of routes. (a) In routed networks, we want to group them by segment

Re: [openstack-dev] [magnum] Generate atomic images using diskimage-builder

Steve, I’m very interested in having an image locally cached in glance in each of the clouds used by OpenStack infra. The local caching of the glance images will produce much faster gate testing times. I don’t care about how the images are built, but we really do care about the performance

[openstack-dev] [release][stable][barbican] python-barbicanclient 4.0.1 release (mitaka)

We are psyched to announce the release of: python-barbicanclient 4.0.1: Client Library for OpenStack Barbican Key Management API This release is part of the mitaka stable release series. With source available at: https://git.openstack.org/cgit/openstack/python-barbicanclient/ Please

Re: [openstack-dev] [magnum] Generate atomic images using diskimage-builder

Yolanda, That is a fantastic objective. Matthieu asked why build our own images if the upstream images work and need no further customization? Regards -steve On 3/29/16, 1:57 AM, "Yolanda Robla Mota" wrote: >Hi >The idea is to build own images using

Re: [openstack-dev] [networking-ovn][Neutron] OVN support for routed networks(plugin interface for host mapping)

On Mon, Mar 21, 2016 at 12:26 PM, Russell Bryant wrote: > On Thu, Mar 17, 2016 at 1:45 AM, Hong Hui Xiao > wrote: > >> Hi Russell. >> >> Since the "ovn-bridge-mapping" will become accessible in OVN Southbound >> DB, do you meant that neutron plugin can

[openstack-dev] [kolla] containers are a hot topic at the operator summit

Fellow Kolla developers, If you plan to be in Austin on Monday of OpenStack Summit week, there is a fantastic opportunity for us to receive feedback from Operators that Carol Barrett pointed out to me. The official Operator summit schedule is yet to be defined. The Operator summit planning

Re: [openstack-dev] [openstack-ansible] OpenVSwitch support

On Tue, Mar 29, 2016 at 8:13 AM, Truman, Travis wrote: > Curtis, > > Please take a look at https://review.openstack.org/#/c/298765/ as its > probably a good place to start digging into OVS. > Perfect, thanks, am looking into it now. :) Thanks, Curtis. > Travis

[openstack-dev] [release][stable][horizon] django_openstack_auth 2.2.1 release (mitaka)

We are eager to announce the release of: django_openstack_auth 2.2.1: Django authentication backend for use with OpenStack Identity This release is part of the mitaka stable release series. With source available at: http://git.openstack.org/cgit/openstack/django_openstack_auth/ With

Re: [openstack-dev] [nova] Bug for image_cache_manager refactoring

Thanks Markus (and Hans)! --- Augustina Ragwitz Sr Systems Software Engineer, HPE Cloud Hewlett Packard Enterprise --- irc: auggy __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [release][puppet] Puppet OpenStack 8.0.0 release (mitaka)

On Mon, Mar 28, 2016 at 06:53:25PM -0400, Emilien Macchi wrote: > Puppet OpenStack team has the immense pleasure to announce the release > of 24 Puppet modules. > > Some highlights and major features: > > Keystone: > * Federation with Mellon support > * Support for multiple LDAP backends > *

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Please, propose your options here then: https://etherpad.openstack.org/p/shotgun-rename > 29 бер. 2016 р. о 18:15 Jay Pipes написав(ла): > > On 03/29/2016 08:41 AM, Roman Prykhodchenko wrote: >> Should we propose options and then arrange a poll? > > Yup, ++ :) > >>> 29

[openstack-dev] [release][all][ptl] release process changes for official projects

During the Mitaka cycle, the release team worked on automation for tagging and documenting releases [1]. For the first phase, we focused on official teams with the release:managed tag for their deliverables, to keep the number of projects manageable as we built out the tools and processes we

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

+1 - Original Message - From: "Paul Bourke" To: openstack-dev@lists.openstack.org Sent: Tuesday, March 29, 2016 12:10:38 PM Subject: Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer +1 On 29/03/16 17:07, Steven Dake (stdake) wrote:

Re: [openstack-dev] [release][puppet] Puppet OpenStack 8.0.0 release (mitaka)

Absolutely fantastic. Great job Emilien and the Puppet-Openstack team. We've made great progress cycle over cycle, and now have closed our release before most of the projects we support. On Mon, Mar 28, 2016 at 3:55 PM Emilien Macchi wrote: > Puppet OpenStack team has the

Re: [openstack-dev] [TripleO] gnocchi backport exception for stable/mitaka

On Tue, Mar 29, 2016 at 11:05:00AM -0400, Pradeep Kilambi wrote: > Hi Everyone: > > As Mitaka branch was cut yesterday, I would like to request a backport > exception to get gnocchi patches[1][2][3] into stable/mitaka. It > should low risk feature as we decided not to set ceilometer to use >

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

On 03/29/2016 08:41 AM, Roman Prykhodchenko wrote: Should we propose options and then arrange a poll? Yup, ++ :) 29 бер. 2016 р. о 16:40 Neil Jerram написав(ла): On 29/03/16 15:17, Jay Pipes wrote: Hi! Once Shotgun is pulled out of Fuel, may I suggest renaming

[openstack-dev] [Fuel] Component based testing pipeline

Dear colleagues, I have prepared a document [1] that describes some aspects of possible testing pipeline in a component based development environment. The main idea of the proposed pipeline is to untie two steps: 1) Merge the code to git 2) Adopt changes to Fuel By that I mean Fuel should be an

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

+1 On 29/03/16 17:07, Steven Dake (stdake) wrote: Hey folks, Consider this proposal a +1 in favor of Vikram joining the core reviewer team. His reviews are outstanding. If he doesn’t have anything useful to add to a review, he doesn't pile on the review with more –1s which are slightly

[openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

Hey folks, Consider this proposal a +1 in favor of Vikram joining the core reviewer team. His reviews are outstanding. If he doesn't have anything useful to add to a review, he doesn't pile on the review with more -1s which are slightly disheartening to people. Vikram has started a trend

Re: [openstack-dev] [neutron][dvr]Why keep SNAT centralized and DNAT distributed?

On Mon, Mar 28, 2016 at 7:25 PM, Wang, Yalei wrote: > Someone is working on full distributed SNAT, like this: > > https://www.openstack.org/summit/tokyo-2015/videos/presentation/network-node-is-not-needed-anymore-completed-distributed-virtual-router > > From: Zhi Chang

Re: [openstack-dev] [puppet] weekly meeting #76

rrow at 3pm UTC on > #openstack-meeting4. > > https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack > > As usual, free free to bring topics in this etherpad: > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160329 > > We'll also have open discussion f

[openstack-dev] [Heat] Mitaka RC2 available

Due to release-critical issues spotted in Heat during RC1 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarball at: https://tarballs.openstack.org/heat/heat-6.0.0.0rc2.tar.gz Unless new release-critical issues are found that warrant a last-minute

Re: [openstack-dev] [Ironic]Nova resource tracker is not able to identify resources of BM instance when fake_pxe driver used

Thanks Jim. WA did the trick. Very well explained. Should I raise a bug for fake driver's power state?. On Tue, Mar 29, 2016 at 5:30 PM, Jim Rollenhagen wrote: > On Tue, Mar 29, 2016 at 04:59:09PM +0300, Senthilprabu Shanmugavel wrote: > > Hello, > > > > I am using

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Should we propose options and then arrange a poll? > 29 бер. 2016 р. о 16:40 Neil Jerram написав(ла): > > On 29/03/16 15:17, Jay Pipes wrote: >> Hi! >> >> Once Shotgun is pulled out of Fuel, may I suggest renaming it to >> something different? I know in the past

Re: [openstack-dev] [Cinder] Mitaka RC2 available

Great, thanks! From: Duncan Thomas [mailto:duncan.tho...@gmail.com] Sent: 29 March 2016 4:01 PM To: OpenStack Development Mailing List (not for usage questions) Cc: openst...@lists.openstack.org Subject: Re: [openstack-dev] [Cinder] Mitaka RC2 available That

[openstack-dev] [nova][neutron] What to do about booting into port_security_enabled=False networks?

Nova has had some long-standing bugs that Sahid is trying to fix here [1]. You can create a network in neutron with port_security_enabled=False. However, the bug is that since Nova adds the 'default' security group to the request (if none are specified) when allocating networks, neutron

  1   2   >