Re: [openstack-dev] [neutron][lbaas] Proposing Michael Johnson for neutron-lbaas core team

And then they were 6 =D> -Sam. -Original Message- From: Doug Wiegley [mailto:doug...@parksidesoftware.com] Sent: Thursday, September 17, 2015 1:34 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron][lbaas] Proposing Michael Johnson for

Re: [openstack-dev] [Magnum] API response on k8s failure

Hi Ryan, There is a bug opened with a similar failure symptom, although I am not sure if the cause is the same: https://bugs.launchpad.net/magnum/+bug/1481889 Trying to use kubectl to deploy the V1 manifest, I get this error message: Error: unable to recognize "redis-master.yaml": no object

[openstack-dev] [Glance] PTL candidacy

Hello everyone, I would like to herewith propose my candidacy for the role of Glance PTL for the Mitaka release cycle. I. Personal Commitment I am a full time upstream OpenStacker at IBM and have recently transitioned into this role with the condition that I will be given 100% time to focus on

[openstack-dev] [dragonflow] Low OVS version for Ubuntu

Hi all, I tried to run devstack to deploy dragonflow, but I failed with lower OVS version. I used Ubuntu 14.10 server, but the official package of OVS is 2.1.3 which is much lower than the required version 2.3.1+? So, can anyone provide a Ubuntu repository that contains the correct OVS

[openstack-dev] [neutron] Please help review this RFE

Hi Neutron folks, I'd like to introduce a pure python-driven network configuration library to Neutron. A discussion just started in the RFE ticket [1]. I'd like to get feedback on this proposal. [1]: https://bugs.launchpad.net/neutron/+bug/1492714 Take a look and let me know your thoughts. --

Re: [openstack-dev] [puppet] service default value functions

On 09/16/2015 09:39 PM, Emilien Macchi wrote: > > On 09/16/2015 12:53 PM, Alex Schultz wrote: >> Hey puppet folks, >> >> Based on the meeting yesterday[0], I had proposed creating a parser >> function called is_service_default[1] to validate if a variable matched >> our agreed upon value of ''.

Re: [openstack-dev] [dragonflow] Low OVS version for Ubuntu

Hello Li Ma, Dragonflow uses OpenFlow1.3 to communicate with OVS and thats why we need OVS 2.3.1. As suggested you can build it from source. For Fedora 21 OVS2.3.1 is part of the default yum repository. You can ping me on IRC (gsagie at freenode) if you need any additional help how to compile

Re: [openstack-dev] [neutron] RFE process question

A reasonable user story. Other than tag, a common description field for Neutron resources is also usable. I submitted a RFE bug for review: https://bugs.launchpad.net/neutron/+bug/1496705 __ OpenStack Development Mailing

[openstack-dev] [oslo][oslo.config] Reloading configuration of service

Hi Doug, > Rather than building hooks into oslo.config, why don't we build them > into the thing that is catching the signal. That way the app can do lots > of things in response to a signal, and one of them might be reloading > the configuration. Hm... Yes... It is really stupid idea to put

Re: [openstack-dev] [dragonflow] Low OVS version for Ubuntu

On Thursday 17 September 2015 12:22 PM, Li Ma wrote: Hi all, I tried to run devstack to deploy dragonflow, but I failed with lower OVS version. I used Ubuntu 14.10 server, but the official package of OVS is 2.1.3 which is much lower than the required version 2.3.1+? So, can anyone provide a

Re: [openstack-dev] [Fuel] Bugs which we should accept in 7.0 after Hard Code Freeze

Hi, I'd like to ask for fixing these security related bugs in stable/7.0 branch: https://bugs.launchpad.net/fuel/+bug/1496407 https://bugs.launchpad.net/fuel/+bug/1488732 Both are fuel-library related tasks, it is Apache2 and NTPD configuration lifting. Thanks, Adam On Tue, Sep 15, 2015 at

Re: [openstack-dev] [all][gate] grende jobs failing.

On Thu, Sep 17, 2015 at 03:34:30PM +1000, Tony Breeds wrote: > On Thu, Sep 17, 2015 at 03:01:53PM +1000, Tony Breeds wrote: > > Hi all, > > The recent relapse of oslo.utils 1.4.1[1] (for juno) is valid in kilo. > > The > > juno global-requirements for Babel are not compatible with kilo so

[openstack-dev] [oslo][oslo.config] Reloading configuration of service

Hi Josh, > Sounds like a useful idea if projects can plug-in themselves into the > reloading process. I definitely think there needs to be a way for > services to plug-in to this, although I'm not quite sure it will be > sufficient at the current time though. > > An example of why: > > - >

[openstack-dev] questions about nova compute monitors extensions

Hi Jay, I notice nova compute monitor now only tries to load monitors with namespace "nova.compute.monitors.cpu", and only one monitor in one namespace can be enabled( https://review.openstack.org/#/c/209499/6/nova/compute/monitors/__init__.py ). Is there a plan to make

[openstack-dev] [magnum][ptl] Magnum PTL Candidacy

Hi all, I would like to announce my candidacy for the PTL position of Magnum. I involved in Magnum project starting from December 2014. At that time, Magnum's code base is much smaller than right now. Since then, I worked with a diverse set of team members to land features, discuss the

Re: [openstack-dev] [oslo][oslo.config] Reloading configuration of service

Excerpts from mhorban's message of 2015-09-17 10:26:28 +0300: > Hi Doug, > > > Rather than building hooks into oslo.config, why don't we build them > > into the thing that is catching the signal. That way the app can do lots > > of things in response to a signal, and one of them might be

Re: [openstack-dev] [defcore] Scoring for DefCore 2016.01 Guideline

On 16/09/15 22:26 -0700, Chris Hoge wrote: The DefCore Committee is working on scoring capabilities for the upcoming 2016.01 Guideline, a solid draft of which will be available at the Mitaka summit for community review and will go to the Board of Directors for approaval in Janaury [1]. The

Re: [openstack-dev] [neutron] PTL Non-Candidacy

Kyle, Thank you for the awesome work you did in the past 3 cycles as PTL. You made hard decisions and drove changes that resulted in a more welcoming, easier to work with community, not to mention a more healthy project. I'm very happy I had the chance to work with you, Livnat On Sat, Sep 12,

Re: [openstack-dev] [glance] proposed priorities for Mitaka

On 15 September 2015 at 18:22, Monty Taylor wrote: > On 09/15/2015 07:09 PM, stuart.mcla...@hp.com wrote: I've been looking into the existing task-based-upload that Doug mentions: can anyone clarify the following? On a default devstack install

[openstack-dev] [keystone] PTL Candidacy

Hello everyone, I'd like to announce my candidacy for the Keystone PTL for the Mitaka cycle. The project has had great leadership the entire time I have been involved and I want to keep up the tradition. I've been working on Keystone for the past 2 years and I'd like to step up and take more of

Re: [openstack-dev] [all][gate] grende jobs failing.

Tony, Looks like the ban is holding up: https://review.openstack.org/#/c/224429/ -- Dims On Thu, Sep 17, 2015 at 4:03 AM, Tony Breeds wrote: > On Thu, Sep 17, 2015 at 03:34:30PM +1000, Tony Breeds wrote: > > On Thu, Sep 17, 2015 at 03:01:53PM +1000, Tony Breeds wrote:

[openstack-dev] [Cinder] PTL Candidacy

Hello everyone, I'm announcing my candidacy for Cinder PTL for the Mitaka release. First of all, I would like to thank John and Mike for their great and hard work making Cinder such a great project with good and a big community. As a Cinder community we made a great progress not only with new

Re: [openstack-dev] [glance] proposed priorities for Mitaka

On 14 September 2015 at 16:27, Thierry Carrez wrote: > Doug Hellmann wrote: >> [...] >> 1. Resolve the situation preventing the DefCore committee from >>including image upload capabilities in the tests used for trademark >>and interoperability validation. >> >> 2.

Re: [openstack-dev] [cinder] LVM snapshot performance issue -- why isn't thin provisioning the default?

On 16 September 2015 at 23:43, Eric Harney wrote: > Currently, at least some options set in [DEFAULT] don't apply to > per-driver sections, and require you to set them in the driver section > as well. > This is extremely confusing behaviour. Do you have any examples? I'm not

Re: [openstack-dev] [all][gate] grende jobs failing.

On Thu, Sep 17, 2015 at 06:22:47AM -0400, Davanum Srinivas wrote: > Tony, > Looks like the ban is holding up: > https://review.openstack.org/#/c/224429/ Sorry yes. Robert Collins pointed out that my new quicker plan wasn't going to work so we went back to the original ban 1.4.1 solution. It

Re: [openstack-dev] [Barbican] Providing service user read access to all tenant's certificates

The tenant admin from Step 1, should also do Step 2. From: Vijay Venkatachalam > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [magnum] Is magnum db going to be removed for k8s resources?

Anyone who have some comments/suggestions on this? Thanks! On Mon, Sep 14, 2015 at 3:57 PM, Jay Lau wrote: > Hi Vikas, > > Thanks for starting this thread. Here just show some of my comments here. > > The reason that Magnum want to get k8s resource via k8s API including

[openstack-dev] [Neutron] Effective Neutron

Hi fellow developers and reviewers, Some of you may have noticed that I put together patch [1] up for review. The intention of this initiative is to capture/share 'pills of wisdom' when it comes to Neutron development and reviewing. In fact, there are a number of common patterns (or

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On Thu, Sep 17, 2015 at 10:26 AM, Monty Taylor wrote: > On 09/17/2015 04:50 PM, Anita Kuno wrote: > >> On 09/17/2015 08:22 AM, Matt Riedemann wrote: >> >>> >>> >>> On 9/17/2015 8:25 AM, Tristan Cacqueray wrote: >>> PTL Nomination is now over. The official candidate

Re: [openstack-dev] [all][elections] PTL nomination period is now over

Monty Taylor wrote: > I agree- and this is a great example of places where human judgement is > better than rules. > > For instance - one of the projects had a nominee but it missed the > deadline, so that's probably an easy on. > > For one of the projects it had been looking dead for a while,

Re: [openstack-dev] [kolla] Followup to review in gerrit relating to RHOS + RDO types

On Thu, Sep 17, 2015 at 3:22 AM, wrote: > There is an apparent need for having official RHOS being supported from > our end, and we just so happen to have the possibility of filling that > need. Should the need arise to support whatever fancy proprietary backend > system or even

Re: [openstack-dev] [all][gate] grende jobs failing.

+1 for range checking and stable team +2's in openstack/releases repo -- dims On Thu, Sep 17, 2015 at 10:05 AM, Matt Riedemann wrote: > > > On 9/17/2015 7:23 AM, Tony Breeds wrote: > >> On Thu, Sep 17, 2015 at 06:22:47AM -0400, Davanum Srinivas wrote: >> >>> Tony,

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On 9/17/2015 8:25 AM, Tristan Cacqueray wrote: PTL Nomination is now over. The official candidate list is available on the wiki[0]. There are 5 projects without candidates, so according to this resolution[1], the TC we'll have to appoint a new PTL for Barbican, MagnetoDB, Magnum, Murano and

Re: [openstack-dev] [all][elections] PTL nomination period is now over

Time.is is showing utc in "PM" not a 24 hour clock. It is past 1500 UTC at the moment. Sent via mobile > On Sep 17, 2015, at 08:05, Douglas Mendizábal > wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > I think someone jumped the gun on this

Re: [openstack-dev] [Neutron] Effective Neutron

Thanks for marking as WPI From: "Armando M." > Reply-To: OpenStack List > Date: Thursday, September 17, 2015 at 6:20 PM To: OpenStack List

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On 09/17/2015 04:50 PM, Anita Kuno wrote: On 09/17/2015 08:22 AM, Matt Riedemann wrote: On 9/17/2015 8:25 AM, Tristan Cacqueray wrote: PTL Nomination is now over. The official candidate list is available on the wiki[0]. There are 5 projects without candidates, so according to this

Re: [openstack-dev] [neutron] What semantics are expected when booting a VM on an external network?

Yes, the L2 semantics apply to the external network as well (at least with ML2). One example of the special casing is the external_network_bridge option in the L3 agent. That would cause the agent to plug directly into a bridge so none of the normal L2 agent wiring would occur. With the L2

Re: [openstack-dev] [Neutron] Effective Neutron

On Thu, Sep 17, 2015 at 11:37:35AM EDT, Edgar Magana wrote: > Actually, I am wondering if replacing the Wiki with this great information > will be better??? > For sure, docs are well structured and they have a great team behind them but > the wikis are not the same, gerrit review provide a

Re: [openstack-dev] [all][elections] PTL nomination period is now over

Likewise, I'm not sure I missed the candidacy window, I think our late mid-cycle threw things out of whack slightly. When I saw the Magnum nomination I made a mental note to apply today. This is a poor-show on my part and I apologise to the TC, the community and the Security team for this

Re: [openstack-dev] [oslo][oslo.config] Reloading configuration of service

Agreed, +1 :) Gotta start somewhere to get to somewhere else ;) mhorban wrote: Hi Josh, > Sounds like a useful idea if projects can plug-in themselves into the > reloading process. I definitely think there needs to be a way for > services to plug-in to this, although I'm not quite sure it

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On Thu, Sep 17, 2015 at 10:26 AM, Monty Taylor wrote: > On 09/17/2015 04:50 PM, Anita Kuno wrote: > >> On 09/17/2015 08:22 AM, Matt Riedemann wrote: >> >>> >>> >>> On 9/17/2015 8:25 AM, Tristan Cacqueray wrote: >>> PTL Nomination is now over. The official candidate

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On 09/17/2015 03:05 PM, Douglas Mendizábal wrote: > I think someone jumped the gun on this thread. According to the wiki > [1] the cutoff time is not until 5:59 UTC, which > doesn't happen for another few hours. [2] > > Am I missing something? > > [1]

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On Thu, Sep 17, 2015 at 10:05:20AM -0500, Douglas Mendizábal wrote: > I think someone jumped the gun on this thread. According to the wiki > [1] the cutoff time is not until 5:59 UTC, which > doesn't happen for another few hours. [2] > > Am I missing something? From the wiki[0]: --- Timeline

Re: [openstack-dev] [Neutron] Effective Neutron

Actually, I am wondering if replacing the Wiki with this great information will be better??? For sure, docs are well structured and they have a great team behind them but the wikis are not the same, gerrit review provide a better way to distribute and update this knowledge… Great initiative

Re: [openstack-dev] [dragonflow] Low OVS version for Ubuntu

Another issue is that the gate is running with Ubuntu 14.04, which is running OVS 2.0. This means we can't test certain features in Neutron (For example, the OVS ARP responder). On Thu, Sep 17, 2015 at 4:17 AM, Gal Sagie wrote: > Hello Li Ma, > > Dragonflow uses OpenFlow1.3

Re: [openstack-dev] [all][elections] PTL nomination period is now over

Folks, Last year I found myself in the same position when I missed a deadline because my wrong planning and time zones nightmare! However, the rules were very clear and I assumed my mistake. So, we should assume that we do not have candidates and follow the already described process. However,

Re: [openstack-dev] [Neutron] Effective Neutron

On Thu, Sep 17, 2015 at 10:20 AM, Armando M. wrote: > Hi fellow developers and reviewers, > > Some of you may have noticed that I put together patch [1] up for review. > > The intention of this initiative is to capture/share 'pills of wisdom' > when it comes to Neutron

[openstack-dev] [Security] Leadership / Participation in PTL elections.

Security Folks, Some how I missed the window to nominate myself as a PTL candidate for Security. I have literally no idea how I missed it. I’ve been working on Security project things all week (Anchor and OSSNs mainly) so it’s not like I wasn’t thinking about the Security team! Anyway, I missed

Re: [openstack-dev] [oslo][oslo.config] Reloading configuration of service

So a few 'event' like constructs/libraries that I know about: http://docs.openstack.org/developer/taskflow/types.html#taskflow.types.notifier.Notifier I'd be happy to extract that and move to somewhere else if needed, it provides basic event/pub/sub kind of activities for taskflow

Re: [openstack-dev] [all][elections] PTL nomination period is nowover

>> I'd like to apply some common sense here and if this many candidates on both sides of the globe got confused, we can still take that into consideration when taking next steps. ++ to this, it was clearly a slip up from some folk. let's use our human judgement and common sense here :) Thanks,

[openstack-dev] [all][elections] PTL nomination period is now over

PTL Nomination is now over. The official candidate list is available on the wiki[0]. There are 5 projects without candidates, so according to this resolution[1], the TC we'll have to appoint a new PTL for Barbican, MagnetoDB, Magnum, Murano and Security There are 7 projects that will have an

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On 17/09/15 13:25 +, Tristan Cacqueray wrote: PTL Nomination is now over. The official candidate list is available on the wiki[0]. There are 5 projects without candidates, so according to this resolution[1], the TC we'll have to appoint a new PTL for Barbican, MagnetoDB, Magnum, Murano and

Re: [openstack-dev] [all][gate] grende jobs failing.

On 9/17/2015 7:23 AM, Tony Breeds wrote: On Thu, Sep 17, 2015 at 06:22:47AM -0400, Davanum Srinivas wrote: Tony, Looks like the ban is holding up: https://review.openstack.org/#/c/224429/ Sorry yes. Robert Collins pointed out that my new quicker plan wasn't going to work so we went back to

Re: [openstack-dev] [magnum] Is magnum db going to be removed for k8s resources?

Here's what I see if I look at this from a matter-of-fact standpoint. When Nova works with libvirt, libvirt might have something that Nova doesn't know about, but Nova doesn't care. Nova's database is the only world that Nova cares about. This allows Nova to have one source of data. With

Re: [openstack-dev] [tripleo] Upgrade plans for RDO Manager - Brainstorming

On 09/09/2015 05:34 PM, Zane Bitter wrote: On 24/08/15 15:12, Emilien Macchi wrote: Hi, So I've been working on OpenStack deployments for 4 years now and so far RDO Manager is the second installer -after SpinalStack [1]- I'm working on. SpinalStack already had interested features [2] that

Re: [openstack-dev] [TripleO] Core reviewers for python-tripleoclient and tripleo-common

Hi, It's been a week, and I've heard no objections this proposal: >> Specifically, the folks I'm proposing are: >> Brad P. Crochet >> Dougal Matthews >> - keep just 1 tripleo acl, and add additional folks there, with a good >> faith agreement not to +/-2,+A

Re: [openstack-dev] [all][elections] PTL nomination period is now over

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I think someone jumped the gun on this thread. According to the wiki [1] the cutoff time is not until 5:59 UTC, which doesn't happen for another few hours. [2] Am I missing something? [1]

Re: [openstack-dev] [neutron] What semantics are expected when booting a VM on an external network?

Thanks, Kevin. Some further queries, then: On 17/09/15 15:49, Kevin Benton wrote: > > It's not true for all plugins, but an external network should provide > the same semantics of a normal network. > Yes, that makes sense. Clearly the core semantic there is IP. I can imagine reasonable

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On 2015-09-17 10:05:20 -0500 (-0500), Douglas Mendizábal wrote: > I think someone jumped the gun on this thread. According to the wiki > [1] the cutoff time is not until 5:59 UTC, which > doesn't happen for another few hours. [2] Per that page the deadline for nominations is September 17, 05:59

Re: [openstack-dev] [neutron] What semantics are expected when booting a VM on an external network?

On Thu, Sep 17, 2015 at 09:58:29AM EDT, Neil Jerram wrote: > Specifically I wonder if VM's attached to an external network expect any > particular L2 characteristics, such as being able to L2 broadcast to > each other? I am fairly certain that our definition of a Neutron Network, as a L2

[openstack-dev] [Magnum]bay/baymodel sharing for multi-tenants

Hi Magnum, Currently, there are about two blueprints related to bay/baymode sharing for different tenants. 1) https://blueprints.launchpad.net/magnum/+spec/tenant-shared-model 2) https://blueprints.launchpad.net/magnum/+spec/public-baymodels What we want to do is we can make the bay/baymodel to

Re: [openstack-dev] [neutron] PTL Non-Candidacy

Thanks for all your hard work Kyle. Enjoy your more relaxed schedule :) On Sep 11, 2015, at 5:12 PM, Kyle Mestery > wrote: I'm writing to let everyone know that I do not plan to run for Neutron PTL for a fourth cycle. Being a PTL is a rewarding

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On 17/09/15 13:44 +, Tristan Cacqueray wrote: On 09/17/2015 01:32 PM, Flavio Percoco wrote: On 17/09/15 13:25 +, Tristan Cacqueray wrote: PTL Nomination is now over. The official candidate list is available on the wiki[0]. There are 5 projects without candidates, so according to this

[openstack-dev] [neutron] What semantics are expected when booting a VM on an external network?

Thanks to the interesting 'default network model' thread, I now know that Neutron allows booting a VM on an external network. :-) I didn't realize that before! So, I'm now wondering what connectivity semantics are expected (or even specified!) for such VMs, and whether they're the same as - or

Re: [openstack-dev] [all][elections] PTL nomination period is now over

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This is quite unfortunate, as I was intending to submit my candidacy for the Barbican project today, but I did not realize the cutoff time would be in the morning in CDT. I'd like to apologize to the OpenStack community and the Barbican team in

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On 09/17/2015 08:22 AM, Matt Riedemann wrote: > > > On 9/17/2015 8:25 AM, Tristan Cacqueray wrote: >> PTL Nomination is now over. The official candidate list is available on >> the wiki[0]. >> >> There are 5 projects without candidates, so according to this >> resolution[1], the TC we'll have to

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On 09/17/2015 01:32 PM, Flavio Percoco wrote: > On 17/09/15 13:25 +, Tristan Cacqueray wrote: >> PTL Nomination is now over. The official candidate list is available on >> the wiki[0]. >> >> There are 5 projects without candidates, so according to this >> resolution[1], the TC we'll have to

Re: [openstack-dev] [neutron] What semantics are expected when booting a VM on an external network?

It's not true for all plugins, but an external network should provide the same semantics of a normal network. The only difference is that it allows router gateway interfaces to be attached to it. We want to get rid of as much special casing as possible for the external network. On Sep 17, 2015

Re: [openstack-dev] [Nova] Design Summit Topics for Nova

On Wed, Sep 16, 2015 at 11:40:28AM -0700, melanie witt wrote: > Today I was informed that google forms are blocked in China [1], so I wanted > to mention it here so we can consider an alternate way to collect submissions > from those who might not be able to access the form. I'll act as an

Re: [openstack-dev] Pycharm License for OpenStack developers

Hey Devs, I'm the guy who's maintained our JetBrains licenses for the past couple of years. License philosophy aside, the IDE you choose to use is entirely up to you. I'm currently waiting to hear back from JetBrains on the actual license. From the sound of it, the opensource license hasn't

Re: [openstack-dev] [neutron] What semantics are expected when booting a VM on an external network?

Thanks so much for your continuing answers; they are really helping me. I see your points now about the special casing, and about the semantic expectations and internal wiring of a Neutron network being just the same for an external network as for non-external. Hence, the model for an L3-only

Re: [openstack-dev] [all][elections] PTL nomination period is now over

Maybe it would be a good idea to switch to 23:59 AOE deadlines like many paper submissions use for academic conferences. That way there is never a need to convert TZs, you just get it in by the end of the day in your own time zone. On Sep 17, 2015 9:18 AM, "Edgar Magana"

Re: [openstack-dev] [all][elections] PTL nomination period is now over

But on the Internet, no one knows that I'm really a crocodile, and writing from Midway... Neil On 17/09/15 18:29, Kevin Benton wrote: > > Maybe it would be a good idea to switch to 23:59 AOE deadlines like > many paper submissions use for academic conferences. That way there is > never a

Re: [openstack-dev] [Sahara] FFE request for improved secret storage

i am retracting this request, i think this feature would benefit from more time to test and review. thanks for the consideration, mike On 09/09/2015 12:09 PM, michael mccune wrote: hi all, i am requesting an FFE for the improved secret storage feature. this change will allow operators to

Re: [openstack-dev] [neutron] What semantics are expected when booting a VM on an external network?

router:external only affects the behavior of Neutron routers. It allows them to attach to it with an external gateway interface which implies NAT and floating IPs. >From an instance's perspective, an external network would be no different than any other provider network scenario that uses a

[openstack-dev] [OSSN 0052] Python-swiftclient exposes raw token values in debug logs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Python-swiftclient exposes raw token values in debug logs - --- ### Summary ### The password and authentication token configuration options for the python-swiftclient are not marked as secret. The values of these options will be logged to the

Re: [openstack-dev] [Congress] CLI equivalent

Thanks Alex. From: Alex Yip [mailto:a...@vmware.com] Sent: Wednesday, September 16, 2015 12:48 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Congress] CLI equivalent Try this: openstack congress policy row list classification error​

Re: [openstack-dev] [Devstack][Sahara][Cinder] BlockDeviceDriver support in Devstack

You need to remove your Workflow-1. -- Sean M. Collins __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [all][elections] PTL nomination period is now over

Because it's still day_n AOE in early hours of day_n+1 local-time in a lot of places. I think I have until 6 AM the day after an AOE deadline where it's still considered the deadline date anywhere on earth, as there are still places on earth where the date hasn't flipped. Your EOD is not the

[openstack-dev] [app-catalog] App Catalog IRC meeting minutes - 9/17/2015

We had a nice meeting today and caught up on some of our plans/intentions for the web site backend. Long ago we knew that a basically static site with assets listed in a YAML would not last for long. It's already causing issues with respect to versions and updates, and makes determining when

Re: [openstack-dev] [all] [ptl] Troubleshooting cross-project communications

On Wed, Sep 16, 2015 at 11:30 AM, Anne Gentle wrote: > > > On Wed, Sep 16, 2015 at 9:16 AM, Thierry Carrez > wrote: > >> Anne Gentle wrote: >> > [...] >> > What are some of the problems with each layer? >> > >> > 1. weekly meeting: time

Re: [openstack-dev] [all][elections] PTL nomination period is now over

Midway is still on earth. :) On Thu, Sep 17, 2015 at 10:35 AM, Neil Jerram wrote: > But on the Internet, no one knows that I'm really a crocodile, and > writing from Midway... > > Neil > > > On 17/09/15 18:29, Kevin Benton wrote: > > > > Maybe it would be a good

Re: [openstack-dev] [kolla] Followup to review in gerrit relating to RHOS + RDO types

It appears the core team is mostly in agreement about the idea of having support for commercial distributions of OpenStack in Kolla. The vote was nearly unanimous. That said, there was some feedback that came out of the various comments. As a community: We should set standards by which

Re: [openstack-dev] [neutron][lbaas] Proposing Michael Johnson for neutron-lbaas core team

Not a core but I would like to share my +1 about Michael. Cheers, Edgar On 9/16/15, 3:33 PM, "Doug Wiegley" wrote: >Hi all, > >As the Lieutenant of the advanced services, I nominate Michael Johnson to be a >member of the neutron-lbaas core reviewer team. >

Re: [openstack-dev] [puppet] service default value functions

Clint, We're solving a different issue. Before anytime someone added an option we had this logic: if $setting { project_config/setting: value => $setting } else { project_config/setting: ensure => absent; } This was annoying to have to write for every single setting but without it, nobody

Re: [openstack-dev] [all][elections] PTL nomination period is now over

How is it not what I described? Time zones become irrelevant if you get it in by the end of the day in your local time zone. https://en.wikipedia.org/wiki/Anywhere_on_Earth On Thu, Sep 17, 2015 at 10:30 AM, Brian Curtin wrote: > On Thu, Sep 17, 2015 at 12:26 PM, Kevin Benton

[openstack-dev] [mistral][requirements] lockfile not in global requirements

The syncing of requirements fails from the requirements repository to mistral-extra with 'lockfile' is not in global-requirements.txt Mistral team, could you either propose to add lockfile to the global requirements file - or remove it from your project, please? for details see:

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On Thu, Sep 17, 2015 at 12:26 PM, Kevin Benton wrote: > Maybe it would be a good idea to switch to 23:59 AOE deadlines like many > paper submissions use for academic conferences. That way there is never a > need to convert TZs, you just get it in by the end of the day in your

Re: [openstack-dev] [cinder] LVM snapshot performance issue -- why isn't thin provisioning the default?

On 09/17/2015 05:00 AM, Duncan Thomas wrote: > On 16 September 2015 at 23:43, Eric Harney wrote: > >> Currently, at least some options set in [DEFAULT] don't apply to >> per-driver sections, and require you to set them in the driver section >> as well. >> > > This is

Re: [openstack-dev] [neutron][lbaas] Proposing Michael Johnson for neutron-lbaas core team

I'm off today so my +1 is more like a +2 On Sep 17, 2015 12:59 PM, Edgar Magana wrote: Not a core but I would like to share my +1 about Michael. Cheers, Edgar On 9/16/15, 3:33 PM, "Doug Wiegley" wrote: >Hi all, > >As the Lieutenant

Re: [openstack-dev] [all][elections] PTL nomination period is now over

Le 17/09/2015 19:26, Kevin Benton a écrit : Maybe it would be a good idea to switch to 23:59 AOE deadlines like many paper submissions use for academic conferences. That way there is never a need to convert TZs, you just get it in by the end of the day in your own time zone. IMHO, the

[openstack-dev] [OSSN 0055] Service accounts may have cloud admin privileges

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Service accounts may have cloud admin privileges - --- ### Summary ### OpenStack services (for example Nova and Glance) typically use a service account in Keystone to perform actions. In some cases this service account has full admin privileges,

Re: [openstack-dev] [all][elections] PTL nomination period is now over

It guarantees that if you hit the date deadline local time, that you won't miss the deadline. It doesn't matter if there are extra hours afterwards. The idea is that it gets rid of the need to do time zone conversions. If we are trying to do some weird optimization where everyone wants to submit

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On 9/17/2015 1:43 PM, Sylvain Bauza wrote: Le 17/09/2015 19:26, Kevin Benton a écrit : Maybe it would be a good idea to switch to 23:59 AOE deadlines like many paper submissions use for academic conferences. That way there is never a need to convert TZs, you just get it in by the end of

Re: [openstack-dev] [neutron] What semantics are expected when booting a VM on an external network?

On Thu, Sep 17, 2015 at 10:26 AM, Kevin Benton wrote: > Yes, the L2 semantics apply to the external network as well (at least with > ML2). This is true and should remain so. I think we've come to the agreement that a neutron Network, external, shared, or not, should be an L2

Re: [openstack-dev] [magnum] Discovery

+1 for stop using public discovery endpoint, most private cloud vms doesn’t have access to internet and operator must to run etcd instance somewhere just for discovery. — Egor From: Andrew Melton > Reply-To: "OpenStack

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On Thu, Sep 17, 2015 at 2:23 PM, Kyle Mestery wrote: > On Thu, Sep 17, 2015 at 3:19 PM, Anne Gentle < > annegen...@justwriteclick.com> wrote: > >> >> >> On Thu, Sep 17, 2015 at 3:15 PM, John Griffith >> wrote: >> >>> >>> >>> On Thu, Sep 17, 2015 at

[openstack-dev] [magnum] Associating patches with bugs/bps (Please don't hurt me)

I'm going to start out by making this clear: I am not looking to incite a flame war. I've been working in Magnum for a couple of weeks now, and I'm starting to get down the processes for contribution. I'm here to talk about the process of always needing to have a patch associated with a bug

[openstack-dev] [murano] [app-catalog] versions for murano assets in the catalog

One big thing missing from the App Catalog right now is the ability to version assets. This is especially obvious with the Murano assets which have some version/release dependencies. Ideally an app-catalog user would be able to pick an older version (ie "works with kilo rather than liberty"),

Re: [openstack-dev] [all][elections] PTL nomination period is now over

Excerpts from Morgan Fainberg's message of 2015-09-17 12:51:33 -0700: > I think this is all superfluous however and we should simply encourage > people to not wait until the last minute. Waiting to see who is > running/what the field looks like isn't as important as standing up and > saying

  1   2   >