[jira] [Commented] (CLOUDSTACK-8249) Dockerize CloudStack deployment

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14650302#comment-14650302 ] 

ASF subversion and git services commented on CLOUDSTACK-8249:
-------------------------------------------------------------

Commit 3381154fafb7fa4f0a61d538f7c2550e48247787 in cloudstack's branch refs/heads/master from [~pdion]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3381154 ]

initial dockerization commit. 1. update injectkeys.sh to work into restricted container 2. move previous dockerfiles into tools/docker 3. dockerfiles for management-server on centos and marvin

CLOUDSTACK-8249

Signed-off-by: Pierre-Luc Dion <pd...@apache.org>


> Dockerize CloudStack deployment
> -------------------------------
>
>                 Key: CLOUDSTACK-8249
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8249
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>         Environment: linux, python, docker, sys admin knowledge
>            Reporter: sebastien goasguen
>              Labels: gsoc2015
>
> CloudStack like any IaaS can be daunting to install.
> I propose to Dockerize the entire deployment process. There is already a few docker images for the simulator. The project will consist of two steps:
> 1-Dockerize the mgt server, including separate container for the MySQl DB and the usage server.
> 2-Dockerize the agent (assuming KVM ). Potentially even run KVM with Docker to contain everything.
> 3-Setup a self discovery mechanism with tools like register, confd, or etcd.
> 4-Automatically configure CloudStack based on self-registered services.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)