Re: [openstack-dev] [cinder][glance]Upload encrypted volumes to images

On Nov 23, 2015 22:34, Daniel P. Berrange wrote: > On Mon, Nov 23, 2015 at 07:05:05AM +0100, Philipp Marek wrote: >>> About uploading encrypted volumes to image, there are three options: >>> 1. Glance only keeps non-encrypted images. So when uploading > encrypted >>>volumes to image, cinder de-

Re: [openstack-dev] [cinder][nova]Move encryptors to os-brick

Hi all, Let me summarize the most important items that need attach/detach encryptors in Cinder: 1. Create an encrypted volume from images. 2. Migrate an unencrypted volume to encrypted. Except above, we may need to upload encrypted volume to Glance. If needs to change encryption

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 11/17/2015 07:31 AM, Tzu-Mainn Chen wrote: On 10 November 2015 at 15:08, Tzu-Mainn Chen mailto:tzuma...@redhat.com>> wrote: Hi all, At the last IRC meeting it was agreed that the new TripleO

Re: [openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

On 24 November 2015 at 20:06, Angus Lees wrote: > Ah, I could have been clearer. A workaround for (2) in the original post: > If you're starting from an older pip version it can be hard to bootstrap the > right order of new things to correctly survive the new "; predicate" > requirements.txt synt

Re: [openstack-dev] [all] [oslo] Please stop removing usedevelop from tox.ini (at least for now)

Ah, I could have been clearer. A workaround for (2) in the original post: If you're starting from an older pip version it can be hard to bootstrap the right order of new things to correctly survive the new "; predicate" requirements.txt syntax. On Mon, 23 Nov 2015 at 18:10 Robert Collins wrote:

[openstack-dev] [keystone] Mid-Cycle Meetup Planning

I'd like to pin down a date and location for our mid-cycle meetup. I've created a very short form for folks to fill out: http://goo.gl/forms/uNsGSRdRLl Depending on the number of responses received (normally we see about 20-30 folks at the mid-cycle), I may make a final call on the date and locat

Re: [openstack-dev] [Openstack-i18n] DocImpact Changes

it sounds a good idea in general. One question is how each project team should handle DocImpact bugs filed in their own project. It will be a part of "Plan and implement an education campaign" mentioned in the docs spec. I think some guidance will be needed. One usual question will be which guide(

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Excerpts from Adam Young's message of 2015-11-23 20:21:47 -0800: > On 11/23/2015 11:42 AM, Morgan Fainberg wrote: > > Hi everyone, > > > > This email is being written in the context of Keystone more than any > > other project but I strongly believe that other projects could benefit > > from a sim

Re: [openstack-dev] [neutron][ipam][devstack] How to use IPAM reference in devstack

Hi Thanh, Thanks a lot. That helped. On Mon, Nov 23, 2015 at 8:45 PM, thanh le giang wrote: > Hi Shraddha > > You can add this line iniset $NEUTRON_CONF DEFAULT ipam_driver "internal" > at the end of function configure_neutron in lib/neutron-legacy file > > Thanh > > 2015-11-24 11:20 GMT+07:

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks _

Re: [openstack-dev] [neutron][ipam][devstack] How to use IPAM reference in devstack

Hi Shraddha You can add this line iniset $NEUTRON_CONF DEFAULT ipam_driver "internal" at the end of function configure_neutron in lib/neutron-legacy file Thanh 2015-11-24 11:20 GMT+07:00 Shraddha Pandhe : > Hi John, > > Thanks for letting me know. How do I setup fresh devstack with pluggable >

[openstack-dev] [all] Time to increase our IRC Meetings infrastructure?

Hello all, I'd like you all to consider making a few changes to our IRC meeting infrastructure TL;DR: I think we need to add #openstack-meeting-5 and make sure people are using it rather then per-project channels Slightly longer version . Capacity I think we've reach

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On 11/23/2015 11:42 AM, Morgan Fainberg wrote: Hi everyone, This email is being written in the context of Keystone more than any other project but I strongly believe that other projects could benefit from a similar evaluation of the policy. Most projects have a policy that prevents the follo

Re: [openstack-dev] [neutron][ipam][devstack] How to use IPAM reference in devstack

Hi John, Thanks for letting me know. How do I setup fresh devstack with pluggable IPAM enabled in the meantime? On Mon, Nov 23, 2015 at 5:34 PM, John Belamaric wrote: > It currently only supports greenfield deployments. See [1] - we plan to > build a migration in the Mitaka time frame. > > John

[openstack-dev] [hyper-v] oslo.privsep vs Windows

Dims has just raised[1] the excellent concern that oslo.privsep will need to at least survive on Windows, because hyper-v. I have no real experience coding on windows (I wrote a windows C program once, but I only ever ran it under wine ;) and certainly none within an OpenStack/python context: 1)

Re: [openstack-dev] [TripleO] workflow

On 24/11/15 03:37, Dan Prince wrote: There are lots of references to "workflow" within TripleO conversations these days. We are at (or near) the limit of what we can do within Heat with regards to upgrades. We've got a new TripleO API in the works (a new version of Tuskar basically) that is speci

[openstack-dev] [keystone] Diagnostic APIs for Keystone

Figuring out what is or is not going to work when a user tries to perform an operation in OpenStack can be frustrating. I've had a few people ask me for help specifically for configuring LDAP. With Federation , things will get better. I mean Worse. What kind of diagnostic tooling do we need

Re: [openstack-dev] [release] process change for closing bugs when patches merge

On 23 November 2015 at 13:58, Doug Hellmann wrote: > As part of completing the release automation work and deprecating our > use of Launchpad for release content tracking, we also want make some > changes to the way patches associated with bugs are handled. > > Right now, when a patch with Closes

Re: [openstack-dev] [neutron][ipam][devstack] How to use IPAM reference in devstack

It currently only supports greenfield deployments. See [1] - we plan to build a migration in the Mitaka time frame. John [1] https://bugs.launchpad.net/neutron/+bug/1516156 On Nov 23, 2015, at 8:05 PM, Shraddha Pandhe mailto:spandhe.openst...@gmail.com>> wrote: Hi folks, What is the right

[openstack-dev] [neutron][ipam][devstack] How to use IPAM reference in devstack

Hi folks, What is the right way to use ipam reference implementation with devstack? When setup devstack, I didnt have the setting ipam_driver = internal I changed it afterwards. But now when I try to create a port, I get this error: 2015-11-23 21:23:00.078 ERROR neutron.ipam.drivers.neutron

[openstack-dev] [app-catalog] Weekly IRC meeting cancelled

We will not be holding our weekly IRC meeting this week due to the Thanksgiving holiday. Our regular meeting will resume Thursday, December 3rd. As always, you can find the meeting schedule and agenda here: https://wiki.openstack.org/wiki/Meetings/app-catalog Hope everyone (celebrating or not) h

[openstack-dev] [magnum] Networking Subteam Meeting

All, There will be no Networking Subteam meeting this week due to the Thanksgiving holiday. Regards, Daneyon Hansen Software Engineer Email: daneh...@cisco.com Phone: 303-718-0400 http://about.me/daneyon_hansen __ OpenStack

Re: [openstack-dev] [puppet] [ceph] Puppet Ceph CI

I'm confused, what is the context here? We use Ceph with OpenStack Kilo without issue. On Nov 23, 2015 2:28 PM, "David Moreau Simard" wrote: > Last I remember, David Gurtner tried to use Kilo instead of Juno but > he bumped into some problems and we settled for Juno at the time [1]. > At this poi

[openstack-dev] [ironic]Ironic operations on nodes in maintenance mode

Hi, I would like to know how everyone is using maintenance mode and what is expected from admins about nodes in maintenance. The reason I am bringing up this topic is because, most of the ironic operations, including manual cleaning are not allowed for nodes in maintenance. Thats a problem for us.

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On Mon, Nov 23, 2015 at 6:06 PM David Chadwick wrote: [snip] > > > > This is just a vote for distrusting the community. If you think there's > > "power" in being able to merge things, and that organizations will abuse > > this power, then you vote for distrust. > > No, rather for the abuse of pow

[openstack-dev] [Keystyone] Mid-Cycle Meetup Planning

I'd like to pin down a date and location for our mid-cycle meetup. I've created a very short form for folks to fill out: http://goo.gl/forms/uNsGSRdRLl Depending on the number of responses received (normally we see about 20-30 folks at the mid-cycle), I may make a final call on the date and locat

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On 23/11/2015 21:59, Clint Byrum wrote: > Excerpts from David Chadwick's message of 2015-11-23 13:20:56 -0800: >> Since the ultimate arbiter is the PTL, then it would be wrong to allow >> members of the same organisation as the PTL to perform all three code >> functions without the input of anyon

Re: [openstack-dev] [Fuel] CentOS-7 Transition Plan

Hey Dmitry, Thank you for your effort. I believe it's a huge step forward that opens number of possibilities. > Every container runs systemd as PID 1 process instead of > supervisord or application / daemon. Taking into account that we're going to drop Docker containers, I think it was unnecessa

Re: [openstack-dev] [stable] Post-release bump after 2014.2.4?

2015-11-23 17:31 GMT+01:00 Matt Riedemann : >> Or do you also suggest juno-eol != 2014.2.4? > I'd prefer to just remove the version tag in setup.cfg entirely so we switch > to post-versioning, then we can EOL the thing. That's what we do internally > on EOL stable branches (switch to post-versionin

Re: [openstack-dev] [Fuel] CentOS-7 Transition Plan

Please, take into account the plan to drop the containerization of Fuel services: https://review.openstack.org/#/c/248814/ -- Best regards, Oleg Gelbukh On Tue, Nov 24, 2015 at 12:25 AM, Dmitry Teselkin wrote: > Hello, > > We've been working for some time on bringing CentOS-7 to master node, >

Re: [openstack-dev] [release] process change for closing bugs when patches merge

So it's only for this time around (Mitaka-1) that I'll have to tag bugs as fix-released, because the release automation will just leave a comment? Going forward, the bugs will be automatically marked as fix-released, so the automation won't change their states when we release? Thanks, Steve Mar

[openstack-dev] DocImpact Changes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, The DocImpact flag was implemented back in Havana to make it easier for developers to notify the documentation team when a patch might cause a change in the docs. This has had an overwhelming response, resulting in a huge amount of t

Re: [openstack-dev] [puppet] [ceph] Puppet Ceph CI

Last I remember, David Gurtner tried to use Kilo instead of Juno but he bumped into some problems and we settled for Juno at the time [1]. At this point we should already be testing against both Liberty and Infernalis, we're overdue for an upgrade in that regard. But, yes, +1 to split acceptance t

[openstack-dev] [api] link definitions guideline to help align differing styles

hello all, there has recently been some activity in the guidelines surrounding the use of links embedded in response objects. it appears that with the recently merged error guideline[1] and the currently frozen pagination guideline[2], that we are on the precipice of introducing a bifurcation

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Excerpts from Brad Topol's message of 2015-11-23 13:38:34 -0800: > So to avoid the perception of a single company owning a piece of code, at > IBM our policy for major projects like Cinder, Nova and currently many > parts of Keystone (except pycadf) is to make sure we do not do the > following for

[openstack-dev] [release] process change for closing bugs when patches merge

As part of completing the release automation work and deprecating our use of Launchpad for release content tracking, we also want make some changes to the way patches associated with bugs are handled. Right now, when a patch with Closes-Bug in the commit message merges, the bug status is updated t

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Excerpts from David Chadwick's message of 2015-11-23 13:20:56 -0800: > Since the ultimate arbiter is the PTL, then it would be wrong to allow > members of the same organisation as the PTL to perform all three code > functions without the input of anyone from any other organisation. This > places to

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Very sensible policy, Brad. Congrats to IBM for it On 23/11/2015 21:38, Brad Topol wrote: > Hi Morgan, > > So lots of good points below. However I am pulled in two directions on > this topic. > > For small projects (e.g. pycadf, heat-translator) there are so few cores > and the project is small

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Hi Morgan, So lots of good points below. However I am pulled in two directions on this topic. For small projects (e.g. pycadf, heat-translator) there are so few cores and the project is small in size that we as project cores permit two people from the same company as the code author to both +

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

On 11/23/2015 2:23 PM, Andrew Laski wrote: On 11/23/15 at 04:43pm, Balázs Gibizer wrote: From: Andrew Laski [mailto:and...@lascii.com] Sent: November 23, 2015 17:03 On 11/23/15 at 08:54am, Ryan Rossiter wrote: > > >On 11/23/2015 5:33 AM, John Garbutt wrote: >>On 20 November 2015 at 09:37, Bal

[openstack-dev] [Fuel] CentOS-7 Transition Plan

Hello, We've been working for some time on bringing CentOS-7 to master node, and now is the time to share and discuss the transition plan. First of all, what have been changed: * Master node itself runs on CentOS-7. Since all the containers share the same repo as master node they all have been

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Since the ultimate arbiter is the PTL, then it would be wrong to allow members of the same organisation as the PTL to perform all three code functions without the input of anyone from any other organisation. This places too much power in the hands of one organisation to the detriment of the overall

[openstack-dev] [ironic] weekly subteam status report

Hi, We are stoked to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === (diff with Nov 16) - Open: 171 (+4). 11 new (+1), 60 in progress (-1), 0 critical, 16 high (+2) and 11 incomplete

Re: [openstack-dev] [nova] FKs in the DB

Excerpts from Mike Bayer's message of 2015-11-22 11:59:06 -0800: > > On 11/20/2015 04:33 PM, Clint Byrum wrote: > > Excerpts from Mike Bayer's message of 2015-11-20 11:29:31 -0800: > >> > >> On 11/20/2015 11:19 AM, Alexis Lee wrote: > >>> We just had a fun discussion in IRC about whether foreign k

[openstack-dev] [all][glance] Add Sabari Kumar Murugesan

Greetings, I'd like to propose adding Sabari Kumar Murugesan to the glance-core team. Sabari has been contributing for quite a bit to the project with great reviews and he's also been providing great feedback in matters related to the design of the service, libraries and other areas of the team.

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

On 11/23/15 at 04:43pm, Balázs Gibizer wrote: From: Andrew Laski [mailto:and...@lascii.com] Sent: November 23, 2015 17:03 On 11/23/15 at 08:54am, Ryan Rossiter wrote: > > >On 11/23/2015 5:33 AM, John Garbutt wrote: >>On 20 November 2015 at 09:37, Balázs Gibizer >> wrote: >>> >>> >> >>There is

Re: [openstack-dev] [Neutron] Security Groups OVS conntrack support

On 11/23/2015 02:16 PM, Kevin Benton wrote: > Security groups already use connection tracking. It's just done via a > linux bridge right now because the versions of OVS shipped with most > distros have no native conntrack support. This post discusses it in the context of OVN, but gets down to show

Re: [openstack-dev] [oslo] A special thank you to Davanum (Dims)

Michael, Thanks! -- Dims On Mon, Nov 23, 2015 at 10:55 AM, Michael Krotscheck wrote: > Have you ever wanted to thank someone directly, but they're not on IRC so > you can't pester them there? Well, dims isn't on IRC right now, so he has to > put up with being told he's awesome in public :). > >

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Excerpts from Thierry Carrez's message of 2015-11-23 09:17:06 -0800: > Morgan Fainberg wrote: > > [...] > > With all that said, here is the proposal I would like to set forth: > > > > 1. Code reviews still need 2x Core Reviewers (no change) > > 2. Code can be developed by a member of the same comp

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

On 23/11/2015 11:14 AM, AFEK, Ifat (Ifat) wrote: I guess I would like to do both: create a new alarm definition, then trigger it (call alarm_actions), and possibly later on set its state back to OK (call ok_action). I understood that currently all alarm triggering is internal in AODH, according

[openstack-dev] [puppet] [ceph] Puppet Ceph CI

I think I have a good lead on the recent failures in openstack / swift / radosgw integration component that we have since disabled. It looks like there is a oslo.config version upgrade conflict in the Juno repo we where using for CentOS. I think moving to Kilo will help sort this out, but at the sa

[openstack-dev] [Monasca]

Guys, I added https://review.openstack.org/#/c/248882/ for review. This should create a stable/kilo release for all the Monasca components. Please review Thanks, Fabio __ OpenStack Development Mailing List (not for usage q

Re: [openstack-dev] Learning to Debug the Gate

On 11/18/2015 06:03 PM, Mikhail Medvedev wrote: > We had a mini tutorial today in #openstack-infra, were Clark Boylan > explained how one can bring up an environment to debug logstash-2.0. > This is tangential to "debugging the gate", but still could be useful to > better understand logstash/es pip

Re: [openstack-dev] [Neutron] Security Groups OVS conntrack support

Security groups already use connection tracking. It's just done via a linux bridge right now because the versions of OVS shipped with most distros have no native conntrack support. On Mon, Nov 23, 2015 at 2:55 AM, Tapio Tallgren wrote: > Hi, > > Sorry for the stupid question, but how will I use

Re: [openstack-dev] [oslo] A special thank you to Davanum (Dims)

+++ Dims is awesome. And so are the other folks mentioned on this thread Happy Thanksgiving folks! Brad Topol, Ph.D. IBM Distinguished Engineer OpenStack (919) 543-0646 Internet: bto...@us.ibm.com Assistant: Kendra Witherspoon (919) 254-0680 From: Joshua Harlow To: "OpenStack Deve

Re: [openstack-dev] [ironic] specs process for ironic-inspector

On 19 November 2015 at 08:39, Pavlo Shchelokovskyy < pshchelokovs...@mirantis.com> wrote: > Hi all, > > +1 for specs in general, big features require a proper review and > discussion for which LP is not a good choice. > > +1 for not requiring a spec for small features, LP BP is enough for just > t

Re: [openstack-dev] [oslo] A special thank you to Davanum (Dims)

Dims is my hero ;) Lol, this thread is interesting :-P -Josh Amrith Kumar wrote: Yes, let’s talk about dims while he isn’t here. I’ll second what Michael and Steve have to say. Dims has been a great guy to work with and he’s been a great resource. On one occasion, I needed some openstack folk

Re: [openstack-dev] [neutron][fwaas]some architectural advice on fwaas driver writing

Oğuz, Eventually service chaining will help but if you need something to work now (and most vendors do) focus on how the other drivers are done. Usually copying the other drivers will work best. On the LBaaS side things are often integrated with tagged vLans but I haven’ read much of the code…

Re: [openstack-dev] [designate][chef] cookbook-openstack-dnsaas

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/23/15 7:17 AM, Hayes, Graham wrote: > On 20/11/15 21:23, JJ Asghar wrote: >> I walked through the developer install guide[2] and automated >> the build. I'm posting here because I can't find a "production" >> install guide, and was hoping that

Re: [openstack-dev] Licenses

I believe that Swapnil Kulkarni took over that role. -amrith From: Armando Dominguez [mailto:armando.doming...@rackspace.com] Sent: Monday, November 23, 2015 12:46 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] Licenses Hey All, Sorry for hitting the entire list, I'm just try

Re: [openstack-dev] [oslo] A special thank you to Davanum (Dims)

Yes, let's talk about dims while he isn't here. I'll second what Michael and Steve have to say. Dims has been a great guy to work with and he's been a great resource. On one occasion, I needed some openstack folks to help (in person) at very short notice. Dims (and Kamesh, also of Mirantis) dro

Re: [openstack-dev] [oslo] Should we make qpid/proton optional dependencies? (please say yes)

On 23 November 2015 at 22:33, Victor Stinner wrote: > Hi, > > Would it be possible to use the "extra dependencies" thing in setup.cfg? > Robert Collins started a similar change for Oslo DB for make DB drivers > optional: > https://review.openstack.org/#/c/184328/ > > Sadly, this change was not mer

Re: [openstack-dev] [stable] Stable team PTL nominations are open

On 11/23/2015 11:11 AM, Thierry Carrez wrote: Hi everyone, We discussed setting up a standalone stable maintenance team and as part of this effort we'll be organizing PTL elections over the coming weeks. We held a preliminary meeting today to converge on team scope and election mechanisms. Th

Re: [openstack-dev] [Ironic] Do we need to have a mid-cycle?

On Mon, Nov 16, 2015 at 06:05:54AM -0800, Jim Rollenhagen wrote: > > Another idea I floated last week was to do a virtual midcycle of sorts. > Treat it like a normal midcycle in that everyone tells their management > "I'm out for 3-4 days for the midcycle", but they don't travel anywhere. > We com

[openstack-dev] Licenses

Hey All, Sorry for hitting the entire list, I'm just trying to find out who took over the license handling from Andrew Melton? I'm looking for a Pycharm license. Thanks, Armando __ OpenStack Development Mailing List (not for

[openstack-dev] [Infra] Meeting Tuesday November 24th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday November 24th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add agend

Re: [openstack-dev] [puppet] mime-types-data requires Ruby version >= 2.0

Cody Herriges wrote: > Emilien Macchi wrote: >> Because of [1], [2] and [3]: all beaker-rspec-dsvm-trusty jobs are broken. >> >> The only one option I see is to pin mime-types in beaker dependencies, >> because beaker needs frog and frog needs mime-types. >> >> Note beaker is currently broken for u

Re: [openstack-dev] [Neutron] Call for review focus

On 23 November 2015 at 09:22, Carl Baldwin wrote: > On Mon, Nov 23, 2015 at 5:02 AM, Rossella Sblendido > wrote: > > To cross-reference we can use the bug ID or the blueprint name. > > > > I created a script that queries launchpad to get: > > 1) Bug number of the bugs tagged with approved-rfe >

Re: [openstack-dev] [Neutron] Call for review focus

On 23 November 2015 at 04:02, Rossella Sblendido wrote: > > > On 11/20/2015 03:54 AM, Armando M. wrote: > >> >> >> On 19 November 2015 at 18:26, Assaf Muller > > wrote: >> >> On Wed, Nov 18, 2015 at 9:14 PM, Armando M. > > wrote: >>

Re: [openstack-dev] [keystone] Case for renewability of tokens, increasing expiration time

Trusts are a part of the solution, yes, but without finer grained roles, the trust model doesn't help too much. You still must delegate far too much access at present. :/ Thanks, Kevin From: Jamie Lennox [jamielen...@gmail.com] Sent: Saturday, November 21, 2015 9

[openstack-dev] [javascript] New linting rules under review

Happy Monday, everyone! We have a few new javascript linting rules under review, since the release of eslint 1.10.1. Also, we have a proposed rule activation and a proposed rule deactivate as well, and all of these would benefit from more reviews. The rules in question are here: https://review.op

Re: [openstack-dev] [nova]New Quota Subteam on Nova

On Fri, 2015-11-20 at 16:13 +, Raildo Mascena wrote: > Me and other guys are working in the nested quota driver > (https://review.openstack.org/#/q/status:open+project:openstack/nova > +branch:master+topic:bp/nested-quota-driver-api,n,z) on Nova. > > > in addition, We want discuss the re-desi

Re: [openstack-dev] [Neutron] Call for review focus

On Mon, Nov 23, 2015 at 5:02 AM, Rossella Sblendido wrote: > To cross-reference we can use the bug ID or the blueprint name. > > I created a script that queries launchpad to get: > 1) Bug number of the bugs tagged with approved-rfe > 2) Bug number of the critical/high bugs > 3) list of blueprints

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Morgan Fainberg wrote: > [...] > With all that said, here is the proposal I would like to set forth: > > 1. Code reviews still need 2x Core Reviewers (no change) > 2. Code can be developed by a member of the same company as both core > reviewers (and approvers). > 3. If the trust that is being giv

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

On Mon, 2015-11-23 at 10:01 +, Alexis Lee wrote: > gord chung said on Fri, Nov 20, 2015 at 01:32:02PM -0500: > > On 20/11/15 11:33 AM, Alexis Lee wrote: > > >why would a producer spit out non-useful datapoints? If no-one cares > > >or will ever care, it simply shouldn't be included. > > > > ..

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On Mon, Nov 23, 2015 at 9:42 AM, Morgan Fainberg wrote: > Hi everyone, > > This email is being written in the context of Keystone more than any other > project but I strongly believe that other projects could benefit from a > similar evaluation of the policy. > > Most projects have a policy that

[openstack-dev] [stable] Stable team PTL nominations are open

Hi everyone, We discussed setting up a standalone stable maintenance team and as part of this effort we'll be organizing PTL elections over the coming weeks. We held a preliminary meeting today to converge on team scope and election mechanisms. The stable team mission is to: * Define and enforce

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On Mon, Nov 23, 2015 at 11:52 AM Dmitry Tantsur wrote: > On 11/23/2015 05:42 PM, Morgan Fainberg wrote: > > Hi everyone, > > > [snip,snip] > > > > This type of policy is an actively distrustful policy. > I don't see it quite like that. I don't think the policy is there because I'm not trusted t

Re: [openstack-dev] [keystone] [Mistral] [Heat] Autoprovisioning, per-user projects, and Federation

Hi. A colleague and i have been experimenting and prototyping an implementation for listening for ampq notifications and kicking off mistral workflows as a mistral service. This is for a use case that is different than discussed here, but seems like it might be useful to this use case as well.

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On Mon, Nov 23, 2015 at 8:51 AM, Dmitry Tantsur wrote: > On 11/23/2015 05:42 PM, Morgan Fainberg wrote: > >> Hi everyone, >> >> This email is being written in the context of Keystone more than any >> other project but I strongly believe that other projects could benefit >> from a similar evaluati

[openstack-dev] [mistral] Team meeting minutes - 11/23/2015

Thanks everyone for very productive meeting! Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-11-23-16.04.html Meeting log: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-11-23-16.04.log.html -- Best regards, Anastasia Kuznetsova _

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On 11/23/2015 05:42 PM, Morgan Fainberg wrote: Hi everyone, This email is being written in the context of Keystone more than any other project but I strongly believe that other projects could benefit from a similar evaluation of the policy. Most projects have a policy that prevents the followin

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

Colleagues, I've started working on the change. Here are two patches (fuel-main [1] and fuel-library [2]). They are not ready to review (still does not work and under active development). Changes are not going to be huge. Here is a spec [3]. Will keep the status up to date in this ML thread. [1]

Re: [openstack-dev] [Fuel] Changing APIs and API versioning

Roman, Sorry for breaking all the stuff again. I've got suggestion to change this from one of the core reviewers. Fortunately, separation of Fuel UI is already in progress (Vladimir Kozhukalov may want to provide extra info here), but it won't guarantee protection from similar issues in future. W

Re: [openstack-dev] [ironic][security] what is OK to put in DEBUG logs?

On 20 November 2015 at 18:32, Ben Nemec wrote: > On 11/19/2015 06:00 AM, Lucas Alvares Gomes wrote: > > Hi, > > > >> Also keep in mind that DEBUG logging, while still should have some > masking > >> of data, since it is explicitly called out (or should be) as not safe > for > >> production, can c

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

> From: Andrew Laski [mailto:and...@lascii.com] > Sent: November 23, 2015 17:03 > > On 11/23/15 at 08:54am, Ryan Rossiter wrote: > > > > > >On 11/23/2015 5:33 AM, John Garbutt wrote: > >>On 20 November 2015 at 09:37, Balázs Gibizer > >> wrote: > >>> > >>>Minor version change shall not cause any pr

[openstack-dev] [keystone][all] Move from active distrusting model to trusting model

Hi everyone, This email is being written in the context of Keystone more than any other project but I strongly believe that other projects could benefit from a similar evaluation of the policy. Most projects have a policy that prevents the following scenario (it is a social policy not enforced by

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

> From: Ryan Rossiter [mailto:rlros...@linux.vnet.ibm.com] > Sent: November 23, 2015 15:54 > On 11/23/2015 5:33 AM, John Garbutt wrote: > > On 20 November 2015 at 09:37, Balázs Gibizer > > wrote: > >> > >> Minor version change shall not cause any problem for the consumer as > the payload is backw

[openstack-dev] [Congress] tempest tests in gate not running

It looks like our tempest tests aren't running in the gate. Here's a recent patch that just merged this morning. https://review.openstack.org/#/c/242305/ If you go to the testr results, you'll see a list of all the tests that were run. http://logs.openstack.org/05/242305/5/gate/gate-congress-ds

Re: [openstack-dev] [stable] Post-release bump after 2014.2.4?

On 11/23/2015 7:00 AM, Ihar Hrachyshka wrote: Vincent Untz wrote: Le lundi 23 novembre 2015, à 13:17 +0100, Ihar Hrachyshka a écrit : Vincent Untz wrote: Hi, I know 2014.2.4 is (in theory) the last juno release, but I'd still expect to see a post-release bump to 2014.2.5 in git, to avoi

Re: [openstack-dev] [nova] release notes with reno and which patches need that?

Excerpts from Markus Zoeller's message of 2015-11-19 18:37:34 +0100: > If you ever had a patch which contained "UpgradeImpact" or "DocImpact", > this mail is for you. You may have already heard of "reno" and how it > will change the handling of the release notes. If not, [1] is the > announcement a

[openstack-dev] [release] Releases vs. development cycle

Hi everyone, As more projects get into the Big Tent there have been questions recently about release models and the development cycle. In particular, some projects want to be independent of the common release cycle and dates, but still keep some adherence to the development cycle. One example of

Re: [openstack-dev] [oslo] A special thank you to Davanum (Dims)

Michael Krotscheck wrote on 2015/11/23 10:55:04 AM: > From: Michael Krotscheck > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 2015/11/23 10:56 AM > Subject: [openstack-dev] [oslo] A special thank you to Davanum (Dims) > > Have you ever wanted to thank someone dir

Re: [openstack-dev] [puppet] mime-types-data requires Ruby version >= 2.0

Emilien Macchi wrote: > Because of [1], [2] and [3]: all beaker-rspec-dsvm-trusty jobs are broken. > > The only one option I see is to pin mime-types in beaker dependencies, > because beaker needs frog and frog needs mime-types. > > Note beaker is currently broken for ubuntu trusty nodes, because

Re: [openstack-dev] [tc][infra][neutron] branches for release-independent projects targeting Openstack release X

Excerpts from Chris Dent's message of 2015-11-19 20:55:15 +: > On Thu, 19 Nov 2015, Julien Danjou wrote: > > > It would be good to support that as being *normal*, not "potentially > > incorrect and random"! > > Yes. > > The underlying issue in this thread is the dominance of the six month >

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

Hi Gord, Please see my answers below. Ifat. > -Original Message- > From: gord chung [mailto:g...@live.ca] > Sent: Monday, November 23, 2015 4:57 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom > alarms in AODH > > hi

Re: [openstack-dev] [nova] Versioned notifications... who cares about the version?

On 11/23/15 at 08:54am, Ryan Rossiter wrote: On 11/23/2015 5:33 AM, John Garbutt wrote: On 20 November 2015 at 09:37, Balázs Gibizer wrote: Minor version change shall not cause any problem for the consumer as the payload is backward compatible between minor versions. So if the consumer doe

Re: [openstack-dev] [Fuel] Changing APIs and API versioning

Folks. This happened again. Nailgun’s API was silently changed [1] breaking python-fuelclient and everything else that was relying on it. I feel like this is the point when just discussing the issue is not enough so I call for a vote: Let’s separate Nailgun from Fuel UI and put them into diffe

Re: [openstack-dev] [Fuel] Changing APIs and API versioning

Recently we had some cool work done regarding decoupling repositories from fuel-web. I think it would be really good to have Fuel UI in separate repository. +1 to the idea. On Mon, Nov 23, 2015 at 4:56 PM, Roman Prykhodchenko wrote: > Folks. > > This happened again. Nailgun’s API was silently ch

[openstack-dev] [oslo] A special thank you to Davanum (Dims)

Have you ever wanted to thank someone directly, but they're not on IRC so you can't pester them there? Well, dims isn't on IRC right now, so he has to put up with being told he's awesome in public :). Thank you, dims, for helping me out on my work in oslo middleware. You've been calm, helpful, ete

  1   2   >