Re: [OpenNode-users] [Opennode-users] Some questions about opennode

[<ope...@li...>]

-- 
----------------------------------------------
Andres Toomsalu, an...@ac...




On 02.03.2010, at 1:40, Scott Dowdle wrote:

> Andres,
> 
> Thanks for the reply.
> 
> ----- "Andres Toomsalu" <an...@ac...> wrote:
>> 1) Actually virt-manager is included probably by some package
>> dependency - so maybe not all needed stuff to run it is there. But in
>> theory if its installed it should run over ssh X tunneling - maybe you
>> just need correctly set DISPLAY env variable or something. But if it
>> runs it can help you to manage only KVM VM-s - no OpenVZ support
>> anyway. Could you try to connect with virt-manager installed on remote
>> machine and see if it works?
> 
> I can easily remove virt-manager and it doesn't take anything out with it, so it doesn't appear that it was dragged in by anything else.
> 
> I installed the xorg-x11-xinit (and the few packages it pulled in to satisfy deps) and I was able to run virt-manager so that seems to have been the missing package.

I'll test this also and maybe we should include xorg-x11-xinit in future releases then.

> 
>> 2) Until FuncMan release (the OpenNode web management console) KVM
>> management is currently possible by virsh shell (execute virsh on
>> console or run opennode cli and choose virsh there). After we get FUNC
>> modules ready then central CLI management through func follows. In
>> theory any libvirt compatible VM management tool/application should
>> work with KVM VM-s (as openvz libvirt support is not complete no apps
>> for that at the moment) - but we havent tested any yet.
> 
> For the moment I was just hoping to use virt-manager and virsh for KVM machine management and vzctl for OpenVZ container management.  I'm not that familiar with virsh but I do use it to start and list machines I've created with virt-manager... on my Fedora 12 x86_64 workstation. 

virsh is pretty handy for existing VM-s managing but for VM install we use virt-install helper script - I'll try to put up working cli management examples under website documentation section soon.

> 
>> 3) Yep - we removed a lot of packages but its still a bit bloated - so
>> we need to do some more work on that. Probably i386 and i686 packages
>> are coming from some package dependencys - need to further investigate
>> the issue. Any suggestions and observations are welcome.
> 
> In your build, when you specify the packages you want, make sure to tack on .x86_64 to the package name so it will only bring in the x86_64 stuff.  Without it, it'll bring in both .x86_64 and .i386 / .i686 stuff.  Getting rid of those packages doesn't save a lot of disk space but every little bit helps.
> 
> -- 
> Scott Dowdle
> 704 Church Street
> Belgrade, MT 59714
> (406)388-0827 [home]
> (406)994-3931 [work]
>