Re: [openstack-dev] [tripleo] rename ovb jobs?

On Fri, Dec 1, 2017 at 7:54 AM, Emilien Macchi wrote: > 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? > No i don't think so. I think -- is ideal for communicating at least the basics. If we

Re: [openstack-dev] [tripleo] rename ovb jobs?

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 wrote: > > > On Fri, Dec 1, 2017 at 2:17 PM, Bogdan Dobrelya wrote: >> >>

Re: [openstack-dev] [tripleo] rename ovb jobs?

On Fri, Dec 1, 2017 at 2:17 PM, Bogdan Dobrelya 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

Re: [openstack-dev] [tripleo] rename ovb jobs?

On 11/30/2017 08: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,

Re: [openstack-dev] [tripleo] rename ovb jobs?

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

Re: [openstack-dev] [tripleo] rename ovb jobs?

On Thu, Nov 30, 2017 at 9: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