[openstack-dev] [neutron] - no drivers meeting today or next week (May 4th and May 11th)

Hi all, I'm canceling the drivers meeting May 4th and 11th to avoid discussion of new features until after the summit when we have collected user/operator feedback. Cheers, Kevin Benton __ OpenStack Development Mailing List (

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

On Wed, May 03, 2017 at 11:09:32PM -0400, Monty Taylor wrote: > On 05/02/2017 11:49 AM, Sean McGinnis wrote: > > On Tue, May 02, 2017 at 03:36:20PM +0200, Jordan Pittier wrote: > > > On Tue, May 2, 2017 at 7:42 AM, Ghanshyam Mann > > > wrote: > > > > > > > In Cinder, there are many features/APIs

[openstack-dev] [Openstack-operators][heat]desire your feedback and join! And welcome on board!

Hi all, Boston Summit is near, and we need your help and feedback! We really hope to improve your orchestration experiences, so *if you're a User, Operator, or Developer,* please join us on *`Large Orchestration Stacks

Re: [openstack-dev] [qa][heat][murano][daisycloud] Removing Heat support from Tempest

On Wed, May 03, 2017 at 11:51:13AM +, Andrea Frittoli wrote: > On Tue, May 2, 2017 at 5:33 PM Matthew Treinish > wrote: > > > On Tue, May 02, 2017 at 09:49:14AM +0530, Rabi Mishra wrote: > > > On Fri, Apr 28, 2017 at 2:17 PM, Andrea Frittoli < > > andrea.fritt...@gmail.com> > > > wrote: > > >

Re: [openstack-dev] [all][tc][cinder][mistral][manila] A path forward to shiny consistent service types

On 05/03/2017 03:47 AM, Thierry Carrez wrote: Monty Taylor wrote: On 05/01/2017 10:44 AM, Ben Swartzlander wrote: On 04/28/2017 06:26 PM, Monty Taylor wrote: [...] Thoughts? Anyone violently opposed? I don't have any problems with this idea. My main concern would be for backwards-compatibili

Re: [openstack-dev] [all][OSC] OpenStack Interpreter: A useful tool python interpreter tool for the OpenStack client libraries.

On 04/05/17 03:32, Dean Troyer wrote: > On Tue, May 2, 2017 at 7:32 PM, Adrian Turjak wrote: >> Shade in this context is both really easy, and harder since I can't just >> give it the same session so it can reuse the same token. I've tried >> seeing if I can pilfer the OpenStackCloudConfig from

Re: [openstack-dev] [all] Yakumo: Pythonic, unified OpenStack client library

Hi Markus, 2017-05-03 15:59 GMT+09:00 Markus Zoeller : > On 03.05.2017 04:46, Akira Yoshiyama wrote: >> Hello all, >> >> I'm pleased to announce Yakumo, yet another unified OpenStack client >> library with an interactive shell. You can find Yakumo below: >> >>PyPI: https://pypi.python.org/pypi

Re: [openstack-dev] [all][OSC] OpenStack Interpreter: A useful tool python interpreter tool for the OpenStack client libraries.

On 04/05/17 03:20, Dean Troyer wrote: > On Mon, May 1, 2017 at 11:11 PM, Adrian Turjak > wrote: >> As part of my dev work I recently put together a cool little tool which >> lets me have much easier access to the various OpenStack python clients >> in the scope of a python interpreter session. Th

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

On 04/05/17 15:01, Ghanshyam Mann wrote: > > On Wed, May 3, 2017 at 21:57 Andrea Frittoli > mailto:andrea.fritt...@gmail.com>> wrote: > > On Tue, May 2, 2017 at 2:41 PM Jordan Pittier > mailto:jordan.pitt...@scality.com>> > wrote: > > On Tue, May 2, 2017 at 7:42 AM, Ghanshyam

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

On Wed, May 3, 2017 at 22:35 Sean McGinnis wrote: > On Wed, May 03, 2017 at 01:14:18PM +, Andrea Frittoli wrote: > > > > > > > > > > > Now that this is all in place, I think it's working well and I would > like > > > to see it continue that way. IMO, tempest proper should not have > anything

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

On 05/02/2017 11:49 AM, Sean McGinnis wrote: On Tue, May 02, 2017 at 03:36:20PM +0200, Jordan Pittier wrote: On Tue, May 2, 2017 at 7:42 AM, Ghanshyam Mann wrote: In Cinder, there are many features/APIs which are backend specific and will return 405 or 501 if same is not implemented on any ba

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

On Wed, May 3, 2017 at 21:57 Andrea Frittoli wrote: > On Tue, May 2, 2017 at 2:41 PM Jordan Pittier > wrote: > >> On Tue, May 2, 2017 at 7:42 AM, Ghanshyam Mann >> wrote: >> >>> In Cinder, there are many features/APIs which are backend specific and >>> will return 405 or 501 if same is not impl

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

On Wed, May 3, 2017 at 21:49 Andrea Frittoli wrote: > On Tue, May 2, 2017 at 6:46 AM Ghanshyam Mann > wrote: > >> In Cinder, there are many features/APIs which are backend specific and >> will return 405 or 501 if same is not implemented on any backend [1]. >> If such tests are implemented in Te

Re: [openstack-dev] [devstack] [all] systemd in devstack by default

On 05/03/2017 06:45 PM, James Slagle wrote: On Tue, May 2, 2017 at 9:19 AM, Monty Taylor wrote: I absolutely cannot believe I'm saying this given what the change implements and my general steaming hatred associated with it ... but this is awesome work and a definite improvement over what existe

[openstack-dev] [keystone] No policy meeting next week (2017-05-10)

Next week is the Forum, so we'll forego the the policy meeting in favor of some face-to-face discussions. Let's pick back up with policy recaps on the 17th of May. Thanks, Lance __ OpenStack Development Mailing List (not fo

Re: [openstack-dev] OpenStack moving both too fast and too slow at the same time

On 05/03/2017 02:00 PM, Drew Fisher wrote: Reading the user survey [2], I see the same issues time and time again. Pages 18-19 of the survey are especially common points. Things move too fast, no LTS release, upgrades are terrifying for anything that isn't N-1 -> N. These come up time and time a

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests thebackend specific feature?

Yea, the situation described below is imagable. And all things seem to be a measure and tradeoff, i.e., if the feature is supported by a big part of the backends and can be deemed as something like "main trend", then we should test it in Tempest, though inevitably we will suffer the procedu

Re: [openstack-dev] [tripleo] pingtest vs tempest

On Wed, 2017-05-03 at 17:53 -0400, Emilien Macchi wrote: > (cross-posting) > > I've seen a bunch of interesting thoughts here. > The most relevant feedback I've seen so far: > > - TripleO folks want to keep testing fast and efficient. > - Tempest folks understand this problematic and is willing t

Re: [openstack-dev] [devstack] [all] systemd in devstack by default

On 05/03/2017 07:08 PM, Doug Hellmann wrote: Excerpts from Sean Dague's message of 2017-05-03 16:16:29 -0400: Screen is going away in Queens. Making the dev / test runtimes as similar as possible is really important. And there is so much weird debt around trying to make screen launch things rel

Re: [openstack-dev] [devstack] [all] systemd in devstack by default

Excerpts from Sean Dague's message of 2017-05-03 16:16:29 -0400: > Screen is going away in Queens. > > Making the dev / test runtimes as similar as possible is really > important. And there is so much weird debt around trying to make screen > launch things reliably (like random sleeps) because scr

Re: [openstack-dev] [vitrage] trouble installing Nagios on devstack on ubuntu 16.04 ...

One easy way could be writing a scenario to raise deduced alarm based on a simple rule, e.g. when a host is discovered, raise an alarm saying host is up. Waines, Greg 于2017年5月4日 周四04:35写道： > I don’t think I saw any responses to this. > > > > Alternative question ... so I’ve got vitrage up and run

Re: [openstack-dev] [devstack] [all] systemd in devstack by default

On Tue, May 2, 2017 at 9:19 AM, Monty Taylor wrote: > I absolutely cannot believe I'm saying this given what the change implements > and my general steaming hatred associated with it ... but this is awesome > work and a definite improvement over what existed before it. If we're going > to be stuck

Re: [openstack-dev] VMware Voting CI

Hi Sean – this was done in error and we have just fixed it. Sorry for the confusion. Tracy Begin forwarded message: From: Sean McGinnis mailto:sean.mcgin...@gmx.com>> Subject: [openstack-dev] VMware Voting CI Date: May 3, 2017 at 7:06:55 AM PDT To: mailto:openstack-dev@lists.openstack.org>> R

Re: [openstack-dev] [tripleo] pingtest vs tempest

(cross-posting) I've seen a bunch of interesting thoughts here. The most relevant feedback I've seen so far: - TripleO folks want to keep testing fast and efficient. - Tempest folks understand this problematic and is willing to collaborate. I propose that we move forward and experiment the usage

Re: [openstack-dev] [neutron] neutron-lib impact: neutron.plugins.common.constants are now in neutron-lib

On 5/3/17 8:55 AM, Eric Fried wrote: > Can you please point to the change(s) that move the constants? Or > provide some other way to figure out which are affected? > This Hound search [1] provides an overall picture and can be honed to specific projects as needed. The search will identify all

[openstack-dev] [LBaaS][octavia] Weekly IRC meeting cancelled for three weeks

Hi Octavia team, At today's weekly LBaaS/Octavia IRC meeting we decided to cancel the next three meetings due to the OpenStack summit, other conflicts, and vacations. We just won't have quorum these weeks. Safe travels for those attending the OpenStack summit and we will meet again 5/31/17. Mic

Re: [openstack-dev] [vitrage] trouble installing Nagios on devstack on ubuntu 16.04 ...

I don’t think I saw any responses to this. Alternative question ... so I’ve got vitrage up and running fine ... What’s the easiest way to generate an alarm against a host ? ( OTHER than NAGIOS, due to problem in original email ) ??? let me know any ideas, Greg. From: Greg Waines Date: Tues

Re: [openstack-dev] [devstack] [all] systemd in devstack by default

Screen is going away in Queens. Making the dev / test runtimes as similar as possible is really important. And there is so much weird debt around trying to make screen launch things reliably (like random sleeps) because screen has funny races in it. It does mean some tricks people figured out in

[openstack-dev] [glance] no meeting this week

Hello Glancers, The weekly Glance IRC meeting is cancelled for tomorrow (May 4) and the summit week (May 11). We'll resume our regular weekly meeting cadence on Thursday, May 18. If you'll be at the summit/forum in Boston, you may find some fellow glance people at these sessions: Mon 8 , 12:45p

Re: [openstack-dev] [devstack] [all] systemd in devstack by default

Hi Sean, I tried the new systemd devstack and frankly I don't like it. There are several handy operations in screen that seems to be impossible after switching to systemd. For example, freeze a process by "Ctrl + a + [". In addition, navigating though the logs seems difficult (perhaps I am not

[openstack-dev] OpenStack moving both too fast and too slow at the same time

This email is meant to be the ML discussion of a question I brought up during the TC meeting on April 25th.; [1] The TL;DR version is: Reading the user survey [2], I see the same issues time and time again. Pages 18-19 of the survey are especially common points. Things move too fast, no LTS rele

Re: [openstack-dev] [nova-scheduler] Get scheduler hint

On 05/03/2017 03:08 AM, Giuseppe Di Lena wrote: Thank you a lot for the help! I think that the problem can be solved using the anti-affinity filter, but we want a regular user can choose an instance and set the property(image, flavour, network, etc.) and a parameter Robustness >= 1(that is the

Re: [openstack-dev] [tc] [all] TC Report 18

On 2017-05-03 14:04:40 -0400 (-0400), Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2017-05-03 13:23:11 -0400: > > On 05/03/2017 01:02 PM, Doug Hellmann wrote: > > > Excerpts from Thierry Carrez's message of 2017-05-03 18:16:29 +0200: [...] > > > Knowing what will be discussed in adv

Re: [openstack-dev] [tc] [all] TC Report 18

Excerpts from Sean Dague's message of 2017-05-03 13:23:11 -0400: > On 05/03/2017 01:02 PM, Doug Hellmann wrote: > > Excerpts from Thierry Carrez's message of 2017-05-03 18:16:29 +0200: > >> Ed Leafe wrote: > >>> On May 3, 2017, at 2:41 AM, Thierry Carrez wrote: > >>> > In the current > s

Re: [openstack-dev] [tc] [all] TC Report 18

On 05/03/2017 01:02 PM, Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2017-05-03 18:16:29 +0200: >> Ed Leafe wrote: >>> On May 3, 2017, at 2:41 AM, Thierry Carrez wrote: >>> In the current system, TC members (or really, anyone in the community) can add to the "Ope

[openstack-dev] [barbican] [security] Project Onboarding in Boston

Greetings! If you are interested in learning more about Barbican with a goal to contribute, please come to the Barbican Project Onboarding session on Tuesday, May 9, at 2pm in Room MR101. We'll be sharing the time slot with the Security project for those interested in becoming an OpenStack Sec

Re: [openstack-dev] [tc] [all] TC Report 18

Excerpts from Thierry Carrez's message of 2017-05-03 18:16:29 +0200: > Ed Leafe wrote: > > On May 3, 2017, at 2:41 AM, Thierry Carrez wrote: > > > >> In the current > >> system, TC members (or really, anyone in the community) can add to the > >> "Open discussion" section of the meeting agenda, bu

Re: [openstack-dev] [tc] [all] TC Report 18

On Wed, May 3, 2017 at 2:41 AM, Thierry Carrez wrote: > Chris Dent wrote: > > > > # Intro > > > > Feedback from last week's first attempt at a weekly overview of TC > > activity was positive enough to continue. Suggestions on how to make > > it more useful welcome. Main change this time is that I

Re: [openstack-dev] [tc] [all] TC Report 18

Ed Leafe wrote: > On May 3, 2017, at 2:41 AM, Thierry Carrez wrote: > >> In the current >> system, TC members (or really, anyone in the community) can add to the >> "Open discussion" section of the meeting agenda, but that happens >> extremely rarely. I suspect that the 5 minutes per week that we

Re: [openstack-dev] [all] Yakumo: Pythonic, unified OpenStack client library

Hi Andrea, 2017-05-03 21:00 GMT+09:00 Andrea Frittoli : > > > On Wed, May 3, 2017 at 12:44 PM Brian Curtin wrote: >> >> On Tue, May 2, 2017 at 10:46 PM, Akira Yoshiyama >> wrote: >>> >>> Hello all, >>> >>> I'm pleased to announce Yakumo, yet another unified OpenStack client >>> library with an i

Re: [openstack-dev] VMware Voting CI

On Wed, May 03, 2017 at 02:42:34PM +, Jeremy Stanley wrote: > On 2017-05-03 09:06:55 -0500 (-0500), Sean McGinnis wrote: > [...] > > This CI account, however, appears to be used for multiple projects. > > I think it got voting rights via a different project. > [...] > > Doesn't work like that;

[openstack-dev] [sahara] Project Onboarding in Boston

Hi folks, If you are interested in learning more about Sahara or meet the expert developers, we organized a Sahara - Project Onboarding on Tue, May 9, 5:30pm -- 6:10pm Level One MR 1015. I've put together an etherpad to list folks from Sahara who will be there, please add yourself, and also to li

Re: [openstack-dev] [keystone] Colleen Murphy for core

On 13:15 May 02, Lance Bragstad wrote: > Hey folks, > > During today's keystone meeting we added another member to keystone's core > team. For several releases, Colleen's had a profound impact on keystone. > Her reviews are meticulous and of incredible quality. She has no hesitation > to jump into

[openstack-dev] [keystone][forum] BM/VM session conflict with project workshop

Looking through the schedule of keystone-tagged sessions, it appears we have a conflict between one of the BM/VM sessions [0] and keystone's project on-boarding session [1]. I wouldn't be opposed to shuffling, but I assume it's too late for that? If we can get a good idea of who is going to show u

[openstack-dev] [murano] Weekly meeting today is cancelled

Hi, I'm going to cancel this week's IRC meeting, because here's not much on the agenda for today and few are likely to make it anyway. Next meeting is 5/9/2017. Thank You, Felipe Monteiro __ OpenStack Development Mailing Li

Re: [openstack-dev] [swift] Adding our developments to Assosciated projects list

Nejc, Great to see stuff being built on and around Swift. There's no special process for adding stuff to that page. It's a .rst file in the Swift code repo (https://github.com/openstack/swift/blob/master/doc/source/associated_projects.rst) and you can submit a patch for it via the normal patch

Re: [openstack-dev] [tc] [all] TC Report 18

On May 3, 2017, at 2:41 AM, Thierry Carrez wrote: > In the current > system, TC members (or really, anyone in the community) can add to the > "Open discussion" section of the meeting agenda, but that happens > extremely rarely. I suspect that the 5 minutes per week that we end up > dedicating to

Re: [openstack-dev] [all] Yakumo: Pythonic, unified OpenStack client library

Hi Brian, 2017-05-03 20:42 GMT+09:00 Brian Curtin : > On Tue, May 2, 2017 at 10:46 PM, Akira Yoshiyama > wrote: >> >> Hello all, >> >> I'm pleased to announce Yakumo, yet another unified OpenStack client >> library with an interactive shell. You can find Yakumo below: >> >>PyPI: https://pypi.

Re: [openstack-dev] [all][OSC] OpenStack Interpreter: A useful tool python interpreter tool for the OpenStack client libraries.

On Tue, May 2, 2017 at 7:32 PM, Adrian Turjak wrote: > Shade in this context is both really easy, and harder since I can't just > give it the same session so it can reuse the same token. I've tried > seeing if I can pilfer the OpenStackCloudConfig from OSC but passing > that to shade seemed to bre

Re: [openstack-dev] [kolla][kolla-ansible] Proposing Bertrand Lallau for kolla and kolla-ansible core

+1 On Wed, May 3, 2017 at 3:10 PM, Mauricio Lima wrote: > +1 > > 2017-05-03 1:43 GMT-03:00 Christian Berendt > : >> >> +1 >> >> > On 2. May 2017, at 17:30, Michał Jastrzębski wrote: >> > >> > Hello, >> > >> > It's my pleasure to start another core reviewer vote. Today it's >> > Bertrand (blallau

Re: [openstack-dev] [all][OSC] OpenStack Interpreter: A useful tool python interpreter tool for the OpenStack client libraries.

On Mon, May 1, 2017 at 11:11 PM, Adrian Turjak wrote: > As part of my dev work I recently put together a cool little tool which > lets me have much easier access to the various OpenStack python clients > in the scope of a python interpreter session. The first version was a > little rough and witho

Re: [openstack-dev] [nova] Degradation of performance on master

Hi, No sorry but we haven’t run this with os-profiler (and don’t have plans to run). Thank you, Anastasia > From: Matt Riedemann mailto:mriede...@gmail.com>> > Sent: Thursday, April 27, 2017 9:20 PM > To: openstack-dev@lists.openstack.org > > Subject:

[openstack-dev] [OSC] OpenStackClient release and core team and meetings

First of all, I would like to say how glad I am to have seen the two recent messages regarding other OpenStack client-side projects. More projects like this raise the visibility of all of the client-side work as it illustrates the importance of the consumer side of OpenStack APIs in the minds of t

Re: [openstack-dev] [neutron] neutron-lib impact: neutron.plugins.common.constants are now in neutron-lib

Boden- Can you please point to the change(s) that move the constants? Or provide some other way to figure out which are affected? Thanks, Eric (efried) On 05/03/2017 09:30 AM, Boden Russell wrote: > If your project uses neutron.plugins.com

Re: [openstack-dev] VMware Voting CI

On 2017-05-03 09:06:55 -0500 (-0500), Sean McGinnis wrote: [...] > This CI account, however, appears to be used for multiple projects. > I think it got voting rights via a different project. [...] Doesn't work like that; there are project-specific "-ci" groups in our Gerrit which your ACLs are con

[openstack-dev] [horizon] Next 2 weekly meetings cancelled

Hi everyone! The next two weekly IRC meetings (3rd May, 10th May) are cancelled. I'm away this week and next week is the summit. Meetings will resume on the 17th! For those going to the summit, please read http://lists.openstack.org/pipermail/openstack-dev/2017-April/115982.html for meetup inf

[openstack-dev] [neutron] neutron-lib impact: neutron.plugins.common.constants are now in neutron-lib

If your project uses neutron.plugins.common.constants please read on. If not, it's probably safe to discard this message. A number of the constants from neutron.plugins.common.constants have moved into neutron-lib: - The service type constants are in neutron_lib.plugins.constants - Many of the oth

[openstack-dev] Project on-boarding - are you going? What do you need/want to know?

Some of the nova team is on a hangout trying to figure out how we're going to structure the nova project on-boarding session at the Forum [1]. We've got an etherpad started here [2]. It became abundantly clear very early that we don't know who is going to be attending a session like this and w

Re: [openstack-dev] VMware Voting CI

Big +1 to Sean especially for Cinder-related issues Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Wed, May 3, 2017 at 5:06 PM, Sean McGinnis wrote: > Hey everyone, > > I'm looking for some background on the VMware NSX CI. Specifically, > why this CI is enabled for voting. > > We had disc

Re: [openstack-dev] [vitrage] Alarm Banner for Vitrage Dashboard ?

Hi, I agree that there should be two blueprints, one for Horizon and one for Vitrage. For new APIs we usually write a spec file with the API definition, so other people can comment on gerrit. Thanks, and looking forward to the blueprint ☺ Ifat. From: "Waines, Greg" Reply-To: "OpenStack Devel

[openstack-dev] VMware Voting CI

Hey everyone, I'm looking for some background on the VMware NSX CI. Specifically, why this CI is enabled for voting. We had discussed whether to have "stable" CI's vote in the Cinder project a while back, and other than potentially some benefit in doing scripted reporting, we couldn't really thin

Re: [openstack-dev] [nova][deployment] Changing to run nova-api/meta-api under uwsgi by default

On Wed, May 3, 2017 at 9:17 AM, Matt Riedemann wrote: > Chris Dent has a change up to devstack [1] which is going to make > nova-api/meta-api run under uwsgi by default on master (Pike). > > That depends on a grenade change [2] which is simply there so we can roll > through upgrades from Ocata to

[openstack-dev] [swift] Adding our developments to Assosciated projects list

Greetings, Since I haven't found any appropriate guideline on the webpages and wiki I have decided to contact the lists. I apologize in advance if I'm spamming a bit. As part of the IOStack project (http://iostack.eu/) we developed a really promising feature for Swift that we called Crystal (htt

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

On Wed, May 03, 2017 at 01:14:18PM +, Andrea Frittoli wrote: > > > > > > > Now that this is all in place, I think it's working well and I would like > > to see it continue that way. IMO, tempest proper should not have anything > > that isn't universally applicable to real world deployments. N

Re: [openstack-dev] [devstack] [all] systemd in devstack by default

On 5/3/2017 5:09 AM, Sean Dague wrote: If you run into any other issues please pop into #openstack-qa (or respond to this email) and we'll try to work through them. Something has definitely gone haywire in the cells v1 job since 5/1 and the journal log handler: http://status.openstack.org/el

[openstack-dev] [nova][deployment] Changing to run nova-api/meta-api under uwsgi by default

Chris Dent has a change up to devstack [1] which is going to make nova-api/meta-api run under uwsgi by default on master (Pike). That depends on a grenade change [2] which is simply there so we can roll through upgrades from Ocata to Pike with eventlet, but new installs in Pike via devstack wi

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

On Tue, May 2, 2017 at 4:56 PM Sean McGinnis wrote: > On Tue, May 02, 2017 at 03:36:20PM +0200, Jordan Pittier wrote: > > On Tue, May 2, 2017 at 7:42 AM, Ghanshyam Mann > > wrote: > > > > > In Cinder, there are many features/APIs which are backend specific and > > > will return 405 or 501 if sam

Re: [openstack-dev] [neutron] stepping down from infra liaison

Really sad to hear that. It was a pleasure working with you - all the best for your future! -- - Andreas IRC: andreas_s On Mi, 2017-05-03 at 00:39 +, Das, Anindita wrote: > Hi All, > > > > Some of you already know about the recent changes in OSIC. > Unfortunately, I am impacted by

Re: [openstack-dev] [kolla][kolla-ansible] Proposing Bertrand Lallau for kolla and kolla-ansible core

+1 2017-05-03 1:43 GMT-03:00 Christian Berendt : > +1 > > > On 2. May 2017, at 17:30, Michał Jastrzębski wrote: > > > > Hello, > > > > It's my pleasure to start another core reviewer vote. Today it's > > Bertrand (blallau). Consider this mail my +1 vote. Members of > > kolla-ansible and kolla c

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

On Tue, May 2, 2017 at 2:41 PM Jordan Pittier wrote: > On Tue, May 2, 2017 at 7:42 AM, Ghanshyam Mann > wrote: > >> In Cinder, there are many features/APIs which are backend specific and >> will return 405 or 501 if same is not implemented on any backend [1]. >> If such tests are implemented in

Re: [openstack-dev] [qa][cinder][ceph] should Tempest tests the backend specific feature?

On Tue, May 2, 2017 at 6:46 AM Ghanshyam Mann wrote: > In Cinder, there are many features/APIs which are backend specific and > will return 405 or 501 if same is not implemented on any backend [1]. > If such tests are implemented in Tempest, then it will break some gate > where that backend job i

Re: [openstack-dev] [ironic] Goodbye ironic o/

Mario, So sorry to hear that you won't be working on Ironic anymore :( Good luck with your new assignments! On Tue, May 2, 2017 at 7:10 AM, Ranganathan, Shobha < shobha.ranganat...@intel.com> wrote: > Hi Mario, > > > > Sorry to hear that you won’t be working on Ironic anymore! > > Best of luck o

[openstack-dev] [TripleO] Deep dive Thursday May 4th 1400 UTC on deployed-server

I saw there was no deep dive scheduled for tomorrow, so I decided I'd go ahead and plan one. It will be recorded if you can't make it on the short notice. I plan to cover the "deployed-server" feature in TripleO. We have been using this feature since Newton to drive our multinode CI. I'll go over

Re: [openstack-dev] [all] Yakumo: Pythonic, unified OpenStack client library

On Wed, May 3, 2017 at 12:44 PM Brian Curtin wrote: > On Tue, May 2, 2017 at 10:46 PM, Akira Yoshiyama > wrote: > >> Hello all, >> >> I'm pleased to announce Yakumo, yet another unified OpenStack client >> library with an interactive shell. You can find Yakumo below: >> >>PyPI: https://pypi.

Re: [openstack-dev] [qa][heat][murano][daisycloud] Removing Heat support from Tempest

On Tue, May 2, 2017 at 5:33 PM Matthew Treinish wrote: > On Tue, May 02, 2017 at 09:49:14AM +0530, Rabi Mishra wrote: > > On Fri, Apr 28, 2017 at 2:17 PM, Andrea Frittoli < > andrea.fritt...@gmail.com> > > wrote: > > > > > > > > > > > On Fri, Apr 28, 2017 at 10:29 AM Rabi Mishra > wrote: > > > >

Re: [openstack-dev] [all] Yakumo: Pythonic, unified OpenStack client library

On Tue, May 2, 2017 at 10:46 PM, Akira Yoshiyama wrote: > Hello all, > > I'm pleased to announce Yakumo, yet another unified OpenStack client > library with an interactive shell. You can find Yakumo below: > >PyPI: https://pypi.python.org/pypi/yakumo/ >Github: https://github.com/yosshy/py

Re: [openstack-dev] [vitrage] Alarm Banner for Vitrage Dashboard ?

Yes, the banner would be displayed on all Horizon screens, not just Vitrage. Agree that this would mean changes in both Horizon and some supporting code in Vitrage. Would this mean 2x Blueprints ? - one in Horizon for the display side of the Banner, and - one in Vitrage to make the Alar

Re: [openstack-dev] [TripleO][CI] Quickstart deep dive

A video from the recording of the deep-dive is now available at https://youtu.be/qaTwGBuLoRc Thanks to everyone for the participation, we hope it helped. __ OpenStack Development Mailing List (not for usage questions) Unsub

[openstack-dev] [tripleo] images.rdoproject.org / thirdparty-logs.rdoproject.org is going tdown for a short maintenance

I need to reboot this machine for updates/fixes. It should be a short downtime, but a few jobs/downloads might be interrupted, so I announce it here for reference. This jobs serves both TripleO and RDO jobs, so I CC both mailing list. Best regards, Attila _

Re: [openstack-dev] [devstack] [all] systemd in devstack by default

On 05/02/2017 08:30 AM, Sean Dague wrote: > We started running systemd for devstack in the gate yesterday, so far so > good. > > The following patch (which will hopefully land soon), will convert the > default local use of devstack to systemd as well - > https://review.openstack.org/#/c/461716/. I

[openstack-dev] [oslo] cancel weekly meeting in next week (05/08)

Hi folks, Just a reminder that we will skip oslo weekly meeting in next week, most people should be in the Boston Summit :-) -- ChangBo Guo(gcb) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: op

Re: [openstack-dev] [nova-scheduler] Get scheduler hint

Thank you a lot for the help! I think that the problem can be solved using the anti-affinity filter, but we want a regular user can choose an instance and set the property(image, flavour, network, etc.) and a parameter Robustness >= 1(that is the number of copies of this particular instance).

[openstack-dev] [Openstack-operators] try and feedback on tenant overlay networking across multiple OpenStack clouds

Hello, Tricircle is a project to provide tenant level L2/L3 overlay networking automation across Neutron in multi-region OpenStack deployments. The cross OpenStack networking topology can be composed mainly from four concepts: Local Network - Local Network is a network which can only reside

Re: [openstack-dev] [all][tc][cinder][mistral][manila] A path forward to shiny consistent service types

Monty Taylor wrote: > On 05/01/2017 10:44 AM, Ben Swartzlander wrote: >> On 04/28/2017 06:26 PM, Monty Taylor wrote: >>> [...] >>> Thoughts? Anyone violently opposed? >> >> I don't have any problems with this idea. My main concern would be for >> backwards-compatibility and it sounds like that's pr

Re: [openstack-dev] [tc] [all] TC Report 18

Chris - I am sure that this was said before (I do recall a mail last week on the mailing list after you sent it out). Thank you - this is awesome! A great recap - please continue doing this!! On 03/05/17 0:46, Chris Dent wrote: > > # Intro > > Feedback from last week's first attempt at a weekly

Re: [openstack-dev] [tc] [all] TC Report 18

Chris Dent wrote: > > # Intro > > Feedback from last week's first attempt at a weekly overview of TC > activity was positive enough to continue. Suggestions on how to make > it more useful welcome. Main change this time is that I've added > some information on stuff happened outside the meeting,

Re: [openstack-dev] [vitrage] Alarm Banner for Vitrage Dashboard ?

Hi Greg, It sounds like a great idea. Do you plan to show this banner in all Horizon menus (your screenshot shows “Compute/Instances”), or just in Vitrage? for the first option I think you would need to write the code in Horizon itself, not in vitrage-dashboard. Let me know if you need any assi

Re: [openstack-dev] [all] Yakumo: Pythonic, unified OpenStack client library

On 03.05.2017 04:46, Akira Yoshiyama wrote: > Hello all, > > I'm pleased to announce Yakumo, yet another unified OpenStack client > library with an interactive shell. You can find Yakumo below: > >PyPI: https://pypi.python.org/pypi/yakumo/ >Github: https://github.com/yosshy/python-yakumo/