Re: [openstack-dev] [kolla] [requirements] Stepping down as core reviewer

Swapnil, Pleasure working with you - hope to see you around the computerverse. Cheers -steve On 10/16/18, 5:34 AM, "ʂʍɒρƞįł Ҟưȴķɒʁʉɨ" wrote: Dear OpenStackers, For a few months now, I am not able to contribute to code or reviewing Kolla and Requirements actively given my

Re: [openstack-dev] [tc] [all] TC Report 18-40

Chris, Thanks for all the hard work you have put into this. FWIW I found value in your reports, but perhaps because I am not involved in the daily activities of the TC. Cheers -steve On 10/2/18, 8:25 AM, "Chris Dent" wrote: HTML: https://anticdent.org/tc-report-18-40.html

Re: [openstack-dev] [kolla] Committing proprietary plugins to OpenStack

?Shyam, Our policy, decided long ago, is that we would work with third party components (such as plugins) for nova, cinder, neutron, horizon, etc that were proprietary as long as the code that merges into Kolla specifically is ASL2. What is your plugin for? if its for nova, cinder, neutron,

Re: [openstack-dev] [kolla][project navigator] kolla missing in project navigator

Thierry, Kolla likely belongs in the packaging recipes in the map. Kolla-Ansible belongs in the lifecycle tools. FWIW, I'm agree with Jean on the location of OpenStack-Ansible in the map. This is a deployment tool, not really a set of recipes. I think the name "openstack-ansible" as a

Re: [openstack-dev] [kolla] Dropping core reviewer

our leadership, guidance and commitment to make > kolla the great project it is now. > > Best luck on your new projects and board of directors. > > Regards > > > > > > 2018-08-07 16:28 GMT+02:00 Steven Dake (stdake) > mailto:std...@cisco.com> > <

[openstack-dev] [kolla] Dropping core reviewer

Kollians, Many of you that know me well know my feelings towards participating as a core reviewer in a project. Folks with the ability to +2/+W gerrit changes can sometimes unintentionally harm a codebase if they are not consistently reviewing and maintaining codebase context. I also

Re: [openstack-dev] [kolla] ptl non candidacy

?Jeffrey, Thanks for your excellent service as Kolla PTL. You have served the Kolla community well. Regards, -steve From: Jeffrey Zhang Sent: Tuesday, July 24, 2018 8:48 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [kolla] ptl non

Re: [openstack-dev] [kolla][vote] Nominating Steve Noyes for kolla-cli core reviewer

+1 On 5/31/18, 10:08 AM, "Borne Mace" wrote: Greetings all, I would like to propose the addition of Steve Noyes to the kolla-cli core reviewer team. Consider this nomination as my personal +1. Steve has a long history with the kolla-cli and should be considered its

Re: [openstack-dev] [Zun][Kolla][Kolla-ansible] Verify Zun deployment in Kolla gate

Mark, The major constraint here is gate memory (which is maxed at 8gb). This is barely enough to run compute-kit (which is tested). Now that multiple nodes are a thing, it may be possible to run computekit on one node, and other services on other nodes. (IOW the environment has changed, and

Re: [openstack-dev] [kolla][vote]Core nomination for Mark Goddard (mgoddard) as kolla core member

+1 From: Jeffrey Zhang Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Thursday, April 26, 2018 at 5:32 PM To: OpenStack Development Mailing List Subject:

Re: [openstack-dev] [kolla] [tripleo] On moving start scripts out of Kolla images

Mark, TLDR good proposal I don’t think Paul was proposing what you proposed. However: You make a strong case for separately packaging the api (mostly which Is setcfg.py and the json API + docs + samples). I am super surprised nobody has ever proposed this in the past, but now is as good of

Re: [openstack-dev] [kolla] [tripleo] On moving start scripts out of Kolla images

+1. From: Mark Goddard Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Friday, April 6, 2018 at 11:41 AM To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [kolla][tc][openstack-helm][tripleo]propose retire kolla-kubernetes project

On April 2, 2018 at 6:00:15 AM, Martin André (m.an...@redhat.com<mailto:m.an...@redhat.com>) wrote: On Sun, Apr 1, 2018 at 12:07 AM, Steven Dake (stdake) <std...@cisco.com> wrote: > My viewpoint is as all deployments projects are already on an equal footing > when usin

Re: [openstack-dev] [kolla][tc][openstack-helm][tripleo]propose retire kolla-kubernetes project

On March 31, 2018 at 12:35:31 PM, Jeremy Stanley (fu...@yuggoth.org<mailto:fu...@yuggoth.org>) wrote: On 2018-03-31 18:06:07 + (+0000), Steven Dake (stdake) wrote: > I appreciate your personal interest in attempting to clarify the > Kolla mission statement. > > The c

Re: [openstack-dev] [kolla][kolla-kubernete][tc][openstack-helm]propose retire kolla-kubernetes project

On March 31, 2018 at 6:45:03 AM, Jeremy Stanley (fu...@yuggoth.org) wrote: [...] Given this, it sounds like the current Kolla mission statement of "provide production-ready containers and deployment tools for operating OpenStack clouds" could use some adjustment to drop

Re: [openstack-dev] [kolla][kolla-kubernete][tc][openstack-helm]propose retire kolla-kubernetes project

On March 30, 2018 at 2:17:09 AM, Thierry Carrez (thie...@openstack.org) wrote: There is a 3rd option, which I've been advocating for a while. The tension here lies in the fact that the Kolla team is both a low-level provider (Kolla the docker image provider) and a

[openstack-dev] [kolla] Dropping off kolla-kubernetes core reviewer team

Hey folks, As many core reviewers in Kolla core teams may already know, I am focused on OpenStack board of director work and adjacent community work. This involves bridging the OpenStack ecosystem and its various strategic focus areas with adjacent community projects that make sense. My work

Re: [openstack-dev] [kolla][vote] core nomination for caoyuan

+1 From: Jeffrey Zhang Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Sunday, March 11, 2018 at 7:13 PM To: OpenStack Development Mailing List Subject: Re:

Re: [openstack-dev] [Election] PTL Election Results & Conclusion

Agreed! Congratulations to all our newly elected PTLs. For past PTLs, thanks a bunch for your service! The election process I'm certain is very difficult to execute, and as a community member, I'd like to thank the election officials for their work. Cheers -steve On 2/15/18, 2:47 AM,

Re: [openstack-dev] [kolla] PTL non candidacy

Cheers Michal. Thank you for your service. Regards -steve From: Vikram Hosakote Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, January 31, 2018 at 1:04 PM To: "OpenStack Development Mailing List

Re: [openstack-dev] [kolla] Policy regarding template customisation

Agree, the “why” of this policy is stated here: https://docs.openstack.org/developer/kolla-ansible/deployment-philosophy.html Paul, I think your corrective actions sound good. Perhaps we should also reword “essential” to some other word that is more lenient. Cheers -steve From: Jeffrey Zhang

[openstack-dev] [kolla] Re: About maridb 10.1 on kolla

Michal wanted to test on multinode. Not sure if he ever got there. Anyway - feel free to take over the patch. Even though gerrit doesn't care about co-authors, co-authors might, and we want to keep a tidy history of authorship for CLA reasons, so please use the "Co-AUthored-by: first last "

Re: [openstack-dev] [kolla] Ansiblize init-runonce script

I wrote that script ages ago. I needed it in the repo so I could consistently deploy. It may still be entirely tailored around my environment ☺ That said, I had always hoped someone would make a generic cloud bootstrap for Kolla based upon the work in that script originally. Maybe this is

Re: [openstack-dev] [kolla] Proposal to add Marcin (hrw) to kolla images core team

+1 Cheers -steve On 11/3/17, 2:59 AM, "Michał Jastrzębski" wrote: It's my great pleasure to start another voting for core team addition! Everyone knows hrw, thanks to him Kolla now runs on both Power and ARM! Voting will be open for 14 days (until 16th of

Re: [openstack-dev] [tc] [kolla] [PTL] who can start the official meeting?

Dims, This was just a fella in the kolla community experimenting without attempting to cause harm. IOW he didn’t know exactly what he was doing which is helpful when messing with the meeting bots (. No harm done anyway, so no need to take any corrective action in implementation. Cheers

Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub

Sam, Agreed this matches my experience. Building one by one though will result in massive image size sprawl. Regards -steve From: Sam Yaple Reply-To: "s...@yaple.net" , "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

-steve On 10/16/17, 8:57 AM, "Steven Hardy" <sha...@redhat.com> wrote: On Mon, Oct 16, 2017 at 2:33 PM, Steven Dake (stdake) <std...@cisco.com> wrote: > Emilien, > > I generally thought the stable policy seemed reasonable enough for lifecycle manag

Re: [openstack-dev] [tc] [stable] [tripleo] [kolla] [ansible] [puppet] Proposing changes in stable policy for installers

Emilien, I generally thought the stable policy seemed reasonable enough for lifecycle management tools. I’m not sure what specific problems you had in TripleO although I did read your review. Kolla was just tagged with the stable policy, and TMK, we haven’t run into trouble yet, although the

Re: [openstack-dev] [kolla] Kolla is now stable:follows-policy project

Folks, The addition of this project maturity tag is a great achievement! This is one of many factors used by Operators to determine maturity of OpenStack projects. Glad to see our project’s persistence in this area paid off for the kolla and kolla-ansible deliverables. Good work all!

Re: [openstack-dev] [kolla] Looking for Docker images for Cinder, Glance etc for oVirt

Leni, Reading their website, they reference the “kollagllue’ namespace. That hasn’t been used for 2+ years (we switched to kolla). They also said a “recent” change in the imges was made to deploy via Ansible “and they weren’t ready for that yet”. That was 3 years ago. I think those docs

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Doug, In short, a configmap takes a bunch of config files, bundles them in a kubernetes object called a configmap, and then ships them to etcd. When a pod is launched, the pod mounts the configmaps using tmpfs and the raw config files are available for use by the openstack services.

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Flavio, Atleast for the kubernetes variant of kolla, bindmounting will always be used as this is fundamentally how configmaps operate. In order to maintain maximum flexilbility and compatibility with kubernetes, I am not keen to try a non-configmap way of doing things. Regards -steve

Re: [openstack-dev] [tc][kolla][stable][security][infra][all] guidelines for managing releases of binary artifacts

Doug, Thanks for the resolution. It is well written and sets appropriate guidelines. I was expecting something terrible – I guess I shouldn’t have expectations ahead of a resolution. Apologies for being a jerk on the ml. Nice work. I left some commentary in the review and left a vote of -1

Re: [Openstack-operators] [kolla] Issue with Galera

Christian, Serious apologies for lag in response. I just caught this mail today. If you are still suffering with this problem, drop by #openstack-kolla on irc and we can see if we can get you going. Note we do recommend 3 nodes for HA deployments, not 2 (this is one of the reasons).

Re: [openstack-dev] [TripleO][Kolla] default docker storage backend for TripleO

My experience with BTRFS has been flawless. My experience with overlayfs is that occasionally (older centos kernels) returned as permissions (rather the drwxrwrw). This most often happened after using the yum overlay driver. I’ve found overlay to be pretty reliable as a “read-only”

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Doug, When a docker image is pushed to dockerhub (or quay.io, etc) a tag is specified. If the tag already exists, it is overwritten. Regards -steve -Original Message- From: Doug Hellmann Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Michael, There has been a lot of cost and risk analysis in this thread. What hasn’t really been discussed at great detail is the “benefit analysis” which you have started. I think we are all clear on the risks and the costs. If we as a technical community are going to place a line in the sand

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Stop! Thanks, Dims On Tue, May 16, 2017 at 12:22 AM, Steven Dake (stdake) <std...@cisco.com> wrote: > Flavio, > > Forgive the top post – outlook ftw. > > I understand the concerns raised in this thread. It is unclear if this thread is

Re: [openstack-dev] [tc][infra][release][security][stable][kolla][loci][tripleo][docker][kubernetes] do we want to be publishing binary container images?

Flavio, Forgive the top post – outlook ftw. I understand the concerns raised in this thread. It is unclear if this thread is the feeling of two TC members or enough TC members care deeply about this issue to permanently limit OpenStack big tent projects’ ability to generate container images

Re: [openstack-dev] [kolla][kolla-ansible] Proposing Bertrand Lallau for kolla and kolla-ansible core

+1 -Original Message- From: Michał Jastrzębski Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, May 2, 2017 at 8:30 AM To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] All Hail our Newest Release Name - OpenStack Rocky

Monty, I guess the obligatory joke “It is going to be a Rocky release ahead!” must be made. \o/ Regards -steve -Original Message- From: Monty Taylor Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [kolla] OpenStack Kolla-Kubernetes Workshop: Demystifying the Gate - video conferencing information

s know if there is any tollfree number inorder to call from India & Hungary or joining webex is sufficient enough for audio even? BR, Sasikiran On Sun, Apr 23, 2017 at 2:59 AM, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote: As proposed earlier on the mailing

Re: [openstack-dev] [kolla] Demystifying the kolla-kubernetes gate

questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [kolla] Demystifying the kolla-kubernetes gate Is there an invite for this? I'm interested. On Apr 19, 2017 1:20 PM, "Steven Dake (stdake)" <std...@cisco.com<mailto:std...@cisco.com>> wrote: Hey

[openstack-dev] [kolla] OpenStack Kolla-Kubernetes Workshop: Demystifying the Gate - video conferencing information

As proposed earlier on the mailing list, A 2 week 6 session workshop has been organized From April 25th – May 4th Tu/W/Th for 45 minutes in length. The agenda for this workshop is as follows: Learn how OpenStack’s kolla-kubernetes gating functions to enable yourself to contribute more

Re: [openstack-dev] [kolla] [daisycloud-core] [requirements][magnum] [oslo] Do we really need to upgrade pbr, docker-py and oslo.utils

tils Zun required docker-py to be 1.8 or higher because older version of docker-py didn't have the API we need. Sorry if it caused difficulties on your side but I don't think it is feasible to downgrade the version for now since it will affect a ton of other projects. Best regards, Hongbin

Re: [openstack-dev] [kolla] [daisycloud-core] [requirements] [magnum] [oslo] Do we really need to upgrade pbr, docker-py and oslo.utils 

Hu, Kolla does not manage the global requirements process as it is global to OpenStack. The Kolla core reviewers essentially rubber stamp changes from the global requirements bot assuming they pass our gating. If they don’t pass our gating, we work with the committer to sort out a working

[openstack-dev] [kolla] Demystifying the kolla-kubernetes gate

Hey folks, I am holding a workshop on how the kolla-kubernetes gate operates. If you are interested in this workshop, please sign up here: http://doodle.com/poll/bee7umevf43nwi6y Regards, -steve __ OpenStack Development

Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

his on. :) Rich On Wed, Apr 12, 2017 at 7:53 PM Matt Riedemann <mriede...@gmail.com<mailto:mriede...@gmail.com>> wrote: On 4/12/2017 3:40 PM, Steven Dake (stdake) wrote: > Matt, > > Thanks for the response. It is helpful. > > Regards > -steve > > -Or

Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

il 12, 2017 at 4:36 PM To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables On 4/12/2017 11:59 AM, Steven Dake (stdake) wrote: > Hey folks,

[openstack-dev] [kolla][nova] Starting a core reviewer mentorship program for Kolla deliverables

Hey folks, In today’s Kolla team meeting, the idea was proposed of adopting nova’s “protocore” mentorship program for Kolla. We would like to know what nova has learned from this effort. In today’s Kolla meeting we had broad consensus on the following: 1) Kolla has participants that

Re: [openstack-dev] [election] TC non-candidacy

Mike, Thank you for your service. Regards -steve -Original Message- From: Mike Perez Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, April 4, 2017 at 1:20 PM To:

[openstack-dev] [kolla] Deployment Guide Documentation for kolla-kubernetes

Hey folks, The deployment guide is shaping up nicely here: https://review.openstack.org/#/c/447356/ If folks are interested giving the review a try: git clone http://github.com/openstack/kolla-kubernetes git fetch git://git.openstack.org/openstack/kolla-kubernetes refs/changes/56/447356/10 &&

[openstack-dev] [kolla] gate unwedged - please recheck your patches

Hey folks, If you have submitted patches for kolla-ansible since Friday March 17, gerrit has likely voted -1 on them because the voting gate was broken. I recommend a recheck which should clear up your patch for review and merge. Regards -steve

Re: [openstack-dev] [kolla] Proposing duonghq for core

+1! -Original Message- From: Michał Jastrzębski Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, March 8, 2017 at 1:41 AM To: "OpenStack Development Mailing List (not for usage questions)"

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

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

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

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

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

[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

[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

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

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

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

[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

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

Re: [openstack-dev] [release][ptl] not planning to serve as release PTL for Pike

Doug, Thanks for your leadership and your consistent help with helping Kolla solve how to use the release team’s tooling. I have to say that manually tagging as we did previously as PTLs (when I was a PTL) was pure madness. I really like what the releases team has done for OpenStack!

[openstack-dev] [kolla] Adding jeffrey4l to kolla-kubernetes-core because he is release liason

We are busily releasing 0.4.0 of the Kolla deliverable kolla-kubernetes and have determined we can’t release the kolla-kubernetes milestone without the release liaison for Kolla being on the core reviewer sub-team to make last minute fine tuning adjustments to the release and approve other

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Thierry, Cool thanks for the leeway here ☺ I agree wholeheartedly with your last sentiment. If an existing Kolla sub-team or an existing project (e.g. the Puppet team) in OpenStack or a new project wants to use Kolla images and feels they would operate more effectively without the structure

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Jozsa" <bjo...@jinkit.com> Date: Wednesday, January 11, 2017 at 1:01 PM To: "Britt Houser (bhouser)" <bhou...@cisco.com>, "Steven Dake (stdake)" <std...@cisco.com>, "OpenStack Development Mailing List (not for usage questions)" <openstack-dev

Re: [openstack-dev] [tc][kolla] Adding new deliverables

team. I'd be happy to discuss how to pave road for full project separation without causing pain for operators, users and developers, as to me their best interest should take priority. Cheers, Michal On 11 January 2017 at 09:59, Doug Hellmann <d...@doughellmann.com> wrote: > Excerpts from Steven D

Re: [openstack-dev] [tc][kolla] Adding new deliverables

k-dev@lists.openstack.org> Subject: Re: [openstack-dev] [tc][kolla] Adding new deliverables Excerpts from Steven Dake (stdake)'s message of 2017-01-11 14:50:31 +: > Thierry, > > I am not a big fan of the separate gerrit teams we have instituted inside the Kolla project.

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Thierry, I am not a big fan of the separate gerrit teams we have instituted inside the Kolla project. I always believed we should have one core reviewer team responsible for all deliverables to avoid not just the appearance but the reality that each team would fragment the overall community

Re: [openstack-dev] [tc][kolla] Adding new deliverables

Michal, Another option is 2 individuals from each core review team + PTL. That is lighter weight then 3 and 4, yet more constrained then 1 and 2 and would be my preferred choice (or alternatively 3 or 4). Adding a deliverable is serious business ☺ FWIW I don’t’ think we are at an impasse,

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

I think optimally we should check if we are running in rax-iad, and if so, set libvirt virtualization to qemu. I was pretty sure the gate script that sets up the system sets the libvirt type to qemu. After inspection of the gate scripts, this is not the case. Perhaps it was setup this way

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

more than ten error gates, all of them happened in rax-iad. On Sat, Dec 31, 2016 at 12:06 PM, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote: Jeffrey, Have you detected any pattern to any specific cloud provider in the logs? Regards -steve From: Jeffr

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

Jeffrey, Have you detected any pattern to any specific cloud provider in the logs? Regards -steve From: Jeffrey Zhang Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Friday, December 30, 2016 at 12:41

Re: [openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverable

- From: "Steven Dake (stdake)" <std...@cisco.com> Date: Friday, December 23, 2016 at 3:53 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [tc] Re: [kolla] A new kolla-salt deli

Re: [openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverable

lla-policy-core-team This way it would be easy to try and fail fast to run kolla with whatever. We need this kind of flexibility for people to innovate. Thoughts? Michal On 23 December 2016 at 13:11, Steven Dake (stdake) <std...@cisco.com> wrote: >

[openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverable

y think that would be overkill at this stage. Thoughts? Cheers Michal On 23 December 2016 at 05:34, Steven Dake (stdake) <std...@cisco.com> wrote: > Michal, > > > > I was thinking about kolla-salt and our Wednesday team meeti

[openstack-dev] [kolla] Collaboration between kolla and Helm upstream

Hey folks, Brandon Jozsa was kind enough to get some collaboration going between the OpenStack Kolla community and the Helm community within CNCF. My hope out of this effort is to build bridges between the OpenStack foundation and CNCF hosted by the Linux Foundation. We are starting small,

[openstack-dev] [kolla] A new kolla-salt deliverable

Michal, I was thinking about kolla-salt and our Wednesday team meeting and the declaration you made about how it should be done. I personally feel it is mandatory we hold a vote of the core review teams to add a new deliverable. We have voted on the addition of every deliverable we have ever

[openstack-dev] [kolla] Please use reno for all blueprints

Hey folks, I have seen many reviews hitting the queue without reno release notes. Its very simple and straightforward to create a reno release note. Simply run: reno –n blurb This creates a file in the releasenotes directory with a hash. Releasenotes should be committed with the commit in

[openstack-dev] [kolla] kolla-kubernetes needs to sort out what to call our k8s objects

Hello folks, In our team meeting today, I took an action to begin a mailing list discussion around what to call our k8s objects in the kolla-kubernetes deliverable. At present, we are calling them “pods”. The general consensus on the team meeting is this is a hard concept for people new to

Re: [openstack-dev] [picasso] Picasso (FaaS) project release!

Derek, I think Serverless is a great idea. I had considered starting a new project in October around Serverless. During my analysis I of course saw iron.io’s work and OpenWhisk. I thought OpenWhisk would be a better community to join as it was open. Iron.io and OpenWhisk should join

[openstack-dev] [kolla] Removal of a core reviewer from the kolla-kubernetes-core team

Hey peeps, David Wang asked that we remove him from the kolla-kubernetes-core team because he is involved in other activities and he isn’t sure if or when he will be able to begin reviewing again. In our earlier cleanup of the kolla-kubernetes-core review team, the core reviewer team was on

Re: [openstack-dev] [all][rdo][kolla] Recommending the RDO tag for the mailing list

k RDO dmsimard = [irc, github, twitter] On Tue, Dec 20, 2016 at 5:19 AM, Erno Kuvaja <ekuv...@redhat.com> wrote: > On Mon, Dec 19, 2016 at 2:21 PM, Steven Dake (stdake) <std...@cisco.com> wrote: >> Folks, >> >> >&g

  1   2   3   4   5   6   7   8   >