Re: [openstack-dev] [Kuryr] IPAM issue with multiple docker networks having same cidr subnets

2016-05-27 Thread Vikas Choudhary
Thanks Toni, after some thought process, to me also also addressSpace approach making sense. We can map neutron addressScopes to docker addressSpaces. Have drafted a blueprint here [1]. I think i have got enough clarity on approach. Will be pushing a spec for this soon. Thanks Vikas [1]https:

Re: [openstack-dev] [keystone] Who is going to fix the broken non-voting tests?

2016-05-27 Thread Adam Young
On 05/27/2016 02:30 PM, Raildo Mascena wrote: In addition, I'm the one of the folks who are working with the v3-only gates, the main case that we are looking for is when the functional job is working and the the v3-only is not, so everything related to this jobs, you can just ping me on irc. :)

[openstack-dev] [infra] [smaug] gate fullstack is shown as NOT_REGISTERED

2016-05-27 Thread xiangxinyong
Hi teams, We have merged smaug full stack job in the project-config by this patch [1]. But the gate-smaug-dsvm-fullstack-nv is shown as NOT_REGISTERED. gate-smaug-dsvm-fullstack-nvNOT_REGISTERED (non-voting) It can be also found in this patch [2]. Could some one help us to run the fullstac

[openstack-dev] [craton] meeting is published

2016-05-27 Thread sean roberts
http://eavesdrop.openstack.org/#Craton_Team_Meeting ~ sean __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/

Re: [openstack-dev] [TripleO][Kolla][Heat][Higgins][Magnum][Kuryr] Gap analysis: Heat as a k8s orchestrator

2016-05-27 Thread Fox, Kevin M
Hi Zane, I've been working on the k8s side of the equation right now... See these two PR's: https://github.com/kubernetes/kubernetes/pull/25391 https://github.com/kubernetes/kubernetes/pull/25624 I'm still hopeful these can make k8s 1.3 as experimental plugins. There is keystone username/passwo

[openstack-dev] [TripleO][Kolla][Heat][Higgins][Magnum][Kuryr] Gap analysis: Heat as a k8s orchestrator

2016-05-27 Thread Zane Bitter
I spent a bit of time exploring the idea of using Heat as an external orchestration layer on top of Kubernetes - specifically in the case of TripleO controller nodes but I think it could be more generally useful too - but eventually came to the conclusion it doesn't work yet, and probably won't

[openstack-dev] [Neutron] Stadium Evolution - next steps

2016-05-27 Thread Armando M.
Hi Neutrinos, I wanted to give an update on [1]. Based on the feedback received so far I think it is time to get on the next stage of this transition and execute on some of the things identified in the proposal, as well as provide more detailed information to some of the folks involved in the proj

Re: [openstack-dev] [higgins] Continued discussion from the last team meeting

2016-05-27 Thread Joshua Harlow
I get this idea, I just want to bring up the option that if u only start off with a basic vision, then u basically get that as a result, vs IMHO where u start off with a bigger/greater vision and work on getting there. I'd personally rather work on a project that has a advanced vision vs one t

Re: [openstack-dev] [tripleo][infra][deployment] Adding multinode CI jobs for TripleO in nodepool

2016-05-27 Thread Emilien Macchi
On Fri, May 27, 2016 at 3:08 PM, James Slagle wrote: > On Fri, May 27, 2016 at 2:37 PM, Emilien Macchi wrote: >> On Fri, May 27, 2016 at 2:03 PM, James Slagle wrote: >>> I've been working on various patches to TripleO to make it possible >>> for the baremetal provisioning part of the workflow to

Re: [openstack-dev] [TaskFlow] TaskFlow persistence: Job failure retry

2016-05-27 Thread Joshua Harlow
Seems like u could just use http://docs.openstack.org/developer/taskflow/jobs.html (it appears that you may not be?); the job itself would when failed be then worked on by a different job consumer. Have u looked at those? It almost appears that u are using celery as a job distribution system

Re: [openstack-dev] [Kuryr] IPAM issue with multiple docker networks having same cidr subnets

2016-05-27 Thread Antoni Segura Puimedon
On Thu, May 26, 2016 at 9:48 PM, Vikas Choudhary wrote: > Hi All, > > Recently, Banix observed and brought into notice this issue [1]. > > To solve this, i could think of two approaches: > 1. Modifying the libnetwork apis to get PoolID also at network creation. > OR > 2. Enhancing the /netwo

Re: [openstack-dev] [tripleo][manila] Moving forward with landing manila in tripleo

2016-05-27 Thread Rodrigo Barbieri
Hello Marios, The Data Service is needed for Share Migration feature in manila since the Mitaka release. There has not been any work done yet towards adding it to puppet. Since its introduction in Mitaka, it has been made compatible only with devstack so far. I have not invested time thinking ab

[openstack-dev] [Neutron] Team meeting - cancelled

2016-05-27 Thread Armando M.
Neutrinos, Because of holidays in US/UK, it's probably safer to cancel the meeting for the week starting Monday 30th. We are approaching N-1, and we'll cut the release sometime next week. Please be aware of release deadlines [1], if you have cross-project items you are working on. Cheers, Armand

Re: [openstack-dev] [tripleo][infra][deployment] Adding multinode CI jobs for TripleO in nodepool

2016-05-27 Thread James Slagle
On Fri, May 27, 2016 at 2:37 PM, Emilien Macchi wrote: > On Fri, May 27, 2016 at 2:03 PM, James Slagle wrote: >> I've been working on various patches to TripleO to make it possible >> for the baremetal provisioning part of the workflow to be optional. In >> such a scenario, TripleO wouldn't use N

Re: [openstack-dev] [tempest][qa][ironic][nova] When Nova should mark instance as successfully deleted?

2016-05-27 Thread Andrew Laski
On Fri, May 27, 2016, at 11:25 AM, Matthew Treinish wrote: > On Fri, May 27, 2016 at 05:52:51PM +0300, Vasyl Saienko wrote: > > Lucas, Andrew > > > > Thanks for fast response. > > > > On Fri, May 27, 2016 at 4:53 PM, Andrew Laski wrote: > > > > > > > > > > > On Fri, May 27, 2016, at 09:25 AM,

Re: [openstack-dev] [tripleo][infra][deployment] Adding multinode CI jobs for TripleO in nodepool

2016-05-27 Thread Emilien Macchi
On Fri, May 27, 2016 at 2:03 PM, James Slagle wrote: > I've been working on various patches to TripleO to make it possible > for the baremetal provisioning part of the workflow to be optional. In > such a scenario, TripleO wouldn't use Nova or Ironic to boot any > baremetal nodes. Instead it would

Re: [openstack-dev] [keystone] Who is going to fix the broken non-voting tests?

2016-05-27 Thread Raildo Mascena
In addition, I'm the one of the folks who are working with the v3-only gates, the main case that we are looking for is when the functional job is working and the the v3-only is not, so everything related to this jobs, you can just ping me on irc. :) Cheers, Raildo On Thu, May 26, 2016 at 6:27 PM

[openstack-dev] [tripleo][infra][deployment] Adding multinode CI jobs for TripleO in nodepool

2016-05-27 Thread James Slagle
I've been working on various patches to TripleO to make it possible for the baremetal provisioning part of the workflow to be optional. In such a scenario, TripleO wouldn't use Nova or Ironic to boot any baremetal nodes. Instead it would rely on the nodes to be already installed with an OS and powe

Re: [openstack-dev] [congress] Spec for congress.conf

2016-05-27 Thread Bryan Sullivan
Masahito, Sorry, I'm not quite clear on the guidance. Sounds like you're saying all options will be defaulted by Oslo.config if not set in the congress.conf file. That's OK, if I understood. It's clear to me that some will be deployment-specific. But what I am asking is where is the spec f

Re: [openstack-dev] [keystone] orchestration and db_sync

2016-05-27 Thread Sheel Rana Insaan
Hi Ryan, >- Create the service's users and add a password into the databse >- Sync the service with the database >- Start the service If I am right, these are one time activity...during installation stage.. one does not need to create "service users" again and again during service star

Re: [openstack-dev] [nova] Centralize Configuration: ignore service list for newton

2016-05-27 Thread Markus Zoeller
On 20.05.2016 11:33, John Garbutt wrote: > Hi, > > The current config template includes a list of "Services which consume this": > http://specs.openstack.org/openstack/nova-specs/specs/mitaka/implemented/centralize-config-options.html#quality-view > > I propose we drop this list from the template

[openstack-dev] [keystone] orchestration and db_sync

2016-05-27 Thread Ryan Hallisey
Hi all, When orchestrating an openstack service from nothing, there are a few steps that need to occur before you have a running service assuming the database already exists. - Create the service's users and add a password into the databse - Sync the service with the database - Start

Re: [openstack-dev] [tempest][qa][ironic][nova] When Nova should mark instance as successfully deleted?

2016-05-27 Thread Vladyslav Drok
On Fri, May 27, 2016 at 5:52 PM, Vasyl Saienko wrote: > Lucas, Andrew > > Thanks for fast response. > > On Fri, May 27, 2016 at 4:53 PM, Andrew Laski wrote: > >> >> >> On Fri, May 27, 2016, at 09:25 AM, Lucas Alvares Gomes wrote: >> > Hi, >> > >> > Thanks for bringing this up Vasyl! >> > >> > >

Re: [openstack-dev] [tempest][qa][ironic][nova] When Nova should mark instance as successfully deleted?

2016-05-27 Thread Matthew Treinish
On Fri, May 27, 2016 at 05:52:51PM +0300, Vasyl Saienko wrote: > Lucas, Andrew > > Thanks for fast response. > > On Fri, May 27, 2016 at 4:53 PM, Andrew Laski wrote: > > > > > > > On Fri, May 27, 2016, at 09:25 AM, Lucas Alvares Gomes wrote: > > > Hi, > > > > > > Thanks for bringing this up Vas

Re: [openstack-dev] [tempest][qa][ironic][nova] When Nova should mark instance as successfully deleted?

2016-05-27 Thread Vasyl Saienko
Lucas, Andrew Thanks for fast response. On Fri, May 27, 2016 at 4:53 PM, Andrew Laski wrote: > > > On Fri, May 27, 2016, at 09:25 AM, Lucas Alvares Gomes wrote: > > Hi, > > > > Thanks for bringing this up Vasyl! > > > > > At the moment Nova with ironic virt_driver consider instance as > deleted

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

2016-05-27 Thread Duarte Cardoso, Igor
Hi all, As Uri mentioned, there is a concrete proposal for an enhanced SFC API (with support for open, IETF SFC Encapsulation [1] and NSH [2]) that was publicly shared last month as a neutron spec at [3]. Service Function Chaining (SFC) is the effort of normalizing and standardizing nomenclatu

Re: [openstack-dev] [horizon] Horizon in devstack is broken, rechecks are futile

2016-05-27 Thread Brant Knudson
On Fri, May 27, 2016 at 8:39 AM, Timur Sufiev wrote: > The root cause of Horizon issue has been identified and fixed at > https://review.openstack.org/#/c/321639/ > The next steps are to release new version of django-openstack-auth library > (which the above fix belongs to), update global-require

Re: [openstack-dev] [tempest][qa][ironic][nova] When Nova should mark instance as successfully deleted?

2016-05-27 Thread Andrew Laski
On Fri, May 27, 2016, at 09:25 AM, Lucas Alvares Gomes wrote: > Hi, > > Thanks for bringing this up Vasyl! > > > At the moment Nova with ironic virt_driver consider instance as deleted, > > while on Ironic side server goes to cleaning which can take a while. As > > result current implementation

Re: [openstack-dev] [horizon] Horizon in devstack is broken, rechecks are futile

2016-05-27 Thread Timur Sufiev
The root cause of Horizon issue has been identified and fixed at https://review.openstack.org/#/c/321639/ The next steps are to release new version of django-openstack-auth library (which the above fix belongs to), update global-requirements (if it's not automatic, I'm not very into the details of

Re: [openstack-dev] [tempest][qa][ironic][nova] When Nova should mark instance as successfully deleted?

2016-05-27 Thread Lucas Alvares Gomes
Hi, Thanks for bringing this up Vasyl! > At the moment Nova with ironic virt_driver consider instance as deleted, > while on Ironic side server goes to cleaning which can take a while. As > result current implementation of Nova tempest tests doesn't work for case > when Ironic is enabled. > > The

[openstack-dev] [tripleo][manila] Moving forward with landing manila in tripleo

2016-05-27 Thread Marios Andreou
Hi all, I explicitly cc'd a few folks I thought might be interested for visibility, sorry for spam if you're not. This email is about getting manila landed into tripleo asap, and the current obstacles to that (at least those visible to me): The current review [1] isn't going to land as is, regardl

[openstack-dev] [tempest][qa][ironic][nova] When Nova should mark instance as successfully deleted?

2016-05-27 Thread Vasyl Saienko
Hello Community! At the moment Nova with ironic virt_driver consider instance as deleted, while on Ironic side server goes to cleaning which can take a while. As result current implementation of Nova tempest tests doesn't work for case when Ironic is enabled. There are two possible options how t

[openstack-dev] [tripleo] Mistral workflows for node assignment

2016-05-27 Thread Honza Pokorny
Hello folks, I would love to get your thoughts on a new way of assigning roles to nodes. Since nova flavors are created during the installation of the undercloud, they don't correspond to the actual hardware specifications of the available nodes. So, once a node is assigned, we should update the

Re: [openstack-dev] [TaskFlow] TaskFlow persistence: Job failure retry

2016-05-27 Thread pnkk
To be specific, we hit this issue when the node running our service is rebooted. Our solution is designed in a way that each and every job is a celery task and inside celery task, we create taskflow flow. We enabled late_acks in celery(uses rabbitmq as message broker), so if our service/node goes

Re: [openstack-dev] [puppet] Watcher module for Puppet

2016-05-27 Thread Emilien Macchi
On Tue, May 10, 2016 at 10:25 AM, Daniel Pawlik wrote: > Hello, > I'm working on implementation of a new puppet module for Openstack Watcher > (https://launchpad.net/watcher). > I'm already creating this module and I would like to share it when it will > be done. > > Could someone tell me how can

Re: [openstack-dev] Sahara Job Binaries Storage

2016-05-27 Thread Trevor McKay
Hi Jerico, we talked about it at Summit in one of the design sessions, but afaik there is no blueprint or spec yet. I don't see why it can't happen in Newton, however. Best, Trevor On Thu, 2016-05-26 at 16:14 +1000, Jerico Revote wrote: > Hi Trevor, > > Just revisiting this, > has there been

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

2016-05-27 Thread Jay Pipes
On 05/24/2016 01:54 AM, Gary Kotton wrote: Hi, We have used tooz to enable concurrency. Zookeeper and Redis worked well. I think that it is certainly something that we need to consider. The challenge becomes a deployment. I'm not following. What does tooz, ZK or Redis have to do with concurre

[openstack-dev] [TaskFlow] TaskFlow persistence: Job failure retry

2016-05-27 Thread pnkk
Hi, When taskflow engine is executing a job, the execution failed due to IO error(traceback pasted below). 2016-05-25 19:45:21.717 7119 ERROR taskflow.engines.action_engine.engine 127.0.1.1 [-] Engine execution has failed, something bad must of happened (last 10 machine transitions were [('SCHED

[openstack-dev] [nova] #help: bug skimming for 1 week (R-18)

2016-05-27 Thread Markus Zoeller
Nova needs one or more volunteers for the bug skimming duty [1] for the coming week (R-18). Unfortunately no one signed up yet. Let me know if you wanna help in this area. References: [1] https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty -- Regards, Markus Zoeller (markus_

Re: [openstack-dev] [Neutron] Mid-cycle development sprint

2016-05-27 Thread Thierry Carrez
Rossella Sblendido wrote: On 05/26/2016 10:47 PM, Henry Gessau wrote: I am happy to announce that the location logistics for the Neutron mid-cycle have been finalized. The mid-cycle will take place in Cork, Ireland on August 15-17. I have updated the wiki [1] where you will find a link to an eth

Re: [openstack-dev] [Nova] Abandoned old code reviews

2016-05-27 Thread Markus Zoeller
On 27.05.2016 11:36, Michael Still wrote: > Hi, > > I've spent some time today abandoning old reviews from the Nova queue. > Specifically, anything which hadn't been updated before February this year > has been abandoned with a message like this: > > "This patch has been idle for a long time, so

Re: [openstack-dev] [Nova] Abandoned old code reviews

2016-05-27 Thread Michael Still
I've always done it manually by eyeballing the review, but the script is tempting. Thanks, Michael On 27 May 2016 8:42 PM, "Sean Dague" wrote: > On 05/27/2016 05:36 AM, Michael Still wrote: > > Hi, > > > > I've spent some time today abandoning old reviews from the Nova queue. > > Specifically, a

Re: [openstack-dev] [kolla] prototype of a DSL for generating Dockerfiles

2016-05-27 Thread Britt Houser (bhouser)
I admit I'm not as knowledgable about the Kolla codebase as I'd like to be, so most of what you're saying is going over my head. I think mainly I don't understand the problem statement. It looks like you're pulling all the "hard coded" things out of the docker files, and making them user repla

Re: [openstack-dev] [Nova] Abandoned old code reviews

2016-05-27 Thread Sean Dague
On 05/27/2016 05:36 AM, Michael Still wrote: > Hi, > > I've spent some time today abandoning old reviews from the Nova queue. > Specifically, anything which hadn't been updated before February this > year has been abandoned with a message like this: > > "This patch has been idle for a long time,

[openstack-dev] [Nova] Abandoned old code reviews

2016-05-27 Thread Michael Still
Hi, I've spent some time today abandoning old reviews from the Nova queue. Specifically, anything which hadn't been updated before February this year has been abandoned with a message like this: "This patch has been idle for a long time, so I am abandoning it to keep the review clean sane. If you

Re: [openstack-dev] [Kuryr] Docker failed to add an existed network with GW interface already created

2016-05-27 Thread Liping Mao (limao)
Thanks Vikas for your help, it’s clear and helpful to me. Regards, Liping Mao From: Vikas Choudhary mailto:choudharyvika...@gmail.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: 2016年5月27日 星期五 下午4:32 To: OpenStack List mailto:openstack-dev@lists.openstack.org>>

Re: [openstack-dev] [Neutron] Mid-cycle development sprint

2016-05-27 Thread Rossella Sblendido
On 05/26/2016 10:47 PM, Henry Gessau wrote: > I am happy to announce that the location logistics for the Neutron mid-cycle > have been finalized. The mid-cycle will take place in Cork, Ireland on August > 15-17. I have updated the wiki [1] where you will find a link to an etherpad > with all the

Re: [openstack-dev] [ironic][neutron] bonding?

2016-05-27 Thread Moshe Levi
Hi Jim, Neutron is supporting resource tagging [1] which is support currently network resource_type With a simple change is neutron you can also allow resource tagging for port resource_type [2] This will allow you to tags ports and indicate that they are in the same group maybe that can work

Re: [openstack-dev] [all][tc] Languages vs. Scope of "OpenStack"

2016-05-27 Thread Thierry Carrez
Ed Leafe wrote: On May 25, 2016, at 7:25 AM, Denis Makogon wrote: Correct me if i'm wrong, none of the messages above were stating about support Go-extensions for Python (C extensions were mentioned couple times). Starting Go v1.5 it is possible to develop extension for Python [1] (lib that

Re: [openstack-dev] [Kuryr] Docker failed to add an existed network with GW interface already created

2016-05-27 Thread Vikas Choudhary
Hi Liping Mao, Please find my response inline. If still not clear or i am wrong somewhere please let me know. Regards Vikas On Fri, May 27, 2016 at 10:37 AM, 毛立平 wrote: > Hi Irena, > > Thanks for your comments. > > Currently, kuryr will create gw port with owner kuryr:container, but this > GW

Re: [openstack-dev] [higgins] Continued discussion from the last team meeting

2016-05-27 Thread Haiwei Xu
Hi all, +1 for starting with basic functionalities and hiding 'host' from end users. Regards, xuhaiwei -Original Message- From: Hongbin Lu [mailto:hongbin...@huawei.com] Sent: Friday, May 27, 2016 6:00 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [op

Re: [openstack-dev] [higgins][devstack][swift] Service name conflict in devstack

2016-05-27 Thread taget
hi Rana Thanks for you quick response, really appreciate of your help. On 2016年05月27日 14:45, Sheel Rana Insaan wrote: Dear Eli Qiao, >@Higgins team >I workaround it by naming them as "higgi-api" and "higgi-cond" (seems no magic in "-i") >Also, the api-port number as "9517", any comments? We