Hi Marcus, I have some questions regarding Kiwi internal working from a developer's point of view. I have gone through the Kiwi System image cookbook but that mainly targets end-users rather than the developers. 1. kiwi takes the initrd, kernel details and the user defined config.xml as input and creates the desired image. I would like to know the details as to how it does that. 2. As you have said-
In kiwi we have experimented with many union approaches using e.g clicfs, unionfs, deltafs, aufs but they are all running as fuse userspace processes which lead to other implementations like device-mapper-snapshot and btrfs+seed.
Why and where do you implement this in Kiwi 3. Now regarding the GSOC project. Kiwi supports Amazon Elastic Compute Cloud (Amazon EC2) which, AFAIK, is a web service that provides re-sizable compute capacity in the cloud. According to Kiwi Cloud Cookbook- For a Simple Storage Service backed Amazon Machine Image, a bundle with a manifest XML file is required and KIWI uses the Amazon tools to create this bundle for you. The steps involved are- 1. Register an Amazon EC2 account. 2. Modify the config.xml with the EC2 account information 3. kiwi --prepare 4. kiwi --create Now the image gets created. The generated image needs to be transfered over to Amazon which is done by the ec2-upload-bundle tool. Now my question is this, what does this GSOC project aim to change in these above steps. What would be the final deliverable of this project? Regards, Saket Sinha -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org