[openstack-dev] [AODH] event-alarm timeout discussion

All, I'd like make some clarification for the event-alarm timeout design as many of you have some misunderstanding here. Pls. correct me if any mistakes. I realized that there are 2 different things, but we mix them sometime: 1. event-timeout-alarm This is one new type of alarm that bracket

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

On Tue, Sep 20, 2016 at 11:57:26AM +0100, Daniel P. Berrange wrote: > On Tue, Sep 20, 2016 at 12:48:49PM +0200, Kashyap Chamarthy wrote: > > The said patch in question fixes a CVE[x] in stable/liberty. > > > > We currently have two options, both of them have caused an impasse with > > the Nova

Re: [openstack-dev] [Neutron] Security groups - API signature breakage

I didn't realize how many plugins subclassed the mixin and called super with the default_sg kwarg. We need a different fix. On Tue, Sep 20, 2016 at 10:00 PM, Gary Kotton wrote: > Hi, > > The patch https://review.openstack.org/373108 has broken the API > signature. I have

[openstack-dev] [osc][keystone] User Project List

I'm running into what doesn't really seem like a sensible design choice around how 'openstack project list' handles the user filter. Because of this here: https://github.com/openstack/python-openstackclient/blob/master/openstackclient/identity/v3/project.py#L199 and because of the find_resource

[openstack-dev] [Neutron] Security groups - API signature breakage

Hi, The patch https://review.openstack.org/373108 has broken the API signature. I have posted a revert for this. Can we do something like this? I do not think so. This breaks all plugins. Thanks Gary __ OpenStack Development

Re: [openstack-dev] [tricircle] Should we discuss the use cases of force volume detach in the Tricircle

Hello, I think Duncan's comments in another thread make sense to me. How do you think about it? Best Regards Chaoyi Huang (joehuang) From: D'Angelo, Scott [scott.dang...@hpe.com] Sent: 19 September 2016 20:34 To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [cinder]tempest test case for force detach volume

Understand that. I think the current situation may be reasonable. If Cinder API calling will lead to un-expected status, and need force-detach to restore the volume status back to normal, that means it's some issue we need to fix in Cinder. Best Regards Chaoyi Huang (joehuang)

Re: [openstack-dev] [tricircle]freeze date and tricircle splitting

very good, let's look over each patch (for all patches in review) in the weekly meeting to decide whether it should be merged before freeze. Best Regards Chaoyi Huang (joehuang) From: Shinobu Kinjo [shinobu...@gmail.com] Sent: 20 September 2016 15:45 To:

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

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. 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] [tc]a chance to meet all TCs for Tricircle big-tent application in Barcelona summit?

Thank you for the message. Will the weekly IRC meeting in that week also be cancelled during the summit period according to your experience? Best Regards Chaoyi Huang (joehuang) From: Thierry Carrez [thie...@openstack.org] Sent: 20 September 2016 18:03

Re: [openstack-dev] [infra]project description not updated in github repository

Thank you for the explanation. Can the description be updated manually in https://github.com/openstack/tricircle/ ? Best Regards Chaoyi Huang (joehuang) From: Andreas Jaeger [a...@suse.com] Sent: 20 September 2016 17:48 To: OpenStack Development

Re: [openstack-dev] [cinder] running afoul of Service.__repr__() during client.serivces.list()

Am Dienstag, den 20.09.2016, 15:31 -0600 schrieb Konstanski, Carlos P: > I am currently using python-cinderclient version 1.5.0, though the code in > question is still in master. > > When calling client.services.list() I get this result: "AttributeError: > service" > > The execution path of

Re: [openstack-dev] Too many mails on announce list again :)

Excerpts from Morgan Fainberg's message of 2016-09-20 14:38:27 -0700: > On Tue, Sep 20, 2016 at 9:18 AM, Doug Hellmann > wrote: > > > Excerpts from Thierry Carrez's message of 2016-09-20 10:19:04 +0200: > > > Steve Martinelli wrote: > > > > I think bundling the puppet,

Re: [openstack-dev] Too many mails on announce list again :)

On 16-09-20 05:38 PM, Morgan Fainberg wrote: On Tue, Sep 20, 2016 at 9:18 AM, Doug Hellmann wrote: Excerpts from Thierry Carrez's message of 2016-09-20 10:19:04 +0200: Steve Martinelli wrote: I think bundling the puppet, ansible and oslo releases together would cut

[openstack-dev] [architecture] Architecture WG Process

The Architecture Working Group discussed a process for managing group topics at the last meeting[0] to guide us down the path to many fruitful discussions. In summary, we propose the following: * We will use a (yet to be created) Git repository and the usual Gerrit review workflow for document

Re: [openstack-dev] Too many mails on announce list again :)

On Tue, Sep 20, 2016 at 9:18 AM, Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2016-09-20 10:19:04 +0200: > > Steve Martinelli wrote: > > > I think bundling the puppet, ansible and oslo releases together would > > > cut down on a considerable amount of

[openstack-dev] [cinder] running afoul of Service.__repr__() during client.serivces.list()

I am currently using python-cinderclient version 1.5.0, though the code in question is still in master. When calling client.services.list() I get this result: "AttributeError: service" The execution path of client.services.list() eventually leads to this method in cinderclient/v2/services.py:24:

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

On 9/20/2016 4:17 PM, Matt Riedemann wrote: On 9/20/2016 7:38 AM, Alan Pevec wrote: 2016-09-20 13:27 GMT+02:00 Kashyap Chamarthy : (3) Do nothing, leave the bug unfixed in stable/liberty That was the unspoken third option, thanks for spelling it out. :-) Yes, let's

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

On 9/20/2016 7:38 AM, Alan Pevec wrote: 2016-09-20 13:27 GMT+02:00 Kashyap Chamarthy : (3) Do nothing, leave the bug unfixed in stable/liberty That was the unspoken third option, thanks for spelling it out. :-) Yes, let's abandon both reviews. Cheers, Alan

[openstack-dev] [stackalytics] [deb] [packaging] OpenStack contribution stats skewed by deb-* projects

Hi, tldr; Commits stats are significantly skewed by deb-* projects ( http://stackalytics.com/?metric=commits=packaging-deb-group) By default Stackalytics processes commits from project's master branch. For some "old core" projects there is configuration to process stable branches as well. If

Re: [openstack-dev] [nova] Ocata development is open

On 9/20/2016 2:44 PM, Matt Riedemann wrote: Since we cut newton-rc1 last Thursday the master branch is now officially open for Ocata development. We're still working on newton-rc2 and may be backporting regression bug fixes. I expect to tag newton-rc2 sometime next week after the final

[openstack-dev] [nova] Ocata development is open

Since we cut newton-rc1 last Thursday the master branch is now officially open for Ocata development. We're still working on newton-rc2 and may be backporting regression bug fixes. I expect to tag newton-rc2 sometime next week after the final translations are in. I've started approving some

Re: [openstack-dev] [networking-sfc] OpenFlow version to use in the OVS agent

Hi Bernard, Networking-sfc currently uses OF1.3. Although OF1.3 dumps all groups, networking-sfc has follow-on filter code to select the info associated with the specific group ID from the dump. So we are fine and let's keep it as OF1.3. We can upgrade to OF1.5 when Neutron uses OF1.5.

[openstack-dev] Community Contributor Awards

Hello all, I’m pleased to announce the next round of community contributor awards! Similar to the Austin Summit, the awards will be presented by the Foundation at the feedback session of the upcoming Summit in Barcelona. Now accepting nominations! Please submit anyone you think is deserving of

Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

2016-09-19 19:40 GMT+02:00 Jeffrey Zhang : > Kolla core reviewer team, > > Kolla supports multiple Linux distros now, including > > * Ubuntu > * CentOS > * RHEL > * Fedora > * Debian > * OracleLinux > > But only Ubuntu, CentOS, and OracleLinux are widely used and we have >

Re: [openstack-dev] [horizon] Browser Support

Thanks, guys. - Shinobu On Tue, Sep 20, 2016 at 5:46 PM, Rob Cresswell wrote: > Agreed. I've created a bug here: > https://bugs.launchpad.net/horizon/+bug/1625514 > > Rob > > On 20 September 2016 at 09:40, amot...@gmail.com wrote: >> >> I think

Re: [openstack-dev] [networking-cisco] Poll to decide networking-cisco weekly meeting times

On 2016-09-20 16:23:29 + (+), Sam Betts (sambetts) wrote: > My interpretation of the guidelines was that those channels are > reserved for official OpenStack projects (projects included in > governance projects.yaml) only, so until we regain that status I > was planning on holding it in

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

Matthias, I was asked why this is so by a different person. The reason is determining majority is impossible if the electorate isn’t well defined in advance of the vote. In this case, the electorate is the core team who were selected by their peers to serve as the leadership of the project.

Re: [openstack-dev] [networking-cisco] Poll to decide networking-cisco weekly meeting times

My interpretation of the guidelines was that those channels are reserved for official OpenStack projects (projects included in governance projects.yaml) only, so until we regain that status I was planning on holding it in the project channel. If this isn't the case and we can use the

Re: [openstack-dev] [tripleo] let's talk (development) environment deployment tooling and workflows

On Mon, Sep 19, 2016 at 11:21 AM, Steven Hardy wrote: > Hi Alex, > > Firstly, thanks for this detailed feedback - it's very helpful to have > someone with a fresh perspective look at the day-1 experience for TripleO, > and while some of what follows are "know issues", it's

Re: [openstack-dev] [nova] ops meetup feedback

On Tue, Sep 20, 2016 at 11:36:29AM -0400, Sean Dague wrote: > On 09/20/2016 11:20 AM, Daniel P. Berrange wrote: > > On Tue, Sep 20, 2016 at 11:01:23AM -0400, Sean Dague wrote: > >> On 09/20/2016 10:38 AM, Daniel P. Berrange wrote: > >>> On Tue, Sep 20, 2016 at 09:20:15AM -0400, Sean Dague wrote: >

Re: [openstack-dev] Too many mails on announce list again :)

Excerpts from Thierry Carrez's message of 2016-09-20 10:19:04 +0200: > Steve Martinelli wrote: > > I think bundling the puppet, ansible and oslo releases together would > > cut down on a considerable amount of traffic. Bundling or grouping new > > releases may not be the most accurate, but if it

Re: [openstack-dev] [nova] ops meetup feedback

On Tue, Sep 20, 2016 at 04:20:49PM +0100, Daniel P. Berrange wrote: > On Tue, Sep 20, 2016 at 11:01:23AM -0400, Sean Dague wrote: [...] > > Here is my reconstruction of the snapshot issue from what I can remember > > of the conversation. > > > > Nova defaults to live snapshots. This uses the

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

On Tue, Sep 20, 2016 at 9:06 AM, Duncan Thomas wrote: > On 20 September 2016 at 16:24, Nikita Konovalov > wrote: > >> Hi, >> >> From Sahara (and Hadoop workload in general) use-case the reason we used >> BDD was a complete absence of any

Re: [openstack-dev] [networking-cisco] Poll to decide networking-cisco weekly meeting times

Sam, Can this meeting instead be held in the normal openstack-meeting-1 -> 4 channels? Having one-off meetings in #openstack-networking-cisco is totally fine. Having standing team meetings there is atypical of OpenStack projects. The main value of using the opentack-meeting-1-4 channels is

Re: [openstack-dev] [nova] ops meetup feedback

On 09/20/2016 11:20 AM, Daniel P. Berrange wrote: > On Tue, Sep 20, 2016 at 11:01:23AM -0400, Sean Dague wrote: >> On 09/20/2016 10:38 AM, Daniel P. Berrange wrote: >>> On Tue, Sep 20, 2016 at 09:20:15AM -0400, Sean Dague wrote: This is a bit delayed due to the release rush, finally getting

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

Mathias, Thank you for voicing your opinion (and anyone is welcome to do that in Kolla), however, core reviewer votes are the only binding votes in the decision making process. Regards -steve From: Mathias Ewald Reply-To: "OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [nova] ops meetup feedback

On Tue, Sep 20, 2016 at 11:01:23AM -0400, Sean Dague wrote: > On 09/20/2016 10:38 AM, Daniel P. Berrange wrote: > > On Tue, Sep 20, 2016 at 09:20:15AM -0400, Sean Dague wrote: > >> This is a bit delayed due to the release rush, finally getting back to > >> writing up my experiences at the Ops

Re: [openstack-dev] [searchlight] Matt Borland Searchlight UI Core Nomination

+ 1 on both issues. Great work, Matt! On 9/19/16, 1:13 PM, "Tripp, Travis S" wrote: >Hello! > >I am nominating Matt Borland for Searchlight UI core. Matt has been >working on searchlight UI since we started it and he is the primary >author of the angular registration

Re: [openstack-dev] [nova] ops meetup feedback

On 20 Sep 2016, at 16:38, Sean Dague > wrote: ... There were also general questions about what scale cells should be considered at. ACTION: we should make sure workarounds are advertised better ACTION: we should have some document about "when cells"? This

Re: [openstack-dev] [puppet] weekly meeting #91

ack-weekly-meeting-20160920 > > See you tomorrow =) > > 2016-09-12 13:23 GMT-03:00 Emilien Macchi <emil...@redhat.com>: > >> Hi, >> >> Tomorrow we'll have our weekly meeting: >> https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160913

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

On 20 September 2016 at 16:24, Nikita Konovalov wrote: > Hi, > > From Sahara (and Hadoop workload in general) use-case the reason we used > BDD was a complete absence of any overhead on compute resources > utilization. > > The results show that the LVM+Local target

Re: [openstack-dev] [nova] ops meetup feedback

On 09/20/2016 10:38 AM, Daniel P. Berrange wrote: > On Tue, Sep 20, 2016 at 09:20:15AM -0400, Sean Dague wrote: >> This is a bit delayed due to the release rush, finally getting back to >> writing up my experiences at the Ops Meetup. >> >> Nova Feedback Session >> = >> >> We

Re: [openstack-dev] [api] API Usability study at Barcelona Summit

Hi Chris, Should we use the API WG meeting slot on Thursday to discuss the study? If so, I will send out details for a virtual room. Piet On 9/20/16, 3:39 AM, "Chris Dent" wrote: >On Mon, 19 Sep 2016, Kruithof Jr, Pieter wrote: > >> I was planning to run a

Re: [openstack-dev] [nova] ops meetup feedback

On Tue, Sep 20, 2016 at 09:20:15AM -0400, Sean Dague wrote: > This is a bit delayed due to the release rush, finally getting back to > writing up my experiences at the Ops Meetup. > > Nova Feedback Session > = > > We had a double session for Feedback for Nova from Operators,

Re: [openstack-dev] [nova]What is definition of critical bugfixes?

On 9/20/2016 4:25 AM, Rikimaru Honjo wrote: Hi All, I requested to review my patch in the last Weekly Nova team meeting.[1] In this meeting, Mr. Dan Smith said following things about my patch. * This patch is too large to merge in rc2.[2] * Fix after Newton and backport to newton and

Re: [openstack-dev] [nova] ops meetup feedback

On 09/20/2016 10:22 AM, Andrew Laski wrote: > Excellent writeup, thanks. Some comments inline. > > > On Tue, Sep 20, 2016, at 09:20 AM, Sean Dague wrote: >> >> >> Performance Bottlenecks >> --- >> >> * scheduling issues with Ironic - (this is a bug we got through during >>

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

Option 2 2016-09-20 16:07 GMT+02:00 Steven Dake (stdake) : > Consider this a reversal of my vote for Debian deprecation. > > Swapnil, thanks for bringing this fact to our attention. It was missing > from the original vote. I don’t know why I didn’t bring up Benedikt’s >

Re: [openstack-dev] [nova] ops meetup feedback

Excellent writeup, thanks. Some comments inline. On Tue, Sep 20, 2016, at 09:20 AM, Sean Dague wrote: > > > Performance Bottlenecks > --- > > * scheduling issues with Ironic - (this is a bug we got through during > the week after the session) > * live snapshots actually

Re: [openstack-dev] [nova] ops meetup feedback

> The current DB online data upgrade model feels *very opaque* to > ops. They didn't realize the current model Nova was using, and didn't > feel like it was documented anywhere. > ACTION: document the DB data lifecycle better for operators This is on me, so I'll take it. I've just thrown

[openstack-dev] [networking-sfc] OpenFlow version to use in the OVS agent

In the OVSSfcAgent migration to a L2 agent extension review[1], Igor Duarte Cardoso noticed a difference on the OpenFlow versions between a comment and actual code. In current code [2], we have: # We need to dump-groups according to group Id, # which is a feature of OpenFlow1.5 full_args =

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

Consider this a reversal of my vote for Debian deprecation. Swapnil, thanks for bringing this fact to our attention. It was missing from the original vote. I don’t know why I didn’t bring up Benedikt’s contributions (which were substantial) just as Paul’s were substantial for Oracle Linux. I

[openstack-dev] [keystone] gate-keystoneclient-dsvm-functional-ubuntu-xenial is broken

Since September 14th the keystoneclient functional test job has been broken. Let's be mindful of infra resources and stop rechecking the patches there. Anyone have time to investigate this? See patches https://review.openstack.org/#/c/369469/ or https://review.openstack.org/#/c/371324/

Re: [openstack-dev] [nova] ops meetup feedback

On 16-09-20 09:20 AM, Sean Dague wrote: This is a bit delayed due to the release rush, finally getting back to writing up my experiences at the Ops Meetup. Nova Feedback Session = We had a double session for Feedback for Nova from Operators, raw etherpad here -

Re: [openstack-dev] [cinder][sahara] LVM vs BDD drivers performance tests results

Hi, >From Sahara (and Hadoop workload in general) use-case the reason we used BDD was a complete absence of any overhead on compute resources utilization. The results show that the LVM+Local target perform pretty close to BDD in synthetic tests. It's a good sign for LVM. It actually shows that

[openstack-dev] [Nova] Live migration IRC meeting

There will be a live migration meeting today – agenda and time here: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [nova] ops meetup feedback

This is a bit delayed due to the release rush, finally getting back to writing up my experiences at the Ops Meetup. Nova Feedback Session = We had a double session for Feedback for Nova from Operators, raw etherpad here - https://etherpad.openstack.org/p/NYC-ops-Nova. The

[openstack-dev] [release][requirements] requirements repo stable/newton branch created

I have created the stable/newton branch in the openstack/requirements repository. It should now be possible to recheck and successfully merge updates to the constraints settings in the tox.ini files for project stable/newton branches. Doug

Re: [openstack-dev] [cinder] moving driver to open source

Erlon, There are exceptions to this rule ((e.g. libraries used for testing), but the general result of the thread is that all python libraries imported by the drivers must conform to OpenStack licensing. That includes Apache and several other licenses (e.g. MIT, LGPL). Alon On Tue, Sep

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

2016-09-20 13:27 GMT+02:00 Kashyap Chamarthy : >> (3) Do nothing, leave the bug unfixed in stable/liberty > > That was the unspoken third option, thanks for spelling it out. :-) Yes, let's abandon both reviews. Cheers, Alan

Re: [openstack-dev] [nova] TL; DR A proposed subsystem maintainer model

Le 20/09/2016 13:07, Matthew Booth a écrit : * +A is reserved for cores. * A subsystem maintainer's domain need not be defined by the directory tree: subteams are a good initial model. * A maintainer should only +2 code in their own domain in good faith, enforced socially, not

[openstack-dev] [networking-cisco] Poll to decide networking-cisco weekly meeting times

For those interested in participating, we are setting up a weekly meeting to discuss the development and design of networking-cisco. This meeting will be held on the #openstack-networking-cisco channel. If you are interested please use the link below to provide which of the dates and times you

Re: [openstack-dev] [cinder] moving driver to open source

On Tue, Sep 20, 2016 at 8:50 AM, Alon Marx wrote: > > From deployment stand point the desire is to have any piece of code that > is required on an openstack installation would be easily downloadable. > And redistributable please. -- *Avishay Traeger, PhD* *System

Re: [openstack-dev] [nova] TL; DR A proposed subsystem maintainer model

On 09/20/2016 07:07 AM, Matthew Booth wrote: > * +A is reserved for cores. > > * A subsystem maintainer's domain need not be defined by the directory > tree: subteams are a good initial model. > > * A maintainer should only +2 code in their own domain in good faith, > enforced socially, not

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

On Tue, Sep 20, 2016 at 11:57:26AM +0100, Daniel P. Berrange wrote: > On Tue, Sep 20, 2016 at 12:48:49PM +0200, Kashyap Chamarthy wrote: [...] > > The two options at hand: > > > > (1) Nova backport from master (that also adds a check for the presence > > of 'ProcessLimits' attribute which

[openstack-dev] [nova] TL; DR A proposed subsystem maintainer model

* +A is reserved for cores. * A subsystem maintainer's domain need not be defined by the directory tree: subteams are a good initial model. * A maintainer should only +2 code in their own domain in good faith, enforced socially, not technically. * Subsystem maintainer is expected to request

Re: [openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

On Tue, Sep 20, 2016 at 12:48:49PM +0200, Kashyap Chamarthy wrote: > The said patch in question fixes a CVE[x] in stable/liberty. > > We currently have two options, both of them have caused an impasse with > the Nova upstream / stable maintainers. We've had two-ish months to > mull over this.

[openstack-dev] [nova][stable/liberty] Backport impasse: "virt: set address space & CPU time limits when running qemu-img"

The said patch in question fixes a CVE[x] in stable/liberty. We currently have two options, both of them have caused an impasse with the Nova upstream / stable maintainers. We've had two-ish months to mull over this. I'd prefer to get this out of a limbo, & bring this to a logical conclusion.

Re: [openstack-dev] [cinder] moving driver to open source

On Tue, Sep 20, 2016 at 5:23 AM, Thierry Carrez wrote: > Alon Marx wrote: > > Thank you ALL for clearing up this issue. > > > > To sum up the discussion (not going into too many details): > > From legal stand point, if one uses python libraries they should be part > > of

Re: [openstack-dev] [tc]a chance to meet all TCs for Tricircle big-tent application in Barcelona summit?

joehuang wrote: > Hello, all TCs, > > Understand that you will be quite busy in Barcelona summit, all TCs will > be shown in the Barcelona summit, and meet together(usually, I assumed). > So is it possible to have a chance to meet all TCs there for Tricircle > big-tent application

Re: [openstack-dev] [infra]project description not updated in github repository

On 09/20/2016 09:39 AM, joehuang wrote: Hello, The project description of has not been updated in in github repository even if the description was updated in gerrit/projects.yaml In following patch, the Tricircle project description has been updated from "Tricircle is a project for OpenStack

Re: [openstack-dev] [api] API Usability study at Barcelona Summit

On Mon, 19 Sep 2016, Kruithof Jr, Pieter wrote: I was planning to run a usability study on behalf of the API working group at the Barcelona summit.     The plan is to have operators complete a set of common tasks, such as adjusting quotas, using the projects APIs. Since you're intending to

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

If it's the case Benedict or noone else is interested in continuing Debian, I can reverse my vote. Though it seems I'll be outvoted anyway ;) On 20/09/16 10:21, Swapnil Kulkarni wrote: On Tue, Sep 20, 2016 at 2:38 PM, Paul Bourke wrote: -1 for deprecating Debian. As

[openstack-dev] [nova]What is definition of critical bugfixes?

Hi All, I requested to review my patch in the last Weekly Nova team meeting.[1] In this meeting, Mr. Dan Smith said following things about my patch. * This patch is too large to merge in rc2.[2] * Fix after Newton and backport to newton and mitaka.[3] In my understanding, we can backport only

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

On Tue, Sep 20, 2016 at 2:38 PM, Paul Bourke wrote: > -1 for deprecating Debian. > > As I mentioned in https://review.openstack.org/#/c/369183/, Debian support > was added incrementally by Benedikt Trefzer as recently as June. So it's > reasonable to believe there is at

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

-1 for deprecating Debian. As I mentioned in https://review.openstack.org/#/c/369183/, Debian support was added incrementally by Benedikt Trefzer as recently as June. So it's reasonable to believe there is at least one active user of Debian. I would like to try get some input from him on

Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

+1 On 19/09/16 18:40, Jeffrey Zhang wrote: Kolla core reviewer team, Kolla supports multiple Linux distros now, including * Ubuntu * CentOS * RHEL * Fedora * Debian * OracleLinux But only Ubuntu, CentOS, and OracleLinux are widely used and we have robust gate to ensure the quality. For

Re: [openstack-dev] [Neutron] Adding ihrachys to the neutron-drivers team

Congratulations Ihar!, well deserved through hard work! :) On Mon, Sep 19, 2016 at 8:03 PM, Brian Haley wrote: > Congrats Ihar! > > -Brian > > > On 09/17/2016 12:40 PM, Armando M. wrote: >> >> Hi folks, >> >> I would like to propose Ihar to become a member of the Neutron

Re: [openstack-dev] [horizon] Browser Support

Agreed. I've created a bug here: https://bugs.launchpad.net/horizon/+bug/1625514 Rob On 20 September 2016 at 09:40, amot...@gmail.com > wrote: I think It is time to merge the wiki into horizon devref. It is not a good

Re: [openstack-dev] [Keystone] Listing Domain roles (or retrieving them by name)

Hello, On 09/20/2016 10:15 AM, Johannes Grassler wrote: is there a canonical way to either * list roles in a given domain * or retrieve a role from a given domain by name (preferred) Looks like there is a way: osc_lib.utils.find_resource(admin_client.roles, role_name,

[openstack-dev] [ceilometer] Release critical fixes for Newton

Hi, We have two critical bugs that needs to be reviewed and fixed here for Ceilometer: Move oslo.db to hard requirements list https://review.openstack.org/#/c/372148/ Remove left over from old ceilometer-api binary https://review.openstack.org/#/c/372146/ Can we have reviews and then

Re: [openstack-dev] [cinder] moving driver to open source

Alon Marx wrote: > Thank you ALL for clearing up this issue. > > To sum up the discussion (not going into too many details): > From legal stand point, if one uses python libraries they should be part > of the community or confirming with the relevant licenses >

Re: [openstack-dev] Too many mails on announce list again :)

Steve Martinelli wrote: > I think bundling the puppet, ansible and oslo releases together would > cut down on a considerable amount of traffic. Bundling or grouping new > releases may not be the most accurate, but if it encourages the right > folks to read the content instead of brushing it off, I

[openstack-dev] [Keystone] Listing Domain roles (or retrieving them by name)

Hello, is there a canonical way to either * list roles in a given domain * or retrieve a role from a given domain by name (preferred) keystoneclient.v3.roles.RoleManager.list() does not appear to do the trick. While it takes a `domain` argument, it only returns roles with a domain_id=None

Re: [openstack-dev] [horizon] Browser Support

As you've noticed, this doc isn't updated currently. The current browsers supported are listed here: http://docs.openstack.org/developer/horizon/faq.html (Stable Firefox and Chrome, and IE 11+) Rob On 20 September 2016 at 08:23, Shinobu Kinjo >

Re: [openstack-dev] [horizon] Browser Support

There are ambiguous definitions like: IE 11 Good? Can we define this description as specific as possible? On Tue, Sep 20, 2016 at 4:15 PM, Radomir Dopieralski wrote: > On Tue, Sep 20, 2016 at 3:53 AM, Jason Rist wrote: >> >> This page hasn't been

Re: [openstack-dev] [horizon] Browser Support

On Tue, Sep 20, 2016 at 3:53 AM, Jason Rist wrote: > This page hasn't been updated for a while - does anyone know the latest? > > https://wiki.openstack.org/wiki/Horizon/BrowserSupport > > As far as I know, there were no changes to the officially supported browser versions.

Re: [openstack-dev] [release][mistral] mistral Newton RC1 available

Yes, we came up with a solution for this issue. Should be solved shortly. Renat Akhmerov @Nokia > On 20 Sep 2016, at 00:28, Lingxian Kong wrote: > > Thanks Dougal for reporting that, we are working on the issue. > > Cheers, > Lingxian Kong (Larry) > > > On Fri, Sep 16,

Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

Fwiw Swapnil, I think having a solid fedora implementation would be fantastic to help manage the transition to centos8 whenever that happens. At this point nobody has stepped up to do the work. We can always revisit any policy or vote in the future if the environment changes (i.e. you are

[openstack-dev] [nova][bugs] Nova Bugs Team Meeting this Tuesday at 1800 UTC

The next Nova Bugs Team meeting will be Tuesday, September 20 at 1800 UTC in #openstack-meeting-4 http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160920T18 Feel free to add to the meeting agenda: https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam -- Augustina Ragwitz Señora