Re: [openstack-dev] [tc][kolla] Change to kolla's release model to gain access to release's website marketing

On 4/2/16, 10:01 AM, "Jeremy Stanley" wrote: >On 2016-04-02 16:13:28 +0000 (+0000), Steven Dake (stdake) wrote: >[...] >> I feel as though we are not permitted to participate in the >> marketing that takes place on the releases website >[...] > >I'll

Re: [openstack-dev] [tc][kolla] Change to kolla's release model to gain access to release's website marketing

A big correction to this thread below. On 4/2/16, 10:05 AM, "Steven Dake (stdake)" wrote: > > >On 4/2/16, 10:01 AM, "Jeremy Stanley" wrote: > >>On 2016-04-02 16:13:28 + (+), Steven Dake (stdake) wrote: >>[...] >>> I feel

Re: [openstack-dev] [tc][kolla] Change to kolla's release model to gain access to release's website marketing

On 4/2/16, 1:08 PM, "Doug Hellmann" wrote: > >> On Apr 2, 2016, at 1:20 PM, Steven Dake (stdake) >>wrote: >> >> A big correction to this thread below. >> >> On 4/2/16, 10:05 AM, "Steven Dake (stdake)" wrote: >> >>>

[openstack-dev] Announcing release of Kolla Mitaka rc3

Hey folks, We did a bangup job in the last 7 days fixing 25 bugs in Kolla. Our weekly capacity to solve bugs as a community is 25-30 bugs. Our final deadline is April 8th. Targeted for 2.0.0 (April 8tih) are currently 22 bugs. Many of these don't have owners, so if you want to contribute, p

[openstack-dev] [release][kolla] Announcing release of Kolla Mitaka rc3

Hey folks, We did a bangup job in the last 7 days fixing 25 bugs in Kolla. Our weekly capacity to solve bugs as a community is 25-30 bugs. Our final deadline is April 8th. Targeted for 2.0.0 (April 8tih) are currently 22 bugs. Many of these don't have owners, so if you want to contribute, p

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

ons)" mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO On Thu, 2016-03-31 at 08:22 +, Steven Dake (stdake) wrote: Kevin, I am not directly answering your question, but from the p

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On 4/3/16, 6:38 PM, "Dan Prince" wrote: > > > >On Mon, 2016-03-21 at 16:14 -0400, Zane Bitter wrote: >> As of the Liberty release, Magnum now supports provisioning Mesos >> clusters, so TripleO wouldn't have to maintain the installer for >> that >> either. (The choice of Mesos is somewhat unfo

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On 4/4/16, 5:53 AM, "Dan Prince" wrote: >On Mon, 2016-04-04 at 02:31 +, Steven Dake (stdake) wrote: >> >> On 4/3/16, 6:38 PM, "Dan Prince" wrote: >> >> > >> > >> > >> > >> > On Mon, 2016-03-21 a

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

The vote is unanimous in favor of Vikram joining the core reviewer team. I have made the appropriate permission changes in gerrit. Welcome to the core reviewer team Vikram! Regards -steve From: Steven Dake mailto:std...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage q

[openstack-dev] [kolla] Using reno

Hey folks, Reno is in our master codebase and mitaka. Every new feature should use reno at the conclusion of the patch set. The full documentation is here: http://docs.openstack.org/developer/reno/usage.html#creating-new-release-notes In short, to create a reno note, just run pip install reno

[openstack-dev] [kolla][vote] Nit-picking documentation changes

Hey folks, The reviewers in Kolla tend to nit-pick the quickstart guide to death during reviews. I'd like to keep that high bar in place for the QSG, because it is our most important piece of documentation at present. However, when new contributors see the nitpicking going on in reviews, I th

Re: [openstack-dev] [kolla][vote] Nit-picking documentation changes

On 4/11/16, 12:54 AM, "Gerard Braad" wrote: >Hi Steven, > >On Mon, Apr 11, 2016 at 3:37 PM, Steven Dake (stdake) >wrote: >> However, when new >> contributors see the nitpicking going on in reviews, I think they may >>get >> discouraged about

Re: [openstack-dev] [kolla][vote] Nit-picking documentation changes

On 4/11/16, 1:38 AM, "Gerard Braad" wrote: >Hi, > >On Mon, Apr 11, 2016 at 4:20 PM, Steven Dake (stdake) >wrote: >> On 4/11/16, 12:54 AM, "Gerard Braad" wrote: >> as >>>at the moment getting an environment up-and-running according to the &

Re: [openstack-dev] [kolla][vote] Nit-picking documentation changes

h after code merge, but well, we can take over >docs review. > >What do you think guys? I'd really like to keep high quality standard >all the way and don't scare off new commiters at the same time. > >Cheers, >Michal > >On 11 April 2016 at 03:50, Steven Dake

Re: [openstack-dev] [kolla][tc] [security] threat analysis, tags, and the road ahead

On 4/12/16, 10:37 AM, "Jeremy Stanley" wrote: >On 2016-04-01 15:50:57 + (+), Hayes, Graham wrote: >> If a team has already done a TA (e.g. as part of an internal >> product TA) (and produced all the documentation) would this meet >> the requirements? >> >> I ask, as Designate looks lik

[openstack-dev] [release][kolla] Release of kolla 2.0.0.0rc4

Hey folks, We had originally planned to release 2.0.0 today but there are a few more bugs left to resolve before our final tag. Hence, we made a decision to move the final 2.0.0 release to Thursday, April 21st. I am super pleased to announce the release of 2.0.0.0 rc4 which fixes 37 bugs, man

[openstack-dev] [kolla][ssecurity] Threat Analysis Design Session

Hey Folks, I've scheduled the Threat Analysis Design session on Thursday 11:50-12:30 in room MR415A. This slot was the best slot I could find that didn't conflict with any security projects. If the security team has a conflict with this slot that I didn't see or am unaware of, please speak u

[openstack-dev] [kolla][release] Infrastructure mailing list thread about how to handle our stable/liberty branch

Hey folks. Our stable/liberty branch is essentially broken beyond repair because of a fatal flaw in our usage of data containers. We have fixed this in Mitaka using named volumes. Our plan is to make Liberty equivalent to Mitaka and then make stable/liberty deploy Liberty. It will require fo

[openstack-dev] [kolla][infra] Gate bused until Sunday April 17th

Core Reviewers and developers, Hey folks. A shade + nodepool change has broken our gating functionality on the OVH cloud provider and probably some others. The net result is we can't actually gate our changes. I'd recommend for the moment to provide +1 reviews and revisit the review queue Su

Re: [openstack-dev] [ptl] [security][tc] Tidy up language in section 5 of the vulnerability:managed tag

On 4/12/16, 10:42 AM, "Jeremy Stanley" wrote: >On 2016-04-02 14:40:57 +0000 (+0000), Steven Dake (stdake) wrote: >[...] >> IANAL and writing these things correctly is hard to do properly ); >> involving the community around the pain points of the tagging

[openstack-dev] [kolla][security][infra][ops] Kolla Design Summit Agenda Published

OpenStackers, The full Kolla summit agenda is here: https://www.openstack.org/summit/austin-2016/summit-schedule/global-search?t=Kolla%3A We would super appreciate any operator presence in our fishbowl or design sessions so we do right by the Operators that use Kolla community generated code in

[openstack-dev] [kolla] let the liberty backport begin

Hey folks, Thanks to the release team and infrastructure team, we have a stable/liberty branch that is equivalent as of this afternoon to each other. Michal is free to submit his backport patch to stable/liberty now. In the process I was required to abandon all changes against stable/liberty.

[openstack-dev] [kolla] kolla-mesos development being scaled back

Hey folks, I know a lot of folks are already aware of this, but as we head into summit, in the interest of an Open Community, it is important to share this information widely. The major implementors of the kolla-emsos repository listed in this specification [1] don't intend to continue its dev

Re: [openstack-dev] Kolla multinode , multi-region deployment support

Grzegorz, This is a technical question about our roadmap and should be sent to the openstack-dev mailing list. As such, ccing openstack-dev so everyone can benefit from my thinking on this matter and others can weigh in. From: Grzegorz Koper mailto:grzegorz.ko...@pl.ibm.com>> Date: Monday, Ap

[openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

Fellow Core Reviewers, Since many of the engineers working on the kolla-mesos repository are moving on to other things[1], possibly including implementing Kubernetes as an underlay for OpenStack containers, I propose we move the kolla-mesos repository into the attic[2]. This will allow folks t

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

Responses inline. From: Sergey Lukjanov mailto:slukja...@mirantis.com>> Reply-To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Date: Friday, April 22, 2016 at 11:17 AM To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Subject: [ope

Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

Jeremy, Thanks for the information - you can tell I'm a bit dated ;) Folks, take this vote to mean what Jeremy has stated as far as repo deprecation goes. Regards -steve On 4/22/16, 8:01 PM, "Jeremy Stanley" wrote: >On 2016-04-23 00:08:03 +0000 (+0000), Steven D

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

On 4/23/16, 1:26 PM, "Jay Pipes" wrote: >On 04/22/2016 08:27 PM, Steven Dake (stdake) wrote: >> * Repository per OpenStack and Infra component, e.g. one from nova, >> one for neutron and etc. - to contain all needed container images >> for ru

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

On 4/24/16, 10:05 PM, "Tomasz Pa" wrote: >On Sat, Apr 23, 2016 at 2:27 AM, Steven Dake (stdake) >wrote: >> >> Trying to understand the issue here, do you believe the current jinja2 >> Dockerfiles are not readable? I'm pretty sure my 11 and 13 year

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

Tomasz, Response inline. On 4/25/16, 12:32 AM, "Tomasz Pa" wrote: >On Mon, Apr 25, 2016 at 5:51 AM, Jeffrey Zhang >wrote: >> >> I do not think this is the issue of Kolla. It is a issue of Docker >> images. All the docker images has such issue. This should be solved >> in the docker side. >> > >

[openstack-dev] [kolla] Meetup in Salon B - split between Magnum and Kolal

Hey folks, The meet up room for this morning is split between two rooms so we will be sharing a room in Salon B. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.opensta

Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

Hey folks, This vote passed with 8 core reviewers +1ing the retirement of the kolla-mesos repository. As such I will submit patches in the following week to retire this project and remove it from the technical committee's governance repository for the Kolla Project. Regards -steve From: Stev

[openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

Fellow core reviewers, We had a fantastic turnout at our fishbowl kubernetes as an underlay for Kolla session. The etherpad documents the folks interested and discussion at summit[1]. This proposal is mostly based upon a combination of several discussions at open design meetings coupled with

[openstack-dev] [kolla][kubernetes] One repo vs two

Ryan had rightly pointed out that when we made the original proposal 9am morning we had asked folks if they wanted to participate in a separate repository. I don't think a separate repository is the correct approach based upon one off private conversations with folks at summit. Many people fro

Re: [openstack-dev] [kolla][vote][kubernetes][infra] kolla-kubernetes repository management proposal up for vote

On 5/1/16, 1:23 PM, "Ryan Hallisey" wrote: >snip >Trust isn't the issue here. The spec that people signed up for says >"Create kolla-kubernetes repo". > >In this thread there seems to be two votes. One is the split repo >discussion Kolla had at summit. The second is to create kolla-kubernetes.

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

not merge. I'm for separate repo. Keep in mind if we start with a seprate repo we cannot merge it into the main kolla repo without losing git history and it suffers from all the various problems of a separate repo. But also core's are welcome to chime in. Regard -steve On May 1, 201

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

onvince me having these orchesetration engines in separate repos are a good idea. :) Regards -steve > >-Ryan > >- Original Message - >From: "Steven Dake (stdake)" >To: "OpenStack Development Mailing List (not for usage questions)" > >Sent: Sund

[openstack-dev] [kolla] rax-ord misbehaving in the gate

Hey folks, We really need to solve rax-ord in the gate. For awhile it was removed because consistently across openstack this gate jobs were failing. Does anyone have any idea why it is failing in the Kolla case? Thanks -steve __

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

On 5/1/16, 10:32 PM, "Swapnil Kulkarni" wrote: >On Mon, May 2, 2016 at 9:54 AM, Britt Houser (bhouser) > wrote: >> Although it seems I'm in the minority, I am in favor of unified repo. >> >> From: "Steven Dake (stdake)" >> Reply-To: "

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

ing to be focused there? >If most of the code ends up landing there, then its probably not worth >splitting? > >Thanks, >Kevin > >From: Steven Dake (stdake) [std...@cisco.com] >Sent: Monday, May 02, 2016 6:05 AM >To: OpenStack Deve

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

should be done >regardless of if there are 1or 2 repo's in the end. > >Thanks, >Kevin >____ >From: Steven Dake (stdake) [std...@cisco.com] >Sent: Monday, May 02, 2016 11:14 AM >To: OpenStack Development Mailing List (not for usage ques

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

er" wrote: >On Sun, May 1, 2016 at 5:03 PM, Steven Dake (stdake) >wrote: >> I don't think a separate repository is the correct approach based upon >>one >> off private conversations with folks at summit. Many people from that >>list >> approached me

Re: [openstack-dev] [kolla][gate] Add a gating check job for precheck

Hui, I am planning to add a general gating blueprint with work items for the 24 gates we identified. Just g o ahead and get started and I'll have the gate blueprint ready to go by tomorrow. Regards -steve On 5/2/16, 8:41 PM, "Hui Kang" wrote: >Fellow kolla developers, >I am wondering if anyon

Re: [openstack-dev] [kolla][kubernetes] One repo vs two

t;difficult to pull them apart. > >The images, ansible, and k8n need to be separate. The alternative is not >scalable. > >Thanks, >-Paul > >On 03/05/16 00:39, Angus Salkeld wrote: >> On Mon, May 2, 2016 at 7:07 AM Steven Dake (stdake) > <mailto:std...@cisco.com>

Re: [openstack-dev] [Kolla] lock the distro version in the stable branch

From: Jeffrey Zhang mailto:zhang.lei@gmail.com>> Reply-To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, May 3, 2016 at 9:12 AM To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Kolla] l

[openstack-dev] [kolla][kubernetes] kolla-kubernetes underway

Hey folks, There was a majority vote result on the separate repository vote and as a result voting was closed early. We have voted to proceed with a separate repository for kolla-kubernetes. The kolla-kubernetes repository is in progress of creation and being added to the governance reposito

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

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

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

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

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

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

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

Sean, Thanks for taking this on :) I didn't know you had such an AR :) From: "Mooney, Sean K" mailto:sean.k.moo...@intel.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Friday, May 6, 2016 at 10:14 AM To: "OpenStack

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

The reason Kolla works in the gate is it is using the btrfs graph driver. The AUFS graph driver in the 14.04 kernel is busted. This is what the precheck is meant to check. Apparently it needs to also check the graph driver type in use. Regards -steve From: Jeffrey Zhang mailto:zhang.lei@

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

On 5/8/16, 7:55 AM, "Monty Taylor" wrote: >On 05/08/2016 03:45 AM, Steve Kowalik wrote: >> On 08/05/16 08:11, lương hữu tuấn wrote: >>> Hi, >>> >>> @Robert: I was successful to update the kernel without change the >>>image. >> >> But that was Robert's point entirely. Installing the kernel will

Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

Paul, There is no request from the Kolla community to churn the images. I don't see that as adding any value. We can just document the reality of the situation, which is only BTRFS works well as a graph driver with 14.04. Regards -steve On 5/9/16, 10:48 AM, "Paul Belanger" wrote: >On Sun, Ma

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

st (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kolla] [bifrost] bifrost container. On Fri, May 6, 2016 at 10:56 AM, Steven Dake (stdake) mailto:std...@cisco.com>> wrote: Sean, Thanks for taking this on :) I didn't

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

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

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

tel.com<mailto:sean.k.moo...@intel.com>] Sent: Friday, May 06, 2016 12:54 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla] [bifrost] bifrost container. From: Steven Dake (stdake) [mailto:std...@cisco.com] Sent: Friday, May

Re: [openstack-dev] [kolla] CentOS binary and source gate failed due to the rabbitmq

Paul, Please run strace with -f (trace child processes). What you have there is not sufficient to do the job. FWIW erlang -16 is totally busted in CentOS because of logging, and erlang -17 is ready for testing which fixes the erlang crashes. Erlang-15 introduced ipv6 which could also be the cau

Re: [openstack-dev] [kolla] How to contribute to kolla

Hu, I'd recommend joining irc and asking on #openstack-infra. They can help you live debug your connection to gerrit. I have also seen Qiming's response, which may or may not help. Regards -steve From: "hu.zhiji...@zte.com.cn" mailto:hu.zhiji...@zte.com.cn>>

Re: [openstack-dev] [magnum]storage for docker-bootstrap

Adrian, Its a real shame Atomic can't execute its mission - serve as a container operating system. If you need some guidance on image building find experienced developers on #kolla – we have extensive experience in producing containers for various runtime environments focused around OpenStack

[openstack-dev] [kolla] recent MIA from Kolla PTL

Hey folks, Normally I wouldn't talk about health problems on a public mailing list, but its not super private - just teeth problems. I wanted to explain why I have been MIA for 4 weeks. I had a tooth infection, which turned into a root canal, which turned into a failed root canal, which turne

[openstack-dev] [kolla] Mitaka Midcycle scheduling voting

Hey folks, Please vote on the days of the Kolla midcycle you can attend. From that data I will select a date that works best for people that wish to attend the midcycle. Coffee will be provided in the mornings. Soda will be provided all day. Lunch will be provided by Servosity both days (yay th

[openstack-dev] [kolla] Adding Ubuntu Liberty to Kolla-Mitaka

Hey folks, I have received significant feedback that the lack of Ubuntu binary support is a problem for Kolla adoption. Still, we had nobody to do the work, so we held off approving the blueprint. There were other reasons such as: * There is no delorean style repository for debian meaning

Re: [openstack-dev] [kolla] Adding Ubuntu Liberty to Kolla-Mitaka

On 12/29/15, 1:51 AM, "Thomas Goirand" wrote: >On 12/28/2015 05:16 PM, Steven Dake (stdake) wrote: >> Hey folks, >> >> I have received significant feedback that the lack of Ubuntu binary >> support is a problem for Kolla adoption. Still, we had nob

Re: [openstack-dev] [kolla] Mitaka Midcycle scheduling voting

Just a reminder Mitaka Kolla midcycle schedule voting closes January 4th. Please vote on your preferred dates. TIA -steve From: Steven Dake mailto:std...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Sunda

Re: [openstack-dev] [kolla] Adding Ubuntu Liberty to Kolla-Mitaka

On 1/4/16, 3:15 AM, "Thomas Goirand" wrote: >On 01/03/2016 10:45 PM, Sam Yaple wrote: >> That said if you have a link to the project-config patch I will be more >>than >> happy to review it and follow it. > >My point being: I don't even know where to start. I need someone to help >me start it,

[openstack-dev] [kolla] Kolla Midcycle Dates

Hey folks, A heads up the voting is in, and he only date that had no conflicts was (Tuesday) 2/9/16 and (Wednesday) 2/10/16. I would recommend booking flights and hotels asap to cut down on costs. Within 14 days of travel, flight costs increase dramatically which is around January 25th. Lat

Re: [openstack-dev] [kolla] Adding Ubuntu Liberty to Kolla-Mitaka

On 1/5/16, 8:25 AM, "Thomas Goirand" wrote: >On 01/04/2016 06:48 PM, Steven Dake (stdake) wrote: >> Thomas, >> >> Adding a distribution to the gating is a very complex activity and >> requires IIRC a full-time engineer to commit to maintaining the images

[openstack-dev] [kolla] Status of python-kollaclient

Ok folks, this is a bit of bad news, but I'll come out with it. Because of the addition of Mesos at the Mitaka design summit, the main engineers working on the CLI decided they want to wait to provide a unified experience with Mesos and Ansible. Nobody is beating us up for a CLI or ReST API, a

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

Eric, Thanks for using the mailing list for this discussion. I like to see more mailing list conversations on big changes related to kolla, which this one is :) Responses inline. Please put document #3 (the design document) in gerrit rather than google docs in the main kolla repo as a spec using

[openstack-dev] [kolla] Heka v ELK stack logistics

Hey folks, I'd like to have a mailing list discussion about logistics of the ELKSTACK solution that Alicja has sorted out vs the Heka implementation that Eric is proposing. My take on that is Eric wants to replace rsyslog and logstash with Heka. That seems fine, but I want to make certain thi

[openstack-dev] [kolla] Can Heka solve all the deficiencies in the current rsyslog implementation: was Re: [kolla] Introduction of Heka in Kolla

Eric, Apologies for top post, not really sure where in this thread to post this list of questions as its sort of a change in topic so I changed the subject line :) 1. Somewhere I read when researching this Heka topic, that Heka cannot log all details from /dev/log. Some services like mariadb for

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

ary/083916.html David Moreau Simard Senior Software Engineer | Openstack RDO dmsimard = [irc, github, twitter] On Jan 13, 2016 7:20 AM, "Steven Dake (stdake)" mailto:std...@cisco.com>> wrote: Hey folks, I'd like to have a mailing list discussion about logistics of the ELKSTAC

[openstack-dev] [kolla] Please vote -> Removal of Harm Weites from the core reviewer team

Hi fellow core reviewers, Harm joined Kolla early on with great enthusiasm and did a bang-up job for several months working on Kolla. We voted unanimously to add him to the core team. Over the last 6 months Harm hasn't really made much contribution to Kolla. I have spoken to him about it in

Re: [openstack-dev] [kolla] Can Heka solve all the deficiencies in the current rsyslog implementation: was Re: [kolla] Introduction of Heka in Kolla

Eric, Comments inline. On 1/14/16, 3:31 AM, "Eric LEMOINE" wrote: >On Wed, Jan 13, 2016 at 1:27 PM, Steven Dake (stdake) >wrote: >> Eric, > > >Hi Steven Feel free to call me Steve > > >> >> Apologies for top post, not really sure where in t

Re: [openstack-dev] [kolla] kolla-mesos IRC meeting

I am -2 on a separate meeting. If there are problems with the current approach to how the agenda is managed as it relates to mesos topics, lets fix that. If there are timezone problems, lets try to fix that. Lets fix the problems you point out rather then create another meeting for our core team

Re: [openstack-dev] [kolla] Please vote -> Removal of Harm Weites from the core reviewer team

I counted 6 votes in favor of removal. We have 10 people on our core team. A majority has been met and I have removed Harm from the core reviewer team. Harm, Thanks again for your helpful reviews and remember, your always welcome back in the future if your availability changes. For the recor

Re: [openstack-dev] [kolla] kolla-mesos IRC meeting

Ryan, I read your response and the idea of incubators is interesting, but the risk there is we will end up with "two core teams" with different objectives, purpose, focus, and most importantly a lack of coordinated efforts and thinking. I'd like to experiment with converting two of our meetings t

[openstack-dev] Closing voting for midcycle agenda on January 25th

On January 25th, I will finalize the agenda for the Kolla midcycle based upon voting in the midcycle agenda document. Feel free to vote, even if your not a core reviewer, on any particular topic (either vote +1, or +0). A +0 vote will be helpful when I craft the agenda to show me that you did

[openstack-dev] [kolla] Please Vote - Closing voting January 25th for Kolla Midcycle Event

On January 25th, I will finalize the agenda for the Kolla midcycle based upon voting in the midcycle agenda etherpad. Feel free to vote, even if your not a core reviewer, on any particular topic (either vote +1, or +0). A +0 vote will be helpful when I craft the agenda to show me that you did

Re: [openstack-dev] [kolla] Heka POC

Eric, One request. Please convert the google doc at your earliest convience into a spec, because we require majority approval of all specs, and it takes awhile to get specs merged. If you can get specs in, the review process can begin earlier rather then later :) Thanks! -steve On 1/18/16, 8:0

[openstack-dev] [kolla] Nominating Lei Zhang (Jeffrey Zhang in English) - jeffrey4l on irc

Hi folks, I would like to propose Lei Zhang for our core reviewer team. Count this proposal as a +1 vote from me. Lei has done a fantastic job in his reviews over the last 6 weeks and has managed to produce some really nice implementation work along the way. He participates in IRC regularly,

[openstack-dev] [kolla] US/APAC meeting scheduling

Please vote on every time slot you can make on Wednesdays on a recurring basis. I will give preference to the time slots to the folks in APAC since this meeting is targeted at including those folks. I'll leave polling open for 1 week until January 27th. EMEA, apologies, you won't be able to m

[openstack-dev] [kolla] Kolla Midcycle February 9th, 10th please RSVP via Eventbrite

Hello folks, If your attending the Kolla midcycle please RSVP via eventbrite. If your a core reviewer and won't be able to make it, would you do me a solid and send me your regrets either via email or an irc message so I know how many folks to expect? Breakfast, lunch and dinner will be provi

Re: [openstack-dev] [kolla] Nominating Lei Zhang (Jeffrey Zhang in English) - jeffrey4l on irc

Lei, Looks like its unanimous in under 24 hours :) Welcome to the Kolla core reviewer team! I made the appropriate changes in gerrit. Regards -steve From: Steven Dake mailto:std...@cisco.com>> Reply-To: "openstack-dev@lists.openstack.org" mailto:op

[openstack-dev] [kolla] 40 hour time commitment requested from core reviewers before Feb 9th/10th midcycle

Hello, In our weekly IRC meeting, all developers and others in attendance were in unanimous agreement that upgrades are the #1 priority for Kolla to solve [1]. inc0 has developed both a simple database migration implementation around keystone [2] as well as a more complex playbook around nova

[openstack-dev] [kolla] interesting development work which isn't extremely complex for new developers

Hi folks, We have had tremendous activity on the drop-root blueprint here: https://blueprints.launchpad.net/kolla/+spec/drop-root Unfortunately the work didn't finish in mitaka-2. There are 5 TODO items left. These are services which need to be securified. There is a significant example work

Re: [openstack-dev] [kolla] 40 hour time commitment requested from core reviewers before Feb 9th/10th midcycle

On 1/26/16, 8:35 AM, "Michał Dulko" wrote: >On 01/26/2016 10:11 AM, Michał Jastrzębski wrote: >> Well we still can perform upgrades with some API downtime, so it's not >> like we're bound to rolling upgrades on architectural level. I'll talk >> to you after midcycle and we'll find a good way to

[openstack-dev] [kolla] Need 5 more Core Reviewer volunteers for upgrades!

Looking for 5 more core reviewers to step forward and take on an OpenStack service and a infrastructure service prior to the midcycle. If you can't finish the openstack service in time and get it merged, that's ok - please just get a patch in the review queue with your work. For the infrastruct

[openstack-dev] [announce][kolla] Announcing Kolla Mitaka 2 availability

The Kolla community is pleased to announce the release of Mitaka milestone #2. We did not announce the release of Mitaka-1 because the PTL was unavailable to tag the release. As a result, we are announcing changes that also occured in the Mitaka-1 tag here. For further releases of Kolla, we h

Re: [openstack-dev] Announcing Ekko -- Scalable block-based backup for OpenStack

On 1/27/16, 12:06 PM, "Flavio Percoco" wrote: >On 27/01/16 12:16 -0500, Emilien Macchi wrote: >> >> >>On 01/27/2016 10:51 AM, Jay Pipes wrote: >>> On 01/27/2016 12:53 PM, gordon chung wrote: > It makes for a crappy user experience. Crappier than the crappy user > experience that OpenSta

Re: [openstack-dev] [Magnum] Bug 1541105 options

Steve, Comments inline On 2/3/16, 3:08 PM, "Steve Gordon" wrote: >- Original Message - >> From: "Hongbin Lu" >> To: "OpenStack Development Mailing List (not for usage questions)" >> >> >> I would vote for a quick fix + a blueprint. >> >> BTW, I think it is a general consensus that we

[openstack-dev] [kolla][midcycle] last notification regarding Kolla Midcycle February 9th and February 10th

Hey folks, The Kolla midcycle is prepared for next week Tuesday February 9th 9:00 am - 5:00 pm and Wednesday February 10th 9:00 am - 3:30 pm. Breakfast, lunch, coffee, soda, water are provided both days, and dinner is provided Tuesday evening. The sprint wiki page is available here: https://wi

Re: [openstack-dev] [kolla] Location of Heka Lua plugins

I agree with Michael. If the LUA plugins are going to be a separate repository, they need to be in the OpenStack git namespace. I am +2 to the idea assuming after extraction of the LUA plugins they hit the OpenStack git namespace. Regards -steve On 2/4/16, 7:22 AM, "Michał Jastrzębski" wrote:

Re: [openstack-dev] [kolla] Location of Heka Lua plugins

On 2/5/16, 1:14 AM, "Eric LEMOINE" wrote: >On Thu, Feb 4, 2016 at 5:13 PM, Jeff Peeler wrote: >> On Thu, Feb 4, 2016 at 9:22 AM, Michał Jastrzębski >>wrote: >>> TLDR; +1 to have lua in tree of kolla, not sure if we want to switch >>>later >>> >>> So I'm not so sure about switching. If these g

Re: [openstack-dev] [Magnum] Bug 1541105 options

Sorry for 1 day delay in response - busy prepping for Kolla midcycle next week. Responses inline. On 2/5/16, 12:14 PM, "Steve Gordon" wrote: >- Original Message ----- >> From: "Steven Dake (stdake)" >> To: "OpenStack Development Mailing List (n

[openstack-dev] [kolla] pid=host

Hey folks, I know we have been through some changes with how pid=host works. I'd like to get to the bottom of this, so we can either add the features we need to docker, or say "all is good". Here is the last quote from this bugzilla where Red Hat in general is interested in the same behavior

Re: [openstack-dev] [kolla] Location of Heka Lua plugins

estions)" mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kolla] Location of Heka Lua plugins Le 6 févr. 2016 20:39, "Steven Dake (stdake)" mailto:std...@cisco.com>> a écrit : > > > > On 2/5/16, 1:14 AM, "Eric LEMOINE"

Re: [openstack-dev] [kolla] pid=host

m > >Cheers, >Michal > >On 8 February 2016 at 07:32, Steven Dake (stdake) >wrote: >> Hey folks, >> >> I know we have been through some changes with how pid=host works. I'd >>like >> to get to the bottom of this, so we can either add the features we

[openstack-dev] Proposed Agenda for Kolla Midcycle

Hey folks, The agenda generation happened approximately a month ago over a 3 week period, and then was voted on. I left the actual creation of the agenda until today in case any last minute pressing issues came in. I took some suggestions from the copious notes in the Etherpad regarding pair p

[openstack-dev] Midcycle today and tomorrow

Reminder, The kolla midcycle begins today at 10:00 AM but breakfast will be available (bagels, coffee) at 9:00 AM. This is an opportunity for folks to visit with other community members and get brain juices flowing :) Tomorrow we are starting pretty early, with breakfast at 9:00 AM and first

<    1   2   3   4   5   6   7   8   >