Stefan Kooman <ste...@bit.nl> writes:
[...] > You can, in your vm template you can put the following: > > SCHED_DS_REQUIREMENTS="NAME=NAMEOFYOURTESTDATASTORE". All other DS'es > will be filtered out. This will force a VM to use this one when it have this SCHED_DS_REQUIREMENTS, but what about all other VMs which do not have any requirements set? As far as I understand, they will use it too. [...] > Actually I was looking for this as well :). For example I would like to > be able to "link" certain datastores to "groups", i.e. use datastore A > for group A by default instead of having it defined in every single > template. If users of group A have the possibility to define their own > templates and they would forget the "SCHED_DS_REQUIREMENTS" to their > datastore it would end up somewhere else (if at least they have enough > rights on other (system) datastores). Basically it would be nice to have > even more filtering capabitilites to ensure correct > placement/deployment. If I remember correctly, I heard about some group and resource providers mechanisms for 4.6, it may address this. Regards. -- Daniel Dehennin Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF
signature.asc
Description: PGP signature
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
