[Openstack-operators] [Tags] Tags Team Repo & our first tags!

Tim Bell Tim.Bell at cern.ch
Sat Jun 6 08:41:48 UTC 2015

> -----Original Message-----
> From: Clint Byrum [mailto:clint at fewbar.com]
> Sent: 05 June 2015 21:06
> To: openstack-operators
> Subject: Re: [Openstack-operators] [Tags] Tags Team Repo & our first tags!
> Excerpts from Tim Bell's message of 2015-06-05 11:34:02 -0700:
> >
> > But if there is one package out of all of the OS options, does that make true or
> false ? Or do we have a rule that says a 1 means that at least CentOS and Ubuntu
> are packaged ?
> >
> > I remain to be convinced that a 0 or 1 can be achieved within the constraints
> that we need something which is useful for the operators rather than
> mathematically correct.
> >
> > Let’s not forget the target audience for the Ops tags.
> >
> Wouldn't it make sense that having coarse grained tags would help the rather
> busy operator more than a pile of information that has to be processed and
> inserted into an already very complex model? Nobody is saying tags can't find a
> position on a sliding scale, like 'packaged-in-ubuntu' or 'tested-on-rhel' seems
> like two tags that would be relevant to ubuntu or rhel users, and are entirely
> binary.
> Data from a real analysis is interesting, but what I really want when evaluating
> options to spend my time on is "Is the community with me?"
> If I can't find any tags that define what I'm trying to do, then the answer is
> "probably not". If I grab the ubuntu packages of project X and they aren't very
> high quality, I think the tag helps me to know that it's worth it to report bugs and
> plow through the problems, because the community is expressing very clearly
> "We want this to be packaged in Ubuntu."
> Meanwhie saying something is a 74 on the packaged scale in Ubuntu is a)
> inaccurate the moment something changes, and b) very confusing to anybody
> who doesn't know what that scale actually means.

I worry about a large number of binary tags without a higher level structure


Thus, some higher level grouping which gives a structure to it. The question would then be how the UI should show the level of packaging at the level one higher up in summary.

For the packaging tag, I'm looking for several things

- Is it packaged on my current deployment (i.e. can I deploy it) ?
- Is it packaged by other distros (i.e. does it have widespread support) ?

> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

More information about the OpenStack-operators mailing list