Re: [Opennode-users] Some questions about opennode

[Andres T. <an...@ac...>]

Hi Scott,

I'll try to answer your questions:

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? 

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. 

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. 

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


Greetings,

I just installed OpenNode b22 late Friday and I haven't had a chance to play with it much... so I'm going to ask some questions that I probably could have figured out if I had played with it more.

1) virt-manager appears to be installed but when I try to tunnel the X11 display of the app over ssh, it says that it can't open my display. I checked and X11 forwarding is turned on in /etc/ssh/sshd_config and it is enabled on my client side as well. Any idea why virt-manager doesn't work for me?

2) Until the release of the web-based admin app, what is the ferred way to create and manage KVM machines?

3) The install size seems a little bloated with 95 of the 535 packages that are installed (that take up about 1.3 GB of /) are i386 or i686 packages... that can almost surely be removed. Here is how I derived that info:

[total packages]
rpm -qa | wc -l

[32-bit packages]
rpm -qa --qf "%{n}.%{arch}\n" | grep -v x86_64 | grep -v noarch | grep -v none | wc -l

Do you know of any reason the 32-bit packages are needed? I know that glibc.i686 has to hang around but everything else can probably go and free up space... and .iso download.

I'm very excited about your product and hope to see it grow and develop quickly. I'll give back as much as I'm able.

TYL,
-- 
Scott Dowdle
704 Church Street
Belgrade, MT 59714
(406)388-0827 [home]
(406)994-3931 [work]