[openstack-dev] [kolla] Google Hangouts discussion for dueling specifications for Dockerfile customization

Hey folks, IRC and mailing list were going far too slow for us to make progress on the competing specifications for handling Dockerfile customization. Instead we held a hangout, which I don't like because it isn't recorded, but it is high bandwidth and permitted us to work through the problem

[openstack-dev] [tc][security] Item #5 of the VMT

Hi folks, I think we are nearly done with Item #5 [1] of the VMT. One question remains. We need to know which repo the analysis documentation will land in . There is security-doc we could use for this purpose, but we could also create a new repository called "security-analysis" (or open to

Re: [openstack-dev] [kolla] OSIC cluster accepteed

Michal, Great news. Just as a followup, the midcycle is scheduled for the 12th and 13th of July. I am working on the eventbrite page today, but the initial information is here: https://wiki.openstack.org/wiki/Sprints#Newton_sprints Unlike last midcycles, there is no vote on the date this time

Re: [openstack-dev] [tc][security] Item #5 of the VMT

ppy with your proposal Steve, kind of you to do the leg-work. -rob On Fri, Jun 3, 2016 at 1:29 AM, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote: Hi folks, I think we are nearly done with Item #5 [1] of the VMT. One question remains. We need to know which re

Re: [openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [Kolla] About kolla-ansible reconfigure

cluster shutdown followed by a full cluster start. This would require adding a stop operation. Deploy already starts containers for us. Regards -steve 发件人: "Steven Dake (stdake)" <std...@cisco.com<mailto:std...@cisco.com>> 收件人: "openstack-de

Re: [openstack-dev] [kolla] Request for changing the meeting time to 1600 UTC for all meetings

Swapnil, Thanks for triggering this community vote. It was sorely overdue :). I counted 8 votes before I voted (I am all for moving everything to 1600UTC) which is a majority of the CR team. Note in the future I think we may need to consider having split meetings again, if our community makeup

Re: [openstack-dev] [kolla] Google Hangouts discussion for dueling specifications for Dockerfile customization

oncerns with recording the Hangouts meetings, we may try to run Zoom for that. On Fri, Jun 3, 2016 at 3:50 AM, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote: Hey folks, IRC and mailing list were going far too slow for us to make progress on the competing spe

Re: [openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [Kolla] About kolla-ansible reconfigure

th reconfiguring globals.yml. I'm not quite sure how it could sanely be implemented without a full cluster shutdown followed by a full cluster start. This would require adding a stop operation. Deploy already starts containers for us. Regards -steve 发件人: "Steven Dake (std

Re: [openstack-dev] [kolla][security] Finishing the job on threat analysis for Kolla

5:37 PM, Chivers, Doug <doug.chiv...@hpe.com<mailto:doug.chiv...@hpe.com>> wrote: Thanks for following up Steve, the sessions at the summit were extremely useful. Both Rob and I have been caught up with the day-job since we got back from the summit, but will discuss next s

[openstack-dev] [kolla] reclaimed the kolla namespace on docker

Hey folks, Kuan Yi Ming @ Docker helped us reclaim the kolla namespace for our images. If you are a core reviewer and would like access to push to the docker hub in the kolla namespace, please send me your email address offline with your interest. Thanks -steve

Re: [openstack-dev] [kolla] stepping down from core

Jeff, Thanks for the notification. Likewise it has been a pleasure working with you over the last 3 years on Kolla. I've removed you from gerrit. You have made a big impact on Kolla. For folks that don't know, at one point Kolla was nearly dead, and Jeff was one of our team of 3 that stuck to

Re: [openstack-dev] [TripleO][Kolla][Heat][Higgins][Magnum][Kuryr] Gap analysis: Heat as a k8s orchestrator

Hongbin, Re Netowrk coverage, he is talking about the best practice way to deploy an OpenStack cloud. I have a diagram here: http://www.gliffy.com/go/publish/10486755 I think what Zane is getting that network Diagram above to magically map into Kubernetes is not possible at present and may not

Re: [openstack-dev] [TripleO][Kolla][Heat][Higgins][Magnum][Kuryr] Gap analysis: Heat as a k8s orchestrator

Quick question below. On 5/28/16, 1:16 PM, "Hongbin Lu" wrote: > > >> -Original Message- >> From: Zane Bitter [mailto:zbit...@redhat.com] >> Sent: May-27-16 6:31 PM >> To: OpenStack Development Mailing List >> Subject: [openstack-dev]

Re: [openstack-dev] [kolla] prototype of a DSL for generating Dockerfiles

>On 5/27/16, 1:58 AM, "Steven Dake (stdake)" <std...@cisco.com> wrote: > >> >> >>On 5/26/16, 8:45 PM, "Swapnil Kulkarni (coolsvap)" <m...@coolsvap.net> >>wrote: >> >>>On Fri, May 27, 2016 at 8:35 AM, Steven Dake (std

[openstack-dev] [kolla] Cross project spec liason

Fellow core reviewers, I have a lot of liasing to do as a PTL and would like to offload some of it so I can get some actual sleep :) Are there any takers on Mike's requirement for a cross-project liason for Kolla? The job involves reviewing all specs in the cross project spec repository and

Re: [openstack-dev] [kolla] prototype of a DSL for generating Dockerfiles

ake a >arch-changing call. Can you make a specification please as you have asked me to do? > >On 29 May 2016 at 14:41, Steven Dake (stdake) <std...@cisco.com> wrote: >> >>>On 5/27/16, 1:58 AM, "Steven Dake (stdake)" <std...@cisco.com> wrote:

[openstack-dev] [kolla] Ansible 2.0.0 functional

Hey folks, In case you haven't been watching the review queue, Kolla has been ported to Ansible 2.0. It does not work with Ansible 2.1, however. Regards, -steve __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [kolla] prototype of a DSL for generating Dockerfiles

On 5/26/16, 8:45 PM, "Swapnil Kulkarni (coolsvap)" <m...@coolsvap.net> wrote: >On Fri, May 27, 2016 at 8:35 AM, Steven Dake (stdake) <std...@cisco.com> >wrote: >> Hey folks, >> >> While Swapnil has been busy churning the dockerfile.j2 files to

[openstack-dev] [kolla] prototype of a DSL for generating Dockerfiles

Hey folks, While Swapnil has been busy churning the dockerfile.j2 files to all match the same style, and we also had summit where we declared we would solve the plugin problem, I have decided to begin work on a DSL prototype. Here are the problems I want to solve in order of importance by this

Re: [openstack-dev] [kolla] Stability and reliability of gate jobs

David, The gates are unreliable for a variety of reasons - some we can fix - some we can't directly. RDO rabbitmq introduced IPv6 support to erlang, which caused our gate reliably to drop dramatically. Prior to this change, our gate was running 95% reliability or better - assuming the code

[openstack-dev] [kolla] Need help from all core reviewers

Hey folks, We have a spec under review for Kolla + Kubernetes, which has been cooking for 6-8 weeks. The specification may have some gaps, but it gives a solid feeling to me atleast the work is achievable. Note specifications are point in time plans and are never revised in the repository.

[openstack-dev] [tc] Re: [fuel] [kolla] Containerized OpenStack on Kubernetes experimental project proposal

Kevin, Why have one snowflake when you can have two? Snarky comments aside :) Sergey did answer that question in the specification he linked (rest quoted): " Alternatives This spec is actually describes an alternative experimental approach for OpenStack deployment,

Re: [openstack-dev] [tc] Re: [fuel] [kolla] Containerized OpenStack on Kubernetes experimental project proposal

On 6/17/16, 11:38 AM, "Jeremy Stanley" <fu...@yuggoth.org> wrote: >On 2016-06-17 18:04:25 +0000 (+0000), Steven Dake (stdake) wrote: >[...] >> The technical committee has set precedent that competition is >> acceptable in the "outer ring" of se

[openstack-dev] [kolla] our 3 voting processes in detail

Hey core reviewers, I was speaking with one of the core reviewers of Kolla today who said "only you can nominate people for core reviewer". By you, he meant me :) This is absolutely not true and I'd like to set the record straight on our three voting processes we have developed over the last

Re: [openstack-dev] [kolla] our 3 voting processes in detail

Thanks for the suggestion. I think it merits further work to write our policies down in git. I wanted to get this out a little more quickly since these are our foundational policies and there is some confusion among the cores about them - even though we have been using them for the better part

Re: [openstack-dev] [magnum] 2 million requests / sec, 100s of nodes

Ricardo, As one of the original authors of Magnum, I'm super pleased to hear Magnum works at this scale with a kubernetes bay. I don't think it would have done that when I finished working on Magnum - a testament to the great community around Magnum. Regards -steve From: Ton Ngo

Re: [openstack-dev] [OpenStack-Infra] Upcoming changes now that Jenkins has retired

On 6/16/16, 6:13 PM, "James E. Blair" wrote: >Now that we have retired Jenkins, we have some upcoming changes: > >* Console logs are now available via TCP > > The status page now has "telnet" protocol links to running jobs. If > you connect to the host and port

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

Looks like a really cool feature, and possibly a way to non-ini files, such as policy.json files which we just want to copy rather then override. Kolla already has ini merging for ini files though and the example you provide is an ini file. I like Kolla's ini merging, and it is sort of an

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

I looked more at this solution and am struggling to come up with a solution for: https://github.com/openstack/kolla/blob/master/ansible/roles/nova/tasks/config.yml#L69-L85 That doesn't involve creating

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

Hey folks, I created the following sequence diagram to show my thinking on Ironic integration. I recognize some internals of the recently merged bifrost changes are not represented in this diagram. I would like to see a bootstrap action do all of the necessary things to bring up BiFrost in a

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

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

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

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" <elemo...@mirantis.com> wrote: >On Wed, Jan 13, 2016 at 1:27 PM, Steven Dake (stdake) <std...@cisco.com> >wrote: >> Eric, > > >Hi Steven Feel free to call me Steve > > &g

[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

[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

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,

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

t; is ambiguous. Ironic >does >not currently support notifications, so, to learn the status of the >deployments, >you will need to poll the Ironic API (eg, "ironic node-list"). > Great, Thanks for the feedback. I'll integrate your changes into the sequence diagram when I have a

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

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" <sgor...@redhat.com> wrote: >- Original Message ----- >> From: "Steven Dake (stdake)" <std...@cisco.com> &

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

show running vm > >Cheers, >Michal > >On 8 February 2016 at 07:32, Steven Dake (stdake) <std...@cisco.com> >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 th

[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

[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

2:39 AM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<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)"

[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

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

ifferent one. And whether or not it is actually >broken. > >On 02/08/2016 10:53 PM, Steven Dake (stdake) wrote: >> Michal, >> >> You listed steps to reproduce but it wasn't clear if docker 1.10 kills >>vms >> or keeps them alive from your description. From our d

Re: [openstack-dev] [infra][keystone][kolla][bandit] linters jobs

Andreas, Totally understand the overload problem with no short-term workarounds. I think all engineering in OpenStack is over capacity a bit and folks are really burning the midnight oil to make sure Mitaka is the best release of OpenStack yet! Please feel free to drop by #kolla and ping the

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"

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

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 >

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

Re: [openstack-dev] [kolla][infra] Publishing kolla images to docker-registry.openstack.org

ace, >> do you have an estimate of storage needed? >> >> Regards >> >> 2016-02-20 14:21 GMT+01:00 Steven Dake (stdake) <std...@cisco.com>: >>> >>> Infra folks, >>> >>> I'd like to see a full CI/CD pipeline of Kolla to an OpenSt

[openstack-dev] [kolla] New Meeting Times altrernating 16:30 and 23; 00 UTC.

Hey folks, We agreed some time ago to be more inclusive and have an APAC/US meeting. I am happy to announce that work has completed. Please see: http://eavesdrop.openstack.org/#Kolla_Team_Meeting >From there you can download an ical file which will insert directly into your >calendar for

Re: [openstack-dev] [kolla][infra] Publishing kolla images to docker-registry.openstack.org

it needs to be injected into our post jobs without us having to check our credentials into the repository. Regards -steve On 2/23/16, 9:58 AM, "Steven Dake (stdake)" <std...@cisco.com> wrote: >Ricardo, > >Apologies in lag, I remember reading your email but not answerin

Re: [openstack-dev] [kolla] New Meeting Times altrernating 16:30 and 23; 00 UTC.

> in #openstack-meeting-4 (IRC webclient<https://webchat.freenode.net/?randomnick=1=%23openstack-meeting-4=1=d4>) On Wed, Feb 24, 2016 at 8:50 PM, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote: Hey folks, We agreed some time ago to be more inclusiv

Re: [openstack-dev] [kolla][vote] port neutron thin containers to stable/liberty

Hi folks, I thought long and hard as how to not make this an exception and came up with the following. I would be in favor (+1) of this particular feature addition, on the conditions that: 1. This does not set a precedent that features will be backported by the typical +2/+2/+W 2. Any

Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company

1:13 AM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company Le 20 févr. 2016 18:

Re: [openstack-dev] [kolla][vote] Proposing Angus Salkeld for kolla-core

Angus, You received 7 +1 votes with no veto votes in the voting window and we require 6 votes or more to join the core team at the time you were proposed. As a result, I have removed you from kolla-mesos-core and added you to kolla-core. Welcome to the core reviewer team! Regards -steve

[openstack-dev] [kolla] unblocking the gate

Hey folks, It should be obvious that commiters should be testing their changes, but unfortunately this is not always the case. With the recent state of the gate relating to the introduction of Docker 1.10.z breaking the gate for 1 week followed by a keystone change upstream breaking the gate

Re: [openstack-dev] [kolla] unblocking the gate

The gate is still blocked apparently by yet another gate-breaking regression. That regression is resolved in this change set: https://review.openstack.org/#/c/285875/ Please rebase once that hits green and hits the repository. From: Steven Dake >

Re: [openstack-dev] [kolla] unblocking the gate

On 2/29/16, 12:26 AM, "Andreas Jaeger" <a...@suse.com> wrote: >On 2016-02-29 06:59, Steven Dake (stdake) wrote: >> Hey folks, >> >> It should be obvious that commiters should be testing their changes, but >> unfortunately this is not always the

Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company

On 2/22/16, 10:13 AM, "Jeff Peeler" <jpee...@redhat.com> wrote: >On Mon, Feb 22, 2016 at 9:07 AM, Steven Dake (stdake) <std...@cisco.com> >wrote: >> The issue isn't about reviewing patches in my opinion. Obviously people >> shouldn't jam patches

[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

[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

[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

[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

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 > Reply-To:

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

[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

[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

[openstack-dev] [kolla] Decision of how to manage stable/liberty from Kolla Midcycle

Hey folks, We held a midcycle Feb 9th and 10th. The full notes of the midcycle are here: https://etherpad.openstack.org/p/kolla-mitaka-midcycle We had 3 separate ~40 minute sessions on making stable stable. The reason for so many sessions on this topic were that it took a long time to come to

Re: [openstack-dev] [kolla] Decision of how to manage stable/liberty from Kolla Midcycle

ct: Re: [openstack-dev] [kolla] Decision of how to manage stable/liberty from Kolla Midcycle On Tue, Feb 16, 2016 at 6:15 PM, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote: Hey folks, We held a midcycle Feb 9th and 10th. The full notes of the midcycle are her

[openstack-dev] [kolla][infra] Re: Patch submission for Kolla

Sebastien, Cool that will be a nice feature :) I recommend contacting #openstack-infra on irc with your question. They are the folks that can get this solved for you. Note I think the best way to update contact information is to login to openstack.org, and fill out your contact information

[openstack-dev] [kolla][vote] Proposing Angus Salkeld for kolla-core

Angus is already in kolla-mesos-core but doesn't have broad ability to approve changes for all of kolla-core. We agreed by majority vote in Tokyo that folks in kolla-mesos-core that integrated well with the project would be moved from kolla-mesos-core to kolla-core. Once kolla-mesos-core is

[openstack-dev] [kolla] Adding folks to the core team

I was asked if anyone can propose someone for the core reviewer team, and the answer is absolutely yes. Any core reviewer can trigger a vote by using the [vote] tag in an email for anything related to project policy (core reviewers fall into this category). The vote must be majority (except

[openstack-dev] [kolla][infra] Publishing kolla images to docker-registry.openstack.org

Infra folks, I'd like to see a full CI/CD pipeline of Kolla to an OpenStack infrastructure hosted registry. With docker registry 2.2 and earlier a Docker push of Kolla containers took 5-10 hours. This is because of design problems in Docker which made a push each layer of each Docker image

[openstack-dev] [kolla][vote] port neutron thin containers to stable/liberty

Folks, There were not enough core reviewers to pass a majority approval of the neutron thin container backport idea, so we separated it out from fixing stable/liberty itself. I am going to keep voting open for *2* weeks this time. The reason for the two weeks is I would like a week of

Re: [openstack-dev] [kolla][vote] port neutron thin containers to stable/liberty

From: Steven Dake > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Saturday, February 20, 2016 at 6:28 AM To: "OpenStack Development Mailing

Re: [openstack-dev] [kolla][vote] port neutron thin containers to stable/liberty

Just clarifying, this is not a "revote" - there were not enough core reviewers in favor of this idea at the Kolla midcycle, so we need to have a vote on the mailing list to sort out this policy decision of managing stable/liberty. Regards, -steve From: Steven Dake

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

Michal, I want to make sure we fix all of the problems, not just the timezone issue (which in progress by the apac friendly meeting). On 1/15/16, 4:38 AM, "Michal Rostecki" wrote: >Hi, > >Currently we're discussing stuff about kolla-mesos project on kolla IRC

Re: [openstack-dev] [kolla]

Wade, My guess is you have six installed via both pip and RPM and they are different versions. If you want help, join us on irc on #freenode, and we can get you going. Its much faster then debugging over a mailing list. Regards -steve From: Wade Holler

[openstack-dev] [kolla] Metting schedule changes - next IRC meeting at 16:30 UTC!

Hi folks, With this review[1] our meeting times have been changed as follows based upon a community vote[2] of the best US/APAC time: Our US/EMEA meeting time remains unchanged. We don't have a EMEA/APAC meeting because there is not enough core reviewers to hold such a meeting. Even work

Re: [openstack-dev] [kolla][vote] port neutron thin containers to stable/liberty

these nice stuff, I'd be happier person;) Cheers, Michal On 20 February 2016 at 07:40, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote: > Just clarifying, this is not a "revote" - there were not enough core > reviewers in favor of this idea at the K

[openstack-dev] [kolla] discussion about core reviewer limitations by company

Hey folks, Mirantis has been developing a big footprint in the core review team, and Red Hat already has a big footprint in the core review team. These are all good things, but I want to avoid in the future a situation in which one company has a majority of core reviewers. Since core

Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company

2 cores from the same company cannot +2 the same patch, but again i am against such things personally.. Disclaimer: i am not personally involved in Kolla or know how things are running there. On Sat, Feb 20, 2016 at 7:09 PM, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>

Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company

following: * the union of the memberships of the core review teams associated with the git repositories managed by the team > >I will show myself out now, ha. > >-Josh > >On 02/20/2016 09:09 AM, Steven Dake (stdake) wrote: >> Hey folks, >> >> Mirantis

Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company

lt;openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kolla] discussion about core reviewer limitations by company On 20 February 2016 at 12:58, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote

[openstack-dev] [magnum] Re: Assistance with Magnum Setup

Shiva, First off, welcome to OpenStack :) Feel free to call me Steve. Ccing openstack-dev which is typically about development questions not usage questions, but you might have found some kind of bug. I am not sure what the state of Magnum and Keystone is with OpenStack. I recall at our

Re: [openstack-dev] [kolla][security] Obtaining the vulnerability:managed tag

e responsive about private >security bug to confirm the issue and discuss the scope of any >vulnerability along with potential solutions. > > > >> Thanks, >> -Ryan >> >> - Original Message - >> From: "Steven Dake (stdake)" <std...@cisc

Re: [openstack-dev] [kolla][security] Obtaining the vulnerability:managed tag

ith vulnerability management process of Kolla and become a member of Kolla VMT team. I have experience and expertise in IT security and related to it processes. Best regards, Adam On Tue, Mar 1, 2016 at 5:55 PM, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wro

Re: [openstack-dev] [kolla] [infra] Size of images built in the gate

.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kolla] [infra] Size of images built in the gate Steve, overlayfs does not reduce the disk usage at all Paul, we can bump the size of the docker mountpoint up to ~20GB if you check all the gates for the approp

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

the choice. Such criteria will be subject to community consensus. This should allow for free experimentation with alternates to allow for innovation. See how this is not locking in a single OS vendor? Adrian On Mar 14, 2016, at 12:41 PM, Steven Dake (stdake) <std...@cisco.com<mailto:std.

[openstack-dev] [kolla][security][tc] Next steps for Kolla vulnerability:managed tag

The Technical Committee, Please see this review which offers threat analysis as an option for the vulnerability:managed tag: https://review.openstack.org/#/c/294212/ Kolla coresec team: In this IRC meeting on Security, I requested an audit, and the security team came back with a threat

Re: [openstack-dev] [kolla] [infra] Size of images built in the gate

Vikarm, /var/lib/docker is a btrfs filesystem. It would be nice to just use overlayfs as it doesn't take nearly as much disk space and is much faster then btrfs. I use overlay daily and it works like a champ unless I want to rebuild, in which case I think a bug in the ovl yum plugin prevents

Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro

awei.com>> wrote: From: Adrian Otto [mailto:adrian.o...@rackspace.com<mailto:adrian.o...@rackspace.com>] Sent: March-04-16 6:31 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Discussion of supporting single/multiple OS distro St

[openstack-dev] [kolla] Mitaka release schedules and priorities - only 30 days left!

Hi Koala Bears! The release candidate schedules are as follows: We are in feature freeze. No new features in Kolla until after Mitaka is released on April 4th-April 8th. We may lag this date a little bit depending on the state of the tarballs repo for build from source, or we may just tag

[openstack-dev] [kolla][release] Announcing Kolla Mitaka-3 milestone release \o/

Fellow OpenStackers, The Kolla community is pleased to announce the release of Mitaka milestone #3. Angus Salkeld has agreed to be our release manager for the kolla-mesos repository. As an aside, we held our midcycle during mitaka-3 development, for which the notes can be found here:

[openstack-dev] [kolla][release] Announcement of release of Mitaka rc1!

The Kolla community is pleased to announce the release of Mitaka milestone RC1. This may look like a large list of features, but really it was finishing the job on 1 or 2 services that were missing for each of our major blueprints for Mitaka. Mitaka RC1 Features: * MariaDB lights out

<    1   2   3   4   5   6   7   8   >