Re: [openstack-dev] [puppet] [stable] Deprecation of newton branches

On Mon, Nov 19, 2018 at 1:18 AM Tobias Urdin wrote: > > Hello, > > We've been talking for a while about the deprecation and removal of the > stable/newton branches. > I think it's time now that we get rid of them, we have no open patches > and Newton is considered EOL. > > Could cores get back

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

+1 On Thu, Nov 15, 2018 at 8:51 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 including but not limited to >

[openstack-dev] [tripleo] puppet5 has broken the master gate

Just a heads up but we recently updated to puppet5 in the master dependencies. It appears that this has completely hosed the master scenarios and containers-multinode jobs. Please do recheck/approve anything until we get this resolved. See https://bugs.launchpad.net/tripleo/+bug/1803024 I have

Re: [openstack-dev] [tripleo] Zuul Queue backlogs and resource usage

ed to figure out the correct way forward with these packages. Thanks, -Alex [0] https://review.openstack.org/#/c/550848/ > On 10/31/18 6:35 PM, Alex Schultz wrote: > > > > So this is a single layer that is updated once and shared by all the > > containers that inherit from i

Re: [openstack-dev] [tripleo] gate issues please do not approve/recheck

is much better. Thanks, -Alex On Wed, Oct 31, 2018 at 9:39 AM Alex Schultz wrote: > > Hey folks, > > So we have identified an issue that has been causing a bunch of > failures and proposed a revert of our podman testing[0]. We have > cleared the gate and are asking that you not appr

Re: [openstack-dev] [tripleo] Zuul Queue backlogs and resource usage

On Wed, Oct 31, 2018 at 11:16 AM Harald Jensås wrote: > > On Tue, 2018-10-30 at 15:00 -0600, Alex Schultz wrote: > > On Tue, Oct 30, 2018 at 12:25 PM Clark Boylan > > wrote: > > > > > > On Tue, Oct 30, 2018, at 10:42 AM, Alex Schultz wrote: > > >

[openstack-dev] [tripleo] reducing our upstream CI footprint

Hey everyone, Based on previous emails around this[0][1], I have proposed a possible reducing in our usage by switching the scenario001--011 jobs to non-voting and removing them from the gate[2]. This will reduce the likelihood of causing gate resets and hopefully allow us to land corrective

[openstack-dev] [tripleo] gate issues please do not approve/recheck

Hey folks, So we have identified an issue that has been causing a bunch of failures and proposed a revert of our podman testing[0]. We have cleared the gate and are asking that you not approve or recheck any patches at this time. We will let you know when it is safe to start approving things.

Re: [openstack-dev] [tripleo] Zuul Queue backlogs and resource usage

On Tue, Oct 30, 2018 at 12:25 PM Clark Boylan wrote: > > On Tue, Oct 30, 2018, at 10:42 AM, Alex Schultz wrote: > > On Tue, Oct 30, 2018 at 11:36 AM Ben Nemec wrote: > > > > > > Tagging with tripleo since my suggestion below is specific to that > > > pr

Re: [openstack-dev] [tripleo] Zuul Queue backlogs and resource usage

On Tue, Oct 30, 2018 at 11:36 AM Ben Nemec wrote: > > Tagging with tripleo since my suggestion below is specific to that project. > > On 10/30/18 11:03 AM, Clark Boylan wrote: > > Hello everyone, > > > > A little while back I sent email explaining how the gate queues work and > > how fixing bugs

[openstack-dev] [tripleo] retirement of instack

With the proposed retirement of instack-undercloud[0], we will no longer be supporting future development of the instack project as well. As with instack-undercloud, we will continue to support the stable branches of instack for their life but will not being doing any future development. Please

[openstack-dev] [puppet][tripleo] puppet 5.5.7 breaks a bunch of stuff

Just a heads up. I've been battling with some unit test issues with the latest version of puppet 5.5. I've proposed some fixes[0][1], but it appears that there is a larger issue with legacy functions which affects the stable branches. I've reported the issues[2][3] upstream to Puppetlabs, but

[openstack-dev] [tripleo] retirement of instack-undercloud

We have officially moved off of the instack-undercloud deployment process in Rocky and have officially removed it's support from python-tripleoclient in Stein. In order to prevent confusion I have proposed a patch to start the retirement of instack-undercloud[0]. We will continue to support the

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Thu, Oct 25, 2018 at 9:16 AM Bogdan Dobrelya wrote: > > > On 10/19/18 8:04 PM, Alex Schultz wrote: > > On Fri, Oct 19, 2018 at 10:53 AM James Slagle > > wrote: > >> > >> On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz > >> wrote: > >

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Fri, Oct 19, 2018 at 10:53 AM James Slagle wrote: > > On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz wrote: > > Additionally I took a stab at combining the puppet/docker service > > definitions for the aodh services in a similar structure to start > > reducing the

Re: [openstack-dev] [tripleo] Proposing Bob Fournier as core reviewer

+1 On Fri, Oct 19, 2018 at 6:29 AM Emilien Macchi wrote: > > On Fri, Oct 19, 2018 at 8:24 AM Juan Antonio Osorio Robles > wrote: >> >> I would like to propose Bob Fournier (bfournie) as a core reviewer in >> TripleO. His patches and reviews have spanned quite a wide range in our >> project, his

Re: [openstack-dev] [TripleO] easily identifying how services are configured

Time to resurrect this thread. On Thu, Jul 5, 2018 at 12:14 PM James Slagle wrote: > > On Thu, Jul 5, 2018 at 1:50 PM, Dan Prince wrote: > > Last week I was tinkering with my docker configuration a bit and was a > > bit surprised that puppet/services/docker.yaml no longer used puppet to > >

Re: [openstack-dev] [tripleo][puppet] clearing the gate and landing patches to help CI

And master is blocked again. We need https://review.openstack.org/#/c/607952/ Thanks, -Alex On Fri, Sep 28, 2018 at 9:02 AM Alex Schultz wrote: > > Hey Folks, > > Currently the tripleo gate is at 21 hours and we're continue to have > timeouts and now scenario001/004 (in quee

[openstack-dev] [tripleo][puppet] clearing the gate and landing patches to help CI

Hey Folks, Currently the tripleo gate is at 21 hours and we're continue to have timeouts and now scenario001/004 (in queens/pike) appear to be broken. Additionally we've got some patches in puppet-openstack that we need to land in order to resolve broken puppet unit tests which is affecting both

Re: [openstack-dev] Are we ready to put stable/ocata into extended maintenance mode?

On Tue, Sep 18, 2018 at 1:27 PM, Matt Riedemann wrote: > The release page says Ocata is planned to go into extended maintenance mode > on Aug 27 [1]. There really isn't much to this except it means we don't do > releases for Ocata anymore [2]. There is a caveat that project teams that do > not

Re: [openstack-dev] [TripleO] Regarding dropping Ocata related jobs from TripleO

io Robles wrote: >> >> >> On 09/14/2018 09:01 AM, Alex Schultz wrote: >>> >>> On Fri, Sep 14, 2018 at 6:37 AM, Chandan kumar >>> wrote: >>>> >>>> Hello, >>>> >>>> As Ocata release is already EOL on 27-08

Re: [openstack-dev] [TripleO] Regarding dropping Ocata related jobs from TripleO

On Fri, Sep 14, 2018 at 6:37 AM, Chandan kumar wrote: > Hello, > > As Ocata release is already EOL on 27-08-2018 [1]. > In TripleO, we are running Ocata jobs in TripleO CI and in promotion > pipelines. > Can we drop it all the jobs related to Ocata or do we need to keep some jobs > to support

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

. - Shared roles are open for reuse/replacement if something better is available (upstream/elsewhere). If anyone has any others, feel free to comment. Thanks, -Alex On Mon, Sep 10, 2018 at 10:58 AM, Alex Schultz wrote: > I just realized I booked the room and put it in the etherpad but >

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

I just realized I booked the room and put it in the etherpad but forgot to email out the time. Time: Tuesday 09:00-10:45 Room: Big Thompson https://etherpad.openstack.org/p/ansible-collaboration-denver-ptg Thanks, -Alex On Tue, Sep 4, 2018 at 1:03 PM, Alex Schultz wrote: > On Thu, Aug 9, 2

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

e collaboration and some basic ideas for best practice items that we can discuss. Feel free to add your own and I'll update the etherpad with a time slot when I get one nailed down. Thanks, -Alex [0] https://etherpad.openstack.org/p/ansible-collaboration-denver-ptg > I'll let others chime in as well

Re: [openstack-dev] [tripleo] using multiple roles

t; On Tue, Sep 4, 2018 at 4:52 PM Alex Schultz wrote: >> >> On Tue, Sep 4, 2018 at 2:31 AM, Samuel Monderer >> wrote: >> > Hi, >> > >> > Due to many different HW in our environment we have multiple roles. >> > I would like to place each role defini

Re: [openstack-dev] [tripleo] using multiple roles

On Tue, Sep 4, 2018 at 2:31 AM, Samuel Monderer wrote: > Hi, > > Due to many different HW in our environment we have multiple roles. > I would like to place each role definition if a different file. > Is it possible to refer to all the roles from roles_data.yaml to all the > different files

Re: [openstack-dev] [tripleo] Rocky RC1 released!

On Fri, Aug 24, 2018 at 9:09 AM, Emilien Macchi wrote: > We just released Rocky RC1 and branched stable/rocky for most of tripleo > repos, please let us know if we missed something. > Please don't forget to backport the patches that land in master and that you > want in Rocky. > > We're currently

Re: [openstack-dev] [release] Release countdown for week R-0, August 27 - 31

On Thu, Aug 23, 2018 at 10:12 AM, Sean McGinnis wrote: > This is the final countdown email for the Rocky development cycle. Thanks to > everyone involved in the Rocky release! > > Development Focus > - > > Teams attending the PTG should be preparing for those discussions and >

Re: [openstack-dev] [tripleo] fedora28 python3 test environment

On Fri, Aug 17, 2018 at 5:18 PM, Alex Schultz wrote: > Ahoy folks, > > In order to get to a spot where can start evaluate the current status > of TripleO under python3 I've thrown together a set of ansible > playbooks[0] to launch a fedora28 node and build the required > py

[openstack-dev] [tripleo] fedora28 python3 test environment

Ahoy folks, In order to get to a spot where can start evaluate the current status of TripleO under python3 I've thrown together a set of ansible playbooks[0] to launch a fedora28 node and build the required python-tripleoclient (and dependencies) These playbooks will spawn a VM on an OpenStack

[openstack-dev] [tripleo] CI is blocked

Please do not approve or recheck anything until further notice. We've got a few issues that have basically broken all the jobs. https://bugs.launchpad.net/tripleo/+bug/1786764 https://bugs.launchpad.net/tripleo/+bug/1787226 https://bugs.launchpad.net/tripleo/+bug/1787244

Re: [openstack-dev] [tripleo] ansible roles in tripleo

On Tue, Aug 14, 2018 at 11:51 AM, Jill Rouleau wrote: > Hey folks, > > Like Alex mentioned[0] earlier, we've created a bunch of ansible roles > for tripleo specific bits. The idea is to start putting some basic > cookiecutter type things in them to get things started, then move some >

Re: [openstack-dev] [releases][requirements][cycle-with-intermediary][cycle-trailing] requirements is going to branch stable/rocky at ~08-15-2018 2100Z

On Tue, Aug 14, 2018 at 10:13 AM, Matthew Thode wrote: .. snip .. > ansible-role-container-registry > ansible-role-redhat-subscription > ansible-role-tripleo-modify-image > instack-undercloud > os-apply-config > os-collect-config > os-net-config > os-refresh-config > paunch >

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

On Thu, Aug 9, 2018 at 2:56 PM, Doug Hellmann wrote: > Excerpts from Alex Schultz's message of 2018-08-09 14:31:34 -0600: >> Ahoy folks, >> >> I think it's time we come up with some basic rules/patterns on where >> code lands when it comes to OpenStack related Ansible roles and as we >>

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

Ahoy folks, I think it's time we come up with some basic rules/patterns on where code lands when it comes to OpenStack related Ansible roles and as we convert/export things. There was a recent proposal to create an ansible-role-tempest[0] that would take what we use in

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

+1 On Mon, Aug 6, 2018 at 7:19 AM, Bogdan Dobrelya wrote: > +1 > > On 8/1/18 1:31 PM, 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

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Thu, Aug 2, 2018 at 11:32 PM, Cédric Jeanneret wrote: > > > On 08/02/2018 11:41 PM, Steve Baker wrote: >> >> >> On 02/08/18 13:03, Alex Schultz wrote: >>> On Mon, Jul 9, 2018 at 6:28 AM, Bogdan Dobrelya >>> wrote: >>>> On 7/6/18 7:02 P

Re: [openstack-dev] [TripleO] easily identifying how services are configured

On Mon, Jul 9, 2018 at 6:28 AM, Bogdan Dobrelya wrote: > On 7/6/18 7:02 PM, Ben Nemec wrote: >> >> >> >> On 07/05/2018 01:23 PM, Dan Prince wrote: >>> >>> On Thu, 2018-07-05 at 14:13 -0400, James Slagle wrote: I would almost rather see us organize the directories by service

Re: [openstack-dev] [tripleo][ci][metrics] FFE request for QDR integration in TripleO (Was: Stucked in the middle of work because of RDO CI)

On Tue, Jul 31, 2018 at 11:31 AM, Pradeep Kilambi wrote: > Hi Alex: > > Can you consider this our FFE for the QDR patches. Its mainly blocked on CI > issues. Half the patches for QDR integration are already merged. The other 3 > referenced need to get merged once CI passes. Please consider this

Re: [openstack-dev] [tripleo] deployement fails

On Mon, Jul 30, 2018 at 8:48 AM, Samuel Monderer wrote: > Hi, > > I'm trying to deploy a small environment with one controller and one compute > but i get a timeout with no specific information in the logs > > 2018-07-30 13:19:41Z [overcloud.Controller.0.ControllerConfig]: > CREATE_IN_PROGRESS

Re: [openstack-dev] [tripleo] The Weekly Owl - 25th Edition

On Mon, Jul 30, 2018 at 8:32 AM, Martin Magr wrote: > > > On Tue, Jul 17, 2018 at 6:12 PM, Emilien Macchi wrote: >> >> Your fellow reporter took a break from writing, but is now back on his >> pen. >> >> Welcome to the twenty-fifth edition of a weekly update in TripleO world! >> The goal is to

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

On Fri, Jul 27, 2018 at 5:48 AM, Emilien Macchi wrote: > > > On Fri, Jul 27, 2018 at 3:58 AM Jiří Stránský wrote: >> >> I'd call this a semi-FFE, as a few of the patches have characteristics of >> feature work, >> but at the same time i don't believe we can afford having Ceph >> unupgradable in

Re: [openstack-dev] [tripleo] FFE request for config-download-ui

On Thu, Jul 26, 2018 at 2:31 AM, Jiri Tomasek wrote: > Hello, > > I would like to request a FFE for [1]. Current status of TripleO UI patches > is here [2] there are last 2 patches pending review which currently depend > on [3] which is close to land. > > [1]

Re: [openstack-dev] [tripleo] FFE request for container-prepare-workflow

On Wed, Jul 25, 2018 at 3:50 PM, Steve Baker wrote: > I'd like to request a FFE for this blueprint[1]. > > The remaining changes will be tracked as Depends-On on this oooq change[2]. > > Initially the aim of this blueprint was to do all container prepare > operations in a mistral action before

[openstack-dev] [tripleo] PTL non-candidacy

Hey folks, So it's been great fun and we've accomplished much over the last two cycles but I believe it is time for me to step back and let someone else do the PTLing. I'm not going anywhere so I'll still be around to focus on the simplification and improvements that TripleO needs going forward.

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

+1 On Fri, Jul 20, 2018 at 2:07 AM, 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

Re: [openstack-dev] [kolla][nova][tripleo] Safe guest shutdowns with kolla?

On Fri, Jul 13, 2018 at 1:54 AM, Bogdan Dobrelya wrote: > [Added tripleo] > > It would be nice to have this situation verified/improved for containerized > libvirt for compute nodes deployed with TripleO as well. > > On 7/12/18 11:02 PM, Clint Byrum wrote: >> >> Greetings! We've been deploying

Re: [openstack-dev] [tripleo][pre] removing default ssh rule from tripleo::firewall::pre

On Thu, Jul 12, 2018 at 8:17 PM, Lars Kellogg-Stedman wrote: > I've had a few operators complain about the permissive rule tripleo > creates for ssh. The current alternatives seems to be to either disable > tripleo firewall management completely, or move from the default-deny > model to a set of

[openstack-dev] [tripleo] Rocky blueprints

Hello everyone, As milestone 3 is quickly approaching, it's time to review the open blueprints[0] and their status. It appears that we have made good progress on implementing significant functionality this cycle but we still have some open items. Below is the list of blueprints that are still

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

On Tue, Jun 26, 2018 at 8:05 AM, Paul Bourke 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 keeping the gate run times down, > as well as general code hygiene. > > The images I've determined that are

Re: [openstack-dev] [tripleo] CI is down stop workflowing

On Tue, Jun 19, 2018 at 1:45 PM, Wesley Hayutin wrote: > Check and gate jobs look clear. > More details on a bit. > So for a recap of the last 24 hours or so... Mistral auth problems - https://bugs.launchpad.net/tripleo/+bug/1777541 - caused by https://review.openstack.org/#/c/574878/ -

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

On Tue, Jun 19, 2018 at 9:17 AM, Jiří Stránský wrote: > 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

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

On Wed, Jun 13, 2018 at 9:50 AM, 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

Re: [openstack-dev] [cloudkitty] configuration, deployment or packaging issue?

On Mon, Jun 18, 2018 at 4:08 PM, Tobias Urdin wrote: > Hello CloudKitty team, > > > I'm having an issue with this review not going through and being stuck after > staring at it for a while now [1]. > > Is there any configuration[2] issue that are causing the error[3]? Or is the > package broken?

Re: [openstack-dev] Puppet debugging help?

On Mon, Jun 18, 2018 at 9:13 AM, Lars Kellogg-Stedman wrote: > Hey folks, > > I'm trying to patch puppet-keystone to support multi-valued > configuration options (like trusted_dashboard). I have a patch that > works, mostly, but I've run into a frustrating problem (frustrating > because it would

Re: [openstack-dev] [tripleo] Status of Standalone installer (aka All-In-One)

On Mon, Jun 4, 2018 at 6:26 PM, Emilien Macchi wrote: > TL;DR: we made nice progress and you can checkout this demo: > https://asciinema.org/a/185533 > > We started the discussion back in Dublin during the last PTG. The idea of > Standalone (aka All-In-One, but can be mistaken with all-in-one

Re: [openstack-dev] [tripleo] Migration to Storyboard

ue. Let's focus on the Rocky work and push this to early Stein instead. I'll talk about this in the next IRC meeting if anyone wishes to discuss further. Thanks, -Alex > Thanks, > Michele > >> Thanks, >> >> On Tue, May 15, 2018 at 7:53 AM, Alex Schultz wrote: >> >> &g

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

+1 On Wed, Jun 13, 2018 at 9:50 AM, 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

Re: [openstack-dev] [tripleo][puppet] Hello all, puppet modules

On Wed, May 30, 2018 at 3:18 PM, Remo Mattei wrote: > Hello all, > I have talked to several people about this and I would love to get this > finalized once and for all. I have checked the OpenStack puppet modules > which are mostly developed by the Red Hat team, as of right now, TripleO is >

Re: [openstack-dev] [Release-job-failures][tripleo] Release of openstack/tripleo-validations failed

On Tue, May 29, 2018 at 9:31 AM, Doug Hellmann wrote: > Excerpts from zuul's message of 2018-05-29 14:28:57 +: >> Build failed. >> >> - release-openstack-python >> http://logs.openstack.org/26/26956a27b95550e2162243da79d62bb1b19d50d7/release/release-openstack-python/2bd7f7d/ >> :

Re: [openstack-dev] [tripleo][ci][infra] Quickstart Branching

n/ [2] http://git.openstack.org/cgit/openstack/ansible-role-tripleo-keystone/ [3] http://git.openstack.org/cgit/openstack/puppet-openstacklib/ [4] https://review.openstack.org/#/c/565856/ [5] https://review.openstack.org/#/c/569830 > Thanks > > > > On Wed, May 23, 2018 at 7:

Re: [openstack-dev] [tripleo][ci][infra] Quickstart Branching

On Wed, May 23, 2018 at 8:30 AM, Sagi Shnaidman wrote: > Hi, Sergii > > thanks for the question. It's not first time that this topic is raised and > from first view it could seem that branching would help to that sort of > issues. > > Although it's not the case.

[openstack-dev] [tripleo] Cancel IRC meeting for May 22, 2018

Since the summit is coming up, there will likely be very low attendance. We'll carry any open items until the following week. Thanks, -Alex __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [docs] Automating documentation the tripleo way?

On Wed, May 16, 2018 at 1:04 PM, Doug Hellmann wrote: > Excerpts from Wesley Hayutin's message of 2018-05-16 12:51:25 -0600: >> On Wed, May 16, 2018 at 2:41 PM Doug Hellmann wrote: >> >> > Excerpts from Petr Kovar's message of 2018-05-16 17:39:14

Re: [openstack-dev] [tripleo] Migration to Storyboard

time to review this and raise any concerns/issues now. Thanks, -Alex [0] https://docs.openstack.org/infra/manual/developers.html#development-workflow On Wed, May 9, 2018 at 1:24 PM, Alex Schultz <aschu...@redhat.com> wrote: > Hello tripleo folks, > > So we've been experimenting

Re: [openstack-dev] [ci][infra][tripleo] Multi-staged check pipelines for Zuul v3 proposal

On Mon, May 14, 2018 at 10:15 AM, Bogdan Dobrelya wrote: > An update for your review please folks > >> Bogdan Dobrelya writes: >> >>> Hello. >>> As Zuul documentation [0] explains, the names "check", "gate", and >>> "post" may be altered for more advanced pipelines. Is it

Re: [openstack-dev] [tripleo] Migration to Storyboard

On Wed, May 9, 2018 at 2:20 PM, Wesley Hayutin <whayu...@redhat.com> wrote: > > > On Wed, May 9, 2018 at 3:25 PM Alex Schultz <aschu...@redhat.com> wrote: >> >> Hello tripleo folks, >> >> So we've been experimenting with migrating some squads over to

[openstack-dev] [tripleo] Migration to Storyboard

Hello tripleo folks, So we've been experimenting with migrating some squads over to storyboard[0] but this seems to be causing more issues than perhaps it's worth. Since the upstream community would like to standardize on Storyboard at some point, I would propose that we do a cut over of all the

[openstack-dev] [tripleo] The Weekly Owl - 20th Edition

Welcome to the twentieth edition of a weekly update in TripleO world! The goal is to provide a short reading (less than 5 minutes) to learn what's new this week. Any contributions and feedback are welcome. Link to the previous version:

[openstack-dev] [tripleo] Retirement of tripleo-incubator

We haven't used tripleo-incubator in some time and it is no longer maintained. We are planning on officially retiring it ASAP[0]. We had previously said we would do it for the pike py35 goals[1] but we never got around to removing it. Efforts have begun to officially retire it. Please let us

Re: [openstack-dev] [TripleO] container-to-container-upgrades CI job and tripleo-common versions

On Thu, May 3, 2018 at 8:29 AM, John Fulton wrote: > We hit a bug [1] in CI job container-to-container-upgrades because a > workflow that was needed only for Pike and Queens was removed [2] as > clean up for the migration to external_deploy_tasks. > > As we need to support an

Re: [openstack-dev] [tripleo] [heat-templates] Deprecated environment files

On Thu, Apr 26, 2018 at 6:08 AM, Waleed Musa wrote: > Hi guys, > > > I'm wondering, what is the plan of having these environments/*.yaml and > enviroments/services-baremetal/*.yaml. > > It seems that it's deprecated files, Please advice here. > The services-baremetal were

Re: [openstack-dev] [tripleo] validating overcloud config changes on a redeploy

On Fri, Apr 27, 2018 at 9:49 AM, Ade Lee wrote: > Hi, > > Recently I starting looking at how we implement password changes in an > existing deployment, and found that there were issues. This made me > wonder whether we needed a test job to confirm that password changes > (and

Re: [openstack-dev] [tripleo] Third party module commits to TripleO/Newton branch

On Wed, May 2, 2018 at 10:23 AM, Shyam Biradar wrote: > Hi, > > I am working on TrilioVault deployment integration with TripleO. > This integration will contain changes to TripleO heat templates repo and > tripleO puppet module as shown in attached document. > > We

Re: [openstack-dev] [all][tc][ptls] final stages of python 3 transition

On Mon, Apr 30, 2018 at 3:16 PM, Ben Nemec wrote: > Resending from an address that is subscribed to the list. Apologies to > those of you who get this twice. > > On 04/30/2018 10:06 AM, Doug Hellmann wrote: >> >> It would be useful to have more input from PTLs on this

Re: [openstack-dev] [Openstack-operators] The Forum Schedule is now live

On Mon, Apr 30, 2018 at 9:47 AM, Jimmy McArthur wrote: > Project Updates are in their own track: > https://www.openstack.org/summit/vancouver-2018/summit-schedule#track=223 > TripleO is still missing? Thanks, -Alex > As are SIG, BoF and Working Groups: >

Re: [openstack-dev] [puppet] Proposing Tobias Urdin to join Puppet OpenStack core

+1 On Fri, Apr 27, 2018 at 11:41 AM, Emilien Macchi wrote: > +1, thanks Tobias for your contributions! > > On Fri, Apr 27, 2018 at 8:21 AM, Iury Gregory wrote: >> >> +1 >> >> On Fri, Apr 27, 2018, 12:15 Mohammed Naser wrote: >>>

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

+1 On Mon, Apr 23, 2018 at 5:55 AM, James Slagle wrote: > On Thu, Apr 19, 2018 at 1:01 PM, Emilien Macchi wrote: >> Greetings, >> >> As you probably know mcornea on IRC, Marius Cornea has been contributing on >> TripleO for a while, specially on the

[openstack-dev] [tripleo] Rocky Milestone 1 has past

Hey everyone, We released Rocky Milestone 1 this week[0]. I have gone through and updated the blueprints that were still targeted to rocky-1 to move them to rocky-2. Please take some time to review the outstanding blueprints to make sure that we still still be able to deliver them during the

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

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 extra tags as they could be

Re: [openstack-dev] [TripleO] Prototyping dedicated roles with unique repositories for Ansible tasks in TripleO

On Thu, Mar 29, 2018 at 11:32 AM, David Moreau Simard wrote: > Nice! > > I don't have a strong opinion > about this but what I might recommend would be to chat with the > openshift-ansible [1] and the kolla-ansible [2] folks. > > I'm happy to do the introductions if necessary

Re: [openstack-dev] [tripleo] Blueprints for Rocky

On Tue, Mar 13, 2018 at 7:58 AM, Alex Schultz <aschu...@redhat.com> wrote: > Hey everyone, > > So we currently have 63 blueprints for currently targeted for > Rocky[0]. Please make sure that any blueprints you are interested in > delivering have an assignee set and have be

Re: [openstack-dev] [Release-job-failures] Tag of openstack/instack-undercloud failed

On Mon, Mar 26, 2018 at 2:33 PM, Doug Hellmann wrote: > Excerpts from zuul's message of 2018-03-26 18:11:49 +: >> Build failed. >> >> - publish-openstack-releasenotes >>

[openstack-dev] [tripleo] Bug status

Hey everyone, In today's IRC meeting, I brought up[0] that we've been having an increase in the number of open bugs of the last few weeks. We're currently at about 635 open bugs. It would be beneficial for everyone to take a look at the bugs that they are currently assigned to and ensure they

[openstack-dev] [tripleo] Blueprints for Rocky

Hey everyone, So we currently have 63 blueprints for currently targeted for Rocky[0]. Please make sure that any blueprints you are interested in delivering have an assignee set and have been approved. I would like to have the ones we plan on delivering for Rocky to be updated by April 3, 2018.

Re: [openstack-dev] [requirements][kolla][openstack-ansible][puppet][tripleo] requirements unfreeze and you, how you should handle it

On Thu, Feb 8, 2018 at 2:29 PM, Matthew Thode wrote: > As the title states, cycle trailing projects will need to change their > requirements update behavior until they create stable/queens branches. > > When requirements unfreezes we will be doing rocky work, meaning

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

On Tue, Oct 10, 2017 at 2:24 PM, Emilien Macchi <emil...@redhat.com> wrote: > On Fri, Oct 6, 2017 at 5:09 AM, Jiří Stránský <ji...@redhat.com> wrote: >> On 5.10.2017 22:40, Alex Schultz wrote: >>> >>> Hey folks, >>> >>> So I wandere

Re: [openstack-dev] [infra][all] New Zuul Depends-On syntax

On Thu, Feb 1, 2018 at 11:55 AM, James E. Blair wrote: > Zane Bitter writes: > >> Yeah, it's definitely nice to have that flexibility. e.g. here is a >> patch that wouldn't merge for 3 months because the thing it was >> dependent on also got proposed as a

[openstack-dev] [tripleo] Rocky PTL candidacy

on developers ability to reproduce CI outside of the upstream. Thanks, Alex Schultz irc: mwhahaha __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org

[openstack-dev] [tripleo][ptl] TripleO PTL unavailable

Due to a loss in my family, I will not be around for the next few weeks. If you have any TripleO issues, please reach out to Emilien Macchi (emil...@redhat.com) or Steven Hardy (sha...@redhat.com). Thanks, -Alex __ OpenStack

Re: [openstack-dev] [tripleo] CI promotion blockers

On Tue, Jan 2, 2018 at 9:08 AM, Julie Pichon wrote: > Hi! > > On 27 December 2017 at 16:48, Emilien Macchi wrote: >> - Keystone removed _member_ role management, so we stopped using it >> (only Member is enough): https://review.openstack.org/#/c/529849/ >

Re: [openstack-dev] [puppet] Ubuntu problems + Help needed

> Just a note, the queens repo is not currently synced in the infra so > the queens repo patch is failing on Ubuntu jobs. I've proposed adding > queens to the infra configuration to resolve this: > https://review.openstack.org/529670 > As a follow up, the mirrors have landed and two of the four

Re: [openstack-dev] [puppet] Ubuntu problems + Help needed

On Thu, Dec 21, 2017 at 10:40 AM, Alex Schultz <aschu...@redhat.com> wrote: > Currently they are all globally failing in master (we are using pike > still[0] which is probably the problem) in the tempest run[1] due to: > AttributeError: 'module' object has no attribute 'require

Re: [openstack-dev] [puppet] Ubuntu problems + Help needed

Currently they are all globally failing in master (we are using pike still[0] which is probably the problem) in the tempest run[1] due to: AttributeError: 'module' object has no attribute 'requires_ext' I've submit a patch[2] to switch UCA to queens. If history is any indication, it will probably

Re: [openstack-dev] [TripleO] Tis the season...for a cloud reboot

On Tue, Dec 19, 2017 at 9:53 AM, Ben Nemec wrote: > The reboot is done (mostly...see below). > > On 12/18/2017 05:11 PM, Joe Talerico wrote: >> >> Ben - Can you provide some links to the ovs port exhaustion issue for >> some background? > > > I don't know if we ever had a

Re: [openstack-dev] [TripleO] Planning for job execution outside the gate with Zuul v3

On Mon, Nov 20, 2017 at 3:31 PM, David Moreau Simard wrote: > Hi, > > As the migration of review.rdoproject.org to Zuul v3 draws closer, I'd like > to open up the discussion around how we want to approach an eventual > migration to Zuul v3 outside the gate. > I'd like to take

[openstack-dev] [tripleo] Canceling weekly meetings for Dec 26th and Jan 2nd

Hey everyone, Due to likely low attendance, we'll be canceling the next two weekly meetings on Dec 26th and Jan 2nd. We'll resume weekly meetings back on Jan 9th. Happy holidays and stuff. Thanks, -Alex __ OpenStack

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

On Thu, Dec 14, 2017 at 5:01 PM, Tony Breeds <t...@bakeyournoodle.com> wrote: > On Wed, Dec 13, 2017 at 03:01:41PM -0700, Alex Schultz wrote: >> I assume since some of this work was sort of done earlier outside of >> tripleo and does not affect the default installation pa

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

On Thu, Dec 14, 2017 at 12:38 PM, Mark Hamzy <ha...@us.ibm.com> wrote: > Alex Schultz <aschu...@redhat.com> wrote on 12/14/2017 09:24:54 AM: >> On Wed, Dec 13, 2017 at 6:36 PM, Mark Hamzy <ha...@us.ibm.com> wrote: >> ... As I said previously, please post the &

  1   2   3   4   >