Open modir opened 4 years ago
Hey @modir, you can just remove ACL which allows to use this datastore, they wil not even see it afterwards
Hi @kvaps , Sadly no. They use the oneadmin Account all the time so they see everything. (We are only a small team so no need for many different accounts in general.)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. The OpenNebula Dev Team
Please keep this issue open.
@modir
onedatastore disable wouldn't do the job?
disable
Disables the given Datastore. Only available for System Datastores
@rsmontero Will then the already existings VMs which have disks on this datastore still run? The way I expect "disable" to behave: no. Hence I need something for "still allow VMs to run from this datastore but do not allow to create something new".
It actually works as you describe. When a new VM has to be scheduled the scheduler filters out any DISABLED datastore. VMs running on the Datastore will not be affected.
This is spelled out in the documentation
OK. In this case the wording is from my point of view missleading.
Is it the same for image stores?
Not currently not implemented. We can reword this issue and use DISABLE in Image datastores to prevent the creation of new images, what do you think?
Yes, good idea. Will you do the rewording so it fits your needs? Or should I do it?
And what I always wanted to have is that the GUI has "help" icons which link to the relevant article the documentation. This would have helped me in this situation to look it up at the right place. But for this I can open up another issue.
I'll take thanks for the feedback!
Description It would be great if I could mark a image datastore as disable. This would then not allow anymore to create new Images on this datastore.
This compliment the disable of system datastores that prevent the allocation of new VMs to it.
Use case We have here one datastore which we want to fade out. I always tell my colleagues to not put any new VMs on this datastore. But some of them are either very lazy or stupid and they create new VMs on this datastore.
Interface Changes on.datastore.enable to work with Image datastores
Progress Status