[openstack-dev] [Infra] Meeting Tuesday October 6th at 19:00 UTC

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

[openstack-dev] Merging DVR-HA into Liberty release

Hi Code Reviewers, I would like to ask if DVR-HA patches can be merged into Liberty release: https://bugs.launchpad.net/neutron/+bug/1365473 https://review.openstack.org/#/c/196893 https://review.openstack.org/#/c/143169 The proper patches has been implemented, the reviews has been addressed,

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Cool. That works. On Mon, Oct 5, 2015 at 9:05 AM, Russell Bryant wrote: > On 10/05/2015 04:28 PM, Murali R wrote: > > Yes. So we can define multiple logical switches per network and ovn > > keeps vlan maps that ovs agent used to maintain and do the tunneling. My > >

[openstack-dev] [Neutron] Effective guide

Hi neutrinos, One of the areas I would like to work on during the Mitaka cycle is 'consistency' [1]. We've grown quite a bit during the last cycle and we need to make sure we are on the same page when it comes to code quality and reviews, and at the same time speeding up review velocity without

Re: [openstack-dev] [Fuel] py.test vs testrepository

On 6 October 2015 at 03:34, Roman Prykhodchenko wrote: > Disclaimer: > I didn’t want to fire up this war but it silently hit one of my patches so > now I think it’s better to spread it to a wide audience. > > > When I was dealing with one of the regular dependency hell in Fuel

[openstack-dev] [Trove][Barbican] Liberty RC2 available

Hello everyone, Due to release-critical issues spotted in Trove and Barbican during RC1 testing, new release candidates were created for Liberty. The list of RC2 fixes, as well as RC2 tarballs are available at: https://launchpad.net/trove/liberty/liberty-rc2

Re: [openstack-dev] Merging DVR-HA into Liberty release

On Mon, Oct 5, 2015 at 2:15 PM, Korzeniewski, Artur < artur.korzeniew...@intel.com> wrote: > Hi Code Reviewers, > > I would like to ask if DVR-HA patches can be merged into Liberty release: > > https://bugs.launchpad.net/neutron/+bug/1365473 > > https://review.openstack.org/#/c/196893 > >

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

On my top of mind for Mitaka: *Introducing common Classifier Model [1]:*Currently, neutron service/s (e.g. Service Function Chaining, QoS, Tap as a Service, FWaaS, Security Group etc) which requires traffic classification defines their own classifier model. This introduces redundancy. In order

Re: [openstack-dev] [fuel] What to do when a controller runs out of space

> > >> > Mirantis does control neither Rabbitmq or Galera. Mirantis cannot assure > their quality as well. > Correct, and rabbitmq was always the pain in the back, preventing any *real *enterprise usage of openstack where reliability does matter. > > 2) it has terrible UX >> > > It looks like

[openstack-dev] [all] Reviewing code coverage syntax/use across projects

As part of reviewing the code coverage on various projects I have found that a number had failing coverage jobs when not configured correctly (many also work just fine). Starting initially in various Oslo projects my goal has been to just ensure coverage is defined, runs without errors and is

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

A kind reminder for tomorrow's meeting. Please add agenda items to the meeting here [1]. See you all tomorrow! Armando [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [all] Reviewing code coverage syntax/use across projects

Excerpts from Ronald Bradford's message of 2015-10-05 16:56:50 -0400: > As part of reviewing the code coverage on various projects I have found > that a number had failing coverage jobs when not configured correctly (many > also work just fine). Starting initially in various Oslo projects my goal

Re: [openstack-dev] [Neutron] AZ Support

Hi, Yes, you are correct. That patch is the culprit (my bad and once again humble apologies) Regarding the AZ support I think that we need to do the following: 1. Have this in a separate topic until it is complete. I have a number of concerns here: * The upgrade impact on Nova. Today

[openstack-dev] [nova-compute][libvirt] permission problems

Hi all, I have permission-related errors when creating instances. In Kilo, since my local disk is small, newly attaching a new disk, /data1 as following. root@cn2:/var/lib/nova# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda5 23G 1.7G 20G 8% / ... /dev/mapper/vg_data-lv_data1 356G

Re: [openstack-dev] [Manila] CephFS native driver

> For ultra isolation, the RADOS pools would also be configured to map to > different OSDs. This is really good idea, and will be motivation to me. > Separate RADOS namespaces do not provide physical separation (multiple > namespaces exist within one pool, hence on the same OSDs), but they >

Re: [openstack-dev] [fuel] What to do when a controller runs out of space

Good morning gentlemen! Alex raised very good question. Thank you very much! We have 3 init systems right now. Some services use SystemV, some services use upstart, some services are under pacemaker. Personally, I would like to have pacemaker as pid 1 to replace init [1]. However, I would like to

Re: [openstack-dev] [Neutron] AZ Support

Hi Gary, Thank you for your suggestion. In Liberty cycle[1], I have discussed about these points with neutron folks and network operators. > On 2015/10/05, at 15:54, Gary Kotton wrote: > > Hi, > Yes, you are correct. That patch is the culprit (my bad and once again humble

Re: [openstack-dev] Fwd: [nova] live migration in Mitaka

On Fri, Oct 02, 2015 at 04:38:30PM -0400, Mathieu Gagné wrote: > On 2015-10-02 4:18 PM, Pavel Boldin wrote: > > > > You have to pass device names from /dev/, e.g., if a VM has > > ephemeral disk > > attached at /dev/vdb you need to pass in 'vdb'. Format expected by > >

Re: [openstack-dev] [fuel] What to do when a controller runs out of space

No pacemaker for os services, please. We'll be moving out neutron agents from pacemaker control in 8.0, other os services don't need it too. E. 5 окт. 2015 г. 12:01 пользователь "Sergii Golovatiuk" < sgolovat...@mirantis.com> написал: > Good morning gentlemen! > > Alex raised very good question.

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

Hi, I have some plans in Mitaka cycle. 1. AZ support[1] - I proposed AZ support in Liberty but the millstone is Mitaka now. The spec has been merged in Mitaka. I keep to propose the patches on Gerrit. 2. LinuxbrideDVR - I'm trying to create concrete implementation and then I achieve it

[openstack-dev] [TripleO] meeting tomorrow

Our team meeting is tomorrow at 14:00 UTC. I made a couple changes to the agenda this week and added a new sections called "Review Highlights" which I hope will help us discuss and move forward some patches that look promising: https://wiki.openstack.org/wiki/Meetings/TripleO#Review_Highlights

Re: [openstack-dev] [fuel] Problems with mcollective offline nodes

[ Was: Re: [openstack-dev] OpenStack-dev Digest, Vol 41, Issue 49] Santosh Parihar, This implies that the nodes are (in order of most to least likely): a) currently offline b) un-accessible from the fuel master node c) the mcollective agent is not running on them d) rabbitmq on the fuel node

Re: [openstack-dev] [Fuel][Plugins] add health check for plugins

OSTF was designed to be a post-deployment test framework. We may introduce pre- and post-deployment tests in Fuel, but from an implementation point of view the "pre-" should be done by Nailgun/Astute and the "post-" by OSTF. I don't think we should mix both in OSTF. On Tue, Sep 29, 2015 at 10:02

Re: [openstack-dev] [all] Reviewing code coverage syntax/use across projects

On 2015-10-05 22:14:20 + (+), Jeremy Stanley wrote: > On 2015-10-05 16:56:50 -0400 (-0400), Ronald Bradford wrote: > [...] > > - Anything else relevant regarding code coverage being more consistent > > for OpenStack. > > I do have https://review.openstack.org/171331 to get PBR to stop >

Re: [openstack-dev] [all] Reviewing code coverage syntax/use across projects

On 2015-10-05 16:56:50 -0400 (-0400), Ronald Bradford wrote: [...] > - Anything else relevant regarding code coverage being more consistent > for OpenStack. I do have https://review.openstack.org/171331 to get PBR to stop stepping on the package name if set in .coveragerc, though it's still WIP

[openstack-dev] [Ironic] backwards compat issue with PXEDeply and AgentDeploy drivers

tldr; the boot / deploy interface split we did broke an out of tree driver. I've proposed a patch. We should get a fix into stable/liberty too. Longer version... I was rebasing my AMTTool driver [0] on top of master because the in-tree one still does not work for me, only to discover that my

Re: [openstack-dev] [magnum] New Core Reviewers

Team, In accordance with our consensus and the current date/time, I hereby welcome Vilobh and Hua as new core reviewers, and have added them to the magnum-core group. I will announce this addition at tomorrow’s team meeting at our new time of 1600 UTC (no more alternating schedule, remember?).

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

(Cross-posting to the operators list for feedback) Thank you Ihar for starting this up. In the absence of any kind of blog or other outlet of my own to disseminate this, let me share my plans here... Routed Networks: My plans for Mitaka (and beyond) are around routed networks. During Liberty,

[openstack-dev] [searchlight] Liberty release finalization

Note: I sent a message to Thierry and Doug for help with the specifics of running the release and after Theirry’s response it seemed we should include the mailing list. >Tripp, Travis S wrote: >>Theirry and Doug, >>We are down to a single patch that needs one more +2 and then we believe

[openstack-dev] [A Bug of Heat in Stable/Liberty] Stack creation fails when connecting a Nova::Server instance with a created network

Hi all, There seems a bug in stable/liberty branch. https://bugs.launchpad.net/heat/+bug/1503060 In an environment installed with Devstack and stable/liberty branch, stack creation fails when I use some templates that worked well with stable/kilo, such as the following: heat_template_version:

Re: [openstack-dev] [A Bug of Heat in Stable/Liberty] Stack creation fails when connecting a Nova::Server instance with a created network

Thanks, I'm triaging this now. On 06/10/15 11:41, Mingyu Li wrote: Hi all, There seems a bug in stable/liberty branch. https://bugs.launchpad.net/heat/+bug/1503060 In an environment installed with Devstack and stable/liberty branch, stack creation fails when I use some templates that worked

Re: [openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

On 29 September 2015 at 08:28, Chris Hoge wrote: > On Sep 29, 2015, at 8:04 AM, Erlon Cruz wrote: > > > Hi Cris, > > There are some questions that came to my mind. > > Cinder has near zero tolerance to backends that does not have a CI > running. So, can

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 06/10/15 06:23, Ben Nemec wrote: On 10/05/2015 12:12 PM, Jeremy Stanley wrote: On 2015-10-05 12:00:31 -0500 (-0500), Ben Nemec wrote: [...] Note that it's best to do this once the change is ready to be approved. If you do it earlier and the committer pushes a new patch set without fixing

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

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) - (diff with Sep 28, no diff for inspector) - Open: 137 (+2). 4 new (-5), 34 in progress (-2), 0 critical, 7 high and 13 incomplete (+4)

[openstack-dev] [heat] perfomance benchmark metrics of heat-api

Hi all, Has anyone done any performance tests on heat-api servers on any standard setup so as to know how many stack requests it can handle before it can stumble so that we can deploy scaling of heat-servers ?? Thanks Eswar

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

Very nice thread Ihar! Here are my plans: 1. Get the last patches of the blueprint restructure-l2-agent merged and keep working on improving the agent. Some code refactor is definitely needed and I'd like to add multiple workers. 2. Introducing oslo versioned objects 3. Make it easier to get

Re: [openstack-dev] [Neutron] Defect management

> On 02 Oct 2015, at 02:37, Armando M. wrote: > > Hi neutrinos, > > Whilst we go down the path of revising the way we manage/process bugs in > Neutron, and transition to the proposed model [1], I was wondering if I can > solicit some volunteers to screen the bugs outlined

Re: [openstack-dev] [all][stable][release] 2015.1.2

Hi, I would like to freeze the branches on Wednesday and get a release out early next week. Are we okay with that? Thanks chuck On Wed, Sep 23, 2015 at 8:47 PM, Chuck Short wrote: > Hi, > > We would like to do a stable/kilo branch release, next Thursday. In order >

Re: [openstack-dev] Fwd: [nova] live migration in Mitaka

Daniel, It is done already in the proposed patch. But this one is about Wily having libvirt 1.2.16 and libvirt-python 1.2.15. Pavel On Mon, Oct 5, 2015 at 11:25 AM, Daniel P. Berrange wrote: > On Fri, Oct 02, 2015 at 04:38:30PM -0400, Mathieu Gagné wrote: > > On

Re: [openstack-dev] I love csv output in openstackclient, please never removed it

On 10/05/2015 12:16 AM, Steve Martinelli wrote: > I loved reading this email as much as zigo loves csv output, great > feedback is an amazing motivator! > > And don't worry, the csv output was never going away :) > > stevemar It might be nice to change some of the devstack usage into that. It

Re: [openstack-dev] [Neutron] AZ Support

> On 04 Oct 2015, at 19:21, Gary Kotton wrote: > > Sorry, it is not a result of the AZ support (humble apologies) > > It is a result of https://review.openstack.org/#/c/226362/ So you use DHCP agent with non-ml2 plugin, and it broke you. Do you think it’s ok for you to

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

Hello! Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC in #openstack-meeting-4: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151006 Feel free to add any additional items you'd like to discuss. If our schedule allows it, we'll make bug triage during

Re: [openstack-dev] [fuel] What to do when a controller runs out of space

On Mon, Oct 5, 2015 at 5:56 AM, Eugene Nikanorov wrote: > Ok, > > Project-wise: > 1) Pacemaker is not under our company's control, we can't assure its quality > 2) it has terrible UX > 3) it is not reliable > I disagree with #1 as I do not agree that should be a criteria

[openstack-dev] [mistral] Team meeting - 10/05/2015

Hi, This is a reminder that we’ll hold a team meeting today at #openstack-meeting at 16.00 UTC. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) UI progress Official Liberty Release health Bugfixing progress Documentation progress Open discussion Feel

Re: [openstack-dev] Fwd: [nova] live migration in Mitaka

OK, I propose to move further discussions of the topic to this particular changeset review. Pavel On Mon, Oct 5, 2015 at 1:25 PM, Daniel P. Berrange wrote: > On Mon, Oct 05, 2015 at 01:10:45PM +0300, Pavel Boldin wrote: > > Daniel, > > > > It is done already in the

Re: [openstack-dev] [fuel] What to do when a controller runs out of space

Ok, Project-wise: 1) Pacemaker is not under our company's control, we can't assure its quality 2) it has terrible UX 3) it is not reliable (3) is not evaluation of the project itself, but just a logical consequence of (1) and (2). As a part of escalation team I can say that it has cost our team

Re: [openstack-dev] [tripleo] How to selectively enable new services?

On 01/10/15 20:34, Dan Prince wrote: > On Wed, 2015-09-30 at 21:05 +0100, Steven Hardy wrote: >> Hi all, >> >> So I wanted to start some discussion on $subject, because atm we have >> a >> couple of patches adding support for new services (which is great!): >> >> Manila:

Re: [openstack-dev] [Neutron] AZ Support

Hi, 2015-10-05 15:54 GMT+09:00 Gary Kotton : > Hi, > Yes, you are correct. That patch is the culprit (my bad and once again > humble apologies) > > Regarding the AZ support I think that we need to do the following: > >1. Have this in a separate topic until it is complete.

[openstack-dev] [cloudkitty] No IRC meeting today

Hi, Most of the people involved in the project won't be able to attend today's meeting. Meeting is canceled. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [fuel] What to do when a controller runs out of space

On Mon, Oct 5, 2015 at 12:22 PM, Eugene Nikanorov wrote: > No pacemaker for os services, please. > We'll be moving out neutron agents from pacemaker control in 8.0, other os > services don't need it too. > could you please provide your arguments. /sv

Re: [openstack-dev] Fwd: [nova] live migration in Mitaka

On Mon, Oct 05, 2015 at 01:10:45PM +0300, Pavel Boldin wrote: > Daniel, > > It is done already in the proposed patch. > > But this one is about Wily having libvirt 1.2.16 and libvirt-python 1.2.15. Assuming you are refering to this patch:

[openstack-dev] Please add your timezone to your Launchpad account (voluntarily)

Hi together, I think it would be very helpful if you all could update your launchpad profile with your timezone information. This makes it more easy to figure out the timeframe when a person can be reached in theory. To update your account, use this link

Re: [openstack-dev] [fuel] What to do when a controller runs out of space

Hi, On Mon, Oct 5, 2015 at 3:03 PM, Alex Schultz wrote: > On Mon, Oct 5, 2015 at 5:56 AM, Eugene Nikanorov > wrote: > > Ok, > > > > Project-wise: > > 1) Pacemaker is not under our company's control, we can't assure its > quality > Mirantis does

Re: [openstack-dev] [Neutron] AZ Support

On 10/5/15, 3:21 AM, "Ihar Hrachyshka" wrote: >> On 04 Oct 2015, at 19:21, Gary Kotton wrote: >> >> Sorry, it is not a result of the AZ support (humble apologies) >> >> It is a result of https://review.openstack.org/#/c/226362/ > >So you use DHCP

Re: [openstack-dev] [Solum] Proposal to change weekly IRC meeting time

Hi team, Last week I had sent out an email proposing changes to our weekly IRC meeting time (see below for reference). There was no objection to this proposal. The patch that makes this change official is now merged. https://review.openstack.org/#/c/228441/ Starting tomorrow (October 6), our

[openstack-dev] [Fuel] py.test vs testrepository

Disclaimer: I didn’t want to fire up this war but it silently hit one of my patches so now I think it’s better to spread it to a wide audience. When I was dealing with one of the regular dependency hell in Fuel Client I noticed, that stuff which is not in global requirements may make the

Re: [openstack-dev] [Neutron] AZ Support

From: Akihiro MOTOKI > Reply-To: OpenStack List > Date: Monday, October 5, 2015 at 3:48 PM To: OpenStack List

Re: [openstack-dev] [Neutron] AZ Support

> On 05 Oct 2015, at 15:32, Gary Kotton wrote: > > > > On 10/5/15, 3:21 AM, "Ihar Hrachyshka" wrote: > >>> On 04 Oct 2015, at 19:21, Gary Kotton wrote: >>> >>> Sorry, it is not a result of the AZ support (humble apologies) >>>

Re: [openstack-dev] [all] [ptls] Proposed Design Summit track/room/time allocation

Thierry Carrez wrote: > [...] Here is the resulting proposed room/time layout result: > > http://tinyurl.com/mitaka-design-summit OK, I just pushed this track layout to the official Design Summit schedule at: https://mitakadesignsummit.sched.org/ > [...] > I'll push this proposed layout to

Re: [openstack-dev] I love csv output in openstackclient, please never removed it

On Mon, Oct 5, 2015 at 11:03 AM, Doug Hellmann wrote: > Devstack should also look at using the shell output formatter, > especially for show commands. Combining that formatter with eval means > no parsing in a lot of cases. > It may in places, but it turns out the 'value'

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 10/01/2015 02:56 AM, Ghe Rivero wrote: > If anyone disagrees with the commit format, please, go ahead and fix it (It's > really easy using the gerrit web) For such cosmetic changes (and others > similars), we should not wait for the author to do it. Sometimes, for a stupid > comma, and with all

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Yes. So we can define multiple logical switches per network and ovn keeps vlan maps that ovs agent used to maintain and do the tunneling. My confusion was from lport-add command that did not have host info, so if there is no neutron, the cms has to maintain the host to lport association and we

[openstack-dev] [Zaqar] Liberty RC2 available

Hello everyone, In order to include last-minute translations updates, a new liberty release candidate was created for Zaqar. RC2 tarballs are available at: https://launchpad.net/zaqar/liberty/liberty-rc2 Unless new release-critical issues are found that warrant a last-minute release candidate

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 10/05/2015 12:12 PM, Jeremy Stanley wrote: > On 2015-10-05 12:00:31 -0500 (-0500), Ben Nemec wrote: > [...] >> Note that it's best to do this once the change is ready to be >> approved. If you do it earlier and the committer pushes a new >> patch set without fixing the commit message, it will

Re: [openstack-dev] I love csv output in openstackclient, please never removed it

Excerpts from Sean Dague's message of 2015-10-05 06:57:06 -0400: > On 10/05/2015 12:16 AM, Steve Martinelli wrote: > > I loved reading this email as much as zigo loves csv output, great > > feedback is an amazing motivator! > > > > And don't worry, the csv output was never going away :) > > > >

Re: [openstack-dev] I love csv output in openstackclient, please never removed it

Excerpts from Dean Troyer's message of 2015-10-05 11:18:55 -0500: > On Mon, Oct 5, 2015 at 11:03 AM, Doug Hellmann > wrote: > > > Devstack should also look at using the shell output formatter, > > especially for show commands. Combining that formatter with eval means > >

Re: [openstack-dev] [Neutron] Defect management

On 5 October 2015 at 03:14, Ihar Hrachyshka wrote: > > On 02 Oct 2015, at 02:37, Armando M. wrote: > > > > Hi neutrinos, > > > > Whilst we go down the path of revising the way we manage/process bugs in > Neutron, and transition to the proposed model [1],

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 10/05/2015 04:28 PM, Murali R wrote: > Yes. So we can define multiple logical switches per network and ovn > keeps vlan maps that ovs agent used to maintain and do the tunneling. My > confusion was from lport-add command that did not have host info, so if > there is no neutron, the cms has to

Re: [openstack-dev] [all][stable][release] 2015.1.2

Chuck Short wrote: > I would like to freeze the branches on Wednesday and get a release out > early next week. Are we okay with that? Next week is Liberty release week so that might be confusing... But if it's the only option, as long as it's *early* next week, I guess that won't hurt. --

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 2015-10-05 12:00:31 -0500 (-0500), Ben Nemec wrote: [...] > Note that it's best to do this once the change is ready to be > approved. If you do it earlier and the committer pushes a new > patch set without fixing the commit message, it will revert the > fix made through the web interface.