cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastien Goasguen <>
Subject Re: [GSOC]CloudStack deployment questions
Date Thu, 20 Jun 2013 20:46:52 GMT

On Jun 20, 2013, at 10:50 AM, "Han,Meng" <> wrote:

> On Wed, 19 Jun 2013 22:16:40 +0530, Prasanna Santhanam wrote:
>> On Wed, Jun 19, 2013 at 10:53:37AM -0400, Han,Meng wrote:
>>> >
>>> >You can run all the management server code from your laptop as a
>>> >development environment and add an external hypervisor host (Either
>>> >Xen/KVM) to it. The guests, system VMs etc will then be deployed on
>>> >your host and not eat up any memory on your laptop. Management server
>>> >does require quite a bit of memory to run and having Hypervisor +
>>> >Management server + storage + kitchen sink will slow it down (unless
>>> >you just need devcloud).
>>> I will add another hypervisor host. Is there any network requirement
>>> for the management server and hypervisor host?
>>> May I know how does the management server know the hypervisor host
>>> and include it to its management?
>> That's what CloudStack is for. It 'discovers' the hypervisor through
>> its discoverers - XenDisoverer talks to XAPI to manage Xenservers, KVM
>> talks via SSH/libvirt and VmWare talks through the vmware SDK. It's
>> all abstracted so you don't have to understand the mechanics of what's
>> going on underneath.
>> Your hypervisor host needs to be prepared with the
>> OS+hypervisor-software of your choice. It will need to have one NIC
>> that the management server (your laptop) can reach. You will need some
>> storage (NFS) where you can pre-seed the systemVM template which is
>> used to launch service VMs that cloudstack uses for management
>> purposes.
> Thanks for the detailed explanation!
>> All this and more is in the installation guide - let us know if
>> there's anything missing and you haven't been able to figure out about
>> the installation.
>>> >>
>>> >>========> WARNING: Provided file does not exist:
>>> >>/home/meng/cloudstack/developer/../utils/conf/
>>> >>========> Initializing database=cloud with host=localhost port=3306
>>> >>username=cloud password=cloud
>>> >>============> Running query: drop database if exists `cloud`
>>> >>SQL exception in trying initDB: java.sql.SQLException: Access denied
>>> >>for user 'root'@'localhost' (using password: NO)
>>> >>
>>> >Does your mysql instance have a root password? If so you'll have to
>>> >put that into file under utils/conf.
>>> >
>>> >I see the wiki(s) are missing this info, so we'll need to edit that
>>> >with this step if it works for you.
>>> >
>>> I create a file named under utils/conf. Put
>>> my root password inside it and it works!
>> Cool! Do you mind updating the wiki @
> I updated the wiki :)
>>> The command "mvn -pl :cloud-client-ui jetty:run" gives me a
>>> error:[INFO] Couldn't find specified project dir:
>>> /home/meng/cloudstack/:cloud-client-ui
>>> I notice that there is no cloud-client-ui directory under
>>> cloudstack. So I switched to "mvn -pl client jetty:run", however it
>>> told me the maven-jetty-plugin does not exist.
>> Yes, client will work.
>>> [INFO] Searching repository for plugin with prefix: 'jetty'.
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does
>>> not exist or no valid version could be found
>>> Any light on this?
>> Odd, the jetty plugin should be downloaded automatically from
>> If your mvn clean install step worked I'm guessing
>> you're not behind any sort of http_proxy?
> The problem turns out to be that I am using maven2 to build the project. After I switch
to maven3 the problem is gone.
> The management server runs at local port 8080 which is also the default port for tomcat.
As the deployment environment requires installing tomcat. Users follow this devcloud wiki
usually have tomcat service running before they start the management server. In order to run
the management server users can either shut down tomcat service or switch to another port.
> I added this to the wiki also

Meng, thanks for emailing the list, that's the way to go.

In your case, the actual storage does not really matter, it's more of a setup/functionality
issue. I would recommend that you indeed get two machines, one for mgt server and one as hypervisor.

For the networking requirements you need to read the documentation, and start with a basic
zone. The guide you mentioned is only for the 4.0 version. Try to use the 4.1 version. Maybe
you can patch the quick install guide so that it works for 4.1, that would be very much appreciated.

Check some of the screencasts I did, this might help:

Also, at:

I created some initial whirr documentation.


> .

View raw message