Re: [openstack-dev] [nova] Proposal to add Alex Xu to nova-core

2015-11-13 17:36 GMT+08:00 John Garbutt : > On 6 November 2015 at 15:32, John Garbutt wrote: > > Hi, > > > > I propose we add Alex Xu[1] to nova-core. > > > > Over the last few cycles he has consistently been doing great work, > > including some

Re: [openstack-dev] [nova] Proposal to add Sylvain Bauza to nova-core

On 6 November 2015 at 15:32, John Garbutt wrote: > Hi, > > I propose we add Sylvain Bauza[1] to nova-core. > > Over the last few cycles he has consistently been doing great work, > including some quality reviews, particularly around the Scheduler. > > Please respond with

Re: [openstack-dev] Last sync from oslo-incubator

Davanum Srinivas wrote: > A long time ago, oslo-incubator had a lot of code, we have made most > of the code to oslo.* libraries. There's very little code left and > we'd like to stop hosting common code in oslo-incubator repository. We > encourage everyone to adopt the code they have in their

Re: [openstack-dev] [puppet] ::db classes

On 11/11/2015 03:50 PM, Clayton O'Neill wrote: > I discovered this issue last night and opened a bug on it ( > https://bugs.launchpad.net/puppet-tuskar/+bug/1515273). > > This effects most of the modules, and the short version of it is that the > defaults in all the ::db classes are wrong for

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Armando M. wrote: On 12 November 2015 at 20:24, Sean M. Collins wrote: On Thu, Nov 12, 2015 at 05:55:51PM EST, Ihar Hrachyshka wrote: > I also believe that the first step to get the job set is making neutron own > its grenade future, by migrating to

Re: [openstack-dev] [glance] [nova] Image Signature Verification

On Thu, Nov 12, 2015 at 08:30:53PM +, Poulos, Brianna L. wrote: > Hello, > > There has recently been additional discussion about the best way to handle > image signature verification in glance and nova [1]. There are two > options being discussed for the signature (the examples below using >

Re: [openstack-dev] Linux kernel IPv4 configuration during the neutron installation

Yes,I don't understand why Neutron needs enable ip_forward and disable RPF. And I also don't understand where the neutron need this config during the instance connect to the extrernal network. I read the neutron code, found when the L3 agent creating, it needs the ip_forward config,but i'm not

Re: [openstack-dev] [neutron][vpnaas] VPNaaS project status

Thanks for everything you've done for VPNaaS, Paul! Your help and guidance was (and is) always very helpful. On Thu, Nov 12, 2015 at 5:56 PM, Paul Michali wrote: > Neutron community, > > During the past several releases, while leading the VPNaaS project, I've > seen many great

[openstack-dev] [Fuel] [Fuel UI] Support of separate provisioning is blocked by backend issues

Hi fuelers, Currently Fuel UI team is working on blueprint [1] to give Fuel UI user an ability to launch provisioning of environment nodes separately from deployment (without choosing particular nodes for now). In the process we were faced with the following issues. Some of them block the

Re: [openstack-dev] [neutron][qos][fwaas] service groups vs. traffic classifiers

Paul Carver wrote: On 11/12/2015 3:50 PM, Ihar Hrachyshka wrote: All I am saying is that IF we merge some classifier API into neutron core and start using it for core, non-experimental, features, we cannot later move to some newer version of this API [that you will

Re: [openstack-dev] [puppet] Creating puppet-keystone-core and proposing Richard Megginson core-reviewer

Congrats Rich ! On 11/04/2015 05:10 PM, Emilien Macchi wrote: > > On 11/03/2015 03:56 PM, Matt Fischer wrote: >> Sorry I replied to this right away but used the wrong email address and >> it bounced! >> >>> I've appreciated all of richs v3 contributions to keystone. +1 from me. > 2 positives

Re: [openstack-dev] [nova] Proposal to add Sylvain Bauza to nova-core

Le 13/11/2015 10:36, John Garbutt a écrit : On 6 November 2015 at 15:32, John Garbutt wrote: Hi, I propose we add Sylvain Bauza[1] to nova-core. Over the last few cycles he has consistently been doing great work, including some quality reviews, particularly around the

Re: [openstack-dev] [nova] Proposal to add Alex Xu to nova-core

On 6 November 2015 at 15:32, John Garbutt wrote: > Hi, > > I propose we add Alex Xu[1] to nova-core. > > Over the last few cycles he has consistently been doing great work, > including some quality reviews, particularly around the API. > > Please respond with comments, +1s,

Re: [openstack-dev] [api] consolidate IRC change with #openstack-sdk?

Cool with me. On 11/13/2015 07:58 AM, Sean Dague wrote: The #openstack-api IRC channel is quite quiet most days. As such it's not something that people are regularly checking in on, or often forget about (I know I've been guilty of that). Plus we don't always have the right people in a

Re: [openstack-dev] [neutron][upgrade] new 'all things upgrade' subteam

Hi Ihar, same for me, all options are ok! cheers, Rossella On 11/12/2015 11:00 PM, Martin Hickey wrote: Hi Ihar, Any of those options would suit me, thanks. Cheers, Martin From: Ihar Hrachyshka To: "OpenStack Development Mailing List (not for usage

[openstack-dev] [freezer] Proposal to add Pierre-Arthur Mathieu to freezer-core

Hi All, I'd like to propose Pierre as core in Freezer. Pierre dedication was amazing on code review, documentation, architectural decision and overall greatly improving the quality of the Freezer Project. Freezer wouldn't be to the point where it is without Pierre. Please respond with

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

Excerpts from Thierry Carrez's message of 2015-11-13 15:10:24 +0100: > So.. quick summary of this thread so far. > > (-) > * Not enough work to warrant a designated "team", now that the work is > decentralized and the cats are mostly herding themselves > * The change is unlikely to bring a

[openstack-dev] [freezer] Proposal to add Eldar Nugaev to freezer-core

Hi All, I'd like to propose Eldar as core in Freezer, as his help, dedication and contribution was incredible for the last 6 months. Eldar not only worked on improving performances overall, but also on making our code more portable, abstracted and implemented outstanding features like the

[openstack-dev] [midonet] Announcing new mailing list topic: MidoNet

Hello everyone, This is just a heads up that Thierry Carrez was so kind as to add a new topic to the openstack-dev mailing list for the MidoNet dev team. We currently use our own mailing list [1] but plan to move our discussions here rather sooner than later. Last chance to adjust your filters!

Re: [openstack-dev] [fuel] Using upstream packages & modules

Hi, Alex! Good to know someone is doing that. One question about Your initiative: Are You going to reimplement all MOS HA features? Seems first implementation of 'upstream on Fuel' will be HA-less. On Thu, Nov 12, 2015 at 1:51 AM, Alex Schultz wrote: > On Tue, Nov 10,

Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing ongate.

I am going to share something that might be off the topic a bit. Yesterday, I was pulled to the #openstack-infra channel to participant a discussion, which is related to the atomic image download in Magnum. It looks the infra team is not satisfied with the large image size. In particular, they

[openstack-dev] [telemetry][aodh][ceilometer][gnocchi] the story of telemetry

hi, you may have noticed that changes are in motion and an extra telemetry tag being floated around. the following is your coles|cliff|spark notes on what you need to know. -- background -- three years ago, the ceilometer project was created to tackle the billing of cloud environments.

[openstack-dev] [designate] Records for floating addresses are not removed when an instance is removed

When removing an instance (with one floating address assigned) in Horizon, designate-sink only receives an event for instance removal. As a result, only the instance is removed but the floating addresses records are not removed. I'm not sure if it's a bug in openstack (I guess that it should also

Re: [openstack-dev] [freezer] Proposal to add Pierre-Arthur Mathieu to freezer-core

+1 :) From: Marzi, Fausto Sent: Friday, November 13, 2015 4:44 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [freezer] Proposal to add Pierre-Arthur Mathieu to freezer-core Hi All, I’d like to propose Pierre as core

Re: [openstack-dev] [neutron][qos][fwaas] service groups vs. traffic classifiers

German wrote: Ihar, The Service Group API will be added to FWaaS only and remain experimental in M. If the community finds it useful for other areas it can be added to Neutron core once it is matures. I think incubating it inside FWaaS will give us the

Re: [openstack-dev] [nova] Backlog Specs: a way to send requirements to the developer community

On 11/12/2015 12:48 PM, Steve Gordon wrote: - Original Message - From: "John Garbutt" To: maishsk+openst...@maishsk.com [SNIP] On 14 May 2015 at 19:52, Maish Saidel-Keesing wrote: Can we please have this as a default template and the

Re: [openstack-dev] [neutron][qos][fwaas] service groups vs. traffic classifiers

Ihar, The Service Group API will be added to FWaaS only and remain experimental in M. If the community finds it useful for other areas it can be added to Neutron core once it is matures. I think incubating it inside FWaaS will give us the velocity to iterate quickly and once it matures a

Re: [openstack-dev] [freezer] Proposal to add Eldar Nugaev to freezer-core

+1 :) From: Marzi, Fausto Sent: Friday, November 13, 2015 4:39 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [freezer] Proposal to add Eldar Nugaev to freezer-core Hi All, I’d like to propose Eldar as core in

Re: [openstack-dev] [nova][bugs] Weekly Status Report

Below are the stats of the week "Mitaka R-21". Changes to the previous week are shown in parantheses behind the current numbers. For example, "28 (+9)" means we have 28 bugs in that category with an increase of 9 bugs comparing to the previous week. Stats = New bugs which are *not* assigned

[openstack-dev] [fuel] Advanced PXE provisioning notes

Forgot about tags, sorry. -- With best regards, Vladimir Eremin, Fuel Deployment Engineer, Mirantis, Inc. > On Nov 13, 2015, at 5:13 PM, Vladimir Eremin wrote: > > Hi folks, > > As you know, to speed up provisioning stage we could use HTTP for downloading > kernel

Re: [openstack-dev] [api] consolidate IRC change with #openstack-sdk?

On Fri, Nov 13, 2015 at 6:58 AM, Sean Dague wrote: > I'd like to propose we drop the channel entirely and make #openstack-sdk > the home of API working group conversations. That's where all the > openstackclient, openstackclientconfig, and sdk conversations are > happening. It's

[openstack-dev] [all][glance][api][infra][defcore] last call for feedback on image import

There was a lot of great pre-summit discussion on the Glance spec for image import refactoring, and more lively discussion at the summit, but it's been very quiet since I posted patch set 5 last week. Please take a few minutes to look over the revised spec and let the Glance community know

Re: [openstack-dev] [fuel] Using upstream packages & modules

On Fri, Nov 13, 2015 at 10:17 AM, Alexander Kostrikov wrote: > Hi, Alex! > Good to know someone is doing that. > > One question about Your initiative: > Are You going to reimplement all MOS HA features? > Seems first implementation of 'upstream on Fuel' will be HA-less. >

Re: [openstack-dev] [fuel] Advanced PXE provisioning notes

Hi Sean, Yes, iPXE could be one-to-rule-them-all replacement, because of HTTP, IPv6 and UEFI support. lpxelinux is good, but for one-line enhancements. -- With best regards, Vladimir Eremin, Fuel Deployment Engineer, Mirantis, Inc. > On Nov 13, 2015, at 6:17 PM, Sean Collins

Re: [openstack-dev] Last sync from oslo-incubator

Excerpts from Davanum Srinivas (dims)'s message of 2015-11-13 07:44:26 -0500: > Hear Hear! Thierry. Many many thanks to everyone who made this possible. > > -- Dims Indeed, as Thierry said, it has truly been a group effort, spanning many cycles and involving many, many contributors. Thank you

Re: [openstack-dev] [kolla] Proposing Michal Rostecki for Core Reviewer (nihilfer on IRC)

+1 Nice work Michal. -Ryan - Original Message - From: "Sam Yaple" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Friday, November 13, 2015 1:15:05 PM Subject: Re: [openstack-dev] [kolla] Proposing Michal

Re: [openstack-dev] [neutron][vpnaas] VPNaaS project status

Paul, I echo the prior comments. Your hard work and persistence in getting the recent new features written, as well as your review suggestions are very much appreciated! Thanks, Al From: Paul Michali [mailto:p...@michali.net] Sent: Thursday, November 12, 2015 8:56 AM To: OpenStack

Re: [openstack-dev] [fuel] Advanced PXE provisioning notes

[sorry for the weirdness - this was cross-posted to two lists] On Fri, Nov 13, 2015 at 11:30:53AM EST, Vladimir Eremin wrote: > Hi Sean, > > Yes, iPXE could be one-to-rule-them-all replacement, because of HTTP, IPv6 > and UEFI support. > OK - based on your research it sounds like iPXE would

[openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

Hi All, The following API guidelines are ready for cross project review. They will be merged on Nov. 20 if there's no further feedback. 1. Add introduction for API micro version guideline https://review.openstack.org/#/c/187112/ 2. Add description of pagination parameters

[openstack-dev] [puppet] A note about composite namevar integration for puppet-keystone module.

Hi, A lot of changes has taken place under the hood of those three providers in the keystone module: - keystone_user; - keystone_tenant; - keystone_user_role; This note will highlight the changes. This has two goals: - make a broader range of puppet users aware of the change and the new

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On Fri, Nov 13, 2015 at 07:42:12AM EST, Sean Dague wrote: > Ok, I top responded with the details of the job, honestly I think it's > just a project-config change to get up and running, and then hacking at > the bugs that fall out. Thanks - that was super helpful. I'm thinking of working on the

Re: [openstack-dev] [designate] Records for floating addresses are not removed when an instance is removed

You can do it like we did for juno Designate as covered in our Vancouver talk start about 21 minutes: https://www.youtube.com/watch?v=N8y51zqtAPA We've not ported the code to Kilo or Liberty yet but the approach may still work. On Fri, Nov 13, 2015 at 9:49 AM, Jaime Fernández

Re: [openstack-dev] [kolla] Proposing Michal Rostecki for Core Reviewer (nihilfer on IRC)

> On 12/11/15 08:41, Steven Dake (stdake) wrote: > > Hey folks, > > Its been awhile since we have had a core reviewer nomination, but I > really feel like Michal has the right stuff. If you look at the 30 day > stats for kolla[1] , he is #3 in reviews (70 reviews) with 6 commits in > a 30 day

Re: [openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

On Nov 13, 2015, at 12:55 PM, Everett Toews wrote: >> Specifically this patch, or the ones dependent on it? Because this specific >> patch doesn't actually say anything. > > Specifically this patch. Just looking to initially move forward in some small > way on

Re: [openstack-dev] [freezer] Proposal to add Eldar Nugaev to freezer-core

+1 ;) From: Marzi, Fausto Sent: 13 November 2015 16:39 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [freezer] Proposal to add Eldar Nugaev to freezer-core Hi All, I'd like to propose Eldar as core in Freezer, as his help, dedication and contribution

Re: [openstack-dev] [freezer] Proposal to add Pierre-Arthur Mathieu to freezer-core

+1 ;) From: Marzi, Fausto Sent: 13 November 2015 16:45 To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [freezer] Proposal to add Pierre-Arthur Mathieu to freezer-core Hi All, I'd like to propose Pierre as core in Freezer. Pierre dedication was amazing

Re: [openstack-dev] [puppet] about $::os_service_default

Yanis Guenane wrote: > > On 11/03/2015 02:57 PM, Emilien Macchi wrote: >> I'm seeing a lot of patches using the new $::os_service_default. >> >> Please stop trying to using it at this time. The feature is not stable >> yet and we're testing it only for puppet-cinder module. >> I've heard Yanis

[openstack-dev] [openstack][devstack]Openstack devstack installation failing.

Hi Folks, I have been trying to install devstack on Ubuntu 14.04 for the last 5 times but I am still getting the following error message while it is Initializing tempest: *ERROR (ConnectionRefused): Unable to establish connection to http://127.0.0.1:8774/v2.1/ * So,

Re: [openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

> On Nov 13, 2015, at 12:01 PM, John Dickinson wrote: > > > > On 13 Nov 2015, at 9:42, Everett Toews wrote: > >> Hi All, >> >> The following API guidelines are ready for cross project review. They will >> be merged on Nov. 20 if there's no further feedback. >> >> 1. Add

Re: [openstack-dev] [kolla] Proposing Michal Rostecki for Core Reviewer (nihilfer on IRC)

Michal does great patches and is very receptive to feedback. +1 for me. We may need to call him Michal2 though. Might get confusing to have multiple Michals on the team. Sam Yaple On Thu, Nov 12, 2015 at 9:23 AM, Paul Bourke wrote: > +1 > > > On 12/11/15 08:41, Steven

Re: [openstack-dev] [neutron][vpnaas] VPNaaS project status

Thanks folks. I have gone through all of the "open" VPN bugs and commented/updated them. The Wiki was updated with references to some of the LP bugs of particular interest. Regards, PCM (pc_m) On Fri, Nov 13, 2015 at 3:42 AM Elena Ezhova wrote: > Thanks for everything

Re: [openstack-dev] [all][api] New API Guidelines Ready for Cross Project Review

On 13 Nov 2015, at 9:42, Everett Toews wrote: > Hi All, > > The following API guidelines are ready for cross project review. They will be > merged on Nov. 20 if there's no further feedback. > > 1. Add introduction for API micro version guideline > https://review.openstack.org/#/c/187112/

Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing ongate.

Excerpts from Hongbin Lu's message of 2015-11-13 16:05:24 +: > I am going to share something that might be off the topic a bit. > > Yesterday, I was pulled to the #openstack-infra channel to participant a > discussion, which is related to the atomic image download in Magnum. It looks > the

Re: [openstack-dev] [Magnum][Testing] Reduce Functional testingongate.

We discussed this topics at the last design summit and a BP has been opened to track the effort: https://blueprints.launchpad.net/magnum/+spec/ubuntu-image-build Ton, From: Gregory Haynes To: openstack-dev Date: 11/13/2015 10:03

Re: [openstack-dev] [puppet] about $::os_service_default

This work is already being done by Clayton (and to a lesser extent me). >From the openstack modules POV it mainly involves moving the packaging code into a separate place [1][2] and then integrating with puppet-os_docker[3]. This os_docker work is only done for designate and heat and of course

Re: [openstack-dev] [kolla] Proposing Michal Rostecki for Core Reviewer (nihilfer on IRC)

+1 :) Jeff Peeler schreef op 2015-11-13 19:51: On 12/11/15 08:41, Steven Dake (stdake) wrote: Hey folks, Its been awhile since we have had a core reviewer nomination, but I really feel like Michal has the right stuff. If you look at the 30 day stats for kolla[1] , he is #3 in reviews (70

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 11/13/2015 01:16 PM, Sean M. Collins wrote: > On Fri, Nov 13, 2015 at 07:42:12AM EST, Sean Dague wrote: >> Ok, I top responded with the details of the job, honestly I think it's >> just a project-config change to get up and running, and then hacking at >> the bugs that fall out. > > Thanks -

Re: [openstack-dev] [neutron][qos][fwaas] service groups vs. traffic classifiers

On Fri, Nov 13, 2015 at 01:53:49AM EST, Paul Carver wrote: > On 11/3/2015 1:03 PM, Sean M. Collins wrote: > >Anyway, the code is currently up on GitHub - I just threw it on there > >because I wanted to scratch my hacking itch quickly. > > > >https://github.com/sc68cal/neutron-classifier > > > >

Re: [openstack-dev] [puppet] about $::os_service_default

What Matt said. I think we don’t need to explicitly support people that aren’t using distribution packages, we just want to try to avoid making harder things harder. I don’t see a need to go out of our way to support it. Anyone that isn’t using distro packages should be able to figure out how

Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On 11/12/2015 7:40 AM, Alan Pevec wrote: This is a call to stable-maint teams for Nova, Keystone, Glance, Cinder, Neutron, Horizon, Heat, Ceilometer, Trove and Sahara to review open stable/juno changes[2] and approve/abandon them as appropriate. CCing CPLs listed in

Re: [openstack-dev] [stable][all] Keeping Juno "alive" for longer.

On 9 November 2015 at 14:42, Sean Dague wrote: > > So lets figure out where the snags are. I'm pretty uninterested in > threads that just scream LTS without a list of upgrade bugs that have > been filed to describe why rapid upgrade isn't the right long term > solution. I agree

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 13 November 2015 at 11:46, Sean Dague wrote: > On 11/13/2015 01:16 PM, Sean M. Collins wrote: > > On Fri, Nov 13, 2015 at 07:42:12AM EST, Sean Dague wrote: > >> Ok, I top responded with the details of the job, honestly I think it's > >> just a project-config change to get up

[openstack-dev] [fuel] Using alternative OpenStack packages with Fuel

Hey folks, Based on my previous email, I promised to send out a note this week about this topic. My original email also included testing out the development version of the upstream puppet modules. I was able to get an environment working with the master branches of the OpenStack Puppet modules

Re: [openstack-dev] [stable][all] Keeping Juno "alive" for longer.

On Fri, Nov 06, 2015 at 05:15:18PM +1100, Tony Breeds wrote: > Hello all, > > I'll start by acknowledging that this is a big and complex issue and I > do not claim to be across all the view points, nor do I claim to be > particularly persuasive ;P > > Having stated that, I'd like to seek

Re: [openstack-dev] [kolla] Proposing Michal Rostecki for Core Reviewer (nihilfer on IRC)

+1! On Sat, Nov 14, 2015 at 4:32 AM, Harm Weites wrote: > +1 :) > > Jeff Peeler schreef op 2015-11-13 19:51: > >> On 12/11/15 08:41, Steven Dake (stdake) wrote: >>> >>> Hey folks, >>> >>> Its been awhile since we have had a core reviewer nomination, but I >>> really feel like

[openstack-dev] Regarding OVN project and integration with SFC

Hi Russell, Has the OVN code been released in Liberty? If not when is it planned for release? Will it replace existing OVS Driver and OVS Agent or it will provide an alternative path of programming the OVS? It is on the networking-sfc project roadmap to support OVN integration with SFC. We

Re: [openstack-dev] [horizon][keystone]

David, FYI, I've submitted a patch to enable registering Identity Providers in horizon: https://review.openstack.org/#/c/244991/ The next logical step for this is to look at the IdP mapping. I can follow-up on the work by Anton to add that support for horizon. Can you send me the code and

Re: [openstack-dev] [neutron][sfc] How could an L2 agent extension access agent methods ?

Ihar, See inline. - Louis -Original Message- From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] Sent: Thursday, November 12, 2015 1:12 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron][sfc] How could an L2 agent extension

Re: [openstack-dev] Linux kernel IPv4 configuration during the neutron installation

Could you share the exact place of the installation guide? I would like to check it. Are you talking about the network node? I think these settings are required when you configure a network node without network namespace. If we use network namespace in a network node, I don't think we need

Re: [openstack-dev] Linux kernel IPv4 configuration during the neutron installation

This installation guide is: http://docs.openstack.org/juno/install-guide/install/yum/content/neutron-network-node.html#treeDiv In Centos 7,controle node and network node in one machine.my output is: [root@controller-59 ~]# cat /proc/sys/net/ipv4/ip_forward 1 [root@controller-59 ~]# cat

Re: [openstack-dev] [HA] weekly High Availability meetings on IRC start next Monday

Hi, United Kingdom/London has UTC+1 in summer. Thus I use Ghana/Accra which is pure UTC all year. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Fri, Nov 13, 2015 at 1:23 AM, Adam Spiers wrote: > Sergii Golovatiuk wrote: > > > >

Re: [openstack-dev] [puppet] about $::os_service_default

On 11/03/2015 02:57 PM, Emilien Macchi wrote: > I'm seeing a lot of patches using the new $::os_service_default. > > Please stop trying to using it at this time. The feature is not stable > yet and we're testing it only for puppet-cinder module. > I've heard Yanis found something that is not

Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

> Speaking of your "hacky" patch: yes and no. It makes the gate passing, > it doesn't change the code itself. For most people, this will work fine. > > The right way to do it, would be to create a juno branch for doa and > cap requirements there. > > How to do this? Is there a procedure to request

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 11/13/2015 04:08 AM, Ihar Hrachyshka wrote: > Armando M. wrote: > >> >> >> On 12 November 2015 at 20:24, Sean M. Collins wrote: >> On Thu, Nov 12, 2015 at 05:55:51PM EST, Ihar Hrachyshka wrote: >> > I also believe that the first step to get the job set

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Sean Dague wrote: On 11/13/2015 04:08 AM, Ihar Hrachyshka wrote: Armando M. wrote: On 12 November 2015 at 20:24, Sean M. Collins wrote: On Thu, Nov 12, 2015 at 05:55:51PM EST, Ihar Hrachyshka wrote: I also believe that the first step

[openstack-dev] [api] consolidate IRC change with #openstack-sdk?

The #openstack-api IRC channel is quite quiet most days. As such it's not something that people are regularly checking in on, or often forget about (I know I've been guilty of that). Plus we don't always have the right people in a conversation to make a decision. I'd like to propose we drop the

Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On 10/11/15 16:11 +0100, Alan Pevec wrote: Hi, while we continue discussion about the future of stable branches in general and stable/juno in particular, I'd like to execute the current plan which was[1] 2014.2.4 (eol) early November, 2015. release manager: apevec Iff there's enough folks

Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On 11/13/15, 3:23 PM, "Flavio Percoco" wrote: >On 10/11/15 16:11 +0100, Alan Pevec wrote: >>Hi, >> >>while we continue discussion about the future of stable branches in >>general and stable/juno in particular, I'd like to execute the current >>plan which was[1] >> >>2014.2.4

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

So.. quick summary of this thread so far. (-) * Not enough work to warrant a designated "team", now that the work is decentralized and the cats are mostly herding themselves * The change is unlikely to bring a meaningful improvement to the situation, or sudden new resources (+) * An empowered

Re: [openstack-dev] [Fuel] API services available on public VIP

Adam I think, the answer is realtively simple - if user does not want to expose those APIs, he can easily configure his infra to filter this traffic. We just need to mention this in Ops Guide. On Fri, Nov 13, 2015 at 4:02 PM, Adam Heczko wrote: > Hello fuelers, > > today

[openstack-dev] Advanced PXE provisioning notes

Hi folks, As you know, to speed up provisioning stage we could use HTTP for downloading kernel and initramfs. There are 3 options to do this: lpxelinux, iPXE (which is successor/fork of gPXE) and GRUB 2, which we were assessed during my work in Yandex and I’d like to share some experience. In

Re: [openstack-dev] [api] consolidate IRC change with #openstack-sdk?

Please note that should be #openstack-sdks (plural) ! > On Nov 13, 2015, at 6:58 AM, Sean Dague wrote: > > The #openstack-api IRC channel is quite quiet most days. As such it's > not something that people are regularly checking in on, or often forget > about (I know I've been

Re: [openstack-dev] [stable][neutron] Kilo is 'security-supported'. What does it imply?

Thierry Carrez wrote: Carl Baldwin wrote: - StableBranch page though requires that we don’t merge non-critical bug fixes there: "Only critical bugfixes and security patches are acceptable” Seems a little premature for Kilo. It is little more than 6 months old. Some

Re: [openstack-dev] [api] consolidate IRC change with #openstack-sdk?

As a -sdks regular, I wouldn't mind some of the API folks crashing the channel :) If it makes sense, then why not. There are already some folks that are involved in both efforts (Everett). Steve From: Sean Dague To: "OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 11/12/2015 02:41 PM, Korzeniewski, Artur wrote: > Hi Sean, > > I’m interested in introducing to Neutron the multinode partial upgrade > job in Grenade. > > > > Can you explain how multinode is currently working in Grenade and how > Nova is doing the partial upgrade? We're hopefully a

Re: [openstack-dev] Last sync from oslo-incubator

Hear Hear! Thierry. Many many thanks to everyone who made this possible. -- Dims On Fri, Nov 13, 2015 at 4:44 AM, Thierry Carrez wrote: > Davanum Srinivas wrote: >> A long time ago, oslo-incubator had a lot of code, we have made most >> of the code to oslo.* libraries.

[openstack-dev] [Fuel] API services available on public VIP

Hello fuelers, today I'd like to raise a questions about Fuel deployment practice related to Public (external) network. Current approach is to expose by default over public IP openstack API endpoints like nova, cinder, glance, neutron etc. These API services are exposed through HAProxy with TLS

[openstack-dev] [stable][neutron] upper constraints for stable/liberty

Hi Sachi and all, I was recently looking into how stable/liberty branches are set for neutron in terms of requirements caps, and I realized that we don’t have neither version caps nor upper constraints applied to unit test jobs in stable/liberty gate. We have -constraints targets defined