On Fri, Jan 19, 2018 at 10:21 AM, Wesley Hayutin
wrote:
> 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
On Fri, Dec 15, 2017 at 1:15 PM, Ben Nemec wrote:
>
>
> On 12/15/2017 10:26 AM, Emilien Macchi wrote:
>
>> On Fri, Dec 15, 2017 at 5:04 AM, Arx Cruz wrote:
>> [...]
>>
>>> The goal on this sprint was to enable into quickstart a way to reproduce
>>>
On Fri, Dec 15, 2017 at 11:26 AM, Emilien Macchi wrote:
> On Fri, Dec 15, 2017 at 5:04 AM, Arx Cruz wrote:
> [...]
> > The goal on this sprint was to enable into quickstart a way to reproduce
> > upstream jobs, in your personal RDO cloud tenant, making
I would like to propose Ronelle be given +2 for the above repos. She has
been a solid contributor to tripleo-quickstart and extras almost since the
beginning. She has solid review numbers, but more importantly has always
done quality reviews. She also has been working in the very intense rover
On 03/28/2017 06:57 PM, Alex Schultz wrote:
> Hey folks,
>
> So as part of the capture-environment-status-and-logs blueprint[0],
> I'm working on adding a single command to perform status and log
> collection of the overcloud nodes via the tripleoclient that can be
> used on the undercloud. I
Both Attila and Gabriele have been rockstars with the work to transition
tripleo-ci to run via quickstart, and both have become extremely
knowledgeable about how tripleo-ci works during that process. They are
both very capable of providing thorough and thoughtful reviews of
tripleo-ci patches.
On
On 03/13/2017 10:30 AM, Emilien Macchi wrote:
> Hi,
>
> Alex is already core on instack-undercloud and puppet-tripleo.
+1 it is actually a bit odd to be +2 on puppet-tripleo without being +2
on THT, since so many changes span the two repos.
Moving this thread from rdo-list, but leaving in copy as it is relevant
there too. However it is more of a TripleO topic.
On 02/07/2017 03:56 PM, Paul Belanger wrote:
> On Tue, Feb 07, 2017 at 03:34:09PM -0500, Ronelle Landy wrote:
>> Greetings All,
>>
>> Links to the RDO-CI team scrum[1] and
On 01/30/2017 10:56 AM, Emilien Macchi wrote:
> Sagi, you're now core on TripleO CI repo. Thanks for your hard work on
> tripleo-quickstart transition, and also helping by keeping CI in good
> shape, your work is amazing!
>
> Congrats!
>
> Note: I couldn't add you to tripleo-ci group, but only
On 01/31/2017 11:02 AM, Ben Nemec wrote:
> In the spirit of all the core team changes, here are a couple more I'd
> like to propose.
>
> Dmitry has been very helpful reviewing in instack-undercloud for a long
> time so this is way overdue. I'm also going to propose that he be able
> to +2
On 01/26/2017 10:00 AM, Emilien Macchi wrote:
> On Thu, Jan 26, 2017 at 9:51 AM, John Trowbridge <tr...@redhat.com> wrote:
>>
>>
>> On 01/26/2017 04:03 AM, mathieu bultel wrote:
>>> Hi,
>>>
>>> I'm sending this email to the list to reques
On 01/26/2017 04:03 AM, mathieu bultel wrote:
> Hi,
>
> I'm sending this email to the list to request reviews about the
> composable upgrade work I have been done in Tripleo quickstart. It's
> pending for a while (dec 4 for one of those 2 reviews), and I have
> addressed all the comments on
On 01/24/2017 12:03 PM, Juan Antonio Osorio wrote:
> Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both
> on the current CI solution and in getting tripleo-quickstart jobs for
> it); So I would like to propose him as part of the TripleO CI core team.
>
> I think he'll make a
On 01/21/2017 05:37 AM, Michele Baldessari wrote:
> Hi Emilien,
>
> while not a design session per se, I would love to propose a short slot
> for TripleO CI Q, if we have some time left. In short, I'd like to be
> more useful around CI failures, but I lack the understanding of a few
> aspects
On 01/17/2017 04:36 PM, Emilien Macchi wrote:
> I'm trying to dress a list of things important to know so we can
> successfully deliver Ocata release, please take some time to read and
> comment if needed.
>
> == Triaging Ocata & Pike bugs
>
> As we discussed in our weekly meeting, we decided
On 01/13/2017 09:25 AM, Emilien Macchi wrote:
> On Fri, Jan 13, 2017 at 9:09 AM, Gabriele Cerami wrote:
>>
>> Hi,
>>
>> following a suggestion from Alal Pevec I'm proposing to stop using
>> "current" repo from dlrn and start using "consistent" instead.
>> The main difference
On 01/03/2017 07:30 PM, Emilien Macchi wrote:
> I've noticed some TripleO core reviewers self approving patch without
> respecting our review policy, specially in tripleo-quickstart.
>
This is slightly misleading. To me, self-approving is +2/+A on your own
patch.
What has been going in
On 11/22/2016 03:49 PM, Gabriele Cerami wrote:
> On 22 Nov, Yolanda Robla Mota wrote:
>> Hi all
>> I wanted to start a thread about the current privileges model for TripleO
>> quickstart.
>> Currently there is the assumption that quickstart does not need root
>> privileges after the
On 11/22/2016 09:02 PM, Emilien Macchi wrote:
> == Context
>
> In Newton we added new multinode jobs called "scenarios".
> The challenged we tried to solve was "how to test the maximum of
> services without overloading the nodes that run tests".
>
> Each scenarios deploys a set of services,
On 11/22/2016 12:01 PM, Dougal Matthews wrote:
> Hi all,
>
> I would like to propose we add Julie (jpich) to the TripleO core team for
> python-tripleoclient and tripleo-common. This nomination is based partially
> on review stats[1] and also my experience with her reviews and
> contributions.
On 11/04/2016 01:40 PM, Emilien Macchi wrote:
> MIchele Baldessari (bandini on IRC) has consistently demonstrated high
> levels of contributions in TripleO projects, specifically in High
> Availability area where's he's for us a guru (I still don't understand
> how pacemaker works, but hopefully
On 10/18/2016 07:20 AM, Wesley Hayutin wrote:
> See my response inline.
>
> On Tue, Oct 18, 2016 at 6:07 AM, Dmitry Tantsur wrote:
>
>> On 10/17/2016 11:10 PM, Wesley Hayutin wrote:
>>
>>> Greetings,
>>>
>>> The RDO CI team is considering adding retries to our calls to
Added tripleo tag as this missed my email filter, and therefore may have
missed others as well.
On 10/14/2016 02:01 PM, Wesley Hayutin wrote:
> Greetings,
>
> Hey everyone, I wanted to post a link to a blueprint I'm interested in
> discussing at summit with everyone. Please share your thoughts
On 09/19/2016 01:21 PM, Steven Hardy wrote:
> Hi Alex,
>
> Firstly, thanks for this detailed feedback - it's very helpful to have
> someone with a fresh perspective look at the day-1 experience for TripleO,
> and while some of what follows are "know issues", it's great to get some
> perspective
On 09/15/2016 05:20 AM, Steven Hardy wrote:
> Hi all,
>
> As we work to finish the last remaining tasks for Newton, it's a good time
> to look back over the cycle, and recognize the excellent work done by
> several new contributors.
>
> We've seen a different contributor pattern develop
There were no objections, so I made the change in gerrit.
On 07/26/2016 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, ho
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 the other core reviewers.
I will be out for paternity leave the
Since there were no objections to this, I have added Gabriele to the
tripleo-quickstart core group.
This also means that all patches to tripleo-quickstart now require 2x +2
to merge.
On 07/18/2016 11:06 AM, John Trowbridge wrote:
> Howdy,
>
> I would like to propose Gabriele (pan
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.
This will bring us to three dedicated core reviewers for
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
baremetal virthost). It displaced another ansible based CI tool
%20cloning%20again%5C%22%20AND%20filename%3A%5C%22console.html%5C%22
On 06/23/2016 03:50 PM, John Trowbridge wrote:
>
>
> On 06/23/2016 02:56 PM, Dan Prince wrote:
>> After discovering some regressions today we found what we think is a
>> package build issue in our CI environment whi
On 06/23/2016 02:56 PM, Dan Prince wrote:
> After discovering some regressions today we found what we think is a
> package build issue in our CI environment which might be the cause of
> our issues:
>
> https://bugs.launchpad.net/tripleo/+bug/1595660
>
> Specifically, there is a case where
On 06/09/2016 10:10 AM, Dougal Matthews wrote:
> On 9 June 2016 at 15:03, Steven Hardy wrote:
>
>> Hi all,
>>
>> I've been in discussion with Martin André and Tomas Sedovic, who are
>> involved with the creation of the new tripleo-validations repo[1]
>>
>> We've agreed that
On 05/19/2016 09:31 AM, Dmitry Tantsur wrote:
> Hi all!
>
> We started some discussions on https://review.openstack.org/#/c/300200/
> about the future of node management (registering, configuring and
> introspecting) in the new API, but I think it's more fair (and
> convenient) to move it here.
On 04/11/2016 05:54 AM, John Trowbridge wrote:
> Hola OOOers,
>
> It came up in the meeting last week that we could benefit from a CI
> subteam with its own meeting, since CI is taking up a lot of the main
> meeting time.
>
> I like this idea, and think we should
On 04/11/2016 06:19 AM, Steven Hardy wrote:
> On Mon, Apr 11, 2016 at 05:54:11AM -0400, John Trowbridge wrote:
>> Hola OOOers,
>>
>> It came up in the meeting last week that we could benefit from a CI
>> subteam with its own meeting, since CI is taking up a lot
Hello again,
This is semi-related to the subteam thread, but deserves its own.
I would like to give Lars +2 on tripleo-quickstart. He has contributed
almost as much as I have to the project in terms of
LOC, and in terms of real impact probably more. He is responsible for
some of the best
Hola OOOers,
It came up in the meeting last week that we could benefit from a CI
subteam with its own meeting, since CI is taking up a lot of the main
meeting time.
I like this idea, and think we should do something similar for the other
informal subteams (tripleoclient, UI), and also add a new
On 03/30/2016 02:16 PM, Paul Belanger wrote:
> On Tue, Mar 29, 2016 at 08:30:22PM -0400, John Trowbridge wrote:
>> Hola,
>>
>> With the approval of the tripleo-quickstart spec[1], it is time to
>> actually start doing the work. The first work item is moving it to the
On 03/29/2016 08:30 PM, John Trowbridge wrote:
> Hola,
>
> With the approval of the tripleo-quickstart spec[1], it is time to
> actually start doing the work. The first work item is moving it to the
> openstack git. The spec talks about moving it as is, and this would
Hola,
With the approval of the tripleo-quickstart spec[1], it is time to
actually start doing the work. The first work item is moving it to the
openstack git. The spec talks about moving it as is, and this would
still be fine.
However, there are roles in the tripleo-quickstart tree that are not
+1 I think this is a good exception for the same reasons.
On 03/29/2016 12:27 PM, Steven Hardy wrote:
> On Tue, Mar 29, 2016 at 11:05:00AM -0400, Pradeep Kilambi wrote:
>> Hi Everyone:
>>
>> As Mitaka branch was cut yesterday, I would like to request a backport
>> exception to get gnocchi
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.
>>
>>
>> 1/ Stop creating swap files. We
On 02/19/2016 07:29 AM, Lucas Alvares Gomes wrote:
> Hi,
>
> By removing stable branches you mean stable branches for mitaka and
> newer releases or that includes stable/liberty which already exist as
> well?
>
> I think the latter is more complicated, I don't think we should drop
>
+1, I will also add for reference, that there is no other project in RDO
that is renamed/rebranded. In fact, even the TripleO packages in RDO
have the same naming as the upstream projects.
On 02/17/2016 11:27 AM, David Moreau Simard wrote:
> Greetings,
>
> (Note: cross-posted between rdo-list
On 02/17/2016 08:30 AM, Dmitry Tantsur wrote:
> On 02/17/2016 02:22 PM, John Trowbridge wrote:
>>
>>
>> On 02/17/2016 06:27 AM, Dmitry Tantsur wrote:
>>> Hi everyone!
>>>
>>> Yesterday on the Ironic midcycle we agreed that we would like to remo
On 02/17/2016 06:27 AM, Dmitry Tantsur wrote:
> Hi everyone!
>
> Yesterday on the Ironic midcycle we agreed that we would like to remove
> support for the old bash ramdisk from our code and gate. This, however,
> pose a problem, since we still support Kilo and Liberty. Meaning:
>
> 1. We can't
On 02/15/2016 02:50 PM, James Slagle wrote:
> On Mon, Feb 15, 2016 at 2:05 PM, John Trowbridge <tr...@redhat.com> wrote:
>> Howdy,
>>
>> The spec to replace instack-virt-setup[1] got me thinking about the
>> relationship between RDO and TripleO. Specifica
Howdy,
The spec to replace instack-virt-setup[1] got me thinking about the
relationship between RDO and TripleO. Specifically, when thinking about
where to store/create an undercloud.qcow2 image, and if this effort is
worth duplicating.
Originally, I agreed with the comments on the spec wrt the
On 02/15/2016 03:59 AM, Steven Hardy wrote:
> On Wed, Feb 10, 2016 at 07:05:41PM +0100, James Slagle wrote:
>>On Wed, Feb 10, 2016 at 4:57 PM, Steven Hardy wrote:
>>
>> Hi all,
>>
>> We discussed this in our meeting[1] this week, and agreed a ML
>>
On 01/29/2016 09:40 AM, Dan Prince wrote:
> On Fri, 2016-01-29 at 08:17 -0500, Emilien Macchi wrote:
>> Hi,
>>
>> I'm wondering why don't we use Mitaka CI tested repository [1].
>> IIRC, TripleO is currently using a snapshot which is updated
>> asynchronously by TripleO CI folks.
>> The problem
On 01/27/2016 05:02 PM, James Slagle wrote:
> On Tue, Jan 26, 2016 at 7:15 PM, Derek Higgins wrote:
>
>> 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
Hola Otripletas,
According to the official schedule[1], this week is scheduled for Mitaka
milestone 2. Do we intend to have something working for this milestone?
I have been tracking the issues when deploying with current from all
other projects[2] (as opposed to using an old pinned delorean for
On 12/03/2015 03:47 PM, Dan Prince wrote:
> On Tue, 2015-11-24 at 15:25 +, Dougal Matthews wrote:
>> On 23 November 2015 at 14:37, Dan Prince wrote:
>>> There are lots of references to "workflow" within TripleO
>>> conversations
>>> these days. We are at (or near) the
On 11/10/2015 10:43 AM, Ben Nemec wrote:
> On 11/10/2015 05:26 AM, John Trowbridge wrote:
>>
>>
>> On 11/09/2015 07:44 AM, Dmitry Tantsur wrote:
>>> Hi OOO'ers, hopefully the subject caught your attentions :)
>>>
>>> Currently, tripleoclient expo
On 11/10/2015 10:08 AM, Tzu-Mainn Chen wrote:
> Hi all,
>
> At the last IRC meeting it was agreed that the new TripleO REST API
> should forgo the Tuskar name, and simply be called... the TripleO
> API. There's one more point of discussion: where should the API
> live? There are two
On 11/10/2015 10:37 AM, Giulio Fidente wrote:
> On 11/10/2015 04:16 PM, Dmitry Tantsur wrote:
>> On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote:
>>> Hi all,
>>>
>>> At the last IRC meeting it was agreed that the new TripleO REST API
>>> should forgo the Tuskar name, and simply be called... the
On 11/09/2015 07:44 AM, Dmitry Tantsur wrote:
> Hi OOO'ers, hopefully the subject caught your attentions :)
>
> Currently, tripleoclient exposes several commands in "openstack
> baremetal" and "openstack baremetal introspection" namespaces belonging
> to ironic and ironic-inspector accordingly.
In general, I think this is a good idea. Rather than putting the logic
for this in tripleoclient, it would be better to put it in
tripleo-common. Then the --assign-profiles just calls the function
imported from tripleo-common. This way the GUI could consume the same logic.
On 11/09/2015 09:51 AM,
On 10/14/2015 10:57 AM, Ben Nemec wrote:
> On 10/14/2015 06:38 AM, Dmitry Tantsur wrote:
>> Hi OoO'ers :)
>>
>> It's going to be a long letter, fasten your seat-belts (and excuse my
>> bad, as usual, English)!
>>
>> In RDO Manager we used to have a feature called advanced profiles
>> matching.
On 08/28/2015 10:36 AM, Lucas Alvares Gomes wrote:
Hi,
If you just want to shoot the breeze please respond here. If you
have specific comments on the spec please response there.
I have been thinking about doing it for Ironic as well so I'm looking
for options. IMHO after using WSME I
:40 John Trowbridge tr...@redhat.com
mailto:tr...@redhat.com wrote:
This is a proposal to add a new repository governed by the ironic
inspector subteam. The current repository is named ahc-tools[1],
however
there is no attachment to this name. ironic-inspector-extra
would seem
target, unless there is
interest from new contributors in working on this feature.
* We are planning a talk for Tokyo on inspector that will also include
details about this project.
Thank you very much for your consideration.
Respectfully,
John Trowbridge
[1] https://github.com/rdo-management/ahc
On 06/04/2015 09:29 AM, Dmitry Tantsur wrote:
Hi again!
~ half an hour has passed since my last email, and now I have one more
question to discuss and decide!
At this rate, we could match the [all] tag today.
On the summit we were discussing things like chassis discovery, and
arrived
64 matches
Mail list logo