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
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
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
On Tue, Jul 5, 2016 at 1:06 PM, Steven Hardy wrote:
> Hi all,
>
> At last weeks meeting, we discussed the idea of some sort of rotation where
> folks would volunteer their time to both help fix CI when it breaks, and
> also pass on some of the accrued knowledge within the team to newer folks
> wi
On Mon, Apr 18, 2016 at 8:36 AM, Sagi Shnaidman wrote:
> For making clear all advantages and disadvantages, I've created a doc:
>
> https://docs.google.com/document/d/1HmY-I8OzoJt0SzLzs79hCa1smKGltb-byrJOkKKGXII/edit?usp=sharing
>
> Please comment.
>
> On Sun, Apr 17, 2016 at 12:14 PM, Sagi Shnai
Greetings,
The TripleO team would like to initiate a conversation about the
possibility of creating a new pipeline in Openstack Infra to allow a set of
jobs to run periodically every four hours [2].
The background and context of why such a pipeline is required is as
follows. TripleO CI executes i
On Wed, Mar 8, 2017 at 1:29 PM, Jeremy Stanley wrote:
> On 2017-03-07 10:12:58 -0500 (-0500), Wesley Hayutin wrote:
> > The TripleO team would like to initiate a conversation about the
> > possibility of creating a new pipeline in Openstack Infra to allow
> > a set of job
quot;usual"
> >> > > > periodic are used for repository promotion and their value are
> equal or
> >> > > > higher than check jobs, so it needs to run with "normal" or even
> "high"
> >> > > > precedence.
> >> >
On Thu, Mar 30, 2017 at 10:08 AM, Steven Hardy wrote:
> On Wed, Mar 29, 2017 at 10:07:24PM -0400, Paul Belanger wrote:
> > On Thu, Mar 30, 2017 at 09:56:59AM +1300, Steve Baker wrote:
> > > On Thu, Mar 30, 2017 at 9:39 AM, Emilien Macchi
> wrote:
> > >
> > > > On Mon, Mar 27, 2017 at 8:00 AM, Fl
On Tue, Apr 18, 2017 at 2:28 PM, Emilien Macchi wrote:
> On Mon, Apr 17, 2017 at 3:52 PM, Justin Kilpatrick
> wrote:
> > Because CI jobs tend to max out about 5 nodes there's a whole class of
> > minor bugs that make it into releases.
> >
> > What happens is that they never show up in small clou
On Wed, May 10, 2017 at 9:26 AM, Jiří Stránský wrote:
> Hi all,
>
> the upgrade job which tests Ocata -> Pike/master upgrade (from bare-metal
> to containers) just got a green flag from the CI [1].
>
> I've listed the remaining patches we need to land at the very top of the
> container CI etherpa
On Fri, Jun 2, 2017 at 11:42 AM, Attila Darazs wrote:
> If the topics below interest you and you want to contribute to the
> discussion, feel free to join the next meeting:
>
> Time: Thursdays, 14:30-15:30 UTC
> Place: https://bluejeans.com/4113567798/
>
> Full minutes: https://etherpad.openstack
On Fri, Jun 2, 2017 at 4:42 PM, Ben Nemec wrote:
>
>
> On 03/28/2017 05:01 PM, Ben Nemec wrote:
>
>> Final (hopefully) update:
>>
>> All active compute nodes have been rebooted and things seem to be stable
>> again. Jobs are even running a little faster, so I'm thinking this had
>> a detrimental
Greetings,
I wanted to send out a summary email regarding some work that is still
developing and being planned to give interested parties time to comment and
prepare for change.
Project:
Move tripleo periodic promotion jobs
Goal:
Increase the cadence of tripleo-ci periodic promotion jobs
Greetings,
It's become apparent that everyone in the tripleo community may not be
aware of where CI specific work is tracked.
To find out which CI related features or bug fixes are in progress or to
see the backlog please consult [1].
To find out what issues have been found in OpenStack via CI p
On Tue, Jun 20, 2017 at 2:51 PM, Emilien Macchi wrote:
> On Tue, Jun 20, 2017 at 12:49 PM, Wesley Hayutin
> wrote:
> > Greetings,
> >
> > It's become apparent that everyone in the tripleo community may not be
> aware
> > of where CI specific work is tracked
posting to openstack-dev
On Sun, Jul 9, 2017 at 10:08 AM, Wesley Hayutin wrote:
> Greetings Andreas, Paul
>
> I'm looking for some pointers on how to include some instructions in our
> openstack logs in the same way the devstack gate works [1] and I'm not able
> to
On Fri, Jul 7, 2017 at 6:20 PM, James Slagle wrote:
> On Fri, Jul 7, 2017 at 5:31 PM, David Moreau Simard
> wrote:
> > On Fri, Jul 7, 2017 at 1:50 PM, James Slagle
> wrote:
> >> (0) tripleo-quickstart which follows the common and well accepted
> >> approach to bundling a set of Ansible playbook
+1
On Fri, Jul 7, 2017 at 5:25 PM, Pradeep Kilambi wrote:
> +1 to Alex
>
> On Fri, Jul 7, 2017 at 4:20 PM, Juan Antonio Osorio
> wrote:
> > +1
> >
> > He's a great reviewer
> >
> > On 7 Jul 2017 8:40 pm, "Emilien Macchi" wrote:
> >>
> >> Alex has demonstrated high technical and community skill
On Mon, Jul 10, 2017 at 2:24 AM, Andreas Jaeger wrote:
> On 2017-07-10 05:03, Wesley Hayutin wrote:
> > posting to openstack-dev
> >
> > On Sun, Jul 9, 2017 at 10:08 AM, Wesley Hayutin > <mailto:whayu...@redhat.com>> wrote:
> >
> > Greetings A
Greetings,
I was looking through the mailing list and I did not see any emails
explicitly calling out the decreased coverage for telemetry in tripleo due
to [1]. A series of changes went into the CI system to disable telemetry
[2].
There is work being done to restore more coverage for telemetry
On Tue, Jul 11, 2017 at 3:41 PM, Pradeep Kilambi wrote:
> On Tue, Jul 11, 2017 at 3:17 PM, Wesley Hayutin
> wrote:
> > Greetings,
> >
> > I was looking through the mailing list and I did not see any emails
> > explicitly calling out the decreased coverage for tel
On Tue, Jul 11, 2017 at 9:04 PM, Emilien Macchi wrote:
> On Tue, Jul 11, 2017 at 12:41 PM, Pradeep Kilambi wrote:
> > On Tue, Jul 11, 2017 at 3:17 PM, Wesley Hayutin
> wrote:
> >> Greetings,
> >>
> >> I was looking through the mailing list and I did not
On Wed, Jul 12, 2017 at 10:33 AM, Pradeep Kilambi wrote:
> On Tue, Jul 11, 2017 at 10:06 PM, Wesley Hayutin
> wrote:
> >
> >
> > On Tue, Jul 11, 2017 at 9:04 PM, Emilien Macchi
> wrote:
> >>
> >> On Tue, Jul 11, 2017 at 12:41 PM, Pradeep Kilambi
&g
Greetings,
Apologies for the delayed notes with regards to the last tripleo-ci-squad
meeting.
Highlights:
* Tempest
* master/pike is down to 2 tempest failures [1] out of 1,337 tests
executed.
* stable/ocata is a full pass on tempest
* proposed tempest test to replace the tripleo ping test
If the topics below interest you and you want to contribute to the
discussion, feel free to join the next meeting:
Time: Thursdays, 14:30-15:30 UTC
Place: https://bluejeans.com/4113567798/
Full minutes: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
= Demo =
* Tempest in gate jobs sta
Greetings,
I thought it may be helpful if we wrote some instructions for other
OpenStack projects with how to add a TripleO job to their projects check
gate in a nonvoting or voting capacity.
I'm not 100% sure if I'm accurate in my steps or if I'm missing something
someone may want to add.
Asking
On Wed, Jul 26, 2017 at 7:39 AM, Jiří Stránský wrote:
> On 21.7.2017 16:55, Emilien Macchi wrote:
>
>> Hi,
>>
>> Bogdan (bogdando on IRC) has been very active in Containerization of
>> TripleO and his quality of review has increased over time.
>> I would like to give him core permissions on conta
On Tue, Aug 15, 2017 at 9:33 PM, Emilien Macchi wrote:
> So far, we're having 3 critical issues, that we all need to address as
> soon as we can.
>
> Problem #1: Upgrade jobs timeout from Newton to Ocata
> https://bugs.launchpad.net/tripleo/+bug/1702955
> Today I spent an hour to look at it and h
Greetings,
I'd like to propose that the mistral project be added to the list of
projects where in CI the very latest built packages are added to each CI
run [1].
This will help get patches that depend on mistral patches to more quickly
be tested and merged. For example Honza's patch [2] depends
On Mon, Aug 28, 2017 at 10:19 AM, Paul Belanger
wrote:
> On Mon, Aug 28, 2017 at 09:42:45AM -0400, David Moreau Simard wrote:
> > Hi,
> >
> > (cc whom I would at least like to attend)
> >
> > The PTG would be a great opportunity to talk about CI design/layout
> > and how we see things moving forw
On Thu, Sep 28, 2017 at 3:23 AM, Steven Hardy wrote:
> On Thu, Sep 28, 2017 at 8:04 AM, Marios Andreou
> wrote:
> >
> >
> > On Thu, Sep 28, 2017 at 9:50 AM, mathieu bultel
> wrote:
> >>
> >> Hi,
> >>
> >>
> >> On 09/28/2017 05:05 AM, Emilien Macchi wrote:
> >> > I was reviewing https://review.o
On Thu, Sep 28, 2017 at 12:32 PM, Emilien Macchi wrote:
> On Thu, Sep 28, 2017 at 9:22 AM, Wesley Hayutin
> wrote:
> [...]
> > OK.. I think the solution is to start migrating these jobs to RDO
> Software
> > Factory third party testing.
> >
> > Here is
Greetings,
The upstream log server is overloaded a bit, I think we can help their
cause.
Please review and add comments to this bug [1]
Yesterday the following two related patches landed [2], [3]
Thank you!
[1] https://bugs.launchpad.net/tripleo/+bug/1723182
[2] https://review.openstack.org/#/
Greetings,
TripleO CI started to hit errors in any of the multinode node pool jobs
last Friday afternoon.
Please review the bug and patch to bring CI back online [1-2]
More work needs to be done to discover exactly why the latest rpm breaks
the vxlan network link between nodes. It's also a good
Greetings,
We noticed the job legacy-tripleo-ci-centos-7-undercloud-containers
failing in the gate in the following patches [1], [2]. The job was voting
in the review here [3]. ATM the job is non-voting in check and voting in
the gate. This is a dangerous combination where the job can fail in
On Fri, Nov 3, 2017 at 5:52 AM, Gabriele Cerami wrote:
> Hi,
>
> since the failures in Tuesday's tests were caused by infra problems, we
> believed a specific hash involved in the failures to remain the best
> candidate for a promotion.
> So we pinned it in our promotion pipeline and insisted on
On Sun, Nov 5, 2017 at 7:55 AM, Adriano Petrich wrote:
> Amazing! Thanks for the effort that took to get the promotion fixed!
>
> On Fri, Nov 3, 2017 at 8:17 PM, Jason E. Rist wrote:
>
>> On 11/03/2017 03:52 AM, Gabriele Cerami wrote:
>> > Hi,
>> >
>> > since the failures in Tuesday's tests were
On Sun, Nov 5, 2017 at 7:01 PM, Emilien Macchi wrote:
> On Mon, Oct 2, 2017 at 5:02 AM, Dan Prince wrote:
> [...]
>
> > -CI resources: better use of CI resources. At the PTG we received
> > feedback from the OpenStack infrastructure team that our upstream CI
> > resource usage is quite high at
On Mon, Nov 6, 2017 at 7:35 AM, Bogdan Dobrelya wrote:
> On 11/6/17 1:01 AM, Emilien Macchi wrote:
>
>> On Mon, Oct 2, 2017 at 5:02 AM, Dan Prince wrote:
>> [...]
>>
>> -CI resources: better use of CI resources. At the PTG we received
>>> feedback from the OpenStack infrastructure team that ou
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 failing after being reviewed by myself and M
On Tue, Nov 7, 2017 at 5:47 PM, Emilien Macchi wrote:
> On Wed, Nov 8, 2017 at 9:29 AM, Wesley Hayutin
> wrote:
> > Greetings,
> >
> > I'd like to propose we remove the upgrade jobs that are consistently
> failing
> > from the upstream infrastructur
On Tue, Nov 7, 2017 at 9:07 PM, James Slagle wrote:
> On Tue, Nov 7, 2017 at 4:59 PM, Emilien Macchi wrote:
> > Yes. Thanks for reformulate with better words.
> > Just to be clear, I want to transform the scenarios into single-node
> > jobs that deploy the SAME services (using composable service
On Wed, Nov 8, 2017 at 5:00 PM, Alex Schultz wrote:
> On Tue, Nov 7, 2017 at 2:59 PM, Emilien Macchi wrote:
> > On Wed, Nov 8, 2017 at 3:30 AM, James Slagle
> wrote:
> >> On Sun, Nov 5, 2017 at 7:01 PM, Emilien Macchi
> wrote:
> >>> On Mon, Oct 2, 2017 at 5:02 AM, Dan Prince wrote:
> >>> [...
On Wed, Nov 8, 2017 at 5:10 PM, Wesley Hayutin wrote:
>
>
> On Wed, Nov 8, 2017 at 5:00 PM, Alex Schultz wrote:
>
>> On Tue, Nov 7, 2017 at 2:59 PM, Emilien Macchi
>> wrote:
>> > On Wed, Nov 8, 2017 at 3:30 AM, James Slagle
>> wrote:
>> >
Greetings,
Infra asked the tripleo team to cut down on the logs we're producing
upstream. We are using a lot of space on their servers and also it's
taking too long to collect the logs themselves.
We need to compromise and be flexible here, so I'd like the tripleo-ci and
tripleo core to take ano
On Sat, Nov 11, 2017 at 10:47 PM, Alex Schultz wrote:
> Ok so here's the current status of things. I've gone through some of
> the pending patches and sent them to the gate over the weekend since
> the gate was empty (yay!). We've managed to land a bunch of patches.
> That being said for any pa
+1 woot
On Wed, Nov 29, 2017 at 2:44 PM, Alex Schultz wrote:
> +1
>
> On Wed, Nov 29, 2017 at 12:34 PM, 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
> > begi
Greetings,
Just wanted to share some progress with the containerized undercloud work.
Ian pushed some of the patches along and we now have a successful
undercloud install with containers.
The initial undercloud install works [1]
The idempotency check failed where we reinstall the undercloud [2]
On Fri, Dec 8, 2017 at 4:32 AM, Sofer Athlan-Guyot
wrote:
> Hi,
>
> We (Upgrade Squad) have eventually save some time for fixing/creating
> the needed upgrade/update jobs.
>
> We have made an inventory of what currently exists there[1] and what is
> missing in the same spreadsheet.
>
> I recap th
On Fri, Dec 8, 2017 at 10:11 PM, Emilien Macchi wrote:
> On Fri, Dec 8, 2017 at 11:42 AM, Emilien Macchi
> wrote:
> > On Fri, Dec 8, 2017 at 5:39 AM, Wesley Hayutin
> wrote:
> > [...]
> >> Sofer, can you estimate when the redhat-openstack gerrit repo will be
On Tue, Jan 2, 2018 at 11:05 PM, Emilien Macchi wrote:
> Mistral broke us with https://review.openstack.org/#/c/506185/ and we
> had a promotion yesterday so now our CI deploy Mistral with this
> patch.
> It breaks some Mistral actions, including the ones needed by
> config-download (in featurese
On Wed, Jan 17, 2018 at 10:52 AM, Sofer Athlan-Guyot
wrote:
> Emilien Macchi writes:
>
> > Nice work Sofer!
> > I have a few questions, see inline.
> >
> > On Wed, Jan 17, 2018 at 4:46 AM, Sofer Athlan-Guyot
> wrote:
> >> Hi,
> >>
> >> So join us (upgrade squad) to celebrate the working ocata->
Thanks Marius for sending this out and kicking off a conversation.
On Tue, Jan 2, 2018 at 12:56 PM, Marius Cornea wrote:
> Hi everyone and Happy New Year!
>
> As the migration of tripleo-upgrade repo to the openstack namespace is
> now complete I think it's the time to create a Pike branch to ca
On Fri, Jan 19, 2018 at 12:23 PM, Ben Nemec wrote:
>
>
> On 01/18/2018 09:45 AM, Emilien Macchi wrote:
>
>> On Thu, Jan 18, 2018 at 6:34 AM, Or Idgar wrote:
>>
>>> Hi,
>>> we're encountering many timeouts for zuul gates in TripleO.
>>> For example, see
>>> http://logs.openstack.org/95/508195/28/
On Mon, Jan 22, 2018 at 6:55 AM, Or Idgar wrote:
> Hi,
> Still having timeouts but now in tripleo-heat-templates experimental gates
> (tripleo-ci-centos-7-ovb-fakeha-caserver and tripleo-ci-centos-7-ovb-ha-
> tempest-oooq).
>
> see examples:
> http://logs.openstack.org/31/518331/23/experimental-
On Tue, Jul 12, 2016 at 3:39 PM, John Trowbridge wrote:
> Howdy folks,
>
> In the TripleO meeting two weeks ago, it came up that tripleo-quickstart
> is being used as a CI tool in RDO. This came about organically, because
> we needed to use RDO CI to self-gate quickstart (it relies on having a
>
On Wed, Jul 13, 2016 at 8:54 AM, Michal Pryc wrote:
> John,
>
> On Tue, Jul 12, 2016 at 9:39 PM, John Trowbridge wrote:
>
>> Howdy folks,
>>
>> In the TripleO meeting two weeks ago, it came up that tripleo-quickstart
>> is being used as a CI tool in RDO. This came about organically, because
>> w
Greetings,
Just wanted to let folks know we're bringing up two 3rd party gates for
TripleO CI atm.
1. The first gate will be for upgrading from mitaka -> newton/master
2. The second gate will be for running TripleO CI on RHEL 7.2
We're working out the logging for #2. ATM we're going to try and
On Thu, Jul 14, 2016 at 5:13 PM, Emilien Macchi wrote:
> On Thu, Jul 14, 2016 at 4:45 PM, Wesley Hayutin
> wrote:
> > Greetings,
> >
> > Just wanted to let folks know we're bringing up two 3rd party gates for
> > TripleO CI atm.
> >
> > 1. T
On Mon, Jul 18, 2016 at 11:06 AM, John Trowbridge wrote:
> Howdy,
>
> I would like to propose Gabriele (panda on IRC), for tripleo-quickstart
> core. He has worked on some pretty major features for the project
> (explicit teardown, devmode), and has a good understanding of the code
> base.
>
> Th
On Tue, Jul 19, 2016 at 2:44 PM, James Slagle
wrote:
> On Tue, Jul 12, 2016 at 3:39 PM, John Trowbridge wrote:
> > Howdy folks,
> >
> > In the TripleO meeting two weeks ago, it came up that tripleo-quickstart
> > is being used as a CI tool in RDO. This came about organically, because
> > we need
On Thu, Jul 21, 2016 at 5:47 PM, James Slagle
wrote:
> On Tue, Jul 19, 2016 at 5:15 PM, Wesley Hayutin
> wrote:
> >
> >
> > On Tue, Jul 19, 2016 at 2:44 PM, James Slagle
> > wrote:
> >> Part of the goal of tripleo.sh was to mirror the commands in the
>
On Tue, Jul 26, 2016 at 10:32 AM, John Trowbridge wrote:
> I would like to add Attila to the tripleo-quickstart core reviewers
> group. Much of his work has been on some of the auxillary roles that
> quickstart makes use of in RDO CI, however his numbers on quickstart
> itself[1] are in line with
On Fri, Aug 5, 2016 at 4:08 PM, Emilien Macchi wrote:
> On Fri, Aug 5, 2016 at 1:58 PM, Steven Hardy wrote:
> > On Thu, Aug 04, 2016 at 09:46:20PM -0400, Emilien Macchi wrote:
> >> Hi,
> >>
> >> I'm currently working by iteration to get a new upstream job that test
> >> upgrades and update.
> >>
Greetings,
In an effort to make TripleO CI composable and managed and governed by the
TripleO project we have found the need to create additional git repos in
openstack under the TripleO project. This could also be done outside of
the TripleO project, but ideally it's in TripleO.
I'm proposing
On Wed, Aug 10, 2016 at 9:45 PM, Lars Kellogg-Stedman
wrote:
> On Wed, Aug 10, 2016 at 03:26:18PM -0400, Wesley Hayutin wrote:
> > I'm proposing the creation of a repo called tripleo-quickstart-extras
> that
> > would contain some or all of the current third party role
Greetings,
Jobs:
tripleo-ci-centos-7-scenario001-multinode-oooq-container
tripleo-ci-centos-7-scenario002-multinode-oooq-container
The above jobs have been failing in check and gate over the past 24 hours.
The fix is posted here [1] which reverts [2]
Thanks
[1] https://review.openstack.org/#/
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 the instructions.
At this time the reprodu
On Thu, Feb 8, 2018 at 6:23 PM, Alex Schultz wrote:
> On Tue, Oct 10, 2017 at 2:24 PM, Emilien Macchi
> wrote:
> > On Fri, Oct 6, 2017 at 5:09 AM, Jiří Stránský wrote:
> >> On 5.10.2017 22:40, Alex Schultz wrote:
> >>>
> >>> Hey folks,
> >>>
> >>> So I wandered across the policy spec[0] for how
On Fri, Feb 16, 2018 at 9:16 AM, Bogdan Dobrelya
wrote:
> On 2/16/18 2:59 PM, Raoul Scarazzini wrote:
>
>> On 16/02/2018 10:24, Bogdan Dobrelya wrote:
>> [...]
>>
>>> +1 this looks like a perfect fit. Would it be possible to install that
>>> tripleo-ha-utils/tripleo-quickstart-utils with ansible-
Greetings,
*The TripleO CI in RDO-Cloud has experienced an unplanned outage and is
down at this time. We will update this thread with more information
regarding when the CI will be brought back online as it becomes available.*
Thank you!
Wes Hayutin
__
On Fri, Feb 23, 2018 at 12:09 PM, Wesley Hayutin
wrote:
> Greetings,
>
> *The TripleO CI in RDO-Cloud has experienced an unplanned outage and is
> down at this time. We will update this thread with more information
> regarding when the CI will be brought back online as it be
>
> On Fri, Feb 23, 2018 at 5:40 PM, Wesley Hayutin
> wrote:
> >
> >
> > On Fri, Feb 23, 2018 at 12:09 PM, Wesley Hayutin
> > wrote:
> >>
> >> Greetings,
> >>
> >> The TripleO CI in RDO-Cloud has experienced an unpl
Greetings,
I've heard from a number of people in the TripleO community that they would
prefer the default libvirt settings for quickstart be changed from user
sessions to root system settings [1].
If you have any thoughts or opinions please share them in the launchpad bug
https://bugs.launchpad.n
On Mon, Mar 12, 2018 at 2:18 PM, Gabriele Cerami wrote:
> Hi,
>
> we recently changed our set of scripts to uniform the users workflow
> with the CI workflow.
> One of the results of this change was the reproducer script, that is now
> the official way to spawn a live environment to debug a set o
On Wed, Mar 21, 2018 at 5:11 PM, Ian Wienand wrote:
> On 03/21/2018 03:39 PM, Ian Wienand wrote:
>
>> We will prepare dib 2.12.1 with the fix. As usual there are
>> complications, since the dib gate is broken due to unrelated triple-o
>> issues [2]. In the mean time, probably avoid 2.12.0 if yo
On Thu, Mar 22, 2018 at 8:33 AM, Wesley Hayutin wrote:
>
>
> On Wed, Mar 21, 2018 at 5:11 PM, Ian Wienand wrote:
>
>> On 03/21/2018 03:39 PM, Ian Wienand wrote:
>>
>>> We will prepare dib 2.12.1 with the fix. As usual there are
>>> complications, sin
Greetings,
The upstream packages for master and queens have not been updated in
TripleO in 22 days. We have come very close to a package promotion a
number of times, but failed for several different reasons. In this latest
issue the full tempest job featureset020 was discussed with both Alex and
On Fri, 30 Mar 2018 at 08:45 Paul Grist wrote:
> On Thu, Mar 29, 2018 at 5:32 PM, Emilien Macchi
> wrote:
>
>> Greeting folks,
>>
>> During the last PTG we spent time discussing some ideas around an
>> All-In-One installer, using 100% of the TripleO bits to deploy a single
>> node OpenStack very
On Tue, 3 Apr 2018 at 10:00 Javier Pena wrote:
>
> > Greeting folks,
> >
> > During the last PTG we spent time discussing some ideas around an
> All-In-One
> > installer, using 100% of the TripleO bits to deploy a single node
> OpenStack
> > very similar with what we have today with the container
On Tue, 3 Apr 2018 at 13:53 Dan Prince wrote:
> On Tue, Apr 3, 2018 at 10:00 AM, Javier Pena wrote:
> >
> >> Greeting folks,
> >>
> >> During the last PTG we spent time discussing some ideas around an
> All-In-One
> >> installer, using 100% of the TripleO bits to deploy a single node
> OpenStack
On Thu, 5 Apr 2018 at 12:25 Emilien Macchi wrote:
> On Thu, Apr 5, 2018 at 4:37 AM, Dan Prince wrote:
>
> Much of the work on this is already there. We've been using this stuff
>> for over a year to dev/test the containerization efforts for a long
>> time now (and thanks for your help with this
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 helpful in
finding the history of particular issues.
So hypothetically would it be "wrong" t
On Tue, 10 Apr 2018 at 19:24 Emilien Macchi wrote:
> Note: this is the sixteenth edition of a weekly update of what happens in
> TripleO.
> The goal is to provide a short reading (less than 5 minutes) to learn
> where we are and what we're doing.
> Any contributions and feedback are welcome.
> Li
On Tue, 10 Apr 2018 at 20:51 Emilien Macchi wrote:
> Greetings,
>
> Steve Baker and I had a quick chat today about the work that is being done
> around containers workflow in Rocky cycle.
>
> If you're not familiar with the topic, I suggest to first read the
> blueprint to understand the context
On Tue, Apr 17, 2018 at 9:44 PM Emilien Macchi wrote:
> Note: this is the seventeeth edition of a weekly update of what happens in
> TripleO.
> The goal is to provide a short reading (less than 5 minutes) to learn
> where we are and what we're doing.
> Any contributions and feedback are welcome.
On Tue, May 1, 2018 at 1:23 PM Emilien Macchi wrote:
> On Tue, May 1, 2018 at 10:02 AM, James E. Blair
> wrote:
> [...]
>
> Okay, let's summarize:
>>
>> Proposal 1: All project-template and project-local job variants matching
>> the item's branch must also match the item.
>>
>> * Files and irrel
On Wed, May 9, 2018 at 3:25 PM Alex Schultz wrote:
> 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
FYI.. https://bugs.launchpad.net/tripleo/+bug/1770298
I'm on #openstack-infra chatting w/ Ian atm.
Thanks
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?s
On Wed, May 9, 2018 at 10:43 PM Wesley Hayutin wrote:
> FYI.. https://bugs.launchpad.net/tripleo/+bug/1770298
>
> I'm on #openstack-infra chatting w/ Ian atm.
> Thanks
>
>
Greetings,
I wanted to update everyone on the status of the upstream tripleo check
and gate jobs.
T
On Sat, May 12, 2018 at 11:45 PM Emilien Macchi wrote:
> On Sat, May 12, 2018 at 9:10 AM, Wesley Hayutin
> wrote:
>>
>> 2. Shortly after #1 was resolved CentOS released 7.5 which comes directly
>> into the upstream repos untested and ungated. Additionally the assoc
On Sun, May 13, 2018 at 11:25 AM Jeremy Stanley wrote:
> On 2018-05-13 08:25:25 -0600 (-0600), Wesley Hayutin wrote:
> [...]
> > We need to in coordination with the infra team be able to pin / lock
> > content for production check and gate jobs while also have the abilit
On Sun, May 13, 2018 at 11:30 PM Jeremy Stanley wrote:
> On 2018-05-13 20:44:25 -0600 (-0600), Wesley Hayutin wrote:
> [...]
> > I do think it would be helpful to say have a one week change
> > window where folks are given the opportunity to preflight check a
> > new
On Mon, May 14, 2018 at 10:36 AM Jeremy Stanley wrote:
> On 2018-05-14 07:07:03 -0600 (-0600), Wesley Hayutin wrote:
> [...]
> > I think you may be conflating the notion that ubuntu or rhel/cent
> > can be updated w/o any issues to applications that run atop of the
> > di
On Mon, May 14, 2018 at 12:08 PM Clark Boylan wrote:
> On Mon, May 14, 2018, at 8:57 AM, Wesley Hayutin wrote:
> > On Mon, May 14, 2018 at 10:36 AM Jeremy Stanley
> wrote:
> >
> > > On 2018-05-14 07:07:03 -0600 (-0600), Wesley Hayutin wrote:
> > > [...]
&
On Mon, May 14, 2018 at 12:37 PM Jeremy Stanley wrote:
> On 2018-05-14 09:57:17 -0600 (-0600), Wesley Hayutin wrote:
> > On Mon, May 14, 2018 at 10:36 AM Jeremy Stanley
> wrote:
> [...]
> > > Couldn't a significant burst of new packages cause the same
> > &g
On Sun, May 13, 2018 at 11:50 PM Tristan Cacqueray
wrote:
> On May 14, 2018 2:44 am, Wesley Hayutin wrote:
> [snip]
> > I do think it would be helpful to say have a one week change window where
> > folks are given the opportunity to preflight check a new image and the
> >
On Mon, May 14, 2018 at 11:36 AM Jiří Stránský wrote:
> 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/
On Tue, May 15, 2018 at 1:29 PM James E. Blair wrote:
> Jeremy Stanley writes:
>
> > On 2018-05-15 09:40:28 -0700 (-0700), James E. Blair wrote:
> > [...]
> >> We're also talking about making a new kind of job which can continue to
> >> run after it's "finished" so that you could use it to do so
1 - 100 of 146 matches
Mail list logo
