[openstack-dev] [neutron] core and driver teams attrition

Hi Neutrinos, By now a few of us have noticed that the neutron core and driver teams have lost a number of very talented and experienced engineers: well...this sucks there's no more polite way to put it!! These engineers are the collective memory of the project, know the kinks and gotchas of the

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

On 1.12.2016 23:26, Emilien Macchi wrote: Team, Alex Schultz (mwhahaha on IRC) has been active on TripleO since a few months now. While he's very active in different areas of TripleO, his reviews and contributions on puppet-tripleo have been very useful. Alex is a Puppet guy and also the

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

On Thu, Dec 01, 2016 at 05:26:31PM -0500, Emilien Macchi wrote: > Team, > > Alex Schultz (mwhahaha on IRC) has been active on TripleO since a few > months now. While he's very active in different areas of TripleO, his > reviews and contributions on puppet-tripleo have been very useful. > Alex is

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On Fri, Dec 02, 2016 at 03:19:26PM +1100, Tony Breeds wrote: On Thu, Dec 01, 2016 at 07:57:37AM +0100, Mehdi Abaakouk wrote: I think the solution is pretty simple. Just Fix it. I'm not saying it's easy but it is *simple*. We're a group of skilled individuals We have several ways forward which

Re: [openstack-dev] [Neutron] Stepping down from core

Henry, it was a pleasure working with you! Thanks! All the best for your further journey! -- - Andreas IRC: andreas_s On Do, 2016-12-01 at 17:51 -0500, Henry Gessau wrote: > I've already communicated this in the neutron meeting and in some neutron > policy patches, but yesterday the PTL

Re: [openstack-dev] [gnocchi] influxdb driver gate error

Le 2016-12-01 23:48, Sam Morrison a écrit : Using influxdb v1.1 works fine. anything less than 1.0 I would deem unusable for influxdb. So to get this to work we’d need a newer version of influxdb installed. That's work for me. Any idea how to do this? I see they push out a custom ceph repo

Re: [openstack-dev] [Zun] Propose a change of Zun core membership

+1 for both. Welcome Pradeep :) Regards Shubham On Thu, Dec 1, 2016 at 5:07 AM, Hongbin Lu wrote: > Hi Zun cores, > > > > I am going to propose the following change of the Zun core reviewers team: > > + Pradeep Kumar Singh (pradeep-singh-u) > > - Vivek Jain

Re: [openstack-dev] [Zun] Propose a change of Zun core membership

+1 for both. 2016-12-01 7:37 GMT+08:00 Hongbin Lu : > Hi Zun cores, > > > > I am going to propose the following change of the Zun core reviewers team: > > + Pradeep Kumar Singh (pradeep-singh-u) > > - Vivek Jain (vivek-jain-openstack) > > > > Pradeep was proven to be a

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

+1 On Fri, Dec 2, 2016 at 12:50 AM, Pradeep Kilambi wrote: > > > On Thu, Dec 1, 2016 at 5:26 PM, Emilien Macchi wrote: > >> Team, >> >> Alex Schultz (mwhahaha on IRC) has been active on TripleO since a few >> months now. While he's very active in different

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On Thu, Dec 01, 2016 at 04:52:52PM +, Keen, Joe wrote: > Unfortunately there’s nothing wrong on the Monasca side so far as we know. > We test new versions of the kafka-python library outside of Monasca > before we bother to try integrating a new version. Since 1.0 the > kafka-python library

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On Thu, Dec 01, 2016 at 08:41:54AM -0800, Joshua Harlow wrote: > Keen, Joe wrote: > > I¹ll look into testing the newest version of kafka-python and see if it > > meets our needs. If it still isn¹t stable and performant enough what are > > the available options? > > Fix the kafka-python library

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On Thu, Dec 01, 2016 at 07:57:37AM +0100, Mehdi Abaakouk wrote: > I'm aware of all of that, oslo.messaging patch for the new version is > ready since 8 months now. And we are still blocked... capping libraries, > whatever the reason, is very annoying and just freezes people work. And I agree with

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Dec. 2 2016

1) Roll Call 2) China Telecom Support (Storage & Bare Metal) 3) OPNFV: Daisy CI Progress 4) AoB B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [kolla] Vote to add zhubingbing to core team

On Tue, Nov 29, 2016 at 9:51 PM, Michał Jastrzębski wrote: > Hello team! > > I'd like to propose to add zhubingbing to kolla (and kolla-ansible) > core teams. He did great job reviewing code during last couple of > months. > > Consider this proposal +1 from me, voting will be

Re: [openstack-dev] [Openstack] OpenStack Ocata B1 for Ubuntu 16.04 LTS

Cool. And Kolla has upgrade ubuntu repo to b1 in master branch. btw, if there is any way or help doc for proposing a new package into ubuntu-cloud-archive? like kolla. On Fri, Dec 2, 2016 at 12:53 AM, Corey Bryant wrote: > Hi All, > > > The Ubuntu OpenStack team

Re: [openstack-dev] [Zun] Propose a change of Zun core membership

+1 Best Regards Eli Qiao(乔立勇）OpenStack Core team OTC Intel. -- 在 16/12/2 上午9:55，“Shuu Mutou” 写入: +1 for both. Thanks, Shu > -Original Message- > From: Hongbin Lu [mailto:hongbin...@huawei.com] > Sent: Thursday, December 01,

Re: [openstack-dev] [Zun] Propose a change of Zun core membership

+1 for both. Thanks, Shu > -Original Message- > From: Hongbin Lu [mailto:hongbin...@huawei.com] > Sent: Thursday, December 01, 2016 8:38 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: [openstack-dev] [Zun] Propose a

[openstack-dev] What's Up, Doc? Holiday Edition!

Hi everyone, The end of the year is nearly upon us already, and this will be my last newsletter for 2016, before I disappear for the holidays on the 16th. I've had yet another wonderful year with all you lovely OpenStack people, and I wish all of you and your families a happy and safe holiday,

[openstack-dev] Fw: Re: Re: [kolla] Obtaining version information for Docker container

Adrian, Thank you for the information. B.R., Zhijiang 发件人: Adrian Mouat 收件人: hu.zhiji...@zte.com.cn, 抄送: "OpenStack Development Mailing List (not for usage questions)" 日期: 2016-12-01 23:49 主题:

Re: [openstack-dev] [infra]help on the description update in github repository

Thank you very much. It's updated :-) Best Regards Chaoyi Huang (joehuang) From: Jeremy Stanley [fu...@yuggoth.org] Sent: 02 December 2016 0:08 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [infra]help on

Re: [openstack-dev] [Neutron] Stepping down from core

On 12/1/2016 4:51 PM, Henry Gessau wrote: I've already communicated this in the neutron meeting and in some neutron policy patches, but yesterday the PTL actually updated the gerrit ACLs so I thought I'd drop a note here too. My work situation has changed and leaves me little time to keep up

Re: [openstack-dev] [Neutron] Stepping down from core

Thanks for your help with recent neutron-lib transitions, and best wishes for your future work, Henry! Neil On Thu, Dec 1, 2016 at 11:06 PM Dariusz Śmigiel wrote: > Henry, > it's very sad to see you stepping down. > Thank you for all the time and help in

Re: [openstack-dev] [keystone] team logo (initial draft)

Looks good! Commented on the Form, but the "grey section" might be even better if there was a little color to it. As it is, It might be too "stark" a contrast as it is to a black laptop/background (white alone tends to be) if the white sections are opaque, and it might fade into a "white" or

[openstack-dev] [nova] Move unapproved specs to Pike

We now have the Pike structure in place for the nova-specs repo: https://specs.openstack.org/openstack/nova-specs/specs/pike/index.html So if you have specs which weren't approved for Ocata and you plan on pursuing them again in Pike, please move them over to the specs/pike/approved/

Re: [openstack-dev] [Neutron] Stepping down from core

Henry, it's very sad to see you stepping down. Thank you for all the time and help in Keystone v3 development. I hope you will have a lot of new, even better, experiences in your further journey. Thank you 2016-12-01 16:51 GMT-06:00 Henry Gessau : > I've already communicated

[openstack-dev] [Neutron] Stepping down from core

I've already communicated this in the neutron meeting and in some neutron policy patches, but yesterday the PTL actually updated the gerrit ACLs so I thought I'd drop a note here too. My work situation has changed and leaves me little time to keep up with my duties as core reviewer, DB

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

On Thu, Dec 1, 2016 at 5:26 PM, Emilien Macchi wrote: > Team, > > Alex Schultz (mwhahaha on IRC) has been active on TripleO since a few > months now. While he's very active in different areas of TripleO, his > reviews and contributions on puppet-tripleo have been very

Re: [openstack-dev] [gnocchi] influxdb driver gate error

I’ve been working a bit on this and the errors I’m getting in the gate I can now replicate in my environment if I use the same version of influxdb in the gate (0.10) Using influxdb v1.1 works fine. anything less than 1.0 I would deem unusable for influxdb. So to get this to work we’d need a

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

+1 On Thu, Dec 1, 2016 at 11:37 PM, Dan Trainor wrote: > +1 > > On Dec 1, 2016 5:36 PM, "James Slagle" wrote: >> >> On Thu, Dec 1, 2016 at 5:26 PM, Emilien Macchi wrote: >> > Team, >> > >> > Alex Schultz (mwhahaha on IRC) has

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

+1 On Dec 1, 2016 5:36 PM, "James Slagle" wrote: > On Thu, Dec 1, 2016 at 5:26 PM, Emilien Macchi wrote: > > Team, > > > > Alex Schultz (mwhahaha on IRC) has been active on TripleO since a few > > months now. While he's very active in different

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

On Thu, Dec 1, 2016 at 7:03 PM, James Slagle wrote: > On Thu, Dec 1, 2016 at 5:26 PM, Emilien Macchi wrote: > > Team, > > > > Alex Schultz (mwhahaha on IRC) has been active on TripleO since a few > > months now. While he's very active in different

Re: [openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

On Thu, Dec 1, 2016 at 5:26 PM, Emilien Macchi wrote: > Team, > > Alex Schultz (mwhahaha on IRC) has been active on TripleO since a few > months now. While he's very active in different areas of TripleO, his > reviews and contributions on puppet-tripleo have been very useful.

[openstack-dev] [tripleo] Proposing Alex Schultz core on puppet-tripleo

Team, Alex Schultz (mwhahaha on IRC) has been active on TripleO since a few months now. While he's very active in different areas of TripleO, his reviews and contributions on puppet-tripleo have been very useful. Alex is a Puppet guy and also the current PTL of Puppet OpenStack. I think he

Re: [openstack-dev] [nova] Status of imagebackend refactor patches

Just following up on this. All of the above are now approved and working their way through the gate. Big thanks to Sean Dague, Feodor Tersin, and Melanie Witt for review assistance over the last couple weeks. Also thanks to Chris Dent for reviewing the bulk of the series today as well and

[openstack-dev] [Horizon][Keystone] Weekly meeting log (2016/12/1)

Hi folks, The meeting bot disappeared during the meeting so the record is incomplete. The last 20 minutes are still in the channel log here: http://eavesdrop.openstack.org/irclogs/%23openstack-meeting-cp/%23openstack-meeting-cp.2016-12-01.log.html#t2016-12-01T20:42:08 Richard

[openstack-dev] [release] Release management team draft logo

Release team, please take a look at the attached logo and let me know what you think. Doug > Begin forwarded message: > > From: Heidi Joy Tretheway > Subject: Release management team draft logo > Date: December 1, 2016 at 2:29:05 PM EST > To: Doug Hellmann > > Thanks

[openstack-dev] [qa] [openstack-health] Avoid showing non-official projects failure ratios

Hi QA-team, In the big-tent policy, we continue creating new projects. On the other hand, some projects became non-active. That seems natural thing. Now openstack-health[1] shows non-active project as 100% failure ratio on "Project Status". The project has became non-official since

[openstack-dev] [Telemetry] team draft logo

Hi team, Attached is our logo. You can share feedback here or directly with the Foundation at www.tinyurl.com/OSmascot Cheers, -- Julien Danjou # Free Software hacker # https://julien.danjou.info signature.asc Description: PGP signature

Re: [openstack-dev] [neutron][octavia] Neutron LBaaS governance change and Octavia to the big tent

On 1 December 2016 at 08:04, Michael Johnson wrote: > There are a lot more than just those three (which are under packaging > and not neutron btw). > > I will start working on moving/scrubbing the bugs today. > At the same time, I'll be working to make sure we have a

Re: [openstack-dev] [tripleo][ci] jobs shuffle to add IPv6 coverage

On 11/15/2016 10:41 AM, Gabriele Cerami wrote: On 18 Oct, Gabriele Cerami wrote: Hello, after adding coverage in CI for HA IPv6 scenario here https://review.openstack.org/363674 we wanted to add IPv6 testing on the gates. To not use any more resources the first suggestion to add IPv6 to the

Re: [openstack-dev] [All][neutron-vpnaas] Finish test job transition to Ubuntu Xenial

On 12/01/2016 05:22 PM, Armando M. wrote: > > > On 1 December 2016 at 07:45, Andreas Jaeger > wrote: > > On 11/15/2016 12:30 AM, Clark Boylan wrote: > > [...] > > Just a friendly reminder that this is still happening. We will be >

Re: [openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

On Thu, Dec 1, 2016 at 7:39 PM, Morgan Fainberg wrote: > On Dec 1, 2016 8:25 AM, "Andrey Kurilin" wrote: > > > > As I replied at IRC, please do not mix two separate issues! > > Yes, we have several scenarios which are not support keystone v3

Re: [openstack-dev] [nova][SR-IOV] update the SR-IOV meeting to bi-weekly

Agreed. Also considering that the amount of known bugs is under control (compared to previous cycle), I'm in favor of going to bi-weekly meetings. /ludovic -Original Message- From: Stephen Finucane [mailto:sfinu...@redhat.com] Sent: December-01-16 12:38 PM To:

Re: [openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

On Dec 1, 2016 8:25 AM, "Andrey Kurilin" wrote: > > As I replied at IRC, please do not mix two separate issues! > Yes, we have several scenarios which are not support keystone v3 yet. It is an issue, but it is unrelated issue to described in the first mail. > We have a job

Re: [openstack-dev] [nova][SR-IOV] update the SR-IOV meeting to bi-weekly

On Thu, 2016-12-01 at 14:48 +, Moshe Levi wrote: > Hi all, > > I would like to update the frequency of the SR-IOV meeting to be  bi- > weekly [1]. > Does anyone see value in keeping it as weekly meeting? > > [1] - https://review.openstack.org/#/c/405415/ Seeing as we don't have any specs

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On 12/1/16, 9:44 AM, "Julien Danjou" wrote: >On Thu, Dec 01 2016, Keen, Joe wrote: > >Hi Joe, > >[…] > >> The message context wrapped around every message is extra overhead we >> don¹t want. >> There¹s no support for batch sends to Kafka. >> There¹s no support for keyed

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, Some good attendance and discussion this week. For many months the API-WG has been claiming that it would try to review any commit that contained an 'APIImpact' tag. This has proven impractical so instead of maintaining a task on our list that we know we're not

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

Reopen them? If they weren't fixed, then seems like the right thing to try to do, and rinse and repeat until actually fixed :-P Keen, Joe wrote: > We reported > the bugs we found to the kafka-python project but they were closed once > they released a new version.

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

Damn, that's supposed to say co-installability... Lol, -Josh Joshua Harlow wrote: Keen, Joe wrote: I¹ll look into testing the newest version of kafka-python and see if it meets our needs. If it still isn¹t stable and performant enough what are the available options? Fix the kafka-python

[openstack-dev] [Openstack] OpenStack Ocata B1 for Ubuntu 16.04 LTS

Hi All, The Ubuntu OpenStack team is pleased to announce the general availability of the OpenStack Ocata B1 milestone in Ubuntu 16.04 LTS via the Ubuntu Cloud Archive. Ubuntu 16.04 LTS You can enable the Ubuntu Cloud Archive pocket for OpenStack Ocata on Ubuntu

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On 12/1/16, 9:41 AM, "Joshua Harlow" wrote: >Keen, Joe wrote: >> I¹ll look into testing the newest version of kafka-python and see if it >> meets our needs. If it still isn¹t stable and performant enough what >>are >> the available options? > >Fix the kafka-python

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On Thu, Dec 01 2016, Keen, Joe wrote: Hi Joe, […] > The message context wrapped around every message is extra overhead we > don¹t want. > There¹s no support for batch sends to Kafka. > There¹s no support for keyed producers. > The forced auto_commit on consumers isn¹t something we can

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

Keen, Joe wrote: I¹ll look into testing the newest version of kafka-python and see if it meets our needs. If it still isn¹t stable and performant enough what are the available options? Fix the kafka-python library or fix monasca; those seem to be the options to me :) I'd also not like to

Re: [openstack-dev] [All][neutron-vpnaas] Finish test job transition to Ubuntu Xenial

Armando M. wrote: I did file bug [1]. FWIW, vpnaas on strongswan works fine in xenial [2], and if the rally teams feel like not losing vpnaas coverage, they could switch to strongswan. [1] https://bugs.launchpad.net/python-neutronclient/+bug/1645819 [2]

Re: [openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

As I replied at IRC, please do not mix two separate issues! Yes, we have several scenarios which are not support keystone v3 yet. It is an issue, but it is unrelated issue to described in the first mail. We have a job which is configured with proper IDENTITY_API_VERSION flag and should be launched

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On 12/1/16, 3:11 AM, "Julien Danjou" wrote: >On Thu, Dec 01 2016, Mehdi Abaakouk wrote: > >> I'm aware of all of that, oslo.messaging patch for the new version is >> ready since 8 months now. And we are still blocked... capping libraries, >> whatever the reason, is very

Re: [openstack-dev] [All][neutron-vpnaas] Finish test job transition to Ubuntu Xenial

On 1 December 2016 at 07:45, Andreas Jaeger wrote: > On 11/15/2016 12:30 AM, Clark Boylan wrote: > > [...] > >> Just a friendly reminder that this is still happening. We will be >> updating any jobs running on Trusty that should be running on Xenial on >> December 6th. I have seen

Re: [openstack-dev] [tripleo] [tripleo-quickstart] Tripleo-Quickstart root privileges

On Thu, Dec 01, 2016 at 09:03:30AM -0500, John Trowbridge wrote: > 1. Doing tasks as root on the virthost makes clean up trickier. With the > current model, deleting the non-root quickstart user cleans up almost > everything. By keeping all of the root privilege tasks in the provision > and

Re: [openstack-dev] [infra]help on the description update in github repository

On 2016-12-01 07:14:58 + (+), joehuang wrote: > The short project description of Tricircle is: "Tricircle is to > provide networking automation across Neutron." in > http://git.openstack.org/cgit/openstack/tricircle/, > the official repository. > > But the description in the mirrored

Re: [openstack-dev] [neutron][octavia] Neutron LBaaS governance change and Octavia to the big tent

There are a lot more than just those three (which are under packaging and not neutron btw). I will start working on moving/scrubbing the bugs today. Michael On Thu, Dec 1, 2016 at 7:30 AM, Brian Haley wrote: > On 12/01/2016 08:54 AM, Ihar Hrachyshka wrote: >> >> Armando M.

Re: [openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

FWIW - i'm seeing a common error in several of the rally failures [0] [1] [2] [3]. Dims also pointed out a few bugs in rally for keystone v3 support [4]. I checked with the folks in #openstack-containers to see if they were experiencing anymore fallout, but it looks like the magnum gate is under

Re: [openstack-dev] [All][neutron-vpnaas] Finish test job transition to Ubuntu Xenial

On 11/15/2016 12:30 AM, Clark Boylan wrote: > [...] Just a friendly reminder that this is still happening. We will be updating any jobs running on Trusty that should be running on Xenial on December 6th. I have seen a few projects jump on this and start making the necessary changes. Thank you

Re: [openstack-dev] [kolla] propose to remove COPY_ONCE feature

K8s shouldn't matter as configmaps are the thing out there, not really kolla-config. Configmap will copy the file where it needs to be copied, so k8s doesn't care that much which is it. Also, having copy-once with this all "ephemeral" "die and restart" pod structure is volatile at least. On 1

[openstack-dev] 3rd party CI - tempest config override changes

Yesterday we merged - https://review.openstack.org/#/c/293954/ - which was long standing work to get Tempest to be configured explicitly in it's *very late* phase in devstack. This was needed by projects that have devstack plugins that need to do something once the whole cloud is up and running

Re: [openstack-dev] [neutron][octavia] Neutron LBaaS governance change and Octavia to the big tent

On 12/01/2016 08:54 AM, Ihar Hrachyshka wrote: Armando M. wrote: Hi folks, A few hours ago a governance change [1] has been approved by TC members. This means that from now on, the efforts for Load Balancing as a Service efforts rest officially in the hands of the Octavia

[openstack-dev] [nova][SR-IOV] update the SR-IOV meeting to bi-weekly

Hi all, I would like to update the frequency of the SR-IOV meeting to be bi-weekly [1]. Does anyone see value in keeping it as weekly meeting? [1] - https://review.openstack.org/#/c/405415/ Thanks, Moshe Levi __

Re: [openstack-dev] [ALU] [vitrage] datasource driver returns entities only?

Another question, how do we describe an entity from *another* datasource in static datasource config? In the test resources of static_physical datasource, it seems to be referred as following. Does it means that it will be `nova.host` to find the matched resource? If so, how will `nova.host`

Re: [openstack-dev] [kolla] propose to remove COPY_ONCE feature

Jeffrey, Can’t post inline (outlook bug). kolla-kubernetes has no use-case for COPY_ALWAYS. The kolla-kubernetes deliverable uses a construct called EmptyDir to store configuration files. There is no way to hand-modify the configuration files in EmptyDir that I am aware of nor was any of the

Re: [openstack-dev] [tripleo] [tripleo-quickstart] Tripleo-Quickstart root privileges

On 11/22/2016 03:49 PM, Gabriele Cerami wrote: > On 22 Nov, Yolanda Robla Mota wrote: >> Hi all >> I wanted to start a thread about the current privileges model for TripleO >> quickstart. >> Currently there is the assumption that quickstart does not need root >> privileges after the

Re: [openstack-dev] [nova] Continued reduction in NFV tech debt - input?

On 12/1/2016 4:51 AM, Stephen Finucane wrote: nova has worked hard over the last few cycles to identify and reduce the amount of tech debt we're carrying. One such item identified early on was the lack of automated testing and upstream documentation for NFV features, such as CPU pinning,

Re: [openstack-dev] [neutron][octavia] Neutron LBaaS governance change and Octavia to the big tent

Armando M. wrote: Hi folks, A few hours ago a governance change [1] has been approved by TC members. This means that from now on, the efforts for Load Balancing as a Service efforts rest officially in the hands of the Octavia PTL and the Octavia core team. I will

Re: [openstack-dev] [ALU] [vitrage] datasource driver returns entities only?

Hi Yujun, Get_all does returns a list of entities to be sent. Each event that is sent from the driver to the processor contains also all the details of the neighbors that it connects to. For example, the event and data that we receive from nova about an instance also contains the host

[openstack-dev] [vitrage] datasource driver returns entities only?

During the implementation of static datasource driver[1], I got a question on the return format of `get_all` method. If I understand correctly, it should return a list of entities to be sent to the queue. Does it infer that the relationship should be embedded in entity, just like the legacy

Re: [openstack-dev] [ptl][release] ocata release management communication

It looks like your email was already replied to: http://lists.openstack.org/pipermail/openstack-dev/2016-November/108141.html On 30 Nov 2016, at 18:38, Rob C > wrote: [Resending without the PTLs in CC because it got my mail stuck in the spam

Re: [openstack-dev] [kolla] propose to remove COPY_ONCE feature

@sdake we can keep COPY_ONCE and COPY_ALWAY in docker images. But in kolla-ansible side, only implement COPY_ALWAY. And does kolla-k8s will only implement COPY_ONCE? @Gerard COPY_ALWAYS only affect the configuration file, like /etc/nova/nova.conf. others are still immutable. @Paul For the

Re: [openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

I think for magnum we are OK. This job [1] finished using keystone v3 [2] Spyros [1] http://logs.openstack.org/93/400593/9/check/gate-functional-dsvm-magnum-api/93e8c14/ [2]

Re: [openstack-dev] [Openstack-operators] Destructive / HA / fail-over scenarios

Hi Timur, You can also consider Stepler from Mirantis https://github.com/Mirantis/stepler. I never tried it, but the documentation states: "Stepler framework is intended to provide the community with a testing framework that is capable of perform advanced scenario and destructive test cases,

Re: [openstack-dev] [oslo] Should we drop kafka driver ?

Le 2016-11-30 17:45, Joshua Harlow a écrit : One of the places for gate testing that is still being worked on is the following: https://github.com/jd/pifpaf/pull/28 I just finished the work on this: https://github.com/jd/pifpaf/pull/35 And I used it in oslo.messaging here:

Re: [openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

It has taken years to get here with a lot of work from many folks. -1 for Any revert! https://etherpad.openstack.org/p/v3-only-devstack http://markmail.org/message/aqq7itdom36omnf6 https://review.openstack.org/#/q/status:merged+project:openstack-dev/devstack+branch:master+topic:bp/keystonev3

[openstack-dev] [neutron] Remove deprecated utility method - camelize

Hi, This method is now supported by neutron-lib. The patch [1] remove this from neutron. Thanks Gary [1] https://review.openstack.org/#/c/403690 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [kolla] Obtaining version information for Docker container

For #1, I think the requirement is that before pulling the image to local registry, one can get its metadata about the version info before hand, thus save time and space spend on pulling wrong images. I don't know if the info in docker label can be retrieved before before pulling the image to

[openstack-dev] [nova] Continued reduction in NFV tech debt - input?

nova has worked hard over the last few cycles to identify and reduce the amount of tech debt we're carrying. One such item identified early on was the lack of automated testing and upstream documentation for NFV features, such as CPU pinning, realtime, hugepages, SR-IOV, and PCI passthrough. We

[openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

Hi folks! Today devstack team decided to switch to keystone v3 by default[0]. Imo, it is important thing, but it was made in silent, so other project was unable to prepare to that change. Also, proposed way to select Keystone API version via devstack configuration doesn't

Re: [openstack-dev] [Openstack-operators] Heat: signaling using SW config/deployment API.

Moving to openstack-dev for more visibility and discussion. We currently have signal API for heat resources(not for standalone software config/deployment). However, you can probably use a workaround with swift temp_url like tripleo[1] to achieve your use case. We do have rpc api[2] for

Re: [openstack-dev] [kolla] propose to remove COPY_ONCE feature

While I would be interested to know how many people actually do use COPY_ONCE, I think if I was in charge of a production deployment I would use COPY_ONCE. On 01/12/16 02:27, Jeffrey Zhang wrote: Kolla has a config_strategy option during deployment. it supports COPY_ONCE and COPY_ALWAYS.

Re: [openstack-dev] [oslo][monasca] Can we uncap python-kafka ?

On Thu, Dec 01 2016, Mehdi Abaakouk wrote: > I'm aware of all of that, oslo.messaging patch for the new version is > ready since 8 months now. And we are still blocked... capping libraries, > whatever the reason, is very annoying and just freezes people work. > > From the API pov python-kafka

Re: [openstack-dev] [neutron] [tap-as-a-service] stable/newton 'broken'

On Mon, Nov 28, 2016 at 8:37 PM, Takashi Yamamoto wrote: > Anil, > > do you have any opinion? > > i'm thinking to branch stable/newton at around > 675af77205d4e404bc7c185c13ab6d86f300d185 after taas meeting, i went ahead and create the branch. > > On Thu, Nov 24, 2016 at

Re: [openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

On Thu, Dec 1, 2016 at 1:02 AM, Armando M. wrote: > > > On 27 November 2016 at 20:50, Takashi Yamamoto > wrote: >> >> On Wed, Nov 16, 2016 at 11:02 AM, Armando M. wrote: >> > Hi >> > >> > As of today, the project neutron-vpnaas is no

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 30/11/16 08:53 -0800, Michael Johnson wrote: Hi Flavio, These tags don't seem to be rendering/laying out well for octavia: https://github.com/openstack/octavia/blob/master/README.rst Any pointers to get this corrected or is this part of the backend rendering work you mentioned in the

Re: [openstack-dev] [kolla] propose to remove COPY_ONCE feature

On Thu, Dec 1, 2016 at 4:43 PM, Steven Dake (stdake) wrote: > The kolla-kubernetes deliverable requires COPY_ONCE not COPY_ALWAYS. > Some operators prefer immutability over hand-modification of configuration > From: Jeffrey Zhang > I am curiosity does

Re: [openstack-dev] [kolla] propose to remove COPY_ONCE feature

Jeffrey, The kolla-kubernetes deliverable requires COPY_ONCE not COPY_ALWAYS. Some operators prefer immutability over hand-modification of configuration files on all nodes. Therefore, I propose we keep both in place. Regards -steve From: Jeffrey Zhang Reply-To: