[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] How to built XCP from source-1.iso ?



Last time i've dig in it, there was some set of minor files (like anaconda replacement to rhel4 installer in eliloader), which was lacking of source code too.

The main problems with openness now (except open government we do not discuss right now):

* Lack of 'rebuild-world' instructions or script
* No any information on internals:
  ** Expectations of components (who must provide what?)
** No any information about xapi database modification, scheme bumping and so on. ** No clearly visible roadmap (not customer features, but internals, like 'splitting xapi to xapi and networkd') to understand what can be messed with and what not. * Very picky upgrade - XCP is 'platform', not solution and modification to internals is obvious for real product environment, installer expect it to be completely untouched.

Second level problem:
* dom0fs.tar.bz2 instead of set of packages. I still sometime wonder 'can I replace package X to Y?' - and I simply can't get right answer because of 'blob installation'.


On 21.10.2012 17:50, Pasi KÃrkkÃinen wrote:
On Sun, Oct 21, 2012 at 01:29:29AM +0400, George Shuklin wrote:
Hi.

Repack is not the 'rebuild'. Repack is simple unpack and pack back,
may be with changes. We do this too (and we actually replace
installer with our own to reduce amount input questions).

"Dark magic" I'm talking about is how to get dom0fs.tar.bz2 from
clear CentOS installation and bunch of source files.

Some of files (afaik) even had no source code. F.e. you can not get
xs-tools.iso (shipped inside XCP to plug to guest domains) from
source code, because windows part (paravirtualized drivers) are
closed source.

Citrix Windows PV drivers are afaik the only closedsource component in XCP ISO.

I think it's very important to be able to rebuild the XCP ISO from 
sources/scratch.
We need to get this documented in the wiki!

I'm sure there are many people in the community who could help with this effort,
trying out things to figure it out the correct process, and document the 
process.

-- Pasi


xcp-xapi on ubuntu/debian is much more opensource, you can rebuild
them completely from scratches, but they are not very stable (xapi
part is fine, but all interaction between xapi and other services is
'done somehow' and under some condition breaks).


On 21.10.2012 00:12, Outback Dingo wrote:
On Sat, Oct 20, 2012 at 12:02 PM, George Shuklin
<george.shuklin@xxxxxxxxx>   wrote:
AFAIK there is no such procedure in public. If you want to change some stuff
in components you can rebuild and reinstall *.rpm, but 'dom0fs.tar.gz' from
installer is some dark xensource magic.

There is now .......

http://wiki.xen.org/wiki/Repacking_the_XCP_ISO

We using custom XCP iso (with software raid on two disks, specific changes
to partition layout (~60Gb for /var/log) and so on) - it done by manual
installation hacking. (Kinda worry about future upgrades...)


On 20.10.2012 13:02, Cody Chan wrote:
Hello all,

I have to modify some source code of XCP, of course source-1.iso, but
after that how can I rebuilt XCP installation iso from modified source-1.iso
? Is there how-to document?

Thx
Cody Chan


_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.