|
| Re: OS template deployment [message #5453 is a reply to message #5437] |
Sat, 19 May 2007 01:57   |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
The ostemplates are downloaded only once. So if the total network overhead is exactly the same as if you want to manually deploy the ostemplates on each slave.
Thanks.
On Fri, May 18, 2007 at 08:29:32AM -0000, roger wrote:
>
>
> It would be nice to have an option to store/deploy OS templates from each node itself (maybe a manual sync feature if new OS templates are added), this way there is no data transfer from CP node to VPS nodes. The reason I bring this up is we have multiple networks and it unnecessarily spikes bandwidth if we deploy a VPS to a node on a network other then where the CP server is located,
>
> Thanks
|
|
|
| Re: OS template deployment [message #5454 is a reply to message #5453] |
Sat, 19 May 2007 02:03 |
 rviradia 
Messages: 95
Registered: February 2007 |
Valuable Member |
|
|
Cool, so the initial install of the template copies from CP to slave node, thereafter installs pull locally from /vz/template/cache/ in openvz,
Thanks
| Lxhelp wrote on Sat, 19 May 2007 01:57 |
The ostemplates are downloaded only once. So if the total network overhead is exactly the same as if you want to manually deploy the ostemplates on each slave.
Thanks.
On Fri, May 18, 2007 at 08:29:32AM -0000, roger wrote:
>
>
> It would be nice to have an option to store/deploy OS templates from each node itself (maybe a manual sync feature if new OS templates are added), this way there is no data transfer from CP node to VPS nodes. The reason I bring this up is we have multiple networks and it unnecessarily spikes bandwidth if we deploy a VPS to a node on a network other then where the CP server is located,
>
> Thanks
|
|
|
|
| Re: OS template deployment [message #65246 is a reply to message #5453] |
Tue, 19 May 2009 11:57 |
mitgib
Messages: 78
Registered: August 2007
Location: The Not So Deep South |
Valuable Member |
|
|
| Lxhelp wrote on Sat, 19 May 2007 01:57 | The ostemplates are downloaded only once. So if the total network overhead is exactly the same as if you want to manually deploy the ostemplates on each slave.
Thanks.
On Fri, May 18, 2007 at 08:29:32AM -0000, roger wrote:
>
>
> It would be nice to have an option to store/deploy OS templates from each node itself (maybe a manual sync feature if new OS templates are added), this way there is no data transfer from CP node to VPS nodes. The reason I bring this up is we have multiple networks and it unnecessarily spikes bandwidth if we deploy a VPS to a node on a network other then where the CP server is located,
>
> Thanks
|
I know this is a very old topic, but my idea is along these lines, just a little change. The ostemplate system is very intelligent as is, but I'd like to request a little more intelligence added to it.
My idea is to have a central template cache per data center. I've never seen a need for this until I grew a cluster in a remote data center when you have a good cache on the 1st node in the remote cluster, add a second node, and now the new node is pulling templates from the master which happens to be in another data center, when the templates are most likely already on another node in the same data center.
Then if the requested template does not exist on the remote cluster cache master, revert to the master which will always maintain a full cache, but copy it to the cluster cache master as well since it will be local lan traffic and no cost.
|
|
|
|
|
HyperVM & Kloxo Support
Members
Search
Help
Register
Login
Home
