Re: [openstack-dev] [tripleo] Unbranched repositories and testing

On 5.10.2017 22:40, Alex Schultz wrote: Hey folks, So I wandered across the policy spec[0] for how we should be handling unbranched repository reviews and I would like to start a broader discussion around this topic. We've seen it several times over the recent history where a change in oooqe

Re: [openstack-dev] [tripleo] Pacemaker + containers CI

On 29.8.2017 17:12, Emilien Macchi wrote: On Tue, Aug 29, 2017 at 2:14 AM, Jiří Stránský <ji...@redhat.com> wrote: [...] the CI for containerized deployments with Pacemaker is close! In fact, it works [1][2] (but there are pending changes to merge). Really good news, thanks for the

Re: [openstack-dev] [tripleo] Adding new roles after upgrade is broken.

On 18.8.2017 17:25, Marios Andreou wrote: On Fri, Aug 18, 2017 at 4:22 PM, Jiří Stránský <ji...@redhat.com> wrote: On 18.8.2017 13:18, Sofer Athlan-Guyot wrote: Hi, We may have missing packages when the user is adding a new role to its roles_data file and the base image is comin

[openstack-dev] [tripleo] Pacemaker + containers CI

Hi owls, the CI for containerized deployments with Pacemaker is close! In fact, it works [1][2] (but there are pending changes to merge). The way it's proposed in gerrit currently is to switch the centos-7-containers-multinode job (featureset010) to deploy with Pacemaker. What do you think

Re: [openstack-dev] [tripleo] Gate is broken - Do not approve any patch until further notice

On 30.8.2017 06:54, Emilien Macchi wrote: On Tue, Aug 29, 2017 at 4:17 PM, Emilien Macchi wrote: We are currently dealing with 4 issues and until they are fix, please do not approve any patch. We want to keep the gate clear to merge the fixes for the 4 problems first. 1)

Re: [openstack-dev] [tripleo] Pacemaker + containers CI

On 29.8.2017 13:22, Giulio Fidente wrote: On 08/29/2017 11:14 AM, Jiří Stránský wrote: Hi owls, the CI for containerized deployments with Pacemaker is close! In fact, it works [1][2] (but there are pending changes to merge). cool :D I also spotted this which we need for ceph https

Re: [openstack-dev] [tripleo] Pacemaker + containers CI

On 29.8.2017 14:42, Giulio Fidente wrote: On 08/29/2017 02:33 PM, Jiří Stránský wrote: A bit of context: Currently our only upgrade check job is non-OVB - containers-multinode-upgrades-nv. As of late we started hitting timeouts, and the job only does mixed-version deploy + 1 node AIO overcloud

Re: [openstack-dev] [TripleO] Proposing Ronelle Landy for Tripleo-Quickstart/Extras/CI core

+1 On 29.11.2017 20:34, John Trowbridge wrote: I would like to propose Ronelle be given +2 for the above repos. She has been a solid contributor to tripleo-quickstart and extras almost since the beginning. She has solid review numbers, but more importantly has always done quality reviews. She

Re: [openstack-dev] [tripleo] Updates on the TripleO on Kubernetes work

Kubernetes on the overcloud === The work on this front started with 2[0][1] patches that some of you might have seen and then evolved into using the config download mechanism to execute these tasks as part of the undercloud tasks[2][3] (Thanks a bunch, Jiri, for your work

Re: [openstack-dev] [tripleo] Help needed on debugging upgrade jobs on Pike

On 6.11.2017 10:52, Marios Andreou wrote: On Mon, Nov 6, 2017 at 11:09 AM, Marius Cornea wrote: On Sat, Nov 4, 2017 at 2:27 AM, Emilien Macchi wrote: Since we've got promotion, we can now properly test upgrades from ocata to pike. It's now failing

Re: [openstack-dev] [tripleo] Nominate chem and matbu for tripleo-core !

+1! On 9.11.2017 09:48, Marios Andreou wrote: Hello fellow owls, (appologies for duplicate, forgot to add the tripleo in subject so worried it would be missed) I would like to nominate (and imo these are both long overdue already): Sofer Athlan Guyot (chem) and Mathieu Bultel (matbu) to

Re: [openstack-dev] [tripleo] Proposing John Fulton core on TripleO

+1! On 8.11.2017 23:24, Giulio Fidente wrote: Hi, I would like to propose John Fulton core on TripleO. I think John did an awesome work during the Pike cycle around the integration of ceph-ansible as a replacement for puppet-ceph, for the deployment of Ceph in containers. I think John has

Re: [openstack-dev] [tripleo] Nominate akrivoka for tripleo-validations core

+1! On 6.11.2017 15:32, Honza Pokorny wrote: Hello people, I would like to nominate Ana Krivokapić (akrivoka) for the core team for tripleo-validations. She has really stepped up her game on that project in terms of helpful reviews, and great patches. With Ana's help as a core, we can get

Re: [openstack-dev] [tripleo]

On 7.11.2017 23:29, Wesley Hayutin wrote: Greetings, I'd like to propose we remove the upgrade jobs that are consistently failing from the upstream infrastructure and instead focus our efforts in RDO Software Factory. The jobs listed in https://review.openstack.org/#/c/518405/ are consistently

Re: [openstack-dev] [tripleo] Help needed on debugging upgrade jobs on Pike

On 6.11.2017 11:17, Jiří Stránský wrote: On 6.11.2017 10:52, Marios Andreou wrote: On Mon, Nov 6, 2017 at 11:09 AM, Marius Cornea <mari...@redhat.com> wrote: On Sat, Nov 4, 2017 at 2:27 AM, Emilien Macchi <emil...@redhat.com> wrote: Since we've got promotion, we can now p

Re: [openstack-dev] [tripleo] Updates on the TripleO on Kubernetes work

On 21.11.2017 12:01, Jiří Stránský wrote: Kubernetes on the overcloud === The work on this front started with 2[0][1] patches that some of you might have seen and then evolved into using the config download mechanism to execute these tasks as part of the undercloud tasks

Re: [openstack-dev] [tripleo] Proposing Wesley Hayutin core on TripleO CI

+1 On 6.12.2017 16:45, Emilien Macchi wrote: Team, Wes has been consistently and heavily involved in TripleO CI work. He has a very well understanding on how tripleo-quickstart and tripleo-quickstart-extras work, his number and quality of reviews are excellent so far. His experience with

[openstack-dev] [tripleo] Zuul repo insertion in update/upgrade CI

Hi, this is mainly for CI folks and whom-it-may-concern. Recently we came across the topic of how to enable/disable zuul repos at various places in the CI jobs. For normal deploy jobs there's no need to customize, but for update/upgrade jobs there is. It's not entirely straightforward and

Re: [openstack-dev] [tripleo] scenario000-multinode-oooq-container-upgrades

On 12.6.2018 15:06, James Slagle wrote: On Mon, Jun 11, 2018 at 3:34 PM, Wesley Hayutin wrote: Greetings, I wanted to let everyone know that we have a keystone only deployment and upgrade job in check non-voting. I'm asking everyone in TripleO to be mindful of this job and to help make sure

Re: [openstack-dev] [tripleo] Proposing Alan Bishop tripleo core on storage bits

+1 On 13.6.2018 17:50, Emilien Macchi wrote: Alan Bishop has been highly involved in the Storage backends integration in TripleO and Puppet modules, always here to update with new features, fix (nasty and untestable third-party backends) bugs and manage all the backports for stable releases:

Re: [openstack-dev] DeployArtifacts considered...complicated?

On 19.6.2018 16:29, Lars Kellogg-Stedman wrote: On Tue, Jun 19, 2018 at 02:18:38PM +0100, Steven Hardy wrote: Is this the same issue Carlos is trying to fix via https://review.openstack.org/#/c/494517/ ? That solves part of the problem, but it's not a complete solution. In particular, it

Re: [openstack-dev] [tripleo] how to reproduce tripleo ci

On 6.2.2018 19:58, Wesley Hayutin wrote: Greetings, The TripleO-CI team has added a recreate / reproduce script to all the tripleo upstream ci jobs as an artifact [1-2] much like the devstack reproduce.sh script. If you find yourself in need of recreating a tripleo ci job please take a look at

[openstack-dev] [tripleo] Rocky Ceph update/upgrade regression risk (semi-FFE)

Hi folks, i want to raise attention on remaining patches that are needed to prevent losing Ceph updates/upgrades in Rocky [1], basically making the Ceph upgrade mechanism compatible with config-download. I'd call this a semi-FFE, as a few of the patches have characteristics of feature work,

Re: [openstack-dev] [tripleo] Proposing Lukas Bezdicka core on TripleO

+1! On 1.8.2018 13:31, Giulio Fidente wrote: Hi, I would like to propose Lukas Bezdicka core on TripleO. Lukas did a lot work in our tripleoclient, tripleo-common and tripleo-heat-templates repos to make FFU possible. FFU, which is meant to permit upgrades from Newton to Queens, requires in

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On 15.8.2018 11:32, Cédric Jeanneret wrote: Dear Community, As you may know, a move toward Podman as replacement of Docker is starting. One of the issues with podman is the lack of daemon, precisely the lack of a socket allowing to send commands and get a "computer formatted output" (like JSON

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On 16.8.2018 10:38, Steven Hardy wrote: On Wed, Aug 15, 2018 at 10:48 PM, Jay Pipes wrote: On 08/15/2018 04:01 PM, Emilien Macchi wrote: On Wed, Aug 15, 2018 at 5:31 PM Emilien Macchi mailto:emil...@redhat.com>> wrote: More seriously here: there is an ongoing effort to converge the

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On 16.8.2018 07:39, Cédric Jeanneret wrote: On 08/16/2018 12:10 AM, Jason E. Rist wrote: On 08/15/2018 03:32 AM, Cédric Jeanneret wrote: Dear Community, As you may know, a move toward Podman as replacement of Docker is starting. One of the issues with podman is the lack of daemon,

Re: [openstack-dev] [tripleo][Edge][FEMDC] Edge clouds and controlplane updates

On 14.8.2018 15:19, Bogdan Dobrelya wrote: On 8/13/18 9:47 PM, Giulio Fidente wrote: Hello, I'd like to get some feedback regarding the remaining work for the split controlplane spec implementation [1] Specifically, while for some services like nova-compute it is not necessary to update the

Re: [openstack-dev] [tripleo] Proposing Jose Luis Franco for TripleO core reviewer on Upgrade bits

+1! On 20.7.2018 10:07, Carlos Camacho Gonzalez wrote: Hi!!! I'll like to propose Jose Luis Franco [1][2] for core reviewer in all the TripleO upgrades bits. He shows a constant and active involvement in improving and fixing our updates/upgrades workflows, he helps also trying to

Re: [openstack-dev] [tripleo] quickstart for humans

On 30.8.2018 16:28, Honza Pokorny wrote: Hello! Over the last few months, it seems that tripleo-quickstart has evolved into a CI tool. It's primarily used by computers, and not humans. tripleo-quickstart is a helpful set of ansible playbooks, and a collection of feature sets. However, it's

[openstack-dev] [tripleo] Updates/upgrades equivalent for external_deploy_tasks

Hi, with the move to config-download deployments, we'll be moving from executing external installers (like ceph-ansible) via Heat resources encapsulating Mistral workflows towards executing them via Ansible directly (nested Ansible process via external_deploy_tasks). Updates and upgrades

Re: [openstack-dev] [tripleo] Updates/upgrades equivalent for external_deploy_tasks

Thanks for the feedback, John and Emilien. On 13.7.2018 01:35, Emilien Macchi wrote: +1 for Option A as well, I feel like it's the one which would give us the more of flexibility and also I'm not a big fan of the usage of Anchors for this use case. Some folks are currently working on extracting

Re: [openstack-dev] [tripleo][ci] use of tags in launchpad bugs

On 5.4.2018 21:04, Alex Schultz wrote: On Thu, Apr 5, 2018 at 12:55 PM, Wesley Hayutin wrote: FYI... This is news to me so thanks to Emilien for pointing it out [1]. There are official tags for tripleo launchpad bugs. Personally, I like what I've seen recently with some

Re: [openstack-dev] [tripleo] Proposing Marius Cornea core on upgrade bits

+1! On 19.4.2018 19:01, Emilien Macchi wrote: Greetings, As you probably know mcornea on IRC, Marius Cornea has been contributing on TripleO for a while, specially on the upgrade bits. Part of the quality team, he's always testing real customer scenarios and brings a lot of good feedback in

Re: [openstack-dev] [tripleo] Proposing Enrique Llorente Pastora as a core reviewer for TripleO

On 15. 11. 18 16:54, Wesley Hayutin wrote: On Thu, Nov 15, 2018 at 8:52 AM Sagi Shnaidman wrote: Hi, I'd like to propose Quique (@quiquell) as a core reviewer for TripleO. Quique is actively involved in improvements and development of TripleO and TripleO CI. He also helps in other projects

Re: [openstack-dev] [tripleo] [quickstart] [networking-ovn] No more overcloud_prep-containers.sh script

Yes I know, but based on the deployment details we have for networking-ovn it should be enough, we will have to update those documents with the new changes anyway, because surprisingly this change has came for "Rocky" last minute. Why did we have such last minute change? :-/ I understand the

Re: [openstack-dev] [tripleo] [quickstart] [networking-ovn] No more overcloud_prep-containers.sh script

On 03/10/2018 10:14, Miguel Angel Ajo Pelayo wrote: Hi folks I was trying to deploy neutron with networking-ovn via tripleo-quickstart scripts on master, and this config file [1]. It doesn't work, overcloud deploy cries with: 1) trying to deploy ovn I end up with a 2018-10-02 17:48:12 |

Re: [openstack-dev] [Tripleo] Automating role generation

On 4.9.2018 08:13, Janki Chhatbar wrote: Hi I am looking to automate role file generation in TripleO. The idea is basically for an operator to create a simple yaml file (operator.yaml, say) listing services that are needed and then TripleO to generate Controller.yaml enabling only those

Re: [openstack-dev] [TripleO] Removing global bootstrap_nodeid?

Hi Steve, On 25/09/2018 10:51, Steven Hardy wrote: Hi all, After some discussions with bandini at the PTG, I've been taking a look at this bug and how to solve it: https://bugs.launchpad.net/tripleo/+bug/1792613 (Also more information in downstream bz1626140) The problem is that we always

Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes

From: Jiří Stránský [ji...@redhat.com] Sent: Thursday, November 29, 2018 9:42 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes On 28. 11. 18 18:29, Bogdan Dobrelya

Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes

On 28. 11. 18 18:29, Bogdan Dobrelya wrote: On 11/28/18 6:02 PM, Jiří Stránský wrote: Reiterating again on previous points: -I'd be fine removing systemd. But lets do it properly and not via 'rpm -ev --nodeps'. -Puppet and Ruby *are* required for configuration. We can certainly put them

Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes

Reiterating again on previous points: -I'd be fine removing systemd. But lets do it properly and not via 'rpm -ev --nodeps'. -Puppet and Ruby *are* required for configuration. We can certainly put them in a separate container outside of the runtime service containers but doing so would

Re: [openstack-dev] [openstack-ansible][kolla-ansible][tripleo] ansible roles: where they live and what do they do

On 11.9.2018 18:53, Alex Schultz wrote: Thanks everyone for coming and chatting. From the meeting we've had a few items where we can collaborate together. Here are some specific bullet points: - TripleO folks should feel free to propose some minor structural changes if they make the

<    1   2