----- Original Message -----
From: "Sven Kieske" <S.Kieske@mittwald.de> To: devel@ovirt.org Sent: Tuesday, May 27, 2014 3:11:18 PM Subject: Re: [ovirt-devel] Entity names in DB scripts
further more, given the terminology of today it's not sure if "cluster" means gluster cluster or migration domain.
also look at my example for "host" a "host" can be everything: a) the machine engine runs on b) a machine in a "cluster", running vms c) a machine in a "cluster", as storage backend d) some network equipment (may be virtualized)
in short: don't use any term which has to broad usage (like "host" or "cluster"):
use: "compute node" for machines running vms
I think Host (=server) is the right term. compute node can be a rack as well, it's all a matter of POV :-)
use: "migration domain" (or similar narrowed down specifc term) for a bunch of hosts between which a vm can be migrated.
Just my opinion of course.
PS: It's no argument at all to say: "but we did this always this way, we can't change it"
I know this can introduce a lot of work, but nameing schemes can be converted over time or via scripts/automatism.
Am 27.05.2014 13:15, schrieb Gilad Chaplik:
Think of the time spent on that, let's take a conversation as an example:
oVirt guy: 'create a cluster' oVirt newcomer: 'what is a cluster?' oVirt guy: 'cluster is a migration domain'
Takes 5 seconds right? Now multiply that by every guy that had ever used/worked/heard/already forgot/ (newcomer) about oVirt.
let the scoring begin: I'm -1 on Cluster.
-- Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel