[openstack-dev] [tripleo] rename ovb jobs?
emilien at redhat.com
Fri Dec 1 14:54:27 UTC 2017
Bogdan and Dmitry's suggestions are imho a bit too much and would lead
to very very (very) long names... Do we actually want that?
On Fri, Dec 1, 2017 at 2:02 AM, Sanjay Upadhyay <supadhya at redhat.com> wrote:
> On Fri, Dec 1, 2017 at 2:17 PM, Bogdan Dobrelya <bdobreli at redhat.com> wrote:
>> On 11/30/17 8:11 PM, Emilien Macchi wrote:
>>> A few months ago, we renamed ovb-updates to be
>>> The name is much longer but it describes better what it's doing.
>>> We know it's a job with one controller, one compute and one storage
>>> node, deploying the quickstart featureset n°24.
>>> For consistency, I propose that we rename all OVB jobs this way.
>>> For example, tripleo-ci-centos-7-ovb-ha-oooq would become
>>> Any thoughts / feedback before we proceed?
>>> Before someone asks, I'm not in favor of renaming the multinode
>>> scenarios now, because they became quite familiar now, and it would
>>> confuse people to rename the jobs.
>> I'd like to see featuresets clarified in names as well. Just to bring the
>> main message, w/o going into the test matrix details, like
>> whatever it is.
> How is this looking?
> I also think we should have clear demarcation of the oooq variables ie
> machine specific goes to nodes/* and feature related goes to featureset/*
>> Best regards,
>> Bogdan Dobrelya,
>> Irc #bogdando
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev