Menu
▾
▴
opennode-users — OpenNode users support mailing list
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
(40) |
Apr
|
May
(1) |
Jun
(8) |
Jul
(9) |
Aug
(2) |
Sep
(9) |
Oct
(8) |
Nov
(23) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
(3) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(4) |
Dec
(1) |
| 2012 |
Jan
(1) |
Feb
(23) |
Mar
(6) |
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(3) |
Oct
|
Nov
(1) |
Dec
(3) |
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(4) |
Oct
|
Nov
(11) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(3) |
|
From: <ope...@li...> - 2010-03-02 19:14:54
|
Greetings, I'm trying to use virt-manager to create and manage KVM VMs on OpenNode. virt-manager doesn't seem to be aware that bridged networking is setup and defaults to providing private DHCP addresses to the VMs one creates. It seems that virt-manager is expecting one bridge setup in order to do public/static IPs and OpenNode sets up the bridging different. Perhaps it is just a matter of using a particular bridge device name. On my OpenNode machine I have two bridge devices: vmbr0 - Has the public IP assigned by OpenNode virbr0 - Has the private IP (192.168.122.1) setup by virt-manager At least I think that is what is going on. I realize that the OpenNode developers are working on a web-based management system... and that there are alternative management tools other than virt-manager... but it is installed and it would be nice if it was pre-configured in a working fashion. I was able to create KVM VM just fine with virt-manager, it just has semi-functional networking because only private IPs and NATing works. I don't know enough about the underlying config of virt-manager to fix it... other than creating a bridge device named br0 and giving it the public IP of the machine... bypassing the bridge device that OpenNode has created/configured. I haven't done that yet but I assume it would work since that's what I do on other Red Hat-based distros with KVM/virt-manager (RHEL 5.4 and Fedora 9, 10, 11, and 12). I also created an OpenVZ container with my own OS Template (rather than using those provided by OpenNode) and it worked fine. I realize that if I try the fix mentioned in the previous paragraph I'd have to edit the /etc/sysconfig/network-scripts/ifcfg-venet0 file to tell it to use the br0 instead of venet0. Any suggestions? TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] |
|
From: <ope...@li...> - 2010-03-02 01:11:57
|
No rush, just curios to see what the plans for this distro are. Thanks for the prompt reply. I look forward to trying your software. _ /-\ ndrew On Mon, Mar 1, 2010 at 4:30 PM, Andres Toomsalu <an...@ac...> wrote: > Yes - it will be up on the web page next week probably. > For now all I can say that we are pretty busy on implementing func cli > management and func RPC for web management console communication. > Milestone1 is to get basic VM management operations implemented (both for > OpenVZ and KVM VM-s). > -- > ---------------------------------------------- > Andres Toomsalu, an...@ac... > > > > > > On 02.03.2010, at 0:15, Andrew Niemantsverdriet wrote: > > > Do you guys have a Roadmap or anything for this project? It looks like > this has some real potential. > > > > Thanks, > > > > -- > > _ > > /-\ ndrew Niemantsverdriet > > Academic Computing > > (406) 238-7360 > > Rocky Mountain College > > 1511 Poly Dr. > > Billings MT, 59102 > > > ------------------------------------------------------------------------------ > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > > http://p.sf.net/sfu/intel-sw-dev_______________________________________________ > > OpenNode-users mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > -- _ /-\ ndrew Niemantsverdriet Academic Computing (406) 238-7360 Rocky Mountain College 1511 Poly Dr. Billings MT, 59102 |
|
From: <ope...@li...> - 2010-03-02 00:56:35
|
-- ---------------------------------------------- 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] > |
|
From: <ope...@li...> - 2010-03-02 00:11:51
|
Please try now again - newer libvirt packages were missing from old repo (activesys) - as we moved OpenNode packages to new opennode repo. After yum upgrade the new repo should be in place and old repo will be removed. -- ---------------------------------------------- Andres Toomsalu, an...@ac... j On 02.03.2010, at 1:42, Scott Dowdle wrote: > Andres, > > ----- "Andres Toomsalu" <an...@ac...> wrote: >> Upgrading: >> >> For upgrading existing OpenNode installations simply execute (on >> OpenNode console): >> yum update > > I just did a yum clean all and then an yum update and I'm getting the following error: > > --> Finished Dependency Resolution > opennode-1.0-8.x86_64 from activesys has depsolving problems > --> Missing Dependency: libvirt >= 0.6.3-20.asys.1 is needed by package opennode-1.0-8.x86_64 (activesys) > Error: Missing Dependency: libvirt >= 0.6.3-20.asys.1 is needed by package opennode-1.0-8.x86_64 (activesys) > > Maybe your repo isn't done syncing or something. > > TYL, > -- > Scott Dowdle > 704 Church Street > Belgrade, MT 59714 > (406)388-0827 [home] > (406)994-3931 [work] > |
|
From: Andres T. <an...@ac...> - 2010-03-01 23:30:51
|
Yes - it will be up on the web page next week probably. For now all I can say that we are pretty busy on implementing func cli management and func RPC for web management console communication. Milestone1 is to get basic VM management operations implemented (both for OpenVZ and KVM VM-s). -- ---------------------------------------------- Andres Toomsalu, an...@ac... On 02.03.2010, at 0:15, Andrew Niemantsverdriet wrote: > Do you guys have a Roadmap or anything for this project? It looks like this has some real potential. > > Thanks, > > -- > _ > /-\ ndrew Niemantsverdriet > Academic Computing > (406) 238-7360 > Rocky Mountain College > 1511 Poly Dr. > Billings MT, 59102 > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev_______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users |
|
From: Andrew N. <an...@ro...> - 2010-03-01 23:12:47
|
Do you guys have a Roadmap or anything for this project? It looks like this has some real potential. Thanks, -- _ /-\ ndrew Niemantsverdriet Academic Computing (406) 238-7360 Rocky Mountain College 1511 Poly Dr. Billings MT, 59102 |
|
From: Andres T. <an...@ac...> - 2010-03-01 22:26:52
|
OpenNode 1.0 beta ISO installer image is available for download from OpenNode sourceforge project page and for existing installations upgrade is provided through yum update. Changelog: * Upgraded kernel to ovzkernel-2.6.18-164.11.1.el5.028stab068.3 * Updated KVM to 83-105.asys.22.4 * Relocated OpenNode specific packages to opennode yum repository * Changed OpenNode OpenVZ templates download URL * Made some changes to opennode rpm in order to provide yum upgrades for existing OpenNode installations Installation: For new installations please download OpenNode ISO installer image and burn it into cd. Boot server from OpenNode CD and follow on-screen instructions. Upgrading: For upgrading existing OpenNode installations simply execute (on OpenNode console): yum update -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
|
From: Andres T. <an...@ac...> - 2010-03-01 22:11:37
|
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]
|
|
From: Scott D. <do...@mo...> - 2010-03-01 18:10:04
|
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 preferred 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]
|
2 messages has been excluded from this view by a project administrator.
