Re: [openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

Excerpts from Doug Hellmann's message of 2018-08-08 09:18:44 -0400: > Excerpts from Doug Hellmann's message of 2018-08-01 09:27:09 -0400: > > Moisés Guimarães (moguimar) did quite a bit of work on oslo.config > > during the Rocky cycle to add driver support. Based on that work, > > and a

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

This is great information, thanks Hongbin. If I'm understanding correctly, it sounds like Zun ultimately wants to be a peer of nova in terms of placement consumption. Using the resource information reported by nova, neutron, etc., you wish to be able to discover viable targets for a container

[openstack-dev] [nova][cinder] Disabling nova volume-update (aka swap volume; aka cinder live migration)

For those who aren't familiar with it, nova's volume-update (also called swap volume by nova devs) is the nova part of the implementation of cinder's live migration (also called retype). Volume-update is essentially an internal cinder<->nova api, but as that's not a thing it's also unfortunately

[openstack-dev] [docs][all] Testing installation guides for Rocky

Hi all, With the Rocky release quickly approaching, I wanted to draw your attention to installation guides testing. With each project team now maintaining their own installation guide, and with the old coordinated effort to test installation docs now retired, the Docs team recently updated

Re: [openstack-dev] New Contributor

Hello Ivoline, While I'm a little late to the party, I still wanted to say welcome and offer my help :) If you have any questions based about the links you've been sent, I'm happy to answer them! I can also help you find/get started with a team and introduce you to community members whenever

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 17/08/18 11:51, Chris Dent wrote: One of the questions that has come up on the etherpad is about how placement should be positioned, as a project, after the extraction. The options are: * A repo within the compute project * Its own project, either:   * working towards being official and

Re: [openstack-dev] [Searchlight] Reaching out to the Searchlight core members for Stein - Call for team meeting

Hi Zhenyu Zheng, Thanks for your response. What is your IRC handler? I would like to have a team meeting this week to decide what we gonna do with Searchlight in Stein. Searchlight IRC channel: #openstack-searchlight My IRC: dangtrinhnt Bests, *Trinh Nguyen *| Founder & Chief Architect

Re: [openstack-dev] [ironic] ironic-staging-drivers: what to do?

Hi, On Mon, Aug 13, 2018 at 2:40 PM, Julia Kreger wrote: > Greetings fellow ironicans! > > As many of you might know an openstack/ironic-staging-drivers[1] > repository exists. What most might not know is that it was > intentionally created outside of ironic's governance[2]. > ... > > This

[openstack-dev] Early Bird Registration Deadline Extended to 8/28 - Berlin Summit

Hi everyone, The OpenStack Summit Berlin schedule is now live and in order to give people some extra time to book tickets, we have decided to extend early bird registration. The NEW early bird registration deadline is August 28 at 11:59pm PT (August 29, 6:59

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 20/08/18 14:02, Chris Friesen wrote: In order to address the "velocity of change in placement" issues, how about making the main placement folks members of nova-core with the understanding that those powers would only be used in the new placement repo? That kind of 'understanding' is only

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 08/20/2018 11:44 AM, Zane Bitter wrote: If you want my personal opinion then I'm a big believer in incremental change. So, despite recognising that it is born of long experience of which I have been blissfully mostly unaware, I have to disagree with Chris's position that if anybody lets you

Re: [openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

o/ Em seg, 20 de ago de 2018 às 17:30, Doug Hellmann escreveu: > Excerpts from Doug Hellmann's message of 2018-08-08 09:18:44 -0400: > > Excerpts from Doug Hellmann's message of 2018-08-01 09:27:09 -0400: > > > Moisés Guimarães (moguimar) did quite a bit of work on oslo.config > > > during the

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On Sat, Aug 18, 2018 at 8:25 AM Chris Dent wrote: > > 5. In OpenStack we have a tradition of the contributors having a > strong degree of self-determination. If that tradition is to be > upheld, then it would make sense that the people who designed and > wrote the code that is being extracted

[openstack-dev] [goal][python3] week 2 update

This is week 2 of the roll-out of the "Run under Python 3 by default" goal (https://governance.openstack.org/tc/goals/stein/python3-first.html). == What we learned last week == As we worked on approving the changes to add the zuul settings to a few Oslo repositories, we had trouble with some of

Re: [openstack-dev] New Contributor

Hi Ivoline, Also a little late but wanted to say welcome aboard, hopefully you will find a very welcoming community here and of course a lot of work to do. I work with Sahara, the big data processing project of OpenStack, we need help for sure. If this area interests you in any way, feel free

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 2018-08-20 14:25:06 -0400 (-0400), Zane Bitter wrote: > On 20/08/18 14:02, Chris Friesen wrote: > > In order to address the "velocity of change in placement" > > issues, how about making the main placement folks members of > > nova-core with the understanding that those powers would only be > >

Re: [openstack-dev] [os-upstream-institute] Restarting meetings on August 20

Hello Everyone, To avoid meeting conflicts with the Women of OpenStack, we will actually be doing meetings weekly on Mondays at 20:00 UTC on odd weeks. Long story short, our kickoff meeting after this luxurious summer break will be a week from today on August 27th. Thanks everyone! See you

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

Hi Doug, I believe Sahara is ready to have those patches worked on. Do we have to do anything specific to get the env ready? Thanks, On Mon, Aug 20, 2018 at 1:13 PM Nguyễn Trí Hải wrote: > Hi, > > Vitrage team is going to finish the zuul job soon. As I see, only few > patches in the old

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On Mon, 20 Aug 2018, Zane Bitter wrote: If you want my personal opinion then I'm a big believer in incremental change. So, despite recognising that it is born of long experience of which I have been blissfully mostly unaware, I have to disagree with Chris's position that if anybody lets you

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

Hi, Vitrage team is going to finish the zuul job soon. As I see, only few patches in the old branches need to be merged. For the other projects, some patches have problems with different errors. Please help to fix them. Thanks for your cooperation. Nguyen Hai On Tue, Aug 21, 2018, 12:27 AM

Re: [openstack-dev] [tripleo] fedora28 python3 test environment

On Fri, Aug 17, 2018 at 5:18 PM, Alex Schultz wrote: > Ahoy folks, > > In order to get to a spot where can start evaluate the current status > of TripleO under python3 I've thrown together a set of ansible > playbooks[0] to launch a fedora28 node and build the required > python-tripleoclient (and

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

As we start looking at how TripleO will address next generation deployment needs such as Edge, multi-site, and multi-cloud, I'd like to kick off a discussion around how TripleO can evolve and adapt to meet these new challenges. What are these challenges? I think the OpenStack Edge Whitepaper does

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/17/2018 12:47 PM, Ed Leafe wrote: I’d like this to be a technical discussion, with as little political overtones as possible. Everyone agrees that technically placement should be in its own repo. The entire debate is political and regards people and who will be making decisions in the

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 18/08/18 18:22, Eric Fried wrote: A year ago we might have developed a feature where one patch would straddle placement and nova. Six months ago we were developing features where those patches were separate but in the same series. Today that's becoming less and less the case: nrp, sharing

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

Excerpts from Doug Hellmann's message of 2018-08-20 16:34:22 -0400: > Excerpts from Telles Nobrega's message of 2018-08-20 15:07:29 -0300: > > Hi Doug, > > > > I believe Sahara is ready to have those patches worked on. > > > > Do we have to do anything specific to get the env ready? > > Just be

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/17/2018 11:56 AM, melanie witt wrote: We've seen exciting progress in finally solving a lot of these issues as we've been developing placement. But, there is still a significant amount of important work to do in Nova that depends on placement. For example, we need to integrate nested

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On Mon, Aug 20, 2018 at 3:15 PM Eric Fried wrote: > This is great information, thanks Hongbin. > > If I'm understanding correctly, it sounds like Zun ultimately wants to > be a peer of nova in terms of placement consumption. Using the resource > information reported by nova, neutron, etc., you

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/17/2018 10:59 AM, Ed Leafe wrote: I would like to hear from the Cinder and Neutron teams, especially those who were around when those compute sub-projects were split off into their own projects. Did you feel that being independent of compute helped or hindered you? And to those who are

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/18/2018 7:25 AM, Chris Dent wrote: 5. In OpenStack we have a tradition of the contributors having a strong degree of self-determination. If that tradition is to be upheld, then it would make sense that the people who designed and wrote the code that is being extracted would get to choose

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/17/2018 11:09 AM, Sean McGinnis wrote: This reluctance on having it part of Nova may be real or just perceived, but with it within Nova it will likely be an uphill battle for some time convincing other projects that it is a nicely separated common service that they can use. Cyborg, Ironic

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On Aug 20, 2018, at 5:31 PM, Matt Riedemann wrote: > >> I would like to hear from the Cinder and Neutron teams, especially those who >> were around when those compute sub-projects were split off into their own >> projects. Did you feel that being independent of compute helped or hindered >>

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/20/2018 5:40 PM, Ed Leafe wrote: That detail aside, the question is still valid: did the split from working within the Nova project to working as an independent project have positive or negative effects? Or both? I'm sure the answer has got to be "both", right? Neutron integration with

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On Aug 20, 2018, at 6:27 PM, Matt Riedemann wrote: > > 3. The biggest fear is on the people involved in what placement on its own > might be, because the current placement team is made of, for the most part, > highly opinionated people that spend a lot of time arguing because they have, > at

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/20/2018 1:32 PM, Hongbin Lu wrote: * Is placement stable enough so that it won't break us often? Yes, we use microversions for this reason. * If there is a breaking change in placement and we contribute a fix, how fast the fix will be merged? Eric hedged on this, but I think the

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

Excerpts from Telles Nobrega's message of 2018-08-20 15:07:29 -0300: > Hi Doug, > > I believe Sahara is ready to have those patches worked on. > > Do we have to do anything specific to get the env ready? Just be ready to do the reviews. I am generating the patches now and will propose them in a

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/17/2018 2:21 PM, Tom Barron wrote: I think that even standalone if I'm running a scheduler (i.e., not doing emberlib version of standalone) then I'm likely to want to run them active-active on multiple nodes and will need a solution for the current races.  So even standalone we face the

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/17/2018 12:30 PM, Dan Smith wrote: I know politics will be involved in this, but this is a really terrible reason to do a thing, IMHO. After the most recent meeting we had with the Cinder people on placement adoption, I'm about as convinced as ever that Cinder won't (and won't need

Re: [openstack-dev] [os-upstream-institute] Restarting meetings on August 20

On Mon, Aug 20, 2018 at 10:23:07AM -0700, Kendall Nelson wrote: > Hello Everyone, > > To avoid meeting conflicts with the Women of OpenStack, we will actually be > doing meetings weekly on Mondays at 20:00 UTC on odd weeks. > > Long story short, our kickoff meeting after this luxurious summer

[openstack-dev] [all] [nova] [neutron] live migration with multiple port bindings.

HI everyone, last week i spent some time testing the live migration capabilities now that nova has started to use neutron multiple port bindings. all testing unless otherwise specifed was done with Rocky RC1 or later commits on Centos 7.5 using devstack. test summary ~~ i have tested

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/20/2018 6:42 PM, Ed Leafe wrote: It was said in the #openstack-tc discussions, but for those on the mailing list, the biggest concern among the Nova core developers is that the consensus among Placement cores will certainly not align with the needs of Nova. I personally think that's

[openstack-dev] [senlin] Senlin Weekly Meeting Time Change

Hi, As we are starting the Stein cycle, I would like to start having weekly meetings again for Senlin. I'm proposing to move the weekly meeting to the following time: Friday 5:30 UTC to 6:30 UTC in #senlin channel Please reply if this works for you or reply with an alternative time slot.

[openstack-dev] [all] PyCharm Licences

I have renewed the Pycharm licenses for community till Aug 13, 2019. Everyone who is using it should have it updated automatically. Please do not request again for renewal. At the same time, I would request not to request multiple licenses with multiple email addresses. -- Best Regards, Swapnil

[openstack-dev] 答复: [senlin] Senlin Weekly Meeting Time Change

ok 原始邮件 发件人：DucTruong 收件人：openstack-dev@lists.openstack.org 日 期 ：2018年08月21日 12:36 主 题 ：[openstack-dev] [senlin] Senlin Weekly Meeting Time Change Hi, As we are starting the Stein cycle, I would like to start having weekly meetings again for Senlin. I'm proposing

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 8/20/2018 8:08 PM, Matt Riedemann wrote: On 8/20/2018 6:42 PM, Ed Leafe wrote: It was said in the #openstack-tc discussions, but for those on the mailing list, the biggest concern among the Nova core developers is that the consensus among Placement cores will certainly not align with the

Re: [openstack-dev] [kolla][project navigator] kolla missing in project navigator

Hi, effectively kolla-ansible is the deployment tool for container images, and kolla the image artifact builder used by other deployment projects as consumable. In the project navigator wasn't kolla nor kolla-ansible, my bad for not expecifying kolla-ansible as deployment deliverable. Regards

Re: [openstack-dev] ?==?utf-8?q? [kolla][project?==?utf-8?q? navigator] kolla missing in project navigator

On Monday, August 20, 2018 15:57 CEST, Jimmy McArthur wrote: > Eduardo, > > Thanks for the heads up. We're in the process of updating the Project > Navigator to match the OpenStack Map [1]. It looks like Kolla got lost > in the shuffle. I've added it back to the Project [2Navigator

Re: [openstack-dev] ?= [kolla][project=?utf-8?q? navigator] kolla missing in project navigator

jean-phili...@evrard.me wrote: That second link is very confusing, on the openstack-ansible case. Yes we ship recipes (roles, playbooks) for deployment using Ansible (any other ansible project could use them, maybe we need to adapt there if it's not the case...), but we also deal with the

Re: [openstack-dev] [kolla][project navigator] kolla missing in project navigator

Eduardo Gonzalez wrote: Hi, effectively kolla-ansible is the deployment tool for container images, and kolla the image artifact builder used by other deployment projects as consumable. In the project navigator wasn't kolla nor kolla-ansible, my bad for not expecifying kolla-ansible as

Re: [openstack-dev] [kolla][project navigator] kolla missing in project navigator

Yes, that was my intention. Didn't meant to say kolla as images, i meant kolla-ansible. On Mon, Aug 20, 2018, 4:59 PM Thierry Carrez wrote: > Eduardo Gonzalez wrote: > > Hi, effectively kolla-ansible is the deployment tool for container > > images, and kolla the image artifact builder used by

[openstack-dev] [neutron] Bug deputy report week Aug 12th - Aug 19th

Dear Neutron Team, I was the bugs deputy for the week of Aug 12th - Aug 19th. Here's the summary of the bugs that were filed: Something what needs attention to clarify: https://bugs.launchpad.net/neutron/+bug/1787385 - vpnaas and dynamic-routing missing neutron-tempest-plugin in

[openstack-dev] [kuryr] No meeting today

Hi folks, since a couple of our core reviewers are on PTO today we have decided not to host a meeting today. If you have any questions just ping us at #openstack-kuryr Best! Daniel __ OpenStack Development Mailing List

Re: [openstack-dev] [Openstack-operators] [puppet] migrating to storyboard

Hello Kendall, I think you can just leave them in the group then, at your convenience. If they are there we can start using them if so. Best regards Tobias On 08/17/2018 11:08 PM, Kendall Nelson wrote: On Fri, Aug 17, 2018 at 12:15 AM Tobias Urdin > wrote:

Re: [openstack-dev] New Contributor

Thanks so much for help Josh and Thierry. I'll check out the links and hopefully find a way forward from there. Will get back here in case I have any questions. Cheers, Ivoline On Mon, Aug 20, 2018, 12:01 Thierry Carrez wrote: > Ivoline Ngong wrote: > > I am Ivoline Ngong. I am a Cameroonian

Re: [openstack-dev] [neutron][neutron-classifier] info on common classifier

Hi Hemanth The API is just waiting for its last review and will hopefully merge after that. https://review.openstack.org/#/c/487182/25 We wanted to ensure that the project was thoroughly tested and setting up the project to run these tests took some time. The patch to follow this one is an

Re: [openstack-dev] [neutron] neutron ipv6 radvd sends out link-local or nothing as def gw (L3 HA issue?)

Ok, so the issue here seems to be that I have a L3 HA router with SLAAC, both the active and standby router will configure the SLAAC obtained address causing a conflict since both side share the same MAC address. Is there any workaround for this? Should SLAAC even be enabled for interfaces on

[openstack-dev] [neutron][neutron-classifier] info on common classifier

Hi I am looking for information on Neutron Common Classifier. What is the implementation done today (Is API extension implemented?) and further plans for the same. I could not get much information except for the specification and github

Re: [openstack-dev] [neutron] neutron ipv6 radvd sends out link-local or nothing as def gw (L3 HA issue?)

Continuing forward, these patches should've fixed that https://review.openstack.org/#/q/topic:bug/1667756+(status:open+OR+status:merged) I'm on Queens. The two inside interfaces on the backup router: [root@controller2 ~]# ip netns exec qrouter-0775785e-a93a-4501-917b-be92ff03f36a cat

Re: [openstack-dev] [neutron] neutron ipv6 radvd sends out link-local or nothing as def gw (L3 HA issue?)

When I removed those ips and set accept_ra to 0 on the backup router: ip netns exec qrouter-0775785e-a93a-4501-917b-be92ff03f36a sysctl -w net.ipv6.conf.qr-7fad6b1b-c9.accept_ra=0 ip netns exec qrouter-0775785e-a93a-4501-917b-be92ff03f36a sysctl -w net.ipv6.conf.qr-5be04815-68.accept_ra=0 ip

Re: [openstack-dev] New Contributor

Ivoline Ngong wrote: I am Ivoline Ngong. I am a Cameroonian who lives in Turkey. I will love to contribute to Open source through OpenStack. I code in Java and Python and I think OpenStack is a good fit for me. I'll appreciate it if you can point me to the right direction on how I can get

[openstack-dev] neutron ipv6 radvd sends out link-local or nothing as def gw (L3 HA issue?)

Hello, Note: before reading, this router was a regular router but was then disable, changed ha=true so it's now a L3 HA router, then it was enabled again. CC openstack-dev for help or feedback if it's a possible bug. I've been testing around with IPv6 and overall the experience has been

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

Chris Dent wrote: [...] So my hope is that (in no particular order) Jay Pipes, Eric Fried, Takashi Natsume, Tetsuro Nakamura, Matt Riedemann, Andrey Volkov, Alex Xu, Balazs Gibizer, Ed Leafe, and any other contributor to placement whom I'm forgetting [1] would express their preference on what

[openstack-dev] [all] [tc] Who is responsible for the mission and scope of OpenStack?

TC-members and everyone else, In the discussion on a draft technical vision for OpenStack at https://review.openstack.org/#/c/592205/ there is a question about whether the TC is "responsible for the mission and scope of OpenStack". As the discussion there indicates, there is plenty of

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

So my hope is that (in no particular order) Jay Pipes, Eric Fried, Takashi Natsume, Tetsuro Nakamura, Matt Riedemann, Andrey Volkov, Alex Xu, Balazs Gibizer, Ed Leafe, and any other contributor to placement whom I'm forgetting [1] would express their preference on what they'd like to see happen.

Re: [openstack-dev] [all] [tc] Who is responsible for the mission and scope of OpenStack?

Chris Dent wrote: In the discussion on a draft technical vision for OpenStack at     https://review.openstack.org/#/c/592205/ there is a question about whether the TC is "responsible for the mission and scope of OpenStack". As the discussion there indicates, there is plenty of nuance, but

[openstack-dev] [neutron] neutron ipv6 radvd sends out link-local or nothing as def gw (L3 HA issue?)

Forgot [neutron] tag. On 08/20/2018 11:36 AM, Tobias Urdin wrote: Hello, Note: before reading, this router was a regular router but was then disable, changed ha=true so it's now a L3 HA router, then it was enabled again. CC openstack-dev for help or feedback if it's a possible bug. I've

[openstack-dev] [ptg] Register now ! Price increases Wednesday

Hi everyone, If you haven't registered for the PTG in Denver yet, I'd recommend you do it today or tomorrow as the price will switch to last-minute pricing at the end of day on August 22 ! https://www.openstack.org/ptg Protip: There might still be a couple of rooms available in the PTG

Re: [openstack-dev] [neutron] neutron ipv6 radvd sends out link-local or nothing as def gw (L3 HA issue?)

On Mon, Aug 20, 2018 at 6:06 AM, Tobias Urdin wrote: > When I removed those ips and set accept_ra to 0 on the backup router: > > ip netns exec qrouter-0775785e-a93a-4501-917b-be92ff03f36a sysctl -w > net.ipv6.conf.qr-7fad6b1b-c9.accept_ra=0 > ip netns exec

Re: [openstack-dev] [oslo] proposing Moisés Guimarães for oslo.config core

On Mon, 2018-08-13 at 17:39 -0500, Ben Nemec wrote: > > On 08/08/2018 08:18 AM, Doug Hellmann wrote: > > Excerpts from Doug Hellmann's message of 2018-08-01 09:27:09 -0400: > > > Moisés Guimarães (moguimar) did quite a bit of work on oslo.config > > > during the Rocky cycle to add driver support.

[openstack-dev] [kolla][project navigator] kolla missing in project navigator

Hi, while checking around the project navigator, I don't see kolla in the deployment tools section. How could we get kolla appear in the navigator along other deployment tools? Regards __ OpenStack Development Mailing List

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

On 08/18/2018 08:25 AM, Chris Dent wrote: So my hope is that (in no particular order) Jay Pipes, Eric Fried, Takashi Natsume, Tetsuro Nakamura, Matt Riedemann, Andrey Volkov, Alex Xu, Balazs Gibizer, Ed Leafe, and any other contributor to placement whom I'm forgetting [1] would express their

Re: [openstack-dev] [astara] Retirement of astara repos?

Yeah. I’ll post the retirement commits this week. mark > On Aug 18, 2018, at 13:39, Andreas Jaeger wrote: > > Mark, shall I start the retirement of astara now? I would appreciate a "go > ahead" - unless you want to do it yourself... > > Andreas > >> On 2018-02-23 14:34, Andreas Jaeger

Re: [openstack-dev] [all] [tc] Who is responsible for the mission and scope of OpenStack?

Excerpts from Thierry Carrez's message of 2018-08-20 11:33:30 +0200: > Chris Dent wrote: > > In the discussion on a draft technical vision for OpenStack at > > > >     https://review.openstack.org/#/c/592205/ > > > > there is a question about whether the TC is "responsible for the > > mission

Re: [openstack-dev] [kolla][project navigator] kolla missing in project navigator

Eduardo, "Kolla" was originally left out of the map (and therefore the new OpenStack components page) because the map only shows deliverables that are directly usable by deployers. That is why "Kolla-Ansible" is listed there and not "Kolla". Are you making the case that Kolla should be used

Re: [openstack-dev] [kolla][project navigator] kolla missing in project navigator

Eduardo, Thanks for the heads up. We're in the process of updating the Project Navigator to match the OpenStack Map [1]. It looks like Kolla got lost in the shuffle. I've added it back to the Project [2Navigator under the Deployment Tools section [2]. Please let me know if I can assist

Re: [openstack-dev] [kolla][project navigator] kolla missing in project navigator

Hi Jimmy, thanks for the the quick update. I see it in the navigator now. Thanks On Mon, Aug 20, 2018, 3:57 PM Jimmy McArthur wrote: > Eduardo, > > Thanks for the heads up. We're in the process of updating the Project > Navigator to match the OpenStack Map [1]. It looks like Kolla got lost >

Re: [openstack-dev] [all] [nova] [placement] placement below or beside compute after extraction?

>> So my hope is that (in no particular order) Jay Pipes, Eric Fried, >> Takashi Natsume, Tetsuro Nakamura, Matt Riedemann, Andrey Volkov, >> Alex Xu, Balazs Gibizer, Ed Leafe, and any other contributor to >> placement whom I'm forgetting [1] would express their preference on >> what they'd like