Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/03/2016 01:47 PM, Truman, Travis wrote: > Major has made an incredible number of contributions of code and reviews to > the OpenStack-Ansible community. Given his role as the primary author of the > openstack-ansible-security project, I can

Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

+1 On Fri, May 6, 2016 at 7:52 AM, Dave Wilde wrote: > I second that emotion +1 > > > > > From: Truman, Travis > > Reply: OpenStack Development Mailing List (not for usage questions) >

[openstack-dev] [kolla][kubernetes] How to join the core team of kolla-kubernetess

Hey folks, A lot of folks have signed up as developers for kolla-kubernetes in the spec, but one thing that hasn't been discussed in much detail is how to join the core reviewer team. To do that, simply provide one (or preferrably a bunch) of reviews on the kolla-kubernetes spec. This will

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

Sean, Thanks for taking this on :) I didn't know you had such an AR :) From: "Mooney, Sean K" > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

[openstack-dev] OpenStack Developer Mailing List Digest April 9-22

HTML rendered: http://www.openstack.org/blog/2016/05/openstack-developer-mailing-list-digest-20160422/ Success Bot Says * Clarkb: infra team redeployed Gerrit on a new larger server. Should serve reviews with fewer 500 errors. * danpb: woooh, finally booted a real VM using

[openstack-dev] [kolla] [bifrost] bifrost container.

Hi everyone. Following up on my AR from the kolla host repository session https://etherpad.openstack.org/p/kolla-newton-summit-kolla-kolla-host-repo I started working on creating a kolla bifrost container. Are some initial success it have hit a roadblock with the current install playbook

Re: [openstack-dev] [UX] OpenStack UX core nomination

+1 On Thu, May 5, 2016 at 2:11 PM, Kruithof Jr, Pieter wrote: > I would like to nominate Shamail Tahir as a core for the OpenStack UX project. > > Shamail has been central to developing a set of personas for the overall > community and providing his significant

Re: [openstack-dev] [kolla] xenial or trusty

On 6 May 2016 at 16:27, Jeffrey Zhang wrote: > > On Fri, May 6, 2016 at 9:09 PM, Jesse Pretorius > wrote: > >> FWIW OpenStack-Ansible is choosing to support deployment on both Ubuntu >> 14.04 LTS and Ubuntu 16.04 LTS for both the Newton and

Re: [openstack-dev] [TripleO][infra] HW upgrade for tripleo CI

On Fri, May 6, 2016 at 10:36 AM, Derek Higgins wrote: > Hi All, >the long awaited RAM and SSD's have arrived for the tripleo rack, > I'd like to schedule a time next week to do the install which will > involve and outage window. We could attempt to do it node by node but >

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 6 May 2016 at 15:25, Doug Hellmann wrote: > > Someone had a tool that looked at second-order dependencies, I think. I > can't find the reference in my notes, but maybe someone else has it > handy? > I don't have a specific tool handy, but I'm guessing that we could

Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

+1 from me. On May 6, 2016 9:12 AM, "Jimmy McCrory" wrote: > +1 > > On Fri, May 6, 2016 at 7:52 AM, Dave Wilde > wrote: > >> I second that emotion +1 >> >> >> >> >> From: Truman, Travis >>

Re: [openstack-dev] [kolla] xenial or trusty

On 5/6/16, 8:32 AM, "Emilien Macchi" wrote: >On Fri, May 6, 2016 at 9:09 AM, Jesse Pretorius > wrote: >> On 4 May 2016 at 19:21, Emilien Macchi wrote: >>> >>> On Wed, May 4, 2016 at 1:52 PM, Jeffrey Zhang

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Thank you! Cathy -Original Message- From: Miguel Angel Ajo Pelayo [mailto:majop...@redhat.com] Sent: Friday, May 06, 2016 12:42 AM To: OpenStack Development Mailing List (not for usage questions) Cc: Cathy Zhang Subject: Re: [openstack-dev] [neutron] work on Common Flow Classifier and

[openstack-dev] [Cinder] Austin Design Summit Recap

At the Design Summit in Austin, the Cinder team met over three days to go over a variety of topics. This is a general summary of the notes captured from each session. We were also able to record most sessions. Please see the openstack-cinder YouTube channel for all its minute and tedious glory:

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

On 2016-05-06 10:25:41 -0400 (-0400), Doug Hellmann wrote: > Excerpts from Tony Breeds's message of 2016-05-06 09:53:11 +1000: [...] > > I think some of these pro-active things will be key. A quick > > check shows we have nearly 30 items in g-r that don't seem to be > > used by anything. So

[openstack-dev] [TripleO][infra] HW upgrade for tripleo CI

Hi All, the long awaited RAM and SSD's have arrived for the tripleo rack, I'd like to schedule a time next week to do the install which will involve and outage window. We could attempt to do it node by node but the controller needs to come down at some stage anyways and doing other nodes groups

Re: [openstack-dev] [kolla] xenial or trusty

On Fri, May 6, 2016 at 9:09 AM, Jesse Pretorius wrote: > On 4 May 2016 at 19:21, Emilien Macchi wrote: >> >> On Wed, May 4, 2016 at 1:52 PM, Jeffrey Zhang >> wrote: >> > I'd like to lock the tag version in certain branch.

[openstack-dev] [Dragonflow] - IRC Meeting time

Hello All, During the summit we received feedback that many people from the US time zone would like to attend our IRC meetings. Our current time is 0900 UTC which is good for Europe/Israel/China where most of our contributors come from. If you are in the US and would like to participate in our

[openstack-dev] [nova][scheduler] Next Scheduler sub-team meeting

The next meeting for the Scheduler sub-team will be on Monday, May 9 at 1400 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160509T14) The agenda for the meeting is here; please add any items that you wish to discuss:

Re: [openstack-dev] [release][requirements][packaging][summit] input needed on summit discussion about global requirements

Excerpts from Tony Breeds's message of 2016-05-06 09:53:11 +1000: > On Thu, May 05, 2016 at 02:35:46PM -0400, Doug Hellmann wrote: > > > This has been a lively thread, and the summit session was similarly > > animated. I'm glad to see so much interest in managing our dependencies! > > > > As we

Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

I second that emotion +1 From: Truman, Travis Reply: OpenStack Development Mailing List (not for usage questions) Date: May 3, 2016 at

Re: [openstack-dev] [kolla] xenial or trusty

On Fri, May 6, 2016 at 9:09 PM, Jesse Pretorius wrote: > FWIW OpenStack-Ansible is choosing to support deployment on both Ubuntu > 14.04 LTS and Ubuntu 16.04 LTS for both the Newton and Ocata cycles, with > the current proposal to drop it in P. The intent is to provide

Re: [openstack-dev] What's Up, Doc? 6 May 2016

Hi Lana, Thanks for the summary, it's pretty good reading to catch up what happened recently. I have one question, I might missed a few entries, so please point me to the right document in this case. We had a docco session with the Telemetry team and we agreed on moving back the documentation

Re: [openstack-dev] [kolla] xenial or trusty

  -Original Message- From: Emilien Macchi Reply: OpenStack Development Mailing List (not for usage questions) Date: May 6, 2016 at 10:34:29 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [TripleO][infra] HW upgrade for tripleo CI

\o/ On 05/06/2016 09:36 AM, Derek Higgins wrote: > Hi All, >the long awaited RAM and SSD's have arrived for the tripleo rack, > I'd like to schedule a time next week to do the install which will > involve and outage window. We could attempt to do it node by node but > the controller needs to

Re: [openstack-dev] [TripleO][infra] HW upgrade for tripleo CI

On 06/05/16 09:57 -0500, Ben Nemec wrote: \o/ On 05/06/2016 09:36 AM, Derek Higgins wrote: Hi All, the long awaited RAM and SSD's have arrived for the tripleo rack, I'd like to schedule a time next week to do the install which will involve and outage window. We could attempt to do it node

Re: [openstack-dev] [requirements] Cruft entries found in global-requirements.txt

On 2016-05-06 13:38:43 -0500 (-0500), Brant Knudson wrote: > python-ldap and ldappool are in keystone's setup.cfg: > http://git.openstack.org/cgit/openstack/keystone/tree/setup.cfg#n24 Yep, that script will miss things like optional dependencies declared in setup.cfg or things installed directly

Re: [openstack-dev] [trove][sahara][infra][Octavia][manila] discussion of image building in Trove

On 05/05/16 19:16 +, Amrith Kumar wrote: Pete, please clarify … I was going to push the dib elements that we currently have and you were writing CentOS elements. Is that right? Seems like there are some crossed wires here. Pete is out today so chiming in on his behalf for now. At the

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

I was under the impression bifrost was 2 things, one, an installer/configurator of ironic in a stand alone mode, and two, a management tool for getting machines deployed without needing nova using ironic. The first use case seems like it should just be handled by enhancing kolla's ironic

[openstack-dev] [requirements] Cruft entries found in global-requirements.txt

Folks, Thanks to Jeremy for pointing to [1]. Please see list below with things that are considered cruft as they don't seem to appear in requirements/test-requirements in projects. Some of them are clearly needed by us :) like libvirt-python. Others are questionable. Example sockjs-tornado added

Re: [openstack-dev] [Cinder] Austin Design Summit Recap

Dear Sean, Great compilation, this will help for sure!! Thank you!! Best Regards, Sheel Rana On Fri, May 6, 2016 at 10:38 PM, Sean McGinnis wrote: > At the Design Summit in Austin, the Cinder team met over three days > to go over a variety of topics. This is a general

[openstack-dev] [Cinder] API features discoverability

I don't think we actually should be moving all the extensions to core, just the ones that are supported by all vendors and fully vetted. In other words, we should be moving extensions to core based on the original intent of extensions. That would mean that for backups we could continue to use

Re: [openstack-dev] [Group-based-policy] Service Chain work with LBaaS/FWaaS

Hi Yao, Responses inline. Thanks, ~Sumit. On Fri, May 6, 2016 at 12:32 AM, 姚威 wrote: > Hi all, > > I know that GBP can work with neutron(ml2) by resource_mapping, and > group/policy all work well. > Assume that I have installed and enabled LBaaS and FWaaS，can I use

Re: [openstack-dev] [horizon] Angular form framework

Yes, it is angular specific. If there is something that can work across all frameworks, then that would be good to know. From: Michael Krotscheck > Reply-To: OpenStack List

Re: [openstack-dev] [nova] Austin summit priorities session recap

Thanks for sending this out Matt. I added a inline comment here. On Thu, May 5, 2016 at 8:34 PM, Matt Riedemann wrote: > There are still a few design summit sessions from the summit that I'll > recap but I wanted to get the priorities session recap out as early as >

Re: [openstack-dev] [requirements] Cruft entries found in global-requirements.txt

On Fri, May 6, 2016 at 1:20 PM, Davanum Srinivas wrote: > Folks, > > Thanks to Jeremy for pointing to [1]. Please see list below with > things that are considered cruft as they don't seem to appear in > requirements/test-requirements in projects. Some of them are clearly >

Re: [openstack-dev] [requirements] Cruft entries found in global-requirements.txt

python-ldap is definitely used by keystone. I think expanding your search to include setup.cfg in addition to req.txt and test-req.txt would catch this case. ldap is optional for keystone and we use setuptool's optional dependencies expose it. i'll update the etherpad. On Fri, May 6, 2016 at 2:20

Re: [openstack-dev] [all] cross-project deployment tool meeting

I started https://etherpad.openstack.org/p/deployment-tools-wg Recent threads on openstack-dev shows that we need to work together (xenial things, etc). If you represent an OpenStack deployment tool (Chef, Ansible, etc), please add your name and your TZ in the etherpad. Also feel free to bring

[openstack-dev] [UX] OpenStack UX core nomination

OpenStack Community, I would like to nominate Lana Brindley as a core for the OpenStack UX project. Lana has been very active in supporting ongoing documentation efforts for cross-project user experience initiatives including the OpenStack personas and the UX Checklist for evaluating GUIs. In

Re: [openstack-dev] [kolla] Ironic broken on Ubuntu

On Thu, May 5, 2016 at 1:51 PM, Franck Barillaud wrote: > All the containers are started expect for 'ironic_inspector' and > 'nova_compute_ironic'. Looking at the > 'kolla/docker/ironic/ironic-inspector' shows no contruct for Ubuntu. Yes, it's a feature gap that is known:

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

Another option, should the install playbook be enhanced to support simply skipping the steps that wouldn't apply to building in the container? Seems to me, all the ironic stuff could just be done with the kolla ironic container, so no systemd stuff should be needed. Thanks, Kevin

Re: [openstack-dev] [all] cross-project deployment tool meeting

On 26 April 2016 at 17:54, Jan Klare wrote: > > i just wanted to follow up on this session ( > https://etherpad.openstack.org/p/newton-deployment-tools-discussion) were > we talked about a cross-project meeting for deployment tools. I would love > to see something like that

Re: [openstack-dev] [kolla] Kolla rpm distribution

On Fri, May 6, 2016 at 2:54 AM, wrote: > > Hi， > > One of our application would like to use Kolla as an upstream deployment > tools. As the application may run in the environment without internet > connections, we are trying to packaging Kolla as well as its requirements,

Re: [openstack-dev] [kolla] [bifrost] bifrost container.

From: Steven Dake (stdake) [mailto:std...@cisco.com] Sent: Friday, May 6, 2016 6:56 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla] [bifrost] bifrost container. Sean, Thanks for taking this on :) I

[openstack-dev] [Neutron] Diagnostics & troubleshooting design summit summary and next steps

It is my personal experience that unless I do my homework, design summit discussions largely go over my head. I'd guess that most people don't have time to research the topic of every design session they intend to go to, so for the session I lead I decided to do the unthinkable and present the

Re: [openstack-dev] [requirements] Cruft entries found in global-requirements.txt

Thanks Jeremy, Since the following folks volunteered to help with requirements: Dirk Mueller (SUSE) Haïkel Guémar (RDO/CentOS) Igor Yozhikov (MOS) Alan Pevec (RDO) Tony Breeds (Rackspace) Ghe Rivero (HPE) So Dirk, Haïkel, Igor, Alan, Tony, Ghe, Can you please do more research and file reviews

Re: [openstack-dev] [requirements] Cruft entries found in global-requirements.txt

On Fri, May 06, 2016 at 04:40:28PM -0400, Davanum Srinivas wrote: > Thanks Jeremy, > > Since the following folks volunteered to help with requirements: > Dirk Mueller (SUSE) > Haïkel Guémar (RDO/CentOS) > Igor Yozhikov (MOS) > Alan Pevec (RDO) > Tony Breeds (Rackspace) > Ghe Rivero (HPE) > > So

[openstack-dev] [puppet] roadmap proposal for puppet-ceph

Hi, Here's a roadmap proposal for puppet-ceph: 1) Release 1.0.0 1.0.0 will be the first release, we'll also create stable/hammer since it was the release that was tested in our CI. https://review.openstack.org/#/c/313687/ https://review.openstack.org/313677 (for release notes) 2) Support and

Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

Hi Alexey, Thanks for the overview of how you see a Congress-Vitrage integration being valuable. I'd imagine that the right first step in this integration would be creating a new datasource driver within Congress to pull data from Vitrage. It doesn't need to pull all the data in your list to

Re: [openstack-dev] [nova] Austin summit priorities session recap

On 5/6/2016 1:37 PM, Nikhil Komawar wrote: Thanks for sending this out Matt. I added a inline comment here. On Thu, May 5, 2016 at 8:34 PM, Matt Riedemann > wrote: There are still a few design summit sessions from the summit

[openstack-dev] [Dragonflow] - No IRC Meeting (5/9)

Hello Everyone, We will not have an IRC meeting in the upcoming Monday (5/9), we will continue doing IRC meeting in our regular time the week after. Thanks Gal. __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [requirements] Cruft entries found in global-requirements.txt

Started on removing some entries, I guess I have big cleanup to do RDO side. H. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [requirements] Cruft entries found in global-requirements.txt

On 2016-05-06 17:18:52 -0400 (-0400), Matthew Treinish wrote: > On Fri, May 06, 2016 at 04:40:28PM -0400, Davanum Srinivas wrote: [...] > > Example feedparser is in a few projects, but not used in those > > projects, so we can file reviews to clean up entries in specific > > projects (except

Re: [openstack-dev] [nova] api-ref docs cleanup review sprint 5/9 and 5/11

On 05/03/2016 04:12 PM, Matt Riedemann wrote: > We discussed at the summit a need for a review sprint on the api-ref > docs cleanup effort that's going on. See Sean's email on that from a > few weeks ago [1]. > > So we plan to do a review sprint next Monday 5/9 and Wednesday 5/11. > > The

[openstack-dev] [Group-based-policy] Service Chain work with LBaaS/FWaaS

Hi all, I know that GBP can work with neutron(ml2) by resource_mapping, and group/policy all work well. Assume that I have installed and enabled LBaaS and FWaaS，can I use service chain of gbp by `chain_mapping` or other plugins ? Another question. I use GBP and Cisco APIC as native driver,

Re: [openstack-dev] [neutron][FWaaS] __init__ arguments issue status

Hi All: In digging thru this, yes with the neutron change, it changed the MRO as below and thus the issue. (, , , , , , <—— the issue is at this point where we have a mismatch with args , , ) Nate, Margaret – thanks for digging thru this – lets get together during the day to discuss

Re: [openstack-dev] [tricircle] About the dynamic pod binding

Yipei, Probably you may be interested in the following section in Blueprint [1]. 7.1 AZ and Pod Binding ... 7.x [1] https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g/edit#heading=h.x14kdooqhai1 Cheers, S On Fri, May 6, 2016 at 3:58 PM, Shinobu Kinjo

Re: [openstack-dev] [tricircle] About the dynamic pod binding

Yipei, According to Chaoyi, you have a bunch of experiences regarding to the OpenStack, networking which is awesome. I look forward to hearing from you soon. Cheers, Shinobu On Fri, May 6, 2016 at 12:05 PM, Yipei Niu wrote: > Got it with thanks. > > Best regards, > Yipei >

[openstack-dev] [kolla] Kolla rpm distribution

Hi， One of our application would like to use Kolla as an upstream deployment tools. As the application may run in the environment without internet connections, we are trying to packaging Kolla as well as its requirements, such as jinja2, into rpm packages and deliver them along with the

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Sounds good, I started by opening a tiny RFE, that may help in the organization of flows inside OVS agent, for inter operability of features (SFC, TaaS, ovs fw, and even port trunking with just openflow). [1] [2] [1] https://bugs.launchpad.net/neutron/+bug/1577791 [2]

[openstack-dev] What's Up, Doc? 6 May 2016

Hi everyone, I hope you all had a safe journey home from Summit, and are now fully recovered from all the excitement (and jetlag)! I'm really pleased with the amount of progress we made this time around. We have a definitive set of goals for Newton, and I'm confident that they're all moving us

[openstack-dev] [Neutron] - Design summit session on the future of Neutron architecture

Hi all, in Austin we had a session to discuss the future of Neutron architecture. You can find the etherpad here [1]. The first part was about agents. In the last releases we have been factoring common code out and allowing pluggability: in Liberty L2 agent extensions were introduced and in

Re: [openstack-dev] [tricircle] [blueprint] Definition of strategies

Good suggestion. Agree that using "when" is not so accurate. Best Regards Chaoyi Huang ( Joe Huang ) -Original Message- From: Shinobu Kinjo [mailto:shinobu...@gmail.com] Sent: Friday, May 06, 2016 4:37 PM To: OpenStack Development Mailing List (not for usage questions) Subject:

[openstack-dev] [nova] notification subteam meeting is cancelled next week

Hi, As we agreed on Tuesday on the subteam meeting[1] the next week meeting is skipped due to lack of chairman. Please use the normal channels to sync during the week. Next meeting will be held on 17th of May 17:00 UTC on #openstack-meeting-4 [2] Cheers, Gibi [1]

[openstack-dev] [tricircle] [blueprint] Definition of strategies

Hi Chaoyi, In the Tricircle's blueprint, there is a section: 7.3 Resource Create Request Dispatch In this section, strategy for each resource is described. It would be better to elaborate on *WHEN* more: *before* or *during* or *after* e.g., security group's strategy is defined as follows:

[openstack-dev] [Cinder][Ceph][Kingbird][Tricircle][Smaug]Build a multisite disaster recovery "stack"

Hi Folks, I was referred to this talk https://www.youtube.com/watch?v=VWFYC6W71tY by a colleague, and really think several projects should collaborate on this subject. Two projects that are missed from the talk but would be helpful are Smaug[1] and Tricircle[2]. Smaug provides data protection

Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

+1 Ship it. Andy On 6 May 2016 at 07:42, Jesse Pretorius wrote: > On 3 May 2016 at 23:59, Jim Rollenhagen wrote: > >> >> Sounds like a major win for the team! > > > Haha! Quite! > > +1 for me on the proposal. I've spoken to Major and

Re: [openstack-dev] [kolla] xenial or trusty

On 4 May 2016 at 19:21, Emilien Macchi wrote: > On Wed, May 4, 2016 at 1:52 PM, Jeffrey Zhang > wrote: > > I'd like to lock the tag version in certain branch. One branch only > support > > one > > distro release. > > > > For example, the mitaka

Re: [openstack-dev] [TripleO] Austin summit - session recap/summary

On Tue, May 03, 2016 at 05:34:55PM +0100, Steven Hardy wrote: > Hi all, > > Some folks have requested a summary of our summit sessions, as has been > provided for some other projects. > > I'll probably go into more detail on some of these topics either via > subsequent more focussed threads

Re: [openstack-dev] [kolla] better solution for the non-ini format configure file

On 5/5/16, 4:52 AM, "Paul Bourke" wrote: >TL;DR keep globals.yml to a minimum, customise configs via >host_vars/group_vars > >It seems right now the "best" approach may be to tokenise variables as >required. This is the approach we currently use in Oracle. There are two

Re: [openstack-dev] [openstack-ansible] Nominate Major Hayden for core in openstack-ansible-security

On 3 May 2016 at 23:59, Jim Rollenhagen wrote: > > Sounds like a major win for the team! Haha! Quite! +1 for me on the proposal. I've spoken to Major and confirmed that he has the support from his employer to commit the time necessary on a consistent basis. -- Jesse

Re: [openstack-dev] [neutron] OSC transition

"Na Zhu" wrote on 05/04/2016 09:54:39 PM: > From: "Na Zhu" > To: "OpenStack Development Mailing List \(not for usage questions\)" > > Date: 05/04/2016 09:59 PM > Subject: Re: [openstack-dev] [neutron] OSC transition > > Hi

Re: [openstack-dev] [Keystone][Nova] Any Code Examples of Other Services Using Keystone Policy?

On 05/05/2016 06:03 PM, Dan Smith wrote: >> I'm currently working on the spec for Project ID Validation in Nova >> using Keystone. The outcome of the Design Summit Session was that the >> Nova service user would use the Keystone policy to establish whether the >> requester had access to the

[openstack-dev] [neutron][osc] Austin Design summit summary on the future of Neutron client

n Austin we had a session on the future of neutron client and discussed the CLI transition to OpenStack Client (OSC). The session etherpad is found at [1]. * We checked the progress of OSC transition and it is good. Support of 11 resources which are targets of the initial effort. In Newton

[openstack-dev] [nova] Austin summit feature classification session recap

On Thursday morning John Garbutt led a session on feature classification in Nova. The full etherpad is here [1]. We've had a concept of this in the Nova devref for awhile [2]. The goals of the session were to agree on understanding what this was trying to fix and figure out the plan for

Re: [openstack-dev] [OpenStack-docs] What's Up, Doc? 6 May 2016

One significant advantage of central documentation involves providing content in a single location with consistent structure or format that best serves the particular audience. Moving most or all documentation into project trees essentially eliminates this advantage, leaving our audiences with an

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

So then let's all get onboard https://review.openstack.org/#/c/260246/? I've yet to see what all these things called 'process-than-ack' not seemingly fit into that API in that review. IMHO most of what people are trying to fit into oslo.messaging here isn't really messages but are jobs to be

Re: [openstack-dev] [oslo][mistral] Saga of process than ack and where can we go from here...

Dmitry Tantsur wrote: On 05/03/2016 11:24 PM, Joshua Harlow wrote: Howdy folks, So I meet up with *some* of the mistral folks during friday last week at the summit and I was wondering if we as a group can find a path to help that project move forward in their desire to have some kind of