Re: [openstack-dev] [kolla] [tools] OpenStack client in a Docker container

>How would you prefer me to approach this? At the moment I am >generating the images based on some ansible scripts I have in a >general playbook repository. > >regards, > > >Gerard > >On Tue, Jun 28, 2016 at 11:56 PM, Steven Dake (stdake) <std...@cisco.com> >

Re: [openstack-dev] [kolla] version of python2-oslo-config

Haikel, We are running master branch of rdo in master of kolla. Thanks Regards, -steve On 6/29/16, 3:45 AM, "Haïkel" <hgue...@fedoraproject.org> wrote: >2016-06-28 17:53 GMT+02:00 Steven Dake (stdake) <std...@cisco.com>: >> The mitaka branch of Kolla requires 3

Re: [openstack-dev] [release] the meaning of the release:managed tag now that everything is released:managed

On 7/1/16, 11:18 AM, "Doug Hellmann" wrote: >Excerpts from Jeremy Stanley's message of 2016-07-01 13:50:30 +: >> On 2016-07-01 11:24:27 +0200 (+0200), Thierry Carrez wrote: >> > Short answer is: release:managed doesn't mean that much anymore (all >> > official

Re: [openstack-dev] [kolla][ironic] My thoughts on Kolla + BiFrost integration

lla >configuration... Could you expand here. Kolla currently expects the machines under its control to be only OpenStack machines, and not have other applications running on them. Hope that was helpful. Regards -steve > > >On Thu, Jun 30, 2016 at 12:43 PM, Mooney, Sean K ><

[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] Phoenix area meet up with the topic of Kolla Feb 15th @ 21:00 UTC

Hey folks, Toby Cardone has kindly organized a local (to me) community meetup hosted by the Red Hat Software User Group at Insight’s facilities in Tempe, AZ with the topic of Kolla on February 15th, 2017 at 21:00 UTC. Several folks in the Kolla IRC channel have asked if remote participation

[openstack-dev] [kolla] pip install kolla-ansible 4.0.0b3+ broken

Hey folks, Pip install kolla-ansible is busted. I’d take ownership of this bug myself, however, I am personally swamped. This is a DOA deliverable issue and as such is higher priority than “critical”. Can someone in the community take a look?

Re: [openstack-dev] Large Contributing OpenStack Operators working group?

Jay, I don’t see a reference to the wiki page in your email and don’t immediately see the LCOO working group wiki. From what you describe this working group is not working within the framework of the 4 opens which is one of OpenStack’s fundamental philosophies. Thanks for bringing up your

Re: [openstack-dev] [kolla-ansible] [kolla] Am I doing this wrong?

Kris, Thanks for adding the kolla tag. As we reach milestone 3, every kolla dev is knee deep in development and probably not reading mails not directly tagged with [kolla]. IOutlook 2016 has a bug where I cannot respond inline. I am replying here so my gmail account picks up the email so

Re: [openstack-dev] [kolla-ansible] [kolla] Am I doing this wrong?

Thanks peeps for responding to Kris. Kris, I had offered a response – do you need further information answered? It looks to me like all the questions have been answered by others in the community. If not, feel free to respond and I’ll answer the remainders. Sean when your around and I am

Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

t; Subject: Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation On 2017-02-18 15:46:19 + (+), Steven Dake (stdake) wrote: [...] > In the past the foundation has been wary of enabling remote > participation. [...] Only wary because of p

[openstack-dev] [kolla] PTG Day #1 Webex remote participation

Dake <messen...@webex.com> Reply-To: "Steven Dake (stdake)" <std...@cisco.com> Date: Saturday, February 18, 2017 at 12:02 AM To: "Steven Dake (stdake)" <std...@cisco.com> Subject: (Forward to others) WebEx meeting invitation: Kolla PTG Day #1 You can forward this

[openstack-dev] [kolla] Kolla PTG Day #2

<messen...@webex.com> Reply-To: "Steven Dake (stdake)" <std...@cisco.com> Date: Saturday, February 18, 2017 at 12:07 AM To: "Steven Dake (stdake)" <std...@cisco.com> Subject: (Forward to others) WebEx meeting invitation: Kolla PTG Day #2 You can forward this

Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

me folks that aren't able to come due to budget constraints, but this would allow them to participate at the PTG sessions. -- Brandon B. Jozsa ________ From: Steven Dake (stdake) <std...@cisco.com> Sent: Saturday, February 18, 2017 2:16:36 AM To: OpenStack Deve

Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

ay, February 18, 2017 at 9:32 AM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation ________ From: Steven Dake (stdake) <std...@ci

Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation

Jeremy, I understood your original message that it was a logistical nightmare to sort out scaling remote participation across the entire ODS or (now the new PTGs) and it is not a software tools problem but rather a logistics problem independent of whatever software platform is used. I agree,

[openstack-dev] Reminder to use recheck rather then rebase to trigger a gate re-run: was Re: [kolla] unblocking the gate

on, Feb 29, 2016 at 6:42 PM, Clark Boylan <cboy...@sapwetik.org> > wrote: > > > On Mon, Feb 29, 2016, at 09:09 AM, Steven Dake (stdake) wrote: > > > > > > > > > On 2/29/16, 12:26 AM, "Andreas Jaeger" <a...@suse.com>

Re: [openstack-dev] [kolla] Support for non-x86_64 architectures

Marcin, I think this work is fantastic! The Ocata feature deadline has passed. Reference: https://releases.openstack.org/ocata/schedule.html The feature freeze deadline was January 25th 2017. What this means is that this work will need to go into Pike instead of Ocata. One of the reasons

Re: [openstack-dev] [kolla] Mascot

The mascot is absolutely fantastic! Nice work to all involved! Regards -steve -Original Message- From: Michał Jastrzębski Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Monday, February 13, 2017 at

Re: [openstack-dev] [kolla] Phoenix area meet up with the topic of Kolla Feb 15th @ 21:00 UTC

. The rest of the information is correct. Hope to see you for the live stream or if your in the greater Phoenix area, in person! Regards -steve From: "Steven Dake (stdake)" <std...@cisco.com> Date: Tuesday, January 31, 2017 at 5:56 PM To: "OpenStack Development Mailin

Re: [openstack-dev] [fuel][kolla][kuryr][openstack-ansible][openstack-helm] OpenStack on containers leaveraging kuryr

Flavio, Somehow the fuel project and openstack-ansible project got left off the taglines. I’m not sure if the fuel peeps saw this thread, but I know the openstack-ansible peeps didn’t see the thread. As a result, I’ve added those taglines. Hopefully we can include the broader deployment

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

Flavio, I think Michal (inc0) was planning to reach out to the TripleO team to at least get one or more design sessions in Wednesday. Kolla’s PTG schedule for Monday and Tuesday is packed with a wait list of topics. I depart IIRC Wednesday at 11AM – I had asked inc0 if we do these we do them

Re: [openstack-dev] [vote][kolla] deprecation for Debian distro support

Gema, Yes team meeting sounds good. I am changing my vote from choice 2 to abstain until this is sorted out. Regards -steve -Original Message- From: Gema Gomez Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [vote][kolla] deprecation for Debian distro support

My vote is for option 2 to deprecate Debian as there has been very little activity and operators seem uninterested in Debian as a platform. We could always add it back in at a later date if operators were to request it and the Debian team were interested in maintaining it. Regards -steve

[openstack-dev] [kolla] Contributors welcome to kolla-kubernetes 0.5.0

Hey folks, The release team released kolla-kubernetes 0.4.0 Sunday January 15th. Now we are in 0.5.0 development which lasts one month. The general architecture of OpenStack based deployments with a Kubernetes underlay is taking form. There are 5 blueprints in 0.5.0 which we expect should

[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

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

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] [deployment][TripleO][kolla][ansible][fuel] Next steps for cross project collaboration

I think IRC is more effective for real time collaboration then waiting a week for a meeting. We shouldn’t have to rant at all since we are all part of OpenStack ☺ Regards -steve -Original Message- From: Michał Jastrzębski Reply-To: "OpenStack Development Mailing

Re: [openstack-dev] [deployment][TripleO][kolla][ansible][fuel] Next steps for cross project collaboration

Andy, A monthly meeting as I have voiced before in this thread is not sufficient to enable good cross-project collaboration. To rectify this, when Steve Hardy started this thread, I started the process of creating an IRC channel in #openstack-deployment. I understand there has been one voice

Re: [openstack-dev] [kolla][infra] does someone cares about Jenkins? I stopped.

Marcin, You can submit a bug for issue #1 you raised and fix it yourself or another community member can fix it after a bug is filed. Regarding issue #2, FWIW, I agree local mirroring is the answer. Kolla needs to locally mirror several repositories in OpenStack Infra so the random failures

[openstack-dev] [kolla] Making a deployment guide for kolla-kubernetes

Hey folks, We decided in Wednesday’s 16:00 UTC Kolla meeting to start tackling some of the blocking items for 1.0.0 of kolla-kubernetes. One of those items is a deployment guide. The start of the deployment guide is here: https://etherpad.openstack.org/p/kolla-kubernetes-deploy-guide-BP We

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

[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

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

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] 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

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,

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

[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

[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] [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][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)" <

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] 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] 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] 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.

[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

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

We have far exceeded a majority for choice C (which is my preferred choice as well). So once 3.0.0 tags, it is all hands on deck to make the repo split happen as well as get started on the osic documentation which we owe the OSIC team. There were no other votes for other choices. While not

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

Christian, While the vote was not unanimous, a strong majority of core reviewers were in favor of our nomination with no veto in the voting period. I know the two core reviewers that did not vote are travelling so perhaps they missed the vote. Welcome to the core review team! I attempted to

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

k.org/meetings/security/2016/security.2016-09-22-17.00.log.html On Fri, Sep 23, 2016 at 4:23 AM, Davanum Srinivas <dava...@gmail.com<mailto:dava...@gmail.com>> wrote: > Steven, > > Fair point. > > Thanks, > Dims > > On Thu, Sep 22, 2016 at 11:04 PM, Steven Dake

Re: [openstack-dev] [kolla] the user in container should NOT have write permission for configuration file

Sam is correct here. This is the why behind the how ☺ Regards -steve From: Sam Yaple Reply-To: "s...@yaple.net" , "OpenStack Development Mailing List (not for usage questions)" Date: Monday, September 26, 2016 at 7:43 AM

[openstack-dev] Self-nomination to serve on the technical committee team

My Peers, I am self-nominating for serving you as your technical committee representative. I won't bore you with my professional accomplishments. If you want to see such information to judge if I'm qualified for serving you on the technical committee team, that information is available in my

Re: [openstack-dev] TC candidacy

Emilen, You say "the previous *PTL* of an OpenStack installation automation project" as if there were only one previous PTL :) There are many previous PTLs of OpenStack automation projects. I feel the question was directed at me, so I'll answer. From:

Re: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

Doug, We have already tagged rc1 long ago, but ack on rc2 (we are targeting 12th at present) and ack on 20th for retag of final rc. We expect our rc2 to be final. If there are critical bugs that make the release doa in some way (such as upgrades, reconfigure etc), we will obviously have to

Re: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

harder time coming up with optimal solutions because I lack the context the release team has. Regards -steve From: "Steven Dake (stdake)" <std...@cisco.com> Date: Friday, October 7, 2016 at 1:39 PM To: "OpenStack Development Mailing List (not for usage questi

[openstack-dev] [kolla] Cross proejct initiative patches should merge free of tags/bugs/blueprints

Hey folks, Cross project initiative patches like this one: https://review.openstack.org/#/c/383226/1 Should always be approved if they pass code review and the gate is green. There is no need for a bug id or trivial fix or blueprint. Please do make sure to verify they are correct and don’t

[openstack-dev] [kolla] ~root and /etc of osic testing

Hey folks, Several people have asked for archives of the OSIC work we did. Those files can be found here: https://drive.google.com/drive/folders/0B8q6xDPETSkHc05fR21qeElpc2M?usp=sharing Regards, -steve __ OpenStack

Re: [openstack-dev] TC candidacy

e questions)" <openstack-dev@lists.openstack.org> Date: Tuesday, October 4, 2016 at 4:46 AM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] TC candidacy On Tue, Oct 4, 2016 at 4:01 AM, S

[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] [vote][kolla] deprecation for debian distro support

n distro support Option 2 2016-09-20 16:07 GMT+02:00 Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>>: Consider this a reversal of my vote for Debian deprecation. Swapnil, thanks for bringing this fact to our attention. It was missing from the original vo

Re: [openstack-dev] [networking-cisco] Poll to decide networking-cisco weekly meeting times

Sam, Can this meeting instead be held in the normal openstack-meeting-1 -> 4 channels? Having one-off meetings in #openstack-networking-cisco is totally fine. Having standing team meetings there is atypical of OpenStack projects. The main value of using the opentack-meeting-1-4 channels is

Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

On 9/20/16, 11:18 AM, "Haïkel" wrote: 2016-09-19 19:40 GMT+02:00 Jeffrey Zhang : > Kolla core reviewer team, > > Kolla supports multiple Linux distros now, including > > * Ubuntu > * CentOS > * RHEL > *

Re: [openstack-dev] [Kolla] Ocata summit session poll

One note in this poll. Repo-split has already reached a consensus decision via ml vote, and the activity around that will happen prior to summit, so it is probably worth ignoring entirely. Regards -steve On 9/21/16, 10:14 AM, "Michał Jastrzębski" wrote: Hello,

Re: [openstack-dev] [kolla][elections][ptl] Kolla PTL Candidacy for Jeffrey Zhang

Hui, Change is what you will see as I am not running for PTL for Ocata. Reference: http://lists.openstack.org/pipermail/openstack-dev/2016-September/103499.html Regards -steve On 9/14/16, 4:32 PM, "Hui Kang" wrote: +1 for Jeffrey Zhang - Jeffrey is full

Re: [openstack-dev] [kolla][release] Branching of stable/newton

Thierry, Cool wfm. Thanks -steve On 9/18/16, 7:08 AM, "Thierry Carrez" <thie...@openstack.org> wrote: Steven Dake (stdake) wrote: > Release team, > > At one point Doug had indicated all projects would automatically branch > on tagging of rc

Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

Fwiw Swapnil, I think having a solid fedora implementation would be fantastic to help manage the transition to centos8 whenever that happens. At this point nobody has stepped up to do the work. We can always revisit any policy or vote in the future if the environment changes (i.e. you are

Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

I disagree. Oracle Linux is well implemented and very well maintained by Paul Bourke and many other fine folks from Oracle. CentOS is derived from RHEL (changing trademarks and marketing fluff, not code). Regards -steve From: Dave Walker Reply-To: "OpenStack Development

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

+1 for option #2 with same commentary as prior relating to fedora. Regards -steve On 9/19/16, 10:44 AM, "Jeffrey Zhang" wrote: Kolla core reviewer team, Kolla supports multiple Linux distros now, including * Ubuntu * CentOS * RHEL *

Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

Dims, This isn’t any of my particular business except it could affect emerging technology projects (which I find important to OpenStack’s future) negatively – so I thought I’d chime in. A lack of activity in a specs repo doesn’t mean much to me. For example, as Kolla was an emerging project

Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

Bogdan, I recognize English isn’t your first language, so forgive me if I have mis-parsed your message. I think the question you are asking is “Can we have cooperation to standardize on how best to do OpenStack on Kubernetes”. We tried an analog of that with Mirantis around Mesos, and that

Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s On 22/09/16 20:55 +, Steven Dake (stdake) wrote: Flavio, Apologies for delay in response – my backlo

Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s On 09/23/2016 01:04 PM, Steven Dake (stdake) wrote: I also fail to see how training the Fuel team with the choices Kolla has made in implementation puts OpenStack first. Sorry, could you elaborate on what exactly you mean above?

Re: [openstack-dev] [kolla][release] Branching of stable/newton

8 16:08:04 +0200: > Steven Dake (stdake) wrote: > > Release team, > > > > At one point Doug had indicated all projects would automatically branch > > on tagging of rc1. I notice in git no Kolla stable/newton branch > > exists. Fwiw this is actually a g

Re: [openstack-dev] [Kolla] Ocata summit session poll

talk more about them. Let see how priorities will look like after couple days:) Also, please vote! On 21 September 2016 at 12:54, Swapnil Kulkarni <cools...@gmail.com> wrote: > On Wed, Sep 21, 2016 at 11:16 PM, Steven Dake (stdake) <std...@cisco.com> wrot

Re: [openstack-dev] [ptl] code churn and questionable changes

Folks, We want to be inviting to new contributors even if they are green. New contributors reflect on OpenStack’s growth in a positive way. The fact that a new-to-openstack contributor would make such and error doesn’t warrant such a negative response even if it a hassle for the various PTLs

[openstack-dev] [all][summit][kolla] Returning one workroom session to the foundation

OpenStack summit planning team, We have been planning summit for approximately 2-3 months here: https://etherpad.openstack.org/p/kolla-O-summit-planning We further codified this into a vote via civs: http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_8368e1e74f8a0049 As you can see from the

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

> > Martin > > On Tue, Sep 20, 2016 at 7:27 PM, Steven Dake (stdake) <std...@cisco.com> wrote: >> Matthias, >> >> >> >> I was asked why this is so by a different person. The reason is determining >> m

Re: [openstack-dev] [kolla] when we use yum install ansible to install ansible2.1.1.0， I deploy failed with mitaka ，and actually precheck limit version to 2.0.0.

Lu, The kolla documentation specifically states Newton has a pin on ansible < 2.0.0.0 From: "lu.yao...@zte.com.cn" Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Thursday, September 22, 2016 at 5:41 AM

Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to deploy OpenStack on k8s

Flavio, Apologies for delay in response – my backlog is large. Forgive me if I parsed your message incorrectly. It came across to me as “How do I blaze a trail for OpenStack on Kubernetes?”. That was asked of me personally 3 years ago which led to the formation of the Kolla project inside

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

ct: Re: [openstack-dev] [vote][kolla] deprecation for debian distro support Option 2 2016-09-20 16:07 GMT+02:00 Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>>: Consider this a reversal of my vote for Debian deprecation. Swapnil, thanks for bringing this fact to our attent

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

Consider this a reversal of my vote for Debian deprecation. Swapnil, thanks for bringing this fact to our attention. It was missing from the original vote. I don’t know why I didn’t bring up Benedikt’s contributions (which were substantial) just as Paul’s were substantial for Oracle Linux. I

Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

+1 for option 2, unless some good Fedora folk appear in Kolla to maintain it in the future. In that case, we can always undo a deprecation within a cycle. Note the deprecation policy states that we do not remove functionality for 1 cycle after having released it for stable deliverables. Even

[openstack-dev] [kolla][release] Branching of stable/newton

Release team, At one point Doug had indicated all projects would automatically branch on tagging of rc1. I notice in git no Kolla stable/newton branch exists. Fwiw this is actually a good thing, because 33 patches have merged since rc1 relating to things that need to go into Newton,

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

[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][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

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:

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

[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

[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][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][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] 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] [magnum] Fedora Atomic image that supports kubernetes external load balancer (for stable/mitaka)

ilt today. Ton, [nactive hide details for "Steven Dake (stdake)" ---09/27/2016 10:18:07 PM]"Steven Dake (stdake)" ---09/27/2016 10:18:07 PM---Dane, I’ve heard Yolanda has done good work on making disk image builder build fedora atomic properl From: "Steven Dake (stda

[openstack-dev] Deprecation Policies (related to Heka)

First off, apologies for missing most of the team meeting today. I have read through the logs and saw a discussion about deprecating heka. We need to ensure that we follow the deprecation policy. My understanding of the deprecation policy is as follows (in a nutshell): 1. We must

Re: [openstack-dev] [magnum] Fedora Atomic image that supports kubernetes external load balancer (for stable/mitaka)

Dane, I’ve heard Yolanda has done good work on making disk image builder build fedora atomic properly consistently. This may work better than the current image building tools available with atomic if you need to roll your own. Might try pinging her on irc for advice if you get jammed up

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Also impacts Kolla (as in our gates are blocked). At present we are using the proposed workaround until the pycparser 2.14 wheel and package are synced up. Regards -steve From: Matt Riedemann Reply-To: "OpenStack Development Mailing List (not for usage questions)"

<    1   2   3   4   5   6   7   8   >