Re: [Openstack-operators] Maintenance

This was originated because theTelco requirements I have described there. The implementation will reside in the OpenStack. So we are looking the problem described, what else operators need and then how to accomplish that. Most probably looking a new tool instead of injecting any existing. Tomi

[openstack-dev] [Telemetry][Ceilometer][Aodh] Clean crazy old bugs and patches

Hi devs, Recently I'm cleaning bugs and reviews of Ceilometer+Aodh, some out dated bugs, long time (two months) no active reviews, assignments will be removed. If you are the owner or just interest in it, please provide new information or follow ups, to let them alive again. Thanks, ZhiQiang Fan

Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

Jeremy, Thanks for the information - you can tell I'm a bit dated ;) Folks, take this vote to mean what Jeremy has stated as far as repo deprecation goes. Regards -steve On 4/22/16, 8:01 PM, "Jeremy Stanley" wrote: >On 2016-04-23 00:08:03 + (+), Steven Dake

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

On 04/22/2016 09:57 PM, Tim Bell wrote: I have reservations on f and g. Probably not the *best* choice of words to describe your concerns, Tim :P -jay __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

On 2016-04-23 00:08:03 + (+), Steven Dake (stdake) wrote: [...] > I propose we move the kolla-mesos repository into the attic [...] We no longer rename Git repositories as a part of their lifecycle. Just abandon any open changes, merge a commit to it replacing its files with a readme

Re: [Openstack] Mitaka, does it supports "VLAN aware VMs"?

On 22 April 2016 at 18:33, Martinx - ジェームズ wrote: > Guys, > > I need to create Instances on Mitaka, that needs to see the VLAN tags... > > Does Mitaka supports that? > > If not, what is the state of this? If yes, where are the docs? =) > > Thanks! > Thiago >

Re: [Openstack-operators] Maintenance

The overall requirements are being reviewed in https://etherpad.openstack.org/p/AUS-ops-Nova-maint. A future tool may make its way in OSOps but I think we should keep the requirements discussion distinct from the available community tools and their tool repository. Tim From: Joseph Bajin

Re: [openstack-dev] [kolla] kolla-kubernetes pm's

Hey, Right now kolla-k8s is on the drawing board. We didn't write any code so far. We will have session in Austin about this topic, so feel free to jump in, your input would be extremely valuable Cheers, Michal On 22 April 2016 at 19:31, Fox, Kevin M wrote: > Are there any

Re: [openstack-dev] [heat]informal meetup during summit

Let's settle down on with A meet up on Monday night 7:00pm At continentalclub address : 1315 S Congress Ave Austin, TX 78704 http://continentalclub.com

Re: [openstack-dev] [kubernetes] Introducing the Kubernetes OpenStack Special Interest Group

Hi Ihor, This is a great news ! As a matter of fact at the moment the Tricircle team from OpenStack is working with Ubernetes team lead by Quinton to explore features about how OpenStack federation could help K8s federation works better. This SIG seems like a good fit for our ongoing work. Will

[openstack-dev] [kolla] kolla-kubernetes pm's

Are there any plans in kolla-kubernetes to integrate with the package managers that are starting to spring up? https://github.com/kubespray/kpm or https://github.com/helm/helm ? It would probably be better to reuse at least one then try and reinvent it if possible. (tangential question. is

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

Responses inline. From: Sergey Lukjanov > Reply-To: OpenStack Development Mailing List > Date: Friday, April 22, 2016 at 11:17 AM To: OpenStack Development Mailing

Re: [openstack-dev] [ironic][nova][horizon] Serial console support for ironic instances

Hi all, Thank you Yuiko. I'll join the console session. See you at the venue. (2)Add console drivers using ironic-console-server https://review.openstack.org/#/c/302291/ (ironic-console-server) https://review.openstack.org/#/c/306754/ (console logging spec)

Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

+1 since Mirantis was only company actively developing kolla-mesos. If anyone want's to take over kolla-mesos, now is the time. On 22 April 2016 at 19:08, Steven Dake (stdake) wrote: > Fellow Core Reviewers, > > Since many of the engineers working on the kolla-mesos repository

[openstack-dev] [kubernetes] Introducing the Kubernetes OpenStack Special Interest Group

Colleagues, I'm happy to announce within the OpenStack community the Kubernetes OpenStack Special Interest Group. Kubernetes Community currently runs to the deeper integration between OpenStack and Kubernetes and one of the main aims now - to work on enabling OpenStack as a platform for running

[openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

Fellow Core Reviewers, Since many of the engineers working on the kolla-mesos repository are moving on to other things[1], possibly including implementing Kubernetes as an underlay for OpenStack containers, I propose we move the kolla-mesos repository into the attic[2]. This will allow folks

Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc project f2f2 meet-up place and time

Sounds good. Thanks Cathy. Anil On Fri, Apr 22, 2016 at 3:30 PM, Cathy Zhang wrote: > Hi Everyone, > > > > As we discussed in our project meeting, we should have a f2f meeting > during the summit. > > let’s meet at "Salon C" for lunch from 12:30pm~1:50pm on Tuesday. >

[openstack-dev] [lbaas][octavia] No Octavia IRC meeting 4/27/16

Since most of us will be attending the summit next week I am canceling the Octavia IRC meeting on April 27th. Michael __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] kolla-kubernetes [kolla][kubernetes]

Just want to give everyone a heads up about a schedule change for kolla summit sessions. Kolla-kubernetes was a kolla spec [1] that we had intended to cover at summit in a design session. We are going to change it to a fish bowl session instead to be held on Wednesday at 9am and the

Re: [Openstack-operators] Maintenance

Rob/Jay, The use of the OSOps Working group and its repos is a great way to address this.. If any of you are coming to the Summit, please take a look at our Etherpad that we have created.[1] This could be a great discussion topic for the working sessions and we can brainstorm how we could help

Re: [openstack-dev] Summit Core Party after Austin

Many thanks Tom! > -Original Message- > From: Tom Fifield [mailto:t...@openstack.org] > Sent: Friday, April 22, 2016 5:59 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] Summit Core Party after Austin > > Hi all, > > On 22/04/16 16:40, Clint Byrum wrote: > >

Re: [Openstack] Openstack security - port-security, security-groups with added container

Thank you Kevin.Works like a charm now. Farhad. On Friday, April 22, 2016 4:43 AM, Kevin Benton wrote: The status being DOWN is an issue. That means either the port binding failed because the host_id was not set on the port that matches the hostname where the

Re: [openstack-dev] [Neutron] Neutron client and plan to transition to OpenStack client

thanks to richard, tangchen, reepid and others for picking this up and running with it; and thanks to armando for embracing OSC and putting it in neutron's plan. On Fri, Apr 22, 2016 at 6:33 PM, reedip banerjee wrote: > Hi Richard, > Thanks for the information :) > > Was

Re: [openstack-dev] [nova] Distributed Database

On 04/22/2016 05:29 PM, Dan Smith wrote: This would be a very interesting direction to explore. Focus on the pain points of the message queue and then look at addressing the beast that is the database layer separately. I am going to toss support in behind a lot of what has been said in this

Re: [Openstack-operators] [openstack-dev] Thank you to our Event Planners

On 04/22/2016 05:22 PM, Anita Kuno wrote: I would like to take a moment to say thank you to all the folks in our community who take the time and trouble to plan events for all of us to enjoy. Events of all kinds help us to learn and grow by extending ourselves and learning about different ways

Re: [openstack-dev] Thank you to our Event Planners

On 04/22/2016 05:22 PM, Anita Kuno wrote: I would like to take a moment to say thank you to all the folks in our community who take the time and trouble to plan events for all of us to enjoy. Events of all kinds help us to learn and grow by extending ourselves and learning about different ways

Re: [openstack-dev] [Neutron] Neutron client and plan to transition to OpenStack client

Hi Richard, Thanks for the information :) Was waiting for it. On Sat, Apr 23, 2016 at 3:27 AM, Armando M. wrote: > > > On 22 April 2016 at 13:58, Richard Theis wrote: > >> FYI: I've pushed a series of WIP patch sets [1], [2] and [3] to enable >>

[Openstack-operators] nova snapshots should dump all RAM to hypervisor disk ?

Hello Operators, one of the users of our cluster opened a ticket about a snapshot corner case. It is not possible to snapshot a instance that is booted from volume when the instance is paused. So I wrote this patch, and from the discussion you can see that I learnt a lot about snapshots.

[openstack-dev] [neutron] [networking-sfc] Network-sfc project f2f2 meet-up place and time

Hi Everyone, As we discussed in our project meeting, we should have a f2f meeting during the summit. let's meet at "Salon C" for lunch from 12:30pm~1:50pm on Tuesday. Since Salon C is a big room, I will put a sign "Networking-SFC Project Meet-Up" on the table. Thanks, Cathy

Re: [openstack-dev] [nova] Distributed Database

> This would be a very interesting direction to explore. Focus on the pain > points of the message queue and then look at addressing the beast that > is the database layer separately. I am going to toss support in behind a > lot of what has been said in this thread already. But I really wanted to

[Openstack-operators] Thank you to our Event Planners

I would like to take a moment to say thank you to all the folks in our community who take the time and trouble to plan events for all of us to enjoy. Events of all kinds help us to learn and grow by extending ourselves and learning about different ways of doing things. We get to interact with new

[openstack-dev] Thank you to our Event Planners

I would like to take a moment to say thank you to all the folks in our community who take the time and trouble to plan events for all of us to enjoy. Events of all kinds help us to learn and grow by extending ourselves and learning about different ways of doing things. We get to interact with new

Re: [openstack-dev] [nova] Distributed Database

On Fri, Apr 22, 2016 at 2:57 PM, Dan Smith wrote: > > However I do want to point out that cells v2 is not just about dealing > > with scale in the database. The message queue is another consideration, > > and as far as I know there is not an analog to the "distributed > >

Re: [openstack-dev] [Security][Barbican][all] Bring your own key fishbowl sessions

Oh, I think I understand. something like: You set up your private cloud with a public region ala K2K federation. The other Cloud then shows up as another region in your cloud. This would then allow your barbican in one region to be accessible to vm's launched in the public region? Kind of a

Re: [openstack-dev] Summit Core Party after Austin

On Fri, Apr 22, 2016 at 2:58 PM, Tom Fifield wrote: > Hi all, > > On 22/04/16 16:40, Clint Byrum wrote: > >> But in the mean time, maybe we can just send this message >> to party planners: Provide us with interesting spaces to converse and >> bond in, and we will be happier.

Re: [openstack-dev] Summit Core Party after Austin

Hi all, On 22/04/16 16:40, Clint Byrum wrote: But in the mean time, maybe we can just send this message to party planners: Provide us with interesting spaces to converse and bond in, and we will be happier. Spoke with the party planners and got the inside gossip :) The good news: for the

Re: [openstack-dev] [Neutron] Neutron client and plan to transition to OpenStack client

On 22 April 2016 at 13:58, Richard Theis wrote: > FYI: I've pushed a series of WIP patch sets [1], [2] and [3] to enable > python-neutronclient OSC plugins. I've used "openstack network agent list" > as the initial OSC plugin command example. Hopefully these will help >

Re: [openstack-dev] [nova] Distributed Database

> However I do want to point out that cells v2 is not just about dealing > with scale in the database. The message queue is another consideration, > and as far as I know there is not an analog to the "distributed > database" option available for the persistence layer. Yeah, it's actually *mostly*

Re: [openstack-dev] [nova] Distributed Database

On 04/22/2016 04:32 PM, Andrew Laski wrote: On Fri, Apr 22, 2016, at 04:27 PM, Ed Leafe wrote: OK, so I know that Friday afternoons are usually the worst times to write a blog post and start an email discussion, and that the Friday immediately before a Summit is the absolute worst, but I did

Re: [openstack-dev] [Security][Barbican][all] Bring your own key fishbowl sessions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 No conflicts with your cross-project session as far as I can tell. In a nutshell BYOK-Push is a model where the customer retains full control of their cryptographic keys. The customer is expected to provide the necessary keys each and every time a

Re: [openstack-dev] Summit Core Party after Austin

Excerpts from Chivers, Doug's message of 2016-04-22 10:17:45 -0700: > The Vancouver core party was a fantastic opportunity to meet some very smart > people and learn a lot about the projects they worked on. It was probably one > of the most useful parts of the summit, certainly more so than the

[Openstack] Mitaka, does it supports "VLAN aware VMs"?

Guys, I need to create Instances on Mitaka, that needs to see the VLAN tags... Does Mitaka supports that? If not, what is the state of this? If yes, where are the docs? =) Thanks! Thiago ___ Mailing list:

Re: [openstack-dev] [nova] Distributed Database

On Fri, Apr 22, 2016, at 04:27 PM, Ed Leafe wrote: > OK, so I know that Friday afternoons are usually the worst times to > write a blog post and start an email discussion, and that the Friday > immediately before a Summit is the absolute worst, but I did it anyway. > >

Re: [openstack-dev] [Security][Barbican][all] Bring your own key fishbowl sessions

Can you please give a little more detail on what its about? Does this have any overlap with the instance user session: https://www.openstack.org/summit/austin-2016/summit-schedule/events/9485 Thanks, Kevin From: Rob C [hyaku...@gmail.com] Sent: Friday, April 22,

Re: [openstack-dev] [release] release hiatus

Excerpts from Tony Breeds's message of 2016-04-22 09:22:59 +1000: > On Thu, Apr 21, 2016 at 02:13:15PM -0400, Doug Hellmann wrote: > > The release team is preparing for and traveling to the summit, just as > > many of you are. With that in mind, we are going to hold off on > > releasing anything

Re: [openstack-dev] [Neutron] Neutron client and plan to transition to OpenStack client

FYI: I've pushed a series of WIP patch sets [1], [2] and [3] to enable python-neutronclient OSC plugins. I've used "openstack network agent list" as the initial OSC plugin command example. Hopefully these will help during the discussions at the summit. [1]

Re: [openstack-dev] [infra][devstack] stable/kilo devstack fails with pkg_resources.ContextualVersionConflict

On Thu, 21 Apr 2016 15:12:53 +1000 Tony Breeds wrote: > On Tue, Apr 19, 2016 at 01:14:34PM +0200, Lajos Katona wrote: > > Hi, > > > > In our internal CI system we realized that stable/kilo devstack > > fails with the following stack trace: > > > > > It seems that

Re: [openstack-dev] [nova] Distributed Database

On 04/22/2016 03:27 PM, Ed Leafe wrote: OK, so I know that Friday afternoons are usually the worst times to write a blog post and start an email discussion, and that the Friday immediately before a Summit is the absolute worst, but I did it anyway.

Re: [openstack-dev] [Security][Barbican][all] Bring your own key fishbowl sessions

So that's one vote for option A and one vote for another vote :) On 22 Apr 2016 4:25 p.m., "Nathan Reller" wrote: > > Thoughts? > > Is anyone interested in the pull model or actually implementing it? I > say if the answer to that is no then only discuss the push model.

Re: [openstack-dev] [nova] Distributed Database

Ed, fyi, i just got a ping about this effort: https://github.com/BeyondTheClouds/BeyondTheClouds.github.io/raw/master/DOCS/PAPERS/2015/nova-description/BTC-DISCOVERY-Overview.pdf https://github.com/BeyondTheClouds/rome https://beyondtheclouds.github.io/ They have a WG session:

[openstack-dev] [nova] Distributed Database

OK, so I know that Friday afternoons are usually the worst times to write a blog post and start an email discussion, and that the Friday immediately before a Summit is the absolute worst, but I did it anyway. http://blog.leafe.com/index.php/2016/04/22/distributed_data_nova/ Summary: we are

Re: [Openstack-operators] Maintenance

Maybe a result of the discussion can be a set of models (let's not go so far as to call them best pracices yet :) for how maintainance can be done at scale, perhaps solidifying the descriptions Jay has above with the user stories Tomi described in his initial note. This seems like an achievable

[openstack-announce] [release][kolla] kolla 2.0.0 release

We are glad to announce the release of: kolla 2.0.0: Kolla OpenStack Deployment For more details, please see below. 2.0.0 ^ This release is production ready for real world field deployments. This release has been tested on a 64 ndoe 13 TB ram 2600 core cluster as well as numerous co-beta

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

Sergey This is very interesting and exciting In fact, a few colleagues and myself actually plan to present at the Austin OS summit [1] around with the self-healing OpenStack Control Plane, a taste of which can be found here [2]. It’s a fully clustered, HA control plane PoC that we’ve put

Re: [Openstack-operators] Maintenance

On 04/14/2016 05:14 AM, Juvonen, Tomi (Nokia - FI/Espoo) wrote: As admin I want to know when host is ready to actions to be done by admin during the maintenance. Meaning physical resources are emptied. You are equating "host maintenance mode" with the end result of a call to `nova

Re: [openstack-dev] [Heat][Horizon] Liberty horizon and get_file workaround?

Based from stable policy, we don't backport new features [1]. The new feature also reads from an external URL, which I think might be too risky to add to stable branches. -Lin [1] http://docs.openstack.org/project-team-guide/stable-branches.html#review-guidelines On Fri, Apr 22, 2016 at 3:14

[openstack-dev] [trove] No weekly Trove meeting next week

As several of us will be at summit next week, there will be no weekly Trove meeting. The complete list of Trove design summit sessions can be found at [1]. There are also several talks about Trove [2] ... [5]. Thanks, -amrith [1]

[openstack-dev] [Congress] No meeting on April 27

No meeting for next week (April 27), since we'll be in Austin at the summit. We will send out an update about what happened during the summit next week. Tim __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] summit tools

On 04/20/2016 06:53 PM, Tony Breeds wrote: > On Wed, Apr 20, 2016 at 04:13:38PM +, Neil Jerram wrote: >> A couple of questions about our Austin-related planning tools... >> >> - Can one's calendar at >> https://www.openstack.org/summit/austin-2016/summit-schedule/#day=2016-04-25 >> be

[openstack-dev] [keystone] weekly meeting canceled on 4/26

as per usual, we will cancel the meeting the week of the summit - see you in austin! Steve __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [kolla] kolla-mesos development being scaled back

Hi folks, just posting a link to the email covering Mirantis position on it. http://lists.openstack.org/pipermail/openstack-dev/2016-April/093143.html On Wed, Apr 20, 2016 at 9:51 AM, Gerard Braad wrote: > On Wed, Apr 20, 2016 at 2:40 PM, Steven Dake (stdake)

[openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

Hi folks, I’ve been approached by multiple people asking questions about what is happening with Mirantis engineers activity around the kolla-mesos project we started and I do feel that I owe an explanation to the community. Indeed during the last few months we significantly reduced the amount of

[openstack-dev] [murano] No weekly meetings on April 26th and May 3d

Due to summit, long flights and holidays, that happen in Russia and Ukraine early in May there would be no weekly meetings on 26th and 3d. --  Kirill Zaitsev Software Engineer Mirantis, Inc__ OpenStack Development Mailing

[openstack-dev] [fuel] Weekly meeting canceled for 4/28

We discussed in the meeting next week that, we will cancel the next week's IRC meeting due to summit activities. The meeting will resume its regular schedule on May-5 -- -- Andrew Woodward Mirantis Fuel Community Ambassador Ceph Community

[openstack-dev] [oslo] No weekly meeting next week

Howday folks, Since there is a summit next week it is highly likely that we will not have a weekly meeting next week (since there just won't be enough people online) so I just wanted to make sure people don't show up (although folks that aren't going to the summit are welcome to still show up

Re: [Openstack-operators] Neutron DHCP agent local routes

Yes, there is an unfortunate possibility of confusion around the word 'subnet'. To some, that means a network segment, or VLAN, and to some that just means the specific IP subnet. Neutron takes the latter view, and treats multiple subnets as multiple IP ranges on the same VLAN (which Neutron calls

[openstack-dev] [Neutron] Neutron client and plan to transition to OpenStack client

Hi Neutrinos, During the Mitaka release the team sat together to figure out a plan to embrace the OpenStack client and supplant the neutron CLI tool. Please note that this does not mean we will get rid of the openstack-neutronclient repo. In fact we still keep python client bindings and keep the

Re: [openstack-dev] [trove][magnum][app-catalog][all] Build unified abstraction for all COEs

Thanks Kevin, much appreciated. I've added [trove] to the subject so it shows up on their mail filters. -amrith > -Original Message- > From: Fox, Kevin M [mailto:kevin@pnnl.gov] > Sent: Friday, April 22, 2016 1:11 PM > To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] Summit Core Party after Austin

The Vancouver core party was a fantastic opportunity to meet some very smart people and learn a lot about the projects they worked on. It was probably one of the most useful parts of the summit, certainly more so than the greasy marketing party, and arguably a much better use of developer time.

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

Thanks for the invite. I'll try my best to be there. :) As for the rest of the comments below, I think they are spot on, and I very much appreciate those features in Trove. It makes for a very nice way of dealing with databases. Thanks to the trove team for all the hard work put in to make it

Re: [openstack-dev] [Glance] Glare and future of artifacts in OpenStack.

On 04/22/2016 10:10 AM, Jay Pipes wrote: 3) On Slide 9, you have this in "future work (in Newton)": "Tasks (asynchronous workflows) support." Please, please, please NO. There is absolutely no reason to couple a service that operates on artifacts in an asynchronous fashion with a service that

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

Keith, I was with you all the way till your last sentence ... > -Original Message- > From: Keith Bray [mailto:keith.b...@rackspace.com] > Sent: Friday, April 22, 2016 11:53 AM > To: OpenStack Development Mailing List (not for usage questions) > >

Re: [openstack-dev] Summit Core Party after Austin

Excerpts from Thierry Carrez's message of 2016-04-21 09:22:53 -0700: > Michael Krotscheck wrote: > > So, HPE is seeking sponsors to continue the core party. The reasons are > > varied - internal sponsors have moved to other projects, the Big Tent > > has drastically increased the # of cores, and

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

Thanks Amirth… I’m glad to see it hasn’t changed much since I was involved with Trove in its early days. What you are describing makes sense, and I view it as an LCD for managing common things across the database types, not an LCD for the database interaction performed by the user/client

[Openstack-operators] [Fuel][MySQL][DLM][Oslo][DB][Trove][Galera][operators] Multi-master writes look OK, OCF RA and more things

[crossposting to openstack-operators@lists.openstack.org] On 04/22/2016 05:42 PM, Bogdan Dobrelya wrote: > [crossposting to openstack-operators@lists.openstack.org] > > Hello. > I wrote this paper [0] to demonstrate an approach how we can leverage a > Jepsen framework for QA/CI/CD pipeline for

Re: [openstack-dev] [Heat][Horizon] Liberty horizon and get_file workaround?

On 22/04/16 01:06, Jason Pascucci wrote: Hi, I wanted to add my yaml as new resources (via /etc/heat/environment.d/default.yaml, but we use some external files in the OS::Nova::Server personality section. I think you're describing this bug: https://bugs.launchpad.net/heat/+bug/1454401

[openstack-dev] [Fuel][MySQL][DLM][Oslo][DB][Trove][Galera][operators] Multi-master writes look OK, OCF RA and more things

[crossposting to openstack-operat...@lists.openstack.org] Hello. I wrote this paper [0] to demonstrate an approach how we can leverage a Jepsen framework for QA/CI/CD pipeline for OpenStack projects like Oslo (DB) or Trove, Tooz DLM and perhaps for any integration projects which rely on

Re: [openstack-dev] [Fuel] [Ci] Re-trigger by keyword in comment

Matthew, It's great that we have this test. But why to rerun it for no changes? It was executed only when a new patch was published for CR or CR was rebased. Now it is executed on "fuel:recheck". Agree, adding a plugin would be helpful. Aleksey Kasatkin On Fri, Apr 22, 2016 at 4:19 PM,

Re: [openstack-dev] Question about OpenStack Code of Conduct

On 04/21/2016 02:04 PM, Jeremy Stanley wrote: > On 2016-04-21 17:54:56 + (+), Adrian Otto wrote: >> Below is an excerpt from: >> https://www.openstack.org/legal/community-code-of-conduct/ >> >> "When we disagree, we consult others. Disagreements, both social >> and technical, happen all

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

to that. It is sorely needed. My way of trying to go there complicated the API too much. Let me know if I can help in any way, but you already knew that. Thanks, -amrith > -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Friday, April 22, 2016 11:19 AM >

Re: [openstack-dev] [Fuel][plugins] Changing role regex from '*' to ['/.*/'] breaks MOS compatibility

Thanks Ilya! We're testing and will be reporting back on monday. Simon On Fri, Apr 22, 2016 at 4:53 PM, Ilya Kutukov wrote: > Hello! > > I think your problem is related to the: > https://bugs.launchpad.net/fuel/+bug/1570846 > > Fix to stable/mitaka was commited 20/04/2016

[openstack-dev] [release][stable] networking-powervm 2.0.0 release (mitaka)

We are excited to announce the release of: networking-powervm 2.0.0: PowerVM Neutron ML2 Agent for OpenStack Neutron. This release is part of the mitaka stable release series. For more details, please see below. Changes in networking-powervm 1.0.0rc1..2.0.0

Re: [openstack-dev] [Security][Barbican][all] Bring your own key fishbowl sessions

> Thoughts? Is anyone interested in the pull model or actually implementing it? I say if the answer to that is no then only discuss the push model. Note that I am having a talk on BYOK on Tuesday at 11:15. My talk will go over provider key management, the push model, and the pull model. There

Re: [openstack-dev] More on the topic of DELIMITER, the Quota Management Library proposal

On 04/22/2016 07:51 AM, Amrith Kumar wrote: If it doesn’t make it harder, I would like to see if we can make the quota API take care of the ordering of requests. i.e. if the quota API is an extension of Jay’s example and accepts some data structure (dict?) with all the claims that a project

Re: [openstack-dev] [Glance] Glare and future of artifacts in OpenStack.

Mike, thanks for the update. Very helpful. I did have a couple concerns, though, from the slides... 1) On Slide 8, you have a bullet point: "Quoting. We want to implement powerful nested quota support, rather than have one global quota config." I do not believe that Glare should have

Re: [openstack-dev] [neutron] [nova] scheduling bandwidth resources / NIC_BW_KB resource class

Le 22/04/2016 16:14, Matt Riedemann a écrit : On 4/22/2016 2:48 AM, Sylvain Bauza wrote: Le 22/04/2016 02:49, Jay Pipes a écrit : On 04/20/2016 06:40 PM, Matt Riedemann wrote: Note that I think the only time Nova gets details about ports in the API during a server create request is when

Re: [openstack-dev] [tc] Leadership training dates - please confirm attendance

On Thu, Apr 21, 2016 at 10:42 AM, Doug Hellmann wrote: > > Excerpts from Colette Alexander's message of 2016-04-21 08:07:52 -0700: > > > > > Hi everyone, > > > > Just checking in on this - if you're a current or past member of the TC and > > haven't yet signed up on the

Re: [openstack-dev] [Fuel][plugins] Changing role regex from '*' to ['/.*/'] breaks MOS compatibility

Hello! I think your problem is related to the: https://bugs.launchpad.net/fuel/+bug/1570846 Fix to stable/mitaka was commited 20/04/2016 https://review.openstack.org/#/c/307658/ Could you, please, try to apply this patch and reply does it help or not. On Fri, Apr 22, 2016 at 5:40 PM, Guillaume

[openstack-dev] [Fuel][plugins] Changing role regex from '*' to ['/.*/'] breaks MOS compatibility

Hello, deployment_tasks.yaml for the fuel-plugin-lma-collector plugin has this task definition: - id: lma-aggregator type: puppet version: 2.0.0 requires: [lma-base] required_for: [post_deployment_end] role: '*' parameters: puppet_manifest: puppet/manifests/aggregator.pp

[openstack-dev] [Neutron][ML2][API]Binding a port to multiple hosts

After some discussion how portbinding handling could be improved during live migration, the following idea came up: Why not bind a port to both, the source and the target host during migration? This would allow us to set the portbinding for the target already in pre_live_migration. Doing so, we

Re: [openstack-dev] [neutron] [nova] scheduling bandwidth resources / NIC_BW_KB resource class

On 4/22/2016 2:48 AM, Sylvain Bauza wrote: Le 22/04/2016 02:49, Jay Pipes a écrit : On 04/20/2016 06:40 PM, Matt Riedemann wrote: Note that I think the only time Nova gets details about ports in the API during a server create request is when doing the network request validation, and that's

Re: [openstack-dev] [magnum][app-catalog][all] Build unified abstraction for all COEs

On Thu, Apr 21, 2016 at 9:30 PM, Fox, Kevin M wrote: > +1. > > From: Hongbin Lu [hongbin...@huawei.com] > Sent: Thursday, April 21, 2016 7:50 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re:

Re: [openstack-dev] Summit Core Party after Austin

On 18:57 Apr 21, Thierry Carrez wrote: > Thierry Carrez wrote: > >[...] > >I think it's inappropriate because it gives a wrong incentive to become > >a core reviewer. Core reviewing should just be a duty you sign up to, > >not necessarily a way to get into a cool party. It was also a bit >

Re: [openstack-dev] [Fuel] [Ci] Re-trigger by keyword in comment

Aleksey, actually I want to extend the test group we run there. Many changes coming out of nailgun are actually creating BVT failures that can only be prevented by such tests. One such extension would be adding a plugin to the deployment to ensure that basic plugins are still deployable. I'm ok

Re: [Openstack-operators] Neutron DHCP agent local routes

But if the subnets are on the same VLAN it should work. That's what that patch is designed for. There is (currently) an assumption in Neutron that subnets in the same network are on the same L2 segment. So if a VM wants to communicate with a VM in another subnet on the same network, it can cut out

Re: [openstack-dev] [Fuel] [Ci] Re-trigger by keyword in comment

Hi Dmitry, Thank you for update. Is it intended that master.fuel-web.pkgs.ubuntu.review_fuel_web_deploy job for code requests to fuel-web runs at every recheck now? Before the change it was executed for new

Re: [openstack-dev] [neutron] use hostname as nameserver when creating subnet

Sun zhengnan wrote: Hi all Can I use hostname as a nameserver when creating or updating a subnet? From API perspective, yes... I noticed that both ip and hostname are checked in neutron/api/attributes.py with _validate_nameservers. But only ip address is allowed in

[openstack-dev] [TripleO] TripleO UI Demo

Hello all, I've created a demo video which shows latest changes in TripleO UI. You can watch it here: https://youtu.be/1Lc04DKGxCg -- Jirka __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [puppet] Summit etherpads + schedule

Hi, The schedule & etherpads for Puppet OpenStack sessions are documented here: https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Puppet_OpenStack During the summit, we won't do the weekly meeting, the next one is May 3rd. Have a safe tip and see you next week! -- Emilien Macchi

Re: [openstack-dev] [TripleO] Change 247669: Ceph Puppet: implement per-pool parameters:

On Fri, Apr 22, 2016 at 3:51 AM, Shinobu Kinjo wrote: > Hi TripleO Team, > > If you could take care of ${subject}, it would be nice. > > [1] https://review.openstack.org/#/c/247669 > Well, the patch is in merge conflict, and has negative review from Cyril. I would suggest

  1   2   >