Re: [openstack-dev] [kolla] Proposing Chason Chan (chason) as kolla-ansible core

+1 On 25/09/18 16:47, Eduardo Gonzalez wrote: Hi, I would like to propose Chason Chan to the kolla-ansible core team. Chason is been working on addition of Vitrage roles, rework VpnaaS service, maintaining documentation as well as fixing many bugs. Voting will be open for 14 days (until

Re: [openstack-dev] [kolla] Dropping core reviewer

+1. Will always have good memories of when Steve was getting the project off the ground. Thanks Steve for doing a great job of building the community around Kolla, and for all your help in general! Best of luck, -Paul On 08/08/18 12:23, Eduardo Gonzalez wrote: Steve, Is sad to see you

Re: [openstack-dev] [sig][upgrades][ansible][charms][tripleo][kolla][airship] reboot or poweroff?

Hi James, Sorry to hear about the lack of participation. I for one am guilty of not taking part, there just seems to be never enough time in the day to cram in all the moving parts that a project like OpenStack requires. That being said, this effort is definitely one of the most important to

Re: [openstack-dev] [kolla] Removing old / unused images

chu...@redhat.com>> wrote: On Tue, Jun 26, 2018 at 8:05 AM, Paul Bourke mailto:paul.bou...@oracle.com>> wrote: > Hi all, > > At the weekly meeting a week or two ago, we mentioned removing some old / > unused images from Kolla in the interest of kee

[openstack-dev] [kolla] Removing old / unused images

Hi all, At the weekly meeting a week or two ago, we mentioned removing some old / unused images from Kolla in the interest of keeping the gate run times down, as well as general code hygiene. The images I've determined that are either no longer relevant, or were simply never made use of in

Re: [openstack-dev] [kolla][vote] Nominating Steve Noyes for kolla-cli core reviewer

+1 On 31/05/18 18:02, Borne Mace wrote: Greetings all, I would like to propose the addition of Steve Noyes to the kolla-cli core reviewer team.  Consider this nomination as my personal +1. Steve has a long history with the kolla-cli and should be considered its co-creator as probably half

[openstack-dev] Slides for Kolla onboarding & project update

Hi all, Here are the slide decks for these sessions. The project update should be available shortly on YouTube also. https://www.slideshare.net/PaulBourke1/kolla-onboarding-vancouver-2018 https://www.slideshare.net/PaulBourke1/kolla-project-update-vancouver-2018 Thanks, -Paul

Re: [openstack-dev] [kolla] Building Kolla containers with 3rd party vendor drivers

On 5/11/18, 5:35 AM, "Paul Bourke" <paul.bou...@oracle.com> wrote: Hi Sandhya, Thanks for starting this thread. I've moved it to the mailing list so the discussion can be available to anyone else who is interested, I hope you don't mind. If

[openstack-dev] [kolla] Building Kolla containers with 3rd party vendor drivers

be part of the kolla-ansible repo or should they be out-of-tree? It is hard to have this type of discussion on IRC so I started this email thread. Thanks, Sandhya On 5/10/18, 5:59 AM, "Paul Bourke (pbourke) (Code Review)" <rev...@openstack.org> wrote: Paul Bourke (pbourke

Re: [openstack-dev] [kolla][vote]Core nomination for Mark Goddard (mgoddard) as kolla core member

+1, always great working with Mark :) On 26/04/18 16:31, Jeffrey Zhang wrote: Kolla core reviewer team, It is my pleasure to nominate ​ mgoddard for kolla core team. ​ Mark has been working both upstream and downstream with kolla and kolla-ansible for over two years, building bare metal

Re: [openstack-dev] [kolla][vote]Retire kolla-kubernetes project

+1 On 18/04/18 02:51, Jeffrey Zhang wrote: Since many of the contributors in the kolla-kubernetes project are moved to other things. And there is no active contributor for months.  On the other hand, there is another comparable project, openstack-helm, in the community.  For less confusion

[openstack-dev] [kolla] [tripleo] On moving start scripts out of Kolla images

Hi all, This mail is to serve as a follow on to the discussion during yesterday's team meeting[4], which was regarding the desire to move start scripts out of the kolla images [0]. There's a few factors at play, and it may well be best left to discuss in person at the summit in May, but

Re: [openstack-dev] [kolla][kolla-kubernete][tc][openstack-helm]propose retire kolla-kubernetes project

+1 Thanks Jeffrey for taking the time to investigate. On 28/03/18 16:47, Jeffrey Zhang wrote: There are two projects to solve the issue that run OpenStack on Kubernetes, OpenStack-helm, and kolla-kubernetes. Them both leverage helm tool for orchestration. There is some different perspective at

Re: [openstack-dev] [kolla][vote] core nomination for caoyuan

+1 On 12/03/18 02:06, Jeffrey Zhang wrote: ​​Kolla core reviewer team, It is my pleasure to nominate caoyuan for kolla core team. caoyuan's output is fantastic over the last cycle. And he is the most active non-core contributor on Kolla project for last 180 days[1]. He focuses on

[openstack-dev] [kolla] PTG Summary

Hi all, Here's my summary of the various topics we discussed during the PTG. There were one or two I had to step out for but hopefully this serves as an overall recap. Please refer to the main etherpad[0] for more details and links to the session specific pads. build.py script refactor

Re: [openstack-dev] [kolla][ptg] Team dinner

, Paul Bourke wrote: Hey Kolla, Hope you're all enjoying Dublin so far :) Some have expressed interest in getting together for a team meal, how does Thursday sound? Please reply to this with +1/-1 and I can see about booking something. Cheers, -Paul

[openstack-dev] [kolla][ptg] Team dinner

Hey Kolla, Hope you're all enjoying Dublin so far :) Some have expressed interest in getting together for a team meal, how does Thursday sound? Please reply to this with +1/-1 and I can see about booking something. Cheers, -Paul

Re: [openstack-dev] [kolla] Rocky PTL candidacy

On 05/02/18 10:25, Christian Berendt wrote: Hello Paul. On 5. Feb 2018, at 11:12, Paul Bourke <paul.bou...@oracle.com> wrote: This does not mean I don't have a vision for Kolla - no project is perfect Regardless of that, I would be interested in your visions. What specifically do yo

[openstack-dev] [kolla] Rocky PTL candidacy

Hello all, I've been involved with Kolla since it's early stages around Liberty, where we saw it evolve through multiple iterations of image formats, orchestration methods and patterns into the project we know and love. From my perspective the community is one of the best things about

Re: [openstack-dev] [kolla] Policy regarding template customisation

On 30/01/18 12:54, Simon Leinen wrote: The perceived downside of (2) - or a perceived advantage of (1) - is that in an ideal world, (1) isolates us from the arcane configuration file details that the crazy devs of individual services come up with. In practice, it turns out that (a) those files

Re: [openstack-dev] [kolla] Policy regarding template customisation

ir in playbooks. Currently, the merge_config is a more better solutions. On Mon, Jan 29, 2018 at 7:13 PM, Paul Bourke <paul.bou...@oracle.com> wrote: Hi all, I'd like to revisit our policy of not templating everything in kolla-ansible's template files. This is a policy that was set in

[openstack-dev] [kolla] Policy regarding template customisation

Hi all, I'd like to revisit our policy of not templating everything in kolla-ansible's template files. This is a policy that was set in place very early on in kolla-ansible's development, but I'm concerned we haven't been very consistent with it. This leads to confusion for contributors and

[openstack-dev] [zuul] Cannot view log outputs in browser

Apologies if this has been asked before. It seems as of late (I think since the roll out of zuul v3, I can't seem to view job outputs directly in my browser. E.g. when I click link[0], I have to download 'job-output.txt.gz', unzip it, rename the extension to '.html', and finally open it in a

Re: [openstack-dev] [castellan] Removing Keystoneauth Dependency in Castellan Discussion

From my understanding it would be a cleanup operation - which to be honest, would be very much welcomed. I recently did a little work with Castellan to integrate it with Murano and found the auth code to be very messy, and flat out broken in some cases. If it's possible to let the barbican

Re: [openstack-dev] [kolla] Ansiblize init-runonce script

I think this came up before at one stage. My position is I don't see the need to ansible-ise small shell scripts. init-runonce is currently just an easy to understand sequence of openstack commands provided to help people test/demo their setups. Unless we want to make it more than that, i.e.

Re: [openstack-dev] [kolla] Proposal to add Marcin (hrw) to kolla images core team

+1 On 02/11/17 15:58, Michał Jastrzębski wrote: It's my great pleasure to start another voting for core team addition! Everyone knows hrw, thanks to him Kolla now runs on both Power and ARM! Voting will be open for 14 days (until 16th of Nov). Consider this mail my +1 vote Regards, Michal

Re: [openstack-dev] [all] review.openstack.org downtime and Gerrit upgrade TODAY 15:00 UTC - 23:59 UTC

I had the following bookmark: status:open is:mergeable (project:openstack/kolla OR project:openstack/kolla-ansible) NOT label:Code-Review>=-2,self NOT owner:pauldbourke NOT age:1month branch:master Which basically means, find changes that are: * open * in kolla or kolla-ansible * not

[openstack-dev] [murano] ptg meetup

Hi, Would those of us at the PTG like to agree on a time to meet for an informal Murano chat? Does Friday suit? Regards, -Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

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

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] Proposing Surya (spsurya) for core

+1, thanks Surya for all your work On 14/06/17 16:46, Michał Jastrzębski wrote: Hello, With great pleasure I'm kicking off another core voting to kolla-ansible and kolla teams:) this one is about spsurya. Voting will be open for 2 weeks (till 28th Jun). Consider this mail my +1 vote, you know

[openstack-dev] [murano] [barbican] Re: Need your opinion on another issue...

Hi Stan, Thanks for your input on this. I'm finding the problem with doing the encryption/decryption on the engine side only is that at this point it is too late - the object model has already been written into the database at the API layer. I can't think how we can change this without

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

[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] 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] 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] [kolla][kolla-ansible] Proposing Bertrand Lallau for kolla and kolla-ansible core

+1 of course from myself. Good job Bertrand. On 02/05/17 16:30, Michał Jastrzębski wrote: Hello, It's my pleasure to start another core reviewer vote. Today it's Bertrand (blallau). Consider this mail my +1 vote. Members of kolla-ansible and kolla core team, please cast your votes:) Voting

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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)"

[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

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

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

  1   2   >