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
On Fri, 21 Sep 2018 at 11:16, Derek Higgins wrote:
> Just quick summary of the status and looking for some input about the
> experimental jobs
>
> 15 jobs are now done, with another 2 ready for reviewing. This leaves 6
> jobs
> 1 x multinode job
>I've yet to finis
Just quick summary of the status and looking for some input about the
experimental jobs
15 jobs are now done, with another 2 ready for reviewing. This leaves 6
jobs
1 x multinode job
I've yet to finished porting this one
2 x grenade jobs
Last time I looked grenade jobs couldn't yet be ported
On 23 February 2018 at 14:48, Derek Higgins wrote:
>
>
> On 1 February 2018 at 16:18, Emilien Macchi wrote:
>
>> On Thu, Feb 1, 2018 at 8:05 AM, Derek Higgins wrote:
>> [...]
>>
>>> o Should I create a new tempest test for baremetal as some of
On 18 April 2018 at 17:12, Derek Higgins wrote:
>
>
> On 18 April 2018 at 14:22, Bogdan Dobrelya wrote:
>
>> On 4/18/18 12:07 PM, Derek Higgins wrote:
>>
>>> Hi All,
>>>
>>> I've been testing the ironic inspector containerised service
On 18 April 2018 at 14:22, Bogdan Dobrelya wrote:
> On 4/18/18 12:07 PM, Derek Higgins wrote:
>
>> Hi All,
>>
>> I've been testing the ironic inspector containerised service in the
>> overcloud, the service essentially works but there is a couple of hurdles
&
Hi All,
I've been testing the ironic inspector containerised service in the
overcloud, the service essentially works but there is a couple of hurdles
to tackle to set it up, the first of these is how to get the IPA kernel
and ramdisk where they need to be.
These need to be be present in the iron
On 1 February 2018 at 16:18, Emilien Macchi wrote:
> On Thu, Feb 1, 2018 at 8:05 AM, Derek Higgins wrote:
> [...]
>
>> o Should I create a new tempest test for baremetal as some of the
>>>> networking stuff is different?
>>>>
>>>
>>>
On 1 February 2018 at 15:36, Emilien Macchi wrote:
>
>
> On Thu, Feb 1, 2018 at 6:35 AM, Derek Higgins wrote:
>
>> Hi All,
>>I've been working on a set of patches as a WIP to test ironic in the
>> overcloud[1], the approach I've started with is to add
Hi All,
I've been working on a set of patches as a WIP to test ironic in the
overcloud[1], the approach I've started with is to add ironic into the
overcloud controller in scenario004. Also to run a script on the controller
(as a NodeExtraConfigPost) that sets up a VM with vbmc that can then be
On 19 December 2017 at 22:23, Brian Haley wrote:
> On 12/19/2017 04:00 PM, Ben Nemec wrote:
>
>>
>>
>> On 12/19/2017 02:43 PM, Brian Haley wrote:
>>
>>> On 12/19/2017 11:53 AM, Ben Nemec wrote:
>>>
The reboot is done (mostly...see below).
On 12/18/2017 05:11 PM, Joe Talerico wrote:
On 30 October 2017 at 15:16, Julia Kreger wrote:
...
>>> When I tried it I got this
>>> [ 370.704896] dracut-initqueue[387]: Warning: iscistart: Could not
>>> get list of targets from firmware.
>>>
>>> perhaps we could alter iscistart to not complain if there are no
>>> targets attached and just
On 25 October 2017 at 13:03, Dmitry Tantsur wrote:
> (ooops, I somehow missed this email. sorry!)
>
> Hi Yolanda,
>
> On 10/16/2017 11:06 AM, Yolanda Robla Mota wrote:
>>
>> Hi
>> Recently i've been helping some customers in the boot from ISCSI feature.
>> So far everything was working, but we had
On 19 July 2017 at 17:02, Derek Higgins wrote:
> On 17 July 2017 at 15:56, Derek Higgins wrote:
>> On 17 July 2017 at 15:37, Emilien Macchi wrote:
>>> On Thu, Jul 13, 2017 at 6:01 AM, Emilien Macchi wrote:
>>>> On Thu, Jul 13, 2017 at 1:55 AM, Derek Higgins wrot
On 17 July 2017 at 15:56, Derek Higgins wrote:
> On 17 July 2017 at 15:37, Emilien Macchi wrote:
>> On Thu, Jul 13, 2017 at 6:01 AM, Emilien Macchi wrote:
>>> On Thu, Jul 13, 2017 at 1:55 AM, Derek Higgins wrote:
>>>> On 12 July 2017 at 22:33, Emilien Macchi wro
On 17 July 2017 at 15:37, Emilien Macchi wrote:
> On Thu, Jul 13, 2017 at 6:01 AM, Emilien Macchi wrote:
>> On Thu, Jul 13, 2017 at 1:55 AM, Derek Higgins wrote:
>>> On 12 July 2017 at 22:33, Emilien Macchi wrote:
>>>> On Wed, Jul 12, 2017 at
On 12 July 2017 at 22:33, Emilien Macchi wrote:
> On Wed, Jul 12, 2017 at 2:23 PM, Emilien Macchi wrote:
> [...]
>> Derek, it seems like you want to deploy Ironic on scenario006
>> (https://review.openstack.org/#/c/474802). I was wondering how it
>> would work with multinode jobs.
>
> Derek, I al
On 12 July 2017 at 22:23, Emilien Macchi wrote:
> Hey folks,
>
> Derek, it seems like you want to deploy Ironic on scenario006
> (https://review.openstack.org/#/c/474802). I was wondering how it
> would work with multinode jobs.
The idea was that we would create a libvirt domain on the overcloud
On 22 March 2017 at 22:36, Ben Nemec wrote:
> Hi all (owl?),
>
> You may have missed it in all the ci excitement the past couple of days, but
> we had a partial outage of rh1 last night. It turns out the OVS port issue
> Derek discussed in
> http://lists.openstack.org/pipermail/openstack-dev/2016
On 16 December 2016 at 21:40, Ben Nemec wrote:
> Just a heads up for everyone, I've added some DB cleanup jobs to rh1 which
> will hopefully prevent the performance degradations over time that we've
> been seeing in that environment. Specifically, the crontab now looks like
> this:
>
> # Clean up
On 7 October 2016 at 14:03, Paul Belanger wrote:
> Greetings,
>
> I wanted to propose a work item, that I am happy to spearhead, about setting
> up
> a 3rd party CI system for tripleo project. The work I am proposing, wouldn't
> actually affect anything today about tripleo-ci but provider a worki
On 9 September 2016 at 16:38, Paul Belanger wrote:
> Greetings,
>
> I would like to start the discussions around the removal of the bastion host
> that sits in front of tripleo-test-cloud-rh1. It is my understanding, all
> traffic from tripleo-test-cloud-rh1 flows through this linux box. Obvious
On 25 August 2016 at 02:56, Paul Belanger wrote:
> On Wed, Aug 24, 2016 at 02:11:32PM -0400, James Slagle wrote:
>> The latest recurring problem that is failing a lot of the nonha ssl
>> jobs in tripleo-ci is:
>>
>> https://bugs.launchpad.net/tripleo/+bug/1616144
>> tripleo-ci: nonha jobs failing
On 24 August 2016 at 19:11, James Slagle wrote:
> The latest recurring problem that is failing a lot of the nonha ssl
> jobs in tripleo-ci is:
>
> https://bugs.launchpad.net/tripleo/+bug/1616144
> tripleo-ci: nonha jobs failing with Unable to establish connection to
> https://192.0.2.2:13004/v1/a9
On 19 August 2016 at 11:08, Giulio Fidente wrote:
> On 08/19/2016 11:41 AM, Derek Higgins wrote:
>>
>> On 19 August 2016 at 00:07, Sagi Shnaidman wrote:
>>>
>>> Hi,
>>>
>>> we have a problem again with not enough memory in HA jobs, al
On 19 August 2016 at 00:07, Sagi Shnaidman wrote:
> Hi,
>
> we have a problem again with not enough memory in HA jobs, all of them
> constantly fails in CI: http://status-tripleoci.rhcloud.com/
Have we any idea why we need more memory all of a sudden? For months
the overcloud nodes have had 5G of
On 27 July 2016 at 17:52, Paul Belanger wrote:
> On Wed, Jul 27, 2016 at 02:54:00PM +0100, Derek Higgins wrote:
>> On 21 July 2016 at 23:04, Paul Belanger wrote:
>> > Greetings,
>> >
>> > I write today to see how I can remove this server from
>> >
On 21 July 2016 at 23:04, Paul Belanger wrote:
> Greetings,
>
> I write today to see how I can remove this server from
> tripleo-test-cloud-rh2. I
> have an open patch[1] currently to migrate tripleo-ci to use our AFS mirrors
> for
> centos and epel. However, I'm still struggling to see what el
Trying to catch up here and summarizing as a top post
so as I see it we have a number of problems that all need sorting out
Regardless of the branch being built, tripleo-ci is currently building
it with the packaging for master
- in most cases this has worked out ok because most projects don't
h
Hi All,
Yesterday the final patch merged to run CI jobs on RH2, and last
night we merged the patch to tripleo-ci to support RH2 jobs. So we now
have a new job (gate-tripleo-ci-centos-7-ovb-ha) running on all
tripleo patch reviews. This job is running pacemaker HA with a 3 node
controller and a
Hi All,
A while back we populated a etherpad[1] with details of our
individual development environments, the idea here was that we can
point newcomers to this page to give them an idea of what hard ware
its possible to deploy triple on and what tools we use drive it.
Its been just over 3 mo
On 13 June 2016 at 21:29, Ben Nemec wrote:
> So our documented repo setup steps are three curls, a sed, and a
> multi-line bash command. And the best part? That's not even what we
> test. The commands we actually use in tripleo.sh --repo-setup consist
> of the following: three curls, four seds,
On 19 May 2016 5:38 pm, "Paul Belanger" wrote:
>
> On Thu, May 19, 2016 at 03:50:15PM +0100, Derek Higgins wrote:
> > On 18 May 2016 at 13:34, Paul Belanger wrote:
> > > On Wed, May 18, 2016 at 12:22:55PM +0100, Derek Higgins wrote:
> > >> O
On 18 May 2016 at 13:34, Paul Belanger wrote:
> On Wed, May 18, 2016 at 12:22:55PM +0100, Derek Higgins wrote:
>> On 6 May 2016 at 14:18, Paul Belanger wrote:
>> > On Tue, May 03, 2016 at 05:34:55PM +0100, Steven Hardy wrote:
>> >> Hi all,
>> >>
>&g
On 6 May 2016 at 14:18, Paul Belanger wrote:
> On Tue, May 03, 2016 at 05:34:55PM +0100, Steven Hardy wrote:
>> Hi all,
>>
>> Some folks have requested a summary of our summit sessions, as has been
>> provided for some other projects.
>>
>> I'll probably go into more detail on some of these topics
On 16 May 2016 at 18:16, Paul Belanger wrote:
> Greetings,
>
> Over the last few weeks I've been head deep into understanding the TripleO CI
> pipeline. For the most part, I am happy that we have merged centos-7 DIB
> support and I'm working to migrate the jobs to it.
>
> Something I have been tr
On 11 May 2016 at 10:24, Derek Higgins wrote:
> Hi All,
> I'll be taking down the tripleo cloud today for the hardware
> upgrade, The cloud will be take down at about 1PM UTC and I'll start
> bringing it back up once dcops have finished installing the new HW. We
> sh
On 6 May 2016 at 15:36, Derek Higgins wrote:
> Hi All,
>the long awaited RAM and SSD's have arrived for the tripleo rack,
> I'd like to schedule a time next week to do the install which will
> involve and outage window. We could attempt to do it node by node but
> the co
On 6 May 2016 at 15:57, Ben Nemec wrote:
> \o/
>
> On 05/06/2016 09:36 AM, Derek Higgins wrote:
>> Hi All,
>>the long awaited RAM and SSD's have arrived for the tripleo rack,
>> I'd like to schedule a time next week to do the install which will
>>
On 6 May 2016 at 17:50, James Slagle wrote:
> On Fri, May 6, 2016 at 10:36 AM, Derek Higgins wrote:
>> Hi All,
>>the long awaited RAM and SSD's have arrived for the tripleo rack,
>> I'd like to schedule a time next week to do the install which will
>>
Hi All,
the long awaited RAM and SSD's have arrived for the tripleo rack,
I'd like to schedule a time next week to do the install which will
involve and outage window. We could attempt to do it node by node but
the controller needs to come down at some stage anyways and doing
other nodes groups
On 13 April 2016 at 09:58, Steven Hardy wrote:
> On Tue, Apr 12, 2016 at 11:08:28PM +0200, Gabriele Cerami wrote:
>> On Fri, 2016-04-08 at 16:18 +0100, Steven Hardy wrote:
>>
>> > Note we're not using devtest at all anymore, the developer script
>> > many
>> > folks use is tripleo.sh:
>>
>> So, I
On 7 April 2016 at 22:03, Gabriele Cerami wrote:
> Hi,
>
> I'm trying to find an entry point to join the effort in TripleO CI.
Hi Gabriele, welcome aboard
> I studied the infrastructure and the scripts, but there's still something I'm
> missing.
> The last step of studying the complex landscape
On 17 March 2016 at 16:59, Ben Nemec wrote:
> On 03/10/2016 05:24 PM, Jeremy Stanley wrote:
>> On 2016-03-10 16:09:44 -0500 (-0500), Dan Prince wrote:
>>> This seems to be the week people want to pile it on TripleO. Talking
>>> about upstream is great but I suppose I'd rather debate major changes
On 20 March 2016 at 18:32, Dan Prince wrote:
> I'd like to propose that we add John Trowbridge to the TripleO core
> review team. John has become one of the goto guys in helping to chase
> down upstream trunk chasing issues. He has contributed a lot to helping
> keep general CI issues running and
On 20 March 2016 at 18:22, Dan Prince wrote:
> I'd like to propose that we add Emilien Macchi to the TripleO core
> review team. Emilien has been getting more involved with TripleO during
> this last release. In addition to help with various Puppet things he
> also has experience in building OpenS
On 16 March 2016 at 02:41, Emilien Macchi wrote:
> I did some testing again and I'm still running in curl issues:
> http://paste.openstack.org/show/BU7UY0mUrxoMUGDhXgWs/
>
> I'll continue investigation tomorrow.
btw, tripleo-ci seems to be doing reasonably well this morning, I
don't see any failu
On 14 March 2016 at 14:26, Dan Prince wrote:
> Looking at the stats for the last 180 days I'd like to propose we
> cleanup TripleO core a bit:
>
> http://russellbryant.net/openstack-stats/tripleo-reviewers-180.txt
>
> There are a few reviewers with low numbers of reviews (just added to
> the tripl
On 14 March 2016 at 14:38, Dan Prince wrote:
> http://russellbryant.net/openstack-stats/tripleo-reviewers-180.txt
>
> Our top reviewer over the last half a year ejuaso (goes by Ozz for
> Osorio or jaosorior on IRC). His reviews seem consistent, he
> consistently attends the meetings and he chimes
On 9 March 2016 at 07:08, Richard Su wrote:
>
>
> On 03/08/2016 09:58 AM, Derek Higgins wrote:
>>
>> On 7 March 2016 at 18:22, Ben Nemec wrote:
>>>
>>> On 03/07/2016 11:33 AM, Derek Higgins wrote:
>>>>
>>>> On 7 March 2016 at 15
On 7 March 2016 at 18:22, Ben Nemec wrote:
> On 03/07/2016 11:33 AM, Derek Higgins wrote:
>> On 7 March 2016 at 15:24, Derek Higgins wrote:
>>> On 6 March 2016 at 16:58, James Slagle wrote:
>>>> On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi wrote:
>>>&g
On 7 March 2016 at 12:11, John Trowbridge wrote:
>
>
> On 03/06/2016 11:58 AM, James Slagle wrote:
>> On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi wrote:
>>> I'm kind of hijacking Dan's e-mail but I would like to propose some
>>> technical improvements to stop having so much CI failures.
>>>
>
On 7 March 2016 at 15:24, Derek Higgins wrote:
> On 6 March 2016 at 16:58, James Slagle wrote:
>> On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi wrote:
>>> I'm kind of hijacking Dan's e-mail but I would like to propose some
>>> technical improvemen
On 6 March 2016 at 16:58, James Slagle wrote:
> On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi wrote:
>> I'm kind of hijacking Dan's e-mail but I would like to propose some
>> technical improvements to stop having so much CI failures.
>>
>>
>> 1/ Stop creating swap files. We don't have SSD, this
On 10/02/16 18:05, James Slagle wrote:
On Wed, Feb 10, 2016 at 4:57 PM, Steven Hardy mailto:sha...@redhat.com>> wrote:
Hi all,
We discussed this in our meeting[1] this week, and agreed a ML
discussion
to gain consensus and give folks visibility of the outcome would be
a
Hi All,
We briefly discussed feature tracking in this weeks tripleo meeting. I
would like to provide a way for downstream consumers (and ourselves) to
track new features as they get implemented. The main things that came
out of the discussion is that people liked the spec-lite process that
th
Hi All,
For the last few months we've been alerting the #tripleo irc channel
when a card is open on the tripleo trello org, in the urgent list.
When used I think it served a good purpose to alert people to the fact
that deploying master is currently broken, but it hasn't been used as
much as
PM, Zane Bitter
wrote:
>
>Â Â Â On 30/11/15 12:51, Ruby Loo wrote:
>
>Â Â Â Â On 30 November 2015 at 10:19, Derek Higgins
    <mailto:der...@redhat.com>> wrote:
>
>Â Â Â Â Ã*Â Ã*Â Hi All,
>
On 30/11/15 22:18, Steven Hardy wrote:
On Mon, Nov 30, 2015 at 12:51:53PM -0500, Ruby Loo wrote:
On 30 November 2015 at 10:19, Derek Higgins wrote:
Hi All,
  A few months tripleo switch from its devtest based CI to one that
was based on instack. Before doing this
On 30/11/15 17:03, Dmitry Tantsur wrote:
On 11/30/2015 04:19 PM, Derek Higgins wrote:
Hi All,
A few months tripleo switch from its devtest based CI to one that
was based on instack. Before doing this we anticipated disruption in the
ci jobs and removed them from non tripleo projects
Hi All,
A few months tripleo switch from its devtest based CI to one that
was based on instack. Before doing this we anticipated disruption in the
ci jobs and removed them from non tripleo projects.
We'd like to investigate adding it back to heat and ironic as these
are the two proje
On 03/11/15 15:25, Gregory Haynes wrote:
Hello everyone,
I would like to propose adding Ian Wienand as a core reviewer on the
diskimage-builder project. Ian has been making a significant number of
contributions for some time to the project, and has been a great help in
reviews lately. Thus, I
On 25/09/15 13:34, Dan Prince wrote:
It has come to my attention that we aren't making great use of our
tripleo.org domain. One thing that would be useful would be to have the
new tripleo-docs content displayed there. It would also be nice to have
quick links to some of our useful resources, pe
On 15/09/15 12:38, Derek Higgins wrote:
On 10/09/15 15:12, Derek Higgins wrote:
Hi All,
The current meeting slot for TripleO is every second Tuesday @ 1900 UTC,
since that time slot was chosen a lot of people have joined the team and
others have moved on, I like to revisit the timeslot to
On 10/09/15 15:12, Derek Higgins wrote:
Hi All,
The current meeting slot for TripleO is every second Tuesday @ 1900 UTC,
since that time slot was chosen a lot of people have joined the team and
others have moved on, I like to revisit the timeslot to see if we can
accommodate more people at the
On 10/09/15 15:06, James Slagle wrote:
TripleO has added a few new repositories, one of which is
python-tripleoclient[1], the former python-rdomanager-oscplugin.
With the additional repositories, there is an additional review burden
on our core reviewers. There is also the fact that folks who
Hi All,
The current meeting slot for TripleO is every second Tuesday @ 1900 UTC,
since that time slot was chosen a lot of people have joined the team and
others have moved on, I like to revisit the timeslot to see if we can
accommodate more people at the meeting (myself included).
Sticking w
On 09/09/15 18:03, Jason Rist wrote:
On 09/09/2015 07:09 AM, Derek Higgins wrote:
On 08/09/15 16:36, Derek Higgins wrote:
Hi All,
Some of ye may remember some time ago we used to organize TripleO
based jobs/tasks on a trello board[1], at some stage this board fell out
of use (the
On 08/09/15 16:36, Derek Higgins wrote:
Hi All,
Some of ye may remember some time ago we used to organize TripleO
based jobs/tasks on a trello board[1], at some stage this board fell out
of use (the exact reason I can't put my finger on). This morning I was
putting a list of t
Hi All,
Some of ye may remember some time ago we used to organize TripleO
based jobs/tasks on a trello board[1], at some stage this board fell out
of use (the exact reason I can't put my finger on). This morning I was
putting a list of things together that need to be done in the area of CI
On 03/09/15 07:34, Derek Higgins wrote:
Hi All,
The patch to reshuffle our CI jobs has merged[1], along with the patch
to switch the f21-noha job to be instack based[2] (with centos images).
So the current status is that our CI has been removed from most of the
non tripleo projects (with the
Hi All,
The patch to reshuffle our CI jobs has merged[1], along with the patch
to switch the f21-noha job to be instack based[2] (with centos images).
So the current status is that our CI has been removed from most of the
non tripleo projects (with the exception of nova/neutron/heat and ironi
08/19/2015 12:22 PM, Dougal Matthews wrote:
- Original Message -
From: "Dmitry Tantsur"
To: openstack-dev@lists.openstack.org
Sent: Wednesday, 19 August, 2015 5:57:36 PM
Subject: Re: [openstack-dev] [TripleO] Moving instack upstream
On 08/19/2015 06:42 PM, Derek Higgins wro
rds)
https://review.openstack.org/#/c/205479/
3. pull in 3 repositories upstream
https://review.openstack.org/#/c/215186/
There will be follow up patches after these but this will get the ball
rolling
thanks,
Derek.
On 23/07/15 07:40, Derek Higgins wrote:
See below
On 21/07/15 20:29, Derek Higgins wrot
On 06/08/15 15:01, Dougal Matthews wrote:
- Original Message -
From: "Dan Prince"
To: "OpenStack Development Mailing List (not for usage questions)"
Sent: Thursday, 6 August, 2015 1:12:42 PM
Subject: Re: [openstack-dev] [TripleO] Moving instack upstream
I would really like to see
On 24/07/15 00:56, James Slagle wrote:
On Thu, Jul 23, 2015 at 2:40 AM, Derek Higgins wrote:
See below
On 21/07/15 20:29, Derek Higgins wrote:
Hi All,
Something we discussed at the summit was to switch the focus of
tripleo's deployment method to deploy using instack using i
See below
On 21/07/15 20:29, Derek Higgins wrote:
Hi All,
Something we discussed at the summit was to switch the focus of
tripleo's deployment method to deploy using instack using images built
with tripleo-puppet-elements. Up to now all the instack work has been
done downstream of tr
On 22/07/15 18:41, Gregory Haynes wrote:
Excerpts from Derek Higgins's message of 2015-07-21 19:29:49 +:
Hi All,
Something we discussed at the summit was to switch the focus of
tripleo's deployment method to deploy using instack using images built
with tripleo-puppet-elements. Up to now
Hi All,
Something we discussed at the summit was to switch the focus of
tripleo's deployment method to deploy using instack using images built
with tripleo-puppet-elements. Up to now all the instack work has been
done downstream of tripleo as part of rdo. Having parts of our
deployment stor
On 09/06/15 10:37, Dirk Müller wrote:
Hi Derek,
2015-06-09 0:34 GMT+02:00 Derek Higgins :
This patch would result in 80 packaging repositories being pulled into
gerrit.
I personally would prefer to start with fewer but common packages
between all RPM distros (is there more than Red Hat
On 03/06/15 17:28, Haïkel wrote:
2015-06-03 17:23 GMT+02:00 Thomas Goirand :
i
On 06/03/2015 12:41 AM, James E. Blair wrote:
Hi,
This came up at the TC meeting today, and I volunteered to provide an
update from the discussion.
I've just read the IRC logs. And there's one thing I would like
On 02/06/15 23:41, James E. Blair wrote:
Hi,
This came up at the TC meeting today, and I volunteered to provide an
update from the discussion.
In general, I think there is a lot of support for a packaging effort in
OpenStack. The discussion here has been great; we need to answer a few
questi
On 29/05/15 02:54, Steve Kowalik wrote:
On 29/05/15 06:41, Haïkel wrote:
Here's the main script to rebuild a RPM package.
https://github.com/openstack-packages/delorean/blob/master/scripts/build_rpm.sh
The script basically uses rpmbuild to build packages, we could have a
build_deb.sh that use
On 28/05/15 20:58, Paul Belanger wrote:
On 05/27/2015 05:26 PM, Derek Higgins wrote:
On 27/05/15 09:14, Thomas Goirand wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
tl;dr:
- - We'd like to push distribution packaging of OpenStack on upstream
gerrit with reviews.
-
On 28/05/15 22:09, Thomas Goirand wrote:
On 05/28/2015 02:53 PM, Derek Higgins wrote:
On 28/05/15 12:07, Jaume Devesa wrote:
Hi Thomas,
Delorean is a tool to build rpm packages from master branches (maybe any
branch?) of OpenStack projects.
Check out here:
https://www.rdoproject.org
otice that the rpm's are being
built using rpmbuild inside a docker container, if expanding to add dep
support this is where we could plug in sbuild.
Regards,
On Thu, 28 May 2015 10:40, Thomas Goirand wrote:
Derek,
Thanks for what you wrote.
On 05/27/2015 11:26 PM, Derek Higgins wrot
On 27/05/15 09:14, Thomas Goirand wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
tl;dr:
- - We'd like to push distribution packaging of OpenStack on upstream
gerrit with reviews.
- - The intention is to better share the workload, and improve the overall
QA for packaging *and* up
On 05/05/15 12:57, James Slagle wrote:
Hi, I'd like to propose adding Giulio Fidente and Steve Hardy to TripleO Core.
Giulio has been an active member of our community for a while. He
worked on the HA implementation in the elements and recently has been
making a lot of valuable contributions a
On 11/04/15 14:02, Dan Prince wrote:
Looks like our SSL certificate has expired for the currently active CI
cloud. We are working on getting a new one generated and installed.
Until then CI jobs won't get processed.
A new cert has been installed in the last few minutes and ZUUL has
started kic
Tl;dr tripleo ci is back up and running, see below for more
On 21/03/15 01:41, Dan Prince wrote:
Short version:
The RH1 CI region has been down since yesterday afternoon.
We have a misbehaving switch and have file a support ticket with the
vendor to troubleshoot things further. We hope to kno
On 11/02/15 17:06, Dan Prince wrote:
I wanted to take a few minutes to go over the progress we've made with
TripleO Puppet in Kilo so far.
For those unfamilar with the efforts our initial goal was to be able to
use Puppet as the configuration tool for a TripleO deployment stack.
This is largely
elf a group of 15 bugs.
thanks,
Derek.
On 18/12/14 11:25, Derek Higgins wrote:
> While bug squashing yesterday, I went through quite a lot of bugs
> closing those that were already fixed or no longer relevant, closing
> around 40 bugs. I eventually ran out of time, but I'm pretty sur
On 08/01/15 05:21, Zhou, Zhenzan wrote:
> Hi,
>
> Does anyone know why TripleO uses "regionOne" as default region name? A
> comment in the code says it's the default keystone uses.
> But I cannot find any "regionOne" in keystone code. Devstack uses "RegionOne"
> by default and I do see lots of
On 07/01/15 23:41, Ben Nemec wrote:
> On 01/07/2015 11:29 AM, Clint Byrum wrote:
>> Excerpts from Derek Higgins's message of 2015-01-07 02:51:41 -0800:
>>> Hi All,
>>> I intended to bring this up at this mornings meeting but the train I
>>> was on had no power sockets (and I had no battery) so
Hi All,
I intended to bring this up at this mornings meeting but the train I
was on had no power sockets (and I had no battery) so sending to the
list instead.
We currently run our CI with on images built for i386, we took this
decision a while back to save memory ( at the time is allowed us t
See below, We got only 5 people signed up, anybody else willing to join
the effort ?
TL;DR if your willing to assess about 15 tripleo related bugs to decide
if they are still current then add your name to the etherpad.
thanks,
Derek
On 18/12/14 11:25, Derek Higgins wrote:
> While bug squash
On 18/12/14 08:48, Steve Kowalik wrote:
> Hai,
>
> I am finding myself at a loss at explaining how the CI clouds that run
> the tripleo jobs work from end-to-end. I am clear that we have a tripleo
> deployment running on those racks, with a seed, a HA undercloud and
> overcloud, but then I'm
While bug squashing yesterday, I went through quite a lot of bugs
closing those that were already fixed or no longer relevant, closing
around 40 bugs. I eventually ran out of time, but I'm pretty sure if we
split the task up between us we could weed out a lot more.
What I'd like to do is, as a onc
On 04/12/14 13:37, Dan Prince wrote:
> On Thu, 2014-12-04 at 11:51 +0000, Derek Higgins wrote:
>> A month since my last update, sorry my bad
>>
>> since the last email we've had 5 incidents causing ci failures
>>
>> 26/11/2014 : Lots of ubuntu jobs failed over
A month since my last update, sorry my bad
since the last email we've had 5 incidents causing ci failures
26/11/2014 : Lots of ubuntu jobs failed over 24 hours (maybe half)
- We seem to suffer any time an ubuntu mirror isn't in sync causing hash
mismatch errors. For now I've pinned DNS on our pro
1 - 100 of 159 matches
Mail list logo
