[openstack-dev] [nova] Notification subteem meeting is cancelled this week

Hi, There won't be subteam meeting this week. Cheers, gibi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [TC][Searchlight] Setting up milestones for Searchlight on Launchpad

Hi Thierry, I just saw that link. Thanks :) Because I couldn't contact any of the core members I emailed this list. I will update the searchlight-core as planned after I am added. Thanks for your response, *Trinh Nguyen *| Founder & Chief Architect *E:*

Re: [openstack-dev] [TC][Searchlight] Setting up milestones for Searchlight on Launchpad

Trinh Nguyen wrote: In an effort to get Searchlight back on track, I would like to set up milestones as well as clean up the incomplete bugs, blueprints etc. on Launchpad [1] I was added to the Searchlight Drivers team but I still can not touch the milestone configuration. As a member of the

Re: [openstack-dev] New Contributor

Hello Kendall and Telles, Thanks so much for warm welcome. I feel at home already.The links sent were quire helpful and gave me an insight into what OpenStack is all about.After reading lightly about the different projects, the Sahara project caught my attention. Probably because I am interested

[openstack-dev] [mistral] No Denver PTG Sessions

Hi all, Unfortunately due to some personal conflicts and trouble with travel plans, there will be no Mistral cores at the Denver PTG. This means that we have had to cancel the Mistral sessions. I recently asked if anyone was planning to attend and only got one maybe. I am considering trying to

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

Works for me. -Qiming On Mon, Aug 20, 2018 at 09:34:46PM -0700, Duc Truong wrote: > 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

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

On Mon, 20 Aug 2018, Matt Riedemann wrote: Here is an example of the concern. In Sydney we talked about adding types to the consumers resource in placement so that nova could use placement for counting quotas [1]. Chris considered it a weird hack but it's pretty straight-forward from a nova

[openstack-dev] [TC][Searchlight] Setting up milestones for Searchlight on Launchpad

Dear TC and Searchlight team, In an effort to get Searchlight back on track, I would like to set up milestones as well as clean up the incomplete bugs, blueprints etc. on Launchpad [1] I was added to the Searchlight Drivers team but I still can not touch the milestone configuration. In addition,

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

Hi, There was a two days workshop on edge requirements back in Dublin. The notes are stored here: https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG I think there are some areas there what can be interesting for the squad. Edge Computing Group plans to have a day long

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

+1, works for me. > On Aug 21, 2018, at 12:34 PM, Duc Truong wrote: > > 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

Re: [openstack-dev] New Contributor

That is great to hear. Plese join us at #openstack-sahara so we can discuss a little more of what work you want to do. Welcome aboard. On Tue, Aug 21, 2018 at 5:22 AM Ivoline Ngong wrote: > Hello Kendall and Telles, > > Thanks so much for warm welcome. I feel at home already. > The links sent

Re: [openstack-dev] [mistral] No Denver PTG Sessions

On 08/21/2018 10:22 AM, Dougal Matthews wrote: Hi all, Unfortunately due to some personal conflicts and trouble with travel plans, there will be no Mistral cores at the Denver PTG. This means that we have had to cancel the Mistral sessions. I recently asked if anyone was planning to attend

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

Thanks. We merged most of them, there is only one that failed the tests so I'm rechecking it. On Mon, Aug 20, 2018 at 5:43 PM Doug Hellmann wrote: > 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: > > >

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

On 8/21/2018 4:28 AM, Chris Dent wrote: Since we're airing things out (which I think is a good thing, at least in the long run), I'll add to this. I think that's a pretty good example of where I did express some resistance, especially since were it to come up again, I still would express some

[openstack-dev] nova 18.0.0.0rc2 (rocky)

Hello everyone, A new release candidate for nova for the end of the Rocky cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/nova/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

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

On 8/20/2018 3:18 PM, Sean Mooney wrote: in both the ovs-dpdk tests, when the migration failed and the vm contiuned to run on the source node however it had no network connectivity. on hard reboot of the vm, it went to error state because the vif binding was set to none as the

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

Matt Riedemann wrote: [...] Regarding microversions I was mostly thinking of the various times I've been asked in the placement channel if something warrants a microversion or if we can just bug fix it in, like microversion 1.26. I then generally feel like I need to be defensive when I say,

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

On 20-08-18 16:29:52, Matthew Booth wrote: > 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,

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

On Tue, Aug 21, 2018 at 2:40 AM Csatari, Gergely (Nokia - HU/Budapest) wrote: > > Hi, > > There was a two days workshop on edge requirements back in Dublin. The notes > are stored here: > https://wiki.openstack.org/wiki/OpenStack_Edge_Discussions_Dublin_PTG I think > there are some areas there

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

On 8/21/2018 7:28 AM, Matt Riedemann wrote: On 8/20/2018 3:18 PM, Sean Mooney wrote: in both the ovs-dpdk tests, when the migration failed and the vm contiuned to run on the source node however it had no network connectivity. on hard reboot of the vm, it went to error state because the vif

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

If I would be a standalone consummer of OpenStack Placement (e.g. I only run cinder or ironic to manage volume / baremetal), and I had to run something like: $ pip install -U placement I would prefer "placement" to be a project driven by diverse people interested by Infrastructure resources

Re: [openstack-dev] [mistral] No Denver PTG Sessions

It’s disappointing that we can’t make it this time. Really bad coincidence of different issues.. I’d love to have a virtual PTG and Dmitry’s notes look very helpful to me. Thanks Renat Akhmerov @Nokia On 21 Aug 2018, 17:15 +0700, Dmitry Tantsur , wrote: > On 08/21/2018 10:22 AM, Dougal

[openstack-dev] Stepping down from Ironic core

Good morning Ironic, I have come to realize that I don't have the time needed to be able to devote the attention needed to continue as an Ironic core. I'm hopeful that in the future I will work on Ironic or OpenStack again! :) The Ironic (and OpenStack) community has been a great one and I have

[openstack-dev] [goal][python3] dealing with new jobs failing on old branches

Goal champions, Most of the jobs in the project-templates do not have branch specifiers. That allows us to add a job to a repository and then not realize that it doesn't work on an old branch. We're finding some of those with this zuul migration (for example,

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

This is sad news to read, but completely understandable! Thank you for all of your excellent work on Ironic, and should time and focus ever make sense later down the road for you to rejoin ironic-core, know you'll be welcomed back. Thanks again! -Julia On Tue, Aug 21, 2018 at 8:38 AM, John

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

On Tue, Aug 21, 2018 at 11:00 AM, Julia Kreger wrote: > This is sad news to read, but completely understandable! > > Thank you for all of your excellent work on Ironic, and should time > and focus ever make sense later down the road for you to rejoin > ironic-core, know you'll be welcomed back.

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

So, nova's worried about having to be in the boat many of us have been in where they depend on another project not recognizing their important use cases? heh... ok, so, yeah. that is a legitimate concern. You need someone like the TC to be able to step in, in those cases to help sort that kind

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

On 2018-08-21 16:38:41 + (+), Fox, Kevin M wrote: [...] > You need someone like the TC to be able to step in, in those cases > to help sort that kind of issue out. In the past, the TC was not > willing to do so. My gut feeling though is that is finally > changing. [...] To be clear, it's

[openstack-dev] [Tacker] Proposing changes in Tacker Core Team

Hi Tacker members, To keep our Tacker project growing with new active members, I would like to propose to prune +2 ability of our farmer member Kanagaraj Manickam, and propose Cong Phuoc Hoang (IRC: phuoc) to join the tacker core team. Kanagaraj is not been involved since last couple of cycle.

Re: [openstack-dev] [Tacker] Proposing changes in Tacker Core Team

+1 On Wed, Aug 22, 2018, 1:21 PM Dharmendra Kushwaha < dharmendra.kushw...@india.nec.com> wrote: > Hi Tacker members, > > > > To keep our Tacker project growing with new active members, I would like > > to propose to prune +2 ability of our farmer member Kanagaraj Manickam, > > and propose Cong

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

There have been plenty of cross project goals set forth from the TC and implemented by the various projects such as wsgi or python3. Those have been worked on by each of the projects in priority to some project specific goals by devs interested in bettering OpenStack. Why is it so hard to

[openstack-dev] [magnum] K8s Conformance Testing

As discussed at the Vancouver SIG-K8s and Copenhagen SIG-OpenStack sessions, we're moving forward with obtaining Kubernetes Conformance certification for Magnum. While conformance test jobs aren't reliably running in the gate yet, the requirements of the program make sumbitting results manually on

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

The stuff you are pushing back against are the very same things that other folks are trying to do at a higher level. You want control so you can prioritize the things you feel your users are most interested in. Folks in other projects have decided the same. Really, where should the priorities

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

On 2018-08-21 22:42:45 + (+), Fox, Kevin M wrote: [...] > Yes, I realize shared storage was Cinders priority and Nova's now > way behind in implementing it. so it is kind of a priority to get > it done. Just using it as an example though in the bigger context. > > Having operators

Re: [openstack-dev] [TC][Searchlight] Setting up milestones for Searchlight on Launchpad

Hi Kendall, Thanks for offering the help. Sure, please do that. Let me know if you need anything. Bests, *Trinh Nguyen *| Founder & Chief Architect *E:* dangtrin...@gmail.com | *W:* *www.edlab.xyz * On Wed, Aug 22, 2018 at 3:16 AM Kendall

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

Thanks Matt. *Trinh Nguyen *| Founder & Chief Architect *E:* dangtrin...@gmail.com | *W:* *www.edlab.xyz * On Tue, Aug 21, 2018 at 10:53 PM Matt Riedemann wrote: > On 8/20/2018 10:10 AM, Trinh Nguyen wrote: > > > > Thanks for your response.

Re: [openstack-dev] [release][qa] QA Rocky release status

Hi All, Here is updated status on QA projects releases. only Devstack and Grenade left which are waiting for swift release - https://review.openstack.org/#/c/594537/ IN-PROGRESS: 1. devstack: Branch. Patch is pushed to branch for Rocky which is in hold state - IN-PROGRESS [1] 2. grenade:

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

> The reshaper code > is still going through code review, then next we have the integration to > do. To clarify: we're doing the integration in concert with the API side. Right now the API side patches [1][2] are in series underneath the nova side [3]. In a placement-in-its-own-repo world, the

[openstack-dev] [congress] meeting cancelled 8/24

Hi all, I¹m not going to be able to make the meeting this week. Let¹s resume next week =) I'm still available by email. Cheers! __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Tacker] Proposing changes in Tacker Core Team

+1 *Sent with Shift * 2018-08-22 13:23 GMT+09:00 Nguyễn Trí Hải : > +1 > > On Wed, Aug 22, 2018, 1:21 PM Dharmendra Kushwaha < >

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

On 08/21/2018 04:33 PM, melanie witt wrote: If we separate into two different groups, all of the items I discussed in my previous reply will become cross-project efforts. To me, this means that the placement group will have their own priorities and goal setting process and if their priorities

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

On Tue, 21 Aug 2018 14:55:26 -0600, Chris Friesen wrote: On 08/21/2018 01:53 PM, melanie witt wrote: Given all of that, I'm not seeing how *now* is a good time to separate the placement project under separate governance with separate goals and priorities. If operators need things for compute,

Re: [openstack-dev] [magnum] K8s Conformance Testing

Hi Chris, This is an awesome effort. We can provide nested virt resources which are leveraged by Kata at the moment. Thanks! Mohammed Sent from my iPhone > On Aug 21, 2018, at 6:38 PM, Chris Hoge wrote: > > As discussed at the Vancouver SIG-K8s and Copenhagen SIG-OpenStack sessions, >

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

On Tue, 21 Aug 2018 17:36:18 -0500, Eric Fried wrote: Affinity modeling and shared storage support are compute features OpenStack operators and users need. Operators need affinity modeling in the placement is needed to achieve parity for affinity scheduling with multiple cells. That means,

Re: [openstack-dev] [Tacker] Proposing changes in Tacker Core Team

+1 -- 龚永生 九州云信息科技有限公司 99CLOUD Co. Ltd. 邮箱（Email）：gong.yongsh...@99cloud.net 地址：北京市海淀区上地三街嘉华大厦B座806 Addr : Room 806, Tower B, Jiahua Building, No. 9 Shangdi 3rd Street, Haidian District, Beijing, China 手机（Mobile)：+86-18618199879 公司网址（WebSite）：http://99cloud.net 在 2018-08-22

Re: [openstack-dev] [goal][python3] dealing with new jobs failing on old branches

Hi, I figured out that we also can submit a patch to fix failure job in the old branches, particularly, the docs job. However, I still struggle with the failure of py27 or py35 jobs. On Tue, Aug 21, 2018 at 11:17 PM Doug Hellmann wrote: > Goal champions, > > Most of the jobs in the

Re: [openstack-dev] [goals][python3] please check with me before submitting any zuul migration patches

Please add yourself to storyboard to everyone know who is working on the project. https://storyboard.openstack.org/#!/story/2002586 On Wed, Aug 22, 2018 at 3:31 AM Doug Hellmann wrote: > We have a few folks eager to join in and contribute to the python3 goal > by helping with the patches to

Re: [openstack-dev] [Freezer] Reactivate the team

If you also wanted to add migrating from Launchpad to Storyboard to this list I am happy to help do the test migration and coordinate the real migration. -Kendall (diablo_rojo) On Fri, Aug 17, 2018 at 6:50 PM Trinh Nguyen wrote: > Dear Freezer team, > > Since we have appointed a new PTL for

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

Excerpts from melanie witt's message of 2018-08-21 12:53:43 -0700: > On Tue, 21 Aug 2018 06:50:56 -0500, Matt Riedemann wrote: > > At this point, I think we're at: > > > > 1. Should placement be extracted into it's own git repo in Stein while > > nova still has known major issues which will have

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

On 08/21/2018 01:53 PM, melanie witt wrote: Given all of that, I'm not seeing how *now* is a good time to separate the placement project under separate governance with separate goals and priorities. If operators need things for compute, that are well-known and that placement was created to

[openstack-dev] neutron-lbaas-dashboard 5.0.0.0rc2 (rocky)

Hello everyone, A new release candidate for neutron-lbaas-dashboard for the end of the Rocky cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron-lbaas-dashboard/ Unless release-critical issues are found that warrant a release candidate

[openstack-dev] octavia-dashboard 2.0.0.0rc2 (rocky)

Hello everyone, A new release candidate for octavia-dashboard for the end of the Rocky cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/octavia-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this

[openstack-dev] UC Elections will not be held

As there were only 2 nominations for the 2 open seats, elections will not be needed. Congratulations to Matt Van Winkle and Joseph Sandoval! -- Ed Leafe __ OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [goals][python3] please check with me before submitting any zuul migration patches

We have a few folks eager to join in and contribute to the python3 goal by helping with the patches to migrate zuul settings. That's great! However, many of the patches being proposed are incorrect, which means there is either something wrong with the tool or the way it is used. The intent was to

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

On Tue, 21 Aug 2018 10:28:26 +0100 (BST), Chris Dent wrote: On Mon, 20 Aug 2018, Matt Riedemann wrote: Here is an example of the concern. In Sydney we talked about adding types to the consumers resource in placement so that nova could use placement for counting quotas [1]. Chris considered it

Re: [openstack-dev] New Contributor

Ivoline, If you need help getting on IRC[1] or setup with any of the other tools we use, please let me know! [1] https://docs.openstack.org/contributors/common/irc.html -Kendall Nelson On Tue, Aug 21, 2018 at 4:44 AM Telles Nobrega wrote: > That is great to hear. Plese join us at

Re: [openstack-dev] [barbican][oslo][release][requirements] FFE request for castellan

Because castellan is in global-requirements, we need an FFE from requirements too. Can someone from the requirements team respond to the review? Thanks. On 08/16/2018 04:34 PM, Ben Nemec wrote: The backport has merged and I've proposed the release here: https://review.openstack.org/592746

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

On Tue, 21 Aug 2018 06:50:56 -0500, Matt Riedemann wrote: At this point, I think we're at: 1. Should placement be extracted into it's own git repo in Stein while nova still has known major issues which will have dependencies on placement changes, mainly modeling affinity? 2. If we extract,

Re: [openstack-dev] New Contributor

Thanks KendallWith the link you sent, I succesfully joined IRC On Tue, Aug 21, 2018 9:10 PM, Kendall Nelson kennelso...@gmail.com wrote: Ivoline, If you need help getting on IRC[1] or setup with any of the other tools we use, please let me know!

Re: [openstack-dev] [TC][Searchlight] Setting up milestones for Searchlight on Launchpad

Hello Trinh, Since Searchlight is in flux right now, it might be an appropriate time to consider migrating to StoryBoard from Launchpad. Since you are working on getting organized and figuring out the state of Seachlight, it might make more sense to do that in the new tool, rather than doing it

[openstack-dev] octavia 3.0.0.0rc2 (rocky)

Hello everyone, A new release candidate for octavia for the end of the Rocky cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/octavia/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

Re: [openstack-dev] [User-committee] UC Elections will not be held

Congratulations Matt and Joseph! Our community is in good hands with your leadership, looking forward to seeing you in Berlin. Do not hesitate to ask for help at any time. Edgar On 8/21/18, 12:45 PM, "Ed Leafe" wrote: As there were only 2 nominations for the 2 open seats, elections will

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

On Tue, 21 Aug 2018 16:41:11 -0400, Doug Hellmann wrote: Excerpts from melanie witt's message of 2018-08-21 12:53:43 -0700: On Tue, 21 Aug 2018 06:50:56 -0500, Matt Riedemann wrote: At this point, I think we're at: 1. Should placement be extracted into it's own git repo in Stein while nova

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

On 2018-08-21 17:18:40 + (+), Fox, Kevin M wrote: [...] > I'm really sure at this point that you can't have a project as > large as OpenStack without leadership setting a course and > sometimes making hard choices for the betterment of the whole. > That doesn't mean a benevolent dictator.

Re: [openstack-dev] [barbican][oslo][release][requirements] FFE request for castellan

On 18-08-21 14:00:41, Ben Nemec wrote: > Because castellan is in global-requirements, we need an FFE from > requirements too. Can someone from the requirements team respond to the > review? Thanks. > > On 08/16/2018 04:34 PM, Ben Nemec wrote: > > The backport has merged and I've proposed the

Re: [openstack-dev] [Openstack-sigs] UC Elections will not be held

Congrats to VW and Joseph. Thank you to Saverio for his hard work. And lastly thank you to Ed, Chandan, and Mohamed for serving as our election officials! Amy (spotz) User Committee On Tue, Aug 21, 2018 at 2:44 PM, Ed Leafe wrote: > As there were only 2 nominations for the 2 open seats,

[openstack-dev] [nova][neutron] Proposal to make SR-IOV port attach explicitly fail in nova

None of the in-tree nova virt drivers support attaching SR-IOV ports to a running instance, you can only create a server with an SR-IOV port. I have a patch proposed [1] to make this an explicit failure rather than the user getting an obscure 500 KeyError failure. Supporting this would be a

Re: [openstack-dev] [ironic] Next bug day is Tuesday August 28th! Vote for timeslot!

Hello, With the next bug day coming in a week from today, I wanted to bring up the timeslot poll we have going again. https://doodle.com/poll/ef4m9zmacm2ey7ce I'd like to finalize a time slot for this on Thursday so if you want to cast your vote, please do it soon! Hope to see you there!

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

On Tue, Aug 21, 2018, 8:29 AM Matt Riedemann wrote: > On 8/21/2018 7:28 AM, Matt Riedemann wrote: > > On 8/20/2018 3:18 PM, Sean Mooney wrote: > >> in both the ovs-dpdk tests, when the migration failed and the vm > >> contiuned to run on the source node however > >> it had no network

Re: [openstack-dev] [all] PyCharm Licences

On 8/20/2018 11:24 PM, Swapnil Kulkarni wrote: 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

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

On 8/20/2018 10:10 AM, Trinh Nguyen wrote: Thanks for your response. What is your IRC handler? Kevin_Zheng. -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

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

On 8/21/2018 7:55 AM, Thierry Carrez wrote: Matt Riedemann wrote: [...] Regarding microversions I was mostly thinking of the various times I've been asked in the placement channel if something warrants a microversion or if we can just bug fix it in, like microversion 1.26. I then generally

[openstack-dev] [cinder][manila] Team Dinner Planning at PTG...

All, We talked in the Cinder team meeting about doing a joint Cinder/Manila team dinner at the PTG in Denver. I have created a Doodle Poll to indicate what night would work best for everyone. [1]  Also, if you are planning to come please add your name in the Cinder Etherpad [2]. Look

[openstack-dev] Pending patches of openstack/intel-nfv-ci-tests Project

Dear all, I am sending you this email because there exists an effort to integrate Intel NFV CI tests tempest plugin with Opnfv Functional Testing project (https://wiki.opnfv.org/display/functest). In order to integrate them though, there are some pending patches which should be merged in

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

Heh. And some things don't change... Having a large project such as OpenStack, made up of large numbers of volunteers, each with their own desires means it will be impossible to make everyone happy all of the time. For the good of the community, the community needs to decide on a common