You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you have a high number of different pools, you might have one pool to generate all your custom templates and then replicate them to all your other pools.
Ideas
Right now, I've thought about 2 approaches:
Doing a "XO Hub" for custom templates, so templates can be consumed more easily everywhere.
Use VM copy feature in XO to achieve it (copy a template or multiple templates to multiple pools/SRs)
Alternatively, we could also go deeper with a real "sync" capability for templates (like with a rule on tags?) to get them automatically sync. But that's for later.
The first approach needs a lot more per-requisites. Option 2 is relatively simple and can be achieved with API/CLI pretty quickly.
Demand origin
It's been asked few times in the past, but it's becoming more & more requested now. See:
Context
When you have a high number of different pools, you might have one pool to generate all your custom templates and then replicate them to all your other pools.
Ideas
Right now, I've thought about 2 approaches:
Alternatively, we could also go deeper with a real "sync" capability for templates (like with a rule on tags?) to get them automatically sync. But that's for later.
The first approach needs a lot more per-requisites. Option 2 is relatively simple and can be achieved with API/CLI pretty quickly.
Demand origin
It's been asked few times in the past, but it's becoming more & more requested now. See:
The text was updated successfully, but these errors were encountered: