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

r 30, 2018 5:31 AM To: Dan Prince; openstack-dev@lists.openstack.org; openstack-disc...@lists.openstack.org Subject: Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes On 11/30/18 1:52 PM, Dan Prince wrote: On Fri, 2018-11-30 at

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

base] -> [service] ? Thanks, Kevin From: Bogdan Dobrelya [bdobr...@redhat.com] Sent: Friday, November 30, 2018 5:31 AM To: Dan Prince; openstack-dev@lists.openstack.org; openstack-disc...@lists.openstack.org Subject: Re: [openstack-dev] [TripleO][Edge] Reduce base

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

penstack.org; openstack-disc...@lists.openstack.org Subject: Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes On 11/30/18 1:52 PM, Dan Prince wrote: > On Fri, 2018-11-30 at 10:31 +0100, Bogdan Dobrelya wrote: >> On 1

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

On 11/30/18 1:52 PM, Dan Prince wrote: On Fri, 2018-11-30 at 10:31 +0100, Bogdan Dobrelya wrote: On 11/29/18 6:42 PM, Jiří Stránský wrote: 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 syst

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

On Fri, 2018-11-30 at 10:31 +0100, Bogdan Dobrelya wrote: > On 11/29/18 6:42 PM, Jiří Stránský wrote: > > 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 r

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

On 11/29/18 6:42 PM, Jiří Stránský wrote: 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 c

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

Thanks Jirka Thanks, Kevin 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.

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

(systemd)? That avoids using --nodeps. Thanks, Kevin From: Fox, Kevin M [kevin@pnnl.gov] Sent: Thursday, November 29, 2018 11:20 AM To: Former OpenStack Development Mailing List, use openstack-discuss now Subject: Re: [openstack-dev] [TripleO][Edge

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

Kevin 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, B

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 in

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

On 11/28/18 8:55 PM, Doug Hellmann wrote: I thought the preferred solution for more complex settings was config maps. Did that approach not work out? Regardless, now that the driver work is done if someone wants to take another stab at etcd integration it’ll be more straightforward today. Dou

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

On Wed, 2018-11-28 at 13:28 -0500, James Slagle wrote: > On Wed, Nov 28, 2018 at 12:31 PM Bogdan Dobrelya > wrote: > > Long story short, we cannot shoot both rabbits with a single shot, > > not > > with puppet :) May be we could with ansible replacing puppet > > fully... > > So splitting config an

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

On Wed, Nov 28, 2018 at 12:31 PM Bogdan Dobrelya wrote: > Long story short, we cannot shoot both rabbits with a single shot, not > with puppet :) May be we could with ansible replacing puppet fully... > So splitting config and runtime images is the only choice yet to address > the raised security

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

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 in a separate container outside of the runtime s

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 actual

Re: [openstack-dev] [tripleo] Workflows Squad changes

On Wed, Nov 28, 2018 at 5:13 AM Jiri Tomasek wrote: > Hi all, > > Recently, the workflows squad has been reorganized and people from the > squad are joining different squads. I would like to discuss how we are > going to adjust to this situation to make sure that tripleo-common > development is n

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

-disc...@lists.openstack.org Subject: Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes On Wed, 2018-11-28 at 00:31 +, Fox, Kevin M wrote: > The pod concept allows you to have one tool per container do one > thing and do it well.

Re: [openstack-dev] [tripleo] Workflows Squad changes

On Wed, Nov 28, 2018 at 5:13 AM Jiri Tomasek wrote: [...] > As a possible solution, I would like to propose Adriano as a core reviewer > to tripleo-common and adding tripleo-ui cores right to +2 tripleo-common > patches. > [...] Not a member of the squad but +2 to the idea Thanks for proposing,

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

Hi, On Tue, Nov 27, 2018 at 7:13 PM Dan Prince wrote: > On Tue, 2018-11-27 at 16:24 +0100, Bogdan Dobrelya wrote: > > Changing the topic to follow the subject. > > > > [tl;dr] it's time to rearchitect container images to stop incluiding > > config-time only (puppet et al) bits, which are not need

Re: [openstack-dev] [tripleo] Let's improve upstream docs

On Wed, Nov 28, 2018 at 4:19 PM Marios Andreou wrote: > great you are very welcome ! Thanks. > not really, I mean "anything goes" as long as it's an improvement ( and the > usual review process will determine if it is or not :) ). Could be as small > as typos or broken links/images, through to

Re: [openstack-dev] [tripleo] Let's improve upstream docs

On Wed, Nov 28, 2018 at 4:33 PM Natal Ngétal wrote: > On Tue, Nov 27, 2018 at 4:50 PM Marios Andreou wrote: > > as just mentioned in the tripleo weekly irc meeting [1] some of us are > trying to make small weekly improvements to the tripleo docs [2]. We are > using this bug [3] for tracking and

Re: [openstack-dev] [tripleo] Let's improve upstream docs

On Tue, Nov 27, 2018 at 4:50 PM Marios Andreou wrote: > as just mentioned in the tripleo weekly irc meeting [1] some of us are trying > to make small weekly improvements to the tripleo docs [2]. We are using this > bug [3] for tracking and this effort is a result of some feedback during the >

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

On Wed, 2018-11-28 at 15:12 +0100, Bogdan Dobrelya wrote: > On 11/28/18 2:58 PM, Dan Prince wrote: > > On Wed, 2018-11-28 at 12:45 +0100, Bogdan Dobrelya wrote: > > > To follow up and explain the patches for code review: > > > > > > The "header" patch https://review.openstack.org/620310 -> > > > (

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

On 11/28/18 2:58 PM, Dan Prince wrote: On Wed, 2018-11-28 at 12:45 +0100, Bogdan Dobrelya wrote: To follow up and explain the patches for code review: The "header" patch https://review.openstack.org/620310 -> (requires) https://review.rdoproject.org/r/#/c/17534/, and also https://review.opensta

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

On Wed, 2018-11-28 at 12:45 +0100, Bogdan Dobrelya wrote: > To follow up and explain the patches for code review: > > The "header" patch https://review.openstack.org/620310 -> (requires) > https://review.rdoproject.org/r/#/c/17534/, and also > https://review.openstack.org/620061 -> (which in tur

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

Added Kolla tag as we all together might want to do something to that systemd included in containers via *multiple* package dependencies, like [0]. Ideally, that might be properly packaging all/some (like those names listed in [1]) of the places having it as a dependency, to stop doing that as

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

the example pod example above is still > usable without k8s? > > Thanks, > Kevin > > From: Dan Prince [dpri...@redhat.com] > Sent: Tuesday, November 27, 2018 10:10 AM > To: OpenStack Development Mailing List (not for usage questions); > openstack-disc

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

To follow up and explain the patches for code review: The "header" patch https://review.openstack.org/620310 -> (requires) https://review.rdoproject.org/r/#/c/17534/, and also https://review.openstack.org/620061 -> (which in turn requires) https://review.openstack.org/619744 -> (Kolla change,

[openstack-dev] [tripleo] Workflows Squad changes

Hi all, Recently, the workflows squad has been reorganized and people from the squad are joining different squads. I would like to discuss how we are going to adjust to this situation to make sure that tripleo-common development is not going to be blocked in terms of feature work and reviews. Wit

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

usage questions); openstack-disc...@lists.openstack.org Subject: Re: [openstack-dev] [TripleO][Edge] Reduce base layer of containers for security and size of images (maintenance) sakes On Tue, 2018-11-27 at 16:24 +0100, Bogdan Dobrelya wrote: > Changing the topic to follow the subject. >

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

On Tue, 2018-11-27 at 16:24 +0100, Bogdan Dobrelya wrote: > Changing the topic to follow the subject. > > [tl;dr] it's time to rearchitect container images to stop incluiding > config-time only (puppet et al) bits, which are not needed runtime > and > pose security issues, like CVEs, to maintain

[openstack-dev] [tripleo] Let's improve upstream docs

Hi folks, as just mentioned in the tripleo weekly irc meeting [1] some of us are trying to make small weekly improvements to the tripleo docs [2]. We are using this bug [3] for tracking and this effort is a result of some feedback during the recent Berlin summit. The general idea is 1 per week (

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

Changing the topic to follow the subject. [tl;dr] it's time to rearchitect container images to stop incluiding config-time only (puppet et al) bits, which are not needed runtime and pose security issues, like CVEs, to maintain daily. Background: 1) For the Distributed Compute Node edge case,

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

Here is a related bug [1] and implementation [1] for that. PTAL folks! [0] https://bugs.launchpad.net/tripleo/+bug/1804822 [1] https://review.openstack.org/#/q/topic:base-container-reduction Let's also think of removing puppet-tripleo from the base container. It really brings the world-in (and

[openstack-dev] [tripleo] Feedback about our project at Summit

Hi folks, I wasn't at the Summit but I was interested by the feedback people gave about TripleO so I've discussed with a few people who made the trip. I would like to see what actions we can take on short and long term to address it. I collected some thoughts here: https://etherpad.openstack.org/p

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

On Thu, Nov 15, 2018 at 3:54 PM 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 > Infras

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

On 15 Nov, 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 > Infrastructure. It'll be grand.

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

+1 on making him tripleo-ci core. Great work! On 11/15/18 5:50 PM, 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 inclu

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

+1 On 11/15/18 4:50 PM, 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 Infrastructure. He shows

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

+1 On Thu, Nov 15, 2018 at 9:24 PM 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 > Inf

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

Thanks guys! On Fri, Nov 16, 2018 at 8:26 AM Martin André wrote: > On Thu, Nov 15, 2018 at 5:00 PM 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

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

On Thu, Nov 15, 2018 at 5:00 PM 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

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

On Thu, Nov 15, 2018 at 5:51 PM 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 > Infrastruc

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

Of course +1 :). On 11/15/18 5:37 PM, Emilien Macchi wrote: > +1 to have him part of TripleO CI core team, thanks for your dedication > and hard work. I'm glad to see you're learning fast. Keep your > motivation and thanks again! > > On Thu, Nov 15, 2018 at 11:33 AM Alex Schultz

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

+1 to have him part of TripleO CI core team, thanks for your dedication and hard work. I'm glad to see you're learning fast. Keep your motivation and thanks again! On Thu, Nov 15, 2018 at 11:33 AM Alex Schultz wrote: > +1 > On Thu, Nov 15, 2018 at 8:51 AM Sagi Shnaidman > wrote: > > > > Hi, > >

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

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 inc

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

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 including but not limited to > Infrastruc

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

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 Infrastructure. He shows a very good understanding how TripleO and CI works

[openstack-dev] [tripleo] Proposal: Remove newton/ocata CI jobs

Greetings, The non-containerized multinode scenario jobs were active up to Ocata release and are no longer supported. I'm proposing a cleanup [1] on these old jobs so I've added this topic to the next tripleo meeting agenda [2] to discuss with the tripleo team. Since this may affect multiple proje

[openstack-dev] [tripleo] no recheck / no workflow until gate is stable

We have serious issues with the gate at this time, we believe it is a mix of mirrors errors (infra) and tempest timeouts (see https://review.openstack.org/617845). Until the situation is resolved, do not recheck or approve any patch for now. Thanks for your understanding, -- Emilien Macchi __

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

Hello Alex, On Tue, Nov 13, 2018 at 9:53 AM Alex Schultz wrote: > > 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 t

[openstack-dev] [tripleo][openstack-ansible] Updates on collaboration on os_tempest role

Hello, During the starting of Denver 2018 PTG [1]., We started collaborating towards using the openstack-ansible-os_tempest role [2] as a unified tempest role in TripleO and openstack-ansible project within OpenStack community. It will help us to improve the testing strategies between two project

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

Re: [openstack-dev] [tripleo] using molecule to test ansible playbooks and roles

On Sun, Nov 11, 2018 at 11:29:43AM +, Sorin Sbarnea wrote: > I recently came across molecule a > project originated at Cisco which recently become an officially Ansible > project, at the same time as ansible-lint. Both projects were transferred > from t

[openstack-dev] [tripleo] using molecule to test ansible playbooks and roles

I recently came across molecule a project originated at Cisco which recently become an officially Ansible project, at the same time as ansible-lint. Both projects were transferred from their former locations to Ansible github organization -- I guess as a c

[openstack-dev] [tripleo] TripleO CI Summary: Sprint 21

Greetings, The TripleO CI team has just completed Sprint 21 (Oct-18 thru Nov-07). The following is a summary of completed work during this sprint cycle: - Created an initial base Standalone job for Fedora 28. - Added initial support for installing Tempest rpm in openstack-ansibl

[openstack-dev] [TripleO] No meeting next week for the security squad

There will be no meeting for the security squad next Tuesday 13th of November since there's the OpenStack summit. Best Regards __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ

[openstack-dev] [TripleO] No weekly meeting next week

There will be no meeting next Tuesday 13th of November since there's the OpenStack summit. Best Regards __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?

Re: [openstack-dev] [tripleo] CI is broken

No alert anymore, gate is green. recheck if needed. On Wed, Nov 7, 2018 at 2:22 PM Emilien Macchi wrote: > I updated the bugs, and so far we have one alert left: > https://bugs.launchpad.net/tripleo/+bug/1801969 > > The patch is in gate, be patient and then we'll be able to +A/recheck > stuff ag

[openstack-dev] [TripleO] Edge squad meeting this week and next week

I won't be around to run the Edge squad meeting this week and next week. If someone else wants to pick it up, that would be great. Otherwise, consider it cancelled :). Thanks! https://etherpad.openstack.org/p/tripleo-edge-squad-status -- -- James Slagle -- __

Re: [openstack-dev] [tripleo] CI is broken

I updated the bugs, and so far we have one alert left: https://bugs.launchpad.net/tripleo/+bug/1801969 The patch is in gate, be patient and then we'll be able to +A/recheck stuff again. On Wed, Nov 7, 2018 at 7:30 AM Juan Antonio Osorio Robles < jaosor...@redhat.com> wrote: > Hello folks, > > >

[openstack-dev] [tripleo] CI is broken

Hello folks, Please do not attempt to merge or recheck patches until we get this sorted out. We are dealing with several issues that have broken all jobs. https://bugs.launchpad.net/tripleo/+bug/1801769 https://bugs.launchpad.net/tripleo/+bug/1801969 https://bugs.launchpad.net/tripleo/+bug/1802

Re: [openstack-dev] [tripleo] shutting down 3rd party TripleO CI for measurements

We measured results and would like to shut down check jobs in RDO cloud CI today. Please let us know if you have objections. Thanks On Thu, Nov 1, 2018 at 12:14 AM Wesley Hayutin wrote: > Greetings, > > The TripleO-CI team would like to consider shutting down all the third > party check jobs ru

Re: [openstack-dev] [tripleo] Ansible getting bumped up from 2.4 -> 2.6.6

On 11/5/18 11:23 PM, Wesley Hayutin wrote: > Greetings, > > Please be aware of the following patch [1].  This updates ansible in > queens, rocky, and stein. >  This was just pointed out to me, and I didn't see it coming so I > thought I'd email the group. > > That is all, thanks > > [1] https://

[openstack-dev] [tripleo] Ansible getting bumped up from 2.4 -> 2.6.6

Greetings, Please be aware of the following patch [1]. This updates ansible in queens, rocky, and stein. This was just pointed out to me, and I didn't see it coming so I thought I'd email the group. That is all, thanks [1] https://review.rdoproject.org/r/#/c/14960 -- Wes Hayutin Associate M

Re: [openstack-dev] [TripleO] PSA lets use deploy_steps_tasks

On Mon, Nov 5, 2018 at 4:06 AM Cédric Jeanneret wrote: > > On 11/2/18 2:39 PM, Dan Prince wrote: > > I pushed a patch[1] to update our containerized deployment > > architecture docs yesterday. There are 2 new fairly useful sections we > > can leverage with TripleO's stepwise deployment. They appea

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

On Mon, Nov 5, 2018 at 3:47 AM Bogdan Dobrelya wrote: > > Let's also think of removing puppet-tripleo from the base container. > It really brings the world-in (and yum updates in CI!) each job and each > container! > So if we did so, we should then either install puppet-tripleo and co on > the hos

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

On 11/5/18 11:47 AM, Bogdan Dobrelya wrote: > Let's also think of removing puppet-tripleo from the base container. > It really brings the world-in (and yum updates in CI!) each job and each > container! > So if we did so, we should then either install puppet-tripleo and co on > the host and bind-

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

Let's also think of removing puppet-tripleo from the base container. It really brings the world-in (and yum updates in CI!) each job and each container! So if we did so, we should then either install puppet-tripleo and co on the host and bind-mount it for the docker-puppet deployment task steps

Re: [openstack-dev] [TripleO] PSA lets use deploy_steps_tasks

On 11/2/18 2:39 PM, Dan Prince wrote: > I pushed a patch[1] to update our containerized deployment > architecture docs yesterday. There are 2 new fairly useful sections we > can leverage with TripleO's stepwise deployment. They appear to be > used somewhat sparingly so I wanted to get the word out.

Re: [openstack-dev] [TripleO] PSA lets use deploy_steps_tasks

On Fri, Nov 2, 2018 at 9:39 AM Dan Prince wrote: > > I pushed a patch[1] to update our containerized deployment > architecture docs yesterday. There are 2 new fairly useful sections we > can leverage with TripleO's stepwise deployment. They appear to be > used somewhat sparingly so I wanted to get

Re: [openstack-dev] [TripleO] PSA lets use deploy_steps_tasks

Thanks! We have been slow to update our docs. I did put up a blog post about these sections of the templates [1], in case folks find that useful. [1] http://jaormx.github.io/2018/dissecting-tripleo-service-templates-p2/ On 11/2/18 3:39 PM, Dan Prince wrote: > I pushed a patch[1] to update our co

[openstack-dev] [TripleO] PSA lets use deploy_steps_tasks

I pushed a patch[1] to update our containerized deployment architecture docs yesterday. There are 2 new fairly useful sections we can leverage with TripleO's stepwise deployment. They appear to be used somewhat sparingly so I wanted to get the word out. The first is 'deploy_steps_tasks' which give

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

On Thu, Nov 1, 2018 at 4:26 PM Emilien Macchi wrote: > done, you're now core in TripleO; Thanks Bob for your hard work! > Thank you Emilien, Juan, and everyone else! > > On Mon, Oct 22, 2018 at 4:55 PM Jason E. Rist wrote: > >> On 10/19/2018 06:23 AM, Juan Antonio Osorio Robles wrote: >> > He

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

done, you're now core in TripleO; Thanks Bob for your hard work! On Mon, Oct 22, 2018 at 4:55 PM Jason E. Rist wrote: > On 10/19/2018 06:23 AM, Juan Antonio Osorio Robles wrote: > > Hello! > > > > > > I would like to propose Bob Fournier (bfournie) as a core reviewer in > > TripleO. His patches

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

Thanks Alex! On Thu, Nov 1, 2018 at 10:27 AM Alex Schultz wrote: > Ok since the podman revert patche has been successfully merged and > we've landed most of the non-voting scenario patches, it should be OK > to restore/recheck. It would be a good idea to prioritized things to > land and if it's

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

On 10/30/18 4:16 PM, Clark Boylan wrote: On Tue, Oct 30, 2018, at 1:01 PM, Ben Nemec wrote: On 10/30/18 1: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

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

Ok since the podman revert patche has been successfully merged and we've landed most of the non-voting scenario patches, it should be OK to restore/recheck. It would be a good idea to prioritized things to land and if it's not critical, let's hold off on approving until we're sure the gate is much

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

On Wed, 31 Oct 2018 at 17:22, Alex Schultz wrote: > > 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 cau

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

On 10/31/18 4:59 PM, Harald Jensås wrote: On Wed, 2018-10-31 at 11:39 -0600, Wesley Hayutin wrote: On Wed, Oct 31, 2018 at 11:21 AM Alex Schultz wrote: Hey everyone, Based on previous emails around this[0][1], I have proposed a possible reducing in our usage by switching the scenario001--

[openstack-dev] [tripleo] shutting down 3rd party TripleO CI for measurements

Greetings, The TripleO-CI team would like to consider shutting down all the third party check jobs running against TripleO projects in order to measure results with and without load on the cloud for some amount of time. I suspect we would want to shut things down for roughly 24-48 hours. If ther

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

On Wed, 2018-10-31 at 11:39 -0600, Wesley Hayutin wrote: > > > On Wed, Oct 31, 2018 at 11:21 AM Alex Schultz > wrote: > > 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-

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

On Wed, 2018-10-31 at 11:35 -0600, Alex Schultz wrote: > 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 < > > > cboy...@sapwetik.org> > > > wrote: > > > > > > > > On Tue, O

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

Alex Schultz writes: > 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

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

On Wed, Oct 31, 2018 at 11:21 AM Alex Schultz wrote: > 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 c

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: > > > > On Tue, Oct 30, 2018 at 11:36 AM Ben Nemec < > >

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

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

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: > > > On Tue, Oct 30, 2018 at 11:36 AM Ben Nemec < > > > openst...@nemebean.com> wrote: > > > > > > > > Tagging with trip

Re: [openstack-dev] [tripleo] request for feedback/review on docker2podman upgrade

Emilien Macchi writes: > A bit of an update here: > > - We merged the patch in openstack/paunch that stop the Docker container if > we try to start a Podman container. > - We switched the undercloud upgrade job to test upgrades from Docker to > Podman (for now containers are stopped in Docker and

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

Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling

On Wed, 31 Oct 2018, Eduardo Gonzalez wrote: - Run db syncs as there is not command for that yet in the master branch - Apply upgrade process for db changes The placement-side pieces for this are nearly ready, see the stack beginning at https://review.openstack.org/#/c/611441/ -- Chris Dent

Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling

Hi, from kolla side I've started the work. In kolla images [0] for now only placement is separated to an independent image, only source is code is being installed, binary still uses nova-placement packages until a binary package exists from the debian and centos families. In kolla-ansible [1] pla

Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling

On 30-10-18 14:29:12, Emilien Macchi wrote: > On the TripleO side, it sounds like Lee Yarwood is taking the lead with a > first commit in puppet-placement: > https://review.openstack.org/#/c/604182/ > > Lee, can you confirm that you and your team are working on it for Stein > cycle? ACK, just get

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

On Tue, Oct 30, 2018, at 1:01 PM, Ben Nemec wrote: > > > On 10/30/18 1: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 > >>

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 > > > project. > > > > > > On 10/30/18 11:03 AM, Cl

Re: [openstack-dev] [tripleo] request for feedback/review on docker2podman upgrade

A bit of an update here: - We merged the patch in openstack/paunch that stop the Docker container if we try to start a Podman container. - We switched the undercloud upgrade job to test upgrades from Docker to Podman (for now containers are stopped in Docker and then started in Podman). - We are n

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

On 10/30/18 1: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 project. On 10/30/18 11:03 AM, Clark Boylan wrote: Hello everyone, A little

Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling

On Tue, 30 Oct 2018, Mohammed Naser wrote: We spoke about this today in the OpenStack Ansible meeting, we've come up with the following steps: Great! Thank you, Guilherme, and Lee very much. 1) Create a role for placement which will be called `os_placement` located in `openstack/openstack-an

Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling

On the TripleO side, it sounds like Lee Yarwood is taking the lead with a first commit in puppet-placement: https://review.openstack.org/#/c/604182/ Lee, can you confirm that you and your team are working on it for Stein cycle? On Thu, Oct 25, 2018 at 1:34 PM Matt Riedemann wrote: > Hello OSA/T

  1   2   3   4   5   6   7   8   9   10   >