Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Jeremy Stanley's message of 2016-11-29 21:52:35 +: > On 2016-11-29 13:40:56 -0800 (-0800), Clint Byrum wrote: > > Excerpts from Jeremy Stanley's message of 2016-11-29 21:10:35 +: > [...] > > > I also feel very strongly that those alone would be terrible reasons > > > to

Re: [openstack-dev] [magnum-ui][horizon] use json-schema-form on workflow

Thanks Rob. Pretty good! We have confirmed 'tabs' type is same look and feel as previous Workflow Service. > -Original Message- > From: Rob Cresswell [mailto:robert.cressw...@outlook.com] > Sent: Friday, November 25, 2016 5:39 PM > To: OpenStack Dev Mailer

[openstack-dev] [neutron] broken linuxbridge gate

Hi folks, A recent devstack set of changes [0,1] accidentally broke the linuxbridge job in that bridge_mappings are no longer applied correct. To add insult to injury, this got applied to both stable and master (with the stable fix landing first). See [2,3] for a difference. This is not the

Re: [openstack-dev] [neutron] broken linuxbridge gate

On 29 November 2016 at 15:46, Armando M. wrote: > Hi folks, > > A recent devstack set of changes [0,1] accidentally broke the linuxbridge > job in that bridge_mappings are no longer applied correct. To add insult to > injury, this got applied to both stable and master (with

[openstack-dev] [all][ptls][tc][goals] community goals for Pike

A few months ago, our community started to find and work on OpenStack-wide goals to "achieve visible common changes, push for basic levels of consistency and user experience, and efficiently improve certain areas where technical debt payments have become too high – across all OpenStack projects".

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 2016-11-29 20:19:13 + (+), gordon chung wrote: [...] > i don't recall why they were moved to be officially under the Telemetry > umbrella[3] but i remember they weren't allowed to do something if they > weren't part of an 'official' project. if i could remember what it was > this

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 29/11/16 01:24 PM, Doug Hellmann wrote: > If we start by assuming that contributors may end up getting more > value from seeming to be a part of the community than the community > will get from their participation, and that we have to guard against > that because it somehow diminishes us, it

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

There are a couple of reasons we want to become an official OpenStack project. From a project perspective, we want to be recognized that the project isn’t just a “public source” repo for Cisco’s drivers but is a community driven open source project for supporting Cisco hardware/software and we

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 2016-11-29 13:40:56 -0800 (-0800), Clint Byrum wrote: > Excerpts from Jeremy Stanley's message of 2016-11-29 21:10:35 +: [...] > > I also feel very strongly that those alone would be terrible reasons > > to consider becoming an official project team under the governance > > of the OpenStack

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Chris Friesen's message of 2016-11-29 11:55:30 -0600: > On 11/29/2016 10:55 AM, Doug Hellmann wrote: > > > I agree that clearly documenting who supports each driver, and how > > tightly integrated that team is with the core team will be important. > > That will be the case no matter

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 2016-11-29 21:00:06 + (+), Sam Betts (sambetts) wrote: [...] > Additionally, being “official” indicates a level of maturity which > benefits us as a project by improving the public perception of our > drivers, and also indicates to OpenStack users that OpenStack > itself is mature and

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Sam Betts (sambetts)'s message of 2016-11-29 21:00:06 +: > There are a couple of reasons we want to become an official OpenStack project. > > From a project perspective, we want to be recognized that the project isn’t > just a “public source” repo for Cisco’s drivers but is a

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 29/11/16 03:53 PM, Jeremy Stanley wrote: > Perhaps they wanted to publish documentation to the > docs.openstack.org site? That's traditionally only been allowed by > the Docs team for official project deliverables. that's probably it, i just couldn't find their docs. from our experience, we

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Jeremy Stanley's message of 2016-11-29 21:10:35 +: > On 2016-11-29 21:00:06 + (+), Sam Betts (sambetts) wrote: > [...] > > Additionally, being “official” indicates a level of maturity which > > benefits us as a project by improving the public perception of our > >

Re: [openstack-dev] [tripleo] [ironic] Need to update kernel parameters on local boot

The problem we have with that is that for changes to take effect we will need a reboot after it. This is suboptimal for production environments, where there are large amount of nodes and with an slow hardware. And also the reboot needs to be carefully synced, to only take place after all puppet

Re: [openstack-dev] Suspected SPAM - Re: Suspected SPAM - [vitrage] datasources terminology

Sounds good to me :) From: Afek, Ifat (Nokia - IL) [mailto:ifat.a...@nokia.com] Sent: Tuesday, November 29, 2016 11:23 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Suspected SPAM - Re: [openstack-dev] Suspected SPAM - [vitrage] datasources terminology Hi, A new

Re: [openstack-dev] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

It was real pleasure to work with you! Thank you for your guidance and comments, we will miss that :( Wish you all the best! On Tue, Nov 29, 2016 at 9:55 AM Vikram Choudhary < vikram.choudh...@huawei.com> wrote: > Hi Assaf, > > Wish you all the best for your future endeavor! > > Thanks > Vikram

[openstack-dev] [tricircle]Weekly meeting(Nov.30) cancelled for we can have a f2f meetup in bug-smash

Hello, team, There is bug-smash this week, and many of us will attend this event[1], so let's have a f2f meetup there, and the weekly meeting(Nov.30) will be cancelled accordingly. Best Regards Chaoyi Huang (joehuang) __

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Doug Hellmann wrote: > [...] > 5. Consider driver teams to be a completely different animal, defined >in drivers.yaml instead of projects.yaml (grey option) [6] > >This establishes drivers as second-order objects that are necessary >for the success of the main projects, and for which

[openstack-dev] [oslo][osprofiler] Sampling rate in OSProfiler

Hey guys, cc: harlowja, DinaBelova, boris-42 I saw a lot of great work in OSProfiler. I see that "Trace every N request configuration (not done yet)". [1] Both Zipkin [2] and OpenTracing [3] have this feature. OSProfiler aim to be a small library --> May this feature make any overhead? Do you

Re: [openstack-dev] Suspected SPAM - [vitrage] datasources terminology

Hi, A new suggestion: * event_type: the type of event/notification that comes from the datasource. For example: ‘compute.instance.delete.end’, ‘volume.detach.start’ * graph_action: used to tell the evaluator what to do with the entity - create, update or delete it. *

Re: [openstack-dev] [neutron]Do we need to rfe to implement active-active router?

Hi Thomas I have already filed a RFE bug.Please refer to bug #1645625 发自网易邮箱手机版 On 2016-11-18 01:27 , Thomas Morin Wrote: Hi, What would active-active exactly be in DVR mode ? -Thomas Le 16/11/2016 à 16:42, huangdenghui a écrit : hi Currently, neutron support DVR router and

Re: [openstack-dev] [aodh] about alarm update with --query

On Tue, Nov 29 2016, dong.wenj...@zte.com.cn wrote: Hi dongwenjuan, I'd suggest to open a bug against aodh on Launchpad. I've no idea if it's a bug or not, but at least it'll be logged and we'll be able to dig into that. :) > Hi all, > > I use aodh cli to create a event alarm with query

[openstack-dev] [vitrage] entity_type in make_pickleable

Several properties are added to entity in `DriverBase.make_pickleable`[1] but the existence check is only applied in `_add_entity_type`. I think it may not be necessary after we prepended vitrage namespace[2]. I could not think of a scenario to let user shadow the built-in `entity_type`. Is

Re: [openstack-dev] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

It’s sad to read this, I’m still digesting some of your articles of your blog. Thanks for all of those years of making OpenStack Quantum/Neutron better. Regards, Victor Morales On 11/28/16, 12:58 PM, "Assaf Muller" wrote: >Hi all, > >For the past few months I've been

[openstack-dev] [gnocchi] influxdb driver gate error

Have been working on my influxdb driver [1] and have managed to figure out the gate to get it to install the deps ect. Now I just get this cryptic error 2016-11-30 06:50:14.969302 | + pifpaf -e GNOCCHI_STORAGE run influxdb -- pifpaf -e GNOCCHI_INDEXER run mysql -- ./tools/pretty_tox.sh

[openstack-dev] "tempest.lib.common.ssh AuthenticationException: Authentication failed." error when run“tempest.api.compute.servers.test_create_server.ServersTestJSON.test_host_name_is_same_as_server_

Hello~ Anyone would concern: We are running the API tests on our cloud with the refstack-client tool. We have prepared the prerequisites required by the official guide. However, the results reported the “tempest.lib.common.ssh AuthenticationException: Authentication failed.” error and the test

Re: [openstack-dev] [ALU] [vitrage] common vs utils

Ready for review https://review.openstack.org/#/c/404517/ On Mon, Nov 28, 2016 at 5:50 PM Weyl, Alexey (Nokia - IL) < alexey.w...@nokia.com> wrote: > Sounds good to me J > > > > *From:* Yujun Zhang [mailto:zhangyujun+...@gmail.com] > *Sent:* Monday, November 28, 2016 10:43 AM > *To:* OpenStack

[openstack-dev] [tacker] Weekly meeting time slot - doodle poll

Given the natural changes in the mix of our active members and the recent daylight savings time change, I'm opening a doodle poll to find the best slot for our weekly meeting with max coverage. Please respond to the doodle poll below, http://doodle.com/poll/ee9p34kfhskd2ucc Note, this is the

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

On 2016-11-29 19:39:03 -0500 (-0500), Emilien Macchi wrote: [...] > - we expected all teams to respond to all goals, even if they have no > work to do. Should we continue that way? [...] While it struck me as a possible source of "busy work" at first, I now see that otherwise it can be quite

Re: [openstack-dev] Suspected SPAM - Re: Suspected SPAM - [vitrage] datasources terminology

LGTM On Tue, Nov 29, 2016 at 6:38 PM Weyl, Alexey (Nokia - IL) < alexey.w...@nokia.com> wrote: > Sounds good to me :) > > From: Afek, Ifat (Nokia - IL) [mailto:ifat.a...@nokia.com] > Sent: Tuesday, November 29, 2016 11:23 AM > To: OpenStack Development Mailing List (not for usage questions) >

Re: [openstack-dev] [Congress] Magnum_driver

Hi Ruben, I left a comment on one of the changes; after you take care of that I'll take a closer look at the code. Let me know if you have questions. Tim On Tue, Nov 29, 2016 at 4:06 AM Ruben wrote: > Hi Tim, > I've added the code of magnum_driver and its

[openstack-dev] [charms] Barbican + Identity Standalone - AWS

Another great day of Juju driven successes - deploying the barbican standalone stack for identity mgmt and secrets mgmt. For those that don't know, newton horizon brings support for identity only! This means you can (as I am) use the openstack-dashboard for mgmt of just users, projects, and

Re: [openstack-dev] [kolla] Vote to add zhubingbing to core team

+1 from me ☺ -Original Message- From: Michał Jastrzębski Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, November 29, 2016 at 9:21 AM To: "OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [kolla] Kolla-ansible is available

It’s not really about easy or hard. We don’t want to make the gating less optimal then it was pre-repo split. To achieve that objective, cross-repo gating is necessary to validate the images in the docker repo are correct wrt the orchestration system they were developed against originally

[openstack-dev] 答复: Re: [aodh] about alarm update with --query

Hi Julien Danjou, Thanks for your suggestion. Already report a bug: https://bugs.launchpad.net/ubuntu/+source/aodh/+bug/1645694 BR, dwj Julien Danjou 2016-11-29 18:12 收件人 dong.wenj...@zte.com.cn 抄送 openstack-dev@lists.openstack.org 主题 Re: [openstack-dev] [aodh] about

Re: [openstack-dev] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

Hi Assaf - It's a sad moment to miss you here. Hope you will find some more time in the future to come back. It's very nice to work with you. All the best. Don't stop your blog. / Trinath -Original Message- From: Assaf Muller [mailto:as...@redhat.com] Sent: Tuesday, November 29,

[openstack-dev] [all] cirros images to change default password

Hi, It was ‘cubswin:)’ before, but now that Cubs won [1] it’s ‘gocubsgo’ [2]. I hope it helps someone in the future. [1] http://www.chicagotribune.com/sports/baseball/cubs/ct-cubs-win-world-series-sullivan-spt-1103-20161102-story.html [2]

Re: [openstack-dev] [Congress] Magnum_driver

Hi Tim, I've added the code of magnum_driver and its unit test to review. It seems everything works. Ruben - Original Message - From: "Tim Hinrichs" To: "Ruben" Cc: openstack-dev@lists.openstack.org, "timothy l hinrichs"

Re: [openstack-dev] [ptl][release] ocata release management communication

I'm struggling to find good info on when the adjusted PTL nomination cycle starts. I've checked here: https://releases.openstack.org/ocata/schedule.html#pike-ptls-self-nomination but it looks like the 'elections' section was supposed to be added to the table and wasn't. I know from the updates

Re: [openstack-dev] [infra][neutron] Intel NFV CI voting permission in Neutron

Hi Ihar et al, Apologies for late reply. We were fighting couple of issues with the CI in last couple of days. The networking problem mentioned by Ihar was one of them. We're running fine as of yesterday [1]. To stay on the safe side let's wait a few days so CI proves stable before making it

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

I'll rank my preferred solutions, because I don't actually like any of them. Excerpts from Doug Hellmann's message of 2016-11-28 13:33:56 -0500: > 6. A resolution requiring projects that consume drivers to host all >proposed drivers. (red option) [7] > >This would require teams with

Re: [openstack-dev] [all] cirros images to change default password

Thank you for sharing this. This gave me a much needed smile this morning. :-) Jay On 11/29/2016 06:48 AM, Ihar Hrachyshka wrote: Hi, It was ‘cubswin:)’ before, but now that Cubs won [1] it’s ‘gocubsgo’ [2]. I hope it helps someone in the future. [1]

Re: [openstack-dev] [all] cirros images to change default password

On Tue, Nov 29, 2016 at 7:48 AM, Ihar Hrachyshka wrote: > Hi, > > It was ‘cubswin:)’ before, but now that Cubs won [1] it’s ‘gocubsgo’ [2]. > > I hope it helps someone in the future. > > [1] >

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 11/29/2016 08:03 AM, Doug Hellmann wrote: I'll rank my preferred solutions, because I don't actually like any of them. Just curious...what would you "actually like"? Chris __ OpenStack Development Mailing List (not

Re: [openstack-dev] [Neutron][networking-*] Refactor of segments db

Folks, note that this change basically changes ml2 driver API that was supposed to be stable (now drivers receive context objects instead of sqlalchemy sessions). I would like folks to chime in the review. I would also suggest to announce the change during the next team meetings. > On 22 Nov

Re: [openstack-dev] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

Assaf, We will miss you. Thanks for all your hard work for the community Good luck On Tue, Nov 29, 2016 at 7:19 AM, Trinath Somanchi wrote: > Hi Assaf - > > It's a sad moment to miss you here. Hope you will find some more time in > the future to come back. > > It's

Re: [openstack-dev] [gnocchi] influxdb driver gate error

Le 2016-11-30 08:06, Sam Morrison a écrit : 2016-11-30 06:50:14.969302 | + pifpaf -e GNOCCHI_STORAGE run influxdb -- pifpaf -e GNOCCHI_INDEXER run mysql -- ./tools/pretty_tox.sh 2016-11-30 06:50:17.399380 | ERROR: pifpaf: 'ascii' codec can't decode byte 0xc2 in position 165: ordinal not in

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 2016-11-28 13:33:56 -0500 (-0500), Doug Hellmann wrote: [...] > 1. A resolution reaffirming the "level playing field" requirement, >and acknowledging that it effectively precludes official status >for teams which only develop drivers for proprietary systems >(hard black) [2] [...] >

Re: [openstack-dev] [kolla] Vote to add zhubingbing to core team

+1 2016-11-29 13:21 GMT-03:00 Michał Jastrzębski : > Hello team! > > I'd like to propose to add zhubingbing to kolla (and kolla-ansible) > core teams. He did great job reviewing code during last couple of > months. > > Consider this proposal +1 from me, voting will be open for

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Chris Friesen's message of 2016-11-29 09:09:17 -0600: > On 11/29/2016 08:03 AM, Doug Hellmann wrote: > > I'll rank my preferred solutions, because I don't actually like any of > > them. > > Just curious...what would you "actually like"? > > Chris > My preference is to have teams

Re: [openstack-dev] [all] cirros images to change default password

On Tue, 29 Nov 2016, Ihar Hrachyshka wrote: > Hi, > > It was ‘cubswin:)’ before, but now that Cubs won [1] it’s ‘gocubsgo’ [2]. > > I hope it helps someone in the future. > > [1] > http://www.chicagotribune.com/sports/baseball/cubs/ct-cubs-win-world-series-sullivan-spt-1103-20161102-story.html >

Re: [openstack-dev] [keystone] Pike PTL

+1! Great job Steve Brad Topol, Ph.D. IBM Distinguished Engineer OpenStack (919) 543-0646 Internet: bto...@us.ibm.com Assistant: Kendra Witherspoon (919) 254-0680 From: Henry Nash To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [all] cirros images to change default password

:) My pleasure. While it’s fun and all, I see some code/docs relying on the old value. I suggest projects to check if they make an assumption, and if so, prepare for the change. Alternatively, we can try to convince cirros folks to revert. Ihar > On 29 Nov 2016, at 16:11, Jay S. Bryant

[openstack-dev] [telemetry][ceilometer] let's talk about volume=1 meters (again)

hi, i should preface the below is arguably not important if we have ability to count events and alarm against panko. ~~ we recently removed all our volume=1 meters in ceilometer and while i cleaning things up some residual stuff i started to wonder if we took out too much. (yes, i'm aware of

[openstack-dev] [kolla] Vote to add zhubingbing to core team

Hello team! I'd like to propose to add zhubingbing to kolla (and kolla-ansible) core teams. He did great job reviewing code during last couple of months. Consider this proposal +1 from me, voting will be open for 1 week (until Dec 6) or if we get unanimous agreement (or veto) before. Regards,

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 28/11/16 13:33 -0500, Doug Hellmann wrote: 5. Consider driver teams to be a completely different animal, defined in drivers.yaml instead of projects.yaml (grey option) [6] This establishes drivers as second-order objects that are necessary for the success of the main projects, and for

Re: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

+1 Regards, Vikram Hosakote IRC: vhosakot From: Mauricio Lima > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Wednesday,

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Flavio Percoco's message of 2016-11-29 17:19:15 +0100: > On 28/11/16 13:33 -0500, Doug Hellmann wrote: > >5. Consider driver teams to be a completely different animal, defined > > in drivers.yaml instead of projects.yaml (grey option) [6] > > > > This establishes drivers as

Re: [openstack-dev] [ptl][release] ocata release management communication

Rob C wrote: > I'm struggling to find good info on when the adjusted PTL nomination > cycle starts. > > I've checked here: > https://releases.openstack.org/ocata/schedule.html#pike-ptls-self-nomination > but it looks like the 'elections' section was supposed to be added to > the table and wasn't.

Re: [openstack-dev] [kolla] Vote to add zhubingbing to core team

+1 Regards, Vikram Hosakote IRC: vhosakot From: Michał Jastrzębski > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Tuesday, November 29, 2016

Re: [openstack-dev] [telemetry][ceilometer] let's talk about volume=1 meters (again)

On Tue, Nov 29 2016, gordon chung wrote: > i'm not talking about bringing back the 'instance', 'volume', etc... > meters because they were measuring nothing (or it measured everything as > some giant, unintelligible, blob meter). there are also stuff like > .created|deleted 'meters' which are

Re: [openstack-dev] [Neutron][neutron-lbaas][octavia] Not be able to ping loadbalancer ip

Hi Wanjing, 1. Yes, active/standby uses VRRP combined with our stickyness table sync between the amphora. However, since some clouds have had issues with multicast we have opted to use the unicast mode between the amphora instances. 2. This is a good question that we have been working on.

Re: [openstack-dev] [kolla] Vote to add zhubingbing to core team

+1 On 29/11/16 16:21, Michał Jastrzębski wrote: Hello team! I'd like to propose to add zhubingbing to kolla (and kolla-ansible) core teams. He did great job reviewing code during last couple of months. Consider this proposal +1 from me, voting will be open for 1 week (until Dec 6) or if we

[openstack-dev] Missing records in Glance "image_locations" table

Hi everyone, A while ago I reported some issues with Glance where image files went missing from the file system. Since then we implemented a monitoring script that regularly verifies the state of every active image in the Glance database, checking that: 1) it has a corresponding record in the

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 11/29/2016 10:55 AM, Doug Hellmann wrote: I agree that clearly documenting who supports each driver, and how tightly integrated that team is with the core team will be important. That will be the case no matter what solution we pick (even saying that drivers aren't official isn't going to

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Zane Bitter's message of 2016-11-29 12:36:03 -0500: > On 29/11/16 10:28, Doug Hellmann wrote: > > Excerpts from Chris Friesen's message of 2016-11-29 09:09:17 -0600: > >> On 11/29/2016 08:03 AM, Doug Hellmann wrote: > >>> I'll rank my preferred solutions, because I don't actually

Re: [openstack-dev] [kolla] Vote to add zhubingbing to core team

+1 nice work. On Wed, Nov 30, 2016 at 12:43 AM, Paul Bourke wrote: > +1 > > > On 29/11/16 16:21, Michał Jastrzębski wrote: > >> Hello team! >> >> I'd like to propose to add zhubingbing to kolla (and kolla-ansible) >> core teams. He did great job reviewing code during

[openstack-dev] [nova] Status of imagebackend refactor patches

I'm continuing to work through updating the imagebackend refactor patches. A bunch of them at the top of the queue already have +2 from jaypipes, who expressed an interest in getting some of these merged. I think the following could be ready to go (in order):

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 29/11/16 10:28, Doug Hellmann wrote: Excerpts from Chris Friesen's message of 2016-11-29 09:09:17 -0600: On 11/29/2016 08:03 AM, Doug Hellmann wrote: I'll rank my preferred solutions, because I don't actually like any of them. Just curious...what would you "actually like"? Chris My

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 2016-11-29 11:27 AM, Jeremy Stanley wrote: I think we also need to look harder at the reasons for driver-only developer teams seeking official status. If it's because they want to be part of the community and help collaborate with the rest of us, then as long as they can do that consistent

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

Excerpts from Anita Kuno's message of 2016-11-29 12:37:21 -0500: > On 2016-11-29 11:27 AM, Jeremy Stanley wrote: > > I think we also need to look harder at the reasons for driver-only > > developer teams seeking official status. If it's because they want > > to be part of the community and help

Re: [openstack-dev] [kolla] Kolla-ansible is available

I would expect nothing less, things that are worthwhile doing are usually not just (always) easy :) Jeffrey Zhang wrote: If we can implement loose coupling, there will be optimal. But it is hard to do this. On Tue, Nov 29, 2016 at 2:50 PM, Joshua Harlow