Hi,
On 09/11/2018 12:08 PM, Bogdan Dobrelya wrote:
> On 9/11/18 4:43 AM, James Slagle wrote:
>> On Mon, Sep 10, 2018 at 10:12 AM Jiri Tomasek
>> wrote:
>>>
>>> Hi Mathieu,
>>>
>>> Thanks for bringing up the topic. There are several efforts
>>> currently in progress which should lead to solving
Hi folks,
Last week I wrote a BluePrint and a spec [1] to propose to change the
way we used and managed the Plan in TripleO for the Deployment and the
Life cycle (update/upgrade and scale).
While I was working on trying to simplified the implementation of the
Update and Upgrade for a end user
Hi
On 08/30/2018 04:28 PM, Honza Pokorny wrote:
> Hello!
>
> Over the last few months, it seems that tripleo-quickstart has evolved
> into a CI tool. It's primarily used by computers, and not humans.
> tripleo-quickstart is a helpful set of ansible playbooks, and a
> collection of feature sets.
and there is no big value in
this except when people external of the DFG bring things, like Weshay
used to or rdo-cloud folks.
Thank you all.
Mathieu
[1]
https://etherpad.openstack.org/p/tripleo-upgrade-squad-meeting
On 11/09/2017 01:23 PM, mathieu bultel wrote:
> Hi TripleO,
>
> A
and there is no big value in
this except when people external of the DFG bring things, like Weshay
used to or rdo-cloud folks.
Thank you all.
Mathieu
[1]
https://etherpad.openstack.org/p/tripleo-upgrade-squad-meeting
On 11/09/2017 01:23 PM, mathieu bultel wrote:
> Hi TripleO,
>
> A
On 12/06/2017 04:45 PM, Emilien Macchi wrote:
> Team,
>
> Wes has been consistently and heavily involved in TripleO CI work.
> He has a very well understanding on how tripleo-quickstart and
> tripleo-quickstart-extras work, his number and quality of reviews are
> excellent so far. His experience
+1 indeed :)
On 11/29/2017 08: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 beginning. She has solid review numbers, but more
> importantly has always done
On 11/07/2017 11: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 infrastructure and instead focus our efforts in RDO
>>
Hi TripleO,
As discuss on the last TripleO meeting, the Upgrade squad will stand a
weekly meeting each Friday to discuss and share about the Upgrade
related topics.
Every body who are interested is welcome to join us and fell free to
raise any questions/issues/concerns.
Tomorrow will be our
Hi,
On 09/28/2017 05:05 AM, Emilien Macchi wrote:
> I was reviewing https://review.openstack.org/#/c/487496/ and
> https://review.openstack.org/#/c/487488/ when I realized that we still
> didn't have any test coverage for minor updates.
> We never had this coverage AFICT but this is not a reason
On 07/18/2017 11:22 PM, Emilien Macchi wrote:
> On Mon, Jul 17, 2017 at 12:10 PM, Emilien Macchi wrote:
>> Since we have mixed feelings but generally agree that we should give
>> it a try, let's give it a try and see how it goes, at least one time,
>> tomorrow.
> So we tried
On 05/08/2017 01:45 PM, Marios Andreou wrote:
> Hi folks, after some discussion locally with colleagues about
> improving the upgrades experience, one of the items that came up was
> pre-upgrade and update validations. I took an AI to look at the
> current status of tripleo-validations [0] and
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 time, rebase & so one [1].
Those reviews is required, and very
On 01/17/2017 05:19 PM, Emilien Macchi wrote:
> On Tue, Jan 17, 2017 at 10:57 AM, mathieu bultel <mbul...@redhat.com> wrote:
>> On 01/17/2017 04:42 PM, Emilien Macchi wrote:
>>> On Tue, Jan 17, 2017 at 9:34 AM, mathieu bultel <mbul...@redhat.com> wrote:
>>>
On 01/17/2017 04:42 PM, Emilien Macchi wrote:
> On Tue, Jan 17, 2017 at 9:34 AM, mathieu bultel <mbul...@redhat.com> wrote:
>> Hi Adriano
>>
>> On 01/17/2017 03:05 PM, Adriano Petrich wrote:
>>
>> So I want to make a backwards compatibility job upstream
Hi Adriano
On 01/17/2017 03:05 PM, Adriano Petrich wrote:
> So I want to make a backwards compatibility job upstream so from last
> scrum I got the feeling that we should not be adding more stuff to the
> experimental jobs due to lack of resources (and large queues)
>
What kind of "test" do you
On 12/14/2016 10:17 AM, Julie Pichon wrote:
> On 14 December 2016 at 08:56, Dougal Matthews wrote:
>> On 13 December 2016 at 16:12, Emilien Macchi wrote:
>>> On Tue, Dec 13, 2016 at 10:58 AM, Marios Andreou
>>> wrote:
Hi OOOs o/ as
On 11/04/2016 06: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
, to trigger the experimental pipeline and
see what's going on with the upgrade.
( and example of the state of the full upgrade job:
http://logs.openstack.org/50/323750/54/experimental-tripleo/gate-tripleo-ci-centos-7-ovb-nonha-upgrades-nv/45916e6/console.html)
On 09/09/2016 09:29 AM, mathieu bultel
On 09/09/2016 12:42 AM, Emilien Macchi wrote:
> On Thu, Sep 8, 2016 at 4:18 PM, David Moreau Simard wrote:
>> How long does the upgrade job take ?
> undercloud upgrade is a matter of 10 min max.
> overcloud upgrade will be much more, I don't have metrics right now.
> matbu maybe?
On 08/18/2016 09:29 AM, Marios Andreou wrote:
> On 17/08/16 15:46, Jiří Stránský wrote:
>> On 16.8.2016 21:08, Brad P. Crochet wrote:
>>> Hello TripleO-ians,
>>>
>>> I've started to look again at the introduced, but unused/undocumented
>>> upgrade commands. It seems to me that given the current
21 matches
Mail list logo