Re: [Xen-API] [Xen-users] New name for Kronos? [was XCP 1.5 availability]

[Mike McClurg <mike.mcclurg@xxxxxxxxxx>]

On 15/12/11 12:01, Pasi Kärkkäinen wrote:
> On Wed, Dec 14, 2011 at 06:01:17PM +0000, Mike McClurg wrote:
>> On 14/12/11 17:32, Alex Perez wrote:
>>> I would go a single step further, and suggest that you not use the term
>>> "XCP" at all in the context of Kronos. There's already pleeenty of
>>> confusion about exactly what is what. Right now, XCP means one thing, and
>>> I would implore you to keep it that way.
>>
>> One of the biggest effects of this confusion is that people are now
>> worried that XCP will become completely unstable, like Fedora versus
>> RHEL, and thus won't be suitable for serious enterprise deployments.
>>
>> Perhaps just calling it Kronos is a good idea. Though our packaging is
>> nearly complete, and they are all prefixed with 'xcp-'... I suppose we
>> can leave that as it is, since it is the XCP toolstack we're installing.
>> Does anyone else feel this strongly about calling it Kronos, and NOT
>> mentioning XCP?
>>
> 
> Imho, if possible, the debian/ubuntu package names should be changed,
> xcp- in the deb package names will cause a lot of confusion.
> 
> xapi- is better, or kronos-, for the deb packages.
> 
> I think 'xcp' should be used only for the .iso image appliance..
> 

So, I hate to use this as an excuse, but there are actually already a
few of our Kronos packages in Debian Sid right now with the name xcp-*.
I actually think this is a good thing, because those packages are
software that came from XCP, so to me it makes sense to call the
packages xcp-blah.

How about this compromise: We call "traditional" XCP, the thing that's
based on CentOS and is delivered as a standalone ISO, the "XCP
Distribution". We can then call the Kronos packages, the set of software
that is installable on Debian and Ubuntu (and hopefully other distros in
the future), the "XCP Toolstack".

I think that this solution will remove some of the confusion about which
thing is which. Will this be an acceptable compromise to everyone?

Mike

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api