Re: [openstack-dev] [tripleo] PTG topics and agenda

On 8/28/18 2:50 PM, Juan Antonio Osorio Robles wrote: > Hello folks! > > > With the PTG being quite soon, I just wanted to remind folks to add your > topics on the etherpad: https://etherpad.openstack.org/p/tripleo-ptg-stein thanks Juan, I think the Edge (line 53) and Split Control Plane (line

Re: [openstack-dev] [stable][nova] Nominating melwitt for nova stable core

On 28-08-18 15:26:02, Matt Riedemann wrote: > I hereby nominate Melanie Witt for nova stable core. Mel has shown that she > knows the stable branch policy and is also an active reviewer of nova stable > changes. > > +1/-1 comes from the stable-maint-core team [1] and then after a week with > no

Re: [openstack-dev] Update global upper constraint of Kubernetes from 7.0.0 to 6.0.0

Hi Matthew, Seems that Openshift version 0.7 was released few hours ago, this version should work properly with kubernetes. I"ll update my PR to change openshift upper constraint to 0.7 and leave K8S at 7.0.0 10x Yossi בתאריך יום ה׳, 30 באוג׳ 2018, 19:12, מאת Matthew Thode ‏<

[openstack-dev] [senlin] weekly meeting

Hi everyone, We'll be having our weekly meeting today at 0530 UTC in the #senlin channel. The meeting agenda has been posted: https://wiki.openstack.org/wiki/Meetings/SenlinAgenda#Agenda_.282018-08-31_0530_UTC.29 Regards, Duc

Re: [openstack-dev] [openstack-ansible] Stepping down from OpenStack-Ansible core

Thanks for all you do and have done for the OpenStack Community, Andy :) Andy McCrae wrote: Now that Rocky is all but ready it seems like a good time! Since changing roles I've not been able to keep up enough focus on reviews and other obligations - so I think it's time to step aside as a core

Re: [openstack-dev] [all] Bringing the community together (combine the lists!)

On 2018-08-30 12:57:31 -0600 (-0600), Chris Friesen wrote: [...] > Do we want to merge usage and development onto one list? That > could be a busy list for someone who's just asking a simple usage > question. A counterargument though... projecting the number of unique posts to all four lists

Re: [openstack-dev] [Openstack-operators] [all] Bringing the community together (combine the lists!)

On 2018-08-30 22:49:26 +0200 (+0200), Thomas Goirand wrote: [...] > I really don't want this. I'm happy with things being sorted in > multiple lists, even though I'm subscribed to multiples. I understand where you're coming from, and I used to feel similarly. I was accustomed to communities where

Re: [openstack-dev] [TripleO]Addressing Edge/Multi-site/Multi-cloud deployment use cases (new squad)

On Mon, Aug 20, 2018 at 4:47 PM James Slagle wrote: > https://etherpad.openstack.org/p/tripleo-edge-squad-status Several folks have signed up for the squad, so I've added a poll in the etherpad to pick a meeting time. > -- > -- James Slagle > -- -- -- James Slagle --

[openstack-dev] [TC][All] Guidelines for Organisations Contributing to OpenStack

Hello, Backstory on this topic: conversations started before the Vancouver Summit about drafting a base set of necessities that we could give to companies to help them understand what their employees will need if they are going to be effective contributors to OpenStack. There was initial

Re: [openstack-dev] [all] Bringing the community together (combine the lists!)

On 08/30/2018 08:57 PM, Chris Friesen wrote: > On 08/30/2018 11:03 AM, Jeremy Stanley wrote: > >> The proposal is simple: create a new openstack-discuss mailing list >> to cover all the above sorts of discussion and stop using the other >> four. > > Do we want to merge usage and development onto

Re: [openstack-dev] [openstack-ansible] Stepping down from OpenStack-Ansible core

Andy, We’ll miss you! Thanks so much for all your hard work and leadership. Don’t be a stranger! Amy (spotz) Sent from my iPhone > On Aug 30, 2018, at 11:05 AM, Ian Y. Choi wrote: > > Hello Andy, > > Thanks a lot for your work on OpenStack-Ansible team. > > It was very happy to

[openstack-dev] [goals][python3] small change of schedule for changing packaging jobs

I had originally been planning to wait for the cycle-trailing projects to finish Rocky before updating the release jobs to use the python3 versions. However, Sean reminded me today that we extended the deadline for cycle-trailing projects to 2 months from now, and I don't think we want to wait

Re: [openstack-dev] [all] Bringing the community together (combine the lists!)

I’m strongly in support of merging the lists. > On Aug 30, 2018, at 2:57 PM, Chris Friesen > wrote: > > On 08/30/2018 11:03 AM, Jeremy Stanley wrote: > >> The proposal is simple: create a new openstack-discuss mailing list >> to cover all the above sorts of discussion and stop using the other

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from Doug Hellmann's message of 2018-08-29 20:04:16 -0400: > Excerpts from Doug Hellmann's message of 2018-08-29 15:22:56 -0400: > > Excerpts from David Peacock's message of 2018-08-29 15:12:03 -0400: > > > On Wed, Aug 29, 2018 at 1:02 PM Doug Hellmann > > > wrote: > > > > > > >

Re: [openstack-dev] [Openstack-sigs] [all] Bringing the community together (combine the lists!)

On 2018-08-31 01:13:58 +0800 (+0800), Rico Lin wrote: [...] > What needs to be done for this is full topic categories support > under `options` page so people get to filter emails properly. [...] Unfortunately, topic filtering is one of the MM2 features the Mailman community decided nobody used

Re: [openstack-dev] [Openstack-operators] [all] Bringing the community together (combine the lists!)

Jeremy Stanley wrote: On 2018-08-30 22:49:26 +0200 (+0200), Thomas Goirand wrote: [...] I really don't want this. I'm happy with things being sorted in multiple lists, even though I'm subscribed to multiples. IMO this is easily solved by tagging. If emails are properly tagged (which they

[openstack-dev] [all] Bringing the community together (combine the lists!)

The openstack, openstack-dev, openstack-sigs and openstack-operators mailing lists on lists.openstack.org see an increasing amount of cross-posting and thread fragmentation as conversants attempt to reach various corners of our community with topics of interest to one or more (and sometimes all)

Re: [openstack-dev] [ironic][tripleo][edge] Discussing ironic federation and distributed deployments

Greetings everyone, It looks like the most agreeable time on the doodle[1] seems to be Tuesday September 4th at 13:00 UTC. Are there any objections to using this time? If not, I'll go ahead and create an etherpad, and setup a bluejeans call for that time to enable high bandwidth discussion.

Re: [openstack-dev] [all] Bringing the community together (combine the lists!)

I fully support merging the lists proposed, as well as the interop-wg list that Chris Hodge proposed. I look forward to the day when cross posting is no longer a necessary evil. -Julia On Thu, Aug 30, 2018 at 10:04 AM Jeremy Stanley wrote: > > The openstack, openstack-dev, openstack-sigs and

Re: [openstack-dev] [neutron][nova] Small bandwidth demo on the PTG

Gibi, Bence, In fact, I added the demo explicitly to the Neutron PTG agenda from 1:30 to 2, to give it visiblilty Cheers On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer wrote: > Hi, > > Based on the Nova PTG planning etherpad [1] there is a need to talk about > the current state of the

Re: [openstack-dev] Update global upper constraint of Kubernetes from 7.0.0 to 6.0.0

בתאריך יום ה׳, 30 באוג׳ 2018, 19:12, מאת Matthew Thode ‏< prometheanf...@gentoo.org>: > On 18-08-30 17:54:24, Yossi Boaron wrote: > > Hi All, > > > > Kubernetes upper constraint was changed lately from 6.0.0 to 7.0.0 [1]. > > Currently, the Openshift python client can't work with Kubernetes

Re: [openstack-dev] Update global upper constraint of Kubernetes from 7.0.0 to 6.0.0

On 18-08-30 20:48:39, Yossi Boaron wrote: > Hi Matthew, > > Seems that Openshift version 0.7 was released few hours ago, this version > should work properly with kubernetes. > I"ll update my PR to change openshift upper constraint to 0.7 and leave K8S > at 7.0.0 > > 10x > Yossi > > בתאריך יום

[openstack-dev] Inquiry about an opportunity to do a thesis project in collaboration with a OpenStack project.

Hi, I am Aniketh Girish, a Junior year Computer Science Engineering student at the Amrita University, Kerala, India. I’m writing to you to inquire about the possibility to do my thesis project in accordance with the OpenStack community and a project in the community. I had initiated to

Re: [openstack-dev] Inquiry about an opportunity to do a thesis project in collaboration with a OpenStack project.

Thank you for your intereset :) Another great place to start is here: https://www.openstack.org/community This page has links to the Contributor Guide, as well as info on all of the OpenStack projects. Another great way to catch up with the community is the OpenStack Summit. We have one

Re: [openstack-dev] [Openstack-sigs] [all] Bringing the community together (combine the lists!)

+1 on this idea, people been posting around for the exactly same topic and got feedback from ops or devs, but never together, this will help people do discussion on the same table. What needs to be done for this is full topic categories support under `options` page so people get to filter emails

Re: [openstack-dev] Stepping down as keystone core

Thanks for all the help Samuel. I remember a couple instances when I first started contributing to keystone where you helped me out and I am extremely grateful. It was great working with you, and hopefully we will still see you around! On Wed, Aug 29, 2018 at 2:33 PM Lance Bragstad wrote: >

Re: [openstack-dev] Update global upper constraint of Kubernetes from 7.0.0 to 6.0.0

On 18-08-30 17:54:24, Yossi Boaron wrote: > Hi All, > > Kubernetes upper constraint was changed lately from 6.0.0 to 7.0.0 [1]. > Currently, the Openshift python client can't work with Kubernetes 7.0.0, > this caused by a version pinning issue (pulled in Kubernetes 7.0.0). > As a result of that,

[openstack-dev] [nova][placement] Freezing placement for extraction

Greetings. The captains of placement extraction have declared readiness to begin the process of seeding the new repository (once [1] has finished merging). As such, we are freezing development in the affected portions of the openstack/nova repository until this process is completed. We're relying

Re: [openstack-dev] [Openstack-operators] [nova][cinder][neutron] Cross-cell cold migration

> > > > Yeah it's already on the PTG agenda [1][2]. I started the thread because I > > wanted to get the ball rolling as early as possible, and with people that > > won't attend the PTG and/or the Forum, to weigh in on not only the known > > issues with cross-cell migration but also the things I'm

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

Greetings OpenStack community, There was nothing specific on the agenda this week, so much of the API-SIG meeting was spent discussing API-related topics that we'd encountered recently. One was: K8s Custom Resources [9] Cool or Chaos? The answer is, of course, "it depends". Another was a

Re: [openstack-dev] [neutron][python3] Neutron and stadium - python 3 community goal changes coming soon

Excerpts from Andreas Jaeger's message of 2018-08-30 17:32:46 +0200: > On 2018-08-30 17:16, Nate Johnston wrote: > > On Thu, Aug 30, 2018 at 08:28:40AM -0400, Doug Hellmann wrote: > >> Excerpts from Michel Peterson's message of 2018-08-30 14:38:00 +0300: > >>> On Thu, Aug 30, 2018 at 12:14 AM,

Re: [openstack-dev] [neutron][nova] Small bandwidth demo on the PTG

Gibi, Bence, Thanks for putting this demo together. Please count me in Regards On Thu, Aug 30, 2018 at 3:55 AM, Balázs Gibizer wrote: > Hi, > > Based on the Nova PTG planning etherpad [1] there is a need to talk about > the current state of the bandwidth work [2][3]. Bence (rubasov) has

Re: [openstack-dev] [Openstack-sigs] [all] Bringing the community together (combine the lists!)

Excerpts from Jeremy Stanley's message of 2018-08-30 17:03:50 +: > The openstack, openstack-dev, openstack-sigs and openstack-operators > mailing lists on lists.openstack.org see an increasing amount of > cross-posting and thread fragmentation as conversants attempt to > reach various corners

Re: [openstack-dev] [Openstack-operators] [ironic][tripleo][edge] Discussing ironic federation and distributed deployments

On Thu, Aug 30, 2018 at 1:21 PM Julia Kreger wrote: > Greetings everyone, > > It looks like the most agreeable time on the doodle[1] seems to be > Tuesday September 4th at 13:00 UTC. Are there any objections to using > this time? > > If not, I'll go ahead and create an etherpad, and setup a

Re: [openstack-dev] [neutron][python3] Neutron and stadium - python 3 community goal changes coming soon

On 2018-08-30 17:16, Nate Johnston wrote: On Thu, Aug 30, 2018 at 08:28:40AM -0400, Doug Hellmann wrote: Excerpts from Michel Peterson's message of 2018-08-30 14:38:00 +0300: On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston wrote: Progress is also being tracked in a wiki page [4]. [4]

Re: [openstack-dev] Inquiry about an opportunity to do a thesis project in collaboration with a OpenStack project.

Greetings! Welcome to the community! Your interests seem to span quite a bit of the OpenStack community, so I think it might be a good idea for you possibly look at the individual teams that interest you the most, and reach out to those teams and engage in discussion from there. What may be a

Re: [openstack-dev] [openstack-ansible] Stepping down from OpenStack-Ansible core

Hello Andy, Thanks a lot for your work on OpenStack-Ansible team. It was very happy to collaborate with you as different teams (me: I18n team) during Ocata and Pike release cycles, and I think I18n team now has better insight on OpenStack-Ansible thanks to the help from you and so many kind

Re: [openstack-dev] [all] Bringing the community together (combine the lists!)

On 08/30/2018 11:03 AM, Jeremy Stanley wrote: The proposal is simple: create a new openstack-discuss mailing list to cover all the above sorts of discussion and stop using the other four. Do we want to merge usage and development onto one list? That could be a busy list for someone who's

Re: [openstack-dev] [neutron][python3] Neutron and stadium - python 3 community goal changes coming soon

On Thu, Aug 30, 2018 at 08:28:40AM -0400, Doug Hellmann wrote: > Excerpts from Michel Peterson's message of 2018-08-30 14:38:00 +0300: > > On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston > > wrote: > > > > > Progress is also being tracked in a wiki page [4]. > > > > > > [4]

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from Michel Peterson's message of 2018-08-30 09:43:30 +0300: > On Thu, Aug 30, 2018 at 3:11 AM, Doug Hellmann > wrote: > > > > OK, there are somewhere just over 100 patches for all of the neutron > > > repositories, so I'm going to wait for a quieter time of day to submit > > > them to

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

Excerpts from Edison Xiang's message of 2018-08-30 14:08:12 +0800: > Hey dims, > > Thanks your reply. Your suggestion is very important. > > > what would be the impact to projects? > > what steps they would have to take? > > We can launch a project to publish OpenStack Projects APIs Schema for

[openstack-dev] [goals][python3] modifying the zuul setting import patches

A few reviewers have suggested using some YAML features that allow repeated sections to be inserted by reference, instead of copying and pasting content in different parts of the Zuul configuration. That's a great idea! However, please do that AFTER the migration is complete. For now, to make the

Re: [openstack-dev] [Openstack-sigs] [all] Bringing the community together (combine the lists!)

I also propose that we merge the interop-wg mailing list also, as the volume on that list is small but topics posted to it are of general interest to the community. Chris Hoge (Interop WG Secretary, amongst other things) > On Aug 30, 2018, at 10:03 AM, Jeremy Stanley wrote: > > The openstack,

Re: [openstack-dev] [all] Bringing the community together (combine the lists!)

Absolutely support merging. Jeremy Stanley wrote: The openstack, openstack-dev, openstack-sigs and openstack-operators mailing lists on lists.openstack.org see an increasing amount of cross-posting and thread fragmentation as conversants attempt to reach various corners of our community with

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from Michel Peterson's message of 2018-08-30 12:51:04 +0300: > On Thu, Aug 30, 2018 at 3:11 AM, Doug Hellmann > wrote: > > > | import zuul job settings from project-config | openstack/networking-odl > > | https://review.openstack.org/597870 | master| > > | switch

[openstack-dev] [openstack-ansible] Stepping down from OpenStack-Ansible core

Now that Rocky is all but ready it seems like a good time! Since changing roles I've not been able to keep up enough focus on reviews and other obligations - so I think it's time to step aside as a core reviewer. I want to say thanks to everybody in the community, I'm really proud to see the work

Re: [openstack-dev] [neutron][nova] Small bandwidth demo on the PTG

On Thu, 30 Aug 2018 12:43:06 -0500, Miguel Lavalle wrote: Gibi, Bence, In fact, I added the demo explicitly to the Neutron PTG agenda from 1:30 to 2, to give it visiblilty I'm interested in seeing the demo too. Will the demo be shown at the Neutron room or the Nova room? Historically, lunch

Re: [openstack-dev] [Openstack-operators] [all] Bringing the community together (combine the lists!)

I think the more we can reduce the ML sprawl the better. I also recall us discussing having some documentation or way of notifying net new signups of how to interact with the ML successfully. An example was having some general guidelines around tagging. Also as a maintainer for at least one of the

Re: [openstack-dev] [goals][python3][adjutant][barbican][chef][cinder][cloudkitty][i18n][infra][loci][nova][charms][rpm][puppet][qa][telemetry][trove] join the bandwagon!

On Thu, Aug 30, 2018 at 4:24 PM, Doug Hellmann wrote: > Below is the list of project teams that have not yet started migrating > their zuul configuration. If you're ready to go, please respond to this > email to let us know so we can start proposing patches. > > Doug > > | adjutant| 3

Re: [openstack-dev] [keystone] [barbican] Keystone's use of Barbican ?

Oh I was literally just thinking about the 'credential' type key value items we store in the Keystone DB. Rather than storing them in the Keystone db and worrying about encryption (and encryption keys) in Keystone around what is otherwise a plaintext secret, just offload that to a service specific

Re: [openstack-dev] [Openstack-sigs] [Openstack-operators] [all] Bringing the community together (combine the lists!)

On 2018-08-30 18:08:56 -0500 (-0500), Melvin Hillsman wrote: [...] > I also recall us discussing having some documentation or way of > notifying net new signups of how to interact with the ML > successfully. An example was having some general guidelines around > tagging. Also as a maintainer for

Re: [openstack-dev] Bumping eventlet to 0.24.1

On 18-08-23 09:50:13, Matthew Thode wrote: > This is your warning, if you have concerns please comment in > https://review.openstack.org/589382 . cross tests pass, so that's a > good sign... atm this is only for stein. > Consider yourself on notice, https://review.openstack.org/589382 is

[openstack-dev] [all][tc] Nominations now open!

Nominations for the Technical Committee positions (6 positions) are now open and will remain open until Sep 06, 2018 23:45 UTC. All nominations must be submitted as a text file to the openstack/election repository as explained on the election website[1]. Please note that the name of the file

[openstack-dev] [octavia] Proposing Carlos Goncalves (cgoncalves) as an Octavia core reviewer

Hello Octavia community, I would like to propose Carlos Goncalves as a core reviewer on the Octavia project. Carlos has provided numerous enhancements to the Octavia project, including setting up the grenade gate for Octavia upgrade testing. Over the last few releases he has also been providing

Re: [openstack-dev] [goals][python3][adjutant][barbican][chef][cinder][cloudkitty][i18n][infra][loci][nova][charms][rpm][puppet][qa][telemetry][trove] join the bandwagon!

Adjutant should be should be good to go. I don't believe there are any blockers (unless I've missed some). On 31/08/18 11:24 AM, Doug Hellmann wrote: > Below is the list of project teams that have not yet started migrating > their zuul configuration. If you're ready to go, please respond to this

Re: [openstack-dev] [keystone] [barbican] Keystone's use of Barbican ?

Actually now that I think about it, another problem is that (at least in our case) Keystone is really a cluster wide service present across regions, so if it was to use Barbican (or Vault for that matter) then the secret store service would too need to be cluster wide and across all regions. Our

Re: [openstack-dev] [octavia] Proposing Carlos Goncalves (cgoncalves) as an Octavia core reviewer

+1 Definitely a good contributor for the octavia community. 发自我的 iPhone > 在 2018年8月31日，上午11:24，Michael Johnson 写道： > > Hello Octavia community, > > I would like to propose Carlos Goncalves as a core reviewer on the > Octavia project. > > Carlos has provided numerous enhancements to the

[openstack-dev] [goals][python3][adjutant][barbican][chef][cinder][cloudkitty][i18n][infra][loci][nova][charms][rpm][puppet][qa][telemetry][trove] join the bandwagon!

Below is the list of project teams that have not yet started migrating their zuul configuration. If you're ready to go, please respond to this email to let us know so we can start proposing patches. Doug | adjutant| 3 repos | | barbican| 5 repos | | Chef OpenStack

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

Hey doug, Thanks your reply. Very good question. It is not a conflict with current API Documents work that has already been done. We can use some tools to generate Open API schema from existing machine readable API-def in every project like nova [1] We can still use the existing tools to generate

Re: [openstack-dev] [kolla][tripleo][oslo][all] Bumping eventlet to 0.24.1

On 18-08-30 20:52:46, Matthew Thode wrote: > On 18-08-23 09:50:13, Matthew Thode wrote: > > This is your warning, if you have concerns please comment in > > https://review.openstack.org/589382 . cross tests pass, so that's a > > good sign... atm this is only for stein. > > > > Consider yourself

Re: [openstack-dev] [Openstack-sigs] [all] Bringing the community together (combine the lists!)

On Thu, Aug 30, 2018 at 09:12:57PM +, Jeremy Stanley wrote: > On 2018-08-31 01:13:58 +0800 (+0800), Rico Lin wrote: > [...] > > What needs to be done for this is full topic categories support > > under `options` page so people get to filter emails properly. > [...] > > Unfortunately, topic

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

Hey dims, Thanks your reply. Your suggestion is very important. > what would be the impact to projects? > what steps they would have to take? We can launch a project to publish OpenStack Projects APIs Schema for users and developers. But now OpenStack Projects have no APIs Schema definition.

Re: [openstack-dev] [goal][python3] week 3 update

On Thu, Aug 30, 2018 at 3:11 AM, Doug Hellmann wrote: > > OK, there are somewhere just over 100 patches for all of the neutron > > repositories, so I'm going to wait for a quieter time of day to submit > > them to avoid blocking other, smaller, bits of work. > > > > Doug > > Those patches are up

[openstack-dev] [neutron] [neutron-fwaas] roadmap

Hi, The FWaaS V2 spec (https://specs.openstack.org/ openstack/neutron-specs/specs/mitaka/fwaas-api-2.0.html) describes quite some changes. Currently only some of that functionality seems to be implemented i.e. applying firewall groups on a L2/L3 port. Does a roadmap exist, describing

Re: [openstack-dev] [keystone] [barbican] Keystone's use of Barbican ?

On 30/08/18 6:29 AM, Lance Bragstad wrote: > > Is that what is being described here ?  > > https://docs.openstack.org/keystone/pike/admin/identity-credential-encryption.html > > > This is a separate mechanism for storing secrets, not necessarily > passwords (although I agree the term

Re: [openstack-dev] [goal][python3] week 3 update

On Thu, Aug 30, 2018 at 3:11 AM, Doug Hellmann wrote: > | import zuul job settings from project-config | openstack/networking-odl > | https://review.openstack.org/597870 | master| > | switch documentation job to new PTI | openstack/networking-odl > |

[openstack-dev] [heat][glance] Heat image resource support issue

Hi Glance team Glance V1 image API been deprecated for a long while, and V2 has been used widely. Heat image resource would like to change to use V2 as well, but there is an unsolved issue, which blocks us from adopting V2. Right now, to image create require Heat to download the image to Heat

Re: [openstack-dev] [keystone] [barbican] Keystone's use of Barbican ?

FWIW, instead of barbican, castellan could be used as a key manager. On 08/30/2018 12:23 PM, Adrian Turjak wrote: > > > On 30/08/18 6:29 AM, Lance Bragstad wrote: >> >> Is that what is being described here ?  >> >>

Re: [openstack-dev] [Openstack-operators] [nova][cinder][neutron] Cross-cell cold migration

On 29/08, Matt Riedemann wrote: > On 8/29/2018 3:21 PM, Tim Bell wrote: > > Sounds like a good topic for PTG/Forum? > > Yeah it's already on the PTG agenda [1][2]. I started the thread because I > wanted to get the ball rolling as early as possible, and with people that > won't attend the PTG

Re: [openstack-dev] [nova][neutron] numa aware vswitch

On Thu, 2018-08-30 at 00:15 +, Guo, Ruijing wrote: > Hi, Stephen, Sean > > It worked as expected. Good to hear. What were you missing? If there are other gaps in the documentation, I'd be happy to fix them. Stephen > Thanks, > -Ruijing > > -Original Message- > From: Stephen

[openstack-dev] [neutron][nova] Small bandwidth demo on the PTG

Hi, Based on the Nova PTG planning etherpad [1] there is a need to talk about the current state of the bandwidth work [2][3]. Bence (rubasov) has already planned to show a small demo to Neutron folks about the current state of the implementation. So Bence and I are wondering about bringing

[openstack-dev] Update global upper constraint of Kubernetes from 7.0.0 to 6.0.0

Hi All, Kubernetes upper constraint was changed lately from 6.0.0 to 7.0.0 [1]. Currently, the Openshift python client can't work with Kubernetes 7.0.0, this caused by a version pinning issue (pulled in Kubernetes 7.0.0). As a result of that, we are unable to run some of our tempest tests in

Re: [openstack-dev] [neutron] tox-siblings alternative for local testing

On Wed, Aug 29, 2018 at 9:06 AM, Takashi Yamamoto wrote: > is there any preferred solution for this? > i guess the simplest solution is to make an intermediate release of neutron > and publish it on pypi. i wonder if it's acceptable or not. > There are pre releases available in PyPI [1]. You

[openstack-dev] [L2-Gateway]

Hello, I am trying to get the l2gw feature installed on an openstack install on centos 7 using the rdo queens repo. Initially I installed the l2gw rpms form the repo: yum install openstack-neutron-l2gw-agent

Re: [openstack-dev] [neutron] tox-siblings alternative for local testing

On 8/30/18 5:49 AM, Michel Peterson wrote: > > There are pre releases available in PyPI [1]. You can use those from > your requirements like we did in n-odl [2]. > > That might be an acceptable solution. > > [1] https://pypi.org/project/neutron/#history > [2]

Re: [openstack-dev] [tripleo] quickstart for humans

On 08/30/2018 08:28 AM, Honza Pokorny wrote: > Hello! > > Over the last few months, it seems that tripleo-quickstart has evolved > into a CI tool.  It's primarily used by computers, and not humans. > tripleo-quickstart is a helpful set of ansible playbooks, and a > collection of feature sets. 

Re: [openstack-dev] [neutron][python3] Neutron and stadium - python 3 community goal changes coming soon

Excerpts from Michel Peterson's message of 2018-08-30 14:38:00 +0300: > On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston > wrote: > > > Progress is also being tracked in a wiki page [4]. > > > > [4] https://wiki.openstack.org/wiki/Python3 > > > > That wiki page should only track teams or

[openstack-dev] [Manila] no meeting today

I've had to travel unexpectedly, won't be able to chair the meeting today, and no one posted any agenda topics this week. The rocky release is imminent so we'll open up stable/rocky for backports soon. Stein specs repo is open. Please put PTG planning ideas in the etherpad [1]. PTG is less

[openstack-dev] [Freezer] Set up the Freezer team meeting

Hi Geng, Could you please help us to set up the team meeting as you're the new PTL? It supposes to be now on #openstack-meeting-alt. I sent you messages about this but haven't got anything back from you. Thanks, *Trinh Nguyen *| Founder & Chief Architect *E:*

[openstack-dev] [tripleo] quickstart for humans

Hello! Over the last few months, it seems that tripleo-quickstart has evolved into a CI tool. It's primarily used by computers, and not humans. tripleo-quickstart is a helpful set of ansible playbooks, and a collection of feature sets. However, it's become less useful for setting up development

Re: [openstack-dev] [stable][nova] Nominating melwitt for nova stable core

On Wed, Aug 29, 2018 at 4:42 AM, Tony Breeds wrote: > On Tue, Aug 28, 2018 at 03:26:02PM -0500, Matt Riedemann wrote: > > I hereby nominate Melanie Witt for nova stable core. Mel has shown that > she > > knows the stable branch policy and is also an active reviewer of nova > stable > > changes.

Re: [openstack-dev] [neutron][python3] Neutron and stadium - python 3 community goal changes coming soon

On Thu, Aug 30, 2018 at 12:14 AM, Nate Johnston wrote: > Progress is also being tracked in a wiki page [4]. > > [4] https://wiki.openstack.org/wiki/Python3 > That wiki page should only track teams or subteams should also be included there? I'm asking because it seems that some subteams appear

Re: [openstack-dev] [neutron][nova] Small bandwidth demo on the PTG

On 08/30/2018 04:55 AM, Balázs Gibizer wrote: Hi, Based on the Nova PTG planning etherpad [1] there is a need to talk about the current state of the bandwidth work [2][3]. Bence (rubasov) has already planned to show a small demo to Neutron folks about the current state of the implementation.

Re: [openstack-dev] [keystone] [barbican] Keystone's use of Barbican ?

This topic has surfaced intermittently ever since keystone implemented fernet tokens in Kilo. An initial idea was written down shortly afterwords [0], then we targeted it to Ocata [1], and removed from the backlog around the Pike timeframe [2]. The commit message of [2] includes meeting links. The