Another thought would be utility to convert docker image to stateless image.  
They tend to be nicely paired down to the essentials (i.e. what genimage 
endeavors to do, but the images are frequently more thorough and someone else 
is doing the work) and are generally designed around the concept of a 
disposable image with specific mount points for non-disposable data, which maps 
quite well to the stateless design.

I will add to the list of concerns that if xCAT provides a docker image, it 
adds the responsibity of curating libraries the image includes.  E.g. when 
openssl needs an update today, operators today can update with no more a delay 
than the distribution inflicts in worst case.  In case of using a container a 
likely scenario would wind up being waiting for openssl to fix, then wait for 
RHEL to build the fix, then wait for CentOS to fix, and then we'd have to 
update the image, and then the 'proper' way of managing a docker container 
would be possible (and a bit more heavyweight than a normal update).

If a docker image is done, I would advocate it as a means of 
training/evaluating a simple setup (no service nodes, sqlite database) rather 
than a production setup.


Jarrod Johnson
Systems Management Architect
Lenovo




www.lenovo.com  <http://www.lenovo.com/>
Forums<http://forums.lenovo.com/> | Blogs<http://lenovoblogs.com/> | 
Twitter<http://twitter.com/lenovo> | Facebook<http://www.facebook.com/lenovo> | 
Flickr<http://www.flickr.com/photos/lenovophotolibrary>
Print only when necessary



From: Xiao Peng Wang [mailto:[email protected]]
Sent: Tuesday, January 06, 2015 12:29 AM
To: xCAT Users Mailing list
Subject: [xcat-user] Call for requirement for docker support in xCAT


The docker technology is very hot in 2014, xCAT is planning to support the 
docker too. Following are the proposals that how xCAT will support docker. Any 
comments are welcome. If you want any feature which has high priority or which 
one is not in the following list, please let us know.
1. Dockerize xCAT
    To include xCAT in docker image.
    1.1 Create a docker image to include 'xCAT' and xCAT dependency packages so 
that xCAT service can be easily enabled by pulling and running a docker image.
    1.2 Create a Dockerfile for xCAT so that customer can easily create a 
docker image for xCAT.

    Benefits:
        1. Customer can easily pull a xCAT docker image from public docker 
register and run it directly to get a xCAT environment.
        2. It will be easy to backup the whole xCAT management node.
        3. It will be easy to implement HA for xCAT management node.

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.

2. Deploy docker host
    Deploy and configure docker host.
    2.1 Prepare docker packages for docker host;
    2.2 Install docker packages on docker host during OS deployment or 
updatenode.
    2.3 Configure network bridges on the docker host. This step is used to 
enable the network connection for dockers cross host.

    After this step, the dock host is ready to initiate container.


3. Container Management
    Create, Remove, Start and Stop Containers on docker host. Also will support 
the status check and remote console for containers.

    Comments: We are arguing that using the 'mkvm, rmvm' which are used for 
virtual machine might NOT suitable for container management.

    3.1 Define a Container in xCAT
        Description: Make the definition of container. Add the necessary 
attributes for a container object.
        Definition Example:
            Object name: host1c1        #Container 1 on Host 1
              mac=xx:xx:xx:xx:xx:xx
              mgt=docker
              ip=xxx.xxx.xxx.xxx
              provmethod=<docker image name>
              vmhost=<docker host>
              vmcpu=xx
              vmmemory=xx
              ... # The docker parameters like 'port', 'volume' and 'link 
containers' are the considered ones.

    3.2 Create a Container
        Description: Create a container on target host. e.g. 'mkvm host1c1'. 
Create a container named c1 on host1 base on the attributes defined in host1c1 
object.
        xcat   CMD: mkvm
        docker CMD: docker run

    3.3 Remove a Container
        Description: Remove a container from target host. e.g. 'rmvm host1c1'. 
Remove the container named c1 from host1.
        xcat   CMD: rmvm
        docker CMD: docker rm

    3.4 Start a Container
        Description: Start a container from target host. e.g. 'rpower host1c1 
on'. Start the container named c1 on host1.
        xcat   CMD: rpower <container node> on
        docker CMD: docker start

    3.5 Stop a Container
        Description: Stop a container from target host. e.g. 'rpower host1c1 
off'. Stop the container named c1 from host1.
        xcat   CMD: rpower <container  node> off
        docker CMD: docker stop

    3.6 Check the Status for a Container
        Description: Display the status of a container. e.g. 'rpower host1c1 
state'. Check the status for the container named c1 from host1.
        xcat   CMD: rpower <container  node> state
        docker CMD: docker ps

    3.7 Start Remote Console for a Container
        Description: Remote connect to container from target host. e.g. 'rcons 
host1c1'. Remote connect to the console of the container named c1 on host1.
        xcat   CMD: rcons
        docker CMD: docker attach

        Comment: This might require the container to have a tty output so that 
rcons can display something.

4. Docker Image Management
    Maintain a local docker image Register in xCAT cluster.

    4.1 Maintain a local docker image register on xCAT management node. (xCAT 
will help to install and configure this local register)
    4.2 Trigger docker host to download docker image from local image register.
        Remotely run 'docker pull' on docker host.
    4.3 For a updated container, support the 'commit' and 'push' command to 
convert the changed container to an image and push the image to local register.

    Comment: In the phase one, it requires customer to create docker image 
manually by docker 'commit', 'pull', 'build', or 'import'. In the phase 2, xCAT 
might implement some commands to help customer to create image.

5. Network Setting Cross Docker Host
    5.1 Enable the cross hosts/cluster network communication for containers. 
(use the bridge mode)
        Assign predefined IP for each container.
        The container can ping each other in the whole cluster.

    5.2 Enable the docker container link between containers. (Need requirement 
scenarios)

6. Storage Management
    Enable volumes for containers. (Need requirement scenarios)



Thanks
Best Regards
----------------------------------------------------------------------
Wang Xiaopeng (王晓朋)
IBM China System Technology Laboratory
Tel: 86-10-82453455
Email: [email protected]<mailto:[email protected]>
Address: 28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian 
District Beijing P.R.China 100193
------------------------------------------------------------------------------
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