Re: [openstack-dev] [all][infra][requirements] Odd cases in requirements?

On 10 November 2016 at 11:00, Tony Breeds wrote: > On Thu, Nov 10, 2016 at 06:17:44AM +1300, Robert Collins wrote: >> Sed doesn't exist on windows, whereas a python script can. Sed doesn't >> handle multiple line constraints. > > I don't think that right now we

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

Will the same DB be maintained or will the LBaaS DB be moved to that of Octavia. I am really concerned about this and I feel that it will cause production problems. From: Kevin Benton Reply-To: OpenStack List Date: Wednesday, November 9,

[openstack-dev] [ironic][ironic-python-agent]code-review about this commit https://review.openstack.org/#/c/369245/

Hi ironic team： I send this email to ask something about https://review.openstack.org/#/c/369245/ . The jenkins has +1 for this commit.I hope you could spare some time to give me some advice of this commit. If it looks good to you，could you please do the workflow？ Thank you very much.

Re: [openstack-dev] [nova] vendordata v2 ocata summit recap

This is a good summary, thanks. I finally uploaded the spec which describes the decisions from the summit. Its here: https://review.openstack.org/395959 Michael On Thu, Nov 10, 2016 at 7:11 AM, Matt Riedemann wrote: > Michael Still led a session on completing

Re: [openstack-dev] [new][keystone] keystonemiddleware 2.3.4 release (liberty)

On Thu, Nov 10, 2016 at 01:10:45AM +, no-re...@openstack.org wrote: > We are grateful to announce the release of: > > keystonemiddleware 2.3.4: Middleware for OpenStack Identity > > This release is part of the liberty stable release series. Actually this release didn't happen the mail was

Re: [openstack-dev] [new][keystone] keystoneauth1 1.1.3 release (liberty)

On Thu, Nov 10, 2016 at 01:10:18AM +, no-re...@openstack.org wrote: > We are glad to announce the release of: > > keystoneauth1 1.1.3: Authentication Library for OpenStack Identity > > This release is part of the liberty stable release series. Actually this release didn't happen the mail

Re: [openstack-dev] [release] change in plan for releases repo data model updates

Sorry for top posting, but exchange Automation is our friend. Define the structure/naming of the release repo patches such that when they merge, they auto generate the governance patch and submit it. It gives you time to run a cycle and see how things work and what a more elegant

Re: [openstack-dev] [manila] Barcelona Design Summit summary

On 11/04/2016 02:00 PM, Joshua Harlow wrote: Ben Swartzlander wrote: Thanks to gouthamr for doing these writeups and for recording! We had a great turn out at the manila Fishbowl and working sessions. Important notes and Action Items are below: === Fishbowl 1: Race

[openstack-dev] [nova][cinder] nova/cinder cross-project ocata summit session recap

On Thursday at the summit the Cinder team had a session about the proposed volume attach/detach API changes that John Griffith is working on. The etherpad for that session is here: https://etherpad.openstack.org/p/ocata-nova-summit-cinder-session On Friday we had a joint nova/cinder session

Re: [openstack-dev] [kolla] How tied is kolla to matching 1:1 releases of openstack?

Fox, Kevin M wrote: currently one to one on kolla version and openstack release. so 2.0.x is mitaka. 3.0.x is newton. I think if we continue forward with the helm idea it will simplify the use case too. as you can then match up a k8s package (with its templates) for a mitaka resource with

[openstack-dev] [new][keystone] keystonemiddleware 2.3.4 release (liberty)

We are grateful to announce the release of: keystonemiddleware 2.3.4: Middleware for OpenStack Identity This release is part of the liberty stable release series. The source is available from: http://git.openstack.org/cgit/openstack/keystonemiddleware Download the package from:

[openstack-dev] [new][keystone] keystoneauth1 1.1.3 release (liberty)

We are glad to announce the release of: keystoneauth1 1.1.3: Authentication Library for OpenStack Identity This release is part of the liberty stable release series. The source is available from: http://git.openstack.org/cgit/openstack/keystoneauth Download the package from:

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

Kevin, Yep, totally understand. This is not a V3, it is simply moving the API from running under neutron to running under the octavia API process. It will still be the LBaaSv2 API, just a new endpoint (though the old endpoint will work for some time into the future). Michael On Wed, Nov 9,

Re: [openstack-dev] [kolla] How tied is kolla to matching 1:1 releases of openstack?

currently one to one on kolla version and openstack release. so 2.0.x is mitaka. 3.0.x is newton. I think if we continue forward with the helm idea it will simplify the use case too. as you can then match up a k8s package (with its templates) for a mitaka resource with the mitaka containers.

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

Ok. cool. thanks. :) Kevin From: Kevin Benton [ke...@benton.pub] Sent: Wednesday, November 09, 2016 1:43 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and

[openstack-dev] [valence] Valence week IRC meeting is at Wednesdays, 15:00 HRS UTC

USA folks, remember we have daylight savings time in effect now. So one hour earlier. Regards, Malini __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [kolla][kubernetes]kolla-kubernetes achitectures spec

Forgot to include the link to the spec :) https://review.openstack.org/#/c/392257/ Thanks, Ryan __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [glance] spec proposal freeze

Just a friendly reminder that the Glance Spec Proposal Freeze is imminent: All Glance, python-glanceclient, and glance_store specs must be proposed as patches to the glance-specs repository by 23:59 UTC on Thursday 10 November 2016. The purpose of the proposal freeze is to allow sufficient time

Re: [openstack-dev] [all][infra][requirements] Odd cases in requirements?

On Wed, Nov 09, 2016 at 12:00:27PM +0100, Ihar Hrachyshka wrote: > I believe sed is the way to go. There is not much we get from > edit-constraints at this point, and it untangles the script from zuul-cloner > that would be needed to fetch requirements repo. > > It seems like the way to go.

Re: [openstack-dev] [all][infra][requirements] Odd cases in requirements?

On Thu, Nov 10, 2016 at 06:17:44AM +1300, Robert Collins wrote: > Sed doesn't exist on windows, whereas a python script can. Sed doesn't > handle multiple line constraints. I don't think that right now we care/handle multiline constraints but the windows think is important and not something I

Re: [openstack-dev] [kolla] How tied is kolla to matching 1:1 releases of openstack?

Fox, Kevin M wrote: I think its kind of in the same vein as the rest of the openstack services. It might, (and probably will) work with n-1& n services in the same system. But it all depends on either: 1. The things that are actually tested or 2. Luck I've been testing the kolla-kubernetes

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

The people working on the migration are ensuring API compatibility and are even leaving in a shim on the Neutron side for some time so you don't even have to change endpoints initially. It should be a seamless change. On Wed, Nov 9, 2016 at 12:28 PM, Fox, Kevin M wrote: >

[openstack-dev] Sharing Cloudkitty Mascot

Hello developer mailing list folks, Like every other project in OpenStack, Cloudkitty has also received a draft logo. While that mascot has been widely shared amonsgt the other member of the Cloudkitty's community, I thought that some developpers from other teams migth be happy to have a

[openstack-dev] [TripleO] dhclient spawned by dhcp-all-interfaces doesn't exit when os-net-config runs

I just opened a bug [1] for behavior which has recently been observed when deploying nodes with TripleO. The problem is that the dhclient processes that are being started by the dhcp-all-interfaces element in disk-image-builder are not stopping after os-net-config runs. Step 1) Image deploys with

[openstack-dev] [glance] rolling upgrade virtual design session Friday 11 Nov

The poll has closed and the winning time for the Glance virtual design session on zero downtime rolling upgrades will be 14:00 UTC on Friday, 11 November 2016. The virtual design session will be held in an on-air Google hangout which should allow it to be recorded (though of course it would be

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

Just please don't make this a lbv3 thing that completely breaks compatibility of existing lb's yet again. If its just an "point url endpoint from thing like x to thing like y" in one place, thats ok. I still have v1 lb's in existence though I have to deal with and a backwards incompatible v3

[openstack-dev] [neutron] Barcelona summit "neutron-agent retrospective" recap

There were three main topics discussed during the neutron-agent retrospective session: deprecating the CLI OVS interfaces, refactoring the agent to use the callback framework, and eliminating the L2pop driver. Deprecating the CLI OVS Interfaces We

Re: [openstack-dev] [kolla] How tied is kolla to matching 1:1 releases of openstack?

I think its kind of in the same vein as the rest of the openstack services. It might, (and probably will) work with n-1 & n services in the same system. But it all depends on either: 1. The things that are actually tested or 2. Luck I've been testing the kolla-kubernetes deployment tools with

[openstack-dev] [nova] vendordata v2 ocata summit recap

Michael Still led a session on completing the vendordata v2 work that was started in the Newton release. The full etherpad is here: https://etherpad.openstack.org/p/ocata-nova-summit-vendoradatav2 Michael started by advertising a bit what it is since it's a new feature and it's meant to

[openstack-dev] [kolla][kubernetes]kolla-kubernetes achitectures spec

Hey folks, The kolla-kubernetes architecture spec has been under review for a day now. The plan is to keep it open for 7 days after the initial review was posted (November 8th). Therefore, voting on the spec will commence on November 15th. So be sure to add any input you may have before that

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

On 11/04/2016 10:40 AM, Emilien Macchi wrote: > MIchele Baldessari (bandini on IRC) has consistently demonstrated high > levels of contributions in TripleO projects, specifically in High > Availability area where's he's for us a guru (I still don't understand > how pacemaker works, but hopefully

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On Wed, Nov 9, 2016 at 3:14 AM, Chris Dent wrote: > > As a community we don't want to be bound together by rules, we want > to be enabled by processes that support making and doing things > effectively. The things that we make and do is what binds us > together. > Here

[openstack-dev] [kolla] How tied is kolla to matching 1:1 releases of openstack?

Hi kolla folks, As I am (and others at godaddy) are working through integrating kolla image building into our jenkins pipeline(s), Currently the pipeline is the following (taking an example of glance), # Checkout stage 1. Checkout kolla at X tag/branch 2. Checkout glance at Y tag/branch 3.

Re: [openstack-dev] [all][infra][requirements] Odd cases in requirements?

Sed doesn't exist on windows, whereas a python script can. Sed doesn't handle multiple line constraints. Rob On 10 Nov 2016 12:00 AM, "Ihar Hrachyshka" wrote: > > > On 8 Nov 2016, at 04:07, Tony Breeds wrote: > > > > On Sat, Sep 03, 2016 at

Re: [openstack-dev] [Openstack] [all][infra][requirements] Odd cases in requirements?

Ah, thanks a lot for that info :) I think that is what I need. On Wed, Nov 9, 2016 at 7:36 AM, Jeremy Stanley wrote: > On 2016-11-09 07:19:04 -0800 (-0800), John Villalovos wrote: > > Sort of related, what is the plan for supporting requirements which are > > Python 3 only

Re: [openstack-dev] Anyone want to meetup at KubeCon?

You can try finding Brad Topol, he's presently at Kubecon and familiar with all things Keystone. On Tue, Nov 8, 2016 at 4:49 PM, Stephen McQuaid wrote: > We have been developing a keystone authz webhook for easy integration. If > anyone is interested we can look at

[openstack-dev] FOSDEM 2017: Call For Proposals -- Virtualization & IaaS DevRoom

=== The call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2017, to be hosted on February 4, 2017. This year will mark FOSDEM’s 17th anniversary as one of the longest-running free and

Re: [openstack-dev] [tripleo] Please review, tripleo ci transition to the quickstart tool set

On 08 Nov, Wesley Hayutin wrote: > [3], please if you have time review the etherpad and respond with any > questions, suggestions or concerns. Hi, I added a step on the PRE phase (line 192) in [3] regarding logs. Coming from TripleO CI developers may feel lost when they try to debug a failure.

Re: [openstack-dev] [keystone][nova][cinder][horizon][all] properties / metadata for resources

On Tue, Nov 8, 2016 at 4:12 PM, Gage Hugo wrote: > The idea is that a cloud admin could define a list of keys that they need > for their setup within keystone's configuration file, then only those keys > will be valid for storing values in the project properties table. Then

Re: [openstack-dev] Anyone want to meetup at KubeCon?

On Nov 8, 2016 4:53 PM, "Stephen McQuaid" wrote: > > We have been developing a keystone authz webhook for easy integration. If anyone is interested we can look at open-sourcing it > > > > Stephen McQuaid > > Sr. Software Engineer | Kubernetes & Openstack > > GoDaddy > > > >

Re: [openstack-dev] [MassivelyDistributed] bi-weekly meeting - Timeslot ?

Thierry Carrez wrote: > lebre.adr...@free.fr wrote: >> After Thierry's cleaning, the possibilities are the following ones: >> >> Wednesday 14 UTC (odd week) >> Wednesday 17 UTC >> Thursday 14 UTC (odd week) >> Thursday 16 UTC (even week) >> Thursday 17 UTC (even week) > > Thursday 15 UTC is

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

Hi Gary, Our intent is to merge neutron-lbaas into the Octavia project. When this is complete, the neutron-lbaas project will remain for some time as a light weight shim/proxy that provides the legacy neutron endpoint experience. The database models are already very similar to the existing

Re: [openstack-dev] [tripleo] proposing Michele Baldessari part of core team

+1 from me. Dan On Fri, 2016-11-04 at 13:40 -0400, Emilien Macchi wrote: > MIchele Baldessari (bandini on IRC) has consistently demonstrated > high > levels of contributions in TripleO projects, specifically in High > Availability area where's he's for us a guru (I still don't > understand > how

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

On 9 November 2016 at 05:50, Gary Kotton wrote: > Hi, > What about neutron-lbaas project? Is this project still alive and kicking > to the merge is done or are we going to continue to maintain it? I feel > like we are between a rock and a hard place here. LBaaS is in

Re: [openstack-dev] [Openstack] [all][infra][requirements] Odd cases in requirements?

On 2016-11-09 07:19:04 -0800 (-0800), John Villalovos wrote: > Sort of related, what is the plan for supporting requirements which are > Python 3 only packages? > > In particular the package: mypy-lang > https://pypi.python.org/pypi/mypy-lang [...] If you only want mypy-lang installed when the

[openstack-dev] [OpenStack-docs] [openstack deployment] Adding deployment guides to docs.o.o

Hi everyone, A discussion was held in the OpenStack manuals social track at the Barcelona summit and we agreed to start including deployment projects, with appropriate installation guide(s), into the docs.o.o site. Similar to what we have done with the Installation

Re: [openstack-dev] [Openstack] [all][infra][requirements] Odd cases in requirements?

Sort of related, what is the plan for supporting requirements which are Python 3 only packages? In particular the package: mypy-lang https://pypi.python.org/pypi/mypy-lang I was considering adding some type hints to the ironic-lib project in the future. But it needs to run the mypy program to do

Re: [openstack-dev] [AODH] event-alarm timeout discussion

On Mon, Sep 26 2016, Zhai, Edwin wrote: > Do you have any idea to resolve this race condition? So following our discussion at the summit, I went ahead and wrote a spec about that feature: https://review.openstack.org/#/c/395058/ Comments are welcome obviously! Cheers, -- Julien Danjou #

[openstack-dev] [fuel][tripleo] Fuel and TripleO Cross-Project Integration

Stackers During OpenStack summit in Barcelona we had a rather productive cross-project integration session between Fuel and TripleO projects [0]. More precisely we discussed the following: 1. Services composition and deployment workflow control 2. Complex networking configuration (bonds,

Re: [openstack-dev] [horizon] USE_SSL

On Wed, Nov 9, 2016 at 1:56 PM, Rob Cresswell wrote: > Was that ever in local_settings? I couldnt find any mention of it. > Yes, seems to have stopped being used around Kilo: http://docs.openstack.org/kilo/config-reference/content/configure-dashboard.html > The

Re: [openstack-dev] [all] important changes to pep8 python jobs

  -Original Message- From: Paul Belanger Reply: OpenStack Development Mailing List (not for usage questions) Date: November 8, 2016 at 17:19:40 To: openstack-dev@lists.openstack.org Subject: 

[openstack-dev] Fwd: Re: [requirements][kolla][security] pycrypto vs cryptography

Apparently Paul's email didn't make it through, so I'm forwarding it to y'all since it pertinent information. -Original Message- From: Paul Kehrer Reply: Paul Kehrer Date: November 8, 2016 at 23:39:32 To: Ian Cordasco

Re: [openstack-dev] [horizon] USE_SSL

Was that ever in local_settings? I couldnt find any mention of it. The Django docs are probably your best bet for information: https://docs.djangoproject.com/en/1.10/topics/security/#ssl-https Rob On 9 November 2016 at 13:23, Luke Hinds > wrote: Hi,

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

Hi, What about neutron-lbaas project? Is this project still alive and kicking to the merge is done or are we going to continue to maintain it? I feel like we are between a rock and a hard place here. LBaaS is in production and it is not clear the migration process. Will Octavia have the same DB

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On Wed, Nov 9, 2016 at 3:14 AM, Chris Dent wrote: > On Tue, 8 Nov 2016, Ash wrote: > > I couldn't agree more. I don't like change for the sake of change (in any >> aspect of my life). So in my mind this would have to be a way to better >> bind us. >> > > Here, have some

Re: [openstack-dev] [mistral] Promoting Dougal Matthews to the core team

On 09/11/16 07:34, Renat Akhmerov wrote: Ok, thank you all! Dougal, welcome to the core team! I’m hoping for fruitful collaboration with you :) Congratulations, Dougal! Miles __ OpenStack Development Mailing List (not

[openstack-dev] [horizon] USE_SSL

Hi, I have noted that USE_SSL is no longer in local_settings.py I have not had any luck in having google find the background of why this was removed for first django (if it has?) and horizon. >From what I can see, it seems related to django views. Does anyone understand the context of this

Re: [openstack-dev] [release] change in plan for releases repo data model updates

Doug Hellmann wrote: > At the summit we said we would move the data that tells us the type > and release model for each deliverable out of the governance > repository and into the releases repository where it is easier to > change over time, but that we needed to think more about what might >

Re: [openstack-dev] [all] Embracing new languages in OpenStack

On Tue, 8 Nov 2016, Ash wrote: I couldn't agree more. I don't like change for the sake of change (in any aspect of my life). So in my mind this would have to be a way to better bind us. Here, have some tortured metaphors: Something that feels like it gets under-emphasised in this

Re: [openstack-dev] [MassivelyDistributed] bi-weekly meeting - Timeslot ?

lebre.adr...@free.fr wrote: > After Thierry's cleaning, the possibilities are the following ones: > > Wednesday 14 UTC (odd week) > Wednesday 17 UTC > Thursday 14 UTC (odd week) > Thursday 16 UTC (even week) > Thursday 17 UTC (even week) Thursday 15 UTC is also an option. Also note that

Re: [openstack-dev] [all][infra][requirements] Odd cases in requirements?

> On 8 Nov 2016, at 04:07, Tony Breeds wrote: > > On Sat, Sep 03, 2016 at 07:33:42PM +0200, Andreas Jaeger wrote: >> Reviewing all the constraints work, I see that repositories have created >> some workaround around requirements install for one of these two legimit >>

Re: [openstack-dev] [tripleo] possible backports for stable/newton

> Since our cherry picks don't seem to be considered equivalents by git > (probably because of modified commit messages) I'd like to understand why is that, do you have an example? It should work when recommendation[*] is followed. Cheers, Alan [*]

Re: [openstack-dev] [requirements][kolla][security] pycrypto vs cryptography

Daviey, I pointed this out to Pavo as well a few weeks ago. I’m not sure if it mattered or not. Regards -steve From: Dave Walker > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [MassivelyDistributed] bi-weekly meeting - Timeslot ?

Dear all After Thierry's cleaning, the possibilities are the following ones: Wednesday 14 UTC (odd week) Wednesday 17 UTC Thursday 14 UTC (odd week) Thursday 16 UTC (even week) Thursday 17 UTC (even week) Please add +1 for the slot that is the most convenient from your side. I would

Re: [openstack-dev] [mistral] Promoting Dougal Matthews to the core team

Thanks everyone, looking forward to helping out more! Cheers, Dougal On 9 November 2016 at 07:34, Renat Akhmerov wrote: > Ok, thank you all! > > Dougal, welcome to the core team! I’m hoping for fruitful collaboration > with you :) > > Renat Akhmerov > @Nokia > > On 8

[openstack-dev] [tricircle]agenda of weekly meeting Nov.9

Hello, team, Agenda of Nov.9 weekly meeting: 1. Tricircle big-tent application info share 2. Ocata feature development discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. If you have other topics