Re: [openstack-dev] Call for Commiters & Contributors for daisycloud-core project

Hi Zhijiang I think you can put Daisy into docker, then use ansible or kolla deploy Daisy. On Tue, May 31, 2016 at 9:43 AM, wrote: > Hi All, > > I would like to introduce to you a new OpenStack installer project > Daisy(project name: daisycloud-core). Daisy used to be a closed source > projec

Re: [openstack-dev] [qa] [Tempest] Abondoned old code reviews

+1! But I think we can leave patches created in 2016 and abandon others. Regards, Yaroslav Lobankov. On Mon, May 30, 2016 at 8:20 PM, Ken'ichi Ohmichi wrote: > Hi, > > There are many patches which are not updated in Tempest review queue > even if having gotten negative feedback from reviewers o

Re: [openstack-dev] [oslo] [keystone] rolling dogpile.core into dogpile.cache, removing namespace packaging (PLEASE REVIEW)

On 05/31/2016 12:17 AM, Mike Bayer wrote: > Hi all - > > Just a heads up what's happening for dogpile.cache, in version 0.6.0 we > are rolling the functionality of the dogpile.core package into > dogpile.cache itself, and retiring the use of namespace package naming > for dogpile.cache. > > Towar

Re: [openstack-dev] [Monasca] influxDB clustering and HA will be "commercial option".

On Mon, May 30 2016, Jaesuk Ahn wrote: > It seems like “clustering” and “high availablity” of influxDB will be > available only in commercial version. > Monasca is currently leveraging influxDB as a metrics and alarm database. > Beside vertical, influxDB is currently only an open source option to

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

Clint Byrum wrote: I 100% support those who are managing bugs doing whatever they need to do to make sure users' issues are being addressed as well as can be done with the resources available. However, I would also urge everyone to remember that the bug tracker is not only a way for developers to

Re: [openstack-dev] [vitrage] vitrage - how much links model in API is permanent?

Hi Eylon, This dictionary is created by NetworkX, and is not about to be changed. You can definitely rely on this API to be permanent. And we should make sure we have a tempest test for verifying it. Best regards, Ifat. > -Original Message- > From: Malin, Eylon (Nokia - IL) [mailto:eyl

[openstack-dev] [ironic] Tooling for recovering nodes

Hi, Recently, I am working on a spec[1] in order to recover nodes which get stuck in deploying state, so I really expect some feedback from you guys. Ironic nodes can be stuck in deploying/deploywait/cleaning/cleanwait/inspecting/deleting if the node is reserved by a dead conductor (the exclus

Re: [openstack-dev] [vitrage] vitrage - how much links model in API is permanent?

Good to know. Thank you very much. -Original Message- From: Afek, Ifat (Nokia - IL) [mailto:[email protected]] Sent: Tuesday, May 31, 2016 11:15 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [vitrage] vitrage - how much links model in

Re: [openstack-dev] [ironic] Tooling for recovering nodes

On 05/31/2016 10:25 AM, Tan, Lin wrote: Hi, Recently, I am working on a spec[1] in order to recover nodes which get stuck in deploying state, so I really expect some feedback from you guys. Ironic nodes can be stuck in deploying/deploywait/cleaning/cleanwait/inspecting/deleting if the node is

Re: [openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

On Tue, May 24, 2016 at 01:59:17PM -0400, Sean Dague wrote: > The team working on live migration testing started with an experimental > job on Ubuntu 16.04 to try to be using the latest and greatest libvirt + > qemu under the assumption that a set of issues we were seeing are > solved. The short an

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

The final patch https://review.openstack.org/#/c/321640/ has just merged, Devstack Horizon is fully functional and integration tests should be passing from this moment. If any of your patches are still failing due to dsvm-integration job's multiple failures, please rebase them. On Fri, May 27, 201

[openstack-dev] [infra] [devstack] [smaug] gate-smaug-dsvm-fullstack-nv is failed with exit code: 2

Hello team, The gate-smaug-dsvm-fullstack-nv is failed with exit code: 2. The console.html [1] includes the below information: Running devstack ERROR: the main setup script run by this job failed - exit code: 2 The devstacklog.txt.gz [2] includes the below information:+ functions-common:git_cl

Re: [openstack-dev] [mistral] Team meeting reminder - 05/30/2016

On 30 May 2016 at 08:40, Renat Akhmerov wrote: > Hi, > > This is a reminder about the team meeting that we’ll have today at 16.00 > UTC at #openstack-meeting. > > Agenda: > >- Review action items >- Current status (progress, issues, roadblocks, further plans) >- Newton-2 scope >-

Re: [openstack-dev] [infra] [devstack] [smaug] gate-smaug-dsvm-fullstack-nv is failed with exit code: 2

Hi xinyong, I remembered that I have seen this error times ago in my CI. Seems like nova doesn’t need noVNC before but now it needs noVNC to complete the installation. You need to clone noVNC into /opt/stack/new manually, or add noVNC project to the $PROJECTS variable in file like: /home/Jenki

[openstack-dev] [Nova] Live Migration meeting

Sorry for late update - this weekend was a holiday in UK Agenda: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lis

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

On 05/30/2016 10:26 AM, Loo, Ruby wrote: > Hi, > >> But the issue here is just capacity. Whether or not we keep an instance >> in a deleting state, or when we release quota, doesn't change the >> Tempest failures from what I can tell. The suggestions below address >> that. >> >> >>> >> >>

Re: [openstack-dev] [python-keystoneclient] Return request-id to caller

Hi, keystone devs, Thank you for your many opinions about request id mapping. I fixed this patch [1] by the way that Brant and Cao gave me suggestions [2]. Could you review it? [1] https://review.openstack.org/#/c/261188/ [2] http://paste.openstack.org/show/495040/ Thank you, On Wed, 20 Apr 201

[openstack-dev] ?????? [infra] [devstack][smaug] gate-smaug-dsvm-fullstack-nv is failed with exit code: 2

Hi Wilson, Thanks very much. You find the key. I also get some information from here. [1] https://review.openstack.org/#/q/project:openstack-infra/project-config+novnc Best Regards, xiangxinyong Wilson Liu 2016-05-31 PM 7:26 wrote >> Hi xinyong, >> >> I remembered that I have se

Re: [openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

On 05/30/2016 06:25 AM, Kashyap Chamarthy wrote: > On Thu, May 26, 2016 at 10:55:47AM -0400, Sean Dague wrote: >> On 05/26/2016 05:38 AM, Kashyap Chamarthy wrote: >>> On Wed, May 25, 2016 at 05:42:04PM +0200, Kashyap Chamarthy wrote: >>> >>> [...] >>> So, in short, the central issue seems to b

Re: [openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

On 05/31/2016 05:39 AM, Daniel P. Berrange wrote: > On Tue, May 24, 2016 at 01:59:17PM -0400, Sean Dague wrote: >> The team working on live migration testing started with an experimental >> job on Ubuntu 16.04 to try to be using the latest and greatest libvirt + >> qemu under the assumption that a

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

On 05/30/2016 02:37 PM, Clint Byrum wrote: > (Top posting as a general reply to the thread) > > Bugs are precious data. As much as it feels like the bug list is full of > cruft that won't ever get touched, one thing that we might be missing in > doing this is that the user who encounters the bug a

Re: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

On 05/30/2016 04:02 PM, Shoham Peller wrote: > I support Clint's comment, and as an example, only today I was able to > search a bug and to see it was reported 2 years ago and wasn't solved since. > I've commented on the bug saying it happened to me in an up-to-date nova. > I'm talking about a bug

Re: [openstack-dev] [nova] API changes on limit / marker / sort in Newton

On 05/30/2016 10:05 PM, Zhenyu Zheng wrote: > I think it is good to share codes and a single microversion can make > life more easier during coding. > Can we approve those specs first and then decide on the details in IRC > and patch review? Because > the non-priority spec deadline is so close. >

[openstack-dev] [infra][shade] Proposing Ricardo Carrillo Cruz for Shade core

Ricardo has been working with shade for a while now, has been great at helping out with reviews, and has offered some quality code contributions. He has showed a good understanding of the code base and coding guidelines, and has been helping to review (and adding to) the new OpenStack Ansible modul

Re: [openstack-dev] [infra][shade] Proposing Ricardo Carrillo Cruz for Shade core

On 05/31/2016 08:53 AM, David Shrewsbury wrote: > Ricardo has been working with shade for a while now, has been great at > helping out with reviews, and has offered some quality code contributions. > He has showed a good understanding of the code base and coding guidelines, > and has been helping t

[openstack-dev] [Monasca] Selectively publish logs to topics

Hi Venkat, thank you for submitting the blueprint [1]. It covers actually two topics, both of them a valuable functional extension: 1) submitting additional (apart from dimensions) information with the logs 2) specifying a specific output topic ad. 1 I think we should keep it generic to allow

Re: [openstack-dev] [infra][shade] Proposing Ricardo Carrillo Cruz for Shade core

Quoting Monty Taylor (2016-05-31 15:00:10) > On 05/31/2016 08:53 AM, David Shrewsbury wrote: > > Ricardo has been working with shade for a while now, has been great at > > helping out with reviews, and has offered some quality code contributions. > > He has showed a good understanding of the code b

Re: [openstack-dev] [mistral] Team meeting reminder - 05/30/2016

That’s no problem! I knew about the holiday ) Renat Akhmerov @Nokia > On 31 May 2016, at 18:05, Dougal Matthews wrote: > > > > On 30 May 2016 at 08:40, Renat Akhmerov > wrote: > Hi, > > This is a reminder about the team meeting that we’ll have today at 16.00

Re: [openstack-dev] How to list all the servers of a user across projects

Link: https://openstack.nimeyo.com/86042/?show=86116#a86116 From: imocha http://localhost:8774/v2.1/a90db774c8fb48b290a161f075a862f6/servers/detail?all_tenants=1&user_id=d3d1ffa545c840148aeeffa62b69aa06 I am able to achieve the functionality using the above api. However, if requires admin role

Re: [openstack-dev] Call for Commiters & Contributors for daisycloud-core project

Hi Shake, Kolla is mainly used for containerzing OpenStack components. But before that, Kolla needs installer to do node discovery as well as OS provisioning. So there should be a installer at the first place which then calls into Kolla or alternative s such as packstack to deploy OpenStack. I ag

[openstack-dev] New core reviewers nomination for TOSCA-Parser and or Heat-Translator project [tosca-parser][heat-translator][heat]

Hello TOSCA-Parser and Heat-Translator core team, I would like to nominate following current active contributors to the tosca-parser and or heat-translator project as core reviewers to speed up the development. They are contributing for more than six months and has remained one of the top five

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

"But if ODL is not supporting its own NSH capable dataplane, instead expecting the user to run a patched OvS that doesn't have upstream acceptance then I think we would be building a rickety tower by piling networking-sfc on top of that unstable base." ODL requires a patched OvS too [1]. [1]

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

On Fri, May 27, 2016 at 12:08 PM, Ryan Hallisey wrote: Theses changes do not all happen at the same times for an OpenStack installation. > - Create the service's users and add a password into the databse Should only happen once during installation. > - Sync the service with the databas

Re: [openstack-dev] [Neutron] Mid-cycle development sprint (NOTE: DATE CHANGE!)

Thierry Carrez wrote: > 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 wik

Re: [openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

On Tue, May 31, 2016 at 08:24:03AM -0400, Sean Dague wrote: > On 05/31/2016 05:39 AM, Daniel P. Berrange wrote: > > On Tue, May 24, 2016 at 01:59:17PM -0400, Sean Dague wrote: > >> The team working on live migration testing started with an experimental > >> job on Ubuntu 16.04 to try to be using th

Re: [openstack-dev] [gate] [nova] live migration, libvirt 1.3, and the gate

On Tue, May 31, 2016 at 08:19:33AM -0400, Sean Dague wrote: > On 05/30/2016 06:25 AM, Kashyap Chamarthy wrote: > > On Thu, May 26, 2016 at 10:55:47AM -0400, Sean Dague wrote: > >> On 05/26/2016 05:38 AM, Kashyap Chamarthy wrote: > >>> On Wed, May 25, 2016 at 05:42:04PM +0200, Kashyap Chamarthy wrot

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

On Tue, May 31, 2016 at 8:41 AM David Stanek wrote: > On Fri, May 27, 2016 at 12:08 PM, Ryan Hallisey > wrote: > > Theses changes do not all happen at the same times for an OpenStack > installation. > > > - Create the service's users and add a password into the databse > > Should only happen

Re: [openstack-dev] [Docs] Enhance Docs Landing Page Descriptive Text

On 2016-05-14 00:08, Laura Clymer wrote: > Hi everyone, > > In the current Ubuntu install guide, there is this > section:http://docs.openstack.org/mitaka/install-guide-ubuntu/common/app_support.html > > It contains a good deal of description on the type of information > contained in each of the r

Re: [openstack-dev] [infra][shade] Proposing Ricardo Carrillo Cruz for Shade core

Only great words about Ricardo. He has been working hard on shade and ansible, he will be a great addition to shade-core team. Yolanda Robla Mota Cloud automation and Distribution Engineer [email protected] +34 605641639 Spain De: Monty Taylor Env

Re: [openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

On 05/30/2016 11:22 PM, Cheng, Yingxin wrote: Hi, cdent: This problem arises because the RT(resource tracker) only knows to consume the DISK resource in its host, but it still doesn’t know exactly which resource provider to place the consumption. That is to say, the RT still needs to *find* the

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

On Mon, May 30, 2016 at 10:12:34PM -0400, Paul Carver wrote: > I don't know the details of why OvS hasn't added NSH support so I can't > judge the validity of the concerns, but one way or another there has to be a > production-quality dataplane for networking-sfc to front-end. It looks like the la

Re: [openstack-dev] [tripleo] weekly meeting

On Mon, May 30, 2016 at 8:45 AM, Emilien Macchi wrote: > Hi! > > We'll have our weekly meeting tomorrow at 2pm UTC on > #openstack-meeting-alt. > > Here's a first agenda: > https://wiki.openstack.org/wiki/Meetings/TripleO#Agenda_for_next_meeting > > Feel free to add more topics, and any outstandin

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

Hey Paul, ODL uses OVS as its dataplane (but is also not limited to just OVS), and ODL already supports IETF SFC today in the ODL SFC project. My point was Neutron is no longer in scope of managing OVS, since it is managed by ODL. I think your comments echo the 2 sides of this discussion - whe

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

On Mon, May 30, 2016 at 8:34 AM, Emilien Macchi wrote: > Hi Puppeteers! > > We'll have our weekly meeting tomorrow at 3pm UTC on > #openstack-meeting-4. > > Here's a first agenda: > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160531 > >

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

Hi Tim, +1 Focus on the plugin and API while improving the n-sfc<->ODL interaction to match that. In parallel, early (non-merged) support in OVS driver itself could be attempted, based on the unofficial April 2016's NSH patches for OVS [1]. After official supports gets merged, it would be less

Re: [openstack-dev] [infra][shade] Proposing Ricardo Carrillo Cruz for Shade core

On 2016-05-31 08:53:22 -0400 (-0400), David Shrewsbury wrote: > Ricardo has been working with shade for a while now, has been > great at helping out with reviews, and has offered some quality > code contributions. He has showed a good understanding of the code > base and coding guidelines, and has

Re: [openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

On 05/29/2016 06:19 PM, Chris Dent wrote: This gets a bit complex (to me) but: The idea for step 4 is that the resource tracker will be modified such that: * if the compute node being claimed by an instance is a member of some aggregates * and one of those aggregates is associated with a res

Re: [openstack-dev] [Openstack-operators] [glance] Proposal for a mid-cycle virtual sync on operator issues

Hey, Thanks for the feedback. 0800UTC is 4am EDT for some of the US Glancers :-) I request this time which may help the folks in Eastern and Central US time. http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016&month=6&day=7&hour=11&min=0&sec=0&p1=881&p2=196&p3=47&p4=22&p5=157&p6

Re: [openstack-dev] [tc] [heat] [murano] [app-catalog] OpenStack Apps Community, several suggestions how to improve collaboration

Hi Infra, Murano and App Catalog teams. We discussed in some more details plan suggested below with App Catalog, Murano and (partially) Infra team regarding moving repositories with source code of Murano applications out of area of responsibility of Murano core team. * *First part related wit

Re: [openstack-dev] [tc] [heat] [murano] [app-catalog] OpenStack Apps Community, several suggestions how to improve collaboration

Sergey, Great initiative, +1 from me. On May 31, 2016 7:24 PM, "Sergey Kraynev" wrote: > Hi Infra, Murano and App Catalog teams. > > We discussed in some more details plan suggested below with App Catalog, > Murano and (partially) Infra team regarding moving repositories with source > code of Mu

Re: [openstack-dev] [kolla][security] Finishing the job on threat analysis for Kolla

Thanks for following up Steve, the sessions at the summit were extremely useful. Both Rob and I have been caught up with the day-job since we got back from the summit, but will discuss next steps and agree a plan this week. Regards Doug From: "Steven Dake (stdake)" mailto:[email protected]>>

Re: [openstack-dev] [tc] [heat] [murano] [app-catalog] OpenStack Apps Community, several suggestions how to improve collaboration

On 2016-05-31 19:20:22 +0300 (+0300), Sergey Kraynev wrote: [...] > * *Second part related with changes with future repositories and* > important for Openstack Infra team * > JFYI, what we plan to do as next steps. > > Murano team will re-create some applications in their repositories usin

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall wrote on 05/26/2016 10:59:48 AM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS, Ben Pfaff > Cc: "[email protected]" , Justin > Pettit , OpenStack Development Mailing List > , Russell Bryant > Date: 05/26/2016 11:00 AM > Subject: Re: [OVN] [networking-ovn] [networ

Re: [openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

On Tue, 31 May 2016, Jay Pipes wrote: Kinda. What the compute node needs is an InventoryList object containing all inventory records for all resource classes both local to it as well as associated to it via any aggregate-resource-pool mapping. Okay, that mostly makes sense. A bit different fr

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

We should add a section to our docs that details the config option names, their descriptions, and which ones are required. We should backport that to mitaka and maybe liberty. Tim On Mon, May 30, 2016 at 12:49 AM Masahito MUROI < [email protected]> wrote: > Hi Bryan, > > > On 2016/05

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall wrote on 05/26/2016 11:08:43 AM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff , "[email protected]" > , Justin Pettit , > "OpenStack Development Mailing List" [email protected]>, Russell Bryant > Date: 05/26/2016 11:09 AM > Subject: Re: [O

[openstack-dev] [ironic] looking for documentation liaison

Hi, We¹re looking for a documentation liaison [1]. If you love (Œlike¹ is also acceptable) documentation, care that ironic has great documentation, and would love to volunteer, please let us know. The position would require you to: - attend the weekly doc team meetings [2] (or biweekly, depend

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

Ryan, I agree that having rules in the ACL table with actions that would steer the packets to SFC Processing would be a good approach. -Louis From: Ryan Moats [mailto:[email protected]] Sent: Tuesday, May 31, 2016 10:18 AM To: John McDowall Cc: Justin Pettit; Russell Bryant; Ben Pfaff

[openstack-dev] [higgins] Docker-compose support

Hello Stackers. As part of discussions around what Higgins is and what its mission there are were couple of you who mentioned docker-compose [1] and necessity of doing the same thing for Higgins but from scratch. I don't think that going that direction is the best way to spend development cycles

Re: [openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

On 05/31/2016 01:06 PM, Chris Dent wrote: On Tue, 31 May 2016, Jay Pipes wrote: Kinda. What the compute node needs is an InventoryList object containing all inventory records for all resource classes both local to it as well as associated to it via any aggregate-resource-pool mapping. Okay, th

Re: [openstack-dev] [qa] [Tempest] Abondoned old code reviews

On Mon, 30 May 2016, 6:25 p.m. Ken'ichi Ohmichi, wrote: > Hi, > > There are many patches which are not updated in Tempest review queue > even if having gotten negative feedback from reviewers or jenkins. > Nova team is abandoning such patches like [1]. > I feel it would be nice to abandone such p

[openstack-dev] [Neutron][Release] Changing release model for *-aas services

Hi folks, Having looked at the recent commit volume that has been going into the *-aas repos, I am considering changing the release model for neutron-vpnaas, neutron-fwaas, neutron-lbaas from release:cycle-with-milestones [1] to release:cycle-with-intermediary [2]. This change will allow us to avo

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

> On 31 May 2016, at 20:12, Armando M. wrote: > > Hi folks, > > Having looked at the recent commit volume that has been going into the *-aas > repos, I am considering changing the release model for neutron-vpnaas, > neutron-fwaas, neutron-lbaas from release:cycle-with-milestones [1] to > rel

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

On 31 May 2016 at 11:17, Ihar Hrachyshka wrote: > > > On 31 May 2016, at 20:12, Armando M. wrote: > > > > Hi folks, > > > > Having looked at the recent commit volume that has been going into the > *-aas repos, I am considering changing the release model for > neutron-vpnaas, neutron-fwaas, neutr

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

On Tue, May 31, 2016 at 1:12 PM, Armando M. wrote: > Hi folks, > > Having looked at the recent commit volume that has been going into the *-aas > repos, I am considering changing the release model for neutron-vpnaas, > neutron-fwaas, neutron-lbaas from release:cycle-with-milestones [1] to > releas

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

"Armando M." wrote on 05/31/2016 01:12:32 PM: > From: "Armando M." > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 05/31/2016 01:13 PM > Subject: [openstack-dev] [Neutron][Release] Changing release model > for *-aas services > > Hi folks, > > Having looked at t

Re: [openstack-dev] [cinder][nova] Multi-attach/Cinder-Nova weekly IRC meetings

Hi All, We skipped the Monday slot this week due to the holiday in the US. __Only this week__ we will hold the meeting on __Thursday, 1700UTC__ on the __#openstack-meeting-cp__ channel. Related etherpad: https://etherpad.openstack.org/p/cinder-nova-api-changes Thanks and Best Regards, /Ildikó

Re: [openstack-dev] [higgins] Docker-compose support

Cool good to know, I see https://github.com/docker/compose/pull/3535/files#diff-1d1516ea1e61cd8b44d000c578bbd0beR66 Would that be the primary API? Hard to tell what is the API there actually, haha. Is it the run() method? I was thinking more along the line that higgins could be a 'interpret

Re: [openstack-dev] [ironic] Tooling for recovering nodes

On 05/31/2016 01:35 AM, Dmitry Tantsur wrote: > On 05/31/2016 10:25 AM, Tan, Lin wrote: >> Hi, >> >> Recently, I am working on a spec[1] in order to recover nodes which get stuck >> in deploying state, so I really expect some feedback from you guys. >> >> Ironic nodes can be stuck in >> deploying/d

Re: [openstack-dev] [higgins] Docker-compose support

Hello. It is hard to tell if given API will be final version, but i tried to make it similar to CLI and its capabilities. So, why not? 2016-05-31 22:02 GMT+03:00 Joshua Harlow : > Cool good to know, > > I see > https://github.com/docker/compose/pull/3535/files#diff-1d1516ea1e61cd8b44d000c578bbd0

Re: [openstack-dev] [nova] [placement] aggregates associated with multiple resource providers

On Tue, 31 May 2016, Jay Pipes wrote: So this seem rather fragile and pretty user-hostile. We're creating an opportunity for people to easily replace their existing bad tracking of disk usage with a different style of bad tracking of disk usage. I'm not clear why the new way of tracking disk u

Re: [openstack-dev] [higgins] Docker-compose support

Denis Makogon wrote: Hello. It is hard to tell if given API will be final version, but i tried to make it similar to CLI and its capabilities. So, why not? 2016-05-31 22:02 GMT+03:00 Joshua Harlow mailto:[email protected]>>: Cool good to know, I see https://github.com/docker/

[openstack-dev] [Nova] State machines in Nova

Hi team, there is blueprint[1] that was approved during Liberty and resubmitted to Newton(with spec[2]). The idea is to define state machines for operations as live-migration, resize, etc. and to deal with them operation states. The spec PoC patches are overall good. At the same time I think is wi

Re: [openstack-dev] [higgins] Docker-compose support

I don’t think it is a good to re-invent docker-compose in Higgins. Instead, we should leverage existing libraries/tools if we can. Frankly, I don’t think Higgins should interpret any docker-compose like DSL in server, but maybe it is a good idea to have a CLI extension to interpret specific DSL

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

Ryan, Hopefully – just wanted to make sure it was there. Regards John From: Ryan Moats mailto:[email protected]>> Date: Tuesday, May 31, 2016 at 10:02 AM To: John McDowall mailto:[email protected]>> Cc: Ben Pfaff mailto:[email protected]>>, "[email protected]

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

Ryan, Let me add the tables to OVN for SFC. That will give us a working system to prototype the flow classifier approach on. Hopefully I can get something done by end of week. Regards John From: Ryan Moats mailto:[email protected]>> Date: Tuesday, May 31, 2016 at 10:17 AM To: John McDowall m

Re: [openstack-dev] [Nova] State machines in Nova

Timofei Durakov wrote: Hi team, there is blueprint[1] that was approved during Liberty and resubmitted to Newton(with spec[2]). The idea is to define state machines for operations as live-migration, resize, etc. and to deal with them operation states. The spec PoC patches are overall good. At th

Re: [openstack-dev] [Openstack-operators] [glance] Proposal for a mid-cycle virtual sync on operator issues

Hi Nikhil, I'm interested in this discussion. Initially you were proposing Thursday June 9th, 2016 at 2000UTC. Are you suggesting to change also the date? Because in the new timeanddate suggestions is 6/7 of June. Belmiro On Tue, May 31, 2016 at 6:13 PM, Nikhil Komawar wrote: > Hey, > > > Than

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

I am opposed to this idea as I don't think we need this. We can solve many problems by using jinja2 to greater extend. I'll publish demo of few improvements soon, please bear with me before we make a arch-changing call. On 29 May 2016 at 14:41, Steven Dake (stdake) wrote: > >>On 5/27/16, 1:58 AM,

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall wrote on 05/31/2016 03:19:54 PM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff , "[email protected]" > , Justin Pettit , > "OpenStack Development Mailing List" [email protected]>, Russell Bryant > Date: 05/31/2016 03:20 PM > Subject: Re: [OVN

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

John McDowall wrote on 05/31/2016 03:21:30 PM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff , "[email protected]" > , Justin Pettit , > "OpenStack Development Mailing List" [email protected]>, Russell Bryant > Date: 05/31/2016 03:22 PM > Subject: Re: [OVN

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

On Mon, May 30, 2016 at 6:12 PM, Steve Baker wrote: > This raises the possibility of an alternative to OVB for trying/developing > TripleO on a host cloud. > > If a vm version of the overcloud-full image is also generated then the host > cloud can boot these directly. The approach above can then b

Re: [openstack-dev] [Neutron] Question about service subnets spec

Thanks Carl for bringing this up, comments below. On 05/26/2016 02:04 PM, Carl Baldwin wrote: Hi folks, Some (but not all) of you will remember a discussion we had about service subnets at the last mid-cycle. We've been iterating a little bit on a spec [1] and we have just one issue that we'd

Re: [openstack-dev] [Openstack-operators] [glance] Proposal for a mid-cycle virtual sync on operator issues

Hey, Thanks for your interest. Sorry about the confusion. Please consider the same time for Thursday June 9th. Thur June 9th proposed time: http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016&month=6&day=9&hour=11&min=0&sec=0&p1=881&p2=196&p3=47&p4=22&p5=157&p6=87&p7=24&p8=78&p

[openstack-dev] [Higgins] Proposing Eli Qiao to be a Higgins core

Hi team, I wrote this email to propose Eli Qiao (taget-9) to be a Higgins core. Normally, the requirement to join the core team is to consistently contribute to the project for a certain period of time. However, given the fact that the project is new and the initial core team was formed based o

Re: [openstack-dev] [Nova] State machines in Nova

On Tue, May 31, 2016, at 04:26 PM, Joshua Harlow wrote: > Timofei Durakov wrote: > > Hi team, > > > > there is blueprint[1] that was approved during Liberty and resubmitted > > to Newton(with spec[2]). > > The idea is to define state machines for operations as live-migration, > > resize, etc. and

Re: [openstack-dev] [Higgins] Proposing Eli Qiao to be a Higgins core

+1 On 01/06/16 09:39, Hongbin Lu wrote: > > Hi team, > > > > I wrote this email to propose Eli Qiao (taget-9) to be a Higgins core. > Normally, the requirement to join the core team is to consistently > contribute to the project for a certain period of time. However, given > the fact that the pr

[openstack-dev] [Higgins] Call for contribution for Higgins API design

Hi team, As discussed in the last team meeting, we agreed to define core use cases for the API design. I have created a blueprint for that. We need an owner of the blueprint and it requires a spec to clarify the API design. Please let me know if you interest in this work (it might require a sig

Re: [openstack-dev] [Nova] State machines in Nova

Andrew Laski wrote: On Tue, May 31, 2016, at 04:26 PM, Joshua Harlow wrote: Timofei Durakov wrote: Hi team, there is blueprint[1] that was approved during Liberty and resubmitted to Newton(with spec[2]). The idea is to define state machines for operations as live-migration, resize, etc. and t

[openstack-dev] [ironic] [oslo] Template to follow for policy support?

Hi all, During this cycle, on behalf of OSIC, I'll be working on implementing proper oslo.policy support for Ironic. The reasons this is needed probably don't need to be explained here, so I won't :). I have two requests for the list regarding this though: 1) Is there a general guideline to

Re: [openstack-dev] [Higgins] Proposing Eli Qiao to be a Higgins core

+1, He will become a good contributor! 2016年6月1日(水) 7:14 Fei Long Wang : > +1 > > > On 01/06/16 09:39, Hongbin Lu wrote: > > Hi team, > > > > I wrote this email to propose Eli Qiao (taget-9) to be a Higgins core. > Normally, the requirement to join the core team is to consistently > contribute

Re: [openstack-dev] [Neutron][vpnaas]Question about MPLS VPN

On 5/26/2016 02:50, zhangyali (D) wrote: I am interested in the VPNaaS project in Neutron. Now I notice that only IPsec tunnel has completed, but other types of VPN, such as, MPLS/BGP, have not completed. I'd like to know how's going about MPLS/BGP vpn? What's the mechanism or extra work need

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

Ben, yes, we submitted nsh support patch set last year, but ovs community told me we have to push kernel part into Linux kernel tree, we're struggling to do this, but something blocked us from doing this. Recently, ovs did some changes in tunnel protocols which requires the packet decapsulated

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

On 5/31/16, 1:42 PM, "Michał Jastrzębski" wrote: >I am opposed to this idea as I don't think we need this. We can solve >many problems by using jinja2 to greater extend. I'll publish demo of >few improvements soon, please bear with me before we make a >arch-changing call. Can you make a specif

Re: [openstack-dev] [OVN] [networking-ovn] [networking-sfc] SFC and OVN

Ryan, More help is always great :-). As far as who to collaborate, what ever Is easiest for everyone – I am pretty flexible. Regards John From: Ryan Moats mailto:[email protected]>> Date: Tuesday, May 31, 2016 at 1:59 PM To: John McDowall mailto:[email protected]>> Cc: Ben Pfaff

Re: [openstack-dev] [Higgins] Call for contribution for Higgins API design

Dear Hongbin, I am interested in this. Thanks!! Best Regards, Sheel Rana On Jun 1, 2016 3:53 AM, "Hongbin Lu" wrote: > Hi team, > > > > As discussed in the last team meeting, we agreed to define core use cases > for the API design. I have created a blueprint for that. We need an owner > of the

Re: [openstack-dev] [Higgins] Proposing Eli Qiao to be a Higgins core

+1, welcome, Eli :) 2016-06-01 7:07 GMT+08:00 Yuanying OTSUKA : > +1, He will become a good contributor! > > > > 2016年6月1日(水) 7:14 Fei Long Wang : > >> +1 >> >> >> On 01/06/16 09:39, Hongbin Lu wrote: >> >> Hi team, >> >> >> >> I wrote this email to propose Eli Qiao (taget-9) to be a Higgins core

Re: [openstack-dev] [Higgins] Proposing Eli Qiao to be a Higgins core

Eli seems strong addition to team, I am happy to have Eli Qiao's expertise in core team. +1 from my side. Best Regards, Sheel Rana On Jun 1, 2016 3:09 AM, "Hongbin Lu" wrote: > Hi team, > > > > I wrote this email to propose Eli Qiao (taget-9) to be a Higgins core. > Normally, the requirement t

Re: [openstack-dev] [higgins] Should we rename "Higgins"?

Shu, According to the feedback from the last team meeting, Gatling doesn't seem to be a suitable name. Are you able to find an alternative name? Best regards, Hongbin > -Original Message- > From: Shuu Mutou [mailto:[email protected]] > Sent: May-24-16 4:30 AM > To: openstack-dev@l

Re: [openstack-dev] [Higgins] Proposing Eli Qiao to be a Higgins core

+1 Welcome Eli -- Dims On Tue, May 31, 2016 at 9:22 PM, Yanyan Hu wrote: > +1, welcome, Eli :) > > 2016-06-01 7:07 GMT+08:00 Yuanying OTSUKA : >> >> +1, He will become a good contributor! >> >> >> >> 2016年6月1日(水) 7:14 Fei Long Wang : >>> >>> +1 >>> >>> >>> On 01/06/16 09:39, Hongbin Lu wrote: >>

  1   2   >