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

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

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

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

[openstack-dev] [kolla] Patches needing review

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Michal and Angus, Thanks a bunch for stepping down gracefully as your personal interests have changed to focus on k8s upstream. We were glad to have you and will be happy to have you on our team in the future if things change for you. Regards, -steve On 7/8/16, 1:01 AM, "Michal Rostecki"

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

On 7/6/16, 5:50 PM, "Paul Belanger" <pabelan...@redhat.com> wrote: >On Thu, Jun 16, 2016 at 12:20:06PM +, Steven Dake (stdake) wrote: >> David, >> >> The gates are unreliable for a variety of reasons - some we can fix - >>some >> we ca

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

a, I hope >you can at least consider my feedback and you can also find me on IRC >if you have questions. > >[1]: https://github.com/openstack/packstack#packstack-integration-tests >[2]: https://github.com/openstack/puppet-openstack-integration#description > >David More

Re: [openstack-dev] 答复: [probably forge email可能是仿冒邮件]Re: [daisycloud-core] [kolla] Kolla Mitakarequirementssupported by CentOS

kolla, but sometimes that is not necessary for OpenStack installers. 发件人: "Steven Dake (stdake)" <std...@cisco.com<mailto:std...@cisco.com>> 收件人: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<

Re: [openstack-dev] [Kolla] [docker] Storage-driver and loopback usage?

Actually our documentation recommends AUFS on Ubuntu and BTRFS on CentOS. See: http://docs.oenstack.org/developer/kolla/operating-kolla.html Search for BTRFS. From: Jeffrey Zhang

Re: [openstack-dev] OpenStack Kolla - External Ceph

Matthias, Copying the response to the mailing list since this is all technical in nature and I don't have all the answers. From: Mathias Ewald <mew...@evoila.de<mailto:mew...@evoila.de>> Date: Sunday, July 3, 2016 at 12:19 PM To: Steven Dake <std...@cisco.com<mailto:std...@c

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

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

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

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

Re: [openstack-dev] [kolla][vote] Apply for release:managed tag

On 6/30/16, 8:26 PM, "Tony Breeds" <t...@bakeyournoodle.com> wrote: >On Fri, Jul 01, 2016 at 12:56:09AM +, Steven Dake (stdake) wrote: >> Hey folks, >> >> I'd like the release management team to take on releases of Kolla. This >> means applying f

[openstack-dev] [kolla][vote] Apply for release:managed tag

Hey folks, I'd like the release management team to take on releases of Kolla. This means applying for the release:managed[1] tag. Please vote +1 if you wish to proceed, or -1 if you don't wish to proceed. The most complex part of this change will be that when feature freeze happens, we must

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

On 6/30/16, 10:22 AM, "Jeremy Stanley" <fu...@yuggoth.org> wrote: >On 2016-06-30 14:07:53 +0000 (+), Steven Dake (stdake) wrote: >[...] >> If it does have some special meaning or requirements beyond the >> "we will freeze on the freeze dea

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

Hey folks, I am keen on tagging Kolla in the governance repository with every tag that is applicable to our project. One of these is release:managed. I've been working as PTL the last 3 cycles to get Kolla processes to the point we could apply for release:managed. Looks like Doug and

Re: [openstack-dev] [kolla] Continued support of Fedora as a base platform

What really cratered our implementation of fedora was the introduction of DNF. Prior to that, we led with Fedora. I switched my focus to something slower moving (CentOS) so I could focus on a properly working RDO rather then working around the latest and greatest changes. That said, if someone

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

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

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

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

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

The mitaka branch of Kolla requires 3.7 or later. Git checkout stable/mitaka Master may require 3.10, but that happens via the global requirements update process, of which RDO will surely address in the future.

[openstack-dev] [kolla] Usage of Reno - all devs please read

Hey folks, We have had reno in place since the end of Mitaka, yet folks aren't using it very often. I am guilty myself of not thinking of it when reviewing changes. Core reviewers: Please -1 any review of significant work that doesn't include a reno release note. Developers: If you have made

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

[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] better solution for the non-ini format configure file

eating a task per file. Any ideas? Regards -steve From: Steven Dake <std...@cisco.com<mailto:std...@cisco.com>> Reply-To: "openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@li

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

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

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

[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] [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] [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 (+), Steven Dake (stdake) wrote: >[...] >> The technical committee has set precedent that competition is >> acceptable in the "outer ring" of se

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

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

6 at 1:34 AM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Cc: Steven Dake <std...@cisco.com<mailto:std...@cisco.com>>, "robcl...@uk.ibm.com<mailto:ro

[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] 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] 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] 答复: [probably forge email可能是仿冒邮件]Re: [Kolla] About kolla-ansible reconfigure

case, the implementation requires lots of experimentation on each variable to permit changes. I'm not certain in what development cycle that work will begin or end. It definitely wont be backported as its a feature. Regards -steve From: Steven Dake <std...@cisco.com<mailto:std...@cis

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

[openstack-dev] [security][infra][tc] security-analysis repo needs +1 from Robert to be merged by Infrastructure

Robert, The infrastructure team will only merge new repos that are going into big tent repositories if the PTL +1s it (as in takes responsibility for it). The review is here: https://review.openstack.org/#/c/325049/ If you click through, the needs-by you will see how it relates to the VMT

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

[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] [magnum] Discuss the idea of manually managing the bay nodes

Hongbin, Have you considered a workflow engine? FWIW I agree with Adrian about the difficulties of heterogenous systems. Much better to operate, and in reality the world has moved entirely to x86_64 + Linux. I could see a future in which ARM breaks into the server space, but that is multiple

Re: [openstack-dev] [Kolla] About kolla-ansible reconfigure

Hu, Reconfigure was not designed to handle changes to globals.yml. I think its a good goal that it should be able to do so, but it does not today. Reconfigure was designed to handle changes to /etc/kolla/config/* (where custom config for services live). Reconfigure in its current incarnation

[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

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:

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

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

[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] Proposing Mauricio Lima for core reviewer

From: Steven Dake <std...@cisco.com<mailto:std...@cisco.com>> Reply-To: "openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, May

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

Rob and Doug, At Summit we had 4 hours of highly productive work producing a list of "things" that can be "threatened". We have about 4 or 5 common patterns where we follow the principle of least privilege. On Friday of Summit we produced a list of all the things (in this case deployed

Re: [openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer

This should be obvious to core reviewers, but for Mauricio to join the core reviewer team, there must be no veto votes and a majority of +1s. Apologies for leaving that out. Regards -steve From: Steven Dake <std...@cisco.com<mailto:std...@cisco.com>> Reply-To: &q

[openstack-dev] [kolla] Proposing Mauricio Lima for core reviewer

Hello core reviewers, I am proposing Mauricio (mlima on irc) for the core review team. He has done a fantastic job reviewing appearing in the middle of the pack for 90 days [1] and appearing as #2 in 45 days [2]. His IRC participation is also fantastic and does a good job on technical work

[openstack-dev] [kolla] Newton Milestone #1 and #2 obectives

Hey OpenStackers, I'd like to point out a few commitments made at OpenStack summit during various discussions among the community. Our direction (if your looking for work to do ;) should be the following: * Ansible 2.0 implementation. * Making the dashboard load automated. *

[openstack-dev] [kolla] Prepare for Ansible 2.0

Hey folks, As distros move to Ansible 2.0 and Ansible 1.9 is unsupported by upstream and essentially unmaintained, I suggest we move Kolla to Ansible 2.y series. The blueprint is here: https://blueprints.launchpad.net/kolla/+spec/ansible2 I'm not sure if Jeffrey is actively working on this,

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

Tom, Devil's advocate here.. :) Can you offer examples of other OpenStack API services which behave in this way with a API? I'm struggling to think of any off the top of my head, but admittedly don't know all the ins and outs of OpenStack ;) Thanks -steve On 5/16/16, 2:28 AM, "Cammann,

Re: [openstack-dev] [kolla] [bifrost] bifrost container poc update

From: "Mooney, Sean K" <sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>> Date: Friday, May 13, 2016 at 2:14 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack

Re: [openstack-dev] [kolla] Vagrant environment for kolla-kubernetes

Jeff, I'd like to see Kolla defaults for k8s come from one place rather then two, so I suggested to Dims in a previous review to depend on the kolla repo for those files rather then copy them and maintain them in two places. Therefore, I don¹t see a viable path forward without the Kolla package

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"

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

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

nk it can be reused regarless or how we decide to deploy ironic. Thanks, Kevin From: Mooney, Sean K [sean.k.moo...@intel.com<mailto:sean.k.moo...@intel.com>] Sent: Friday, May 06, 2016 12:54 PM To: OpenStack Development Mailing List (not for usage questions) Subje

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

__ From: Mooney, Sean K [sean.k.moo...@intel.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) [

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

9, 2016 at 1:12 PM 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] [bifrost] bifrost container. On Fri, May 6, 2016 at 10:56 AM, Steven Dake (st

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"

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.

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

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" > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

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

[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

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

[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

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

From: Jeffrey Zhang > Reply-To: OpenStack Development Mailing List > Date: Tuesday, May 3, 2016 at 9:12 AM To: OpenStack Development Mailing List

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

gt;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) <std...@cisco.com >&

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,

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

uot; <jpee...@redhat.com> wrote: >On Sun, May 1, 2016 at 5:03 PM, Steven Dake (stdake) <std...@cisco.com> >wrote: >> I don't think a separate repository is the correct approach based upon >>one >> off private conversations with folks at summit. Many people f

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

ded/reasonable. This 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 (no

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

arate repo's >much or is the majority of the work in the end going 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

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

On 5/1/16, 10:32 PM, "Swapnil Kulkarni" <m...@coolsvap.net> wrote: >On Mon, May 2, 2016 at 9:54 AM, Britt Houser (bhouser) ><bhou...@cisco.com> wrote: >> Although it seems I'm in the minority, I am in favor of unified repo. >> >> From: &quo

[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

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

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

f a separate repo. But also core's are welcome to chime in. Regard -steve On May 1, 2016 4:06 PM, "Steven Dake (stdake)" <std...@cisco.com<mailto:std...@cisco.com>> wrote: Ryan had rightly pointed out that when we made the original proposal 9am morning we had asked folks if t

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

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

* mark casey * Steven Dake (delta-alpha-kilo-echo) * Michael Schmidt * Marian Schwarz * Andrew Battye * Kevin Fox (kfox) * Sidharth Surana (ssurana) *Michal Rostecki (mrostecki) * Swapnil Kulkarni (coolsvap) * MD NADEEM (mail2nadeem92

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

tory until proposed for the kolla-core reviewer group where they can gate changes to any part of the repository. * Britt Houser * mark casey * Steven Dake (delta-alpha-kilo-echo) * Michael Schmidt * Marian Schwarz * Andrew Battye * Kevin Fox (kfox) * Sidha

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

: Steven Dake <std...@cisco.com<mailto:std...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Friday, April 22, 2016 at 7:08 PM To: "OpenStack

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

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

<    1   2   3   4   5   6   7   8   9   >