Hi Rudolf, * Rudolf Kutina (Rudolf.Kutina at Sun.COM) wrote: > >The VMC project will need to define a 'base' if you will in terms of > >installed packages for the virtual machine being created that can then > >be built upon. I expect it's going to be pretty minimal (no X or > >desktop for instance). I intend to look more into your JeOS work to get > >a starting point for that base. > Well. We define then JeOS is OS building block for creating of > Virtual Appliances and VM Templates. > Preview of OpenSolaris 200906 JeOS will be available soon. > > What about some non-formal presentation of what we done as part of > 200811/200906 JeOS creation process ?
Sure, that'd be great. > >>Reducing OpenSolaris (Part1: Approaches and Strategies) > >>http://blogs.sun.com/VirtualGuru/entry/reducing_opensolaris_part1_approaches_and > >> > >>AI Live-CD environment must be created to allow perform common user > >>tasks, so what will users do with VMC related Live-CD media when > >>when they will "Drop to Shell" ? > > > >I'm not sure I understand what you mean by when a user with VMC related > >Live-CD media 'drops to shell'. The AI image that the VMC project is > >going to use to create virtual machines is essentially going to be an > >implementation detail to the user (for the most part). In the basic use > >case, a user creating a virtual machine image will modify a DC manifest > >and specify what packages they want installed, some install related > >parameters and possibly a few virtual machine specific parameters (disk > >size, networking settings, stuff like that) and then start the build > >which will first generate an AI image and then create a VM and boot it > >using the AI image so it can be installed and then export the VM. The > >installation into VirtualBox will be an entirely hands off process > >requiring zero interaction from the user creating a virtual machine > >image (it has to be). So in the process of creating a virtual machine > >image, there won't be any 'dropping to a shell'. > VMC Live-CD media is where all "install and customization" are > performed, "Drop-to-Shell" on Live-CD can be simple just don't > reboot after "all is done". But more valuable concept can be if > "install" can work debug mode in similar way as today DC works. > All install and post configuration parts executed in context of > Live-CD can be represented as "steps", I can break in any of steps > by "pause-continue" or restart execution from some "step" same way > as we do now do it in NEW DC. This can very speed up creation of > final fully unattended (automated) procedures. Many users of new DC > see a concept of resumable "steps" most useful part of DC design. The approach we're taking for the VMC project is that the 'install' will be handled by the AI client code. The AI media will be enhanced such that it is bootable and start the AI client once booted automatically. The AI client will then perform the installation inside the virtual machine and once finished shutdown the VM. At which point the DC (which has been monitoring the installation) will export the VM and stop. So there won't be any 'drop to shell' or stepping. The entire process from start to finish *must* be 'hands off'. A user will modify a DC xml manifest describing what he wants to install in the VM (within the constraints of the AI engine, currently) and then run the DC using that manifest. Cheers, -- Glenn
