Evolution #75
storage visibility from another vsite
| Status: | Comment | Start: | 08/18/2010 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | Spent time: | - | |
| Target version: | - | |||
Description
Hi,
We will use Zinn as an expandable system for our customers, mainly e-commerce shops, so they can get some extra CPU / BW for punctual marketing operations. The system will heavily use your the 'cloning' facility, there will be a simple template storage cloned and autoconfigured from our side.
We initially planned to use a vsite by customer, but i realized there's no way i can clone a storage from a vsite to another, so we're pretty much forced to use a single vsite for all of our customers. Would it be thinkable to add the ability to clone a storage from one vsite to another ?
On the same idea, we'd really like to be able to copy / move a storage from a vsite to another.
Thanks !
History
Updated by pnl 528 days ago
- Status changed from New to Comment
Interesting feature. vsite is currently an isolated container which various daemons try to keep in a consistent state, whatever happens.
However this seems feasable to move services (machines, storages, etc) from a vsite to another. Limitations would be:
- Source and destination
vsitemust belong to the sameclient - Source and destination
vsitemust belong to the samesite_group - User requesting the operation must have privileges to remove services of said family from the source
vsite - User requesting the operation must have privileges to create services of said family in the destination
vsite
Thoughts welcome.