Open Stack

Todd,  Mike -

This looks great!  From the looks of things, the main difference seem to be
slight changes due to the fact that dom0 is ubuntu, rather than redhat.  Is
that accurate?  If so, it seems like it should be straightforward to
support both with roughly the same code, and just if-else the ubuntu/redhat
code.  In fact, we could probably even automatically check the os, and do
the right thing depending on the situation.

Since your branch was made, we've made some changes, primarily to
generalize the networking configuration, so you'll need to rebase.  Most
notably, we've separated the building of the .xva into its own script,
which should simplify things a bit for this; build_domU.sh (which could be
more aptly called install_domU.sh) is pretty brief right now.

I'd love to help debug and test this, so let me know what I can do to help.

A

On Mon, Feb 20, 2012 at 9:34 AM, Todd Deshane <todd.deshane at xen.org> wrote:

> On Mon, Feb 20, 2012 at 12:25 PM, Todd Deshane <todd.deshane at xen.org>
> wrote:
> > Hi Jesse and Anthony,
> >
> > Mike McClurg has a devstack branch that implements support for
> > devstack on Debian/Ubuntu + the XCP toolstack [1]. Bascially, you can
> > take a Debian/Ubuntu system with the xcp-xapi package installed and
> > configured [2] and then run the devstack xcp-toolstack branch
> > (specially the scripts in the xcp-toolstack directory of that branch)
> > to prepare the Debian/Ubuntu-based Dom0 and build the OpenStack VM on
> > top of that. We've been testing it and we also have some early
> > adopters that have also been testing it. We would like to open it up
> > to a wider audience.
> >
>
> Oops. I swapped the link references. corrected as:
> [1]
> https://github.com/mcclurmc/devstack/tree/xcp-toolstack/tools/xcp-toolstack
> [2] http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distribution
>
> >
> > First of all, our you guys interested in merging this type of suppport
> > into devstack?
> >
> > Second, we are wondering about the right implementation approach as
> > far as merging it with the existing Xen scripts. The are basically two
> > choices:
> >
> > 1) Pull in the xcp-toolstack branch as its own and have it just work,
> > but have the maintenance problem of duplication of code. (Less work
> > now, bigger maintenance cost)
> >
> > or
> >
> > 2) Refactor the xcp-toolstack and Xen versions so that the common code
> > is factored out nicely. (More work now, less maintenance cost)
> >
> > For your convenience, a diff is available here:
> > http://paste.openstack.org/show/4909/
> >
> > Thoughts?
> >
> > Thanks,
> > Todd
> >
> > --
> > Todd Deshane
> > http://www.linkedin.com/in/deshantm
> > http://blog.xen.org/
> > http://wiki.xen.org/
>
>
>
> --
> Todd Deshane
> http://www.linkedin.com/in/deshantm
> http://blog.xen.org/
> http://wiki.xen.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120221/29ce779b/attachment.html>