Re: [openstack-dev] [heat] resigning from heat-cores

Thank you very much for the helps. Good luck on your new journey! - Qiming On Mon, Sep 12, 2016 at 03:35:05PM +0300, Pavlo Shchelokovskyy wrote: > Hi Heaters, > > with great regret I announce my resignation from the heat-core team. > > About a year ago I was reassigned to another project, and d

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Wed, Sep 14, 2016 at 11:22 AM, Liping Mao (limao) wrote: > You have a valid point regarding ipvlan support in newer kernel versions >> but IIUC overlay mode might not help if nic has a limit on max number of >> macs that it supports in hardware. >> >for example: http://www.brocade.com/cont

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

You have a valid point regarding ipvlan support in newer kernel versions but IIUC overlay mode might not help if nic has a limit on max number of macs that it supports in hardware. for example: http://www.brocade.com/content/html/en/configuration-guide/fastiron-08030b-securityguide/GUID-ED71C

[openstack-dev] [vitrage] Vitrage IRC meeting - SKIPPED this week

Hi, Vitrage meeting today will be SKIPPED. We will meet again next week, on September 20. Thanks, Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.o

[openstack-dev] [meghdwar] Edge Cloud Gateway API and Wednesday meeting

Hi all ? lets meet  7-8am PDT (Wed 14:00-15:00 UTC)irc Channel?: #openstack-meghdwar You can edit the etherpad if you want to update agenda...or reply be email on item1-5 below. https://etherpad.openstack.org/p/meghdwar 1.a.Megdwar Gateway API discussions? Focus is what APIs needed for minimu

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Wed, Sep 14, 2016 at 10:33 AM, Vikas Choudhary < choudharyvika...@gmail.com> wrote: > > > On Wed, Sep 14, 2016 at 9:39 AM, Liping Mao (limao) > wrote: > >> > Though, not the best person to comment on macvlan vs ipvlan, one >> limitation of macvlan is that on physical interfaces, maximum possib

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Wed, Sep 14, 2016 at 9:39 AM, Liping Mao (limao) wrote: > > Though, not the best person to comment on macvlan vs ipvlan, one > limitation of macvlan is that on physical interfaces, maximum possible > number of random mac generations may not cope-up with large number of > containers on same vm.

Re: [openstack-dev] [requirements][FFE][keystone][release] block keystonemiddleware 4.0.0

On Tue, Sep 13, 2016 at 03:53:46PM -0400, Steve Martinelli wrote: > A bug was recently filed against keystone [1]. As of the Newton release we > depend on a class being public -- BaseAuthProtocol instead of > _BaseAuthProtocol [2]. Which was introduced in 4.1.0 [3]. > > The current requirement for

Re: [openstack-dev] [keystone][oslo][release][requirements][FFE] global-requirements update for requests-kerberos

On Tue, Sep 13, 2016 at 03:23:08PM -0400, Adam Young wrote: > https://review.openstack.org/#/c/368530/ > > This change is for Python >2.7 only, as python2.7 already supports the > latest version of these libraraies. Back in the "just get pythoin3 to work" > days we cut our losses on Kerberos supp

Re: [openstack-dev] [all][python3] use of six.iteritems()

On 09/13/2016 08:23 PM, Terry Wilson wrote: On Tue, Sep 13, 2016 at 6:31 PM, Jay Pipes wrote: On 09/13/2016 01:40 PM, Terry Wilson wrote: On Thu, Jun 11, 2015 at 8:33 AM, Sean Dague wrote: On 06/11/2015 09:02 AM, Jay Pipes wrote: On 06/11/2015 01:16 AM, Robert Collins wrote: But again

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

> Though, not the best person to comment on macvlan vs ipvlan, one limitation > of macvlan is that on physical interfaces, maximum possible number of random > mac generations may not cope-up with large number of containers on same vm. Thanks, yes, it is a limitation, Vikas. This happened if you

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Wed, Sep 14, 2016 at 7:10 AM, Liping Mao (limao) wrote: > Hi Ivan and Gary, > > maybe we can use macvlan as ipvlan need very new kernel. > allow-address-pairs can aslo allow different mac in vm. > Do we consider macvlan here? Thanks. > Though, not the best person to comment on macvlan vs ipvl

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Tue, Sep 13, 2016 at 11:13 PM, Antoni Segura Puimedon wrote: > On Tue, Sep 13, 2016 at 5:05 PM, Hongbin Lu wrote: > > > > > > On Tue, Sep 13, 2016 at 2:10 AM, Vikas Choudhary > > wrote: > >> > >> > >> > >> On Mon, Sep 12, 2016 at 9:17 PM, Hongbin Lu > wrote: > >>> > >>> Ivan, > >>> > >>> Th

[openstack-dev] [kolla] Removal of folks from kolla-drivers

Forgot kolla tag. See message inside. From: Steven Dake Date: Tuesday, September 13, 2016 at 8:34 PM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Removal of folks from kolla-drivers Hey folks, I removed several folks which appeared inactive for the Newton cycle

Re: [openstack-dev] [kolla][ptl] Self non-nomination for Kolla PTL for Ocata cycle

Thank Steve for all you do to make Kolla come true. On Wed, Sep 14, 2016 at 10:19 AM, Vikram Hosakote (vhosakot) wrote: > Thanks a lot Steve for being a great PTL, leader and a mentor! > > Regards, > Vikram Hosakote > IRC: vhosakot > > From: "Steven Dake (stdake)" > Reply-To: "OpenStack Develop

Re: [openstack-dev] [all][python3] use of six.iteritems()

>All performance matters. All memory consumption matters. Being wasteful over a purely aesthetic few extra characters of code is silly. Isn't the logical conclusion of this to write everything in a different language? :) On Tue, Sep 13, 2016 at 8:42 AM, Terry Wilson wrote: > On Wed, Jun 10, 201

[openstack-dev] Removal of folks from kolla-drivers

Hey folks, I removed several folks which appeared inactive for the Newton cycle from the kolla-drivers team on launchpad. As a reminder, the reason we add people to the kolla-drivers team is to do bug triage, move blueprint states around, and distribute the process of handling the release. If

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Tue, Sep 13, 2016 at 5:26 PM, Liping Mao (limao) wrote: > Hi Ivan， > > It sounds cool！ > > for security group and allowed address pair， > Maybe we can disable port-security，because all the docker in one vm will > share one security group on the vm port. I'm not sure how to use sg for > each do

Re: [openstack-dev] [all][python3] use of six.iteritems()

On Tue, Sep 13, 2016 at 6:31 PM, Jay Pipes wrote: > On 09/13/2016 01:40 PM, Terry Wilson wrote: >> >> On Thu, Jun 11, 2015 at 8:33 AM, Sean Dague wrote: >>> >>> On 06/11/2015 09:02 AM, Jay Pipes wrote: On 06/11/2015 01:16 AM, Robert Collins wrote: > > But again - where in OpenSt

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Tue, Sep 13, 2016 at 8:35 PM, Hongbin Lu wrote: > > > On Tue, Sep 13, 2016 at 2:10 AM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> >> >> On Mon, Sep 12, 2016 at 9:17 PM, Hongbin Lu wrote: >> >>> Ivan, >>> >>> Thanks for the proposal. From Magnum's point of view, this proposal

[openstack-dev] [cinder] [oslo] privsep socket's client receive thread may crash without attention

Hello everyone: I found an error when backing up a volume with oslo_privsep,it seems that the client channel use a thread to receive socket message,but the thread may crash with inner exception unhandled while the main procedure continues,so I report a bug and upload a patchset to fix: https://r

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting tomorrow. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

Re: [openstack-dev] [kolla][ptl] Self non-nomination for Kolla PTL for Ocata cycle

Thanks a lot Steve for being a great PTL, leader and a mentor! Regards, Vikram Hosakote IRC: vhosakot From: "Steven Dake (stdake)" mailto:std...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Monday, Septembe

Re: [openstack-dev] [kolla] warning about PBR issue for kolla operators

pip install –e . is not viable either for a variety of reasons. We expect developers to be able to find their way to the tools directory and operate the commands directly from there. Regards -steve From: Clay Gerrard Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

Hi Ivan and Gary, maybe we can use macvlan as ipvlan need very new kernel. allow-address-pairs can aslo allow different mac in vm. Do we consider macvlan here? Thanks. Regards, Liping Mao From: Liping Mao mailto:li...@cisco.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org

[openstack-dev] [cinder]tempest test case for force detach volume

Hello, Is there ant tempest test case for "os-force_detach" action to force detach a volume? I didn't find such a test case both in the repository https://github.com/openstack/cinder/tree/master/cinder/tests/tempest and https://github.com/openstack/tempest The API link is: http://developer.open

[openstack-dev] [tc][swg] Summary of today's SWG meeting/work items

Hi everyone, I thought it might be a good idea to send a summary of the Stewardship Working Group (SWG) meeting[0] to the -dev list today - both to increase engagement around what we're up to, and to reach the (quite a few) folks who couldn't make today's meeting because of conflicts: 1. We're in

Re: [openstack-dev] [kolla] warning about PBR issue for kolla operators

There's a note in the "for development" section [1] that notes the development instructions don't include anything that puts kolla in your sys.path or any bin scripts copied out anywhere into the PATH - i.e. it's not installed That seems less than ideal for a developer - did I miss a `pip install

[openstack-dev] [kolla] warning about PBR issue for kolla operators

Hey folks, The quickstart guide was modified as a result of a lot of painful debugging over the last cycle approximately a month ago. The only solution available to us was to split the workflow into an operator workflow (working on stable branches) and a developer workflow (working on master).

Re: [openstack-dev] [all][python3] use of six.iteritems()

On 09/13/2016 01:40 PM, Terry Wilson wrote: On Thu, Jun 11, 2015 at 8:33 AM, Sean Dague wrote: On 06/11/2015 09:02 AM, Jay Pipes wrote: On 06/11/2015 01:16 AM, Robert Collins wrote: But again - where in OpenStack does this matter the slightest? Precisely. I can't think of a single case wher

Re: [openstack-dev] [Cinder] FFE request for RBD replication

+1 Since this is very isolated to the rbd driver and it's passing already Walt On 09/09/2016 12:32 PM, Gorka Eguileor wrote: Hi, As some of you may know, Jon Bernard (jbernard on IRC) has been working on the RBD v2.1 replication implementation [1] for a while, and we would like to request a F

Re: [openstack-dev] [release] proposing adding Tony Breeds to "Release Managers" team

On Tue, Sep 13, 2016 at 11:00:40AM -0400, Doug Hellmann wrote: > After a week with only positive responses, I've added Tony to both the > "Release Managers" and "release-tools-core" groups in gerrit. > > Welcome aboard, Tony! Thanks so much Doug. I'd like to thank you and the rest of the team fo

Re: [openstack-dev] [neutron] Is OVS implementation for supporting VLAN-Aware-VM compeleted?

Ryan, Thanks! Cathy From: Tidwell, Ryan [mailto:ryan.tidw...@hpe.com] Sent: Tuesday, September 13, 2016 1:17 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] Is OVS implementation for supporting VLAN-Aware-VM compeleted? Cathy, There a

Re: [openstack-dev] [keystone][oslo][release][requirements][FFE] global-requirements update for requests-kerberos

Excerpts from Matthew Thode's message of 2016-09-13 16:07:46 -0500: > On 09/13/2016 03:55 PM, Doug Hellmann wrote: > > Excerpts from Matthew Thode's message of 2016-09-13 15:09:39 -0500: > >> On 09/13/2016 02:37 PM, Doug Hellmann wrote: > >>> Excerpts from Adam Young's message of 2016-09-13 15:23:0

Re: [openstack-dev] [keystone][oslo][release][requirements][FFE] global-requirements update for requests-kerberos

On 09/13/2016 03:55 PM, Doug Hellmann wrote: > Excerpts from Matthew Thode's message of 2016-09-13 15:09:39 -0500: >> On 09/13/2016 02:37 PM, Doug Hellmann wrote: >>> Excerpts from Adam Young's message of 2016-09-13 15:23:08 -0400: https://review.openstack.org/#/c/368530/ This change

Re: [openstack-dev] [keystone][oslo][release][requirements][FFE] global-requirements update for requests-kerberos

Excerpts from Matthew Thode's message of 2016-09-13 15:09:39 -0500: > On 09/13/2016 02:37 PM, Doug Hellmann wrote: > > Excerpts from Adam Young's message of 2016-09-13 15:23:08 -0400: > >> https://review.openstack.org/#/c/368530/ > >> > >> This change is for Python >2.7 only, as python2.7 already s

Re: [openstack-dev] [all][python3] use of six.iteritems()

On Thu, Jun 11, 2015 at 8:33 AM, Sean Dague wrote: > On 06/11/2015 09:02 AM, Jay Pipes wrote: >> On 06/11/2015 01:16 AM, Robert Collins wrote: >>> But again - where in OpenStack does this matter the slightest? >> >> Precisely. I can't think of a single case where we are iterating over >> anywhere

Re: [openstack-dev] [neutron] Is OVS implementation for supporting VLAN-Aware-VM compeleted?

Cathy, There are a few outstanding reviews to be wrapped up, including docs. However, this is mostly complete and the bulk of the functionality has merged and you can try it out. Code Reviews: https://review.openstack.org/#/q/project:openstack/neutron+branch:master+topic:bp/vlan-aware-vms Docs

Re: [openstack-dev] [keystone][oslo][release][requirements][FFE] global-requirements update for requests-kerberos

On 09/13/2016 02:23 PM, Adam Young wrote: > https://review.openstack.org/#/c/368530/ > > This change is for Python >2.7 only, as python2.7 already supports the > latest version of these libraraies. Back in the "just get pythoin3 to > work" days we cut our losses on Kerberos support, but now it is

Re: [openstack-dev] [requirements][FFE][keystone][release] block keystonemiddleware 4.0.0

On 09/13/2016 02:53 PM, Steve Martinelli wrote: > A bug was recently filed against keystone [1]. As of the Newton release > we depend on a class being public -- BaseAuthProtocol instead of > _BaseAuthProtocol [2]. Which was introduced in 4.1.0 [3]. > > The current requirement for keystonemiddlewar

Re: [openstack-dev] [keystone][oslo][release][requirements][FFE] global-requirements update for requests-kerberos

On 09/13/2016 02:37 PM, Doug Hellmann wrote: > Excerpts from Adam Young's message of 2016-09-13 15:23:08 -0400: >> https://review.openstack.org/#/c/368530/ >> >> This change is for Python >2.7 only, as python2.7 already supports the >> latest version of these libraraies. Back in the "just get pyt

[openstack-dev] [requirements][FFE][keystone][release] block keystonemiddleware 4.0.0

A bug was recently filed against keystone [1]. As of the Newton release we depend on a class being public -- BaseAuthProtocol instead of _BaseAuthProtocol [2]. Which was introduced in 4.1.0 [3]. The current requirement for keystonemiddleware is: keystonemiddleware>=4.0.0,!=4.1.0,!=4.5.0 Blockin

Re: [openstack-dev] [charms]Running two haproxy-using units on same machine?

Hi Neil On Tue, 13 Sep 2016 at 20:43 Neil Jerram wrote: > Should it be possible to run two OpenStack charm units, that both use > haproxy to load balance their APIs, on the same machine? Or is there some > doc somewhere that says that a case like that should use separate machines? > > (I'm aski

[openstack-dev] [charms]Running two haproxy-using units on same machine?

Should it be possible to run two OpenStack charm units, that both use haproxy to load balance their APIs, on the same machine? Or is there some doc somewhere that says that a case like that should use separate machines? (I'm asking in connection with the bug report at https://bugs.launchpad.net/o

Re: [openstack-dev] [keystone][oslo][release][requirements][FFE] global-requirements update for requests-kerberos

Excerpts from Adam Young's message of 2016-09-13 15:23:08 -0400: > https://review.openstack.org/#/c/368530/ > > This change is for Python >2.7 only, as python2.7 already supports the > latest version of these libraraies. Back in the "just get pythoin3 to > work" days we cut our losses on Kerber

[openstack-dev] [ironic] Extending python-dracclient to fetch System/iDrac resources

I'm extending python-dracclient to pull in iDrac & System resources (DCIM_iDRACCard* & DCIM_System*). The way DCIM_BIOS* attributes work right now, only AttributeName, current_value, pending_value and read_only status are parsed. However, this approach does not work with iDRAC or System attributes

[openstack-dev] [keystone][oslo][release][requirements][FFE] global-requirements update for requests-kerberos

https://review.openstack.org/#/c/368530/ This change is for Python >2.7 only, as python2.7 already supports the latest version of these libraraies. Back in the "just get pythoin3 to work" days we cut our losses on Kerberos support, but now it is working. Getting this restriction removed mean

[openstack-dev] [new][tripleo] diskimage-builder 1.19.0 release

We are thrilled to announce the release of: diskimage-builder 1.19.0: Golden Disk Image builder. For more details, please see below. Changes in diskimage-builder 1.18.2..1.19.0 --- 49baaa4 Remove EPEL as hardcoded dependency of centos elements 01a0dbf Rem

[openstack-dev] [magnum] PTL candidacy

Hi, I would like to announce my candidacy for re-election as Magnum PTL. My involvement in Magnum began in December 2014, in which the project was at a very early stage. Since then, I have been working with the team to explore the roadmap, implement and refine individual components, and gradually

[openstack-dev] [neutron] Is OVS implementation for supporting VLAN-Aware-VM compeleted?

Hi All, Sorry I lost track of this work. Is the implementation completed? Can we start using the OVS version of VLAN-Aware VMs ? Thanks, Cathy __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: open

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

Sounds good!. Thanks for the clarification. Best regards, Hongbin On Tue, Sep 13, 2016 at 1:43 PM, Antoni Segura Puimedon wrote: > On Tue, Sep 13, 2016 at 5:05 PM, Hongbin Lu wrote: > > > > > > On Tue, Sep 13, 2016 at 2:10 AM, Vikas Choudhary > > wrote: > >> > >> > >> > >> On Mon, Sep 12, 201

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Tue, Sep 13, 2016 at 5:05 PM, Hongbin Lu wrote: > > > On Tue, Sep 13, 2016 at 2:10 AM, Vikas Choudhary > wrote: >> >> >> >> On Mon, Sep 12, 2016 at 9:17 PM, Hongbin Lu wrote: >>> >>> Ivan, >>> >>> Thanks for the proposal. From Magnum's point of view, this proposal >>> doesn't seem to require

Re: [openstack-dev] [all][python3] use of six.iteritems()

On Sep 13, 2016, at 10:42 AM, Terry Wilson wrote: > All performance matters. All > memory consumption matters. Being wasteful over a purely aesthetic few > extra characters of code is silly. import this -- Ed Leafe _

[openstack-dev] [nova] Let's wrap up config option changes for Newton

I've created a new blueprint for centralizing and cleaning up configuration options for Ocata: https://blueprints.launchpad.net/nova/+spec/centralize-config-options-ocata Please start moving existing changes, or create any new changes, in that blueprint rather than the newton blueprint: http

[openstack-dev] [new][murano] murano-pkg-check 0.1.0 release

We are pleased to announce the release of: murano-pkg-check 0.1.0: Murano package validator tool This is the first release of murano-pkg-check. With source available at: http://git.openstack.org/cgit/openstack/murano-pkg-check With package available at: https://pypi.python.org/pypi/mu

Re: [openstack-dev] [glance] [elections] Glance PTL non-candidacy

Thanks wangxiyuan! I'm happy to work with you and truly appreciate all your good work in Glance. Very glad to hear that my reviews are helping you. On 9/13/16 4:29 AM, 王玺源 wrote: > Hi Nikhil, > > You are the first PTL I knew when I started to work with OpenStack > community, we can see your hard

Re: [openstack-dev] [packaging-deb][PTL] candidacy

2016-09-12 21:10 GMT+02:00 Thomas Goirand : > I am writing to submit my candidacy for re-election as the PTL for the > packaging-deb project. > > The idea sparked in Vancouver (spring 2015). The project joined the > big-tent about a year ago (in August 2015, it was approved by the TC) > But it then

Re: [openstack-dev] [all][python3] use of six.iteritems()

On Wed, Jun 10, 2015 at 4:41 AM, Robert Collins wrote: > On 10 June 2015 at 21:30, Ihar Hrachyshka wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> On 06/10/2015 02:15 AM, Robert Collins wrote: >>> I'm very glad folk are working on Python3 ports. >>> >>> I'd like to call attenti

[openstack-dev] [ironic] Marking untested drivers as unsupported

Hi folks, I submitted this patch[0] to mark any untested driver as deprecated. Please review it to be sure I didn't miss anything or mark things that are tested (I suspect SSH driver will be controversial, but from what I've seen, the community is keen to stop supporting that). To be clear, the d

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Tue, Sep 13, 2016 at 2:10 AM, Vikas Choudhary wrote: > > > On Mon, Sep 12, 2016 at 9:17 PM, Hongbin Lu wrote: > >> Ivan, >> >> Thanks for the proposal. From Magnum's point of view, this proposal >> doesn't seem to require to store neutron/rabbitmq credentials in tenant VMs >> which is more de

Re: [openstack-dev] [release] proposing adding Tony Breeds to "Release Managers" team

Excerpts from Doug Hellmann's message of 2016-09-06 11:36:01 -0400: > Team, > > I would like to add Tony Breeds to the "Release Managers" team in > gerrit. This would give him +2 permissions on openstack-infra/release-tools > and on openstack/releases. I feel his reviews on both of those repos > h

Re: [openstack-dev] [kuryr] Spec and devref placement

+1 for (b) or (d). devrefs should should be where the related code is > On 12 Sep 2016, at 18:18, Irena Berezovsky wrote: > > I am fine with option (b) as well. > We can add option (d): > Specs in openstack/kuryr-specs but devrefs in each specific project, > i.e., the one that will end up with

Re: [openstack-dev] [neutron] Skip-only tests

On Thu, Sep 8, 2016 at 12:44 PM, Joe Hakim Rahme wrote: > On Thu, 2016-09-08 at 10:36 +0200, Andreas Jaeger wrote: > > > > Toni, sorry, I wasn't clear. I'm not advocating for this, I wanted to > > bring Joe into this discussion to see whether the solution that John > > suggested will help them as

Re: [openstack-dev] Election Season, PTL and TC September/October 2016

On 16-09-13 10:23 AM, Anita Kuno wrote: On 16-09-13 09:52 AM, Nate Johnston wrote: On Tue, Sep 13, 2016 at 07:48:06AM -0500, Sean McGinnis wrote: On Tue, Sep 13, 2016 at 05:14:56PM +1000, Tony Breeds wrote: On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: Lastly, election o

[openstack-dev] [nova] Tracking newton-rc-potential fixes for RC1 on Thursday 9/15

I've started an etherpad here: https://etherpad.openstack.org/p/nova-newton-rc-potential We'll use that for tracking the newton-rc-potential bugs and last few remaining placement fixes before we cut RC1 on Thursday. -- Thanks, Matt Riedemann ___

Re: [openstack-dev] Election Season, PTL and TC September/October 2016

On 16-09-13 09:52 AM, Nate Johnston wrote: On Tue, Sep 13, 2016 at 07:48:06AM -0500, Sean McGinnis wrote: On Tue, Sep 13, 2016 at 05:14:56PM +1000, Tony Breeds wrote: On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: Lastly, election officials are also reachable through the #

[openstack-dev] [watcher] PTL candidacy

Hello everyone, I would like to announce my candidacy to continue as Watcher PTL for the Ocata release. [1] During the Newton cycle, our main achievement was to enter the OpenStack big tent by demonstrating a great diversity of contributors and the added-value of an infrastructure optimization se

Re: [openstack-dev] [tripleo] tripleo-test-cloud-rh1 and bastion host

On Tue, Sep 13, 2016 at 12:53:41PM +0100, Derek Higgins wrote: > On 9 September 2016 at 16:38, Paul Belanger wrote: > > Greetings, > > > > I would like to start the discussions around the removal of the bastion host > > that sits in front of tripleo-test-cloud-rh1. It is my understanding, all > >

Re: [openstack-dev] Election Season, PTL and TC September/October 2016

On Tue, Sep 13, 2016 at 07:48:06AM -0500, Sean McGinnis wrote: > On Tue, Sep 13, 2016 at 05:14:56PM +1000, Tony Breeds wrote: > > On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: > > > > > Lastly, election officials are also reachable through the > > > #openstack-election Freenod

Re: [openstack-dev] [cinder] moving driver to open source

On 13 September 2016 at 06:44, Ben Swartzlander wrote: > On 09/09/2016 11:12 AM, Duncan Thomas wrote: > >> I don't care so much whether your CLI or API proxy in open or closed >> source, but I really do care if I can create a distribution, even a >> novel one, with that software in it, without hi

[openstack-dev] [Nova] Iive migration IRC meeting

There will be a meeting today – just amended the agenda: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.

Re: [openstack-dev] [cinder] moving driver to open source

On 2016-09-12 23:44:10 -0400 (-0400), Ben Swartzlander wrote: [...] > I don't understand how you can have this stance while tolerating the > existence of such things as the VMware driver. That software (ESXi) > absolutely requires a license to use or distribute. If it has to be installed on the sa

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

Hi Gary? I mean maybe that can be one choice in my mind. Security Group is for each neutron port?in this case?all the docker on one vm will share one neutron port?if I understand correct??then they will share the security group on that port?it is not per container per security group?not sure h

Re: [openstack-dev] Election Season, PTL and TC September/October 2016

On Tue, Sep 13, 2016 at 05:14:56PM +1000, Tony Breeds wrote: > On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: > > > Lastly, election officials are also reachable through the > > #openstack-election Freenode channel. > > I wonder if it's worth having all conversations in #opens

Re: [openstack-dev] [Congress] Default devstack deployment config

I completely agree with a single process deployment for DevStack. I ran into issues last week with the multiple process configuration while I trying to pinpoint an error. I was using the pdb command line debugger to step through Congress and Oslo Messaging, making a call from the CLI. More than on

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

Hi Liping, Thank you for the feedback! Do you mean to have disabled security groups as an optional configuration for Kuryr? Do you have any opinion on the consequences/acceptability of disabling SG? Regards, Gary From: Liping Mao (limao) [mailto:li...@cisco.com] Sent: Tuesday, September 13, 20

Re: [openstack-dev] [tripleo] Overriding internal_api network name

On 09/12/2016 11:08 PM, Steven Hardy wrote: On Mon, Sep 12, 2016 at 04:21:43PM +0200, Dmitry Tantsur wrote: Hi folks! I'm looking into support for multiple overclouds with shared control plane. I'm porting a downstream guide: https://review.openstack.org/368840. However, this no longer works,

Re: [openstack-dev] [fuel-library] Nominate Stanislaw Bogatkin to fuel-library core

+1 Aleksey Kasatkin On Mon, Sep 12, 2016 at 5:01 PM, Alex Schultz wrote: > +1 > > On Wed, Sep 7, 2016 at 5:07 PM, Maksim Malchuk > wrote: > > Hello, > > > > I would like to nominate Stanislaw Bogatkin to fuel-library core due to > his > > significant contribution to the project [1] and [2].

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

Hi Ivan? It sounds cool? for security group and allowed address pair? Maybe we can disable port-security?because all the docker in one vm will share one security group on the vm port. I'm not sure how to use sg for each docker?maybe just disable port-security can be one of the choice. then do n

Re: [openstack-dev] [tripleo] tripleo-test-cloud-rh1 and bastion host

On 9 September 2016 at 16:38, Paul Belanger wrote: > Greetings, > > I would like to start the discussions around the removal of the bastion host > that sits in front of tripleo-test-cloud-rh1. It is my understanding, all > traffic from tripleo-test-cloud-rh1 flows through this linux box. Obvious

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

> -Original Message- > From: Thierry Carrez [mailto:thie...@openstack.org] > Sent: Tuesday, September 13, 2016 3:45 AM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [all] governance proposal worth a visit: > Write down OpenStack principles > > Clay Gerrard wrote:

Re: [openstack-dev] [kuryr] Spec and devref placement

+1，option b） > 在 2016年9月12日，19:39，Antoni Segura Puimedon 写道： > > Hi Kuryrs! > > On September 5th's weekly IRC meeting Irena Berezovsky suggested that > we should take a decision regarding the location of specs and devrefs. > > Currently we default to putting all the specs and devrefs for: > -

Re: [openstack-dev] [ironic] weekly subteam report

On Tue, Sep 13, 2016 at 7:27 AM, Dmitry Tantsur wrote: > On 09/13/2016 12:52 PM, Pavlo Shchelokovskyy wrote: >> >> Hi all, >> >> On Mon, Sep 12, 2016 at 9:28 PM, Loo, Ruby > > wrote: >> >> Cross-project: >> == >> - Infra insists on switching new j

Re: [openstack-dev] [ironic] weekly subteam report

On 09/13/2016 12:52 PM, Pavlo Shchelokovskyy wrote: Hi all, On Mon, Sep 12, 2016 at 9:28 PM, Loo, Ruby mailto:ruby@intel.com>> wrote: Cross-project: == - Infra insists on switching new jobs to Xenial A small heads up. If we have any gate jobs that use PXE instead o

Re: [openstack-dev] [ironic] weekly subteam report

Hi all, On Mon, Sep 12, 2016 at 9:28 PM, Loo, Ruby wrote: > Cross-project: > == > - Infra insists on switching new jobs to Xenial > A small heads up. If we have any gate jobs that use PXE instead of iPXE, those won't work on Xenial with current Ironic devstack plugin due to some pac

[openstack-dev] [Fuel] PTL non candidacy

Dear colleagues, Newton cycle is getting to its end and it is time to look at what we've managed to achieve by the moment. * Improved task based deployment engine (memory efficiency, code structure, graph sequences, noop run). * Re-implemented OS provisioning as a graph. Now it is one of the gr

[openstack-dev] [ironic][devstack][devstack-gate][networking-generic-switch] Ironic multinode job

Hello Community, I'm happy to announce that we got stable ironic multinode job. There are a lot of patches (around 20) to different projects needed to be merged before we can move this job to check pipeline. That is why I'm writing this email to openstack-dev. I'm kindly asking cores from the de

[openstack-dev] [all] Ocata Design Summit - Proposed slot allocation

Hi PTLs, Here is the proposed slot allocation for project teams at the Ocata Design Summit in Barcelona. This is based on the requests the current PTLs have made, adjusted to account for limited space availability. | fb: fishbowl 40-min slots (Wednesday afternoon - Friday morning) | wr: workroom

Re: [openstack-dev] [glance] [elections] Glance PTL non-candidacy

Hi Nikhil, You are the first PTL I knew when I started to work with OpenStack community, we can see your hard work for Glance during these cycles. I have learned a lot from your review suggestion. Thanks very much!!! And it's great to know that you still work on Glance. Best wishes. 2016-09-13

Re: [openstack-dev] [kolla] potential Ansible template issue you may meet

thanks for heads up. suggest we add this to the kolla docs as is easy to forget about it On Tue, Sep 13, 2016 at 3:15 AM, Jeffrey Zhang wrote: > When using ansible template module, you may see the trailing newline > is stripped by blocks, like > > # template.j2 > a = {% if true %}1{% endfor %}

Re: [openstack-dev] Election Season, PTL and TC September/October 2016

Tony Breeds wrote: > On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: > >> Lastly, election officials are also reachable through the >> #openstack-election Freenode channel. > > I wonder if it's worth having all conversations in #openstack-dev? > > There are pros and cons to bo

Re: [openstack-dev] [release] proposing adding Tony Breeds to "Release Managers" team

+1 , Tony Breads is a nice guy, glad to see release team make openstack more better :-) 2016-09-13 12:53 GMT+08:00 Swapnil Kulkarni : > On Tue, Sep 6, 2016 at 9:06 PM, Doug Hellmann > wrote: > > Team, > > > > I would like to add Tony Breeds to the "Release Managers" team in > > gerrit. This woul

Re: [openstack-dev] [all] governance proposal worth a visit: Write down OpenStack principles

Clay Gerrard wrote: > This is why I always have and presumably always will support Thierry on > the TC. His initial thinking *frequently* seems out of alignment with > me, but after observing others healthy debate and discussion [1] - I > always find we tend we both come around a little and seem t

Re: [openstack-dev] [kuryr] Spec and devref placement

Agree with Irena's proposal. Also ok with option b. On Mon, Sep 12, 2016 at 5:18 PM, Irena Berezovsky wrote: > I am fine with option (b) as well. > We can add option (d): > Specs in openstack/*kuryr-specs* but devrefs in each specific project, > i.e., the one that will end up with the implementa

Re: [openstack-dev] [Karbor] Thoughts on Decoupling Checkpoint API from the current Provider API

hi, Leon: welcome to join the Karbor project. sounds a good suggestion, but the checkpoints belong to each provider in current design, I am afraid of there are many impactive points for the whole framework. did you make design impact analysis? 2016-09-11 20:45 GMT+08:00 Leon Wang :

Re: [openstack-dev] Election Season, PTL and TC September/October 2016

On Fri, Sep 02, 2016 at 12:10:53PM +, Tristan Cacqueray wrote: > Lastly, election officials are also reachable through the > #openstack-election Freenode channel. I wonder if it's worth having all conversations in #openstack-dev? There are pros and cons to both. Having a single purpose elec

Re: [openstack-dev] [Release] [FFE] two xstatic packages to be bumped in upper-constraints, please

On Tue, Sep 13, 2016 at 6:09 AM, Richard Jones wrote: > Hi folks, > > We have two patches to upper-constraints up that we'd like to see merged for > Newton. The package updates in question only changed meta-data, but they did > so in a way that fixes issues for downstream, and it makes sense to ke

Re: [openstack-dev] [Release] [FFE] two xstatic packages to be bumped in upper-constraints, please

Am 13.09.2016 05:03 schrieb "Tony Breeds" : > > The reviews are: > > > > update constraint for XStatic-Bootstrap-SCSS to new release 3.3.7.1 > > https://review.openstack.org/#/c/368970/ > > > > update constraint for XStatic-smart-table to new release 1.4.13.2 > > https://review.openstack.org/#/c/3

[openstack-dev] Call for mentors and funding

Hello everyone, An update on the Outreachy program, including a request for volunteer mentors and funding. For those of you who are not aware, Outreachy helps people from underrepresented groups get involved in free and open source software by matching interns with established mentors in the upst

Re: [openstack-dev] [glance] Periodically checking Glance image files

On Tue, Sep 13, 2016 at 7:16 AM, Nikhil Komawar wrote: > Firstly, I'd like to mention that Glance is built-in (and if deployed > correctly) is self-resilient in ensuring that you do NOT need an audit > of such files. In fact, if any operator (particularly large scale > operator) ne

  1   2   >