[openstack-dev] [vote][kolla] Splitting out Ansible into a separate deliverable

Core Reviewers: The facts: We have roughly 250 bugs in rc2. Of those, I suspect over half can just be closed out as dupes, fixed, wontfix, or the like. The core reviewer team has had various discussions around splitting the repository at various times but has not come to a concrete conclusion

Re: [openstack-dev] [kolla][ptl] Self non-nomination for Kolla PTL for Ocata cycle

ed, Sep 14, 2016 at 10:19 AM, Vikram Hosakote (vhosakot) <vhosa...@cisco.com> wrote: > Thanks a lot Steve for being a great PTL, leader and a mentor! > > Regards, > Vikram Hosakote > IRC: vhosakot > > From: "Steven Dake (stdake)" <

[openstack-dev] [kolla] Removal of folks from kolla-drivers

Forgot kolla tag. See message inside. From: Steven Dake Date: Tuesday, September 13, 2016 at 8:34 PM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Removal of folks from kolla-drivers Hey folks, I removed

[openstack-dev] Removal of folks from kolla-drivers

Hey folks, I removed several folks which appeared inactive for the Newton cycle from the kolla-drivers team on launchpad. As a reminder, the reason we add people to the kolla-drivers team is to do bug triage, move blueprint states around, and distribute the process of handling the release.

Re: [openstack-dev] [kolla] warning about PBR issue for kolla operators

l for a developer - did I miss a `pip install -e .` somewhere? -Clay 1. http://docs.openstack.org/developer/kolla/quickstart.html#installing-kolla-and-dependencies-for-development On Tue, Sep 13, 2016 at 4:33 PM, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrot

[openstack-dev] [kolla] warning about PBR issue for kolla operators

Hey folks, The quickstart guide was modified as a result of a lot of painful debugging over the last cycle approximately a month ago. The only solution available to us was to split the workflow into an operator workflow (working on stable branches) and a developer workflow (working on

[openstack-dev] [kolla][ptl] Self non-nomination for Kolla PTL for Ocata cycle

To the OpenStack Community, Consider this email my self non-nomination for PTL of Kolla for the coming Ocata release. I let the team know in our IRC team meeting several months ago I was passing the on baton at the conclusion of Newton, but I thought the broader OpenStack community would

Re: [openstack-dev] [kolla] Problem regarding named volume data location

I believe what Pual was indicating was On 9/2/16, 12:59 PM, "Christian Berendt" wrote: > On 02 Sep 2016, at 19:04, Jeffrey Zhang wrote: > > I think the right solution should warn the end-user: you need configure a large

[openstack-dev] [kolla] Please add kolla-kubernetes to your watched prjoects

Kollagues, The reviews on kolla-kubernetes are going slowly. I suspect the reason is folks don’t have kolla-kubernetes enabled in their watched projects list. If you need instruction on how to do that, please contact me on IRC. We need to work as a team to get the kolla-kubernetes backed-up

[openstack-dev] [vote][kolla] Core Nomination for Christian Berendt (berendt on irc)

Kolla core reviewer team, It is my pleasure to nominate Christian Berendt for the Kolla core team. Christian’s output over the last cycle has been fantastic – cracking the top 10 reviewer list for the full cycle. His 30 day stats [1] place him in solid 7th position, and considering the size

Re: [openstack-dev] [poll][kolla] Name of baremetal role/group

Sean, I’d recommend deploy-hosts (I assume this is the bootstrap renamed?) I’d also add a duplicate API of “deploy” and mark deploy as deprecated and follow the standard deprecation policies. I’d recommend making the new OpenStack specific deploy command deploy-openstack Regards -steve

Re: [openstack-dev] [kolla] Problem regarding named volume data location

On 9/2/16, 8:48 AM, "Paul Bourke" wrote: >Hi Kolla, > >We have been experiencing a long running issue with Kolla that I have >brought up briefly a few times, but not made too much noise about. > >I'm taking the time to write about it in the hopes that a) as a

[openstack-dev] [kolla] Barcelona Summit Friday Scheduling

Hey folks, Summit space is a bit more constrained compared to Austin and there are more teams to accommodate. Also there are no full day contributor meetups. As a result, unlike past summits Koalleans have participated in, Friday is being scheduled by the foundation for workroom sessions and

Re: [openstack-dev] [kolla] Requirement for bug when reno is present

From: Dave Walker > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Tuesday, August 30, 2016 at 4:24 AM To: "OpenStack Development Mailing List

[openstack-dev] [kolla] important instructions or Newton Milestone #3 Release today 8/31/2015 @ ~23:30 UTC

Hey folks, Milestone 3 will be submitted for tagging to the release team today around my end of work day. All milestone 3 blueprints and bugs will be moved to rc1 in the case they don't make the August 31st(today) deadline. We require fernet in rc1, so if there is anything that can be done to

[openstack-dev] [kolla] Deadline Aug 31 for Newton Milestone #3

Hey folks, The deadline for milestone #3 is August 31st (this is when we are tagging milestone #3). We then have until September 15th to stabilize the release and tag rc1. The release team branches occata at rc1, so if a feature doesn’t make rc1, its not making newton. After rc1, any

Re: [openstack-dev] [kolla] Requirement for bug when reno is present

The bug id and blueprint id are for automatic tracking via Launchpad. If they are omitted, managing the release becomes especially difficult. Unfortunately launchpad doesn't know about reno because then I'd agree, that would be an optimal way too go. Regards -steve On 8/30/16, 3:42 AM,

[openstack-dev] [kolla][osic] Ubuntu scale testing completed - now need CentOS deployed

Britt, Paul, and Michal, We are in need of centos deployed on the osic cluster (but not the deployment node). I'm not sure if we have time to get through all of the scenarios we have but I'd like to have data on centos as well. When you wake up, if you could sort out getting centos deployed

Re: [openstack-dev] [kolla][oisc] scenario #8 running - need help deploying centos next

Scenario #8 was running about 12 hours (mitaka rally and tempest testing) and was only half way done. Inspection of the control machines showed out of disk space errors on the control nodes (which only have a 50gb total partition for where /var/lib/docker was stored). Elasticsearch produces

[openstack-dev] [kolla][ironic][bifrost][osic] future of bifrost & Ironic for Kolla

Hey Stackers & Sean :), I just wanted to provide a quick update on where we think Kolla will be when ironic and bare metal config are fully fleshed out (landing in Newton). 3 controller, 20 storage, 100 compute with ceph+ovs+cinder+enable_central_logging on OSIC 130 node cluster Currently

[openstack-dev] [kolla] NOTICE: Deadline of 31st for milestone #3 - PLEASE UPDATE BLUEPRINT STATUS

Please take heed of the subject line. It would be immensely helpful if people working on the 35 blueprints would get them into he correct state (good progress or NEEDS REVIEW) so we can best select which features land in Newton. Ping any of the cores on #openstack-kolla if you don’t have

Re: [openstack-dev] [kolla][vote] Core nomination for Dave Walker (Daviey on irc)

This vote has passed unanimously prior to August 30th, therefore, closing voting early. Welcome to the core reviewer team Dave! If you have any questions, feel free to ask any core reviewer or myself. I have made the necessary changes in gerrit. Regards -steve From: Steven Dake

Re: [openstack-dev] [kolla][oisc] scenario #5 running

Scenario #6 is running – should finish in 4-6 hours. Regards -steve From: Steven Dake > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date:

[openstack-dev] [kolla][oisc] scenario #5 running

Hey folks, I didn't undo any of what Dave did to the cluster. I wrote a simple shell script to run time on all of the operations. We will be doing the same thing for liberty and mitaka. I expect the test of all operations will take about 40 minutes to 2 hours. Full instructions are on the

[openstack-dev] [kolla] OSIC scale testing

Hey folks, We have nearly automated all of the OSIC testing and there are instructions to follow in NEXTSTEPS. They take about 1 hour to execute (to setup a test0 and then all done. We have the cluster until the 30th. I need folks that have access to help out as much as possible between now

[openstack-dev] [kolla][vote] Core nomination for Dave Walker (Daviey on irc)

Kolla core reviewers, I am nominating Dave Walker for the Kolla core reviewer team. His 30 day review stats [1] place him in the middle of the pack for reviewers and his 60 day stats[2] are about equivalent. Dave participates heavily in IRC and has done some good technical work including the

Re: [openstack-dev] [kolla] Kolla configuration files owner and permission

On 8/23/16, 7:05 AM, "Gerard Braad" wrote: >On Tue, Aug 23, 2016 at 9:56 PM, lương hữu tuấn wrote: >> I also prefer a dedicated user ("kolla" seems the best choice) as same > On >> Tue, Aug 23, 2016 at 3:51 PM, Paul Bourke

Re: [openstack-dev] [kolla] Kolla configuration files owner and permission

On 8/23/16, 1:04 AM, "duon...@vn.fujitsu.com" wrote: >Hi S.Dake, > >>> Hello Kollish, >>> >>> I am working on bp ansible-specific-task-become so I need community opinion >>> about Kolla configuration files owner and permissions. >>> >>> For files in

Re: [openstack-dev] [kolla] Kolla configuration files owner and permission

On 8/22/16, 7:24 PM, "duon...@vn.fujitsu.com" wrote: >Hello Kollish, > >I am working on bp ansible-specific-task-become so I need community opinion >about Kolla configuration files owner and permissions. > >For files in "/var/lib/kolla", it's quite clear that the

Re: [openstack-dev] [vote][kolla] Core nomination proposal for Eduardo Gonzalez Gutierrez (egonzales90 on irc)

Eduardo, Their was a unanimous response in votes with no veto on this core reviewer nomination. As a result, voting is closed early. Welcome to the Kolla core review team! Looking for further good work from you! I have added you to the kolla-core team in gerrit. You should have access to

Re: [openstack-dev] [vote][kolla] Core nomination proposal for Eduardo Gonzalez Gutierrez (egonzales90 on irc)

][kolla] Core nomination proposal for >Eduardo Gonzalez Gutierrez (egonzales90 on irc) > >+1 > >-Ryan > >- Original Message - >From: "Steven Dake (stdake)" <std...@cisco.com> >To: "OpenStack Development Mailing List (not for usage questions)" &g

[openstack-dev] [vote][kolla] Core nomination proposal for Eduardo Gonzalez Gutierrez (egonzales90 on irc)

Kolla Core Review Team: I am nominating Eduardo for the core reviewer team. His reviews are fantastic, as I'm sure most of you have seen after looking over the review queue. His 30 day stats place him at #3 by review count [1] and 60 day stats [2] at #4 by review count. He is also first to

[openstack-dev] [kuryr][kolla] keystone v3 support status and plans?

Hey kuryrians, Kolla has a kuryr review in our queue and its looking really solid from Hui Kang. The last key problem blocking the merge (and support of Kuryr in Kolla) is that Kolla only supports keystone v3 (and later when that comes from upstream). As a result we are unable to merge kuryr

[openstack-dev] [kolla] FW: [all][ptl][tc] extra ATCs for newton

Koalligans, I can't think of anyone off the top of my head that hasn't submitted a patch for Newton that would qualify for an ATC pass under the bylaws [1] and TC Charter [2], but would like to open up nominations from core reviewers since I am not omnipotent. The only candidates that even come

Re: [openstack-dev] [kolla] Question about kolla git tag

Confirming Chao's statement. We support this model all the time on the #openstack-kollal. Thanks Chao. Regards -steve From: 韩潮 > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

[openstack-dev] [kolla][ironic][odm][ACTION NEEDED] Kolla's BiFrost and kolla-host work

Sean has done a fantastic job on the BiFrost work and kolla-host work. What is needed is the last step - which is a final thorough technical review from the core review team so we can get it merged by end of week. If your struggling to find the work in the review queue, use this link:

Re: [openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project

Well don't let me stop ya :) On 8/9/16, 7:21 AM, "Ian Cordasco" <sigmaviru...@gmail.com> wrote: > > >-Original Message- >From: Steven Dake (stdake) <std...@cisco.com> >Reply: OpenStack Development Mailing List (not for usage questions) ><opens

Re: [openstack-dev] [glare][kolla][odm] timing of release of glare and request for technical interview on IRC wherever the glare team wants to have it

.log.html#t2016-08-08T16:01:50 Thanks again Mike. Regards, -steve On 8/8/16, 8:01 AM, "Jay Pipes" <jaypi...@gmail.com> wrote: >On 08/08/2016 07:48 AM, Steven Dake (stdake) wrote: >> Cool thanks for the response. Appreciate it. I think the big take away >> is a

Re: [openstack-dev] [glare][kolla] timing of release of glare and request for technical interview on IRC wherever the glare team wants to have it

And for sure, I'll be glad to answer all your questions, 1600 UTC today works for me. So, let's meet at this time in your channel. Best, Mike On Sat, Aug 6, 2016 at 2:21 PM, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote: Hey folks, I guess the split of gla

[openstack-dev] [osic][kolla] Start of OSIC scale testing documentation [WIP]

Hey Koalaians, See review: https://review.openstack.org/352101 What I'd like to see happen is everyone working on scale testing commit their work by pulling down that review, modifying it, and submitting it to gerrit. Lets not mege it until the OSIC cluster is no longer in our hands. If you

Re: [openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project

o][Tacker] Glare as a new Project However, interested parties could start a project like the ec2 project that is independently released and provides that compatibility using glare On Aug 6, 2016 5:18 AM, "Steven Dake (stdake)" <std...@cisco.com<mailto:std...@cisco.com>>

Re: [openstack-dev] [kolla] I need help on multisite deploy

Lu Yao, Please drop by #openstack-kolla and our community can help you get rolling. Although now isn't a particularly good time (4:30 AM PST) - I'm awake and can get you up and running. My nick is sdake. Regards, -steve From: "lu.yao...@zte.com.cn"

[openstack-dev] [glare][kolla] timing of release of glare and request for technical interview on IRC wherever the glare team wants to have it

Hey folks, I guess the split of glare and glance have been in the works for awhile. It is challenging for operational deployment managers (ODMs) such as Kolla to keep up with the internal goings-on of every big tent project (or projects that shave off from big-tent projects). Just to be

Re: [openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project

Kevin, Agree it would be a very useful feature, however, easier said then done. Part of Docker's approach is to "move fast";they schedule releases every 2 months. I'm sure the glare team is quite competent, however, keeping API parity on such a fast moving project such as the docker registry

Re: [openstack-dev] [kolla][osic][bifrost] OSIC cluster status

Hey folks, Thanks for the video, those are great - if not a little hard for the casual observer to follow. That said, benchmark results of scale testing can be a dangerous game to play, so lets not play games about it. I'd like to see a full characterization of the hardware gear and topology

Re: [openstack-dev] [docker] [magnum] Magnum account on Docker Hub

ticket to acquire the username openstackmagnum. I included Hongbin's contact information explaining that he's the project's PTL. Thanks Steve, Spyros On 2 August 2016 at 13:29, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote: Ton, I may or may not have set it up

Re: [openstack-dev] [kolla] Needing volunteers for Geography Coordinators for making use of OSIC cluster

Typo is subject tag - please see inside :) From: Steven Dake > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Friday, August 5, 2016 at 6:52 AM

[openstack-dev] [kollla] Needing volunteers for Geography Coordinators for making use of OSIC cluster

Hey folks, The kind folks at OSIC have granted the Kolla team access to 132 nodes of super high powered gear for scale testing Kolla. The objectives are 3 fold: 1. Determine if Kolla can scale to 132 nodes for a variety of test cases - if not fix bugs around those problems 2. If

Re: [openstack-dev] Project mascots update

From: Heidi Joy Tretheway > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Thursday, August 4, 2016 at 9:13 AM To: "OpenStack

Re: [openstack-dev] Project mascots update

On 8/3/16, 10:37 AM, "Steven Hardy" wrote: >On Wed, Aug 03, 2016 at 10:19:10AM -0700, Heidi Joy Tretheway wrote: >>Thanks to all of you for contributing unique and inspiring ideas to >>choose >>a team mascot. You can view a list of projects that have chosen their >>

Re: [openstack-dev] [tc] persistently single-vendor projects

Responses inline: On 8/2/16, 8:13 AM, "Hayes, Graham" wrote: >On 02/08/2016 15:42, Flavio Percoco wrote: >> On 01/08/16 10:19 -0400, Sean Dague wrote: >>> On 08/01/2016 09:58 AM, Davanum Srinivas wrote: Thierry, Ben, Doug, How can we distinguish between.

Re: [openstack-dev] [tc] persistently single-vendor projects

On 8/2/16, 7:17 AM, "Ed Leafe" <e...@leafe.com> wrote: >On Aug 2, 2016, at 8:50 AM, Steven Dake (stdake) <std...@cisco.com> wrote: > >> For example tripleo is single-vendor, but is doing all the right things >>to >> dig out of single vendor by d

Re: [openstack-dev] [tc] persistently single-vendor projects

tion track which from my experience with founding Heat was a serious hurdle for OpenStack in general and Ceilometer and Heat specifically. Regards, -steve > >Doug > >> >> -- >> Adrian >> >> > On Aug 1, 2016, at 5:11 AM, Sean Dague <s...@dague.net

Re: [openstack-dev] [kolla] Why base image always be built each time build a specific image.

Paul, I think the cache isn't working exactly as you described for the base image. Not sure what is going on there - it could just be my misperception. However, as you point out the time spent "rebuilding" the base image is very small (under 30 seconds) so I don't believe its a pressing

Re: [openstack-dev] [docker] [magnum] Magnum account on Docker Hub

Ton, I may or may not have set it up early in Magnum's development. I just don't remember. My recommendation is to file a support ticket with docker and see if they will tell you who it belongs to (as in does it belong to one of the founders of Magnum) or if it belongs to some other third

Re: [openstack-dev] [tc] persistently single-vendor projects

On 7/31/16, 11:29 AM, "Doug Hellmann" <d...@doughellmann.com> wrote: >Excerpts from Steven Dake (stdake)'s message of 2016-07-31 18:17:28 +: >> Kevin, >> >> Just assessing your numbers, the team:diverse-affiliation tag covers >>what >>

Re: [openstack-dev] [tc] persistently single-vendor projects

Kevin, Just assessing your numbers, the team:diverse-affiliation tag covers what is required to maintain that tag. It covers more then core reviewers - also covers commits and reviews. See: https://github.com/openstack/governance/blob/master/reference/tags/team_div erse-affiliation.rst I can

Re: [openstack-dev] [kolla][stable] Please consider our application for stable:follows-policy for Kolla

Hey folks, I just wanted to let the core team and others in the community know this tag application was rejected. The Kolla core team made a choice when we decided to make Liberty non-dangerous. We knew at the time it would imperil an application for stable:follows-policy. We thought at the

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

-steve On 7/28/16, 1:13 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: >Excerpts from Steven Dake (stdake)'s message of 2016-07-28 19:40:29 +: >> >> On 7/28/16, 12:30 PM, "Davanum Srinivas" <dava...@gmail.com> wrote: >> >>

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

a resolution is reached is not the right thing. Regards -steve > >Thanks, >Dims > >On Thu, Jul 28, 2016 at 3:26 PM, Steven Dake (stdake) <std...@cisco.com> >wrote: >> Dims, >> >> I personally think its the responsibility of the TC to resolve this >&g

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

lease write up a proposal for the TC to >consider? (https://review.openstack.org/#/q/project:openstack/governance) > >Thanks, >-- Dims > >On Thu, Jul 28, 2016 at 2:01 PM, Steven Dake (stdake) <std...@cisco.com> >wrote: >> Jay, >> >> I'll be frank. I have

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

e repos *aren't in the OpenStack tent* so how precisely would TC >guidance about what it means for a repo to be part of the OpenStack tent >be useful here? > >-jay > >On 07/28/2016 01:04 PM, Steven Dake (stdake) wrote: >> Jay, >> >> That resolution doesn't clari

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

of >time. > >Please stop using a marketing press release as some indication of what >the "intent" is for these repos or even that there *is* any intent at >this point. It's really early on and these repos are intended as a place >to experiment and innovate. I don't see why there is so

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Doug, Zane's analysis is correct. I agree with Zane's assessment that TC clarification can solve this situation. Regards -steve On 7/28/16, 9:15 AM, "Zane Bitter" wrote: >On 28/07/16 08:48, Vladimir Kozhukalov wrote: >> Fuel-ccp repositories are public, everyone is

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Thanks for the clarity Doug. Regards -steve On 7/28/16, 8:37 AM, "Doug Hellmann" <d...@doughellmann.com> wrote: >Excerpts from Flavio Percoco's message of 2016-07-28 16:43:35 +0200: >> On 28/07/16 04:45 +, Steven Dake (stdake) wrote: >> > >> >

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On 7/27/16, 2:12 PM, "Jay Pipes" wrote: >On 07/27/2016 04:42 PM, Ed Leafe wrote: >> On Jul 27, 2016, at 2:42 PM, Fox, Kevin M wrote: >> >>> Its not an "end user" facing thing, but it is an "operator" facing >>>thing. >> >> Well, the end user for Kolla

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

One correction inside: On 7/27/16, 12:02 PM, "Jay Pipes" wrote: >On 07/27/2016 01:59 PM, Fox, Kevin M wrote: >> Kolla is providing a public api for docker containers and kubernetes >>templates though. So its not just a deployment tool issue. Its not >>specifically rest, but

Re: [openstack-dev] [kolla] repo split

artin André" <m.an...@redhat.com> wrote: >On Thu, Jul 21, 2016 at 5:21 PM, Steven Dake (stdake) <std...@cisco.com> >wrote: >> I am voting -1 for now, but would likely change my vote after we branch >> Newton. I'm not a super big fan of votes way ahead of major

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Michael, Response inline. From: Michael Still > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Wednesday, July 27, 2016 at 5:30 AM To:

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

M >To: OpenStack Development Mailing List (not for usage questions) >Subject: Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is >getting Fuel CCP (docker/k8s) kicked off > >On Tue, Jul 26, 2016 at 09:42:10PM +, Steven Dake (stdake) wrote: >> >> >> O

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On 7/26/16, 2:13 PM, "Jim Rollenhagen" <j...@jimrollenhagen.com> wrote: >On Tue, Jul 26, 2016 at 08:36:01PM +, Steven Dake (stdake) wrote: >> Dims, >> >> The project-config addition was debated by Andreas before this >>partnership >> in thi

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

n the project-config review: >https://review.openstack.org/#/c/335584/ > > >Thanks, >Dims > >On Tue, Jul 26, 2016 at 3:47 PM, Steven Dake (stdake) <std...@cisco.com> >wrote: >> Dims, >> >> Given the strong language around partnership between Intel, Mirantis, >

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Dims, Given the strong language around partnership between Intel, Mirantis, and Google in that press release, and the activity in the review queue (2 pages of outstanding reviews) it seems clear to me that the intent is for this part of Fuel to participate in the big tent. The right thing to do

Re: [openstack-dev] [release][kolla] Error in tagging process by release liason

On 7/26/16, 5:55 AM, "Doug Hellmann" <d...@doughellmann.com> wrote: >Excerpts from Steven Dake (stdake)'s message of 2016-07-23 18:27:00 +: >> Doug and friends, >> >> I made a pretty serious error when tagging kolla-kubernetes originally.

Re: [openstack-dev] [kolla] Monitoring tooling

Response inline On 7/25/16, 11:54 AM, "Matthias Runge" wrote: >On 25/07/16 09:57, Julien Danjou wrote: >> On Sun, Jul 24 2016, Mathias Ewald wrote: >> >>> 5. InfluxDB to store metrics >>> 6. Grafana to dashboard metrics >> >> Would be nice to leverage scalable and open

Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag

ck-dev] [kolla][vote] Applying for stable-follows tag +1 to apply I'd like to be the volunteer. On Mon, Jul 18, 2016 at 9:04 PM, Swapnil Kulkarni (coolsvap) <m...@coolsvap.net<mailto:m...@coolsvap.net>> wrote: On Mon, Jul 18, 2016 at 6:23 PM, Paul Bourke <paul.bou...@oracle.com<m

Re: [openstack-dev] [kolla] Monitoring tooling

This 218 issue looks like it has a full solution to containerizing telegraf. I suspect collectd is VERY similar in nature – so if your up for two challenges instead of one, collectd would be a good second target :) Regards -steve From: Mathias Ewald >

Re: [openstack-dev] [kolla] Monitoring tooling

Collectd is how you obtain the host disk usage. It can be done although collectd is nearing the complexity of turning nova into a container so it may need someone experienced with Kolla to execute. Regards -steve On 7/25/16, 12:39 AM, "Jeffrey Zhang" wrote: >I am open

[openstack-dev] [kolla][stable] Please consider our application for stable:follows-policy for Kolla

[Forgot kolla tag] From: Steven Dake > Date: Saturday, July 23, 2016 at 12:30 PM To: "OpenStack Development Mailing List (not for usage questions)" > Subject: [stable] Please

[openstack-dev] [stable] Please consider our application for stable:follows-policy for Kolla

Hey folks, The review is here: https://review.openstack.org/346455 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag

This vote passed unanimously prior to the July 25th deadline. Lets apply :) Regards -steve From: Steven Dake > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

[openstack-dev] [release][kolla] Error in tagging process by release liason

Doug and friends, I made a pretty serious error when tagging kolla-kubernetes originally. Kolla-kubernetes is in development and not in a production ready state. We also don't intend to apply for many if any tags for this repository until it becomes more mature. We do not intend to do

Re: [openstack-dev] [kolla] Monitoring tooling

or concerns welcome. Regards -steve On 7/22/16, 3:42 PM, "Stephen Hindle" <shin...@llnw.com> wrote: >Don't forget mewalds implementation as well - we now have 2 monitoring >options for kolla :-) > >On Fri, Jul 22, 2016 at 3:15 PM, Steven Dake (stdake) <std...

Re: [openstack-dev] [Magnum] Remove Davanum Srinivas from Magnum core team

Your a class act Dims. It was good working with you on Magnum :) Regards -steve On 7/22/16, 2:15 PM, "Davanum Srinivas" wrote: >Thanks Hongbin! > >On Fri, Jul 22, 2016 at 5:13 PM, Hongbin Lu wrote: >> Hi all, >> >> >> >> Based on Dims¹s request, I

Re: [openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes

nt: Friday, July 22, 2016 2:19 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes On 22 July 2016 at 21:35, Steven Dake (stdake) <std...@cisco.com<mailto:std.

[openstack-dev] [kolla] Monitoring tooling

Hi folks, At the midcycle we decided to push off implementing Monitoring until post Newton. The rationale for this decision was that the core review team has enough on their plates and nobody was super keen to implement any monitoring solution given our other priorities. Like all good

Re: [openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes

quot;OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes On 22 July 2016 at 2

[openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes

Hey folks, I know it doesn't make a lot of sense to break up containers from ansible changes to people outside the core review team, but for anything with backport potential, please do so. We are considering in Occata splitting the kolla repo into two (kolla = containers & build,

Re: [openstack-dev] [kolla] repo split

I am voting -1 for now, but would likely change my vote after we branch Newton. I'm not a super big fan of votes way ahead of major events (such as branching) because a bunch of things could change between now and then and the vote would be binding. Still community called the vote - so vote

Re: [openstack-dev] [kolla] our mascot - input needed

e questions)" >>><openstack-dev@lists.openstack.org> >>> Sent: Saturday, July 16, 2016 1:24:08 PM >>> Subject: Re: [openstack-dev] [kolla] our mascot - input needed >>> >>> Sorry, I missed the kolla mid-cycle summit as I was at a conference.

[openstack-dev] [kolla][vote] Applying for stable-follows tag

Hey Koalians, I'd like us to consider applying for the stable follows policy tag. Full details are here: http://github.com/openstack/governance/blob/master/reference/tags/stable_follows-policy.rst Because of the magic work we did to make liberty functional, it is possible that we may not be

[openstack-dev] [kolla] Patches needing review

Hey folks, If you have spare cycles to burn on reviews, the following would help: https://etherpad.openstack.org/p/R3rVu81fGU __ OpenStack Development Mailing List (not for usage

[openstack-dev] [kolla] our mascot - input needed

Hey folks, The OpenStack foundation is putting together mascots for every project with a proper artist doing the work. The cool thing about this is we a) get stickers b) have consistent look and feel among mascots in OpenStack. The downside is we have to make a decision. The foundation wants

Re: [openstack-dev] [kolla][nova][infra] Voting gates

ibuteError: 'module' object has no attribute >'VIR_MIGRATE_AUTO_CONVERGE' > >The full log can be viewed at >http://logs.openstack.org/76/339776/7/check/gate-kolla-dsvm-deploy-ubuntu- >source/0849a74/console.html#_2016-07-13_18_04_12_526704 > >-Paul > >On 14/07/16 17:13,

Re: [openstack-dev] [kolla][nova][infra] Voting gates

Matt, My computer is bust, but I've asked Paul and Serguei to get back to you with answers to your questions in the next 30 minutes. Regards -steve On 7/14/16, 9:13 AM, "Matt Riedemann" <mrie...@linux.vnet.ibm.com> wrote: >On 7/14/2016 9:21 AM, Steven Dake (stda

Re: [openstack-dev] [kolla][nova][infra] Voting gates

Antia, Thanks for the correction. I've been at this about 5 years, and agree - things are muddy :) Kolla cores - when reading this email, please keep Anita's comments in mind. Regards -steve On 7/14/16, 7:37 AM, "Anita Kuno" <ante...@anteaya.info> wrote: >On 07/14/2016 10

[openstack-dev] [kolla][nova][infra] Voting gates

Hey folks, At the midcycle, we had a session on gating. Out of that session came the decision to make the build gates voting as soon as the mirroring is finished for ubuntu first (because that is closer for us to get mirroring sorted out) followed by CentOS/Oracle Linux. I am taking this

[openstack-dev] [kolla] ended up with extra 85watt magsafe power supply

Hey folks, I ended up with an extra power supply for a mac. I'm not sure if it is from someone at the midcycle or from the Ansible HQ offices. If its from the Ansible HQ offices, I'll have my wife take it with her next time she visits. If it was a midcycle attendee, please contact me off

Re: [openstack-dev] [kolla] New specs process - a dicussion

Josh, We did have the discussion at summit. We aren't even going to have a "big spec". We are going to run as bare minimal of a spec as possible. The reason I brought up spec additions is because Kolla has become so large, managing the project using current techniques is not optimal. I don't

Re: [openstack-dev] [kolla] New specs process - a dicussion

One thing Michal left out is we are not planning to make this change until we branch Newton, assuming there is a majority vote reached. As typical, voting will remain open for one week until either a majority has been reached or the time has expired. The deadline to vote is Tuesday 19th of July.

<    1   2   3   4   5   6   7   8   >