Thanks for your reply.

So it sounds like I just need to do a standard XenServer install and not
have to configure anything specific for CS  - is that correct?

In your response to question 3 - "if your going with NFS this isnt
necessary, adding it via the GUI/API as a shared nfs storage should do the
trick." - by GUI do you mean the CS GUI and where do you add the storage?

In what situation would I need to set up a storage repository on the
Xenserver?

Clark


On 14 February 2013 19:30, Ahmad Emneina <aemne...@gmail.com> wrote:

> See inline:
>
>
> On Thu, Feb 14, 2013 at 11:24 AM, CK <cloudw...@gmail.com> wrote:
>
> > Hi all,
> >
> > I am new to CS and have been reading the documentation. I have have some
> > questions on the CS configuration/deployment.
> >
> > My setup is basic and as follows:
> > - 1x Centos Host running the CS management server, MySQL DB and NFS
> > providing primary/secondary storage
> > - 1x Xenserver Host to run the guest VMs
> >
> > Questions:
> > 1 - is the above sufficient for a basic env to test/play with CS?
> >
>
> Definitely.
>
>
> > 2 - I understand the guest VMs are created/stored on the primary storage,
> > but how (ie. directly from CS-Primary or CS->XenServer->Primary) and what
> > is the actual process how this done ?
> >
>
> cloudstack gets the xenserver to mount both secondary and primary.
> CS sends a command to XenServer to copy template from secondary to Primary
> CS clones the template and launches the vm.
>
>
>
>
> > 3 - When setting up the Xenserver host, do I need to configure a Storage
> > repository which happens to be the primary storage?
> >
>
> if your going with NFS this isnt necessary, adding it via the GUI/API as a
> shared nfs storage should do the trick.
>
>
> >
> > Is there a blog/wiki available that details how to setup the above?
> >
>
> There is a runbook/quick install being updated at the moment, in the mean
> time look at the install guide:
>
> https://incubator.apache.org/cloudstack/docs/en-US/index.html
>
>
>
> >
> > Thanks in advance.
> >
> > Clark
> >
>

Reply via email to