[openstack-dev] [tripleo] os-apply-config 6.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for os-apply-config for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/os-apply-config/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [tripleo] os-cloud-config 6.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for os-cloud-config for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/os-cloud-config/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [tripleo] os-net-config 6.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for os-net-config for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/os-net-config/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

[openstack-dev] [tripleo] os-refresh-config 6.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for os-refresh-config for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/os-refresh-config/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] [tripleo] os-collect-config 6.0.0.0rc1 (ocata)

Hello everyone, A new release candidate for os-collect-config for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/os-collect-config/ Unless release-critical issues are found that warrant a release candidate respin, this

Re: [openstack-dev] [puppet] Nominating mkarpin for core for the Puppet OpenStack modules

Thank you very much for this opportunity! I learned a lot from you and I will do my best to continue improving puppet modules! On 01/26/2017 07:32 PM, Alex Schultz wrote: On Thu, Jan 19, 2017 at 3:25 PM, Alex Schultz wrote: Hey Puppet Cores, I would like to nominate

Re: [openstack-dev] [neutron-lbaas][barbican][octavia]certs don't get deregistered in barbican after lbaas listener delete

Yeah, I believe it was because we intended to leave it up to the specific certificate manager to determine what needs to be done -- we are treating it as a delete, and if the cert manager wants to do a true delete, they can. I'll agree the verb is not perfectly clear, but the driver author should

[openstack-dev] [Nova] FFE Request for "restore-vm-diagnostics"

Hi, folks! I'm asking a FFE for restore-vm-diagnostics [1]. There are 3 patches and yesterday I had five +2 on them from Alex Xu, Stephen Finucane and John Garbutt. Unfortunatly I lost 3 of them because of nits fixing. I mean that patches are totally ready for merge and it would be a pity to move

Re: [openstack-dev] [OpenStack-I18n] What's Up, Doc? Farewell edition

I am sad too ☹ end of an era. Looking forward to what we can achieve together ☺ Thank you to everyone for your support ☺ On 1/27/17, 1:17 AM, "Lana Brindley" wrote: Hi everyone, I must confess, I'm feeling a little sad. This is my very last What's

Re: [openstack-dev] [cinder][nova] Cinder-Nova API changes meeting

Hi All, According to the results of our Doodle poll, the new meeting day will be __Thursday__ starting from next week. The time slot and the meeting channel are supposed to remain the same, I hope the patch [1] to register the changes gets merged soon to make it fully official. In this sense,

[openstack-dev] [nova] The status of servers API's filters

The patches about validation the filters and sorts for servers API are merged [0]. But we still have something left [1]. The left is about the proposal of introducing the new rule 'os_compute_api:servers:all_tenants_visible' which is soft enforcement. The new rule will instead of the old hard

[openstack-dev] [FFE][requirements] python-* clients from last 2 days

Dear requirements team, Can you please allow the following to merge: https://review.openstack.org/#/q/owner:%22OpenStack+Proposal+Bot%22+status:open+project:openstack/requirements+branch:master+topic:new-release -- Davanum Srinivas :: https://twitter.com/dims

Re: [openstack-dev] [FFE][requirements] python-* clients from last 2 days

Oops hit send too soon. Technically the release deadline was till today (27th) https://releases.openstack.org/ocata/schedule.html If we have a release and do not have that in upper constraints and hence haven't tested it, bad things can happen in the field. Thanks, Dims On Fri, Jan 27, 2017 at

[openstack-dev] [nova] placement/resource providers update 9

There was no update last week because I was away. This week's will be short as we're facing some challenges getting last minutes resource provider and placement things through the gate. We'll just do: What Matters Most = There are two priorty changes in progress that we want to

Re: [openstack-dev] [FFE][requirements] python-* clients from last 2 days

Dear Requirements Team, I've consolidated the changes to the upper-constraints into One single review: https://review.openstack.org/#/c/426116/ Thanks, Dims On Fri, Jan 27, 2017 at 5:58 AM, Davanum Srinivas wrote: > Oops hit send too soon. > > Technically the release

Re: [openstack-dev] [FFE][requirements] python-* clients from last 2 days

Hi Dims, 2017-01-27 13:51 GMT+01:00 Davanum Srinivas : > I've consolidated the changes to the upper-constraints into One single review: > https://review.openstack.org/#/c/426116/ I'm ok with it if we have release team buy in. Greetings, Dirk

Re: [openstack-dev] [neutron]

Hi. Do you have a pointer to how you extended the driver to have this? Thanks! Ricardo On Fri, Nov 18, 2016 at 2:02 PM, ZZelle wrote: > Hello, > > AFAIK, it's not possible. > > I did a similar thing by extending neutron iptables driver in order to set > "pre-rules". > > Best

Re: [openstack-dev] [tripleo] tripleo-heat-templates, vendor plugins and the new hiera hook

On Wed, 2017-01-25 at 14:59 +0200, Marios Andreou wrote: > Hi, as part of the composable upgrades workflow shaping up for Newton > to > Ocata, we need to install the new hiera hook that was first added > with > [1] and disable the old hook and data as part of the upgrade > initialization [2]. Most

[openstack-dev] [openstack-ansible] Proposing Amy Marrich for core

Hi OpenStack-Ansible team, I would like to propose Amy Marrich for the core team for OpenStack-Ansible. Amy has been consistently in the top 10 reviewers for our team in the last 30 [1] and 90 [2] days, respectively, this release alone. She has been an active and diligent member of the

Re: [openstack-dev] [openstack-ansible] Proposing Amy Marrich for core

+1 on spotz for core. I can always count on Amy to provide great reviews. Travis Truman From: Alexandra Settle > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [tripleo] tripleo-heat-templates, vendor plugins and the new hiera hook

On 27/01/17 16:23, Dan Prince wrote: > On Wed, 2017-01-25 at 14:59 +0200, Marios Andreou wrote: >> Hi, as part of the composable upgrades workflow shaping up for Newton >> to >> Ocata, we need to install the new hiera hook that was first added >> with >> [1] and disable the old hook and data as

Re: [openstack-dev] [openstack-ansible] Proposing Amy Marrich for core

+1 from me too. Thanks for your contributions so far Amy, glad to have you as part of the community. Andy __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [openstack-ansible] Proposing Amy Marrich for core

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/27/2017 08:29 AM, Alexandra Settle wrote: > I would like to propose Amy Marrich for the core team for OpenStack-Ansible. +3.14 - -- Major Hayden -BEGIN PGP SIGNATURE- Version: GnuPG v2

[openstack-dev] [requirements][stable][relmgt] PTG prep

Hi! The requirements team, the stable maintenance team and the release management team will share a single room on the Monday and Tuesday of the PTG. Since we don't all need 2 full days of coordination (and several of us need to also attend some other team meeting at the same time), I propose we

Re: [openstack-dev] [openstack-ansible] Proposing Amy Marrich for core

-Original Message- From: Major Hayden Reply: OpenStack Development Mailing List (not for usage questions) Date: January 27, 2017 at 08:52:58 To: openstack-dev@lists.openstack.org Subject:  Re:

[openstack-dev] [OpenStack][Dev] Changes coming to Product WG & Enterprise WG

After 35+ yrs in the Technology Industry, I have decided it's time for a change. I will be retiring from Intel on February 2nd. OpenStack has been a highlight of my career and I owe much of that to you all. It's been a pleasure knowing and working with you. Yih Leong Sun (aka Leong) will be

Re: [openstack-dev] [glance] priorities for the coming week (01/27-02/02)

I'm working on that patch, Ian. -Hemanth From: Ian Cordasco Sent: Friday, January 27, 2017 9:53 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [glance] priorities for the coming

Re: [openstack-dev] [glance] priorities for the coming week (01/27-02/02)

-Original Message- From: Brian Rosmaita Reply: OpenStack Development Mailing List (not for usage questions) Date: January 26, 2017 at 17:03:58 To: OpenStack Development Mailing List

Re: [openstack-dev] [OpenStack][Dev] Changes coming to Product WG & Enterprise WG

Barrett, Carol L wrote: > After 35+ yrs in the Technology Industry, I have decided it’s time for a > change. I will be retiring from Intel on February 2^nd . > > OpenStack has been a highlight of my career and I owe much of that to > you all. It’s been a pleasure knowing and working with you.

Re: [openstack-dev] [puppet] Nominating zhongshengping for core of the Puppet OpenStack modules

On Fri, Jan 20, 2017 at 10:19 AM, Alex Schultz wrote: > Hey Puppet Cores, > > I would like to nominate Zhong Shengping as a Core reviewer for the > Puppet OpenStack modules. He is an excellent contributor to our > modules over the last several cycles. His stats for the last

Re: [openstack-dev] [neutron-lbaas][barbican][octavia]certs don't get deregistered in barbican after lbaas listener delete

Frankie, What is the reason why the cert has to be deleted on the balancer deletion? The entire workflow, if I'm not mistaken, is to first work with Barbican API in order to create the cert bundle. And technically it is not yet connected to anything else. After that you create the balancer,

Re: [openstack-dev] [neutron] [ovo] unhashable type error

On 1/25/17, 1:59 PM, "Ihar Hrachyshka" wrote: > Looking at the code, I don't see a clear case to even use set() type > there. A list would seem to work just fine. Should we try to convert > to using lists there? I will convert it into a list and check how it works.

Re: [openstack-dev] [neutron-lbaas][barbican][octavia]certs don't get deregistered in barbican after lbaas listener delete

Hi, The idea was that we would like to let the user know in Barbican when the certificate is being used with LBaaS. Therefore, we added the register and de-register logic. I don’t know of any use case where a certificate needs to be deleted in Barbican when LBaaS doesn’t need it any longer.

Re: [openstack-dev] [neutron-lbaas][barbican][octavia]certs don't get deregistered in barbican after lbaas listener delete

Hi German, Once again, we are not talking about a real delete of a cert in whatever cert storage. The problem we are trying to resolve is, even the lbaas is deleted, users still see the lbaas is using the cert in Barbican. We didn't call the deregister logic during lbaas deletion. Best, On

Re: [openstack-dev] [OpenStack][Dev] Changes coming to Product WG & Enterprise WG

Excerpts from Barrett, Carol L's message of 2017-01-27 15:56:21 +: > After 35+ yrs in the Technology Industry, I have decided it's time for a > change. I will be retiring from Intel on February 2nd. > > OpenStack has been a highlight of my career and I owe much of that to you > all. It's

Re: [openstack-dev] [neutron-lbaas][barbican][octavia]certs don't get deregistered in barbican after lbaas listener delete

Hi Andrey, The reason Barbican cert container has a property called consumer. The definition is as following: > What is a Consumer? > > >> A consumer is a way to register as an interested party for a container. >> All of the registered consumers can be viewed by performing a GET on the >>

Re: [openstack-dev] [openstack-ansible] Proposing Amy Marrich for core

+1 Amy's been giving helpful reviews for a long time. On Fri, Jan 27, 2017 at 7:54 AM, Ian Cordasco wrote: > -Original Message- > From: Major Hayden > Reply: OpenStack Development Mailing List (not for usage questions) >

[openstack-dev] [nova][qa] gate-grenade-dsvm-neutron-multinode-live-migration-nv is 100% fail since 1/21

I noticed that this job is 100% failure since 1/21: http://tinyurl.com/zjh5bc5 http://logs.openstack.org/61/417961/40/check/gate-grenade-dsvm-neutron-multinode-live-migration-nv/8c363cd/logs/devstack-gate-post_test_hook.txt.gz#_2017-01-27_23_43_40_367 For whatever reason, live_migration=False

[openstack-dev] [Zun] PTL candidacy

Hi all, This is the first time Zun participants on official PTL election, which is exciting. I nominated myself to be a candidate of Zun PTL. As the founder of this project, it is my honor to work with all of you to build an innovative container service for OpenStack. Since April 2016, in which

Re: [openstack-dev] [networking-sfc]

Networking-sfc features are available to orchestrate using a TOSCA template through Tacker. The feature is called VNF Forwarding Graph (VNFFG) and it is available both through tacker cli and horizon screens. See tacker docs here for more details,

[openstack-dev] OpenStack Developer Mailing List Digest January 21-27

HTML version: https://www.openstack.org/blog/2017/01/openstack-developer-mailing-list-digest-20170127/ SuccessBot Says === * dims [1] : Nova now has a python35 based CI job in check queue running Tempest tests (everything running on py35) * markvoelker [2]: Newly published

[openstack-dev] [release] libraries that still need stable/ocata branches

We are now past the library release freeze, and all libraries should have their final release and be ready for a stable/ocata branch. The following libraries have not yet branched: $ list-deliverables --no-stable-branch -v --model cycle-with-intermediary --type library ceilometermiddleware

[openstack-dev] [puppet] Nominating zhongshengping for core of the Puppet OpenStack modules

Thanks everyone, it's my pleasure! I'll try to do my best. On Fri, Jan 20, 2017 at 10:19 AM, Alex Schultz wrote: >> Hey Puppet Cores, I would like to nominate Zhong Shengping as a Core reviewer for the >> Puppet OpenStack modules. He is an excellent contributor to our >> modules over the

Re: [openstack-dev] [nova][qa] gate-grenade-dsvm-neutron-multinode-live-migration-nv is 100% fail since 1/21

2017-01-27 19:35 GMT-08:00 Matt Riedemann : > On 1/27/2017 5:00 PM, Matt Riedemann wrote: >> >> I noticed that this job is 100% failure since 1/21: >> >> http://tinyurl.com/zjh5bc5 >> >> >>

Re: [openstack-dev] [nova] Latest and greatest on trying to get n-sch to require placement

On 1/26/2017 8:40 AM, Matt Riedemann wrote: And circling back on *that*, we've agreed to introduce a new service version for the compute to indicate it's Ocata or not. Then we'll: * check in the scheduler if the minimum compute service version is ocata, * if minimum is ocata, then use

Re: [openstack-dev] [nova][qa] gate-grenade-dsvm-neutron-multinode-live-migration-nv is 100% fail since 1/21

On 1/27/2017 5:00 PM, Matt Riedemann wrote: I noticed that this job is 100% failure since 1/21: http://tinyurl.com/zjh5bc5

Re: [openstack-dev] [all][Community_App_Catalog][Ec2_Api][Karbor][Magnum][OpenStack_UX][Requirements][Senlin] Last days for PTL candidate announcements

On 01/26/2017 06:33 PM, Kendall Nelson wrote: > Hello All! > > It appears that there are several projects without PTL nominations and we > are reaching the close of the nomination period. The period ends Jan 29, > 2017 23:45 UTC. > The current leaderless projects are: - Community_App_Catalog -

Re: [openstack-dev] [neutron-lbaas][barbican][octavia]certs don't get deregistered in barbican after lbaas listener delete

Ah, I see the point... So basically it is just updating one of the values of the cert object in Barbican. In this case yes, fully agree it should be marked as a bug and fixed asap. Sorry for misunderstanding! On Fri, Jan 27, 2017 at 1:44 PM, Jiahao Liang (Frankie) < gzliangjia...@gmail.com>