[openstack-dev] [kolla] Question about kolla git tag

Hi The image we built before is tagged automatically as 2.0.2. and now the kolla code has been upgrade to 2.0.3. I would like to ask if it is OK to use code 2.0.3 do deploy images 2.0.2, or we'd better to sync the version by using "git tag" command according to the image version? B.R., Zhiji

Re: [openstack-dev] [Zun][Higgins] Proposing Sudipta Biswas and Wenzhi Yu for Zun core reviewer team

+1 from me for both. From: Hongbin Lu [mailto:hongbin...@gmail.com] Sent: Wednesday, August 10, 2016 8:40 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Zun][Higgins] Proposing Sudipta Biswas and Wenzhi Yu for Zun core reviewer team Hi all, Both

[openstack-dev] [nova] The deprecation of proxy API related CLI

Hi, guys, We have agreement on how to deprecate the CLI for the proxy APIs which were deprecated in 2.36 when mid-cycle. But I still feels that we have something isn't very clear. So I just want to summary the situation at here, and to be clear the final goal. Here are the patches https://review.

Re: [openstack-dev] [Cinder] Pending removal of Scality volume driver

On Wed, Aug 10, 2016 at 11:26:28PM +0200, Nicolas Trangez wrote: > Sean and team, > > Sadly enough, we have been unable to resolve the recent issues in the > system/lab backing our CI server (originally caused by some hardware > migrations), and it's unclear when this would be back in a stable > s

[openstack-dev] [openstack-ansible] git repo in infra_repo container not working

Hi guys, I'm encounter new problems with the OSA SHA master eb3aec7827e78d81469ff4489c28963ee602117c (I use this version because previously the master version cf79d4f6 has problems with the nova transport_url settings which blocks nova-api to be launched), the problem is that the git repo in i

Re: [openstack-dev] [TripleO] additional git repo(s) for tripleo-quickstart

On Wed, Aug 10, 2016 at 03:26:18PM -0400, Wesley Hayutin wrote: > I'm proposing the creation of a repo called tripleo-quickstart-extras that > would contain some or all of the current third party roles used with > TripleO-Quickstart. Which roles in particular would you place in this -extras reposi

Re: [openstack-dev] [python-bileanclient] [infra] Duplicateentriesin test-requirement.txt

@Jeremy Stanley, thank you! -- Original -- From: "Jeremy Stanley"; Date: Wed, Aug 10, 2016 11:02 PM To: "OpenStack Development Mailing List (not for usage questions)"; Subject: Re: [openstack-dev] [python-bileanclient] [infra] Duplicateentriesin test-requ

Re: [openstack-dev] [ironic] static Portgroup support.

Thank you for creating these videos, they are great and certainly help my understanding! Michael... On Tue, Aug 9, 2016 at 5:58 PM, Vasyl Saienko wrote: > Hello Ironic'ers! > > We've recorded a demo that shows how static portgroup works at the moment: > > Flat network scenario: https://youtu.be

Re: [openstack-dev] [TripleO] Network Template Generator

On 08/10/2016 11:05 AM, Liz Blanchard wrote: > > > On Wed, Aug 10, 2016 at 11:52 AM, Ben Nemec > wrote: > > On 08/08/2016 09:22 PM, Dan Prince wrote: > > On Mon, 2016-08-08 at 15:42 -0500, Ben Nemec wrote: > >> This is something that has existed for a

[openstack-dev] Wiki upgrade maintenance 21:00 UTC Friday, August 12

On Friday, August 12, from approximately 21:00 to 23:00 UTC our Mediawiki instance on wiki.openstack.org will be upgraded from its present 1.25 pre-release to the latest 1.27 version. We're allotting two hours in case issues are encountered with the upgrade requiring us to roll back to a snapshot,

[openstack-dev] Brief Gerrit maintenance 20:00 UTC Friday, August 12

On Friday, August 12, at approximately 20:00 UTC our Gerrit service on review.openstack.org will be restarted for some minor patch updates and addition of a Storyboard integration plug-in. The outage is anticipated to run less than 5 minutes, though could go slightly longer if issues are encountere

Re: [openstack-dev] [all][ptl][tc] extra ATCs for newton

On 2016-08-11 08:25:00 +1000 (+1000), Michael Still wrote: [...] > At the time I proposed it for the tools directory in the governance repo, > but it never actually landed. [...] For reference: https://review.openstack.org/121730 -- Jeremy Stanley

Re: [openstack-dev] [Watcher] Promote Alexchadin to the core team.

+1 On Wed, Aug 10, 2016 at 4:13 AM, Antoine Cabot wrote: > +1 > > On Thu, Aug 4, 2016 at 9:29 AM, Vincent FRANÇOISE > wrote: > > Alexander Chadin did prove he knew the various moving parts of Watcher > > by participating the numerous design discussions and blueprints during > > the last months

Re: [openstack-dev] [all][ptl][tc] extra ATCs for newton

On Thu, Aug 11, 2016 at 7:38 AM, Doug Hellmann wrote: > Excerpts from Michael Still's message of 2016-08-11 07:27:07 +1000: > > On Thu, Aug 11, 2016 at 7:12 AM, Doug Hellmann > > wrote: > > > > > Excerpts from Michael Still's message of 2016-08-11 07:01:37 +1000: > > > > On Thu, Aug 11, 2016 at

Re: [openstack-dev] [all][ptl][tc] extra ATCs for newton

On 2016-08-11 07:01:37 +1000 (+1000), Michael Still wrote: > I have a script to generate this that I wrote while Nova PTL. [...] Note that, as one requirement for ATC status is being a current OpenStack Foundation Individual Member, there is still the manual step of confirming that for each potent

Re: [openstack-dev] [all][ptl][tc] extra ATCs for newton

Excerpts from Michael Still's message of 2016-08-11 07:27:07 +1000: > On Thu, Aug 11, 2016 at 7:12 AM, Doug Hellmann > wrote: > > > Excerpts from Michael Still's message of 2016-08-11 07:01:37 +1000: > > > On Thu, Aug 11, 2016 at 2:24 AM, Doug Hellmann > > > wrote: > > > > > > > It's time to mak

Re: [openstack-dev] [all][ptl][tc] extra ATCs for newton

On Thu, Aug 11, 2016 at 7:12 AM, Doug Hellmann wrote: > Excerpts from Michael Still's message of 2016-08-11 07:01:37 +1000: > > On Thu, Aug 11, 2016 at 2:24 AM, Doug Hellmann > > wrote: > > > > > It's time to make sure we have all of our active technical contributors > > > (ATCs) identified for

Re: [openstack-dev] [Cinder] Pending removal of Scality volume driver

Sean and team, On Wed, 2016-08-03 at 08:55 -0300, Erlon Cruz wrote: > Hi sean, I think it would worth to CC the contact info informed in > the CI > Wiki (openstack...@scality.com). > > On Tue, Aug 2, 2016 at 4:26 PM, Sean McGinnis > wrote: > > > > > Tomorrow is the one week grace period. I jus

Re: [openstack-dev] [all][ptl][tc] extra ATCs for newton

Excerpts from Michael Still's message of 2016-08-11 07:01:37 +1000: > On Thu, Aug 11, 2016 at 2:24 AM, Doug Hellmann > wrote: > > > It's time to make sure we have all of our active technical contributors > > (ATCs) identified for Newton. > > > > Following the Foundation bylaws [1] and TC Charter

[openstack-dev] [requirements] near term gate optimization opportunity

Based on reading some logs, it looks like requirements updates are getting regenerated on every requirements land for all open patches, even if they aren't impacted by it - https://review.openstack.org/#/c/351991/ patch 10,11,12 in that series are just rebases, all happening within a couple of hou

Re: [openstack-dev] [all][ptl][tc] extra ATCs for newton

On Thu, Aug 11, 2016 at 2:24 AM, Doug Hellmann wrote: > It's time to make sure we have all of our active technical contributors > (ATCs) identified for Newton. > > Following the Foundation bylaws [1] and TC Charter [2], Project > teams should identify contributors who have had a significant impac

Re: [openstack-dev] [ironic] static Portgroup support.

On 08/09/2016 01:28 AM, Vasyl Saienko wrote: > Hello Ironic'ers! > > We've recorded a demo that shows how static portgroup works at the moment: > > Flat network scenario: https://youtu.be/vBlH0ie6Lm4 > Multitenant network scenario: https://youtu.be/Kk5Cc_K1tV8 Awesome! Thank you for creating & s

Re: [openstack-dev] [requirements] History lesson please

On Tue, Aug 9, 2016 at 11:54 AM, Hayes, Graham wrote: > > It might not make a difference to deployers / packagers who only deploy > one project from OpenStack, but they are in the minority - having a > known good minimum for requirements helps deployers who have multiple > services to deploy. >

Re: [openstack-dev] [octavia] Multi-node controller testing

Miguel-- There have been a number of tempest patches in the review queue for a long time now, but I think the reason they're not getting attention is that we don't want to have to import a massive amount of tempest code into our repository (which will become stale and need hot-fixing, as has happe

[openstack-dev] [api] [doc] API status report

Hi all, I wanted to report on status and answer any questions you all have about the API reference and guide publishing process. The expectation is that we provide all OpenStack API information on developer.openstack.org. In order to meet that goal, it's simplest for now to have all projects use t

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wed, Aug 10, 2016 at 10:57 AM, Matthew Treinish wrote: > > http://specs.openstack.org/openstack/qa-specs/specs/tempest/implemented/ > branchless-tempest.html > > > This was actually a *great* read, thanks for that link! -Clay ___

[openstack-dev] [TripleO] additional git repo(s) for tripleo-quickstart

Greetings, In an effort to make TripleO CI composable and managed and governed by the TripleO project we have found the need to create additional git repos in openstack under the TripleO project. This could also be done outside of the TripleO project, but ideally it's in TripleO. I'm proposing

[openstack-dev] [tc] Storlets to become official - Proposed governance change

https://review.openstack.org/353693 Thanks! Eran __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/

[openstack-dev] App Catalog IRC meeting Thursday August 11th

Join us Thursday for our weekly meeting, scheduled for August 11th at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to discuss something with the Community App Catalog team: https://wiki.openstack.org/wiki/Meetings/app-catalog Tomorrow we will be tal

Re: [openstack-dev] [neutron] Feature Classification

On 10 August 2016 at 10:20, Gupta, Ankur wrote: > Hello Neutrinos, > > > > One of the things, that is required to have ease of use, is good > documentation. > > Similar to what's done for Nova [4], I've decided to prepare Feature > Classification for Neutron. > > Work was already approved, and it

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wed, Aug 10, 2016 at 10:57 AM, Matthew Treinish wrote: > We also test every incoming > tempest change on all the stable branches, and nothing can land unless it > works > on all supported branches. Did not know that, pretty awesome! > -Clay _

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wed, Aug 10, 2016 at 09:52:55AM -0700, Clay Gerrard wrote: > On Wed, Aug 10, 2016 at 7:42 AM, Ben Swartzlander > wrote: > > > > > A big source of problems IMO is that tempest doesn't have stable branches. > > We use the master branch of tempest to test stable branches of other > > projects, an

Re: [openstack-dev] [requirements] History lesson please

-Original Message- From: Chris Friesen Reply: OpenStack Development Mailing List (not for usage questions) Date: August 10, 2016 at 11:50:48 To: openstack-dev@lists.openstack.org Subject:  Re: [openstack-dev] [requirements] History lesson please > On 08/10/2016 04:51 AM, Erno Kuvaja wr

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wed, Aug 10, 2016 at 10:21 AM, Matthew Treinish wrote: > But, to keep the gate running > involves a lot of coordination between multiple projects that are tightly > coupled. Things like an entire extra set of job definitions in zuul, a > branch on > global requirements, a devstack branch, extr

Re: [openstack-dev] [ironic] About third-party CI

Excerpts from Jim Rollenhagen's message of 2016-08-10 13:21:11 -0400: > On Wed, Aug 10, 2016 at 1:05 PM, Clint Byrum wrote: > > Excerpts from Jim Rollenhagen's message of 2016-08-10 09:21:41 -0400: > >> 2) A number of drivers do not have third-party CI up, let alone reporting > >>on patches. U

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wed, Aug 10, 2016 at 09:56:09AM -0700, Clay Gerrard wrote: > On Mon, Aug 8, 2016 at 8:31 AM, Matthew Treinish > wrote: > > > When we EOL a branch all of the infrastructure for running any ci against > > it goes away. > > > But... like... version control? I mean I'm sure it's more complicate

Re: [openstack-dev] [ironic] About third-party CI

On Wed, Aug 10, 2016 at 1:05 PM, Clint Byrum wrote: > Excerpts from Jim Rollenhagen's message of 2016-08-10 09:21:41 -0400: >> 2) A number of drivers do not have third-party CI up, let alone reporting >>on patches. Unless someone moves quickly, I strongly suspect the following >>drivers wi

[openstack-dev] [neutron] Feature Classification

Hello Neutrinos, One of the things, that is required to have ease of use, is good documentation. Similar to what's done for Nova [4], I've decided to prepare Feature Classification for Neutron. Work was already approved, and it got greenlit [1], but we still lack of final approval. In the light

Re: [openstack-dev] [ironic] About third-party CI

Excerpts from Jim Rollenhagen's message of 2016-08-10 09:21:41 -0400: > 2) A number of drivers do not have third-party CI up, let alone reporting >on patches. Unless someone moves quickly, I strongly suspect the following >drivers will be dropped from our tree before the end of Newton. Thes

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Mon, Aug 8, 2016 at 8:31 AM, Matthew Treinish wrote: > When we EOL a branch all of the infrastructure for running any ci against > it goes away. But... like... version control? I mean I'm sure it's more complicated than that or you wouldn't have said this - but I don't understand, sorry. C

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wed, Aug 10, 2016 at 7:42 AM, Ben Swartzlander wrote: > > A big source of problems IMO is that tempest doesn't have stable branches. > We use the master branch of tempest to test stable branches of other > projects, and tempest regularly adds new features. > How come not this +1000 just fix t

Re: [openstack-dev] [requirements] History lesson please

On 08/10/2016 04:51 AM, Erno Kuvaja wrote: On Wed, Aug 10, 2016 at 9:27 AM, Thomas Goirand wrote: Not necessarily. Take for example Swift. It has lower requirements than other projects in OpenStack. Yet, Swift is fully co-installable with all other OpenStack projects. They just support lower

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wednesday, 10 August 2016 12:00:41 CEST Ben Swartzlander wrote: > On 08/10/2016 11:33 AM, Luigi Toscano wrote: > > On Wednesday, 10 August 2016 17:00:36 CEST Ihar Hrachyshka wrote: > >> Luigi Toscano wrote: > >>> On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote: > On 08/10

Re: [openstack-dev] [charms] nominating thedac for charms-release team

+1 On Tue, Aug 9, 2016 at 9:13 AM, James Page wrote: > On Mon, 8 Aug 2016 at 18:19 Ryan Beisner wrote: >> >> Greetings, >> >> I would like to nominate David Ames for addition to the >> charms-release team, as he has played a valuable role in the charm release >> processes. This change will gra

[openstack-dev] [all][ptl][tc] extra ATCs for newton

It's time to make sure we have all of our active technical contributors (ATCs) identified for Newton. Following the Foundation bylaws [1] and TC Charter [2], Project teams should identify contributors who have had a significant impact this cycle but who would not qualify for ATC status using the r

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On 19:42 Aug 09, Ben Swartzlander wrote: > Mike, you must have left the midcycle by the time this topic came up. On the > issue of out-of-tree drivers, I specifically offered this proposal (a > community managed mechanism for distributing driver bugfix backports) as an > compromise alternative to t

Re: [openstack-dev] [TripleO] Network Template Generator

On Wed, Aug 10, 2016 at 11:52 AM, Ben Nemec wrote: > On 08/08/2016 09:22 PM, Dan Prince wrote: > > On Mon, 2016-08-08 at 15:42 -0500, Ben Nemec wrote: > >> This is something that has existed for a while, but I had been > >> hesitant > >> to evangelize it until it was a little more proven. At thi

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On 08/10/2016 11:33 AM, Luigi Toscano wrote: On Wednesday, 10 August 2016 17:00:36 CEST Ihar Hrachyshka wrote: Luigi Toscano wrote: On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote: On 08/10/2016 04:33 AM, Duncan Thomas wrote: So I tried to get into helping with the cinder s

Re: [openstack-dev] [TripleO] Network Template Generator

On 08/08/2016 09:22 PM, Dan Prince wrote: > On Mon, 2016-08-08 at 15:42 -0500, Ben Nemec wrote: >> This is something that has existed for a while, but I had been >> hesitant >> to evangelize it until it was a little more proven. At this point >> I've >> used it to generate templates for a number o

Re: [openstack-dev] Nova mascot

On 08/10/2016 11:36 AM, Sean Dague wrote: > On 08/09/2016 07:30 PM, Heidi Joy Tretheway wrote: >> TL;DR: If you don’t want a mascot, you don’t have to. But Nova, you’ll >> be missed. :-) >> >> A few notes following up on Matt Riedemann, Clint Byrum, Daniel >> Berrange’s conversation regarding the N

Re: [openstack-dev] [ironic] About third-party CI

On Wed, Aug 10, 2016 at 8:21 AM, Jim Rollenhagen wrote: > Hi Ironicers, > > This email serves as a reminder (and a bit of a call to action) about our > third party CI policy: > http://specs.openstack.org/openstack/ironic-specs/specs/ > not-implemented/third-party-ci.html > > 1) When I went to fin

Re: [openstack-dev] [ironic] About third-party CI

On Wed, Aug 10, 2016 at 9:21 AM, Jim Rollenhagen wrote: > Hi Ironicers, > > This email serves as a reminder (and a bit of a call to action) about our > third party CI policy: > http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/third-party-ci.html > > 1) When I went to find a

Re: [openstack-dev] Nova mascot

On 08/09/2016 07:30 PM, Heidi Joy Tretheway wrote: > TL;DR: If you don’t want a mascot, you don’t have to. But Nova, you’ll > be missed. :-) > > A few notes following up on Matt Riedemann, Clint Byrum, Daniel > Berrange’s conversation regarding the Nova mascot… > > Nova doesn’t have to have a mas

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wednesday, 10 August 2016 17:00:36 CEST Ihar Hrachyshka wrote: > Luigi Toscano wrote: > > On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote: > >> On 08/10/2016 04:33 AM, Duncan Thomas wrote: > >>> So I tried to get into helping with the cinder stable tree for a while, > >>> and

Re: [openstack-dev] [tripleo] Fernet Key rotation

On 09/08/16 21:21, Adam Young wrote: On 08/09/2016 06:00 PM, Zane Bitter wrote: In either case a good mechanism might be to use a Heat Software Deployment via the Heat API directly (i.e. not as part of a stack) to push changes to the servers. (I say 'push' but it's more a case of making the dat

Re: [openstack-dev] Nova mascot

On 08/10/2016 11:19 AM, Szankin, Maciej wrote: > While supernova looks super cool on photographs, I frankly have no idea > how this could look like a logo. You know, the cartoonish style. Tried > to google for examples, but they do look terrible… That's why you have graphics designers try a thing.

Re: [openstack-dev] [all][tc][ptl] establishing project-wide goals

Excerpts from Doug Hellmann's message of 2016-07-29 16:55:22 -0400: > One of the outcomes of the discussion at the leadership training > session earlier this year was the idea that the TC should set some > community-wide goals for accomplishing specific technical tasks to > get the projects synced

Re: [openstack-dev] [tripleo] Fernet Key rotation

On 09/08/16 18:28, Fox, Kevin M wrote: It needs to work in a distributed way... What happens if the one node you have cron running on doesn't work for a while. Keystone breaks? IIUC it wouldn't break, but your keys wouldn't get rotated so you'd end up using the same key until such time as yo

Re: [openstack-dev] Nova mascot

While supernova looks super cool on photographs, I frankly have no idea how this could look like a logo. You know, the cartoonish style. Tried to google for examples, but they do look terrible… From: Bob Ball [mailto:bob.b...@citrix.com] Sent: Wednesday, August 10, 2016 6:37 AM To: OpenStack Dev

[openstack-dev] [Zun][Higgins] Proposing Sudipta Biswas and Wenzhi Yu for Zun core reviewer team

Hi all, Both Sudipta and Wenzhi have been actively contributing to the Zun project for a while. Sudipta provided helpful advice for the project roadmap and architecture design. Wenzhi consistently contributed high quality patches and insightful reviews. I think both of them are qualified to join t

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On 10/08/2016 16:04, Ihar Hrachyshka wrote: > Luigi Toscano wrote: > >> On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote: >>> On 08/10/2016 04:33 AM, Duncan Thomas wrote: So I tried to get into helping with the cinder stable tree for a while, and while I wasn't very succ

Re: [openstack-dev] [python-bileanclient] [infra] Duplicate entriesin test-requirement.txt

On 2016-08-10 10:46:23 +0800 (+0800), 吕冬兵 wrote: > The issue still exists after the > https://review.openstack.org/352490 merged, what else should I do? > http://logs.openstack.org/58/351458/8/check/gate-python-bileanclient-requirements/fa1119c/console.html That change was for a script which gets

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

Luigi Toscano wrote: On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote: On 08/10/2016 04:33 AM, Duncan Thomas wrote: So I tried to get into helping with the cinder stable tree for a while, and while I wasn't very successful (lack of time and an inability to convince my employe

Re: [openstack-dev] [neutron] Neutron Port MAC Address Uniqueness

Miguel, I talked to our driver architect and according to him this is vendor implementation (according to him this should work with Mellanox NIC) I need to verify that this indeed working. I will update after I will prepare SR-IOV setup and try it myself. -Original Message- From: Mi

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wednesday, 10 August 2016 10:42:41 CEST Ben Swartzlander wrote: > On 08/10/2016 04:33 AM, Duncan Thomas wrote: > > So I tried to get into helping with the cinder stable tree for a while, > > and while I wasn't very successful (lack of time and an inability to > > convince my employer it should b

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On 08/10/2016 04:33 AM, Duncan Thomas wrote: So I tried to get into helping with the cinder stable tree for a while, and while I wasn't very successful (lack of time and an inability to convince my employer it should be a priority), one thing I did notice it that much of the breakage seemed to co

Re: [openstack-dev] [vitrage] spec for datasource

From: Yujun Zhang Date: Tuesday, 9 August 2016 at 14:48 1. How do I register a new datasource in an existing system? [yujunz] It seems to be in https://github.com/openstack/vitrage/blob/master/vitrage/datasources/__init__.py Not exactly. This file defines the default datasources to be used. You

Re: [openstack-dev] [tripleo] Fernet Key rotation

On 08/09/2016 05:11 PM, Adam Young wrote: The Fernet token format uses a symmetric key to sign tokens. In order to check the signature, these keys need to be synchronized across all of the Keystone servers. I don't want to pass around nake symmetric keys. The right way to do this is to put

Re: [openstack-dev] [tripleo] Fernet Key rotation

On 08/09/2016 09:21 PM, Adam Young wrote: On 08/09/2016 06:00 PM, Zane Bitter wrote: In either case a good mechanism might be to use a Heat Software Deployment via the Heat API directly (i.e. not as part of a stack) to push changes to the servers. (I say 'push' but it's more a case of making

Re: [openstack-dev] [puppet] proposal: start gating on puppet4

+1 from me also. This will help everyone who is trying to transition to it. On Wed, Aug 10, 2016 at 1:46 AM, Javier Pena wrote: > > > - Original Message - > > Hi, > > > > Today Puppet OpenStack CI is running unit and functional test jobs > > against puppet 3 and puppet 4. > > Unit jobs f

[openstack-dev] [meghdwar] Incubation Patches and irc call agenda

Please join the meeting  for Incubation and ptaches decision  Meeting Wednesday 10th (14 Hr-15 Hr UTC )   [7AM-8AM PDT] irc #openstck-megdwar Follow up1 The last week agenda and actions taken or pending 2 Meghdwar Gateway API discussions https://review.openstack.org/#/c/319466/ https://rev

Re: [openstack-dev] [neutron][networking-ovs-dpdk] conntrack security group driver with ovs-dpdk

Hi, > [Mooney, Sean K] > In ovs 2.5 only linux kernel conntrack was supported assuming you had a 4.x > kernel that supported it. that means that the feature was not available on > bsd,windows or with dpdk. Yup, I also thought about something like that. I think I was at-least-slightly misguided by

[openstack-dev] Is there a logging_exception_prefix option for Neutron (Juno) ?

Hi, Does anyone know if the Neutron Juno release logging conf allows options such as: logging_exception_prefix, logging_debug_format_suffix, logging_default_format_string, logging_context_format_string like the other general OS services? >From the Juno doc ( http://docs.openstack.org/juno/config-

[openstack-dev] [ironic] About third-party CI

Hi Ironicers, This email serves as a reminder (and a bit of a call to action) about our third party CI policy: http://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/third-party-ci.html 1) When I went to find a link to the policy, I realized that it isn't in our developer docs

[openstack-dev] [new][neutron] python-neutronclient 5.1.0 release (newton)

We are chuffed to announce the release of: python-neutronclient 5.1.0: CLI and Client Library for OpenStack Networking This release is part of the newton release series. With source available at: https://git.openstack.org/cgit/openstack/python-neutronclient With package available at:

Re: [openstack-dev] [requirements] History lesson please

On 08/10/2016 07:30 AM, Ian Cordasco wrote: > To be clear, I think the requirements work Tony is doing has the potential to > make things worse for some subset of deployers/operators. > > -- > Ian Cordasco Any change we make has the potential to make things worse for some subset :P -- -- Mat

Re: [openstack-dev] Nova mascot

> TL;DR: If you don’t want a mascot, you don’t have to. But Nova, you’ll be > missed. :-) It also seems from http://www.openstack.org/project-mascots that the majority of OpenStack projects have selected a mascot. I think it would be a great shame if the Nova project didn’t have an easily reco

[openstack-dev] [new][oslo] taskflow 2.5.0 release (newton)

We are exuberant to announce the release of: taskflow 2.5.0: Taskflow structured state management library. This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/taskflow With package available at: https://pypi.python.org/p

Re: [openstack-dev] [requirements] History lesson please

  -Original Message- From: Erno Kuvaja Reply: OpenStack Development Mailing List (not for usage questions) Date: August 10, 2016 at 05:53:14 To: OpenStack Development Mailing List (not for usage questions) Subject:  Re: [openstack-dev] [requirements] History lesson please > On Wed, A

[openstack-dev] [new][oslo] oslo.versionedobjects 1.15.0 release (newton)

We are glowing to announce the release of: oslo.versionedobjects 1.15.0: Oslo Versioned Objects library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.versionedobjects With package available at: https://pypi.py

[openstack-dev] [new][oslo] oslo.serialization 2.13.0 release (newton)

We are exuberant to announce the release of: oslo.serialization 2.13.0: Oslo Serialization library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.serialization With package available at: https://pypi.python.org

[openstack-dev] [new][oslo] oslo.service 1.15.0 release (newton)

We are delighted to announce the release of: oslo.service 1.15.0: oslo.service library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.service With package available at: https://pypi.python.org/pypi/oslo.service

[openstack-dev] [new][oslo] oslo.vmware 2.13.0 release (newton)

We are pleased to announce the release of: oslo.vmware 2.13.0: Oslo VMware library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.vmware With package available at: https://pypi.python.org/pypi/oslo.vmware Plea

[openstack-dev] [new][oslo] oslo.rootwrap 5.1.0 release (newton)

We are mirthful to announce the release of: oslo.rootwrap 5.1.0: Oslo Rootwrap This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.rootwrap With package available at: https://pypi.python.org/pypi/oslo.rootwrap Plea

[openstack-dev] [new][oslo] oslo.messaging 5.7.0 release (newton)

We are thrilled to announce the release of: oslo.messaging 5.7.0: Oslo Messaging API This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.messaging With package available at: https://pypi.python.org/pypi/oslo.messagi

[openstack-dev] [new][oslo] oslo.reports 1.14.0 release (newton)

We are tickled pink to announce the release of: oslo.reports 1.14.0: oslo.reports library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.reports With package available at: https://pypi.python.org/pypi/oslo.repo

[openstack-dev] [new][oslo] oslo.policy 1.14.0 release (newton)

We are joyful to announce the release of: oslo.policy 1.14.0: Oslo Policy library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.policy With package available at: https://pypi.python.org/pypi/oslo.policy Pleas

[openstack-dev] [new][oslo] oslo.log 3.14.0 release (newton)

We are gleeful to announce the release of: oslo.log 3.14.0: oslo.log library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.log With package available at: https://pypi.python.org/pypi/oslo.log Please report is

[openstack-dev] [new][oslo] oslo.middleware 3.17.0 release (newton)

We are glowing to announce the release of: oslo.middleware 3.17.0: Oslo Middleware library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.middleware With package available at: https://pypi.python.org/pypi/oslo.

[openstack-dev] [new][oslo] oslo.config 3.15.0 release (newton)

We are frolicsome to announce the release of: oslo.config 3.15.0: Oslo Configuration API This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.config With package available at: https://pypi.python.org/pypi/oslo.config

[openstack-dev] [new][oslo] oslo.db 4.11.0 release (newton)

We are frolicsome to announce the release of: oslo.db 4.11.0: Oslo Database library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.db With package available at: https://pypi.python.org/pypi/oslo.db Please repo

[openstack-dev] [new][oslo] oslo.context 2.8.0 release (newton)

We are gleeful to announce the release of: oslo.context 2.8.0: Oslo Context library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.context With package available at: https://pypi.python.org/pypi/oslo.context P

[openstack-dev] [new][oslo] debtcollector 1.8.0 release (newton)

We are overjoyed to announce the release of: debtcollector 1.8.0: A collection of Python deprecation patterns and strategies that help you collect your technical debt in a non- destructive manner. This release is part of the newton release series. With source available at: http://git.openst

Re: [openstack-dev] Use the zmq as message backend for Opnestack components

Hi, The general answer is: yes! it is possible for all services except Ceilometer yet. RPC use case is 100% covered, but Ceilometer uses Notifications which are partly supported in zmq backend because they need some persistence when consumer is not present etc. For all the other services (Nov

[openstack-dev] Use the zmq as message backend for Opnestack components

Hello, I wanted to uset he zmq as message Q for all Openstack components like, Nova, glance, cinder, Ceilmeter,etc (just replace the default rabbitmq with zmq). Is it possible to do this? Please advise. Thanks Swami __ Open

Re: [openstack-dev] [requirements] History lesson please

On Wed, Aug 10, 2016 at 9:27 AM, Thomas Goirand wrote: > On 08/09/2016 08:33 PM, Ian Cordasco wrote: >> >> >> -Original Message- >> From: John Dickinson >> Reply: OpenStack Development Mailing List (not for usage questions) >> >> Date: August 9, 2016 at 13:17:08 >> To: OpenStack Develop

Re: [openstack-dev] [nova] os-capabilities library created

On Wed, 3 Aug 2016, Jay Pipes wrote: Let me know what you think about the structure of the library and whether you would be interested in owning additions to the library of constants in your area of expertise. Seems mostly sane to me. I don't really care for the inspection of sys.modules (or

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

On Wed, Aug 10, 2016 at 11:33:52AM +0300, Duncan Thomas wrote: > So I tried to get into helping with the cinder stable tree for a while, and > while I wasn't very successful (lack of time and an inability to convince > my employer it should be a priority), one thing I did notice it that much > of t

[openstack-dev] [tricircle]agenda of weekly meeting Aug.10

Hello, team, Cross pod L2 networking(shared VLAN) has made good progress, let's continue the discussion: IRC meeting: https://webchat.freenode.net/?channels=openstack-meetingon every Wednesday starting from UTC 13:00. The agenda of this weekly meeting is: # progress review in feature

Re: [openstack-dev] [Cinder] [stable] [all] Changing stable policy for drivers

Duncan Thomas wrote: So I tried to get into helping with the cinder stable tree for a while, and while I wasn't very successful (lack of time and an inability to convince my employer it should be a priority), one thing I did notice it that much of the breakage seemed to come from outside c

  1   2   >