Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

Tony Breeds wrote: On Tue, Jan 12, 2016 at 01:27:30PM +0100, Ihar Hrachyshka wrote: Agreed with Gary on behalf of my European compatriots. (Note that I *personally* +1’d the patch because I don’t mind, doing late hours anyway; but it’s sad it was ninja merged without

[openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

Hey all, I realize now from the title of the other TripleO/Mistral thread [1] that the discussion there may have gotten confused. I think using Mistral for TripleO processes that are obviously workflows - stack deployment, node registration - makes perfect sense. That thread is exploring

Re: [openstack-dev] [nova][neutron][os-vif] os-vif core review team membership

On Tue, Jan 12, 2016 at 10:28:49PM +, Mooney, Sean K wrote: > > -Original Message- > > From: Moshe Levi [mailto:mosh...@mellanox.com] > > Sent: Tuesday, January 12, 2016 4:23 PM > > To: Russell Bryant; Daniel P. Berrange; openstack- > > d...@lists.openstack.org > > Cc: Jay Pipes;

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

Eric, Patrick, Simon, Clark thanks for your comments. I don't know Heka, so that's why I ask a lot of questions. I hope you are fine with that:) I am not against Heka, I was just curious how reliable it is and how much experience you have with setting it up in Docker environment in order to

Re: [openstack-dev] [infra][all] "openstack-meeting-cp" == "openstack-meeting-5"?

Markus Zoeller wrote: Understood. Would it then be possible to create a new channel "openstack-meeting-5"? The short time span I have as an overlap with the US folks already uses all existing 4 meeting rooms. We limit the number of channels by design, to limit the number of concurrent

Re: [openstack-dev] [TripleO] Driving workflows with Mistral

Hi, Seems like most of the questions raised in the thread have been answered. Just some clarifications on Mistral+Zaqar from my side: Mistral integration with Zaqar still doesn’t exist although has been very much wanted for a while. In its most trivial form it’s just a matter of adding Zaqar

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

Hi Alicja Thank you for your comments. Answers and comments below. On Tue, Jan 12, 2016 at 1:19 PM, Kwasniewska, Alicja wrote: > Unfortunately I do not have any experience in working or testing Heka, so > it’s hard for me to compare its performance vs Logstash

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

On 12 Jan 2016 at 13:24:26, Kwasniewska, Alicja (alicja.kwasniew...@intel.com) wrote: Unfortunately I do not have any experience in working or testing Heka, so it’s hard for me to compare its performance vs Logstash performance. However I’ve read that Heka possess a lot advantages over

Re: [openstack-dev] [nova] config options: IRC meeting at Jan. 11th

Esra Celik wrote on 01/12/2016 12:55:25 PM: > From: Esra Celik > To: "OpenStack Development Mailing List (not for usage questions)" > , Markus Zoeller/Germany/IBM@IBMDE > Date: 01/12/2016 12:55 PM >

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

Kevin Benton wrote: The issue with this data is that who says something is not a good metric. For example, this shows that I attended more than twice as many afternoon meetings as the morning meetings when I know I actually only missed a couple of morning ones. I just

[openstack-dev] [nova] nova unit tests failing with os-win 0.1.0

This post is just to make you aware that there was an issue in the last 24 hours which might have hit your patches: https://bugs.launchpad.net/nova/+bug/1533290 Regards, Markus Zoeller (markus_z) __ OpenStack Development

[openstack-dev] [infra][all] "openstack-meeting-cp" == "openstack-meeting-5"?

Hi, I'd like to revive the nova-bugs-team IRC meeting and I'm looking for a channel to use. I've seen that there is an "openstack-meeting-cp" channel. The other channels are already in use for the timeslots I envisioned. Is this channel solely for (future) cross-project efforts or can I use it

Re: [openstack-dev] [infra][all] "openstack-meeting-cp" == "openstack-meeting-5"?

Markus Zoeller wrote: I'd like to revive the nova-bugs-team IRC meeting and I'm looking for a channel to use. I've seen that there is an "openstack-meeting-cp" channel. The other channels are already in use for the timeslots I envisioned. Is this channel solely for (future) cross-project efforts

[openstack-dev] [neutron] Testing Neutron with latest OVS

Hi all, recently I was working on firewall driver [1] that requires latest features in OVS, specifically conntrack support. In order to get the driver tested, we need to have the latest OVS kernel modules on machines running tests but AFAIK there is no stable "2.5 like" release of OVS yet.

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

The issue with this data is that who says something is not a good metric. For example, this shows that I attended more than twice as many afternoon meetings as the morning meetings when I know I actually only missed a couple of morning ones. I just don't say anything unless there is something that

[openstack-dev] [vitrage] Vitrage meeting minutes

Hi, You can find the meeting minutes of Vitrage meeting: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-13-09.00.html Meeting log: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-13-09.00.log.html See you next week, Ifat.

Re: [openstack-dev] [Bareon][Fuel] Dynamic allocation algorithm

Hi. Very good documentation. For Integer Solution you can use bytes instead of megabytes. Hence N bytes will be unallocated in the worst case. I didn't find solution for problem: - Don’t allocate a single volume on ssd and hdd Best regards, Svechnikov Artur On Tue, Jan 12, 2016 at 9:37

[openstack-dev] [magnum] Nesting /containers resource under /bays

I've recently been gathering feedback about the Magnum API and one of the things that people commented on? was the global /containers endpoints. One person highlighted the danger of UUID collisions: """ It takes a container ID which is intended to be unique within that individual cluster.

Re: [openstack-dev] [TripleO] Removing unused/deprecated template parameters?

On 01/13/2016 10:33 AM, Juan Antonio Osorio wrote: IIRC some of them were already marked (via a comment) as deprecated. +1 to cleaning up the parameters. I think it should be done as soon as possible, as the existence of some of them makes the usage of the templates quite confusing. BR On

[openstack-dev] [Nova] [Live Migration] topics for midcycle

Hi All, Following up on a question raised in the live migration meeting yesterday about organizing topics for the mid cycle: please add topic suggestions to https://etherpad.openstack.org/p/mitaka-nova-midcycle and we will review them in next week's meeting. Paul Paul Murray Technical Lead,

Re: [openstack-dev] [infra][all] "openstack-meeting-cp" == "openstack-meeting-5"?

Thierry Carrez wrote on 01/13/2016 10:44:04 AM: > From: Thierry Carrez > To: openstack-dev@lists.openstack.org > Date: 01/13/2016 10:44 AM > Subject: Re: [openstack-dev] [infra][all] "openstack-meeting-cp" == > "openstack-meeting-5"? > > Markus

Re: [openstack-dev] [keystone][security] New BP for anti brute force in keystone

Hi, Can't you just do some rate limiting at your webserver level ? On Tue, Jan 12, 2016 at 3:55 PM, McPeak, Travis wrote: > One issue to be aware of is the use of this as a Denial of Service > vector. Basically an attacker can use this to lock out key accounts > by

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

Doug Wiegley wrote: I don’t think it ninja merged. It had plenty of reviews, and was open during international hours. I don’t have any issue there. I merely meant it was merged too quick. I did not know some people feel the 'ninja merge’ term has negative

Re: [openstack-dev] [TripleO] Removing unused/deprecated template parameters?

IIRC some of them were already marked (via a comment) as deprecated. +1 to cleaning up the parameters. I think it should be done as soon as possible, as the existence of some of them makes the usage of the templates quite confusing. BR On Tue, Jan 12, 2016 at 10:47 PM, Steven Hardy

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

On Tue, Jan 12, 2016 at 5:36 PM, Michał Jastrzębski wrote: > So tracebacks sort of works, they're there just ugly. That's why I'm > also happy if we change rsyslog to heka. > > Eric, I hope I wont ask too much, but could you please prepare PoC of > kolla+heka, for what I care

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

On Tue, Jan 12, 2016 at 8:26 PM, Steven Dake (stdake) wrote: > Eric, > > Thanks for using the mailing list for this discussion. I like to see more > mailing list conversations on big changes related to kolla, which this one > is :) > Responses inline. > > Please put document #3

[openstack-dev] [all] "Upstream Development" track at the Austin OpenStack Summit

Hi everyone, As you may have already noticed in the CFP[1], in Austin for the first time we'll have a conference track clearly targeted to upstream OpenStack developers (us all on this mailing-list). It will run on the Monday, /before/ the design summit tracks start, so it should actually be

Re: [openstack-dev] [Bareon][Fuel] Dynamic allocation algorithm

Hi Artur, You are correct, we probably may consider using bytes instead of megabytes. Regarding to question "ssd vs hdd", user can describe which space is better to allocate on ssd and which is better on hdd, the mechanism is completely data driven, it can be done using "best_with_disks" [0], in

[openstack-dev] [nova][bugs] nova-bugs-team IRC meeting

Hey folks, I'd like to revive the nova-bugs-team IRC meeting. As I want to chair those meetings in my "bug czar" role, the timeslots are bound to my timezone (UTC+1). The two bi-weekly alternating slots I have in mind are: * Tuesdays, 10:00 UTC biweekly-odd (to get folks to the east of me) *

Re: [openstack-dev] [nova] config options: IRC meeting at Jan. 11th

- Orijinal Mesaj - > Kimden: "Markus Zoeller" > Kime: "OpenStack Development Mailing List" > > Gönderilenler: 13 Ocak Çarşamba 2016 10:36:56 > Konu: Re: [openstack-dev] [nova] config options: IRC meeting at Jan. 11th > Esra Celik

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

So is it decided that we want Heka instead of ELK in Kolla and that it is just a matter of time, then ? Clark Boyle put forward some very good points [1] which seem to have gone sadly mostly ignored. What are we trying to address by replacing ELK ? Performance ? Clark's numbers are far from

[openstack-dev] [Fuel] Repositories on master node and delivering updates

Hi, There was a request to deliver updates to master node some time ago. As a result of subsequent discussion in email thread and several offline discussions a document [1] was created that describes existing situation with repositories on master node, and a proposal on delivering updates. Please

[openstack-dev] [neutron][neutron-lib] Proposal for callback mechanism migration

Reposted: as I had a typo in subject line that affected filtering of message... I wanted to float two ideas related to the neutron callback mechanism that is being moved to neutron-lib. 1) API The current API uses kwargs as a way for the notifier to pass information to the subscribers listening

[openstack-dev] [Monasca] Add Monasca Client to global reqs

Guys, I just updated the requirements patch to update the monasca client to the global reqs. It now points to the latest version 1.0.27 that has all the compatible libraries (thanks Joe). https://review.openstack.org/#/c/251674/ Please review it so we can merge it. Thanks, Fabio

[openstack-dev] [kolla] Can Heka solve all the deficiencies in the current rsyslog implementation: was Re: [kolla] Introduction of Heka in Kolla

Eric, Apologies for top post, not really sure where in this thread to post this list of questions as its sort of a change in topic so I changed the subject line :) 1. Somewhere I read when researching this Heka topic, that Heka cannot log all details from /dev/log. Some services like mariadb

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

From: David Moreau Simard > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Wednesday, January 13, 2016 at 5:55 AM To: "OpenStack Development

Re: [openstack-dev] [chef] deprecation and removal of old branches

Hi, i talked to infra and they can remove all of our old branches, but would also like us to tag them first. To do this, i (as the PTL) need to push these signed tags directly to gerrit. To be able to do this i need to adapt our gerrit acls and allow this. While i walked through the whole

[openstack-dev] [kolla] Heka v ELK stack logistics

Hey folks, I'd like to have a mailing list discussion about logistics of the ELKSTACK solution that Alicja has sorted out vs the Heka implementation that Eric is proposing. My take on that is Eric wants to replace rsyslog and logstash with Heka. That seems fine, but I want to make certain

[openstack-dev] [Oslo][all] os-profiler under Oslo umbrella

Team, Oslo folks have voted[1] to be the home for the osprofiler project[2]. Several projects are already using osprofiler. One example of work in flight is for Nova[3]. Please take a look at the README to see the features/description, in a nutshell it will allow operators / end users to drill

Re: [openstack-dev] App dev guides update [nova] [keystone] [cinder] [swift] [glance] [neutron] [trove] [heat] [manila] [ceilometer] [sahara] [senlin]

Anne, thank you for this update. And thank you to the contributors who improved the SDK and developer guide documentation. Fantastic work, all of you! Best, -jay On 01/13/2016 12:18 AM, Anne Gentle wrote: Hi all, I wanted to be sure to post to the dev, docs, and user mailing lists about the

[openstack-dev] [Fuel] New version of fuel-devops (2.9.16)

Hi All, We are going to update the 'fuel-devops' framework on our product CI to the version 2.9.16 on Friday, 15 Jan. This is bugfix update. Changes since 2.9.15: - Default memory size for Fuel master node updated to 3Gb [1] - Added support for creation Fuel master node with Centos 7 from

[openstack-dev] Add Monasca Client to global reqs

Guys, I just updated the requirements patch to update the monasca client to the global reqs. It now points to the latest version 1.0.27 that has all the compatible libraries (thanks Joe). https://review.openstack.org/#/c/251674/ Please review it so we can merge it. Thanks, Fabio

Re: [openstack-dev] [kolla] Can Heka solve all the deficiencies in the current rsyslog implementation: was Re: [kolla] Introduction of Heka in Kolla

Some random thoughts... I've been looking into how to log our production docker containers better, and a couple of things have shown up that may be of interest to you... 1, docker now has a journald backend. so rather then log to files, you just set your daemons to log to stdout, and

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

- Original Message - > On Wed, 2016-01-13 at 04:41 -0500, Tzu-Mainn Chen wrote: > > Hey all, > > > > I realize now from the title of the other TripleO/Mistral thread [1] > > that > > the discussion there may have gotten confused.  I think using Mistral > > for > > TripleO processes that

[openstack-dev] [app-catalog] IRC Meeting Thursday January 14th at 17:00UTC

Join us tomorrow for our weekly meeting, January 14th at 17:00UTC in #openstack-meeting-3. The agenda can be found here, and please add to it if you want to get something on the agenda: https://wiki.openstack.org/wiki/Meetings/app-catalog Tomorrow we hope to have someone from Mistral joining to

Re: [openstack-dev] [neutron] Testing Neutron with latest OVS

On 01/13/2016 03:59 PM, Assaf Muller wrote: > On Wed, Jan 13, 2016 at 4:50 AM, Jakub Libosvar wrote: >> Hi all, >> >> recently I was working on firewall driver [1] that requires latest >> features in OVS, specifically conntrack support. In order to get the >> driver tested,

Re: [openstack-dev] [nova][libvirt] VIR_MIGRATE_NON_SHARED_INC works more like full copy in block migration ?

On 01/12/2016 05:35 AM, Kashyap Chamarthy wrote: On Sun, Jan 10, 2016 at 06:07:33PM +0800, Luo Gangyi wrote: Hi devs, Do you test the difference between within and without VIR_MIGRATE_NON_SHARED_INC ? When I add VIR_MIGRATE_NON_SHARED_INC in block_migration_flags in nova, nova block

Re: [openstack-dev] Shovel (RackHD/OpenStack)

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Wednesday, January 13, 2016 8:53 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] Shovel (RackHD/OpenStack) > > On 01/13/2016 03:28 PM, Keedy, Andre wrote: > > Hi All, I'm pleased to

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

On Wed, Jan 13, 2016 at 02:59:35AM CST, Ihar Hrachyshka wrote: > Kevin Benton wrote: > > >The issue with this data is that who says something is not a good metric. > >For example, this shows that I attended more than twice as many afternoon > >meetings as the morning meetings

Re: [openstack-dev] [api][all] api variation release by release

On 01/12/2016 09:55 PM, Matt Riedemann wrote: Nova and Ironic already support microversioned APIs. Cinder and Neutron are working on it I think, and there could be others. just as a heads up, sahara is also working towards implementing microversions in its next api[1] regards, mike [1]:

Re: [openstack-dev] [nova] config options: IRC meeting at Jan. 11th

- Orijinal Mesaj - > Kimden: "Markus Zoeller" > Kime: "OpenStack Development Mailing List (not for usage questions)" > > Gönderilenler: 13 Ocak Çarşamba 2016 17:38:21 > Konu: Re: [openstack-dev] [nova] config options: IRC meeting

Re: [openstack-dev] [TripleO] Removing unused/deprecated template parameters?

On Tue, 2016-01-12 at 20:47 +, Steven Hardy wrote: > Hi all, > > I've noticed that we have a fairly large number of unused parameters > in > t-h-t, some of which are marked deprecated, some aren't. > > Since we moved tripleoclient to use parameter_defaults everywhere, I > think > it should

[openstack-dev] Further closing the holes that let gate breakage happen

Hi, I was looking at the most recent gate breakage in Neutron [1], fixed by [2]. This gate breakage was held off for some time by the upper-constraints.txt file. This is great progress and I applaud it. I'll continue to cheer on this effort. Now to the next problem. If my assessment of this

[openstack-dev] [Cinder] [Ironic] Attach Cinder Volume to the Ironic Instance without Nova Step-by-Step guide

Hi team, In scope of 'use-cinder-without-nova' blueprint [1] I've created PoC code [2] with detailed instructions how to attach volumes inside Ironic or Nova instances. Detailed instructions could be found on my blog [3]. Any feedback are welcome! [1]

[openstack-dev] [zuul][infra] Synchronizing state of Zuul with Gerrit

Today we had a change [0] that somehow weren't being picked up by Zuul to gate queue although it had Workflow+1 and Verified+1. Only after I added another Workflow+1 it did get Zuul's attention. I don't know what exactly happen, but it seems Zuul didn't notice (lost) either initial Verified+1 or

Re: [openstack-dev] [neutron] Testing Neutron with latest OVS

On Wed, Jan 13, 2016 at 4:50 AM, Jakub Libosvar wrote: > Hi all, > > recently I was working on firewall driver [1] that requires latest > features in OVS, specifically conntrack support. In order to get the > driver tested, we need to have the latest OVS kernel modules on

[openstack-dev] [nova][stable] Proposal to add Tony Breeds to nova-stable-maint

I'm formally proposing that the nova-stable-maint team [1] adds Tony Breeds to the core team. I don't have a way to track review status on stable branches, but there are review numbers from gerrit for stable/liberty [2] and stable/kilo [3]. I know that Tony does a lot of stable branch

[openstack-dev] Shovel (RackHD/OpenStack)

Hi All, I'm pleased to announce a new application called 'Shovel 'that is now available in a public repository on GitHub (https://github.com/keedya/Shovel). Shovel is a server with a set of APIs that wraps around RackHD/Ironic's existing APIs allowing users to find Baremetal Compute nodes that

Re: [openstack-dev] Further closing the holes that let gate breakage happen

On 13 January 2016 at 11:24, Carl Baldwin wrote: > Hi, > > I was looking at the most recent gate breakage in Neutron [1], fixed > by [2]. This gate breakage was held off for some time by the > upper-constraints.txt file. This is great progress and I applaud it. > I'll

Re: [openstack-dev] [puppet] list of blockers to deploy mitaka

A quick update. CentOS jobs are all green. Ubuntu jobs are green for scenario002 and red for scenario001 because of [1] which will be resolved on Thursday 14th. The only remaining blocker is [2] and [3]. Please help to review these patches so we can bump our CI to Mitaka OpenStack codebase.

Re: [openstack-dev] Shovel (RackHD/OpenStack)

On 01/13/2016 03:28 PM, Keedy, Andre wrote: Hi All, I’m pleased to announce a new application called ‘Shovel ‘that is now available in a public repository on GitHub (https://github.com/keedya/Shovel). Shovel is a server with a set of APIs that wraps around RackHD/Ironic’s existing APIs allowing

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

On Wed, Jan 13, 2016 at 12:01 PM, Armando M. wrote: > > > On 12 January 2016 at 20:07, Kyle Mestery wrote: > >> On Tue, Jan 12, 2016 at 5:28 PM, Doug Wiegley < >> doug...@parksidesoftware.com> wrote: >> >>> I don’t think it ninja merged. It had plenty of

Re: [openstack-dev] [Heat] Status of the Support Conditionals in Heat templates

On 12/15/2015 12:07 PM, Fox, Kevin M wrote: My $0.02: heat as it is today, requires all users to be devops, and to carefully craft the templates launched specific to the cloud and the particular app they are trying to write. Making sharing code between heat users difficult. This means the

Re: [openstack-dev] [openstack-ansible][security] Should the playbook stop on certain tasks?

I’m pretty new to openstack-ansible-security but based on my use cases which are as much About using this for verification as they are for building secure boxes my preference would be 3) Use an Ansible callback plugin to catch these and print them at the end of the playbook run -Rob On

Re: [openstack-dev] [nova][stable] Proposal to add Tony Breeds to nova-stable-maint

On 01/13/2016 03:59 PM, Matt Riedemann wrote: > I'm formally proposing that the nova-stable-maint team [1] adds Tony > Breeds to the core team. > > I don't have a way to track review status on stable branches, but there > are review numbers from gerrit for stable/liberty [2] and stable/kilo [3].

[openstack-dev] [ceilometer] ceilometer meter-list output is empty

Hi, I have installed a devstack environment with ceilometer enabled: enable_plugin ceilometer https://git.openstack.org/openstack/ceilometer I am trying to run some ceilometer commands to test whether my ceilometer is working well and get to know ceilometer as well. But, no matter how

Re: [openstack-dev] [Neutron]{l2-gateway] is this project alive

From: "Armando M." > Reply-To: OpenStack List > Date: Tuesday, January 12, 2016 at 8:57 PM To: OpenStack List

Re: [openstack-dev] OpenStack-Announce List

On 2016-01-14 08:13, Tom Fifield wrote: So, I'm prompted by another 20 oslo release emails to dredge up this thread :) There appears to be broad consensus that those shouldn't be going to the announce list ... what do we need to do to get that to change to posted to "-dev + batched inside the

Re: [openstack-dev] OpenStack-Announce List

So, I'm prompted by another 20 oslo release emails to dredge up this thread :) There appears to be broad consensus that those shouldn't be going to the announce list ... what do we need to do to get that to change to posted to "-dev + batched inside the weekly -dev digest from thingee" as

Re: [openstack-dev] OpenStack-Announce List

On 14/01/16 15:22, Andreas Jaeger wrote: On 2016-01-14 08:13, Tom Fifield wrote: So, I'm prompted by another 20 oslo release emails to dredge up this thread :) There appears to be broad consensus that those shouldn't be going to the announce list ... what do we need to do to get that to change

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

In Nova the alternate meetings were chaired by different people. I think that was very productive and fruitful. So it is certainly something worth considering. At the end of the day all of the meetings are logged and people can go over the logs and address issues that can and may concern them.

Re: [openstack-dev] [magnum] Nesting /containers resource under /bays

On 01/13/2016 04:42 AM, Jamie Hannaford wrote: I've recently been gathering feedback about the Magnum API and one of the things that people commented on​ was the global /containers endpoints. One person highlighted the danger of UUID collisions: """ It takes a container ID which is intended

Re: [openstack-dev] [all] re-introducing twisted to global-requirements

On 8 January 2016 at 08:09, Jim Rollenhagen wrote: > Hi all, > > A change to global-requirements[1] introduces mimic, which is an http > server that can mock various APIs, including nova and ironic, including > control of error codes and timeouts. The ironic team plans to

Re: [openstack-dev] [neutron] Testing Neutron with latest OVS

On Wed, Jan 13, 2016 at 03:57:37PM CST, Mooney, Sean K wrote: > One of the ideas that I have been thinking about over the last month or two > is do we > Want to create a dedicated library file in devstack to support compilation > and installation > Of ovs. So, my suggestion is as follows:

Re: [openstack-dev] [puppet] list of blockers to deploy mitaka

On 01/13/2016 03:41 PM, Emilien Macchi wrote: > A quick update. > > CentOS jobs are all green. > Ubuntu jobs are green for scenario002 and red for scenario001 because of > [1] which will be resolved on Thursday 14th. > > The only remaining blocker is [2] and [3]. > > Please help to review

Re: [openstack-dev] Further closing the holes that let gate breakage happen

On 01/13/2016 03:41 PM, Armando M. wrote: > > > On 13 January 2016 at 11:24, Carl Baldwin > wrote: > > Hi, > > I was looking at the most recent gate breakage in Neutron [1], fixed > by [2]. This gate breakage was held off for some

[openstack-dev] [networking guide meeting] Meeting Tomorrow!

Hi, Kind reminder email that we have our networking guide team meeting tomorrow Thursday at 16:00 UTC in #openstack-meeting Agenda: https://wiki.openstack.org/wiki/Documentation/NetworkingGuide/Meetings Cheers, Edgar __

Re: [openstack-dev] [infra][all] "openstack-meeting-cp" == "openstack-meeting-5"?

On Wed, Jan 13, 2016 at 12:11:27PM +0100, Thierry Carrez wrote: > One possible solution here would be to check if the meetings currently > scheduled on your ideal slots are actually still using the spot, as there > are a non-trivial amount of dead meetings around. You can ping me on IRC so > that

Re: [openstack-dev] [oslo][osdk] PrettyTable needs a home in OpenStack

On 11 January 2016 at 10:27, Doug Hellmann wrote: > ... > > > There are a few libraries on the list, too (automaton, ironic-lib), and > that's confusing. It would be interesting to know how they're using > table output. > > Doug > > As far as ironic-lib goes, I took a

Re: [openstack-dev] Further closing the holes that let gate breakage happen

On 14 January 2016 at 08:24, Carl Baldwin wrote: > Hi, > > I was looking at the most recent gate breakage in Neutron [1], fixed > by [2]. This gate breakage was held off for some time by the > upper-constraints.txt file. This is great progress and I applaud it. > I'll

Re: [openstack-dev] [Neutron] Gate failure

This fix failed to merge, due to a new regression in how another job is using dib. Here's a non voting patch for that, until it gets debugged: https://review.openstack.org/267223 The fail stack is now two deep. Doug > On Jan 13, 2016, at 11:41 AM, Armando M. wrote: > >

Re: [openstack-dev] [nova][cinder] How will nova advertise that volume multi-attach is supported?

On Wed, Jan 13, 2016 at 04:52:37PM -0600, Matt Riedemann wrote: > tl;dr - do we need a REST API microversion for multi-attach support in nova? Yes, I think so > > The details: > > The volume multi-attach series in nova, starting here [1], has run into an > upgrade problem. > > Basically,

[openstack-dev] [glance] allow a ranking mechanism for glance-api to order image locations

Hi all, I've recently ran across a constraint in glance-api while working with image locations. In essence, there is no way to customize ordering of image-locations other than the default location strategies, namely location_order and store_type [0]. It seems like a more generic method of

Re: [openstack-dev] [nova][cinder] How will nova advertise that volume multi-attach is supported?

> While I don't think it's strictly required by the api change guidelines [3] > I think the API interactions and behavior here feel different enough to > warrant > having a microversion. Ideally there should have been some versioning in the > cinder api around the multiattach support but that

Re: [openstack-dev] [neutron] Testing Neutron with latest OVS

On Wed, Jan 13, 2016 at 04:47:19PM CST, Sean M. Collins wrote: > I'd prefer to see small, very specific DevStack plugins that have narrow > focus, and jobs that need them for specific things adding them to their > local.conf settings explicitly via enable_repo lines. Sorry, enable_plugin lines

Re: [openstack-dev] [magnum] Nesting /containers resource under /bays

Hi Jamie, I would like to clarify several things. First, a container uuid is intended to be unique globally (not within individual cluster). If you create a container with duplicated uuid, the creation will fail regardless of its bay. Second, you are in control of the uuid of the container

Re: [openstack-dev] [neutron] Testing Neutron with latest OVS

On Wed, Jan 13, 2016 at 10:47:21PM +, Sean M. Collins wrote: > On Wed, Jan 13, 2016 at 03:57:37PM CST, Mooney, Sean K wrote: > > One of the ideas that I have been thinking about over the last month or two > > is do we > > Want to create a dedicated library file in devstack to support

[openstack-dev] [nova][cinder] How will nova advertise that volume multi-attach is supported?

tl;dr - do we need a REST API microversion for multi-attach support in nova? The details: The volume multi-attach series in nova, starting here [1], has run into an upgrade problem. Basically, there is code in liberty which doesn't pass an instance uuid and volume id to the

Re: [openstack-dev] [glance] allow a ranking mechanism for glance-api to order image locations

Hi Jake, Thanks for raising this topic. I'm really interested in it. I reviewed most of the locations patches of Glance, so drop my 2 cents about this. So firstly, I think it's a valid user case. As for the implementation, I think a spec-lite is enough, given it's just a driver for current

Re: [openstack-dev] [api][all] api variation release by release

Thanks for pointing the history out, Matt. According to this thread, I feel the NOTE of each release maximum microversion will help for users because many clouds are deployed from certain releases. https://review.openstack.org/#/c/267247/ is doing that. Thanks Ken Ohmichi 2016-01-13 11:55

[openstack-dev] [release][oslo] taskflow release 1.26.0 (mitaka)

We are delighted to announce the release of: taskflow 1.26.0: Taskflow structured state management library. This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/taskflow With package available at:

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

On 01/14/2016 03:49 AM, Sean M. Collins wrote: On Wed, Jan 13, 2016 at 02:59:35AM CST, Ihar Hrachyshka wrote: Kevin Benton wrote: The issue with this data is that who says something is not a good metric. For example, this shows that I attended more than twice as many

[openstack-dev] [QA] Meeting Thursday January 14th at 9:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, Jan 14th at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here:

[openstack-dev] [release][oslo] oslo.utils release 3.4.0 (mitaka)

We are amped to announce the release of: oslo.utils 3.4.0: Oslo Utility library This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.utils With package available at: https://pypi.python.org/pypi/oslo.utils Please

[openstack-dev] [release][oslo] oslo.log release 2.3.0 (mitaka)

We are tickled pink to announce the release of: oslo.log 2.3.0: oslo.log library This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.log With package available at: https://pypi.python.org/pypi/oslo.log Please

[openstack-dev] [release][oslo] oslo.config release 3.2.1 (mitaka)

We are pumped to announce the release of: oslo.config 3.2.1: Oslo Configuration API This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.config With package available at: https://pypi.python.org/pypi/oslo.config

[openstack-dev] [release][oslo] oslo.vmware release 2.2.1 (mitaka)

We are tickled pink to announce the release of: oslo.vmware 2.2.1: Oslo VMware library This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.vmware With package available at: https://pypi.python.org/pypi/oslo.vmware

Re: [openstack-dev] Further closing the holes that let gate breakage happen

On 2016-01-14 12:32:02 +1300 (+1300), Robert Collins wrote: [...] > We tried to add some unit test jobs to cross check constraints, but we > need some infrastructure work to permit specifying that a unit test > job for a change to requirements checkout the code for e.g. nova and > run nova's

[openstack-dev] [neutron][L3] Wrong fail over of HA-Router

Hi All Could you give me some advice for our problem? We use Neutron L3-HA. When I associate/disassociate floating-ip, the state of ha keepalived become MASTER/MASTER state. Then Because at that time,the sending of vrrp packet from MASTER to BACKUP stop for 40 seconds. I checked logs of

[openstack-dev] [release][oslo] oslo.i18n release 3.2.0 (mitaka)

We are jazzed to announce the release of: oslo.i18n 3.2.0: Oslo i18n library This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.i18n With package available at: https://pypi.python.org/pypi/oslo.i18n Please report

  1   2   >