On Wed, Jun 18, 2014 at 4:32 PM, sebgoa <run...@gmail.com> wrote:
>
>
> there is on-going work about this:
> http://markmail.org/thread/sxezpziog2koewlt


Thanks for this Sebastien, re-reading them. I saw the emails but I could
not understand the email thread and had the Xen/XenServer/Xen Project
confusion at the time.

Regards.


>
>
>
>
> >
> >
> >>>
> >>> The Xen/XenProject/XenServer/XAPI/XCP is confusing [1]. From what I
> >>> understand, XCP was some sort of an opensource version of XenServer,
> but
> >>> since XenServer distribution (which consists of Xen, XenCenter, XAPI,
> >> Linux
> >>> etc.) is opensource, XCP has been discontinued since 1.6 release?
> >>>
> >>
> >> XCP was rolled into XenServer as of XenServer 6.2 which means 1.6 was
> the
> >> last version of XCP.  I tried to sum it up in this blog:
> >>
> >>
> http://open.citrix.com/blog/342-knowing-what-you-ve-got-avoiding-the-xen-vs-xenserver-confusion.html
> >
> >
> > Thanks, this helps to understand what went in this transition.
> >
> >>
> >>> Now, on many Linux distro XAPI is still available as 'xcp-xapi' such as
> >> in
> >>> Debian/Ubuntu, so what package(s) do you suggest one needs to install
> and
> >>> configure so I can get DevCloud [2] work again? DevCloud is a VM that
> >> runs
> >>> Xen (Xen Project) inside it and can be used as a virtual host to
> >>> test/develop ACS against it.
> >>>
> >>>
> >> I see no reason why any other XAPI implementation wouldn't work, but
> it's
> >> entirely possible the version of xcp-xapi you have has issues with
> >> XenProject 4.4 due to normal versioning type issues.  There also was a
> >> different "productization" attempt called xenserver-core, but that
> looks to
> >> have died on the vine.  That being said, I could easily have broken
> >> something.  If I've broken something, I probably won't be able to test
> >> until next week due to travels.  The question of xapi inclusion in
> distros
> >> is one I'd need to check on.
> >>
> >
> > Yes, that would be great. I'll attempt testing it again with fresh setup
> in
> > upcoming weekends.
> >
> > Regards.
> >
> >
> >>
> >>
> >>
> >>> [1] http://www.xenproject.org/developers/teams/xapi.html
> >>> [2] http://bhaisaab.org/logs/devcloud
> >>>
> >>> Regards.
> >>>
> >>>
> >>>
> >>>
> >>> On Tue, Jun 17, 2014 at 4:27 PM, Tim Mackey <tmac...@gmail.com> wrote:
> >>>
> >>>> Rohit,
> >>>>
> >>>> We've only supported xapi so far, so I'm curious if you had Xen
> Project
> >>> 4.4
> >>>> working before with xapi and if that is now broken. Nothing I did
> >> should
> >>>> have impacted that, but it wasn't in my test suite so anything is
> >>> possible
> >>>> On Jun 17, 2014 11:21 AM, "Rohit Yadav" <bhais...@apache.org> wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> Xen Project (previously xen.org xenserver) is widely accessible in
> >>>> several
> >>>>> Linux distributions such as Arch, Fedora etc. Therefore, people may
> >>> want
> >>>> to
> >>>>> use it instead of XenServer (6.2 or later). The ACS 4.5 design doc
> >> [1]
> >>>>> explains about XenServer and how it should be tested etc. but what
> >>> about
> >>>>> using Xen Project?
> >>>>>
> >>>>> Since the recent Xen plugin refactoring as xenserver plugin [1], I'm
> >>>> unable
> >>>>> to get ACS to work with Xen Project 4.4 (on a real host and on a new
> >>>> custom
> >>>>> DevCloud). Using the XenServer ACS plugin, it identifies a Xen
> >> Project
> >>>> host
> >>>>> as some version of Xen but then fails. Has anyone tried this with ACS
> >>>>> 4.4/master? Are we going to test/support Xen Project (4.x) soon? If
> >> so,
> >>>> can
> >>>>> people involved share their plan/vision/roadmap on it?
> >>>>>
> >>>>> Lastly, as the design doc [1] suggested XCP's development has
> >> stopped,
> >>>> are
> >>>>> we going to favour using XAPI [1] now or libVirt [2] or something
> >> else?
> >>>>>
> >>>>> [1]
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Convert+Xen+usage+to+XenServer
> >>>>>
> >>>>> [2] http://blog.xen.org/index.php/2014/03/10/xen-4-4-released
> >>>>>
> >>>>> Regards.
> >>>>>
> >>>>
> >>>
> >>
>
>

Reply via email to