Quoting Carlos Martín Sánchez (cmar...@opennebula.org): > Hi there, > > Maybe we could try to replicate the 'onehost disable' behaviour. > That is, a disabled system DS would be ignored by the scheduler, but you > can still deploy VMs manually there.
I think this would support Daniel's use case. But how do you deploy a VM manually? I.e how do you by-pass the scheduler (except by creating a "WILD" vm)? At the moment the multi DS support is configured at template level. From a "system" perspective it would be nice to be able to control which datastore gets used. For example filter on user, group, vm template attributes, etc. At least we have a use case for this (seperate "Qtree" per datastore for IO billing). It proably makes the scheduler's life more complicated :(. > What do you think? Should I open a ticket for this? Yes, it's definitely useful. Gr. Stefan -- | BIT BV http://www.bit.nl/ Kamer van Koophandel 09090351 | GPG: 0xD14839C6 +31 318 648 688 / i...@bit.nl _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
