You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Ian Duffy (JIRA)" <ji...@apache.org> on 2014/03/13 05:33:42 UTC

[jira] [Commented] (CLOUDSTACK-6114) Create config management recipes to install CloudStack

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

Ian Duffy commented on CLOUDSTACK-6114:
---------------------------------------

I'm interested in looking into this.

There are scripts already available in the source within /tools/devcloud/src.

I have no idea what their current state is. From what I can tell they are outdated. They also required a modified version of vagrant to allow files to be transferred over SCP. This is not required, since vagrant 1.5 they have introduced rsync for exposing files to guest VMs.

Preferred configuration management tool would be puppet.
Preferred box building tool would be packer.

Myself and Chris Snow made some progress on creating a 4.3 devcloud: https://github.com/imduffy15/devcloud

At the moment it works, I have 50gb storage on root for base OS + secondary storage. I use SR type EXT for primary/localstorage on a separate partition. 
I modified the devcloud.cfg to use 192.168.56.10(the hypervisor) as the gateway for the guest VMs, this enables them to have internet access.

Cloning the codebase and executing vagrant up will give you xcp-xapi 6.2 on debian. It is ready to be added as a host on 4.3.

I haven't ran the management server on dom0, I didn't think it was realistic due to the RAM requirements required(2-4gb for xen, reserve 2gb on dom0 for management server). Chris has been running it fine with a few modifications.

Suggested systems would be as follows:

Simulator - All in one solution based of simstack using puppet. Most likely created for CentOS.

Devcloud1: 1 VM running debian + xcp-xapi as done in my above github link with the host machine acting as the management server.

Devcloud2:
  - VM1 debian + xcp-xapi (local storage enabled)
  - VM2 management server + mysql + secondary storage

Devcloud3: All in one solution, xcp-xapi and management on one box.

Testing with vagrant-fusion would be interesting to allow for vt-x to be used to expose HVM capabilities on devcloud, however this needs a license.

> Create config management recipes to install CloudStack
> ------------------------------------------------------
>
>                 Key: CLOUDSTACK-6114
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6114
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: sebastien goasguen
>              Labels: gsoc2014
>
> To ease deployment of CloudStack we need to develop a set of recipes for all the configuration management systems. A few already exists using Chef, Puppet and Ansible.
> This project will do an inventory of existing recipes available on-line, coalesce them into a coherent set and write missing recipes.
> The student will need to learn configuration management with at least one tool (chef, puppet, ansible, salt..etc) and will develop recipes using Vagrant.
> The outcome will be a fully functional devcloud (cloudstack sandbox) with mutiple recipes. CloudStack will be deployable in a sanbox or in a multi-machine environment.



--
This message was sent by Atlassian JIRA
(v6.2#6252)