On 06/01/15 16:29, Xiao Peng Wang wrote:

> 1. Dockerize xCAT
[...]
>     Comments from xCAT team that this might NOT be a valid requirement:
>         1. Customer might want to have a physical and individual server
>     for xCAT MN;
>         2. Use Yum or Zypper to install xCAT is not hard.
>         3. Even with xCAT docker, customer still needs to run a lot
>     configuration to enable a xCAT MN.

I would concur with all 3 of those points - we want xCAT on the
management node itself, installing it is trivial and it's the
configuration that takes 99% of the time.

O the other hand it's just struck me that docker on the management node
might be a reasonable way to build stateless/statelite images for other
distros - for instance building Debian images on a RHEL box, or vice-versa..

> 2. Deploy docker host
[...]
>     After this step, the dock host is ready to initiate container.

That all sounds good.

I think (for me at least) that's where my interest would end, I think I
would prefer to use the batch system (Slurm in our case) to deploy the
docker instances in response to the job request.  Of course for this to
work Slurm would have to have to grow docker support.. ;-)

All the best,
Chris
-- 
 Christopher Samuel        Senior Systems Administrator
 VLSCI - Victorian Life Sciences Computation Initiative
 Email: [email protected] Phone: +61 (0)3 903 55545
 http://www.vlsci.org.au/      http://twitter.com/vlsci


------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to