Re: [openstack-dev] [vitrage] Synchronizer - explanation and name refactoring

Great, I think it is much more clear now. I also think we should rename SyncMode and SyncType, these names are confusing. > -Original Message- > From: EXT Har-Tal, Liat (Nokia - IL) [mailto:liat.har-...@nokia.com] > Sent: Monday, April 11, 2016 9:44 AM > To: openstack-dev@lists.openstack.o

[openstack-dev] [glance][reno] Broken releasenotes in glance_store

I've noticed that the translation bot fails extracting strings from the release notes: https://jenkins.openstack.org/job/glance_store-propose-translation-update/203/console I could reproduce this with running "tox -e releasenotes" locally on glance_store. Could you check what's broken - and figure

Re: [openstack-dev] [Nova] RFC Host Maintenance

Hi, Looking the discussion so far: -Suggestion to have extended information for maintenance to somewhere outside Nova. -Notification about Nova state changes. So how about if the whole logic of maintenance would be triggered by Nova API disable/enable service notification, but otherwise the bu

[openstack-dev] [kolla][vote] Nit-picking documentation changes

Hey folks, The reviewers in Kolla tend to nit-pick the quickstart guide to death during reviews. I'd like to keep that high bar in place for the QSG, because it is our most important piece of documentation at present. However, when new contributors see the nitpicking going on in reviews, I th

Re: [openstack-dev] [kolla][vote] Nit-picking documentation changes

Hi Steven, On Mon, Apr 11, 2016 at 3:37 PM, Steven Dake (stdake) wrote: > However, when new > contributors see the nitpicking going on in reviews, I think they may get > discouraged about writing documentation for other parts of Kolla. This is one of the things I experienced myself and this thou

Re: [openstack-dev] [all][elections] Results of the TC Election

Jeremy Stanley wrote: On 2016-04-08 14:04:15 + (+), gordon chung wrote: [...] understandably it's more difficult to manage a large group of cores, but it does seem strange that all the projects have roughly the same core team size even though some projects have a contributor base that is

[openstack-dev] [Glance] How to add location in the image

Hi All, I created image and I want to add location in the created image. For that I am executing this command from glance cli. usage: glance --os-image-api-version 2 location-add --url [--metadata ] So here what is the . What should I pass to add the location. Please anybody can help me out

Re: [openstack-dev] [kolla][vote] Nit-picking documentation changes

On 4/11/16, 12:54 AM, "Gerard Braad" wrote: >Hi Steven, > >On Mon, Apr 11, 2016 at 3:37 PM, Steven Dake (stdake) >wrote: >> However, when new >> contributors see the nitpicking going on in reviews, I think they may >>get >> discouraged about writing documentation for other parts of Kolla. > >T

Re: [openstack-dev] [TripleO] [CI] Tempest configuration in Tripleo CI jobs

Hi, Andrey I've checked this option - to use rally for configuring and running tempest test. Although it looks like great choice, unfortunately a few issues and bugs makes it not useful right now. For example it can not work with current public networks and can not create new ones, so that everyth

Re: [openstack-dev] [Glance] How to add location in the image

It must be valid http reference to image file that can be downloaded by Glance. For example: http://cdimage.debian.org/cdimage/openstack/testing/debian-testing-openstack-amd64.qcow2 You can also ask similar questions in #openstack-glance IRC channel. Best regards, Kairat Kushaev On Mon, Apr 11,

[openstack-dev] How to execute Name space in glance in liberty

Hi Team, Please guide me that how to execute the below commands What to pass in place of glance --os-image-api-version 2 md-namespace-create Ref : http://docs.openstack.org/cli-reference/glance.html#glance-md-namespace-create-v2 glance --os-image-api-version 2 md-resource-type-associate

Re: [openstack-dev] [kolla][vote] Nit-picking documentation changes

Hi, On Mon, Apr 11, 2016 at 4:20 PM, Steven Dake (stdake) wrote: > On 4/11/16, 12:54 AM, "Gerard Braad" wrote: > as >>at the moment getting an environment up-and-running according to the >>quickstart guide is a hit and miss > I don't think deployment is not hit or miss as long as the QSG are > f

[openstack-dev] [ironic] [api] Fixing bugs in old microversions

Hi all! There is a bug in ironic API that allows to remove node name using any API version, while node names were added in version 1.5. There are concerns that fixing this might be a breaking change, and I'm not sure how to proceed with that. Here i

Re: [openstack-dev] [kolla][vote] Nit-picking documentation changes

On 4/11/16, 1:38 AM, "Gerard Braad" wrote: >Hi, > >On Mon, Apr 11, 2016 at 4:20 PM, Steven Dake (stdake) >wrote: >> On 4/11/16, 12:54 AM, "Gerard Braad" wrote: >> as >>>at the moment getting an environment up-and-running according to the >>>quickstart guide is a hit and miss >> I don't think

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalyticsstats

> From: Masayuki Igawa > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 04/11/2016 03:20 AM > Subject: Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats > > 2016-04-11 9:46 GMT+09:00 Matt Riedemann : > > > > > > On 4/10/2016 6:37 PM, Clint Byru

Re: [openstack-dev] [heat] convergence cancel messages

On 14-Mar-16 14:40, Anant Patil wrote: > On 24-Feb-16 22:48, Clint Byrum wrote: >> Excerpts from Anant Patil's message of 2016-02-23 23:08:31 -0800: >>> Hi, >>> >>> I would like the discuss various approaches towards fixing bug >>> https://launchpad.net/bugs/1533176 >>> >>> When convergence is on,

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

On Sun, Apr 10, 2016 at 10:07 AM, Moshe Levi wrote: > > > > > *From:* Miguel Angel Ajo Pelayo [mailto:majop...@redhat.com] > *Sent:* Friday, April 08, 2016 4:17 PM > *To:* OpenStack Development Mailing List (not for usage questions) < > openstack-dev@lists.openstack.org> > *Subject:* [openstack-d

[openstack-dev] [mistral] Team meeting reminder - 04/11/2016

Hi Mistral team, This is a reminder that we’ll have a team meeting today at 16.00 UTC at #openstack-meeting. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) Proposals for summit topics https://etherpad.openstack.org/p/mistral-austin-summit-topics-2106

[openstack-dev] [mistral] Mistral Austin Summit topics

Hi, Please leave your suggestions for what to discuss in Austin at https://etherpad.openstack.org/p/mistral-austin-summit-topics-2106 . Now it’s blank but don’t hesitate to add anything you need. Renat Akhmerov @Nokia ___

Re: [openstack-dev] [TripleO] Austin summit sessions

On Tue, Apr 05, 2016 at 05:25:48PM +0100, Steven Hardy wrote: > All, > > As discussed briefly today in our weekly meeting, I've started this > etherpad: > > https://etherpad.openstack.org/p/newton-tripleo-sessions > > We have two fishbowl sessions and 3 working sessions, plus a half-day > contri

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

gordon chung wrote: On 08/04/2016 1:26 PM, Davanum Srinivas wrote: Steve pointed out to a problem in Stackalytics: https://twitter.com/stevebot/status/718185667709267969 It's pretty clear what's happening if you look here: https://review.openstack.org/#/q/owner:openstack-infra%2540lists.opensta

Re: [openstack-dev] [ironic] [inspector] Proposing Anton Arefiev (aarefiev) for ironic-inspector-core

+1 from me too :D Sam On 05/04/2016 17:45, "Jim Rollenhagen" wrote: >+1 from me :) > >// jim > >> On Apr 5, 2016, at 03:24, Dmitry Tantsur wrote: >> >> Hi! >> >> I'd like to propose Anton to the ironic-inspector core reviewers team. >>His stats are pretty nice [1], he's making meaningful

Re: [openstack-dev] [magnum][requirements][release] The introduction of package py2-ipaddress

Hongbin Lu wrote: Hi requirements team, In short, the recently introduced package py2-ipaddress [1] seems to break Magnum. In details, Magnum gate recently broke by an error: “'\xac\x18\x05\x07' does not appear to be an IPv4 or IPv6 address” [2] (the gate breakage has been temporarily fixed but

Re: [openstack-dev] [all][elections] Results of the TC Election

On Fri, Apr 08, 2016 at 03:14:33PM +0200, Thierry Carrez wrote: [...] > Long term I'd like to remove the summit pass perk (or no longer link > it to "one commit"). Agreed. FWIW, I recall discussing this in the hallways of the Paris Summit, and suggesting something like 3-5 commits and someway t

Re: [openstack-dev] [Neutron] OVS flow modification performance

At Fri, 8 Apr 2016 12:21:21 +0200, Miguel Angel Ajo Pelayo wrote: > > Hi, good that you're looking at this, > > > You could create a lot of ports with this method [1] and a bit of extra > bash, without the extra expense of instance RAM. > > > [1] > http://www.ajo.es/post/89207996034/creating-a

Re: [openstack-dev] [Ironic] Failed to update Neutron port

Looking at the errors here it appears that everything is configured correctly in Ironic (mac addresses etc) because you are getting through the ramdisk boot and deploy successfully. The error that is of real concern here is "Unauthorized: {"error": {"message": "The resource could not be found."

[openstack-dev] [TripleO] Can we create some subteams?

Hola OOOers, It came up in the meeting last week that we could benefit from a CI subteam with its own meeting, since CI is taking up a lot of the main meeting time. I like this idea, and think we should do something similar for the other informal subteams (tripleoclient, UI), and also add a new s

[openstack-dev] [TripleO] Propose Lars Kellogg-Stedman for tripleo-quickstart core

Hello again, This is semi-related to the subteam thread, but deserves its own. I would like to give Lars +2 on tripleo-quickstart. He has contributed almost as much as I have to the project in terms of LOC, and in terms of real impact probably more. He is responsible for some of the best features

[openstack-dev] [Neutron][Infra] Post processing of gate hooks on job timeouts

Hi, recently we hit an issue in Neutron with tests getting stuck [1]. As a side effect we discovered logs are not collected properly which makes it hard to find the root cause. The reason of missing logs is that we send SIGKILL to whatever gate hook is running when we hit the global timeout per ga

Re: [openstack-dev] [TripleO] Can we create some subteams?

On Mon, Apr 11, 2016 at 05:54:11AM -0400, John Trowbridge wrote: > Hola OOOers, > > It came up in the meeting last week that we could benefit from a CI > subteam with its own meeting, since CI is taking up a lot of the main > meeting time. > > I like this idea, and think we should do something si

Re: [openstack-dev] [TripleO] Propose Lars Kellogg-Stedman for tripleo-quickstart core

On Mon, Apr 11, 2016 at 06:06:03AM -0400, John Trowbridge wrote: > Hello again, > > This is semi-related to the subteam thread, but deserves its own. > > I would like to give Lars +2 on tripleo-quickstart. He has contributed > almost as much as I have to the project in terms of > LOC, and in term

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalyticsstats

Markus Zoeller wrote: From: Masayuki Igawa To: "OpenStack Development Mailing List (not for usage questions)" Date: 04/11/2016 03:20 AM Subject: Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats 2016-04-11 9:46 GMT+09:00 Matt Riedemann : On 4/10/2016 6:37 PM, Clint Byru

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

Clint Byrum wrote: Excerpts from Morgan Fainberg's message of 2016-04-10 16:47:28 -0700: On Sun, Apr 10, 2016 at 4:37 PM, Clint Byrum wrote: Excerpts from Matt Riedemann's message of 2016-04-09 06:42:54 -0700: There is also disincentive in +1ing a change that you don't understand and is wr

[openstack-dev] [trove] call to action: blueprints awaiting review

There are several blueprints for Trove that are awaiting review [1]. Many of these are targeted for Newton, some were originally started for Mitaka but missed the deadlines and are still being considered for Newton. Would all reviewers please take a look at these and provide feedback. Several o

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

Hi Miguel Angel, comments/answers inline :) On 04/08/2016 09:17 AM, Miguel Angel Ajo Pelayo wrote: Hi!, In the context of [1] (generic resource pools / scheduling in nova) and [2] (minimum bandwidth guarantees -egress- in neutron), I had a talk a few weeks ago with Jay Pipes, The idea

Re: [openstack-dev] [ironic] [api] Fixing bugs in old microversions

On 04/11/2016 04:48 AM, Vladyslav Drok wrote: Hi all! There is a bug in ironic API that allows to remove node name using any API version, while node names were added in version 1.5. There are concerns that fixing this might be a breaking change, a

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

On 09/04/16 22:31 +, Amrith Kumar wrote: Thanks to Dims and Steve for bringing this up. It has long been my opinion that +0's are invaluable for the question asking, and for getting to understand software, and unfortunately +0's are lost in the noise. So a while ago, I posted to th

Re: [openstack-dev] [release][puppet] Puppet OpenStack 8.0.0 release (mitaka)

On Mon, Apr 11, 2016 at 1:57 AM, Marcus Furlong wrote: > On 29 March 2016 at 09:53, Emilien Macchi wrote: >> Puppet OpenStack team has the immense pleasure to announce the release >> of 24 Puppet modules. > > Great to hear that :) Just wondering if there is a timeline for when these > modules wil

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

On Mon, Apr 11, 2016 at 6:48 AM, Ihar Hrachyshka wrote: > Clint Byrum wrote: > > Excerpts from Morgan Fainberg's message of 2016-04-10 16:47:28 -0700: >> >>> On Sun, Apr 10, 2016 at 4:37 PM, Clint Byrum wrote: >>> >>> Excerpts from Matt Riedemann's message of 2016-04-09 06:42:54 -0700: >>>

Re: [openstack-dev] [Neutron] OVS flow modification performance

On Mon, Apr 11, 2016 at 11:40 AM, IWAMOTO Toshihiro wrote: > At Fri, 8 Apr 2016 12:21:21 +0200, > Miguel Angel Ajo Pelayo wrote: >> >> Hi, good that you're looking at this, >> >> >> You could create a lot of ports with this method [1] and a bit of extra >> bash, without the extra expense of instan

Re: [openstack-dev] [all][stackalytics] Gaming the Stackalytics stats

On 11/04/2016 5:10 AM, Thierry Carrez wrote: > gordon chung wrote: >> On 08/04/2016 1:26 PM, Davanum Srinivas wrote: >>> Steve pointed out to a problem in Stackalytics: >>> https://twitter.com/stevebot/status/718185667709267969 >>> >>> It's pretty clear what's happening if you look here: >>> http

[openstack-dev] [release][tripleo] os-net-config 0.2.4 release

We are gleeful to announce the release of: os-net-config 0.2.4: OpenStack network configuration With source available at: http://git.openstack.org/cgit/openstack/os-net-config With package available at: https://pypi.python.org/pypi/os-net-config Please report issues through launchpad:

[openstack-dev] [release][openstack] os-client-config 1.17.0 release (newton)

We are chuffed to announce the release of: os-client-config 1.17.0: OpenStack Client Configuation Library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/os-client-config With package available at: https://pypi.pytho

[openstack-dev] [release][stable][senlin] senlin-dashboard 0.2.1 release (mitaka)

We are delighted to announce the release of: senlin-dashboard 0.2.1: Senlin Dashboard This release is part of the mitaka stable release series. Please report issues through launchpad: https://bugs.launchpad.net/senlin-dashboard For more details, please see below. Changes in senlin-dashboa

[openstack-dev] [release][cinder] os-brick 1.3.0 release (newton)

We are overjoyed to announce the release of: os-brick 1.3.0: OpenStack Cinder brick library for managing local volume attaches This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/os-brick With package available at: https

Re: [openstack-dev] [kolla][vote] Nit-picking documentation changes

So one way to approach it is to decouple docs from code, make it 2 reviews. We can -1 code without docs and ask to create separate patchset depending on one in question with docs. Then we can nitpick all we want:) new contributor will get his/hers code merged, at least one patchset, so it will work

[openstack-dev] [Security][Keystone] OSSN-0064 Draft. Request for review

Hi Guys, OSSN-0064 is in review and requires some Keystone love. https://review.openstack.org/#/c/300091/ In relation to: https://bugs.launchpad.net/ossn/+bug/1545789 Cheers -Rob __ OpenStack Development Mailing List (not

Re: [openstack-dev] [Infra] Gerrit performance

Guys, My twitter-status was published long time ago and it is more about how bad gerrit is itself. I know you are doing your best to make it work. Thanks a lot for your work! On Sun, Apr 10, 2016 at 3:52 PM, Jeremy Stanley wrote: > On 2016-04-10 12:43:06 +0300 (+0300), Andrey Kurilin wrote: >

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

Ping. -Original Message- From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com] Sent: Friday, April 08, 2016 4:24 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Cao, Shufeng/曹 树烽; doug...@parkside.io Subject: [openstack-dev] [neutron] [API]Make API errors conform to th

[openstack-dev] [oslo] Removing Nova specifics from oslo.log

Hi, There's a lot of assumption in oslo.log about Nova, such as talking about "instance" and "context" in a lot of the code by default. There's even a dependency on oslo.context. >.< That's being an issue for projects not being Nova, where we end up having configuration options talking about "ins

Re: [openstack-dev] [Neutron][Infra] Post processing of gate hooks on job timeouts

On 4/11/16, 5:07 AM, "Jakub Libosvar" wrote: >Hi, > >recently we hit an issue in Neutron with tests getting stuck [1]. As a >side effect we discovered logs are not collected properly which makes it >hard to find the root cause. The reason of missing logs is that we send >SIGKILL to whatever

Re: [openstack-dev] [ironic] [api] Fixing bugs in old microversions

On 04/11/2016 02:00 PM, Jay Pipes wrote: On 04/11/2016 04:48 AM, Vladyslav Drok wrote: Hi all! There is a bug in ironic API that allows to remove node name using any API version, while node names were added in version 1.5. There are concerns that

[openstack-dev] [board][tc][all] One Platform – Containers/Bare Metal? (Re: [OpenStack Foundation] Board of Directors Meeting)

Hi, I haven't heard back on this email from last week. So, trying with new email subject/tags and cc'ing foundation ML. Can folks who were there please respond? Thanks, Dims On Wed, Apr 6, 2016 at 1:11 PM, Davanum Srinivas wrote: > Hi, > > Reading unofficial notes [1], i found one topic very i

Re: [openstack-dev] [ironic] [api] Fixing bugs in old microversions

On 04/11/2016 10:48 AM, Vladyslav Drok wrote: Hi all! There is a bug in ironic API that allows to remove node name using any API version, while node names were added in version 1.5. There are concerns that fixing this might be a breaking change, a

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

So by adding the handling of a header to change the behaviour of the API, you're basically implementing a subset of microversions, with a non-standard header (See the API WG spec on non-proliferation of headers). You'll find it takes much of the work that implementing microversions does, and explod

Re: [openstack-dev] [ironic] [api] Fixing bugs in old microversions

On 04/11/2016 09:48 AM, Dmitry Tantsur wrote: On 04/11/2016 02:00 PM, Jay Pipes wrote: On 04/11/2016 04:48 AM, Vladyslav Drok wrote: Hi all! There is a bug in ironic API that allows to remove node name using any API version, while node names wer

Re: [openstack-dev] [ironic] [api] Fixing bugs in old microversions

On 04/11/2016 03:54 PM, Jay Pipes wrote: On 04/11/2016 09:48 AM, Dmitry Tantsur wrote: On 04/11/2016 02:00 PM, Jay Pipes wrote: On 04/11/2016 04:48 AM, Vladyslav Drok wrote: Hi all! There is a bug in ironic API that allows to remove node name u

Re: [openstack-dev] [oslo] Removing Nova specifics from oslo.log

On 04/11/2016 08:38 AM, Julien Danjou wrote: > There's a lot of assumption in oslo.log about Nova, such as talking > about "instance" and "context" in a lot of the code by default. There's > even a dependency on oslo.context. >.< > > That's being an issue for projects not being Nova, where we end

Re: [openstack-dev] [ironic] [api] Fixing bugs in old microversions

On 04/11/2016 09:54 AM, Jay Pipes wrote: > On 04/11/2016 09:48 AM, Dmitry Tantsur wrote: >> On 04/11/2016 02:00 PM, Jay Pipes wrote: >>> On 04/11/2016 04:48 AM, Vladyslav Drok wrote: Hi all! There is a bug in ironic API that allow

Re: [openstack-dev] [oslo] Removing Nova specifics from oslo.log

On 04/11/2016 10:08 AM, Ed Leafe wrote: > On 04/11/2016 08:38 AM, Julien Danjou wrote: > >> There's a lot of assumption in oslo.log about Nova, such as talking >> about "instance" and "context" in a lot of the code by default. There's >> even a dependency on oslo.context. >.< >> >> That's being an

[openstack-dev] [keystone][performance][profiling] Profiling Mitaka Keystone: some results and asking for a help

Hey, openstackers! Recently I was trying to profile Keystone (OpenStack Liberty vs Mitaka) using this set of changes (that's currently on review - some final steps are required there to finish the work) and OSprofi

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

On 04/08/2016 03:23 AM, Xie, Xianshan wrote: > According to the discussion, a new header would be a good idea to resolve > this issue [4], we think. > For instance: > curl -X DELETE "http://xxx:9696/v2.0/networks/xxx"; -H > "Neutron-Common-Error-Format: True" > > But we haven't decided which he

[openstack-dev] [puppet] weekly meeting #78

Hi, We'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting4. https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack As usual, free free to bring topics in this etherpad: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160412 We'll also have open discussion

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

On Mon, Apr 11, 2016 at 1:46 PM, Jay Pipes wrote: > Hi Miguel Angel, comments/answers inline :) > > On 04/08/2016 09:17 AM, Miguel Angel Ajo Pelayo wrote: >> >> Hi!, >> >> In the context of [1] (generic resource pools / scheduling in nova) >> and [2] (minimum bandwidth guarantees -egress- in n

Re: [openstack-dev] [TripleO] Can we create some subteams?

On 04/11/2016 04:19 AM, Steven Hardy wrote: > On Mon, Apr 11, 2016 at 05:54:11AM -0400, John Trowbridge wrote: > > Hola OOOers, > > > > It came up in the meeting last week that we could benefit from a CI > > subteam with its own meeting, since CI is taking up a lot of the main > > meeting time. > >

Re: [openstack-dev] [Openstack-security] [Security]abandoned OSSNs?

Matt: Thanks for asking this. I forwarded this email to the new email list so that folks with better knowledge can answer this. Thanks and have a great day. Yours, Michael - Michael Xin | Manager, Security Engineering

Re: [openstack-dev] [TripleO] Can we create some subteams?

+1 from me too, we have it in Puppet OpenStack group, and it works just fine. On Mon, Apr 11, 2016 at 10:27 AM, Jason Rist wrote: > On 04/11/2016 04:19 AM, Steven Hardy wrote: >> On Mon, Apr 11, 2016 at 05:54:11AM -0400, John Trowbridge wrote: >> > Hola OOOers, >> > >> > It came up in the meeting

Re: [openstack-dev] [devstack][neutron] Eliminating the DevStack layer

Armando M. wrote: > My understanding of the plan to overhaul the neutron (bloated) layer > present in DevStack being tackled in [1] has always been that this was > about trimming the layer rather than eliminating it altogether. Is this > email a reflection of a desire to change direction? If so, Se

Re: [openstack-dev] [ironic] [api] Fixing bugs in old microversions

On 04/11/2016 10:11 AM, Sean Dague wrote: On 04/11/2016 09:54 AM, Jay Pipes wrote: On 04/11/2016 09:48 AM, Dmitry Tantsur wrote: On 04/11/2016 02:00 PM, Jay Pipes wrote: On 04/11/2016 04:48 AM, Vladyslav Drok wrote: Hi all! There is a bug in i

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

> On Wed, Apr 6, 2016 at 1:11 PM, Davanum Srinivas wrote: >> Reading unofficial notes [1], i found one topic very interesting: >> One Platform – How do we truly support containers and bare metal under >> a common API with VMs? (Ironic, Nova, adjacent communities e.g. >> Kubernetes, Apache Mesos et

Re: [openstack-dev] [TripleO] Can we create some subteams?

On 04/11/2016 06:19 AM, Steven Hardy wrote: > On Mon, Apr 11, 2016 at 05:54:11AM -0400, John Trowbridge wrote: >> Hola OOOers, >> >> It came up in the meeting last week that we could benefit from a CI >> subteam with its own meeting, since CI is taking up a lot of the main >> meeting time. >> >>

Re: [openstack-dev] [User-committee] [all] [app-catalog] Newton summit schedule

On Sat, Apr 9, 2016 at 8:41 AM, Yih Leong, Sun. wrote: > I think it needs to relate to 'workload'. > The Enterprise WG is working on a series of workload reference architecture. > These architecture documents will include sample Heat template for each type > of workload. We can work together and i

Re: [openstack-dev] [Openstack-security] [Security]abandoned OSSNs?

Thanks Matt, Michael, To start with, lets look quickly at the more recent OSSNs that are marked as work in progress, namely 63,64,65 and 66 – these should all be published within a week or so. Looking further back we have the more difficult OSSNs 50 and 51, I’m not 100% sure what the blockers

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

please forgive my lack of direct knowledge about the neutron process and how this fits in. i'm just commenting from the perspective of someone looking at this from the api-wg. On 04/11/2016 09:52 AM, Duncan Thomas wrote: So by adding the handling of a header to change the behaviour of the API,

[openstack-dev] [vitrage] Austin preparation

Hi all, Here are the tasks that we should finish for the Austin summit, with the current owners: - List of default Templates + testing - danoffek - Description support in Templates - ifat_afek / (or lhartal?) - Installation - First Steps Guide - elisha_r - Aodh – Installation requirements t

Re: [openstack-dev] [devstack][neutron] Eliminating the DevStack layer

Good news... the number of neutron options with a sane default value has increased significantly in the last couple of releases. If you're looking at the installation guide, it explicitly configures more options to override bad values set by distribution packages. For deployment tools, explicitly c

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

On 04/11/2016 09:43 AM, Allison Randal wrote: On Wed, Apr 6, 2016 at 1:11 PM, Davanum Srinivas wrote: Reading unofficial notes [1], i found one topic very interesting: One Platform – How do we truly support containers and bare metal under a common API with VMs? (Ironic, Nova, adjacent communiti

Re: [openstack-dev] [TripleO] Can we create some subteams?

On 04/11/2016 04:54 AM, John Trowbridge wrote: > Hola OOOers, > > It came up in the meeting last week that we could benefit from a CI > subteam with its own meeting, since CI is taking up a lot of the main > meeting time. > > I like this idea, and think we should do something similar for the othe

Re: [openstack-dev] [Neutron][Infra] Post processing of gate hooks on job timeouts

On Mon, Apr 11, 2016 at 9:39 AM, Morales, Victor wrote: > > > > > > On 4/11/16, 5:07 AM, "Jakub Libosvar" wrote: > >>Hi, >> >>recently we hit an issue in Neutron with tests getting stuck [1]. As a >>side effect we discovered logs are not collected properly which makes it >>hard to find the root c

[openstack-dev] [Rally] Term "workload" has two clashing meanings

Hi all, this is about terminology, we have term "workload" in Rally that appears in two clashing meanings: 1. module rally.plugins.workload which collects plugins for cross-VM testing 2. workload replaces term "scenario" in

Re: [openstack-dev] [Openstack-security] [Security]abandoned OSSNs?

On 04/11/2016 08:04 AM, Clark, Robert Graham wrote: > Thanks Matt, Michael, > > > > To start with, lets look quickly at the more recent OSSNs that are > marked as work in progress, namely 63,64,65 and 66 – these should all be > published within a week or so. > > > > Looking further back w

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

Monty, Dims, I read the notes and was similarly intrigued about the idea. In particular, from the perspective of projects like Trove, having a common Compute API is very valuable. It would allow the projects to have a single view of provisioning compute, as we can today with Nova and get the b

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

On 04/11/2016 11:11 AM, michael mccune wrote: > please forgive my lack of direct knowledge about the neutron process and > how this fits in. i'm just commenting from the perspective of someone > looking at this from the api-wg. > > On 04/11/2016 09:52 AM, Duncan Thomas wrote: >> So by adding the h

Re: [openstack-dev] [Openstack-security] [Security]abandoned OSSNs?

Hi, I believe 50 and 51 were both assigned to me. They were closely linked, but seperate issues. I wrote 50 up here: https://review.openstack.org/#/c/200303/2 After discussion in a security meeting, my memory is that it was agreed that they probably weren't required. I'd have to pull out the m

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

The more I've used Containers in production the more I've come to the conclusion they are much different beasts then Nova Instances. Nova's abstraction lets Physical hardware and VM's share one common API, and it makes a lot of sense to unify them. Oh. To be explicit, I'm talking about docker s

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

On Mon, Apr 11, 2016 at 11:30 AM, Monty Taylor wrote: > On 04/11/2016 09:43 AM, Allison Randal wrote: > >> On Wed, Apr 6, 2016 at 1:11 PM, Davanum Srinivas >>> wrote: >>> Reading unofficial notes [1], i found one topic very interesting: One Platform – How do we truly support containers

Re: [openstack-dev] [Neutron][Infra] Post processing of gate hooks on job timeouts

On Mon, Apr 11, 2016, at 03:07 AM, Jakub Libosvar wrote: > Hi, > > recently we hit an issue in Neutron with tests getting stuck [1]. As a > side effect we discovered logs are not collected properly which makes it > hard to find the root cause. The reason of missing logs is that we send > SIGKILL t

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

Amrith, I respect your point of view, and agree that the idea of a common compute API is attractive… until you think a bit deeper about what that would mean. We seriously considered a “global” compute API at the time we were first contemplating Magnum. However, what we came to learn through the

[openstack-dev] [nova] Encrypted Ephemeral Storage

I've been looking into using encrypted ephemeral storage with LVM. With the [ephemeral_storage_encryption] and [keymgr] sections to nova.conf, I get an LVM volume with "-dmcrypt" is appended to the volume name, but otherwise see no difference; I can still grep for text inside the volume. Upon read

Re: [openstack-dev] [TripleO] Can we create some subteams?

On Mon, Apr 11, 2016 at 10:33:53AM -0500, Ben Nemec wrote: > On 04/11/2016 04:54 AM, John Trowbridge wrote: > > Hola OOOers, > > > > It came up in the meeting last week that we could benefit from a CI > > subteam with its own meeting, since CI is taking up a lot of the main > > meeting time. > >

Re: [openstack-dev] [Cinder] About snapshot Rollback?

The actual user workflow is: 1 - User creates a volume(s) 2 - User attach volume to instance 3 - User creates a snapshot 4 - Something happens causing the need of a revert 5 - User creates a volume(s) from the snapshot(s) 6 - User detach old volumes 7 - User attach new volumes (and pray so

Re: [openstack-dev] [Cinder] About snapshot Rollback?

You can't just change the contents of a volume under the instance though - at the very least you need to do an unmount in the instance, and a detach is preferable, otherwise you've got data corruption issues. At that point, the device naming problems are identical. On 11 April 2016 at 20:22, Erlo

Re: [openstack-dev] [cinder][nova] Cinder-Nova API meeting

Hi All, It's a friendly reminder we're having the next Cinder-Nova API interactions meeting this Wednesday __13th April 2100UTC__, on the #openstack-meeting-cp channel. You can follow up the recent activities here: https://etherpad.openstack.org/p/cinder-nova-api-changes Our current focus is

Re: [openstack-dev] [TripleO] Can we create some subteams?

On 04/11/2016 05:33 PM, Ben Nemec wrote: On 04/11/2016 04:54 AM, John Trowbridge wrote: Hola OOOers, It came up in the meeting last week that we could benefit from a CI subteam with its own meeting, since CI is taking up a lot of the main meeting time. I like this idea, and think we should do

Re: [openstack-dev] [Neutron][Infra] Post processing of gate hooks on job timeouts

On Mon, Apr 11, 2016, at 10:52 AM, Jakub Libosvar wrote: > On 04/11/2016 06:41 PM, Clark Boylan wrote: > > On Mon, Apr 11, 2016, at 03:07 AM, Jakub Libosvar wrote: > >> Hi, > >> > >> recently we hit an issue in Neutron with tests getting stuck [1]. As a > >> side effect we discovered logs are not c

Re: [openstack-dev] [Neutron][Infra] Post processing of gate hooks on job timeouts

On 04/11/2016 06:41 PM, Clark Boylan wrote: > On Mon, Apr 11, 2016, at 03:07 AM, Jakub Libosvar wrote: >> Hi, >> >> recently we hit an issue in Neutron with tests getting stuck [1]. As a >> side effect we discovered logs are not collected properly which makes it >> hard to find the root cause. The

Re: [openstack-dev] [Openstack-security] [Security]abandoned OSSNs?

Thanks Michael, I'm following the thread and I've asked Thierry for this tag to be subscribable here if we're not using openstack-security anymore so that I can receive the follow-ups. On Mon, Apr 11, 2016 at 8:28 AM, Michael Xin wrote: > Matt: > Thanks for asking this. I forwarded this email

Re: [openstack-dev] [Cinder] About snapshot Rollback?

You are right, the instance should be shutdown or the device be unmounted, before 'revert' or removing the old device. That should be enough to avoid corruption. I think the device naming is not a problem if you use the same volume (at least the disk UUID will be the same). On Mon, Apr 11, 2016 at

[openstack-dev] [heat] upgrade options for custom heat resource plug-ins

Hi, We are developing a custom heat resource plug-in and wondering about how to handle plug-in upgrades. As our product's object model changes with new releases, we will need to release updated resource plug-in code too. However, the "properties" stored in the heat DB for the existing resources, w

Re: [openstack-dev] [OpenStack Foundation] [board][tc][all] One Platform – Containers/Bare Metal? (Re: Board of Directors Meeting)

Adrian, thx for your detailed mail. Yes, I was hopeful of a silver bullet and as we’ve discussed before (I think it was Vancouver), there’s likely no silver bullet in this area. After that conversation, and some further experimentation, I found that even if Trove had access to a single Compute

  1   2   >