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

+1 for Zun, I love it and it's definitely a good container :) On 02/06/16 15:46, Monty Taylor wrote: > On 06/02/2016 06:29 AM, 秀才 wrote: >> i suggest a name Zun :) >> please see the reference: https://en.wikipedia.org/wiki/Zun > It's available on pypi and launchpad. I especially love that one of

[openstack-dev] [Monasca] "The server is currently unavailable. on Monasca service

Hello, I am seeing the following issue after installing Monasca recently as a devstack environment" stack@scsor0002143001-pradipm:~/devstack$ monasca metric-list ERROR (exc:80) exception: {"message": "The server is currently unavailable. Please try again at a later time.\n\n\n", "code": "503

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

Hi Hongbin, I also liked the idea of having heterogeneous set of nodes but IMO such features should not be implemented in Magnum, thus deviating Magnum again from its roadmap. Whereas we should leverage Heat(or may be Senlin) APIs for the same. I vote +1 for this feature. Regards, Madhuri

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

On 06/02/2016 06:29 AM, 秀才 wrote: > i suggest a name Zun :) > please see the reference: https://en.wikipedia.org/wiki/Zun It's available on pypi and launchpad. I especially love that one of the important examples is the "Four-goat square Zun"

Re: [openstack-dev] Kilo end of life

On 06/01/2016 11:19 PM, Matt Riedemann wrote: > FYI, I've got some changes up to project-config and the releases repo to > mark kilo as end of life [1]. Andreas has done the same for the manuals. > > The project-config changes remove the kilo periodic job definitions and > usage from all repos,

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

i suggest a name Zun :) please see the reference: https://en.wikipedia.org/wiki/Zun Regards XiuCai -- Original -- From: "Rochelle Grober";; Date: Thu, Jun 2, 2016 09:47 AM To: "OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John, Thanks your reply. Seems you have covered everything :) The development work can be broken down in 3 parts: 1, add ovn driver to networking-sfc 2, provide APIs in networking-ovn for networking-sfc 3, implement the sfc in ovn So what about we take part 1 and part 2, and you take part

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

Well, you could stick with the wine bottle analogy and go with a bigger size: Jeroboam Methuselah Salmanazar Balthazar Nabuchadnezzar --Rocky -Original Message- From: Kumari, Madhuri [mailto:madhuri.kum...@intel.com] Sent: Wednesday, June 01,

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

Replies inline, please check. -Original Message- From: Elzur, Uri [mailto:uri.el...@intel.com] Sent: Thursday, June 02, 2016 9:19 AM To: OpenStack Development Mailing List (not for usage questions) ; Cathy Zhang ;

Re: [openstack-dev] [TripleO][diskimage-builder] Proposing Stephane Miller to dib-core

On 06/01/2016 12:50 PM, Gregory Haynes wrote: > Hello everyone, > > I'd like to propose adding Stephane Miller (cinerama) to the > diskimage-builder core team. She has been a huge help with our reviews > for some time now and I think she would make a great addition to our > core team. I know I

[openstack-dev] [Kolla] About kolla-ansible reconfigure

Hi After modifying the kolla_internal_vip_address in /etc/kolla/global.yml , I use kolla-ansible reconfigure to reconfigure OpenStack. But I got the following error. TASK: [mariadb | Restart containers] ** skipping: [localhost] => (item=[{'group':

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

Few comments below Thx Uri ("Oo-Ree") C: 949-378-7568 -Original Message- From: Yang, Yi Y [mailto:yi.y.y...@intel.com] Sent: Wednesday, June 1, 2016 5:20 PM To: Cathy Zhang ; OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [kolla] Ansible 2.0.0 functional

2.0, 2.0.1.0 and 2.1 were all fine for me for the most part. 2.0.2.0 was a regression disaster for us (yup, a 0.0.1 increment) but thankfully they fixed the issues for 2.1. David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Wed, Jun 1, 2016 at

[openstack-dev] [QA] Meeting Thursday June 2nd at 9:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, June 2nd at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_June_2nd_2016_.280900_UTC.29

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

Indeed, but I saw an exceptional case, LISP, it is in ovs but not in Linux kernel. For our nsh patches, kernel is easier than ovs. -Original Message- From: Ben Pfaff [mailto:b...@ovn.org] Sent: Thursday, June 02, 2016 7:17 AM To: OpenStack Development Mailing List (not for usage

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

Also cc to Jiri and Jesse, I think mandatory L3 requirement is not reasonable for tunnel port, say VxLAN or VxLAN-gpe, its intention is to L2 over L3, so L2 header is must-have, but mandatory L3 requirement removed L2. I also think VxLAN + Eth + NSH + Original frame should be an option, at

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

Some comments inline. On 5/31/16 12:26 PM, Devananda van der Veen wrote: 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

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

Hey Tan, some comments inline. On 5/31/16 1: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

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

I'm probably the wrong person to give advice on kernel development, since I haven't been involved in it for years. I just know that it's difficult, and not always because of the code. It's hard to support a protocol in OVS before it's supported in the kernel, since userspace without a kernel

Re: [openstack-dev] [kolla] Ansible 2.0.0 functional

Jeffrey, I'm not experienced enough in writing plugins to give you a good answer. You should pop into #ansible-devel and ask your question there. -Dave On Wed, Jun 1, 2016 at 5:59 PM, Jeffrey Zhang wrote: > ​David, > > is there any standard way to create the _tmp

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

Pls note that VXLAN-gpe and VXLAN are using different UDP ports. Lots of consideration and discussion went into this working on the IETF draft and on ODL implementations. So I'm not sure I follow the backwards compatibility issues raised below In any rate, the Ovs-Eth-NSH could be making

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

Cathy So we are ok moving forward on networking-sfc? What is the next step from your pov? Thx Uri ("Oo-Ree") C: 949-378-7568 -Original Message- From: Cathy Zhang [mailto:cathy.h.zh...@huawei.com] Sent: Wednesday, June 1, 2016 11:58 AM To: OpenStack Development Mailing List (not for

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

Personally, I think this is a good idea, since it can address a set of similar use cases like below: * I want to deploy a k8s cluster to 2 availability zone (in future 2 regions/clouds). * I want to spin up N nodes in AZ1, M nodes in AZ2. * I want to scale the number of nodes in specific

[openstack-dev] [Neutron][networking-sfc] meeting topics for 6/1/2016 networking-sfc project IRC meeting

Hi everyone, The following link shows the topics I have for this week's project meeting discussion(The meeting time is not changed, still UTC 1700 Thursday). Feel free to add more. https://wiki.openstack.org/wiki/Meetings/ServiceFunctionChainingMeeting Meeting Info: Every Thursday 1700 UTC on

[openstack-dev] [puppet] 8.1.0 released (Mitaka)

Hi, We're happy to announce the release of 8.1.0 (Mitaka). All you need to know is documented here: http://releases.openstack.org/teams/puppet_openstack.html You'll also find tarballs and release notes. Thanks to our group for the hard work! Regards, -- Emilien Macchi

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

+1 from me too How do we close on this thread? Is anyone on the ml, NOT cool with this approach as outlined by Tim below? Thx Uri ("Oo-Ree") C: 949-378-7568 -Original Message- From: Duarte Cardoso, Igor [mailto:igor.duarte.card...@intel.com] Sent: Tuesday, May 31, 2016 8:48 AM To:

Re: [openstack-dev] [kolla] Ansible 2.0.0 functional

​David, is there any standard way to create the _tmp path? ansible 2.0 and ansible 2.1 have not the same function signature. [0] [0]​ https://github.com/openstack/kolla/blob/master/ansible/action_plugins/merge_configs.py#L45,L54 On Wed, Jun 1, 2016 at 9:53 PM, David Shrewsbury

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

Hi Ben Any guidance you can offer will be appreciated. The process has taken long time and precious cycles. How can we get to a coordinated Kernel and OvS approach to avoid the challenges and potentially misaligned advise we got (per Yi Yang's mail)? Thx Uri ("Oo-Ree") C: 949-378-7568

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

Interesting way to combine taskflow + celery. I didn't expect it to be used like this, but the more power to you! Taskflow itself has some similar capabilities via http://docs.openstack.org/developer/taskflow/workers.html#design but anyway what u've done is pretty neat as well. I am

[openstack-dev] [heat][swift] New TC Resolutions on DefCore Tests

Hi Everyone, At today’s DefCore Committee meeting, we discussed a couple of newly-approved TC resolutions and wanted to take a quick moment to make folks aware of them in case they weren’t already. These new resolutions may impact what capabilities and tests projects ask to have included in

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

Aaaand correct link: https://review.openstack.org/#/c/323589/ sorry for pastefail. On 1 June 2016 at 15:55, Michał Jastrzębski wrote: > So this is prototype of working template overrides: > https://review.openstack.org/#/c/323612/ > > Pass --template-overrides=path-to-file to

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

So this is prototype of working template overrides: https://review.openstack.org/#/c/323612/ Pass --template-overrides=path-to-file to build.py in file override you can add any custom code/logic/dockerfile stuff to any of hooks we provide in Dockerfiles, and we'll provide a lot of them as it's

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

Just a reminder, dogpile.cache is doing away with namespace packaging in version 0.6.0, due for the end of this week or sometime next week. dogpile.core is being retired and left as-is. No changes should be needed by anyone using only dopgile.cache. On 05/30/2016 06:17 PM, Mike Bayer

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

On 5/31/2016 7:35 AM, Sean Dague wrote: 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

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

Thanks for the nice documentation. To my knowledge celery is widely used for distributed task processing. This fits our requirement perfectly where we want to return immediate response to the user from our API server and run long running task in background. Celery also gives flexibility with the

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

John McDowall wrote on 05/31/2016 07:57:02 PM: > From: John McDowall > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: Ben Pfaff , "disc...@openvswitch.org" > , Justin Pettit , >

[openstack-dev] Kilo end of life

FYI, I've got some changes up to project-config and the releases repo to mark kilo as end of life [1]. Andreas has done the same for the manuals. The project-config changes remove the kilo periodic job definitions and usage from all repos, regardless of whether or not they are managed by the

[openstack-dev] [requirements][all] Cleaning up Global Requirements

Team, Please see the following reviews, If you see a package being dropped and you need it, please chime in ASAP: https://review.openstack.org/#/q/status:open+project:openstack/requirements+branch:master+topic:remove-crufts if your project needs it and your project does not follow requirements

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

I think it makes sense to merge the triplo heat templates without m-dat support, as including m-dat will require a bunch of dependent patches and slow everything down. The lack of the m-dat service won't cause any issues other than that the experimental share-migration APIs won't work. We

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

On 5/31/2016 7:38 AM, Sean Dague wrote: 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

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

Igor and Tim, +1 on your suggestion. Thanks, Cathy -Original Message- From: Duarte Cardoso, Igor [mailto:igor.duarte.card...@intel.com] Sent: Tuesday, May 31, 2016 8:48 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] support of NSH in

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

Looks like the work of removing the mandatory L3 requirement associated with decapsulated VxLAN-gpe packet also involves OVS kernel change, which is difficult. Furthermore, even this blocking issue is resolved and eventually OVS accepts the VLAN-gpe+NSH encapsulation, there is still another

Re: [openstack-dev] Fwd: keystone federation user story

On Wed, May 25, 2016 at 2:57 AM Jamie Lennox wrote: > On 25 May 2016 at 03:55, Alexander Makarov wrote: > >> Colleagues, >> >> here is an actual use case for shadow users assignments, let's discuss >> possible solutions: all suggestions are

Re: [openstack-dev] [ironic] Virtual midcycle date poll

On Thu, May 19, 2016 at 09:25:18AM -0400, Jim Rollenhagen wrote: > Hi Ironickers, > > We decided in our last meeting that the midcycle for Newton will again > be virtual. Now, we need to choose a date. Please indicate which options > work for you (more than one may be selected): > >

[openstack-dev] [release] Release countdown for week R-17, June 6-10

Focus - Leading into the second milestone, new feature development should be under way and specs should be approved or close to approved. First milestone tags are due this week. General Notes - We've had a few library release requests filed late in the week. Please keep in mind

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

On 06/01/2016 01:33 PM, Matt Riedemann wrote: > > Sounds like there was a bad check in nova which is fixed here: > > https://review.openstack.org/#/c/323467/ > > And a d-g change depends on that here: > > https://review.openstack.org/#/c/320925/ > > Is there anything more to do for this? I'm

[openstack-dev] [TripleO][diskimage-builder] Proposing Stephane Miller to dib-core

Hello everyone, I'd like to propose adding Stephane Miller (cinerama) to the diskimage-builder core team. She has been a huge help with our reviews for some time now and I think she would make a great addition to our core team. I know I have benefited a lot from her bash expertise in many of my

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

On 5/31/2016 8:36 AM, Daniel P. Berrange wrote: 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

Re: [openstack-dev] [Murano] Does Murano support version management?

Hi, Murano does have partial support for version management. Murano (deployment) engine can work with several versions of the same package. You can even have them in single environment. I order to store several such packages you must use Glare backend rather than old API backend and must use

[openstack-dev] [new][oslo] oslo.messaging 5.2.0 release (newton)

We are thrilled to announce the release of: oslo.messaging 5.2.0: Oslo Messaging API This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/oslo.messaging With package available at:

Re: [openstack-dev] [puppet] Discussion of PuppetOpenstack Project abbreviation

> On Jun 1, 2016, at 5:56 AM, Dmitry Tantsur wrote: > > On 06/01/2016 02:20 PM, Jason Guiditta wrote: >> On 01/06/16 18:49 +0800, Xingchao Yu wrote: >>> Hi, everyone: >>> >>> Do we need to give a abbreviation for PuppetOpenstack project? B/C >>> it's really a long

Re: [openstack-dev] [TripleO] [diskimage-builder] Howto refactor?

Hi! Created a first draft of a 'Big Picture' document including an overview and a technical breakdown [1]. I'm not sure if this is what you expect or if still something is missing? Maybe we can start with etherpad - and do the first some iterations there. Later on I'd like to see it moved to the

[openstack-dev] [trove] Today's Trove meeting is canceled

Nothing new has been added to the agenda. Today's meeting is canceled. If anything urgent comes up, use #openstack-trove. Thanks, -amrith > -Original Message- > From: Amrith Kumar > Sent: Wednesday, June 01, 2016 9:17 AM > To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [octavia] enabling new topologies

Hey Sergey-- Apologies for the delay in my response. I'm still wrapping my head around your option 2 suggestion and the implications it might have for the code base moving forward. I think, though, that I'm against your option 2 proposal and in favor of option 1 (which, yes, is more work

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

> On Jun 1, 2016, at 12:27 PM, Armando M. wrote: > > > > On 1 June 2016 at 02:28, Thierry Carrez wrote: > Armando M. wrote: > Having looked at the recent commit volume that has been going into the > *-aas repos, I am considering changing the release

[openstack-dev] [vitrage] Vitrage is now an official OpenStack project

Hi, Great news - Vitrage (OpenStack RCA service) was accepted into the big tent yesterday, in the TC IRC meeting[1]. Thanks to everyone who participated in this huge effort of creating a whole project from scratch in a little more than 6 months. Now, with the wind in our sails, we invite

Re: [openstack-dev] [octavia] is l7 rule using routed L3 connectivity

Hello Yong Sheng Gong! Apologies for the lateness of my reply (I've been intermittently available over the last month and am now just catching up on ML threads). Anyway, did you get your question answered elsewhere? It looks like you've discovered a bug in the behavior here-- when you created the

Re: [openstack-dev] [TripleO] [diskimage-builder] Howto refactor?

On Wed, Jun 1, 2016, at 01:06 AM, Ian Wienand wrote: > On 06/01/2016 02:10 PM, Andre Florath wrote: > > My long term goal is, to add some functionality to the DIB's block > > device layer, like to be able to use multiple partitions, logical > > volumes and mount points. > > Some thoughts... > >

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

I've been holding off, but I'll chime in now. I believe Higgins should be about abstracting away differences in the container systems where there are needless differences the user really could care less about. IE, "here, launch this container" can be done: * k8s pod create ... * docker run

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

On 1 June 2016 at 02:28, Thierry Carrez wrote: > Armando M. wrote: > >> 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

Re: [openstack-dev] [neutron][dvr] Wasting so many external network IPs in DVR mode?

On Wed, Jun 1, 2016 at 9:48 AM, zhi wrote: > hi, all > > I have some questions about north/south traffic in DVR mode. > > As we all know, packets will be sent to instance's default gateway (qr > interface) when an instance want to communicate to the external

Re: [openstack-dev] [networking-guide] First IRC meeting tomorrow

Folks, This is a kind reminder that we are having our IRC meeting tomorrow at 1600 UTC in #openstack-meeting Agenda: https://etherpad.openstack.org/p/docnetworkingteam-agenda Thanks, Edgar __ OpenStack Development Mailing

[openstack-dev] [neutron][dvr] Wasting so many external network IPs in DVR mode?

hi, all I have some questions about north/south traffic in DVR mode. As we all know, packets will be sent to instance's default gateway (qr interface) when an instance want to communicate to the external network. Next, these packets will be sent from rfp interface(qrouter interface) to

Re: [openstack-dev] [docs] [install-guide] Install guide from source

This work aims to be published to magnum's developer page: http://docs.openstack.org/developer/magnum/ Cheers, Spyros On 1 June 2016 at 17:30, Andreas Jaeger wrote: > On 06/01/2016 05:21 PM, Spyros Trigazis wrote: > >> Hi everyone, >> >> Is the idea of having an install-guide

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

Miles Gould wrote: On 31/05/16 21:03, Timofei Durakov wrote: 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. +1 to

Re: [openstack-dev] [OpenStack-docs] [docs] [install-guide] Install guide from source

You can't mix distribution packages and source on the same host without using at least virtual environments for the latter. On Wed, Jun 1, 2016 at 9:30 AM, Andreas Jaeger wrote: > On 06/01/2016 05:21 PM, Spyros Trigazis wrote: > >> Hi everyone, >> >> Is the idea of having an

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

Hi team, A blueprint was created for tracking this idea: https://blueprints.launchpad.net/magnum/+spec/manually-manage-bay-nodes . I won't approve the BP until there is a team decision on accepting/rejecting the idea. From the discussion in design summit, it looks everyone is OK with the idea

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

Witek, Thanks, I like the way you break it into two topics. I agree with you on the first one to make it similar to dimensions (global and per message). On the second one, I see your point about including the topic as part of the resource URI. I am ok with it if others don’t see any issues

[openstack-dev] [watcher] Newton mid-cycle meetup details

The Watcher Newton mid-cycle developer meetup will take place in Hillsboro, OR on July 19-21 2016 For more details see the wiki [1] [1] https://wiki.openstack.org/wiki/Watcher_newton_mid-cycle_meetup_agenda Regards Susanne

Re: [openstack-dev] [docs] [install-guide] Install guide from source

On 06/01/2016 05:21 PM, Spyros Trigazis wrote: Hi everyone, Is the idea of having an install-guide from source and possibly virtualenvs still under consideration? I'd like to share with you what we are currently doing along with the install-guide based on the cookiecutter template. I have

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Na/Srilatha, Great, I am working from three repos: https://github.com/doonhammer/networking-sfc https://github.com/doonhammer/networking-ovn https://github.com/doonhammer/ovs I had an original prototype working that used an API I created. Since then, based on feedback from everyone I have been

[openstack-dev] [docs] [install-guide] Install guide from source

Hi everyone, Is the idea of having an install-guide from source and possibly virtualenvs still under consideration? I'd like to share with you what we are currently doing along with the install-guide based on the cookiecutter template. I have created this change [1] in our project repo.

[openstack-dev] [nova] Newton midcycle meetup details posted in the wiki

I've updated the Newton midcycle meetup details in the wiki [1]. There is now info on where to go, including directions from PDX airport and a map of the Intel campus where we'll be meeting. There is also hotel information on the wiki. If you're coming from outside the US and have questions

Re: [openstack-dev] [magnum][lbaas] Operator-facing installation guide

Hi. I have added https://wiki.openstack.org/wiki/Neutron/LBaaS/HowToRun Regards, Spyros On 1 June 2016 at 16:39, Hongbin Lu wrote: > Hi lbaas team, > > > > I wonder if there is an operator-facing installation guide for > neutron-lbaas. I asked that because Magnum is

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

I don't love writing docs but I've spent more than my share of reading them :). I'm very willing to help out here as docs liason. Thanks, Jay Faulkner From: Loo, Ruby Sent: Tuesday, May 31, 2016 10:23:57 AM To: OpenStack Development

Re: [openstack-dev] [Fuel] [Plugins] Netconfig tasks changes

Hi, YAQL expressions support for task dependencies has been added to Nailgun [0]. So now it's possible to fix network configuration idempotency issue without introducing new 'netconfig' task [1]. There will be no problems with loops in task graph in such case (tested on multiroles, worked fine).

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

Sounds similar to https://review.openstack.org/#/c/224022/ (which is the ironic version of expose state machine transitions over the REST API); probably useful to read over the review commentary there and/or talk to the ironic folks about that before doing much here (to learn some of the

[openstack-dev] [magnum][lbaas] Operator-facing installation guide

Hi lbaas team, I wonder if there is an operator-facing installation guide for neutron-lbaas. I asked that because Magnum is working on an installation guide [1] and neutron-lbaas is a dependency of Magnum. We want to link to an official lbaas guide so that our users will have a completed

Re: [openstack-dev] [glance] [stable] Proposal to add Ian Cordasco to glance-stable-maint

On 5/25/2016 4:12 PM, Nikhil Komawar wrote: Hi all, I would like to propose adding Ian to glance-stable-maint team. The interest is coming from him and I've already asked for feedback from the current glance-stable-maint folks, which has been in Ian's favor. Also, as Ian mentions the current

Re: [openstack-dev] [Fuel] Correct wrong nomenclature in the Networks section of Fuel-ui

Hi, I'll try to explain it better. As reported in the Fuel documentation "Internal networks include Storage, Management, and Admin (PXE) Fuel networks. Internal network connects all OpenStack nodes within an OpenStack environment. All components of an OpenStack environment communicate with each

[openstack-dev] [new][designate] designate-tempest-plugin 0.1.0 release

We are thrilled to announce the release of: designate-tempest-plugin 0.1.0: OpenStack DNS As A Service (Designate) Functional Tests This is the first release of designate-tempest-plugin. With package available at: https://pypi.python.org/pypi/designate-tempest-plugin For more details,

Re: [openstack-dev] [kolla] Ansible 2.0.0 functional

I believe 2.1 was when Toshio introduced the new ziploader, which totally changed how the modules were loaded: https://github.com/ansible/ansible/pull/15246 That broke a few of the 2.x OpenStack modules, too. But that was mostly our fault as we didn't code some of them correctly to the proper

Re: [openstack-dev] [Fuel] Correct wrong nomenclature in the Networks section of Fuel-ui

As I just commented in the review, I think the wording was clearer as it was before. So would prefer if you do not use this as a model for further similar changes. Neil On Wed, Jun 1, 2016 at 2:06 PM Giuseppe Cossu wrote: > Hi folks, > I submitted a bug and

[openstack-dev] [trove] Reminder: Trove meeting this afternoon

A reminder to everyone that there's a Trove meeting scheduled for 2pm Eastern Time today. Currently there is nothing on the agenda. If there's nothing on the agenda by ~ 60m before the meeting, I propose that we cancel the meeting. Agenda is at

[openstack-dev] [Fuel] Correct wrong nomenclature in the Networks section of Fuel-ui

Hi folks, I submitted a bug and the related fix about a wrong nomenclatura in fuel-ui. The fix is merged but I think we need to improve other things such as the translations of the same content and the related parameters (e.g., replace "internal_cidr" with "admin_tenant_cidr") inside the fuel-ui

Re: [openstack-dev] [puppet] Discussion of PuppetOpenstack Project abbreviation

On 06/01/2016 02:20 PM, Jason Guiditta wrote: On 01/06/16 18:49 +0800, Xingchao Yu wrote: Hi, everyone: Do we need to give a abbreviation for PuppetOpenstack project? B/C it's really a long words when I introduce this project to people or writng article about it. How about

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

On 06/01/2016 03:50 PM, Andrew Laski wrote: > > > On Wed, Jun 1, 2016, at 05:51 AM, Miles Gould wrote: >> On 31/05/16 21:03, Timofei Durakov wrote: >>> there is blueprint[1] that was approved during Liberty and resubmitted >>> to Newton(with spec[2]). >>> The idea is to define state machines for

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

On Wed, Jun 1, 2016, at 06:06 AM, Timofei Durakov wrote: > From my sight, I concerned proposed transition from option #1 to > option #2. > because it would be quite big change. So I wonder, has any > component team > implemented such transition. Open questions: > * upgrades story potential

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

On Wed, Jun 1, 2016, at 05:51 AM, Miles Gould wrote: > On 31/05/16 21:03, Timofei Durakov wrote: > > 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] [puppet] Discussion of PuppetOpenstack Project abbreviation

On 01/06/16 18:49 +0800, Xingchao Yu wrote: Hi, everyone: Do we need to give a abbreviation for PuppetOpenstack project? B/C it's really a long words when I introduce this project to people or writng article about it. How about POM(PuppetOpenstack Modules) or

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

Hi, I "like" documentation, so if you won't find anyone that "loves" it, consider me a candidate :) - Vlad On Tue, May 31, 2016 at 8:23 PM, Loo, Ruby wrote: > Hi, > > We¹re looking for a documentation liaison [1]. If you love (Œlike¹ is also > acceptable) documentation,

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

Hi Jay, Posted here because you're probably sleeping now ;) On 2016-05-31 7:01 PM, Jay Faulkner wrote: 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,

Re: [openstack-dev] [monitoring-for-openstack] Project retiring

On 2016-06-01 13:26, Monty Taylor wrote: > On 06/01/2016 12:24 PM, Martin Magr wrote: >> Greetings, >> >> due to the import of project monitoring-for-openstack to project >> osops-tools-monitoring [1] the imported project will be retired. I've >> started with the process today [2] and expect to

Re: [openstack-dev] [monitoring-for-openstack] Project retiring

On 06/01/2016 12:24 PM, Martin Magr wrote: > Greetings, > > due to the import of project monitoring-for-openstack to project > osops-tools-monitoring [1] the imported project will be retired. I've > started with the process today [2] and expect to finish the retiring > within a week. > >

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

Hi, thanks Nikhil. My availability considering what was proposed: 2000 UTC - OK 1100 UTC - OK On Tue, May 31, 2016 at 11:13 PM, Nikhil Komawar wrote: > Hey, > > > Thanks for your interest. > > Sorry about the confusion. Please consider the same time for Thursday > June

[openstack-dev] [puppet] Discussion of PuppetOpenstack Project abbreviation

Hi, everyone: Do we need to give a abbreviation for PuppetOpenstack project? B/C it's really a long words when I introduce this project to people or writng article about it. How about POM(PuppetOpenstack Modules) or POP(PuppetOpenstack Project) ? I would like +1 for POM. Just

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

Thanks Shu for providing suggestions. I wanted the new name to be related to containers as Magnum is also synonym for containers. So I have few options here. 1. Casket 2. Canister 3. Cistern 4. Hutch All above options are free to be taken on pypi and Launchpad. Thoughts? Regards Madhuri

Re: [openstack-dev] [Fuel] Storing deployment configuration before or after a successful deployment

IMO: Because we do not have the versioning for all settings, the discard button shall reset to last deployed state(in case if last deployed state exists, otherwise the discard button should not be available). Now the availability of discard button calculates according to state of cluster, but

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

> -Original Message- > From: Andrew Laski [mailto:and...@lascii.com] > Sent: 31 May 2016 22:34 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] State machines in Nova > > > > On Tue, May 31, 2016, at 04:26 PM, Joshua Harlow wrote: > > Timofei Durakov

Re: [openstack-dev] [kolla] Ansible 2.0.0 functional

1. the ansible 2.1 make lots of change compare to the ansible 2.0 about how the plugin works. So in default, kolla do not work with ansible 2.1 2. the compatible fix is merged here[0]. So the kolla works on both ansible 2.1 and ansible 2.0 [0] https://review.openstack.org/321754 On Wed,

  1   2   >