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 <supad...@redhat.com> wrote: > > > On Fri, Dec 1, 2017 at 2:17 PM, Bogdan Dobrelya <bdobr...@redhat.com> wrote: >> >> On 11/30/17 8:11 PM, Emilien Macchi 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. >>> >>> 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, >>> >> >> 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 >> tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001-ovn/ceph/k8s/tempest >> whatever it is. >> > > How is this looking? > > tripleo-ci/os/centos/7/ovb/ha/nodes/3ctrlr_1comp.yaml > tripleo-ci/os/centos/7/ovb/ha/featureset/ovn_ceph_k8s_with-tempest.yaml > > I also think we should have clear demarcation of the oooq variables ie > machine specific goes to nodes/* and feature related goes to featureset/* > > regards > /sanjay > > >> >> -- >> Best regards, >> Bogdan Dobrelya, >> Irc #bogdando >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Emilien Macchi __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev