Re: [openstack-dev] [tripleo][tripleo-heat-template] how to get interface name from network name in service profile

On Wed, Aug 2, 2017 at 5:21 AM, Zenghui Shi wrote: > > On Wed, 2 Aug 2017 at 02:34 Ben Nemec wrote: >> >> >> >> On 07/25/2017 09:53 PM, Zenghui Shi wrote: >> > Hi, >> > >> > Could anyone shed some light on how to get the physical interface name >> > (e.g

[openstack-dev] [election][glance] Queens PTL candidacy

I just submitted https://review.openstack.org/#/c/489834/ , which announces my candidacy as Glance PTL for the Queens cycle. This is what it says: Hello everyone, I'm asking for the opportunity to continue to serve as the PTL of Glance into the Queens cycle. Things looked good for Glance at

[openstack-dev] OpenStack Developer Mailing List Digest July 22-28

HTML version: https://www.openstack.org/blog/2017/08/openstack-developer-mailing-list-digest-20170728/ Summaries = * Nova placement/resource providers update 30 [1] * TC Report 30 [2] * POST /api-wg/news [3] * Release countdown for week R-4, July 28 - Aug 4 [4] * Technical Committee

Re: [openstack-dev] [requirements][release][oslo] FFE for oslo.policy

On Tue, Aug 01, 2017 at 06:32:36PM -0500, Matthew Thode wrote: > +1 here as well, my only concern is that this will need to be consumed > by so many projects. If the community consensus on this is to go > foraward with it then it's OK then. > >

Re: [openstack-dev] [release][requirements][barbican][octavia][LBaaS][heat] FFE Request for python-barbicanclient library

On Tue, Aug 01, 2017 at 04:58:22PM -0400, Doug Hellmann wrote: > Excerpts from Dave McCowan (dmccowan)'s message of 2017-08-01 20:48:12 +: > > This note is to request a Feature Freeze Exemption (FFE) for the > > python-barbicanclient library in Pike. > > > > Python-barbicanclient 4.5.0 was

Re: [openstack-dev] [tripleo][tripleo-heat-template] how to get interface name from network name in service profile

On Wed, 2 Aug 2017 at 02:34 Ben Nemec wrote: > > > On 07/25/2017 09:53 PM, Zenghui Shi wrote: > > Hi, > > > > Could anyone shed some light on how to get the physical interface name > > (e.g eth0) from network name (e.g PublicNetwork, ExternalNetwork) in > >

Re: [openstack-dev] [release][requirements][barbican][octavia][LBaaS][heat] FFE Request for python-barbicanclient library

I agree, this does seem like a fairly reasonable, limited impact change, it looks like we'd be adding the block to 4.5.1, when 4.5.2 hits UC.txt doesn't mater as much (unless it has something that NEEDS to be in pike, in which case we should probably be updating the minimum in GR.txt as well). I'm

Re: [openstack-dev] [requirements][release][oslo] FFE for oslo.policy

+1 here as well, my only concern is that this will need to be consumed by so many projects. If the community consensus on this is to go foraward with it then it's OK then. http://codesearch.openstack.org/?q=oslo.policy=nope=requirements.txt= On 17-08-01 16:58:53, Doug Hellmann wrote: > Excerpts

[openstack-dev] [Zun] Queens PTL candidacy

Hi all, I nominated myself to be a candidate of Zun PTL for Queens. As the founder of this project, it is my honor to work with all of you to build an innovative OpenStack container service. OpenStack provides a full-featured data center management solution which includes multi-tenant security,

[openstack-dev] [keystone] office hours report 2017-08-01

Hey all, Here is a condensed report of what was accomplished during office hours today. Most activity focused on reviewing fixes in flight. Full log can be found in IRC [0]. Bug #1635389 in OpenStack Identity (keystone): "keystone.contrib.ec2.controllers.Ec2Controller is untested"

Re: [openstack-dev] [tripleo] not running PTL during Queens

You've been a great leader and have done a good job herding all of us cats into one direction. It will be great to see where this project leads us to in the future. Keith On Sun, Jul 30, 2017 at 23:53 Emilien Macchi wrote: > Hi, > > After 3 cycles of Puppet OpenStack PTL

Re: [openstack-dev] [tripleo] not running PTL during Queens

Emilien, While I haven't worked closely on the implementation of TripleO, it has been a pleasure working with you as the PTL of TripleO. Your a great example of how to perform the service of the PTL and really demonstrate how cross-project collaboration can work effectively to achieve common

Re: [openstack-dev] [release][ptl] new "linter" rules for openstack/releases repository

Excerpts from Alex Schultz's message of 2017-08-01 13:56:53 -0600: > On Tue, Aug 1, 2017 at 1:45 PM, Doug Hellmann wrote: > > Excerpts from Alex Schultz's message of 2017-08-01 12:55:15 -0600: > >> On Tue, Aug 1, 2017 at 12:07 PM, Doug Hellmann > >>

Re: [openstack-dev] [requirements][release][oslo] FFE for oslo.policy

Excerpts from Davanum Srinivas (dims)'s message of 2017-08-01 16:38:13 -0400: > +1, i'd support this as the 2 commits in there are not in the > normal/runtime flow for oslo.policy and just touch the doc bits. +1 as well > > Thanks, > Dims > > On Tue, Aug 1, 2017 at 4:36 PM, Lance Bragstad

Re: [openstack-dev] [release][requirements][barbican][octavia][LBaaS][heat] FFE Request for python-barbicanclient library

Excerpts from Dave McCowan (dmccowan)'s message of 2017-08-01 20:48:12 +: > This note is to request a Feature Freeze Exemption (FFE) for the > python-barbicanclient library in Pike. > > Python-barbicanclient 4.5.0 was intended to be the Pike release. However, > after it was released,

Re: [openstack-dev] [release][requirements][barbican][octavia][LBaaS][heat] FFE Request for python-barbicanclient library

4.5.0 is already blocked. My +1 to block 4.5.1 as well. https://github.com/openstack/requirements/blob/master/global-requirements.txt The release team was waiting for a good barbicanclient release before branching as mentioned by Doug:

[openstack-dev] [release][requirements][barbican][octavia][LBaaS][heat] FFE Request for python-barbicanclient library

This note is to request a Feature Freeze Exemption (FFE) for the python-barbicanclient library in Pike. Python-barbicanclient 4.5.0 was intended to be the Pike release. However, after it was released, testing with the Heat and Octavia projects found that it contained an incompatible change

Re: [openstack-dev] [requirements][release][oslo] FFE for oslo.policy

> > Two fixes were made to the oslo.policy library (thanks, Doug!) that will > allow projects to render their entire policy document using the > show-policy directive. Both fixes have merged in oslo.policy master and > have been backported to stable/pike. I also have a release proposed to > cut a

Re: [openstack-dev] [requirements][release][oslo] FFE for oslo.policy

+1, i'd support this as the 2 commits in there are not in the normal/runtime flow for oslo.policy and just touch the doc bits. Thanks, Dims On Tue, Aug 1, 2017 at 4:36 PM, Lance Bragstad wrote: > I was cleaning up a few documentation things for keystone and noticed an >

[openstack-dev] [requirements][release][oslo] FFE for oslo.policy

I was cleaning up a few documentation things for keystone and noticed an issue with how the configuration reference was rendering. It turns out the oslo.policy library needed a few tweaks to the show-policy directive along with some changes to keystone that allowed us to properly render all

Re: [openstack-dev] [TripleO] Non-voting job for testing container builds against tripleo-common

On Tue, Aug 1, 2017 at 9:56 AM, David Moreau Simard wrote: > Hi, > > We temporarily stood up a third party job from review.rdoproject.org > for the tripleo-common project to test that container builds are not > broken as a result of a patch. > > For example, recently we took out

Re: [openstack-dev] [release][ptl] new "linter" rules for openstack/releases repository

On Tue, Aug 1, 2017 at 1:45 PM, Doug Hellmann wrote: > Excerpts from Alex Schultz's message of 2017-08-01 12:55:15 -0600: >> On Tue, Aug 1, 2017 at 12:07 PM, Doug Hellmann wrote: >> > The release team is working on a series of patches to improve the

Re: [openstack-dev] [release][ptl] new "linter" rules for openstack/releases repository

Excerpts from Alex Schultz's message of 2017-08-01 12:55:15 -0600: > On Tue, Aug 1, 2017 at 12:07 PM, Doug Hellmann wrote: > > The release team is working on a series of patches to improve the > > data validation within openstack/releases. Part of that work is to > > apply

[openstack-dev] [neutron] FFE for dns_domain for ports extension

Hi PTL/all I want to request an exception to include the dns_domain for ports extension in the Pike release. The extension is implemented by 3 patchsets, out of which [1] and [2] have already merged. The third patchset [3] is ready for reviews. The RFE can be found in [4]. Best regards Miguel

[openstack-dev] [all][docs] recruiting for help with documentation tools

With the changes we've made to docs processes upstream, every team is going to need to build up their knowledge of how the new documentation tools and jobs work. The docs team will still help, but things will obviously go more smoothly if folks know how the tools work, now that the bulk of the

[openstack-dev] [tc] [all] TC Report 31

(Rendered version: https://anticdent.org/tc-report-31.html ) Writing these reports is somewhat difficult when there hasn't been a meeting and we're in a crunch time in the release cycle. The things that have happened that are related to TC activity are disjointed, a bit hard to track, and hard

[openstack-dev] [sahara] Telles Nobrega candidacy for Sahara PTL

Hi all! I am announcing my candidacy for PTL for the Sahara team for the Queens release cycle. In case you don't know me, I'm tellesnobrega on IRC. I started working on Sahara in 2014 and became core in 2016 and not long after acted as PTL for Pike cycle. First of all, I would like to thank

Re: [openstack-dev] [release][ptl] new "linter" rules for openstack/releases repository

On Tue, Aug 1, 2017 at 12:07 PM, Doug Hellmann wrote: > The release team is working on a series of patches to improve the > data validation within openstack/releases. Part of that work is to > apply consistent formatting rules for all of the YAML files, so it > is easier to

Re: [openstack-dev] [oslo][oslo.db] nominating Jay Pipes for oslo-db-core

+1, always happy to have more contributors, especially to projects like oslo.db that almost everyone uses. On 07/27/2017 09:04 AM, Doug Hellmann wrote: I have noticed that Jay has been very deeply involved in several recent design discussions about oslo.db, and he obviously has a great deal of

Re: [openstack-dev] [tripleo][tripleo-heat-template] how to get interface name from network name in service profile

On 07/25/2017 09:53 PM, Zenghui Shi wrote: Hi, Could anyone shed some light on how to get the physical interface name (e.g eth0) from network name (e.g PublicNetwork, ExternalNetwork) in tripleo-heat-template service profile ? for example: I want to add a service profile under

[openstack-dev] [release][ptl] new "linter" rules for openstack/releases repository

The release team is working on a series of patches to improve the data validation within openstack/releases. Part of that work is to apply consistent formatting rules for all of the YAML files, so it is easier to build tools that automatically update those files. To enable those consistent rules,

[openstack-dev] [puppet] PTL wanted

It's an unusual request but we need a new PTL for Queens. Alex Schultz and I have been leading Puppet OpenStack modules for some time now and it's time to rotate. We know you're out there consuming (and contributing) to the modules - if you want this project to survive, it's time to step-up and

[openstack-dev] [TripleO] Non-voting job for testing container builds against tripleo-common

Hi, We temporarily stood up a third party job from review.rdoproject.org for the tripleo-common project to test that container builds are not broken as a result of a patch. For example, recently we took out EPEL with overrides and all containers built fine. After that, we introduced barbican

[openstack-dev] [elections][heat] Candidacy for Heat Project PTL (Queens)

Hi team, I would like to submit my name for Heat PTL for Queens release. I'd been involved with the project around two and half years. And it's my privilege to work and learn within this great team and have the honor to serve as Pike PTL. No doubt, heat already become the engine for other

Re: [openstack-dev] [all][ptl][docs] adding redirects for moved pages

Excerpts from Doug Hellmann's message of 2017-08-01 12:29:38 -0400: > When we started the doc-migration projects we knew that moving all > of the content around would break a lot of external links. We said > we would deal with it if we had time at the end of the cycle. We > have put the changes

[openstack-dev] [all][ptl][docs] adding redirects for moved pages

When we started the doc-migration projects we knew that moving all of the content around would break a lot of external links. We said we would deal with it if we had time at the end of the cycle. We have put the changes into place to allow us to do that now. I'm going to explain it here, and

Re: [openstack-dev] [security][barbican] PTG room sharing

On 8/1/17, 12:21 PM, "Thierry Carrez" wrote: >Luke Hinds wrote: >> Thanks Dave, I will let Kendall know that we can free up the room from >> Mon / Tuesday, and instead have the sec proj join barbican on Wed / >>Thur. > >Note that we have extra room on Monday/Tuesday, so

Re: [openstack-dev] [SPAM] Re: [security][barbican] PTG room sharing

Luke Hinds wrote: > Thanks Dave, I will let Kendall know that we can free up the room from > Mon / Tuesday, and instead have the sec proj join barbican on Wed / Thur. Note that we have extra room on Monday/Tuesday, so it would be OK to keep the room to have cross-project "security discussions",

[openstack-dev] [nova] Working toward Pike RC1

Now that we're past feature freeze for Pike, I've started an etherpad for tracking items needed to get done before the first release candidate here: https://etherpad.openstack.org/p/nova-pike-release-candidate-todo Just a reminder but Pike RC1 is Thursday August 10th. -- Thanks, Matt

[openstack-dev] [ironic] Dmitry Tantsur candidacy for Bare Metal (Ironic) PTL

Hi all! I am announcing my candidacy for PTL for the Ironic team for the Queens release cycle. In case you don't know me, I'm dtantsur on IRC. I started working on Ironic around late spring or summer 2014 (oh, time flies!), and has been dedicated full time to bare metal provisioning since then.

Re: [openstack-dev] [puppet] End of scheduled IRC meetings

On Tue, Aug 1, 2017 at 8:16 AM, Alex Schultz wrote: > Hey everyone, > > So over the last cycle as participation has dropped off, we've been > having less of the scheduled meetings. In today's meeting[0] it was > expressed that the formal meeting is nice but realistically it's

[openstack-dev] [election][release] Sean McGinnis candidacy for Release Management PTL

Hey everyone, I would like to submit my name for release management PTL for the Queens release. I've just recently been added to the core team, but I've been around for a few cycles interacting with the release management team. So I've been able to see the great work that they've done up to this

[openstack-dev] [elections][security] Candidacy for Security Project PTL (Queens)

Hello All, I would like to announce my candidacy for Security Project PTL for Queens. I have been a member of the Security Project for 2-3 years, and a core member for one year. During my tenure as core I have managed public and embargoed security notes and contributed with my feedback to the

[openstack-dev] [puppet] End of scheduled IRC meetings

Hey everyone, So over the last cycle as participation has dropped off, we've been having less of the scheduled meetings. In today's meeting[0] it was expressed that the formal meeting is nice but realistically it's more work than it's worth these days. So we will be dropping the formal schedule

[openstack-dev] [tripleo] tips to debug TripleO CI more easily

One of the feedback we've got during the TripleO QuickStart transition was "where do I find logs". We've implemented a README file that we hope will evolve but the basic piece is now in place. See for example:

[openstack-dev] [All][Trove] Adding Amrith candidacy for Trove.Queens

This email is to announce my candidacy for the PTL of Trove for the Queens cycle. My candidacy has been formally submitted in[1]. I have been the PTL for the Trove project since the Trove release (in March 2016). During this time, we've seen significant improvements during the Newton and Ocata

[openstack-dev] [CIX][dci][BZ:1449769][selinux-policy]RHEL7.4's keepalived breaks the undercloud+ssl

Hi, RACKSPACE enables SSL on ther undercloud. keepalived does not set up the VIP anymore (BZ1475505) because of a regression. This regression should be fixed by an update of selinux-policy (BZ1449769). This bug breaks the RAX/DCI configuration. Regards, -- Gonéri Le Bouder signature.asc

[openstack-dev] [FEMDC] IRC meeting Tomorrow 15:00 UTC

Dear all, As usual, the agenda is available at: https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 991) Please feel free to add items. Best, Ad_rien_ PS: Paul-André will chair the meeting (I'm taking some holidays ;))

Re: [openstack-dev] [security][barbican] PTG room sharing

On Tue, Aug 1, 2017 at 2:50 PM, Dave McCowan (dmccowan) wrote: > > Hello Barbican Team, > > I believe there were some discussions on room sharing between the security > project and barbican team. > > We are still keen on this in the security project. How would you like to >

Re: [openstack-dev] [security][barbican] PTG room sharing

Hello Barbican Team, I believe there were some discussions on room sharing between the security project and barbican team. We are still keen on this in the security project. How would you like to work out logistics? Should we share PTG planning etherpads? We have 4 days between us, not sure

[openstack-dev] [horizon] A Monitoring panel plugin for Horizon

Hi all, We are happy to share with you that we developed an AngularJS based usage monitoring panel for Horizon. The panel visualizes the collected utilization data by Ceilometer. Source code is now available on github [1]. The plugin consists of 3 panels; a monitoring panel for users, a

Re: [openstack-dev] [magnum] Interface configuration and assumptions for masters/minions launched by magnum

I'm going to assume we're talking about a typical environment with nova and neutron here. There are two separate boots to consider: 1. The IPA deployment ramdisk, which writes the user's image to the node's disk. 2. The user's image. Prior to 1, ironic communicates with neutron to apply

[openstack-dev] [Blazar] review meeting date for Pike release

Hi Blazar folks, As we discussed in the last weekly meeting, the team has a patch review meeting for Pike release. In the meeting the team reviews patches targeting to Pike release is ready to merge or not. And if not, we decide what's needed to fix before merge. The meeting date is 9am on

Re: [openstack-dev] [tricircle]

Hello, The problem was related to the proxy, I added the ip address of keystone to the variable no_proxy, so that Tricircle is now successfully installed in the two nodes. Regards, Meher [Logo Orange] Meher Hihi Intern ORANGE/IMT/OLN/WTC/CMA/MAX Fixe : +33 2 96 07 03

[openstack-dev] [keystone][kubernetes] Webhook PoC for Keystone based Authentication and Authorization for Kubernetes

Team, Having waded through the last 4 attempts as seen in kubernetes PR(s) and Issues and talked to a few people on SIG-OpenStack slack channel, the consensus was that we should use the Webhook mechanism to integrate Keystone and Kubernetes. Here's the experiment :

[openstack-dev] [publiccloud-wg] Reminder meeting PublicCloudWorkingGroup

Hi everyone, Don't forget tomorrows meeting for the PublicCloudWorkingGroup. A lot of important stuff to chat about =) 1400 UTC in IRC channel #openstack-meeting-3 Etherpad: https://etherpad.openstack.org/p/publiccloud-wg Regards, Tobias Rydberg smime.p7s Description: S/MIME Cryptographic

Re: [openstack-dev] [tc][kolla] Distribute Ansible module with Kolla

Steven Dake wrote: > Doung, > > The TC cannot provide legal advice as they are not attorneys (forgive me > if there are TC members that also have legal credentials coupled with a > legal degree). I'd suggest contacting your specific companies legal > counsel. If that doesn't yield results, you

Re: [openstack-dev] [neutron] FFE for midonet v2 plugin removal

On Tue, Aug 1, 2017 at 8:01 AM, Takashi Yamamoto wrote: > hi, > > I'm not sure if changes like this requires an FFE, but just in case. > I'd like to request an FFE for midonet v2 plugin removal. > > - patches are ready for review: https://review.openstack.org/#/c/486790/ >

Re: [openstack-dev] [tc][kolla] Distribute Ansible module with Kolla

Doung, The TC cannot provide legal advice as they are not attorneys (forgive me if there are TC members that also have legal credentials coupled with a legal degree). I'd suggest contacting your specific companies legal counsel. If that doesn't yield results, you might try the legal list. The

[openstack-dev] [tc][kolla] Distribute Ansible module with Kolla

Cross-post from [1] Hello everyone, I'm looking for legal advice about distribute Ansible module within Kolla. In order to implement one feature in Kolla, I need developing one Ansible strategy plugin, which in turn need to include and inherit from a couple modules from Ansible. Kolla does not