[one-users] one-context package in debian is not working
Hi, I installed one-context in debian 6.0 VM to create master image. But really if I install it in debian-installer (in autoseed configuration file), then symlink is created in /, because runlevel is not defined. If I try to use correct symlink (ln -sf ../init.d/vmcontext /etc/rc2.d/S99vmcontext) it is not executed, because Debian usually use dependency based init. The correct way to install startup scripts is to put correct information in LSB part of vmcontext and use update-rc.d. Default-Stop should have no values, because vmcontext doesn't handle stop requests. Default-Start should have 2 3 4 5 (or even S 2 3 4 5). In postinstall script there should be update-rc.d vmcontext start 99 2 3 4 5 . 99 - is not used, because the order depends on other LSB parameters in vmcontext. Regards, Rolandas Naujikas P.S. Additionally I found that if I put empty line into /etc/udev/rules.d/75-persistent-net-generator.rules and /etc/udev/rules.d/75-cd-aliases-generator.rules there will not be warning/error message in startup about can no read ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] one-context package in debian is not working
try using /sbin/insserv -d vmcontext Am 22.01.2013 09:26, schrieb Rolandas Naujikas: Hi, I installed one-context in debian 6.0 VM to create master image. But really if I install it in debian-installer (in autoseed configuration file), then symlink is created in /, because runlevel is not defined. If I try to use correct symlink (ln -sf ../init.d/vmcontext /etc/rc2.d/S99vmcontext) it is not executed, because Debian usually use dependency based init. The correct way to install startup scripts is to put correct information in LSB part of vmcontext and use update-rc.d. Default-Stop should have no values, because vmcontext doesn't handle stop requests. Default-Start should have 2 3 4 5 (or even S 2 3 4 5). In postinstall script there should be update-rc.d vmcontext start 99 2 3 4 5 . 99 - is not used, because the order depends on other LSB parameters in vmcontext. Regards, Rolandas Naujikas P.S. Additionally I found that if I put empty line into /etc/udev/rules.d/75-persistent-net-generator.rules and /etc/udev/rules.d/75-cd-aliases-generator.rules there will not be warning/error message in startup about can no read ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Monitoring vm OCCI
Hi to all, Is there a way to monitor the performance of vm? In sunstone exists, my request is if there is a method to retrieve this information by OCCI or through other methods. Thanks in advance Emanuel ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] one-context package in debian is not working
On 2013-01-22 10:53, Tobias Honacker wrote: try using /sbin/insserv -d vmcontext Debian packages use update-rc.d to create/remove startup symlinks in postinstall/postremove scripts. I'm not sure, but it is probably in Debian packages policy documents. Regards, Rolandas Naujikas Am 22.01.2013 09:26, schrieb Rolandas Naujikas: Hi, I installed one-context in debian 6.0 VM to create master image. But really if I install it in debian-installer (in autoseed configuration file), then symlink is created in /, because runlevel is not defined. If I try to use correct symlink (ln -sf ../init.d/vmcontext /etc/rc2.d/S99vmcontext) it is not executed, because Debian usually use dependency based init. The correct way to install startup scripts is to put correct information in LSB part of vmcontext and use update-rc.d. Default-Stop should have no values, because vmcontext doesn't handle stop requests. Default-Start should have 2 3 4 5 (or even S 2 3 4 5). In postinstall script there should be update-rc.d vmcontext start 99 2 3 4 5 . 99 - is not used, because the order depends on other LSB parameters in vmcontext. Regards, Rolandas Naujikas P.S. Additionally I found that if I put empty line into /etc/udev/rules.d/75-persistent-net-generator.rules and /etc/udev/rules.d/75-cd-aliases-generator.rules there will not be warning/error message in startup about can no read ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Monitoring vm by OCCI
Hi to all, Is there a way to monitor the performance of vm? In sunstone exists, my request is if there is a method to retrieve this information by OCCI or through other methods. Thanks in advance ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] one-context package in debian is not working
http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot maybe this will help you out. update-rc.d is outdated. Am 22.01.2013 10:05, schrieb Rolandas Naujikas: On 2013-01-22 10:53, Tobias Honacker wrote: try using /sbin/insserv -d vmcontext Debian packages use update-rc.d to create/remove startup symlinks in postinstall/postremove scripts. I'm not sure, but it is probably in Debian packages policy documents. Regards, Rolandas Naujikas Am 22.01.2013 09:26, schrieb Rolandas Naujikas: Hi, I installed one-context in debian 6.0 VM to create master image. But really if I install it in debian-installer (in autoseed configuration file), then symlink is created in /, because runlevel is not defined. If I try to use correct symlink (ln -sf ../init.d/vmcontext /etc/rc2.d/S99vmcontext) it is not executed, because Debian usually use dependency based init. The correct way to install startup scripts is to put correct information in LSB part of vmcontext and use update-rc.d. Default-Stop should have no values, because vmcontext doesn't handle stop requests. Default-Start should have 2 3 4 5 (or even S 2 3 4 5). In postinstall script there should be update-rc.d vmcontext start 99 2 3 4 5 . 99 - is not used, because the order depends on other LSB parameters in vmcontext. Regards, Rolandas Naujikas P.S. Additionally I found that if I put empty line into /etc/udev/rules.d/75-persistent-net-generator.rules and /etc/udev/rules.d/75-cd-aliases-generator.rules there will not be warning/error message in startup about can no read ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] one-context package in debian is not working
On 2013-01-22 11:09, Tobias Honacker wrote: http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot maybe this will help you out. update-rc.d is outdated. It is in contradiction with Debian 6.0 packages. Most of them (at least in base) are using update-rc.d and no of them insserv. Probably that will change in Debian 7.0. Regards, Rolandas Naujikas Am 22.01.2013 10:05, schrieb Rolandas Naujikas: On 2013-01-22 10:53, Tobias Honacker wrote: try using /sbin/insserv -d vmcontext Debian packages use update-rc.d to create/remove startup symlinks in postinstall/postremove scripts. I'm not sure, but it is probably in Debian packages policy documents. Regards, Rolandas Naujikas Am 22.01.2013 09:26, schrieb Rolandas Naujikas: Hi, I installed one-context in debian 6.0 VM to create master image. But really if I install it in debian-installer (in autoseed configuration file), then symlink is created in /, because runlevel is not defined. If I try to use correct symlink (ln -sf ../init.d/vmcontext /etc/rc2.d/S99vmcontext) it is not executed, because Debian usually use dependency based init. The correct way to install startup scripts is to put correct information in LSB part of vmcontext and use update-rc.d. Default-Stop should have no values, because vmcontext doesn't handle stop requests. Default-Start should have 2 3 4 5 (or even S 2 3 4 5). In postinstall script there should be update-rc.d vmcontext start 99 2 3 4 5 . 99 - is not used, because the order depends on other LSB parameters in vmcontext. Regards, Rolandas Naujikas P.S. Additionally I found that if I put empty line into /etc/udev/rules.d/75-persistent-net-generator.rules and /etc/udev/rules.d/75-cd-aliases-generator.rules there will not be warning/error message in startup about can no read ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] network problem opennebula 3.8
Hi all, I'm trying to launch virtual machine on my cloud with opennebula 3.8 and kvm hypervisor. When I create vm, I got a this error message Tue Jan 22 15:29:37 2013 [DiM][I]: New VM state is ACTIVE. Tue Jan 22 15:29:38 2013 [LCM][I]: New VM state is PROLOG. Tue Jan 22 15:29:38 2013 [VM][I]: Virtual Machine has no context Tue Jan 22 15:29:57 2013 [TM][I]: clone: Cloning gcloud-front.sdfarm.kr:/gcloud/one/var/datastores/101/ba084f2e80cf462c39f3d63e67c280f0 in /gcloud/one/var/datastores/0/113/disk.0 Tue Jan 22 15:29:57 2013 [TM][I]: ExitCode: 0 Tue Jan 22 15:30:00 2013 [TM][I]: mkimage: Making filesystem of 10240M and type ext3 at gcloud01:/gcloud/one/var//datastores/0/113/disk.1 Tue Jan 22 15:30:00 2013 [TM][I]: ExitCode: 0 Tue Jan 22 15:30:01 2013 [TM][I]: mkimage: Making filesystem of 1024M and type swap at gcloud01:/gcloud/one/var//datastores/0/113/disk.2 Tue Jan 22 15:30:01 2013 [TM][I]: ExitCode: 0 Tue Jan 22 15:30:01 2013 [LCM][I]: New VM state is BOOT Tue Jan 22 15:30:01 2013 [VMM][I]: Generating deployment file: /gcloud/one/var/vms/113/deployment.0 Tue Jan 22 15:30:01 2013 [VMM][I]: Remote worker node files not found Tue Jan 22 15:30:01 2013 [VMM][I]: Updating remotes Tue Jan 22 15:30:01 2013 [VMM][I]: ExitCode: 0 Tue Jan 22 15:30:01 2013 [VMM][I]: ExitCode: 0 Tue Jan 22 15:30:01 2013 [VMM][I]: Command execution fail: /var/tmp/one/vnm/tm_ssh/pre PFZNPjxJRD4xMTM8L0lEPjxVSUQ+MDwvVUlEPjxHSUQ+MDwvR0lEPjxVTkFNRT5vbmVhZG1pbjwvVU5BTUU+PEdOQU1FPm9uZWFkbWluPC9HTkFNRT48TkFNRT5zbF9saXZlPC9OQU1FPjxQRVJNSVNTSU9OUz48T1dORVJfVT4xPC9PV05FUl9VPjxPV05FUl9NPjE8L09XTkVSX00+PE9XTkVSX0E+MDwvT1dORVJfQT48R1JPVVBfVT4wPC9HUk9VUF9VPjxHUk9VUF9NPjA8L0dST1VQX00+PEdST1VQX0E+MDwvR1JPVVBfQT48T1RIRVJfVT4wPC9PVEhFUl9VPjxPVEhFUl9NPjA8L09USEVSX00+PE9USEVSX0E+MDwvT1RIRVJfQT48L1BFUk1JU1NJT05TPjxMQVNUX1BPTEw+MDwvTEFTVF9QT0xMPjxTVEFURT4zPC9TVEFURT48TENNX1NUQVRFPjI8L0xDTV9TVEFURT48UkVTQ0hFRD4wPC9SRVNDSEVEPjxTVElNRT4xMzU4ODM2MTUyPC9TVElNRT48RVRJTUU+MDwvRVRJTUU+PERFUExPWV9JRC8+PE1FTU9SWT4wPC9NRU1PUlk+PENQVT4wPC9DUFU+PE5FVF9UWD4wPC9ORVRfVFg+PE5FVF9SWD4wPC9ORVRfUlg+PFRFTVBMQVRFPjxDUFU+PCFbQ0RBVEFbMC41XV0+PC9DUFU+PERJU0s+PENMT05FPjwhW0NEQVRBW1lFU11dPjwvQ0xPTkU+PERBVEFTVE9SRT48IVtDREFUQVtTTDYuM19pbnN0YWxsX09TXV0+PC9EQVRBU1RPUkU+PERBVEFTVE9SRV9JRD48IVtDREFUQVsxMDFdXT48L0RBVEFTVE9SRV9JRD48REVWX1BSRUZJWD48IVtDREFUQVtoZF1dPjwvREVWX1BSRUZJWD48RElTS19JRD48IVtDREFUQVswXV0+PC9ESVNLX0lEPjxJTUFHRT48IVtDREFUQVtTTDYgbGl2ZSBjZF1dPjwvSU1BR0U+PElNQUdFX0lEPjwhW0NEQVRBWzExXV0+PC9JTUFHRV9JRD48UkVBRE9OTFk+PCFbQ0RBVEFbWUVTXV0+PC9SRUFET05MWT48U0FWRT48IVtDREFUQVtOT11dPjwvU0FWRT48U09VUkNFPjwhW0NEQVRBWy9nY2xvdWQvb25lL3Zhci9kYXRhc3RvcmVzLzEwMS9iYTA4NGYyZTgwY2Y0NjJjMzlmM2Q2M2U2N2MyODBmMF1dPjwvU09VUkNFPjxUQVJHRVQ+PCFbQ0RBVEFbaGRhXV0+PC9UQVJHRVQ+PFRNX01BRD48IVtDREFUQVtzc2hdXT48L1RNX01BRD48VFlQRT48IVtDREFUQVtDRFJPTV1dPjwvVFlQRT48L0RJU0s+PERJU0s+PEJVUz48IVtDREFUQVt2aXJ0aW9dXT48L0JVUz48REVWX1BSRUZJWD48IVtDREFUQVtoZF1dPjwvREVWX1BSRUZJWD48RElTS19JRD48IVtDREFUQVsxXV0+PC9ESVNLX0lEPjxGT1JNQVQ+PCFbQ0RBVEFbZXh0M11dPjwvRk9STUFUPjxTSVpFPjwhW0NEQVRBWzEwMjQwXV0+PC9TSVpFPjxUQVJHRVQ+PCFbQ0RBVEFbdmRhXV0+PC9UQVJHRVQ+PFRZUEU+PCFbQ0RBVEFbZnNdXT48L1RZUEU+PC9ESVNLPjxESVNLPjxCVVM+PCFbQ0RBVEFbdmlydGlvXV0+PC9CVVM+PERFVl9QUkVGSVg+PCFbQ0RBVEFbaGRdXT48L0RFVl9QUkVGSVg+PERJU0tfSUQ+PCFbQ0RBVEFbMl1dPjwvRElTS19JRD48UkVBRE9OTFk+PCFbQ0RBVEFbbm9dXT48L1JFQURPTkxZPjxTSVpFPjwhW0NEQVRBWzEwMjRdXT48L1NJWkU+PFRBUkdFVD48IVtDREFUQVt2ZGJdXT48L1RBUkdFVD48VFlQRT48IVtDREFUQVtzd2FwXV0+PC9UWVBFPjwvRElTSz48R1JBUEhJQ1M+PExJU1RFTj48IVtDREFUQVswLjAuMC4wXV0+PC9MSVNURU4+PFBPUlQ+PCFbQ0RBVEFbNjAxM11dPjwvUE9SVD48VFlQRT48IVtDREFUQVt2bmNdXT48L1RZUEU+PC9HUkFQSElDUz48TUVNT1JZPjwhW0NEQVRBWzUxMl1dPjwvTUVNT1JZPjxOQU1FPjwhW0NEQVRBW3NsX2xpdmVdXT48L05BTUU+PE5JQz48QlJJREdFPjwhW0NEQVRBW2V0aDFdXT48L0JSSURHRT48SVA+PCFbQ0RBVEFbMTkyLjE2OC41Ni40XV0+PC9JUD48TUFDPjwhW0NEQVRBWzAyOjAwOmMwOmE4OjM4OjA0XV0+PC9NQUM+PE5FVFdPUks+PCFbQ0RBVEFbUHJpdmF0ZSBMQU4gd2l0aCBldGgxXV0+PC9ORVRXT1JLPjxORVRXT1JLX0lEPjwhW0NEQVRBWzhdXT48L05FVFdPUktfSUQ+PFZMQU4+PCFbQ0RBVEFbTk9dXT48L1ZMQU4+PC9OSUM+PE9TPjxCT09UPjwhW0NEQVRBW2Nkcm9tXV0+PC9CT09UPjwvT1M+PFZNSUQ+PCFbQ0RBVEFbMTEzXV0+PC9WTUlEPjwvVEVNUExBVEU+PEhJU1RPUllfUkVDT1JEUz48SElTVE9SWT48T0lEPjExMzwvT0lEPjxTRVE+MDwvU0VRPjxIT1NUTkFNRT5nY2xvdWQwMTwvSE9TVE5BTUU+PEhJRD4xOTwvSElEPjxTVElNRT4xMzU4ODM2MTc3PC9TVElNRT48RVRJTUU+MDwvRVRJTUU+PFZNTU1BRD52bW1fa3ZtPC9WTU1NQUQ+PFZOTU1BRD50bV9zc2g8L1ZOTU1BRD48VE1NQUQ+c2hhcmVkPC9UTU1BRD48RFNfTE9DQVRJT04+L2djbG91ZC9vbmUvdmFyLy9kYXRhc3RvcmVzPC9EU19MT0NBVElPTj48RFNfSUQ+MDwvRFNfSUQ+PFBTVElNRT4xMzU4ODM2MTc3PC9QU1RJTUU+PFBFVElNRT4xMzU4ODM2MjAxPC9QRVRJTUU+PFJTVElNRT4xMzU4ODM2MjAxPC9SU1RJTUU+PFJFVElNRT4wPC9SRVRJTUU+PEVTVElNRT4wPC9FU1RJTUU+PEVFVElNRT4wPC9FRVRJTUU+PFJFQVNPTj4wPC9SRUFTT04+PC9ISVNUT1JZPjwvSElTVE9SWV9SRUNPUkRTPjwvVk0+ Tue Jan 22 15:30:01 2013 [VMM][I]: bash: line 2: /var/tmp/one/vnm/tm_ssh/pre: No such file or directory Tue Jan 22 15:30:01 2013 [VMM][I]: ExitCode: 127 Tue Jan 22 15:30:01 2013 [VMM][I]: Failed to execute network driver operation: pre. Tue Jan 22 15:30:01
Re: [one-users] problems with images in 3.8.3
On 2013-01-22 09:58, Rolandas Naujikas wrote: Hi, I see that bug http://dev.opennebula.org/issues/1087 reappeared in 3.8.3. The sequence to repeat is: 1) create an image as save from VM (as an user in oneadmin group); 2) change owner to oneadmin; 3) delete image; 4) repeat (1) and (2) will fail saying [ImageChown] USER [0] already owns IMAGE [N] with NAME XXX, where N - is id of already deleted image. Restart of one solves temporary problem. Also I saw several times that images were in use by nonexistent VM. onedb fsck will complain and correct that. At least I can confirm it with cancel action on VM. Regards, Rolandas Naujikas ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Monitoring vm by OCCI
On 01/22/2013 09:05 AM, Emanuel Marzini wrote: Hi to all, Is there a way to monitor the performance of vm? In sunstone exists, my request is if there is a method to retrieve this information by OCCI or through other methods. If you have a management network, you can get this via ganglia - its literally a case of yum installing starting it and needing no configs - KB ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Change one.db path [was ONE sunstone locking randomly]
Hello, Is there any way to place the one.db sqlite file in another directory? (so it is outside the NFS shared path) Thanks On 14/01/13 15:32, Andreas Calvo Gómez wrote: We will try it under our maintenance schedule. However, stopping and starting daemons shows the following warnings: [root@opennebula ~]# /etc/init.d/opennebula-occi stop /etc/init.d/opennebula-sunstone stop /etc/init.d/opennebula stop /etc/init.d/httpd stop Stopping OCCI Server daemon: occi-server stopped [ OK ] Stopping Sunstone Server daemon: sunstone-server stopped [ OK ] Stopping OpenNebula daemon: oned and scheduler stopped [ OK ] Stopping httpd:[ OK ] [root@opennebula ~]# service opennebula start service opennebula-sunstone start service opennebula-occi start service httpd start Starting OpenNebula daemon: Stale .lock detected. Erasing it. [ OK ] Starting Sunstone Server daemon: sunstone-server started [ OK ] Starting OCCI Server: Stale .lock detected. Erasing it. occi-server started [ OK ] Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using opennebula.scytl.net for ServerName [ OK ] Any hint about those lock files detected? Thanks On 11/01/13 14:51, Carlos Martín Sánchez wrote: Hi, I guess you are referring to the old documentation, right? I found the warning about sqlite and NFS in the 3.2 archives [1]. It should be enough if you move the one.db file and create a symlink. Regards [1] http://opennebula.org/documentation:archives:rel3.2:sfs#considerations_limitations -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org http://www.OpenNebula.org | cmar...@opennebula.org mailto:cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebula On Fri, Jan 11, 2013 at 2:30 PM, Andreas Calvo Gómez andreas.ca...@scytl.com mailto:andreas.ca...@scytl.com wrote: Carlos, We are exporting the whole /var/lib/one directory as per the documentation, which helps to maintain all the cloud by sharing the same ssh public keys and configuration. Do you think placing the SQLite database in a non-NFS directory will make things better? On 11/01/13 14:09, Carlos Martín Sánchez wrote: Hi, Are you exporting only the shared datastores, or the whole /var/lib/one location? In older versions we advised to share /var/lib/one to make the ssh configuration easier, but NFS would make the sqlite DB misbehave. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org http://www.OpenNebula.org | cmar...@opennebula.org mailto:cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebula On Thu, Jan 10, 2013 at 11:45 AM, Andreas Calvo Gómez andreas.ca...@scytl.com mailto:andreas.ca...@scytl.com wrote: Hello, We've been using ONE for some time now, and it worked flawlessly. A month ago, we switched from GFS to NFS to shared storage, because GFS is really difficult to maintain and operate. We found out that Sunstone is becoming inactive randomly: while the WEBUI seems to be working, users cannot log in and logged users cannot operate (launch VNC, start/stop VMs, ...). However, there are no references to an error or lockup either in sunstone logs (both .log and .error) or in ONE logs. Any hint or point to track down this behaviour? ONE version is 3.8.1 under CentOS 6.3. Thanks -- Andreas Calvo Gómez Systems Engineer Scytl Secure Electronic Voting Plaça Gal·la Placidia, 1-3, 1st floor · 08006 Barcelona Phone: + 34 934 230 324 tel:%2B%2034%20934%20230%20324 Fax: + 34 933 251 028 tel:%2B%2034%20933%20251%20028 http://www.scytl.com NOTICE: The information in this e-mail and in any of its attachments is confidential and intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, any disclosure, copying, distribution or retaining of this message or any part of it, without the prior written consent of Scytl Secure Electronic Voting, SA is prohibited and may be unlawful. If you have received this in error, please contact the sender and
Re: [one-users] network problem opennebula 3.8
Hi, Looks like you set the networking driver to tm_ssh, which is a transfer manager driver. You will need to delete and create your host again, using one of the networking drivers [1]. Regards [1] http://opennebula.org/documentation:rel3.8:nm -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | cmar...@opennebula.org | @OpenNebulahttp://twitter.com/opennebulacmar...@opennebula.org 2013/1/22 GyeongRyoon Kim gr...@kisti.re.kr Hi all, I'm trying to launch virtual machine on my cloud with opennebula 3.8 and kvm hypervisor. When I create vm, I got a this error message Tue Jan 22 15:29:37 2013 [DiM][I]: New VM state is ACTIVE. Tue Jan 22 15:29:38 2013 [LCM][I]: New VM state is PROLOG. Tue Jan 22 15:29:38 2013 [VM][I]: Virtual Machine has no context Tue Jan 22 15:29:57 2013 [TM][I]: clone: Cloning gcloud-front.sdfarm.kr:/gcloud/one/var/datastores/101/ba084f2e80cf462c39f3d63e67c280f0 in /gcloud/one/var/datastores/0/113/disk.0 Tue Jan 22 15:29:57 2013 [TM][I]: ExitCode: 0 Tue Jan 22 15:30:00 2013 [TM][I]: mkimage: Making filesystem of 10240M and type ext3 at gcloud01:/gcloud/one/var//datastores/0/113/disk.1 Tue Jan 22 15:30:00 2013 [TM][I]: ExitCode: 0 Tue Jan 22 15:30:01 2013 [TM][I]: mkimage: Making filesystem of 1024M and type swap at gcloud01:/gcloud/one/var//datastores/0/113/disk.2 Tue Jan 22 15:30:01 2013 [TM][I]: ExitCode: 0 Tue Jan 22 15:30:01 2013 [LCM][I]: New VM state is BOOT Tue Jan 22 15:30:01 2013 [VMM][I]: Generating deployment file: /gcloud/one/var/vms/113/deployment.0 Tue Jan 22 15:30:01 2013 [VMM][I]: Remote worker node files not found Tue Jan 22 15:30:01 2013 [VMM][I]: Updating remotes Tue Jan 22 15:30:01 2013 [VMM][I]: ExitCode: 0 Tue Jan 22 15:30:01 2013 [VMM][I]: ExitCode: 0 Tue Jan 22 15:30:01 2013 [VMM][I]: Command execution fail: /var/tmp/one/vnm/tm_ssh/pre PFZNPjxJRD4xMTM8L0lEPjxVSUQ+MDwvVUlEPjxHSUQ+MDwvR0lEPjxVTkFNRT5vbmVhZG1pbjwvVU5BTUU+PEdOQU1FPm9uZWFkbWluPC9HTkFNRT48TkFNRT5zbF9saXZlPC9OQU1FPjxQRVJNSVNTSU9OUz48T1dORVJfVT4xPC9PV05FUl9VPjxPV05FUl9NPjE8L09XTkVSX00+PE9XTkVSX0E+MDwvT1dORVJfQT48R1JPVVBfVT4wPC9HUk9VUF9VPjxHUk9VUF9NPjA8L0dST1VQX00+PEdST1VQX0E+MDwvR1JPVVBfQT48T1RIRVJfVT4wPC9PVEhFUl9VPjxPVEhFUl9NPjA8L09USEVSX00+PE9USEVSX0E+MDwvT1RIRVJfQT48L1BFUk1JU1NJT05TPjxMQVNUX1BPTEw+MDwvTEFTVF9QT0xMPjxTVEFURT4zPC9TVEFURT48TENNX1NUQVRFPjI8L0xDTV9TVEFURT48UkVTQ0hFRD4wPC9SRVNDSEVEPjxTVElNRT4xMzU4ODM2MTUyPC9TVElNRT48RVRJTUU+MDwvRVRJTUU+PERFUExPWV9JRC8+PE1FTU9SWT4wPC9NRU1PUlk+PENQVT4wPC9DUFU+PE5FVF9UWD4wPC9ORVRfVFg+PE5FVF9SWD4wPC9ORVRfUlg+PFRFTVBMQVRFPjxDUFU+PCFbQ0RBVEFbMC41XV0+PC9DUFU+PERJU0s+PENMT05FPjwhW0NEQVRBW1lFU11dPjwvQ0xPTkU+PERBVEFTVE9SRT48IVtDREFUQVtTTDYuM19pbnN0YWxsX09TXV0+PC9EQVRBU1RPUkU+PERBVEFTVE9SRV9JRD48IVtDREFUQVsxMDFdXT48L0RBVEFTVE9 SRV9JRD48 REVWX1BSRUZJWD48IVtDREFUQVtoZF1dPjwvREVWX1BSRUZJWD48RElTS19JRD48IVtDREFUQVswXV0+PC9ESVNLX0lEPjxJTUFHRT48IVtDREFUQVtTTDYgbGl2ZSBjZF1dPjwvSU1BR0U+PElNQUdFX0lEPjwhW0NEQVRBWzExXV0+PC9JTUFHRV9JRD48UkVBRE9OTFk+PCFbQ0RBVEFbWUVTXV0+PC9SRUFET05MWT48U0FWRT48IVtDREFUQVtOT11dPjwvU0FWRT48U09VUkNFPjwhW0NEQVRBWy9nY2xvdWQvb25lL3Zhci9kYXRhc3RvcmVzLzEwMS9iYTA4NGYyZTgwY2Y0NjJjMzlmM2Q2M2U2N2MyODBmMF1dPjwvU09VUkNFPjxUQVJHRVQ+PCFbQ0RBVEFbaGRhXV0+PC9UQVJHRVQ+PFRNX01BRD48IVtDREFUQVtzc2hdXT48L1RNX01BRD48VFlQRT48IVtDREFUQVtDRFJPTV1dPjwvVFlQRT48L0RJU0s+PERJU0s+PEJVUz48IVtDREFUQVt2aXJ0aW9dXT48L0JVUz48REVWX1BSRUZJWD48IVtDREFUQVtoZF1dPjwvREVWX1BSRUZJWD48RElTS19JRD48IVtDREFUQVsxXV0+PC9ESVNLX0lEPjxGT1JNQVQ+PCFbQ0RBVEFbZXh0M11dPjwvRk9STUFUPjxTSVpFPjwhW0NEQVRBWzEwMjQwXV0+PC9TSVpFPjxUQVJHRVQ+PCFbQ0RBVEFbdmRhXV0+PC9UQVJHRVQ+PFRZUEU+PCFbQ0RBVEFbZnNdXT48L1RZUEU+PC9ESVNLPjxESVNLPjxCVVM+PCFbQ0RBVEFbdmlydGlvXV0+PC9CVVM+PERFVl9QUkVGSVg+PCFbQ0RBVEFbaGRdXT48L0RFVl9QUkVGSVg+PERJU0tfSUQ+PCFbQ0RBVEFbMl1dPjwvRElTS19JRD48Uk VBRE9OTFk +PCFbQ0RBVEFbbm9dXT48L1JFQURPTkxZPjxTSVpFPjwhW0NEQVRBWzEwMjRdXT48L1NJWkU+PFRBUkdFVD48IVtDREFUQVt2ZGJdXT48L1RBUkdFVD48VFlQRT48IVtDREFUQVtzd2FwXV0+PC9UWVBFPjwvRElTSz48R1JBUEhJQ1M+PExJU1RFTj48IVtDREFUQVswLjAuMC4wXV0+PC9MSVNURU4+PFBPUlQ+PCFbQ0RBVEFbNjAxM11dPjwvUE9SVD48VFlQRT48IVtDREFUQVt2bmNdXT48L1RZUEU+PC9HUkFQSElDUz48TUVNT1JZPjwhW0NEQVRBWzUxMl1dPjwvTUVNT1JZPjxOQU1FPjwhW0NEQVRBW3NsX2xpdmVdXT48L05BTUU+PE5JQz48QlJJREdFPjwhW0NEQVRBW2V0aDFdXT48L0JSSURHRT48SVA+PCFbQ0RBVEFbMTkyLjE2OC41Ni40XV0+PC9JUD48TUFDPjwhW0NEQVRBWzAyOjAwOmMwOmE4OjM4OjA0XV0+PC9NQUM+PE5FVFdPUks+PCFbQ0RBVEFbUHJpdmF0ZSBMQU4gd2l0aCBldGgxXV0+PC9ORVRXT1JLPjxORVRXT1JLX0lEPjwhW0NEQVRBWzhdXT48L05FVFdPUktfSUQ+PFZMQU4+PCFbQ0RBVEFbTk9dXT48L1ZMQU4+PC9OSUM+PE9TPjxCT09UPjwhW0NEQVRBW2Nkcm9tXV0+PC9CT09UPjwvT1M+PFZNSUQ+PCFbQ0RBVEFbMTEzXV0+PC9WTUlEPjwvVEVNUExBVEU+PEhJU1RPUllfUkVDT1JEUz48SElTVE9SWT48T0lEPjExMzwvT0lEPjxTRVE+MDwvU0VRPjxIT1NUTkFNRT5nY2xvdWQwMTwvSE9TVE5BTUU+PEhJRD4xOTwvSElEPjxTVElNRT4xMzU4ODM2MTc3PC9TVElNRT48RVRJTUU+MDwvR VRJTUU+PF
Re: [one-users] iSCSI multipath
Hi, thank you both for such a high quality and educational thread. I wasn't aware of the possibility of configuring the LVM metadata in a host as read-only, but it fits beautifully with OpenNebula. Mihály, would you like to share your experiences somewhere in the OpenNebula community? wiki.opennebula.org or blog.opennebula.org? I think many people can benefit from your setup. cheers, Jaime On Mon, Jan 21, 2013 at 6:58 PM, Miloš Kozák milos.ko...@lejmr.com wrote: Oh snap, that sounds great I didn't know about that.. it makes all easier. In this scenario only frontend can work with LVM, so no issues of concurrent change. Only one last think to make it really safe against that. Is there any way to suppress LVM changes from hosts, make it read only? And let it RW at frontend? Thanks Dne 21.1.2013 18:50, Mihály Héder napsal(a): Hi, no, you don't have to do any of that. Also, nebula doesn't have to care about LVM metadata at all and therefore there is no corresponding function in it. At /etc/lvm there is no metadata, only configuration files. Lvm metadata simply sits somewhere at the beginning of your iscsi-shared disk, like a partition table. So it is on the storage that is accessed by all your hosts, and no distribution is necessary. Nebula frontend simply issues lvcreate, lvchange, etc, on this shared disk and those commands will manipulate the metadata. It is really LVM's internal business, many layers below opennebula. All you have to make sure that you don't run these commands concurrently from multiple hosts on the same iscsi-attached disk, because then they could interfere with each other. This setting is what you have to indicate in /etc/lvm on the server hosts. Cheers Mihály On 21 January 2013 18:37, Miloš Kozák milos.ko...@lejmr.com wrote: Thank you. does it mean, that I can distribute metadata files located in /etc/lvm on frontend onto other hosts and these hosts will see my logical volumes? Is there any code in nebula which would provide it? Or I need to update DS scripts to update/distribute LVM metadata among servers? Thanks, Milos Dne 21.1.2013 18:29, Mihály Héder napsal(a): Hi, lvm metadata[1] is simply stored on the disk. In the setup we are discussing this happens to be a shared virtual disk on the storage, so any other hosts that are attaching the same virtual disk should see the changes as they happen, provided that they re-read the disk. This re-reading step is what you can trigger with lvscan, but nowadays that seems to be unnecessary. For us it works with Centos 6.3 so I guess Sc Linux should be fine as well. Cheers Mihály [1] http://www.centos.org/docs/5/**html/Cluster_Logical_Volume_** Manager/lvm_metadata.htmlhttp://www.centos.org/docs/5/html/Cluster_Logical_Volume_Manager/lvm_metadata.html On 21 January 2013 12:53, Miloš Kozák milos.ko...@lejmr.com wrote: Hi, thank you for great answer. As I wrote my objective is to avoid as much of clustering sw (pacemaker,..) as possible, so clvm is one of these things I feel bad about them in my configuration.. Therefore I would rather let nebula manage LVM metadata in the first place as I you wrote. Only one last thing I dont understand is a way nebula distributes LVM metadata? Is kernel in Scientific Linux 6.3 new enought to LVM issue you mentioned? Thanks Milos Dne 21.1.2013 12:34, Mihály Héder napsal(a): Hi! Last time we could test an Equalogic it did not have option for create/configure Virtual Disks inside in it by an API, so I think the iSCSI driver is not an alternative, as it would require a configuration step per virtual machine on the storage. However, you can use your storage just fine in a shared LVM scenario. You need to consider two different things: -the LVM metadata, and the actual VM data on the partitions. It is true, that the concurrent modification of the metadata should be avoided as in theory it can damage the whole virtual group. You could use clvm which avoids that by clustered locking, and then every participating machine can safely create/modify/delete LV-s. However, in a nebula setup this is not necessary in every case: you can make the LVM metadata read only on your host servers, and let only the frontend modify it. Then it can use local locking that does not require clvm. -of course the host servers can write the data inside the partitions regardless that the metadata is read-only for them. It should work just fine as long as you don't start two VMs for one partition. We are running this setup with a dual controller Dell MD3600 storage without issues so far. Before that, we used to do the same with XEN machines for years on an older EMC (that was before nebula). Now with nebula we have been using a home-grown module for doing that, which I can send you any time - we plan to submit that as a feature enhancement anyway. Also, there seems to be a similar shared LVM module in the nebula upstream
[one-users] vmcontext in one-context never executes init.sh from context iso
Hi, Because all files in context iso are not executable, then /mnt/init.sh line is never executed in /etc/init.d/vmcontext. Regards, Rolandas Naujikas ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] vmcontext in one-context never executes init.sh from context iso
On Tue, Jan 22, 2013 at 1:48 PM, Rolandas Naujikas rolandas.nauji...@mif.vu.lt wrote: Hi, Because all files in context iso are not executable, then /mnt/init.sh line is never executed in /etc/init.d/vmcontext. Regards, Rolandas Naujikas __**_ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/**listinfo.cgi/users-opennebula.**orghttp://lists.opennebula.org/listinfo.cgi/users-opennebula.org Hello World, A fix could be to run the script using bash /mnt/init.sh. Do you people think that could lead to problems? As far as I know Bash is present in all Linux distribution OpenNebula runs on. Regards, Valentin Bud ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] vmcontext in one-context never executes init.sh from context iso
On 2013-01-22 14:10, Valentin Bud wrote: On Tue, Jan 22, 2013 at 1:48 PM, Rolandas Naujikas rolandas.nauji...@mif.vu.lt mailto:rolandas.nauji...@mif.vu.lt wrote: Hi, Because all files in context iso are not executable, then /mnt/init.sh line is never executed in /etc/init.d/vmcontext. Regards, Rolandas Naujikas _ Users mailing list Users@lists.opennebula.org mailto:Users@lists.opennebula.org http://lists.opennebula.org/__listinfo.cgi/users-opennebula.__org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org Hello World, A fix could be to run the script using bash /mnt/init.sh. Do you people think that could lead to problems? As far as I know Bash is present in all Linux distribution OpenNebula runs on. Better would be sh, because it is lighter (in Debian at least). Rolandas Regards, Valentin Bud ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] vmcontext in one-context never executes init.sh from context iso
On 2013-01-22 14:13, Rolandas Naujikas wrote: On 2013-01-22 14:10, Valentin Bud wrote: On Tue, Jan 22, 2013 at 1:48 PM, Rolandas Naujikas rolandas.nauji...@mif.vu.lt mailto:rolandas.nauji...@mif.vu.lt wrote: Hi, Because all files in context iso are not executable, then /mnt/init.sh line is never executed in /etc/init.d/vmcontext. Regards, Rolandas Naujikas _ Users mailing list Users@lists.opennebula.org mailto:Users@lists.opennebula.org http://lists.opennebula.org/__listinfo.cgi/users-opennebula.__org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org Hello World, A fix could be to run the script using bash /mnt/init.sh. Do you people think that could lead to problems? As far as I know Bash is present in all Linux distribution OpenNebula runs on. Better would be sh, because it is lighter (in Debian at least). I think better solution would be exec_and_log chmod +x $ISO_DIR/* chmod +x error in every remotes/tm/*/context script just before creating iso image. Regards, Rolandas Naujikas Rolandas Regards, Valentin Bud ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Monitoring vm by OCCI
Thanks a lot for your quickly reply. I hope that ganglia will resolve my problem. Therefore there isn't a mode in OpenNebula - OCCI to resolve this issue? 2013/1/22 Karanbir Singh mail-li...@karan.org On 01/22/2013 09:05 AM, Emanuel Marzini wrote: Hi to all, Is there a way to monitor the performance of vm? In sunstone exists, my request is if there is a method to retrieve this information by OCCI or through other methods. If you have a management network, you can get this via ganglia - its literally a case of yum installing starting it and needing no configs - KB __**_ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/**listinfo.cgi/users-opennebula.**orghttp://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Change one.db path [was ONE sunstone locking randomly]
Hi, On Tue, Jan 22, 2013 at 12:02 PM, Andreas Calvo Gómez andreas.ca...@scytl.com wrote: Hello, Is there any way to place the one.db sqlite file in another directory? (so it is outside the NFS shared path) The path to one.db cannot be changed in oned.conf, but a symbolic link works fine. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org http://www.opennebula.org/ | cmar...@opennebula.org | @OpenNebula http://twitter.com/opennebula cmar...@opennebula.org Thanks On 14/01/13 15:32, Andreas Calvo Gómez wrote: We will try it under our maintenance schedule. However, stopping and starting daemons shows the following warnings: [root@opennebula ~]# /etc/init.d/opennebula-occi stop /etc/init.d/opennebula-sunstone stop /etc/init.d/opennebula stop /etc/init.d/httpd stop Stopping OCCI Server daemon: occi-server stopped [ OK ] Stopping Sunstone Server daemon: sunstone-server stopped [ OK ] Stopping OpenNebula daemon: oned and scheduler stopped [ OK ] Stopping httpd:[ OK ] [root@opennebula ~]# service opennebula start service opennebula-sunstone start service opennebula-occi start service httpd start Starting OpenNebula daemon: Stale .lock detected. Erasing it. [ OK ] Starting Sunstone Server daemon: sunstone-server started [ OK ] Starting OCCI Server: Stale .lock detected. Erasing it. occi-server started [ OK ] Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using opennebula.scytl.net for ServerName [ OK ] Any hint about those lock files detected? Thanks On 11/01/13 14:51, Carlos Martín Sánchez wrote: Hi, I guess you are referring to the old documentation, right? I found the warning about sqlite and NFS in the 3.2 archives [1]. It should be enough if you move the one.db file and create a symlink. Regards [1] http://opennebula.org/documentation:archives:rel3.2:sfs#considerations_limitations -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | cmar...@opennebula.org | @OpenNebulahttp://twitter.com/opennebula On Fri, Jan 11, 2013 at 2:30 PM, Andreas Calvo Gómez andreas.ca...@scytl.com wrote: Carlos, We are exporting the whole /var/lib/one directory as per the documentation, which helps to maintain all the cloud by sharing the same ssh public keys and configuration. Do you think placing the SQLite database in a non-NFS directory will make things better? On 11/01/13 14:09, Carlos Martín Sánchez wrote: Hi, Are you exporting only the shared datastores, or the whole /var/lib/one location? In older versions we advised to share /var/lib/one to make the ssh configuration easier, but NFS would make the sqlite DB misbehave. Regards -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | cmar...@opennebula.org | @OpenNebulahttp://twitter.com/opennebula On Thu, Jan 10, 2013 at 11:45 AM, Andreas Calvo Gómez andreas.ca...@scytl.com wrote: Hello, We've been using ONE for some time now, and it worked flawlessly. A month ago, we switched from GFS to NFS to shared storage, because GFS is really difficult to maintain and operate. We found out that Sunstone is becoming inactive randomly: while the WEBUI seems to be working, users cannot log in and logged users cannot operate (launch VNC, start/stop VMs, ...). However, there are no references to an error or lockup either in sunstone logs (both .log and .error) or in ONE logs. Any hint or point to track down this behaviour? ONE version is 3.8.1 under CentOS 6.3. Thanks -- Andreas Calvo Gómez Systems Engineer Scytl Secure Electronic Voting Plaça Gal·la Placidia, 1-3, 1st floor · 08006 Barcelona Phone: + 34 934 230 324 %2B%2034%20934%20230%20324 Fax: + 34 933 251 028 %2B%2034%20933%20251%20028 http://www.scytl.com NOTICE: The information in this e-mail and in any of its attachments is confidential and intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, any disclosure, copying, distribution or retaining of this message or any part of it, without the prior written consent of Scytl Secure Electronic Voting, SA is prohibited and may be unlawful. If you have received this in error, please contact the sender and delete the material from any computer.
Re: [one-users] network problem opennebula 3.8
You have to make the bridges on all the host machines first. OpenNebula doesn't do it for you. But you also have to get the remote scripts on the VM host, there is a onehost command to do that. Steve Timm From: users-boun...@lists.opennebula.org [mailto:users-boun...@lists.opennebula.org] On Behalf Of GyeongRyoon Kim Sent: Tuesday, January 22, 2013 4:00 AM To: opennebula mailing list Subject: [one-users] network problem opennebula 3.8 Hi all, I'm trying to launch virtual machine on my cloud with opennebula 3.8 and kvm hypervisor. When I create vm, I got a this error message Tue Jan 22 15:29:37 2013 [DiM][I]: New VM state is ACTIVE. Tue Jan 22 15:29:38 2013 [LCM][I]: New VM state is PROLOG. Tue Jan 22 15:29:38 2013 [VM][I]: Virtual Machine has no context Tue Jan 22 15:29:57 2013 [TM][I]: clone: Cloning gcloud-front.sdfarm.kr:/gcloud/one/var/datastores/101/ba084f2e80cf462c39f3d63e67c280f0 in /gcloud/one/var/datastores/0/113/disk.0 Tue Jan 22 15:29:57 2013 [TM][I]: ExitCode: 0 Tue Jan 22 15:30:00 2013 [TM][I]: mkimage: Making filesystem of 10240M and type ext3 at gcloud01:/gcloud/one/var//datastores/0/113/disk.1 Tue Jan 22 15:30:00 2013 [TM][I]: ExitCode: 0 Tue Jan 22 15:30:01 2013 [TM][I]: mkimage: Making filesystem of 1024M and type swap at gcloud01:/gcloud/one/var//datastores/0/113/disk.2 Tue Jan 22 15:30:01 2013 [TM][I]: ExitCode: 0 Tue Jan 22 15:30:01 2013 [LCM][I]: New VM state is BOOT Tue Jan 22 15:30:01 2013 [VMM][I]: Generating deployment file: /gcloud/one/var/vms/113/deployment.0 Tue Jan 22 15:30:01 2013 [VMM][I]: Remote worker node files not found Tue Jan 22 15:30:01 2013 [VMM][I]: Updating remotes Tue Jan 22 15:30:01 2013 [VMM][I]: ExitCode: 0 Tue Jan 22 15:30:01 2013 [VMM][I]: ExitCode: 0 Tue Jan 22 15:30:01 2013 [VMM][I]: Command execution fail: /var/tmp/one/vnm/tm_ssh/pre PFZNPjxJRD4xMTM8L0lEPjxVSUQ+MDwvVUlEPjxHSUQ+MDwvR0lEPjxVTkFNRT5vbmVhZG1pbjwvVU5BTUU+PEdOQU1FPm9uZWFkbWluPC9HTkFNRT48TkFNRT5zbF9saXZlPC9OQU1FPjxQRVJNSVNTSU9OUz48T1dORVJfVT4xPC9PV05FUl9VPjxPV05FUl9NPjE8L09XTkVSX00+PE9XTkVSX0E+MDwvT1dORVJfQT48R1JPVVBfVT4wPC9HUk9VUF9VPjxHUk9VUF9NPjA8L0dST1VQX00+PEdST1VQX0E+MDwvR1JPVVBfQT48T1RIRVJfVT4wPC9PVEhFUl9VPjxPVEhFUl9NPjA8L09USEVSX00+PE9USEVSX0E+MDwvT1RIRVJfQT48L1BFUk1JU1NJT05TPjxMQVNUX1BPTEw+MDwvTEFTVF9QT0xMPjxTVEFURT4zPC9TVEFURT48TENNX1NUQVRFPjI8L0xDTV9TVEFURT48UkVTQ0hFRD4wPC9SRVNDSEVEPjxTVElNRT4xMzU4ODM2MTUyPC9TVElNRT48RVRJTUU+MDwvRVRJTUU+PERFUExPWV9JRC8+PE1FTU9SWT4wPC9NRU1PUlk+PENQVT4wPC9DUFU+PE5FVF9UWD4wPC9ORVRfVFg+PE5FVF9SWD4wPC9ORVRfUlg+PFRFTVBMQVRFPjxDUFU+PCFbQ0RBVEFbMC41XV0+PC9DUFU+PERJU0s+PENMT05FPjwhW0NEQVRBW1lFU11dPjwvQ0xPTkU+PERBVEFTVE9SRT48IVtDREFUQVtTTDYuM19pbnN0YWxsX09TXV0+PC9EQVRBU1RPUkU+PERBVEFTVE9SRV9JRD48IVtDREFUQVsxMDFdXT48L0RBVEFTVE9 SRV9JRD48 REVWX1BSRUZJWD48IVtDREFUQVtoZF1dPjwvREVWX1BSRUZJWD48RElTS19JRD48IVtDREFUQVswXV0+PC9ESVNLX0lEPjxJTUFHRT48IVtDREFUQVtTTDYgbGl2ZSBjZF1dPjwvSU1BR0U+PElNQUdFX0lEPjwhW0NEQVRBWzExXV0+PC9JTUFHRV9JRD48UkVBRE9OTFk+PCFbQ0RBVEFbWUVTXV0+PC9SRUFET05MWT48U0FWRT48IVtDREFUQVtOT11dPjwvU0FWRT48U09VUkNFPjwhW0NEQVRBWy9nY2xvdWQvb25lL3Zhci9kYXRhc3RvcmVzLzEwMS9iYTA4NGYyZTgwY2Y0NjJjMzlmM2Q2M2U2N2MyODBmMF1dPjwvU09VUkNFPjxUQVJHRVQ+PCFbQ0RBVEFbaGRhXV0+PC9UQVJHRVQ+PFRNX01BRD48IVtDREFUQVtzc2hdXT48L1RNX01BRD48VFlQRT48IVtDREFUQVtDRFJPTV1dPjwvVFlQRT48L0RJU0s+PERJU0s+PEJVUz48IVtDREFUQVt2aXJ0aW9dXT48L0JVUz48REVWX1BSRUZJWD48IVtDREFUQVtoZF1dPjwvREVWX1BSRUZJWD48RElTS19JRD48IVtDREFUQVsxXV0+PC9ESVNLX0lEPjxGT1JNQVQ+PCFbQ0RBVEFbZXh0M11dPjwvRk9STUFUPjxTSVpFPjwhW0NEQVRBWzEwMjQwXV0+PC9TSVpFPjxUQVJHRVQ+PCFbQ0RBVEFbdmRhXV0+PC9UQVJHRVQ+PFRZUEU+PCFbQ0RBVEFbZnNdXT48L1RZUEU+PC9ESVNLPjxESVNLPjxCVVM+PCFbQ0RBVEFbdmlydGlvXV0+PC9CVVM+PERFVl9QUkVGSVg+PCFbQ0RBVEFbaGRdXT48L0RFVl9QUkVGSVg+PERJU0tfSUQ+PCFbQ0RBVEFbMl1dPjwvRElTS19JRD48Uk VBRE9OTFk +PCFbQ0RBVEFbbm9dXT48L1JFQURPTkxZPjxTSVpFPjwhW0NEQVRBWzEwMjRdXT48L1NJWkU+PFRBUkdFVD48IVtDREFUQVt2ZGJdXT48L1RBUkdFVD48VFlQRT48IVtDREFUQVtzd2FwXV0+PC9UWVBFPjwvRElTSz48R1JBUEhJQ1M+PExJU1RFTj48IVtDREFUQVswLjAuMC4wXV0+PC9MSVNURU4+PFBPUlQ+PCFbQ0RBVEFbNjAxM11dPjwvUE9SVD48VFlQRT48IVtDREFUQVt2bmNdXT48L1RZUEU+PC9HUkFQSElDUz48TUVNT1JZPjwhW0NEQVRBWzUxMl1dPjwvTUVNT1JZPjxOQU1FPjwhW0NEQVRBW3NsX2xpdmVdXT48L05BTUU+PE5JQz48QlJJREdFPjwhW0NEQVRBW2V0aDFdXT48L0JSSURHRT48SVA+PCFbQ0RBVEFbMTkyLjE2OC41Ni40XV0+PC9JUD48TUFDPjwhW0NEQVRBWzAyOjAwOmMwOmE4OjM4OjA0XV0+PC9NQUM+PE5FVFdPUks+PCFbQ0RBVEFbUHJpdmF0ZSBMQU4gd2l0aCBldGgxXV0+PC9ORVRXT1JLPjxORVRXT1JLX0lEPjwhW0NEQVRBWzhdXT48L05FVFdPUktfSUQ+PFZMQU4+PCFbQ0RBVEFbTk9dXT48L1ZMQU4+PC9OSUM+PE9TPjxCT09UPjwhW0NEQVRBW2Nkcm9tXV0+PC9CT09UPjwvT1M+PFZNSUQ+PCFbQ0RBVEFbMTEzXV0+PC9WTUlEPjwvVEVNUExBVEU+PEhJU1RPUllfUkVDT1JEUz48SElTVE9SWT48T0lEPjExMzwvT0lEPjxTRVE+MDwvU0VRPjxIT1NUTkFNRT5nY2xvdWQwMTwvSE9TVE5BTUU+PEhJRD4xOTwvSElEPjxTVElNRT4xMzU4ODM2MTc3PC9TVElNRT48RVRJTUU+MDwvR VRJTUU+PF
Re: [one-users] problems with images in 3.8.3
Hi Rolandas, I've tried to reproduce the bug following your steps, but there must be something else that is triggering it. These are the exact commands I have executed, could you please check if I missed something? $ oneuser list ID NAMEGROUP AUTH VMSMEMORY CPU 0 oneadminoneadmin core - - - 1 serveradmin oneadmin server_c - - - 2 a oneadmin core - - - $ oneimage list ID USER GROUP NAMEDATASTORE SIZE TYPE PER STAT RVMS 0 a oneadmin os default 1M OSNo used 1 $ onevm list ID USER GROUPNAMESTAT UCPUUMEM HOST TIME 0 aoneadmin one-0 runn0 0K localhost0d 00h00 $ onevm saveas 0 0 img_saveas $ onevm cancel 0 $ oneimage chown img_saveas oneadmin $ oneimage list ID USER GROUP NAMEDATASTORE SIZE TYPE PER STAT RVMS 0 a oneadmin os default 1M OSNo rdy 0 1 oneadmin oneadmin img_saveas default 1M OSNo rdy 0 $ oneimage delete img_saveas $ onetemplate instantiate 0 $ onevm list ID USER GROUPNAMESTAT UCPUUMEM HOST TIME 1 aoneadmin one-1 runn0 0K localhost0d 00h00 $ onevm saveas 1 0 img_saveas $ onevm cancel 1 $ oneimage list ID USER GROUP NAMEDATASTORE SIZE TYPE PER STAT RVMS 0 a oneadmin os default 1M OSNo rdy 0 2 a oneadmin img_saveas default 1M OSNo rdy 0 $ oneimage chown img_saveas oneadmin $ oneimage list ID USER GROUP NAMEDATASTORE SIZE TYPE PER STAT RVMS 0 a oneadmin os default 1M OSNo rdy 0 2 oneadmin oneadmin img_saveas default 1M OSNo rdy 0 And the templates: $ onetemplate show 0 TEMPLATE 0 INFORMATION ID : 0 NAME : template-0 USER : a GROUP : oneadmin REGISTER TIME : 01/22 15:44:24 PERMISSIONS OWNER : um- GROUP : --- OTHER : --- TEMPLATE CONTENTS CPU=1 DISK=[ IMAGE=os ] MEMORY=128 TEMPLATE_ID=0 $ oneimage show 0 IMAGE 0 INFORMATION ID : 0 NAME : os USER : a GROUP : oneadmin DATASTORE : default TYPE : OS REGISTER TIME : 01/22 15:44:12 PERSISTENT : No SOURCE : /var/lib/one/datastores/1/4be57b711606b657765d2c677fdf1767 PATH : /etc/hosts SIZE : 1M STATE : rdy RUNNING_VMS: 0 PERMISSIONS OWNER : um- GROUP : --- OTHER : --- IMAGE TEMPLATE DEV_PREFIX=hd Regards -- Carlos Martín, MSc Project Engineer OpenNebula - The Open-source Solution for Data Center Virtualization www.OpenNebula.org | cmar...@opennebula.org | @OpenNebulahttp://twitter.com/opennebulacmar...@opennebula.org On Tue, Jan 22, 2013 at 11:09 AM, Rolandas Naujikas rolandas.nauji...@mif.vu.lt wrote: On 2013-01-22 09:58, Rolandas Naujikas wrote: Hi, I see that bug http://dev.opennebula.org/**issues/1087http://dev.opennebula.org/issues/1087reappeared in 3.8.3. The sequence to repeat is: 1) create an image as save from VM (as an user in oneadmin group); 2) change owner to oneadmin; 3) delete image; 4) repeat (1) and (2) will fail saying [ImageChown] USER [0] already owns IMAGE [N] with NAME XXX, where N - is id of already deleted image. Restart of one solves temporary problem. Also I saw several times that images were in use by nonexistent VM. onedb fsck will complain and correct that. At least I can confirm it with cancel action on VM. Regards, Rolandas Naujikas __**_ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/**listinfo.cgi/users-opennebula.**orghttp://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Good Morning
Please unsubscribe me of you user list, This e-mail and any attached documents may contain confidential or proprietary information. Any unauthorized disclosure, distribution, or other use is prohibited. If you are not the intended recipient, please advise the sender immediately and delete this message and all attached documents from your information system. Este correo electr?nico as? como los archivos adjuntos, se consideran como informaci?n confidencial. Queda prohibido la distribuci?n, uso o divulgaci?n de la informaci?n si no cuenta con autorizaci?n. Si usted no es la persona a quien deba ir dirigido este correo electr?nico, favor de notificar por este medio al remitente y eliminar el mensaje de su sistema de informaci?n. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] (no subject)
Please unsubscribe me -- *Mangai vellingiri M.E.,* ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Please unsubscribe me of you user list
Please unsubscribe me of you user list, Shabir Cassamo Sent from my iPhone ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] error : virDomainDefParseXML:8303 : unknown OS type hvm
Hi, I launched 100 virtual machines using the self-service. 97 were fine but three failed with the error below. This is strange as all the hosts as identical copies booted with PXE. Any idea why three would get this error? Regards, Gerry error : virDomainDefParseXML:8303 : unknown OS type hvm -- Gerry O'Brien Systems Manager School of Computer Science and Statistics Trinity College Dublin Dublin 2 IRELAND 00 353 1 896 1341 ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] iSCSI multipath
Hi! You need to look at locking_type in the lvm.conf manual [1]. The default - locking in a local directory - is ok for the frontend, and type 4 is read-only. However, you should not forget that this only prevents damaging thing by the lvm commands. If you start to write zeros to your disk with the dd command for example, that will kill your partition regardless the lvm setting. So this is against user or middleware errors mainly, not against malicious attacks. Cheers Mihály Héder MTA SZTAKI [1] http://linux.die.net/man/5/lvm.conf On 21 January 2013 18:58, Miloš Kozák milos.ko...@lejmr.com wrote: Oh snap, that sounds great I didn't know about that.. it makes all easier. In this scenario only frontend can work with LVM, so no issues of concurrent change. Only one last think to make it really safe against that. Is there any way to suppress LVM changes from hosts, make it read only? And let it RW at frontend? Thanks Dne 21.1.2013 18:50, Mihály Héder napsal(a): Hi, no, you don't have to do any of that. Also, nebula doesn't have to care about LVM metadata at all and therefore there is no corresponding function in it. At /etc/lvm there is no metadata, only configuration files. Lvm metadata simply sits somewhere at the beginning of your iscsi-shared disk, like a partition table. So it is on the storage that is accessed by all your hosts, and no distribution is necessary. Nebula frontend simply issues lvcreate, lvchange, etc, on this shared disk and those commands will manipulate the metadata. It is really LVM's internal business, many layers below opennebula. All you have to make sure that you don't run these commands concurrently from multiple hosts on the same iscsi-attached disk, because then they could interfere with each other. This setting is what you have to indicate in /etc/lvm on the server hosts. Cheers Mihály On 21 January 2013 18:37, Miloš Kozák milos.ko...@lejmr.com wrote: Thank you. does it mean, that I can distribute metadata files located in /etc/lvm on frontend onto other hosts and these hosts will see my logical volumes? Is there any code in nebula which would provide it? Or I need to update DS scripts to update/distribute LVM metadata among servers? Thanks, Milos Dne 21.1.2013 18:29, Mihály Héder napsal(a): Hi, lvm metadata[1] is simply stored on the disk. In the setup we are discussing this happens to be a shared virtual disk on the storage, so any other hosts that are attaching the same virtual disk should see the changes as they happen, provided that they re-read the disk. This re-reading step is what you can trigger with lvscan, but nowadays that seems to be unnecessary. For us it works with Centos 6.3 so I guess Sc Linux should be fine as well. Cheers Mihály [1] http://www.centos.org/docs/5/html/Cluster_Logical_Volume_Manager/lvm_metadata.html On 21 January 2013 12:53, Miloš Kozák milos.ko...@lejmr.com wrote: Hi, thank you for great answer. As I wrote my objective is to avoid as much of clustering sw (pacemaker,..) as possible, so clvm is one of these things I feel bad about them in my configuration.. Therefore I would rather let nebula manage LVM metadata in the first place as I you wrote. Only one last thing I dont understand is a way nebula distributes LVM metadata? Is kernel in Scientific Linux 6.3 new enought to LVM issue you mentioned? Thanks Milos Dne 21.1.2013 12:34, Mihály Héder napsal(a): Hi! Last time we could test an Equalogic it did not have option for create/configure Virtual Disks inside in it by an API, so I think the iSCSI driver is not an alternative, as it would require a configuration step per virtual machine on the storage. However, you can use your storage just fine in a shared LVM scenario. You need to consider two different things: -the LVM metadata, and the actual VM data on the partitions. It is true, that the concurrent modification of the metadata should be avoided as in theory it can damage the whole virtual group. You could use clvm which avoids that by clustered locking, and then every participating machine can safely create/modify/delete LV-s. However, in a nebula setup this is not necessary in every case: you can make the LVM metadata read only on your host servers, and let only the frontend modify it. Then it can use local locking that does not require clvm. -of course the host servers can write the data inside the partitions regardless that the metadata is read-only for them. It should work just fine as long as you don't start two VMs for one partition. We are running this setup with a dual controller Dell MD3600 storage without issues so far. Before that, we used to do the same with XEN machines for years on an older EMC (that was before nebula). Now with nebula we have been using a home-grown module for doing that, which I can send you any time - we plan to submit that as a feature enhancement anyway. Also, there seems to be a similar
Re: [one-users] vmcontext in one-context never executes init.sh from context iso
I also think it is better to make the file executable. I'll check the ISO extensions and test if we can add executable permissions there. Having an executable is better as this init.sh script can be executed by anything, just setting the shebang. On Tue, Jan 22, 2013 at 1:20 PM, Rolandas Naujikas rolandas.nauji...@mif.vu.lt wrote: On 2013-01-22 14:13, Rolandas Naujikas wrote: On 2013-01-22 14:10, Valentin Bud wrote: On Tue, Jan 22, 2013 at 1:48 PM, Rolandas Naujikas rolandas.nauji...@mif.vu.lt mailto:rolandas.nauji...@mif.vu.lt wrote: Hi, Because all files in context iso are not executable, then /mnt/init.sh line is never executed in /etc/init.d/vmcontext. Regards, Rolandas Naujikas _ Users mailing list Users@lists.opennebula.org mailto:Users@lists.opennebula.org http://lists.opennebula.org/__listinfo.cgi/users-opennebula.__org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org Hello World, A fix could be to run the script using bash /mnt/init.sh. Do you people think that could lead to problems? As far as I know Bash is present in all Linux distribution OpenNebula runs on. Better would be sh, because it is lighter (in Debian at least). I think better solution would be exec_and_log chmod +x $ISO_DIR/* chmod +x error in every remotes/tm/*/context script just before creating iso image. Regards, Rolandas Naujikas Rolandas Regards, Valentin Bud ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Javier Fontán Muiños Project Engineer OpenNebula - The Open Source Toolkit for Data Center Virtualization www.OpenNebula.org | jfon...@opennebula.org | @OpenNebula ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] [HELP] noVNC
Hay, i cann't install noVNC : sudo ./install_noVNC.sh Downloding noVNC lastest version ./install_noVNC.sh: line 25: curl: command not found \nError downloading noVNC in cd /usr/share/one how can I be able to run install noVNC? and why after sunstone start, /etc/one/sunstone-server.conf inaccessible ? ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] [HELP] noVNC
You need to install curl. In Ubuntu it's apt-get install curl Centos and so yum install curl On Jan 22, 2013 6:51 PM, Dimas Alif dimas...@gmail.com wrote: Hay, i cann't install noVNC : sudo ./install_noVNC.sh Downloding noVNC lastest version ./install_noVNC.sh: line 25: curl: command not found \nError downloading noVNC in cd /usr/share/one how can I be able to run install noVNC? and why after sunstone start, /etc/one/sunstone-server.conf inaccessible ? ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] [HELP] unable connect sunstone
hay,
config --
dimas@dimas:~S cat /var/log/one/sunstone.log
--
Server configuration
--
{:vnc_proxy_support_wss=false,
:one_xmlrpc=http://localhost:2633/RPC2;,
:marketplace_url=https://marketplace.c12g.com/appliance;,
:core_auth=cipher,
:debug_level=3,
:host=127.0.0.1,
:lang=en_US,
:vnc_proxy_cert=nil,
:vnc_proxy_port=29876,
:tmpdir=/var/tmp,
:auth=sunstone,
:port=9869,
:vnc_proxy_key=nil,
:vnc_proxy_path=/usr/share/one/websockify/websocketproxy.py}
Wed Jan 23 13:22:17 2013 [E]: Error initializing authentication system
Wed Jan 23 13:22:17 2013 [E]: Connection refused - connect(2)
and opened with browser does not connect unable to connect, what is wrong?
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] [HELP] unable connect sunstone
Hey,
try changing the host parameter to the IP-adress of the computer, where
Sunstone is running.
Keeping it on 127.0.0.1 will only allow you to reach it from the same computer,
where Sunstone is installed.
Best regards,
Markus
hay,
config --
dimas@dimas:~S cat /var/log/one/sunstone.log
--
Server configuration
--
{:vnc_proxy_support_wss=false,
:one_xmlrpc=http://localhost:2633/RPC2;,
:marketplace_url=https://marketplace.c12g.com/appliance;,
:core_auth=cipher,
:debug_level=3,
:host=127.0.0.1,
:lang=en_US,
:vnc_proxy_cert=nil,
:vnc_proxy_port=29876,
:tmpdir=/var/tmp,
:auth=sunstone,
:port=9869,
:vnc_proxy_key=nil,
:vnc_proxy_path=/usr/share/one/websockify/websocketproxy.py}
Wed Jan 23 13:22:17 2013 [E]: Error initializing authentication system
Wed Jan 23 13:22:17 2013 [E]: Connection refused - connect(2)
and opened with browser does not connect unable to connect, what is wrong?
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] [HELP] unable connect sunstone
Try to set:
host="0.0.0.0"
to connect sunstone from anywhere, or:
host="IP adress of node where sunstone is running"
J.B.
Dňa 23.01.2013 07:47, Dimas Alif wrote
/ napísal(a):
hay,
config --
dimas@dimas:~S cat /var/log/one/sunstone.log
--
Server configuration
--
{:vnc_proxy_support_wss=false,
:_one_xmlrpc_="http://localhost:2633/RPC2",
:marketplace_url="https://marketplace.c12g.com/appliance",
:core_auth="cipher",
:debug_level=3,
:host="127.0.0.1",
:lang="en_US",
:vnc_proxy_cert=nil,
:vnc_proxy_port=29876,
:tmpdir="/var/tmp",
:auth="sunstone",
:port=9869,
:vnc_proxy_key=nil,
:vnc_proxy_path="/usr/share/one/websockify/websocketproxy.py"}
Wed Jan 23 13:22:17 2013 [E]: Error initializing authentication
system
Wed Jan 23 13:22:17 2013 [E]: Connection refused - connect(2)
and opened with browser
does not connect "unable to
connect", what is wrong?
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
--
S pozdravom / Best Regards
Jan Benadik
tel.: 00421 46 5151 332
fax : 00421 46 5151380
mailto: jbena...@elas.sk
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
