Attendees:
- John Garbutt (rackspace)
- olivier lambert (Vates)
-julien fontanet (Vates)
- Jon Ludlam (Citrix)
- Anil Madhavapeddy (Cambridge University)
- Nik Sultana (Cambridge University)
JonL: time for a release! All: yay! So what is it?
Goals of xapi 2 are: avoid source level patches to work on multiple distros. the version in debian was a big fork, and this was hard to maintain. its been pulled out of debian. Should have all the regular functionality. Will work with libxl and has storage backends. FFS storage backend is simple and works out of the box.
Networking - xcp-networkd takes over the system's networking. If its read only then leave network setup to distros. Delegation ability for guest vifs useful to rackspace (JohnG).
Xen orchestra -- uses npm so can hook straight into whatever distro support runs.
Opam support for xapi? all libraries have opam support, but daemons dont. Opam installs all the dependencies of xapi and then it builds. This includes things like xcp-idl which includes the interfaces between the daemons. Relocatable binary packages is up for question.
Manually written spec files, and upstreaming. Ubuntu trusty is the target on arm, and needs ocaml 4.01 (much improved arm support from 3.12.1!). Rackspace (JohnG) offers VM resources to do xapi build automation using Citrix's in house environment.
Post xapi2 drops? Will support ubuntu trusty (Xen 4.4). In xen4centos, jessie (4.3) as gated features. Wheezy (xen 4.1) is unlikely. Focus on two good working releases first (ubuntu, centos are likely). Need better web/PR presence for the release to encourage user adoption.
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
- John Garbutt (rackspace)
- olivier lambert (Vates)
-julien fontanet (Vates)
- Jon Ludlam (Citrix)
- Anil Madhavapeddy (Cambridge University)
- Nik Sultana (Cambridge University)
JonL: time for a release! All: yay! So what is it?
Goals of xapi 2 are: avoid source level patches to work on multiple distros. the version in debian was a big fork, and this was hard to maintain. its been pulled out of debian. Should have all the regular functionality. Will work with libxl and has storage backends. FFS storage backend is simple and works out of the box.
Networking - xcp-networkd takes over the system's networking. If its read only then leave network setup to distros. Delegation ability for guest vifs useful to rackspace (JohnG).
Xen orchestra -- uses npm so can hook straight into whatever distro support runs.
Opam support for xapi? all libraries have opam support, but daemons dont. Opam installs all the dependencies of xapi and then it builds. This includes things like xcp-idl which includes the interfaces between the daemons. Relocatable binary packages is up for question.
Manually written spec files, and upstreaming. Ubuntu trusty is the target on arm, and needs ocaml 4.01 (much improved arm support from 3.12.1!). Rackspace (JohnG) offers VM resources to do xapi build automation using Citrix's in house environment.
Post xapi2 drops? Will support ubuntu trusty (Xen 4.4). In xen4centos, jessie (4.3) as gated features. Wheezy (xen 4.1) is unlikely. Focus on two good working releases first (ubuntu, centos are likely). Need better web/PR presence for the release to encourage user adoption.
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api