Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of runseb@gmail.com designates
 74.125.83.52 as permitted sender)
From: Sebastien Goasguen <runseb@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: [ACS4.5] move from xen 2 xenserver
Message-Id: <C74B4351-9AE3-43DA-8FFF-9C4816FDE383@gmail.com>
Date: Tue, 15 Apr 2014 03:35:45 -0400
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))

Folks,

I just applied a patch from Tim Mackey:

=
https://git-wip-us.apache.org/repos/asf?p=3Dcloudstack.git;a=3Dcommit;h=3D=
748b575af8a66c58b0d52e7457e4d4e1e875231f

commit: 748b575af8a66c58b0d52e7457e4d4e1e875231f=20

This followed a [PROPOSAL] thread [1]

This was pushed into a separate branch: xen2server

This is a significant change that we should get consensus on and merge =
to master relatively quickly to avoid any conflicts later on.

Basically, we have been treating xen and xenserver the same so far, =
since the integration with Xen (i.e Xen Project) was/is done via xapi.

There has been discussion to integrate with Xen using straight up =
libvirt, by creating a new Xen agent probably based on the KVM agent and =
there was some discussion to that effect in the Denver Hackathon.

Making a clear split between Xen and Xenserver type of hypervisors will =
help support different integration methods.

I have asked Tim (in the review message) to create a wiki page, =
discussing all of this, but I wanted to give a heads up that this just =
hit the repo and that we should see a [MERGE] thread quickly.

thoughts, flames ?


[1] http://markmail.org/thread/yrl3ii7gqlaaexij

-Sebastien