[openstack-dev] [Glance] Removing python-sendfile related code from BaseClient

I'm adding some unit tests for glance/common/client.py as part of bug/1115551, and noticed the image_iterator() function (https://github.com/openstack/glance/blob/master/glance/common/client.py#L568) returns two non-existent types, SendFileIterator and ImageBodyIterator. It seems there's no code

Re: [openstack-dev] [Glance] images tasks API -- final call for comments

Hi Brian, I had a read over the summary wiki page and the individual docs. My main thought was that although the asynchronous nature seems attractive, the problems the new API is setting out to solve could be adapted to the existing images API. This view seems to be shared and well highlighted

[openstack-dev] [requirements] Review request for adding ordereddict

Hi all, I've submitted https://review.openstack.org/#/c/46474/ to add ordereddict to openstack/requirements. The reasoning behind the change is that we want ConfigParser to store sections in the order they're read, which is the default behavior in py2.7[1], but it must be specified in py2.6.

Re: [openstack-dev] [kolla][tripleo] Update on Kolla

Hi Steve, Thanks for the update. For those interested in Kolla development and discussion, where is the best place to go? Regards, -Paul On 05/02/15 17:25, Steven Dake (stdake) wrote: Hey folks, I wanted to provide a brief update on where we are headed with Kolla. Initially Kolla began

Re: [openstack-dev] [kolla] Proposal for changing 1600UTC meeting to 1700 UTC

+1 On 08/06/15 18:37, Smigiel, Dariusz wrote: Folks, Several people have messaged me from EMEA timezones that 1600UTC fits right into the middle of their family life (ferrying kids from school and what-not) and 1700UTC while not perfect, would be a better fit time-wise. For all people that

Re: [openstack-dev] [kolla] Proposal for changing 1600UTC meeting to 1700 UTC

Actually I misread the time, 1700 UTC is 6pm Irish time which is not as good for me. So -1 On 09/06/15 09:30, Paul Bourke wrote: +1 On 08/06/15 18:37, Smigiel, Dariusz wrote: Folks, Several people have messaged me from EMEA timezones that 1600UTC fits right into the middle of their family

[openstack-dev] [kolla] Add your name and TZ to wiki

Hi all, Steve suggested adding a new table to the Kolla wiki to help us keep track of who's actively working on Kolla along with relevant info such as timezones and IRC names. I'm missing lots of names and timezones so if you'd like to be on this please feel free to update it at

Re: [openstack-dev] [kolla] Proposal for changing 1600UTC meeting to 1700 UTC

I'm fairly easy on this but, if the issue is that the meeting is running into people's evening schedules (in EMEA), would it not make sense to push it back an hour or two into office hours, rather than forward? On 10/06/15 18:20, Ryan Hallisey wrote: After some upstream discussion, moving the

[openstack-dev] [kolla] Providing image specific build info

All, As part of the install-from-source blueprint, I'm proposing a basic script that can fetch tarballs in various ways, the result of which is installed as part of the image build. This script is for review here: https://review.openstack.org/#/c/197919/ This requires a couple of variables,

[openstack-dev] [kolla] Marking install-from-source as implemented

Hi Kolla folk, Just a quick note to say I've marked this bp as implemented. Source builds for all key services are merged so I think it's as a time as any. Please file separate bugs for subsequent contrib services (any existing ones for out for review can stay as is). Any issues with this

Re: [openstack-dev] [kolla] Proposing Swapnil Kulkarni (coolsvap) for kolla core reviewer team

+1, Swapnil has made a ton of useful contributions and continues to do so :) On 14/08/15 14:29, Steven Dake (stdake) wrote: Hi folks, Swapnil has done a bunch of great technical work, participates heavily in IRC, and has contributed enormously to the implementation of Kolla. I’d like to see

Re: [openstack-dev] [kolla] Proposal for Paul Bourke for Kolla Core

(not for usage questions) openstack-dev@lists.openstack.org mailto:openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [kolla] Proposal for Paul Bourke for Kolla Core +1 From: Steven Dake (stdake) std...@cisco.com mailto:std...@cisco.com Reply-To: OpenStack Development

Re: [openstack-dev] [kolla] Integrating kollacli as python-kollaclient

Having used the cli for some time I can vouch for it being very useful, and usable. The guys have done a nice job of giving it an "OpenStack feel", mimicking the patterns used in openstackclient and the like. It should give users a more polished introduction to Kolla. +1 -Paul On 21/10/15

Re: [openstack-dev] [kolla] Liberty release builds

stdake) wrote: On 10/20/15, 9:06 AM, "Paul Bourke" <paul.bou...@oracle.com> wrote: Kolla core team, Here's a link to an etherpad created just now for deciding the process on getting release builds to dockerhub: https://etherpad.openstack.org/p/kolla-release-builds Please review

Re: [openstack-dev] [kolla] Proposing Michal Rostecki for Core Reviewer (nihilfer on IRC)

+1 On 12/11/15 08:41, Steven Dake (stdake) wrote: Hey folks, Its been awhile since we have had a core reviewer nomination, but I really feel like Michal has the right stuff. If you look at the 30 day stats for kolla[1] , he is #3 in reviews (70 reviews) with 6 commits in a 30 day period. He

Re: [openstack-dev] [kolla] Mesos orchestration as discussed at mid cycle (action required from core reviewers)

+1 - the below sums up my impressions from the summit which I was good with. Look forward to seeing what Angus the guys come up with. -Paul On 02/11/15 17:02, Steven Dake (stdake) wrote: Hey folks, We had an informal vote at the mid cycle from the core reviewers, and it was a majority vote,

[openstack-dev] [kolla] Liberty release builds

Kolla core team, Here's a link to an etherpad created just now for deciding the process on getting release builds to dockerhub: https://etherpad.openstack.org/p/kolla-release-builds Please review and revise. Steve, can you follow up to this mail when you'd like volunteers to kick off

[openstack-dev] [gertty] Replying to inline comments

Hi, Does anyone know if this is possible in the current version of gertty? Thanks, -Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [kolla] Followup to review in gerrit relating to RHOS + RDO types

On 13/09/15 18:34, Steven Dake (stdake) wrote: Response inline. From: Sam Yaple > Reply-To: "s...@yaple.net" > Date: Sunday, September 13, 2015 at 1:35 AM To: Steven Dake

Re: [openstack-dev] [kolla] proposing Michal Jastrzebski (inc0) for core reviewer

+1 I actually thought he was core already :) On 30/09/15 01:24, Sam Yaple wrote: +1 Michal will be a great addition to the Core team. On Sep 29, 2015 6:48 PM, "Martin André" > wrote: On Wed, Sep 30, 2015 at 7:20 AM, Steven Dake

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

+1 On 08/06/16 13:54, Swapnil Kulkarni (coolsvap) wrote: Dear Kollagues, Some time ago we discussed the requirement of alternating meeting times for Kolla weekly meeting due to major contributors from kolla-mesos were not able to attend weekly meeting at UTC 1600 and we implemented alternate

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

Michal, I'd be interested in helping with this. Keep us updated! -Paul On 03/06/16 17:58, Michał Jastrzębski wrote: Hello Kollagues, Some of you might know that I submitted request for 130 nodes out of osic cluster for testing Kolla. We just got accepted. Time window will be 3 weeks between

[openstack-dev] [kolla] Fwd: Re: Kilo version of Kolla

fyi Forwarded Message Subject: Re: Kilo version of Kolla Date: Fri, 3 Jun 2016 16:01:59 + From: Steven Dake (stdake) <std...@cisco.com> To: Paul Bourke <paul.bou...@oracle.com>, POLAKU, CHANDRA <cp6...@att.com> CC: VENKATSUBRAMANIAM, SHRINATH <sv3

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

Hi David, I agree with this completely. Gates continue to be a problem for Kolla, reasons why have been discussed in the past but at least for me it's not clear what the key issues are. I've added this item to agenda for todays IRC meeting (16:00 UTC -

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

+1, hopefully we'll see Harm again in the future. Cheers, -Paul On 15/01/16 13:44, Michał Jastrzębski wrote: That's an unfortunate +1, it's always sad to lose one of our own. Hope we'll see you back soon! Thanks for all the fis...reviews! On 15 January 2016 at 06:59, Ryan Hallisey

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

I was also thinking of adding Lei. He was a big help to me only recently with fixing plugin support and adding unit test support to build.py. +1 from me. -Paul On 19/01/16 08:26, Steven Dake (stdake) wrote: Hi folks, I would like to propose Lei Zhang for our core reviewer team. Count this

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

+1 I'm against this on a theoretical basis as I don't think backporting features/architectural changes is good practice for a stable branch. People will say this will increase stability (no longer lose namespaces on container restart), in reality the chances are it will decrease stability

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

+1 On 22/02/16 03:23, Jeffrey Zhang wrote: +1 Nick work! On Mon, Feb 22, 2016 at 10:27 AM, Ryan Hallisey > wrote: +1. Nice work Angus! -Ryan > On Feb 19, 2016, at 11:51 PM, Michał Jastrzębski

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

Hi all, I'm currently working to add new gates for the oraclelinux image base type (https://blueprints.launchpad.net/kolla/+spec/oraclelinux-gate) and had a question on size available in the gate VMs. Right now the binary build is running out of space in the gate, as it exceeds the 10GB

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

+1 On 29/03/16 17:07, Steven Dake (stdake) wrote: Hey folks, Consider this proposal a +1 in favor of Vikram joining the core reviewer team. His reviews are outstanding. If he doesn’t have anything useful to add to a review, he doesn't pile on the review with more –1s which are slightly

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

I've said in the past I'm not a fan of nitpicking docs. That said, I feel it's important for spelling and grammar to be correct. The quickstart guide is the first point of contact for many people to the project, and rightly or wrongly it will give an overall impression of the quality of the

Re: [openstack-dev] [kolla] [vote] Managing bug backports to Mitaka branch

Hey Steve, Thanks for dropping this round - I was occupied during the meeting and wanted to be sure what I was asked to vote on! It seems like it's not a big deal after all, also considering it's standard practice it's a no brainer. +1 Cheers, -Paul On 24/03/16 03:55, Swapnil Kulkarni

Re: [openstack-dev] [kolla][vote] deprecation of icehosue/juno/kilo branches

+1 On 25/03/16 15:36, Steven Dake (stdake) wrote: Hey folks, These branches are essentially unmaintained and we have completely given up on them. That’s ok – they were paths of our development. I didn't really want to branch them in the first place, but the community demanded it, so I

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

This is a messy topic. I feel there's been some miscommunication and confusion on the issue which hopefully I can sum up. As far as I remember it, Sam is correct, we did always plan to do Liberty upgrades. However, over the course of time post Tokyo these plans didn't really materialise, at

Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core reviewer

I've been impressed with Alicja's contributions and had suggested this nomination. So +1 a valuable addition. Cheers, -Paul On 04/03/16 17:27, Swapnil Kulkarni wrote: On Fri, Mar 4, 2016 at 10:25 PM, Steven Dake (stdake) wrote: Core Reviewers, Alicja has been instrumental

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

+1 On 30/03/16 04:27, Steven Dake (stdake) wrote: Dear cores, inc0 has been investigating our backport options for 1.1.0 and they look bleak. At this time we would have to backport heka because of changes in Docker 1.10.z which are incompatible with the syslog dev file. We had originally

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

+1 thanks for all the work Mauricio On 17/05/16 20:00, Steven Dake (stdake) wrote: 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

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

Having read through the full thread I'm still in support of separate repos. I think the explanations Jeff Peeler and Adam Young have put forward summarise my thoughts very well. One of the main arguments I seem to be hearing for a single repo is Git tooling which I don't think is a good one;

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

TL;DR keep globals.yml to a minimum, customise configs via host_vars/group_vars It seems right now the "best" approach may be to tokenise variables as required. This is the approach we currently use in Oracle. There are two other approaches I can think of available to us: 1) The overwrite

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

I have a debug job open atm to try and investigate this: https://review.openstack.org/#/c/300988/ If anyone is handy with strace here is a run with the output: http://logs.openstack.org/88/300988/6/check/gate-kolla-dsvm-deploy-centos-binary/726c3b1/console.html On 09/05/16 18:23, Hui Kang

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

system and qemu-utils ii qemu-utils1:2.5+dfsg-5ubuntu10.2~cloud0 amd64QEMU utilities Thanks, -Paul On 14/07/16 17:34, Paul Bourke wrote: Hi Matt, Here is the failure from nova_compute on trying to start an instance: 2016-07-13 18:04:12.634378 | 2016-07-13

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

Hi Matt, Here is the failure from nova_compute on trying to start an instance: 2016-07-13 18:04:12.634378 | 2016-07-13 18:01:34.560 1 ERROR oslo_service.service [req-0d77b2c1-43c8-41de-b57f-8aaa974b9807 - - - - -] Error starting thread. 2016-07-13 18:04:12.634410 | 2016-07-13 18:01:34.560 1

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

Zhijiang, You will see lines relating to the base image each time you build, however, they should be cached so will add almost no additional time to the build. -Paul On 21/07/16 09:48, hu.zhiji...@zte.com.cn wrote: Hi, When I use the following command to build keystone image, I saw

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

Update Aug 9th: We are on scenario two: 3 control, 20 storage, 100 compute with Ceph. Notes are now being collected in https://review.openstack.org/#/c/352101/ along with tempest/rally results. -Paul On 05/08/16 17:48, Paul Bourke wrote: Hi Kolla, Thought it will be helpful to send

[openstack-dev] [kolla][osic] Accessing the osic VPN

For those starting work on the OSIC cluster, I was having some trouble installing the F5 VPN browser plugin, not to mention it's no good if wanting to access the cluster remotely. In the spirit of Kolla here's a Dockerfile I knocked up to run the VPN client in a container:

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

Hi Steve, +1 to applying. I'll volunteer for the backport team also. -Paul On 18/07/16 13:07, Steven Dake (stdake) wrote: Hey Koalians, I'd like us to consider applying for the stable follows policy tag. Full details are here:

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

Sounds reasonable +1 On 12/07/16 15:32, Michał Jastrzębski wrote: Hey guys, Since our project matured, we decided that we should have a discussion regarding our spec process. https://etherpad.openstack.org/p/kolla-N-midcycle-specs Currently we do specs for most critical things, and they

[openstack-dev] [kolla][osic] OSIC cluster status

Hi Kolla, Thought it will be helpful to send a status mail once we hit checkpoints in the osic cluster work, so people can keep up to speed without having to trawl IRC. Reference: https://etherpad.openstack.org/p/kolla-N-midcycle-osic Work began on the cluster Wed Aug 3rd, item 1) from the

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

I can do this for EMEA -Paul On 05/08/16 17:11, Steven Dake (stdake) wrote: Typo is subject tag – please see inside :) From: Steven Dake > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

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

sets of data after each deploy scenario. -Paul On 16/08/16 12:57, Paul Bourke wrote: Kollagues, Can we get an update from the APAC / US reps? The last I heard we were having trouble getting guests spawned on an external network so they could be accessible by Rally. There's been various people

Re: [openstack-dev] [kolla-ansible] [kolla] Am I doing this wrong?

Hi Kris, Thanks for the feedback, I think everyone involved in kolla-ansible should take the time to read through it, as it definitely highlights some areas that we need to improve. There's a lot of questions here, so I haven't gone into too much detail on any specific one; my hope is that

[openstack-dev] [kolla] Docs status?

Hi Kolla, Does anyone know the current status of docs refactor? I believe there was someone looking into it (apologies can't remember their name). If not, I'd like to propose a vote for some immediate changes that can improve things. Regards, -Paul

Re: [openstack-dev] [kolla-ansible] [kolla] Am I doing this wrong?

Ah, I think you may be misreading what Sean is saying there. What he means is kolla-ansible provides the bare minimum config templates to make the service work. To template every possible config option would be too much of a maintenance burden on the project. Of course, users will want to

Re: [openstack-dev] [kolla] Docs status?

against the kolla repository. Please have a look if you have time. Thanks, -Paul On 24/01/17 12:06, Paul Bourke wrote: Hi Kolla, Does anyone know the current status of docs refactor? I believe there was someone looking into it (apologies can't remember their name). If not, I'd like to propose

Re: [openstack-dev] [kolla-ansible] [kolla] Am I doing this wrong?

ating it, might be worth reaching out to people from Ansible for more info. On 25/01/17 00:01, Mooney, Sean K wrote: -Original Message----- From: Paul Bourke [mailto:paul.bou...@oracle.com] Sent: Tuesday, January 24, 2017 11:49 AM To: OpenStack Development Mailing List (not for usage ques

Re: [openstack-dev] [kolla][kolla-ansible] How to restart working on a patch started before repo split?

Hi Hiroki, To my knowledge it's not possible to change the target repository for an open patch. What we've done so far is to abandon the in progress one, cherry-pick to the correct repository and start a new review (adding the original author as a co-author of course). Hope that helps,

Re: [openstack-dev] [kolla] Structuring the documentation on all repositories

Hi Christian, Thanks for the summary, useful for those of us not at the PTG. I'm a little confused on the final outcome, it sounds like most of what you've written is currently the case. Besides a more user friendly deploy guide appearing under

Re: [openstack-dev] [vote][kolla] Core nomination proposal for Eduardo Gonzalez Gutierrez (egonzales90 on irc)

+1 On 19/08/16 00:15, Michał Jastrzębski wrote: +1 On 18 August 2016 at 18:09, Steven Dake (stdake) wrote: Kolla Core Review Team: I am nominating Eduardo for the core reviewer team. His reviews are fantastic, as I'm sure most of you have seen after looking over the

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

is short. If someone could summarise(looking at Jeffrey / inc0 ;)) what's been happening that will allow us to make a decision on how to progress. Cheers, -Paul On 05/08/16 17:48, Paul Bourke wrote: Hi Kolla, Thought it will be helpful to send a status mail once we hit checkpoints in the osic

Re: [openstack-dev] [kolla][vote] Core nomination for Dave Walker (Daviey on irc)

+1 On 23/08/16 21:45, Steven Dake (stdake) wrote: Kolla core reviewers, I am nominating Dave Walker for the Kolla core reviewer team. His 30 day review stats [1] place him in the middle of the pack for reviewers and his 60 day stats[2] are about equivalent. Dave participates heavily in IRC

[openstack-dev] [kolla] Problem regarding named volume data location

Hi Kolla, We have been experiencing a long running issue with Kolla that I have brought up briefly a few times, but not made too much noise about. I'm taking the time to write about it in the hopes that a) as a community we may be able to solve it, and b) if other operators start

Re: [openstack-dev] [kolla] Requirement for bug when reno is present

sdake kindly took the time to explain the release process. Logs are here: http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-kolla.2016-09-01.log.html#t2016-09-01T09:06:49 On 30/08/16 20:31, Christian Berendt wrote: On 30 Aug 2016, at 12:42, Paul Bourke <paul.

Re: [openstack-dev] [vote][kolla] Core Nomination for Christian Berendt (berendt on irc)

+1 On 08/09/16 03:59, Steven Dake (stdake) wrote: Kolla core reviewer team, It is my pleasure to nominate Christian Berendt for the Kolla core team. Christian’s output over the last cycle has been fantastic – cracking the top 10 reviewer list for the full cycle. His 30 day stats [1]

[openstack-dev] [kolla] Requirement for bug when reno is present

Kolla, Do people feel we still want to require a bug-id in the commit message for features, when reno notes are present? My understanding is that till now we've required people to add bugs for non trivial features in order to track them as part of releases. Does/should reno supersede this?

Re: [openstack-dev] [kolla] Deprecation Policies (related to Heka)

Tagging kolla On 29/09/16 16:22, Michał Jastrzębski wrote: Agree with Christian, this is our internal wiring. As long as we provide automated upgrade procedure which will seamlessly migrate from heka to alternative we want, we should be good without deprecation per se. Cheers, Michal On 29

Re: [openstack-dev] [vote][kolla] Splitting out Ansible into a separate deliverable

c) Split the repository shortly after tagging 3.0.0 – creating a kolla-ansible deliverable for Ocata. On 15/09/16 07:12, Steven Dake (stdake) wrote: Core Reviewers: The facts: We have roughly 250 bugs in rc2. Of those, I suspect over half can just be closed out as dupes, fixed,

Re: [openstack-dev] [vote][kolla] deprecation for fedora distro support

+1 On 19/09/16 18:40, Jeffrey Zhang wrote: Kolla core reviewer team, Kolla supports multiple Linux distros now, including * Ubuntu * CentOS * RHEL * Fedora * Debian * OracleLinux But only Ubuntu, CentOS, and OracleLinux are widely used and we have robust gate to ensure the quality. For

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

-1 for deprecating Debian. As I mentioned in https://review.openstack.org/#/c/369183/, Debian support was added incrementally by Benedikt Trefzer as recently as June. So it's reasonable to believe there is at least one active user of Debian. I would like to try get some input from him on

Re: [openstack-dev] [vote][kolla] deprecation for debian distro support

If it's the case Benedict or noone else is interested in continuing Debian, I can reverse my vote. Though it seems I'll be outvoted anyway ;) On 20/09/16 10:21, Swapnil Kulkarni wrote: On Tue, Sep 20, 2016 at 2:38 PM, Paul Bourke <paul.bou...@oracle.com> wrote: -1 for deprecating

[openstack-dev] [kolla] Regarding footer blocks

Kolla, There seems to be a lot of confusion and thrashing on the customisation patches regarding the footer blocks. To help this I have documented the scheme at https://review.openstack.org/#/c/361253/2/doc/CONTRIBUTING.rst. Please review this and respond with questions if it doesn't make

Re: [openstack-dev] [kolla] Kolla configuration files owner and permission

In my experience operators prefer a dedicated user (kolla:kolla), though I can't see any major problem with your root:kolla approach. On 23/08/16 14:40, Steven Dake (stdake) wrote: On 8/23/16, 1:04 AM, "duon...@vn.fujitsu.com" wrote: Hi S.Dake, Hello Kollish,

Re: [openstack-dev] [kolla] Re: Your draft logo & sneak peek

Reminder Kolla, today is the deadline for feedback on this! Personally I think it could use a few tweaks so please don't forget to take a look. Link: http://tinyurl.com/OSmascot On 21/10/16 21:58, Steven Dake (stdake) wrote: Forgot kolla tag in subject. From: Steven Dake

Re: [openstack-dev] [kolla] How tied is kolla to matching 1:1 releases of openstack?

Hi Joshua, Thanks for sharing your workflow, interesting to see. To answer your question, there is a 1:1 relationship between Kolla and OpenStack releases. As Kevin outlined, you may get lucky, currently in Oracle we deploy OpenStack Mitaka with Kolla Newton and for the most part it works

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

of removing the requirement for TrivialFix. As per our standard policy, the voting window is open for 7 days beginning November 3^rd , and finishing (in 7 days) on November 11^th . Regards -steve *From: *Paul Bourke <paul.bou...@oracle.com> *Reply-To: *"OpenStack

[openstack-dev] [kolla] Notes on Ansible fact gathering

There is some concerns internally around Ansible fact gathering, and how it relates to adding / removing individual nodes in Kolla. As I've spent a fair bit of time in this area I decided to send some info around both for anyone confused about this in the future and also to tease out any ways

Re: [openstack-dev] [kolla] Kolla-ansible is available

Seems good so far, thanks Michal / Steve. Cores don't forget to add openstack/kolla-ansible to your watched projects in Gerrit :) I assume we just -2 any Ansible related patches currently open against the openstack/kolla project with instructions on how to resubmit. Also has it been

Re: [openstack-dev] [kolla][kolla-ansible][kolla-kubernetes] Kolla core election policy change - vote

+1 On 17/11/16 07:18, Martin André wrote: On Wed, Nov 16, 2016 at 7:23 PM, Michał Jastrzębski wrote: Hello, In light of recent events (kolla-kubernetes becoming thriving project, kolla-ansible being split) I feel we need to change of core reviewer election process.

[openstack-dev] [git-upstream] How to view only commits applied since last import

Hi Darragh / git-upstream community, I've been looking at a way to easily view a log of what commits made since the last upstream import when managing a branch with git-upstream. Right now this can be hard to do - something like 'git log upstream/master..HEAD' shows a lot of duplicate commits

Re: [openstack-dev] [kolla][git]How to backport commit after repo split

Seen as both repos stem from the same codebase, we should be able to just cherry-pick changes as usual. If a fix comprises of a change to both kolla and kolla-ansible, it will just mean two cherry-picks. Will need to wait till the relevant pieces are removed from both repos to confirm this but

Re: [openstack-dev] [kolla] Obtaining version information for Docker container

If I'm understanding the requirement correctly, we want to know which version of an OpenStack component is installed in an image? If so why not just run something like: # docker run kolla/oraclelinux-source-keystone:3.0.0 pip show keystone Name: keystone Version: 10.0.0.0rc2.dev290 [...] Or

Re: [openstack-dev] [kolla] How to handle doc in kolla and kolla-ansible

Propose all docs stay under the kolla namespace (http://docs.openstack.org/developer/kolla). Steve mentioned that we should try to keep all components (e.g. mailing list tags) under the same umbrella which I agree with. On 21/11/16 08:05, Jeffrey Zhang wrote: After the split, we have two

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

Thanks for the reminder Andreas, patchset here: https://review.openstack.org/397672 On 15/11/16 10:29, Andreas Jaeger wrote: On 2016-11-15 11:10, Paul Bourke wrote: Given the window for this vote is now closed and I saw no minus ones I'll assume this has passed. TrivialFix is now optional

[openstack-dev] [kolla] Propose removal of TrivialFix requirement

Kolleagues, How do people feel above removing the requirement of having TrivialFix in commit messages where a bug/bp is not required? I'm seeing a lot of valid and important commits being held up because of this, in my opinion, unnecessary requirement. It also causes friction for new

Re: [openstack-dev] [kolla] Propose removal of TrivialFix requirement

Hi Jeremy, > All I ask is that if the Kolla team wants to differentiate itself > from the review requirements of most OpenStack projects, please make We have no desire to do this, that's not what is being discussed here. On the contrary we're looking to reduce the barrier to entry for

Re: [openstack-dev] [kolla] balancing core team karma and collecting statements from kolla team.

Right now I try to attack the bug list whenever I get time, admittedly it's not a regular activity though. I actually wasn't aware kolla and kolla-ansible had separate bug trackers, so far I've just been following the kolla one so this is good to know. One issue I have is the fact that a

Re: [openstack-dev] [kolla] Bugs cleanup dashboard

This actually seems really useful, thanks Christian. On 15/12/16 11:35, Christian Berendt wrote: Hello everybody. Based on the dashboard which is used for the Nova project I have created one for Kolla. The dashboard gets updated hourly. http://kolla.betacloud.io/bugs-dashboard.html

Re: [openstack-dev] [kolla] Vote to add zhubingbing to core team

+1 On 29/11/16 16:21, Michał Jastrzębski wrote: Hello team! I'd like to propose to add zhubingbing to kolla (and kolla-ansible) core teams. He did great job reviewing code during last couple of months. Consider this proposal +1 from me, voting will be open for 1 week (until Dec 6) or if we

Re: [openstack-dev] [kolla] propose to remove COPY_ONCE feature

While I would be interested to know how many people actually do use COPY_ONCE, I think if I was in charge of a production deployment I would use COPY_ONCE. On 01/12/16 02:27, Jeffrey Zhang wrote: Kolla has a config_strategy option during deployment. it supports COPY_ONCE and COPY_ALWAYS.

Re: [openstack-dev] [kolla] [ironic] Introducing Kayobe - Scientific OpenStack deployment using kolla

Looks really cool Mark, congrats on the release! -Paul On 30/03/17 09:46, Mark Goddard wrote: Hi, I'd like to announce Kayobe[1], a project that we at StackHPC have been working on recently as we help to build out a performance prototyping platform for the SKA telescope[2]. Kayobe is an open

[openstack-dev] [murano] MuranoPL types question

Hi Stan, I had a quick(hopefully) question about MuranoPL that I hope you might be able to help with, Felipe had mentioned you are very knowledgeable in this area. If you don't have time please disregard! I'm working on a patch for the Murano core library to make volume attachment info

Re: [openstack-dev] [murano] [heat] [cinder] MuranoPL types question

with contract on each dict entry. If you don't get contract violation exception, you can be sure that the list contains list of dicts with appropriate keys/values rather than list of strings or anything else Sincerely yours, Stan Lagun Principal Software Engineer @ Mirantis <mailto

Re: [openstack-dev] [kolla] Tags, revisions, dockerhub

I'm wondering if moving to using docker labels is a better way of solving the various issue being raised here. We can maintain a tag for each of master/ocata/newton/etc, and on each image have a LABEL with info such as 'pbr of service/pbr of kolla/link to CI of build/etc'. I believe this

Re: [openstack-dev] [kolla][keystone] better way to rotate and distribution keystone fernet keys in container env

Two initial ideas: We could create a specific ansible task to rotate the keys, and document that operator should set up a cron job on the deployment node to run this periodically. We could also look at making use of VRRP (keepalived). Potentially the cron job could run on every controller,

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

+1 On 08/03/17 08:29, Jeffrey Zhang wrote: +1 from me On Wed, Mar 8, 2017 at 2:41 PM, Michał Jastrzębski > wrote: Hello, I'd like to start voting to include Duong (duonghq) in Kolla and Kolla-ansible core teams. Voting will be open for 2

Re: [openstack-dev] [kolla] why common_options type is dictionary ?

Because its a series of key value pairs: https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml#L96-L105 Is there another type you feel would fit better? On 11/07/17 05:22, Margin Hu wrote: Hi Guys: I want to set docker_common_options parameter but find its type is

Re: [openstack-dev]  [kolla][kolla-ansible] ceph_osd error when startup ceph_osd container.

Hi, This usually means your ceph mons have failed to cluster correctly. The osd bootstrap calls 'ceph quorum_status' to ensure a successful quorum before proceeding. If the mons are blocked or otherwise unavailable this command can time out which is likely what you're seeing. Make sure the

[openstack-dev] [murano] Meeting time

Hi Felipe / Murano community, I was wondering how would people feel about revising the time for the Murano weekly meeting? Personally the current time is difficult for me to attend as it falls at the end of a work day, I also have some colleagues that would like to attend but can't at the

Re: [openstack-dev] [murano] Meeting time

:08 PM, Paul Bourke <paul.bou...@oracle.com <mailto:paul.bou...@oracle.com>> wrote: Hi Felipe / Murano community, I was wondering how would people feel about revising the time for the Murano weekly meeting? Personally the current time is difficult for me to attend as it

[openstack-dev] [murano][barbican] Encrypting sensitive properties

Hi all, I've been looking at a blueprint[0] logged for Murano which involves encrypting parts of the object model stored in the database that may contain passwords or sensitive information. I wanted to see if people had any thoughts or preferences on how this should be done. On the face of

Re: [openstack-dev] [murano][barbican] Encrypting sensitive properties

deploy murano with or without it. As for the way to convey this, I believe metadata attributes were designed to answer use-cases like this one. see https://docs.openstack.org/developer/murano/appdev-guide/murano_pl/metadata.html for more info. Regards, Kirill Le 25 мая 2017 г. à 18:49, Paul

  1   2   >