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

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

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

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

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

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

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

[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

[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

[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

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" <fu...@yuggoth.org> 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

[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

[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

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

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

From: Steven Dake > Reply-To: "openstack-dev@lists.openstack.org" > Date: Tuesday, May 17, 2016 at 12:00 PM To:

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Dims, Given the strong language around partnership between Intel, Mirantis, and Google in that press release, and the activity in the review queue (2 pages of outstanding reviews) it seems clear to me that the intent is for this part of Fuel to participate in the big tent. The right thing to do

Re: [openstack-dev] [release][kolla] Error in tagging process by release liason

On 7/26/16, 5:55 AM, "Doug Hellmann" <d...@doughellmann.com> wrote: >Excerpts from Steven Dake (stdake)'s message of 2016-07-23 18:27:00 +: >> Doug and friends, >> >> I made a pretty serious error when tagging kolla-kubernetes originally.

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

n the project-config review: >https://review.openstack.org/#/c/335584/ > > >Thanks, >Dims > >On Tue, Jul 26, 2016 at 3:47 PM, Steven Dake (stdake) <std...@cisco.com> >wrote: >> Dims, >> >> Given the strong language around partnership between Intel, Mirantis, >

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

M >To: OpenStack Development Mailing List (not for usage questions) >Subject: Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is >getting Fuel CCP (docker/k8s) kicked off > >On Tue, Jul 26, 2016 at 09:42:10PM +, Steven Dake (stdake) wrote: >> >> >> O

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On 7/26/16, 2:13 PM, "Jim Rollenhagen" <j...@jimrollenhagen.com> wrote: >On Tue, Jul 26, 2016 at 08:36:01PM +, Steven Dake (stdake) wrote: >> Dims, >> >> The project-config addition was debated by Andreas before this >>partnership >> in thi

[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

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

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

Collectd is how you obtain the host disk usage. It can be done although collectd is nearing the complexity of turning nova into a container so it may need someone experienced with Kolla to execute. Regards -steve On 7/25/16, 12:39 AM, "Jeffrey Zhang" wrote: >I am open

[openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes

Hey folks, I know it doesn't make a lot of sense to break up containers from ansible changes to people outside the core review team, but for anything with backport potential, please do so. We are considering in Occata splitting the kolla repo into two (kolla = containers & build,

Re: [openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes

quot;OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes On 22 July 2016 at 2

Re: [openstack-dev] [kolla] Monitoring tooling

This 218 issue looks like it has a full solution to containerizing telegraf. I suspect collectd is VERY similar in nature – so if your up for two challenges instead of one, collectd would be a good second target :) Regards -steve From: Mathias Ewald >

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

ck-dev] [kolla][vote] Applying for stable-follows tag +1 to apply I'd like to be the volunteer. On Mon, Jul 18, 2016 at 9:04 PM, Swapnil Kulkarni (coolsvap) <m...@coolsvap.net<mailto:m...@coolsvap.net>> wrote: On Mon, Jul 18, 2016 at 6:23 PM, Paul Bourke <paul.bou...@oracle.com<m

Re: [openstack-dev] [kolla] Monitoring tooling

Response inline On 7/25/16, 11:54 AM, "Matthias Runge" wrote: >On 25/07/16 09:57, Julien Danjou wrote: >> On Sun, Jul 24 2016, Mathias Ewald wrote: >> >>> 5. InfluxDB to store metrics >>> 6. Grafana to dashboard metrics >> >> Would be nice to leverage scalable and open

Re: [openstack-dev] [kolla] repo split

artin André" <m.an...@redhat.com> wrote: >On Thu, Jul 21, 2016 at 5:21 PM, Steven Dake (stdake) <std...@cisco.com> >wrote: >> I am voting -1 for now, but would likely change my vote after we branch >> Newton. I'm not a super big fan of votes way ahead of major

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

One correction inside: On 7/27/16, 12:02 PM, "Jay Pipes" wrote: >On 07/27/2016 01:59 PM, Fox, Kevin M wrote: >> Kolla is providing a public api for docker containers and kubernetes >>templates though. So its not just a deployment tool issue. Its not >>specifically rest, but

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Thanks for the clarity Doug. Regards -steve On 7/28/16, 8:37 AM, "Doug Hellmann" <d...@doughellmann.com> wrote: >Excerpts from Flavio Percoco's message of 2016-07-28 16:43:35 +0200: >> On 28/07/16 04:45 +, Steven Dake (stdake) wrote: >> > >> >

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

of >time. > >Please stop using a marketing press release as some indication of what >the "intent" is for these repos or even that there *is* any intent at >this point. It's really early on and these repos are intended as a place >to experiment and innovate. I don't see why there is so

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Doug, Zane's analysis is correct. I agree with Zane's assessment that TC clarification can solve this situation. Regards -steve On 7/28/16, 9:15 AM, "Zane Bitter" wrote: >On 28/07/16 08:48, Vladimir Kozhukalov wrote: >> Fuel-ccp repositories are public, everyone is

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

e repos *aren't in the OpenStack tent* so how precisely would TC >guidance about what it means for a repo to be part of the OpenStack tent >be useful here? > >-jay > >On 07/28/2016 01:04 PM, Steven Dake (stdake) wrote: >> Jay, >> >> That resolution doesn't clari

[openstack-dev] [kolla] Monitoring tooling

Hi folks, At the midcycle we decided to push off implementing Monitoring until post Newton. The rationale for this decision was that the core review team has enough on their plates and nobody was super keen to implement any monitoring solution given our other priorities. Like all good

Re: [openstack-dev] [Magnum] Remove Davanum Srinivas from Magnum core team

Your a class act Dims. It was good working with you on Magnum :) Regards -steve On 7/22/16, 2:15 PM, "Davanum Srinivas" wrote: >Thanks Hongbin! > >On Fri, Jul 22, 2016 at 5:13 PM, Hongbin Lu wrote: >> Hi all, >> >> >> >> Based on Dims¹s request, I

Re: [openstack-dev] [kolla] Monitoring tooling

or concerns welcome. Regards -steve On 7/22/16, 3:42 PM, "Stephen Hindle" <shin...@llnw.com> wrote: >Don't forget mewalds implementation as well - we now have 2 monitoring >options for kolla :-) > >On Fri, Jul 22, 2016 at 3:15 PM, Steven Dake (stdake) <std...

Re: [openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes

nt: Friday, July 22, 2016 2:19 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla] Please start getting in the habit of breaking up containers from ansible changes On 22 July 2016 at 21:35, Steven Dake (stdake) <std...@cisco.com<mailto:std.

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

-steve On 7/28/16, 1:13 PM, "Doug Hellmann" <d...@doughellmann.com> wrote: >Excerpts from Steven Dake (stdake)'s message of 2016-07-28 19:40:29 +: >> >> On 7/28/16, 12:30 PM, "Davanum Srinivas" <dava...@gmail.com> wrote: >> >>

Re: [openstack-dev] [kolla][stable] Please consider our application for stable:follows-policy for Kolla

Hey folks, I just wanted to let the core team and others in the community know this tag application was rejected. The Kolla core team made a choice when we decided to make Liberty non-dangerous. We knew at the time it would imperil an application for stable:follows-policy. We thought at the

Re: [openstack-dev] [tc] persistently single-vendor projects

Kevin, Just assessing your numbers, the team:diverse-affiliation tag covers what is required to maintain that tag. It covers more then core reviewers - also covers commits and reviews. See: https://github.com/openstack/governance/blob/master/reference/tags/team_div erse-affiliation.rst I can

Re: [openstack-dev] [tc] persistently single-vendor projects

On 7/31/16, 11:29 AM, "Doug Hellmann" <d...@doughellmann.com> wrote: >Excerpts from Steven Dake (stdake)'s message of 2016-07-31 18:17:28 +: >> Kevin, >> >> Just assessing your numbers, the team:diverse-affiliation tag covers >>what >>

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

Michael, Response inline. From: Michael Still > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Wednesday, July 27, 2016 at 5:30 AM To:

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On 7/27/16, 2:12 PM, "Jay Pipes" wrote: >On 07/27/2016 04:42 PM, Ed Leafe wrote: >> On Jul 27, 2016, at 2:42 PM, Fox, Kevin M wrote: >> >>> Its not an "end user" facing thing, but it is an "operator" facing >>>thing. >> >> Well, the end user for Kolla

Re: [openstack-dev] [docker] [magnum] Magnum account on Docker Hub

Ton, I may or may not have set it up early in Magnum's development. I just don't remember. My recommendation is to file a support ticket with docker and see if they will tell you who it belongs to (as in does it belong to one of the founders of Magnum) or if it belongs to some other third

Re: [openstack-dev] [tc] persistently single-vendor projects

tion track which from my experience with founding Heat was a serious hurdle for OpenStack in general and Ceilometer and Heat specifically. Regards, -steve > >Doug > >> >> -- >> Adrian >> >> > On Aug 1, 2016, at 5:11 AM, Sean Dague <s...@dague.net

Re: [openstack-dev] [kolla] Why base image always be built each time build a specific image.

Paul, I think the cache isn't working exactly as you described for the base image. Not sure what is going on there - it could just be my misperception. However, as you point out the time spent "rebuilding" the base image is very small (under 30 seconds) so I don't believe its a pressing

Re: [openstack-dev] [tc] persistently single-vendor projects

On 8/2/16, 7:17 AM, "Ed Leafe" <e...@leafe.com> wrote: >On Aug 2, 2016, at 8:50 AM, Steven Dake (stdake) <std...@cisco.com> wrote: > >> For example tripleo is single-vendor, but is doing all the right things >>to >> dig out of single vendor by d

Re: [openstack-dev] [tc] persistently single-vendor projects

Responses inline: On 8/2/16, 8:13 AM, "Hayes, Graham" wrote: >On 02/08/2016 15:42, Flavio Percoco wrote: >> On 01/08/16 10:19 -0400, Sean Dague wrote: >>> On 08/01/2016 09:58 AM, Davanum Srinivas wrote: Thierry, Ben, Doug, How can we distinguish between.

[openstack-dev] [kolla] FW: [all][ptl][tc] extra ATCs for newton

Koalligans, I can't think of anyone off the top of my head that hasn't submitted a patch for Newton that would qualify for an ATC pass under the bylaws [1] and TC Charter [2], but would like to open up nominations from core reviewers since I am not omnipotent. The only candidates that even come

Re: [openstack-dev] Project mascots update

On 8/3/16, 10:37 AM, "Steven Hardy" wrote: >On Wed, Aug 03, 2016 at 10:19:10AM -0700, Heidi Joy Tretheway wrote: >>Thanks to all of you for contributing unique and inspiring ideas to >>choose >>a team mascot. You can view a list of projects that have chosen their >>

Re: [openstack-dev] [kolla] Question about kolla git tag

Confirming Chao's statement. We support this model all the time on the #openstack-kollal. Thanks Chao. Regards -steve From: 韩潮 > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [kolla] repo split

I am voting -1 for now, but would likely change my vote after we branch Newton. I'm not a super big fan of votes way ahead of major events (such as branching) because a bunch of things could change between now and then and the vote would be binding. Still community called the vote - so vote

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.

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

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

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

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] 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 > Date: Sunday, July 3, 2016 at 12:19 PM To: Steven Dake > Subject:

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] Project mascots update

From: Heidi Joy Tretheway > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Thursday, August 4, 2016 at 9:13 AM To: "OpenStack

Re: [openstack-dev] [docker] [magnum] Magnum account on Docker Hub

ticket to acquire the username openstackmagnum. I included Hongbin's contact information explaining that he's the project's PTL. Thanks Steve, Spyros On 2 August 2016 at 13:29, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote: Ton, I may or may not have set it up

Re: [openstack-dev] [kolla] Needing volunteers for Geography Coordinators for making use of OSIC cluster

Typo is subject tag - please see inside :) From: Steven Dake > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Friday, August 5, 2016 at 6:52 AM

[openstack-dev] [kollla] Needing volunteers for Geography Coordinators for making use of OSIC cluster

Hey folks, The kind folks at OSIC have granted the Kolla team access to 132 nodes of super high powered gear for scale testing Kolla. The objectives are 3 fold: 1. Determine if Kolla can scale to 132 nodes for a variety of test cases - if not fix bugs around those problems 2. If

Re: [openstack-dev] [kolla][osic][bifrost] OSIC cluster status

Hey folks, Thanks for the video, those are great - if not a little hard for the casual observer to follow. That said, benchmark results of scale testing can be a dangerous game to play, so lets not play games about it. I'd like to see a full characterization of the hardware gear and topology

Re: [openstack-dev] [glare][kolla][odm] timing of release of glare and request for technical interview on IRC wherever the glare team wants to have it

.log.html#t2016-08-08T16:01:50 Thanks again Mike. Regards, -steve On 8/8/16, 8:01 AM, "Jay Pipes" <jaypi...@gmail.com> wrote: >On 08/08/2016 07:48 AM, Steven Dake (stdake) wrote: >> Cool thanks for the response. Appreciate it. I think the big take away >> is a

[openstack-dev] [glare][kolla] timing of release of glare and request for technical interview on IRC wherever the glare team wants to have it

Hey folks, I guess the split of glare and glance have been in the works for awhile. It is challenging for operational deployment managers (ODMs) such as Kolla to keep up with the internal goings-on of every big tent project (or projects that shave off from big-tent projects). Just to be

Re: [openstack-dev] [kolla] I need help on multisite deploy

Lu Yao, Please drop by #openstack-kolla and our community can help you get rolling. Although now isn't a particularly good time (4:30 AM PST) - I'm awake and can get you up and running. My nick is sdake. Regards, -steve From: "lu.yao...@zte.com.cn"

Re: [openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project

Kevin, Agree it would be a very useful feature, however, easier said then done. Part of Docker's approach is to "move fast";they schedule releases every 2 months. I'm sure the glare team is quite competent, however, keeping API parity on such a fast moving project such as the docker registry

Re: [openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project

o][Tacker] Glare as a new Project However, interested parties could start a project like the ec2 project that is independently released and provides that compatibility using glare On Aug 6, 2016 5:18 AM, "Steven Dake (stdake)" <std...@cisco.com<mailto:std...@cisco.com>>

Re: [openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project

Well don't let me stop ya :) On 8/9/16, 7:21 AM, "Ian Cordasco" <sigmaviru...@gmail.com> wrote: > > >-Original Message- >From: Steven Dake (stdake) <std...@cisco.com> >Reply: OpenStack Development Mailing List (not for usage questions) ><opens

[openstack-dev] [osic][kolla] Start of OSIC scale testing documentation [WIP]

Hey Koalaians, See review: https://review.openstack.org/352101 What I'd like to see happen is everyone working on scale testing commit their work by pulling down that review, modifying it, and submitting it to gerrit. Lets not mege it until the OSIC cluster is no longer in our hands. If you

Re: [openstack-dev] [glare][kolla] timing of release of glare and request for technical interview on IRC wherever the glare team wants to have it

And for sure, I'll be glad to answer all your questions, 1600 UTC today works for me. So, let's meet at this time in your channel. Best, Mike On Sat, Aug 6, 2016 at 2:21 PM, Steven Dake (stdake) <std...@cisco.com<mailto:std...@cisco.com>> wrote: Hey folks, I guess the split of gla

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

This vote passed unanimously prior to the July 25th deadline. Lets apply :) Regards -steve From: Steven Dake > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

[openstack-dev] [release][kolla] Error in tagging process by release liason

Doug and friends, I made a pretty serious error when tagging kolla-kubernetes originally. Kolla-kubernetes is in development and not in a production ready state. We also don't intend to apply for many if any tags for this repository until it becomes more mature. We do not intend to do

[openstack-dev] [stable] Please consider our application for stable:follows-policy for Kolla

Hey folks, The review is here: https://review.openstack.org/346455 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [kolla][stable] Please consider our application for stable:follows-policy for Kolla

[Forgot kolla tag] From: Steven Dake > Date: Saturday, July 23, 2016 at 12:30 PM To: "OpenStack Development Mailing List (not for usage questions)" > Subject: [stable] Please

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

lease write up a proposal for the TC to >consider? (https://review.openstack.org/#/q/project:openstack/governance) > >Thanks, >-- Dims > >On Thu, Jul 28, 2016 at 2:01 PM, Steven Dake (stdake) <std...@cisco.com> >wrote: >> Jay, >> >> I'll be frank. I have

Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

a resolution is reached is not the right thing. Regards -steve > >Thanks, >Dims > >On Thu, Jul 28, 2016 at 3:26 PM, Steven Dake (stdake) <std...@cisco.com> >wrote: >> Dims, >> >> I personally think its the responsibility of the TC to resolve this >&g

[openstack-dev] [kolla][ironic][odm][ACTION NEEDED] Kolla's BiFrost and kolla-host work

Sean has done a fantastic job on the BiFrost work and kolla-host work. What is needed is the last step - which is a final thorough technical review from the core review team so we can get it merged by end of week. If your struggling to find the work in the review queue, use this link:

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

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

<    1   2   3   4   5   6   7   8   >