Re: [Engine-devel] restapi: 'gluster' prefix
----- Original Message -----
i can't see any justification for the 'gluster' prefix,
as this is only additional /service/ provided by the project,
and Gluster now is a part of the RHT.
I believe there needs to be an indication which service this is about.
If we will support provisioning other storage types which also have volumes then we'd
want a way to differentiate.
However, isn't there a way to simply add gluster as the name space?
i.e. somthing like: /api/gluster/.../volumes ? (instead of 'cluster' as it is
redundant imho)
On 05/06/2012 09:56 AM, Ori Liel wrote:
> We are introducing Gluster functionality into ovirt-engine
> REST-API.
>
> Gluster entities are 'Volumes' and 'Bricks'. The question is:
> should
> they be called: 'volume'/'brick' or
'gluster_volume/gluster_brick'?
> (with or without the 'gluster' prefix)?
>
> There was a short conversation about this in a patch in Gerrit:
> http://gerrit.ovirt.org/#change,3918
>
> Since there are conflicting opinions, I'm bringing it here for a
> resolution.
>
> Thanks,
>
> Ori.
>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
--
Michael Pasternak
RedHat, ENG-Virtualization R&D
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel