Open Stack

On Thu, Nov 30, 2017 at 9:11 PM, Emilien Macchi <emilien at redhat.com> wrote:

> A few months ago, we renamed ovb-updates to be
> tripleo-ci-centos-7-ovb-1ctlr_1comp_1ceph-featureset024.
> 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
> tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001
> etc.
>
Sounds reasonable. That would make it easier for me to check what's
actually in the featureset, as opposed to having to ask folks every time.

>
> 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.
>
> Thanks,
> --
> Emilien Macchi
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Juan Antonio Osorio R.
e-mail: jaosorior at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171201/f34d5a72/attachment.html>