incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus Sorensen <shadow...@gmail.com>
Subject Re: DevCloud Question
Date Wed, 23 Jan 2013 03:47:37 GMT
You could always run them side by side as well, but at least with a
devcloud you'll have a working model to go off of if you run into issues in
building your own.

On Tue, Jan 22, 2013 at 8:34 PM, Mike Tutkowski <
mike.tutkowski@solidfire.com> wrote:

> OK, cool...I can start with DevCloud, but at some point I'd like to create
> my own from scratch just to understand the details better.  For the time
> being, though, I do want to get up and running, use SolidFire storage,
> etc., so using DevCloud is the way to go.
>
>
> On Tue, Jan 22, 2013 at 8:31 PM, Marcus Sorensen <shadowsor@gmail.com
> >wrote:
>
> > The only thing that works in virtualbox for running VMs is a Xen kernel.
> > You can roll your own distribution with a Xen kernel, sure, but devcloud
> is
> > preconfigured and is documented on how to set up.  That shouldn't stop
> you
> > from doing your own, though!
> >
> > On Tue, Jan 22, 2013 at 8:28 PM, Mike Tutkowski <
> > mike.tutkowski@solidfire.com> wrote:
> >
> > > No...it is network accessible...I was just thinking I would not use
> NFS.
> > >  If I use SolidFire's storage, run the management server on my host OS,
> > > then I guess all that leaves for DevCloud to do is provide a hypervisor
> > to
> > > run VMs...is that true?  If that's the case, I could just run my own
> > > hypervisor in a different VirtualBox VM.  That's all I was thinking.
>  Do
> > > you think that's not a good way to go?  Just curious.
> > >
> > >
> > > On Tue, Jan 22, 2013 at 8:14 PM, Marcus Sorensen <shadowsor@gmail.com
> > > >wrote:
> > >
> > > > Why not? Is solid fire storage not network accessible?
> > > > On Jan 22, 2013 8:11 PM, "Mike Tutkowski" <
> > mike.tutkowski@solidfire.com>
> > > > wrote:
> > > >
> > > > > OK, guys...thanks for the info!
> > > > >
> > > > > In my case, I will need to make use of SolidFire's storage, so
> using
> > > > > DevCloud for storage is probably not going to be applicable for me.
> > > > >
> > > > > I could use DevCloud to run VMs...I see now.  I also have another
> VM
> > > I've
> > > > > been using that has XenServer installed where I could run my VMs.
> >  This
> > > > is
> > > > > making more sense to me now.  I just wasn't really confident I
> > > understood
> > > > > what DevCloud provided.
> > > > >
> > > > > Thanks again
> > > > >
> > > > >
> > > > > On Tue, Jan 22, 2013 at 8:02 PM, Marcus Sorensen <
> > shadowsor@gmail.com
> > > > > >wrote:
> > > > >
> > > > > > Devcloud is where your VMS run. So in cloudstack when you add
> > hosts,
> > > it
> > > > > is
> > > > > > your host. In production you generally would have 3 or so
> > management
> > > > > > servers controlling tens or hundreds of hosts that run VMS.
So
> the
> > > mac
> > > > is
> > > > > > your management server and devcloud is what it controls.
> > > > > > On Jan 22, 2013 6:34 PM, "Mike Tutkowski" <
> > > > mike.tutkowski@solidfire.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Sorry about what might be silly questions :) but if I develop
> my
> > > code
> > > > > on
> > > > > > > Mac OS X, I'm not really sure what DevCloud would do for
me?
> > Could
> > > > you
> > > > > > > explain that part to me?
> > > > > > >
> > > > > > > Thanks!
> > > > > > >
> > > > > > >
> > > > > > > On Tue, Jan 22, 2013 at 6:22 PM, Mike Tutkowski <
> > > > > > > mike.tutkowski@solidfire.com> wrote:
> > > > > > >
> > > > > > > > Ah, didn't realize that DevCloud2 was Debian based.
> > > > > > > >
> > > > > > > > I'm developing on Max OS X.  So, it sounds like for
a
> developer
> > > in
> > > > > that
> > > > > > > > situation, it is best for me to download the source
code to
> my
> > > Mac,
> > > > > > code,
> > > > > > > > build, run, test, etc. on Mac OS X?
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tue, Jan 22, 2013 at 5:23 PM, Fang Wang <
> > fang.wang@citrix.com
> > > >
> > > > > > wrote:
> > > > > > > >
> > > > > > > >> IT depends on what OS X you have. IF you have
Ubuntu, then
> > > either
> > > > > > > >> DevCloud or your environment is the same.
> > > > > > > >> You may directly use your Ubuntu.
> > > > > > > >>
> > > > > > > >> But if OS X is windows, for some hypervisor, you
can't
> > directly
> > > > > deploy
> > > > > > > MS
> > > > > > > >> on Windows.
> > > > > > > >> Then DevCloud provides a way to bypass this Windows
> > limitation.
> > > > > > > >>
> > > > > > > >> -Fang
> > > > > > > >>
> > > > > > > >> -----Original Message-----
> > > > > > > >> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> > > > > > > >> Sent: Tuesday, January 22, 2013 3:43 PM
> > > > > > > >> To: cloudstack-dev@incubator.apache.org
> > > > > > > >> Subject: DevCloud Question
> > > > > > > >>
> > > > > > > >> Hi everyone,
> > > > > > > >>
> > > > > > > >> I'm curious to learn a bit about DevCloud.  I
don't
> currently
> > > > > > understand
> > > > > > > >> how it relates from a development-workflow perspective.
> > > > > > > >>
> > > > > > > >> My host OS is OS X.  I have VirtualBox, Eclipse,
Git, Maven,
> > > etc.
> > > > > > > >> installed in OS X.  I am running the DevCloud
appliance via
> > > > > > VirtualBox.
> > > > > > >  I
> > > > > > > >> can bring up the CloudStack GUI and log in this
way and
> that's
> > > > easy
> > > > > > and
> > > > > > > >> great to be able to do.  What I don't really understand
is
> how
> > > our
> > > > > > > >> development workflow should be using DevCloud.
> > > > > > > >>
> > > > > > > >> Do I develop code in Eclipse on OS X and port
the artifacts
> > over
> > > > to
> > > > > > > >> DevCloud to update it?  Am I supposed to develop
directly on
> > > > Ubuntu
> > > > > in
> > > > > > > >> DevCloud (and, as such, should not use Eclipse).
 Should I
> > just
> > > > > ignore
> > > > > > > >> DevCloud completely and develop everything on
OS X?
> > > > > > > >>
> > > > > > > >> I'm a little lost here.
> > > > > > > >>
> > > > > > > >> Thanks!!
> > > > > > > >>
> > > > > > > >> --
> > > > > > > >> *Mike Tutkowski*
> > > > > > > >> *Senior CloudStack Developer, SolidFire Inc.*
> > > > > > > >> e: mike.tutkowski@solidfire.com
> > > > > > > >> o: 303.746.7302
> > > > > > > >> Advancing the way the world uses the
> > > > > > > >> cloud<http://solidfire.com/solution/overview/?video=play>
> > > > > > > >> *(tm)*
> > > > > > > >>
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > *Mike Tutkowski*
> > > > > > > > *Senior CloudStack Developer, SolidFire Inc.*
> > > > > > > > e: mike.tutkowski@solidfire.com
> > > > > > > > o: 303.746.7302
> > > > > > > > Advancing the way the world uses the cloud<
> > > > > > > http://solidfire.com/solution/overview/?video=play>
> > > > > > > > *™*
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > *Mike Tutkowski*
> > > > > > > *Senior CloudStack Developer, SolidFire Inc.*
> > > > > > > e: mike.tutkowski@solidfire.com
> > > > > > > o: 303.746.7302
> > > > > > > Advancing the way the world uses the
> > > > > > > cloud<http://solidfire.com/solution/overview/?video=play>
> > > > > > > *™*
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > *Mike Tutkowski*
> > > > > *Senior CloudStack Developer, SolidFire Inc.*
> > > > > e: mike.tutkowski@solidfire.com
> > > > > o: 303.746.7302
> > > > > Advancing the way the world uses the
> > > > > cloud<http://solidfire.com/solution/overview/?video=play>
> > > > > *™*
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkowski@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the
> > > cloud<http://solidfire.com/solution/overview/?video=play>
> > > *™*
> > >
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkowski@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud<http://solidfire.com/solution/overview/?video=play>
> *™*
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message