Re: [one-users] mooseFS OpenNebula integration
2012/11/7 Shankhadeep Shome shank15...@gmail.com: look at glusterfs for mirrored storage configurations, its been very stable for us since 3.3 and you don't need any special transfer drivers. standard file system will suffice. Even with MooseFS you don't need any special driver. A standard fuse mount, like for gluster, is enough. The special driver allows the use of advanced features present in moosefs like snapshot and so on, but is not mandatory. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] VNC problem from Sunstone interface
Dňa 07.11.2012 08:18, Hector Sanjuan
wrote / napísal(a):
Any chance the "Use Secure WSS" is checked in sunstone
config? Can you check/uncheck and retry with it unchecked just
in case?
Secure WSS wasn't checked, but I tried to check/uncheck and run once
again with unchecked - nothing changed :-(
Otherwise, kill your sunstone proxy and restart it manually:
python
/usr/share/opennebula/websockify/websocketproxy.py
--target-config=/var/lib/one/sunstone_vnc_tokens 29876
1. sunstone stopped, occi stopped
oneadmin@myto-node:~$ ps aux|grep py
oneadmin 12456 0.0 0.0 9516 904 pts/2 S+ 09:56 0:00
grep py
2.
oneadmin@myto-node:/etc/one$ python
/usr/share/opennebula/websockify/websocketproxy.py
--target-config=/var/lib/one/sunstone_vnc_tokens 29876
WebSocket server settings:
- Listen on :29876
- Flash security policy server
- No SSL/TLS support (no cert file)
- proxying from :29876 to targets in
/var/lib/one/sunstone_vnc_tokens
oneadmin@myto-node:~$ ps aux|grep py
oneadmin 12457 0.5 0.1 93056 16800 pts/1 S+ 09:57 0:00
python /usr/share/opennebula/websockify/websocketproxy.py
--target-config=/var/lib/one/sunstone_vnc_tokens 29876
oneadmin 12460 0.0 0.0 9516 908 pts/2 S+ 09:57 0:00
grep py
3. oneadmin@myto-node:~$ sunstone-server start
sunstone-server started
oneadmin@myto-node:~$ ps aux|grep py
oneadmin 12457 0.1 0.1 93056 16800 pts/1 S+ 09:57 0:00
python /usr/share/opennebula/websockify/websocketproxy.py
--target-config=/var/lib/one/sunstone_vnc_tokens 29876
oneadmin 12481 0.9 0.0 0 0 pts/2 Z 09:58 0:00
[python] defunct
oneadmin 12484 0.0 0.0 9516 908 pts/2 S+ 09:58 0:00
grep py
Here seems to be an issue - if websockify process runs in time of
sunstone is starting - python process is defunct. If a
defunct python proces exist in system, VNC server is disconnected
immediately and 10 lines is added to websockify console:
oneadmin@myto-node:~$ python
/usr/share/opennebula/websockify/websocketproxy.py
--target-config=/var/lib/one/sunstone_vnc_tokens 29876
WebSocket server settings:
- Listen on :29876
- Flash security policy server
- No SSL/TLS support (no cert file)
- proxying from :29876 to targets in
/var/lib/one/sunstone_vnc_tokens
1: 10.0.1.125: SSL connection but '/var/lib/one/self.pem'
not found
2: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
3: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
4: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
5: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
6: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
7: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
8: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
9: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
10: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
In /etc/one/sunstone-server there is:
:vnc_proxy_base_port: 29876
:vnc_proxy_path: /usr/share/opennebula/websockify/websocketproxy.py
:vnc_proxy_support_wss: no
:vnc_proxy_cert:
:vnc_proxy_key:
-rwxr-xr-x 1 root root 3691 okt 26 18:13 sunstone-server
if [ -z "$ONE_LOCATION" ]; then
SUNSTONE_PID=/var/run/one/sunstone.pid
SUNSTONE_SERVER=/usr/share/opennebula/sunstone/sunstone-server.rb
SUNSTONE_LOCK_FILE=/var/lock/one/.sunstone.lock
SUNSTONE_LOG=/var/log/one/sunstone.log
SUNSTONE_LOG_ERROR=/var/log/one/sunstone.error
SUNSTONE_CONF=/etc/one/sunstone-server.conf
else
SUNSTONE_PID=$ONE_LOCATION/var/sunstone.pid
SUNSTONE_SERVER=$ONE_LOCATION/lib/sunstone/sunstone-server.rb
SUNSTONE_LOCK_FILE=$ONE_LOCATION/var/.sunstone.lock
SUNSTONE_LOG=$ONE_LOCATION/var/sunstone.log
SUNSTONE_LOG_ERROR=$ONE_LOCATION/var/sunstone.error
SUNSTONE_CONF=$ONE_LOCATION/etc/sunstone-server.conf
fi
setup()
{
TMPDIR=$(grep ^:tmpdir: $SUNSTONE_CONF|awk '{print $2}')
if [ -n "$TMPDIR" ]; then
export TMPDIR
mkdir -p $TMPDIR
fi
if [ -f $SUNSTONE_LOCK_FILE ]; then
if [ -f $SUNSTONE_PID ]; then
SUNSTONEPID=`cat $SUNSTONE_PID`
ps $SUNSTONEPID /dev/null
if [ $? -eq 0 ]; then
echo -n "Sunstone Server is still running
Re: [one-users] VM Disaster Recovery without resubmit of harddisk images
Hi Stefan, That can't be done currently, but I've opened a ticket [1] to evaluate this feature for future versions. Meanwhile, the workaround is quite simple: From the running or unknown state you can execute a resubmit. This will move the VM to pending, and the scheduler will re-deploy it in a working Host. At this point, the VM will be in prolog state [2], and this in when the disks are copied again to the VM directory. In the front-end, edit the files /var/lib/one/remotes/tm/shared/ clone context ln mkimage mkswap to check if the destination disk file already exists and exit. Remember to execute 'onehost sync' after any change in the remotes directory. This way opennebula will copy the new files to the Hosts in the next monitorization cycle. Regards [1] http://dev.opennebula.org/issues/1639 [2] http://opennebula.org/_media/documentation:rel3.8:states-complete.png -- 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 Mon, Oct 1, 2012 at 4:57 PM, stefan.stein...@brodos.de wrote: Hi, I am currently using OpenNebula with multiple Hosts and the VM Images Stored in an shared NFS System. So every Host sees all Images. I got now the Problem that I want to provide a fault tolerant system with mostly no loss of data on crash. Let's have the situation that one of my Host crashes... OpenNebula now tells me that the Host is down but still assumes that the VM are running. What I now want to do is to restart the VM which was running on the crashed Host with the same already deployed hard disk images on a different Host still working host to get the system with the existing data back running (something like an offline migration but with one host down). Till now I was not able to find a way to do that in OpenNebula. Is there already a way and I didn't find it or is that planed as a future feature? regards Stefan ___ 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] How to use virtio bus for disks
Hello @all, maybe I missed this one, but I can't find the relevant part of the Documentation pointing out that you have to name you device 'vdX' in order to use the virtio-bus! It really took me some time to figure this out! To use a disk via virtio (at leased while using Windows as a guest), you have to set DEV_PREFIX=vd TARGET=vda in your image template definition. BTW.: Is virtio faster than SCSI or IDE? ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] How to use virtio bus for disks
On Wed, Nov 7, 2012 at 1:51 PM, Ruben S. Montero rube...@dacya.ucm.eswrote: Hi Its in the KVM driver http://opennebula.org/documentation:rel3.8:kvmg#virtio Maybe we can link it in other places of the documentation...? I think this should be mentioned at leased in the Image Definition Template section http://opennebula.org/documentation:rel3.8:img_template and maybe also in the Virtual Machine Definition File section ... http://opennebula.org/documentation:rel3.8:template Cheers, Markus ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Can't log on into Windows XP virtual machine
On 11/7/2012 8:40 PM, Daniel Molina wrote: Hi, On 30 October 2012 04:25, Hoàng Thái Xuân Khoa htxuank...@gmail.com mailto:htxuank...@gmail.com wrote: Hello everyone, I use OpenNebula 3.6 Ubuntu 12.04 (desktop server). I was successfully deploy log on into ttylinux virtual machine. After that, I decided deploy Windows XP to cluster nodes, the WinXP virtual machine in “runn” state. But, when I try to log on into Windows XP after deployed via OpenNebula, I got the error: “Boot failed: could not boot into hard disk. Fatal error: no bootable device”. So, I decided to log on Windows XP not via OpenNebula, I used this command: kvm -m 1024 /path/to/WinXP.img and I successfully logged on Windows XP and used it normally. I don't understand why? Why when i used OpenNebula to deploy to cluster nodes, it's state is runn but i can't log on. Can someone give me a hint for this problem? I installed Windows XP by these command: qemu-img create -f raw WinXP.img 6G kvm -cdrom /path/toWinXP.iso -m 1024 -boot d /path/to/WinXP.img This is my image template virtual machine template: // IMAGE TEMPLATE NAME = WinXP PATH = /path/to/WinXP.img TYPE = OS PUBLIC = YES RESTRICTED_DIRS = /etc/ DESCRIPTION = WinXP for testing purpose when using OpenNebula to deploy a private cloud. // WINXP VIRTUAL MACHINE TEMPLATE NAME = WinXP CPU = 1 MEMORY = 1024 OS = [ BOOT = hd ] DISK = [IMAGE_ID = 2] DISK = [ type = fs, size = 1024, format = ntfs, target = hda] GRAPHICS = [ TYPE = vnc, LISTEN = 0.0.0.0, PORT = 5920 ] NIC = [ NETWORK = RANGEDLAN ] FEATURES = [ acpi = yes ] It looks like it cannot find a bootable device. You can specify this device in the OS section (ROOT) [1]. Since you added a second disk with the target hda the first disk (IMAGE_ID=2) will be hdb. Hope this helps [1] http://opennebula.org/documentation:rel3.8:template#os_and_boot_options_section Thanks you in advance. -- Hoàng Thái Xuân Khoa Ho Chi Minh city, Vietnam ___ Users mailing list Users@lists.opennebula.org mailto:Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Daniel Molina Project Engineer OpenNebula - The Open Source Solution for Data Center Virtualization www.OpenNebula.org http://www.OpenNebula.org | dmol...@opennebula.org mailto:dmol...@opennebula.org | @OpenNebula Thanks you so much Daniel. I followed your solution and the original error No bootable device [1] is solved. But, then i got the error BOOTMGR is missing [2]. I think maybe this is the error about Windows XP boot process, not OpenNebula. But as i mentioned in my previous email, when i used this virtual machine by this command: kvm -m 1024 /path/to/WinXP.img, i can log on and using the virtual machine normally. Here is my virtual template after modified: NAME = WinXP CPU = 1 MEMORY = 1024 OS = [ BOOT = hd, ROOT = hdb ] DISK = [IMAGE_ID = 2] DISK = [ type = fs, size = 1024, format = ntfs, target = hda] GRAPHICS = [ TYPE = vnc, LISTEN = 0.0.0.0, PORT = 5920 ] NIC = [ NETWORK = RANGEDLAN ] FEATURES = [ acpi = yes ] I aslo get some information about the virtual machine when it was deployed via virsh command: virsh # list IdName State 2 one-98 running virsh # dumpxml 2 domain type='kvm' id='2' nameone-98/name uuid1ed4a54b-fc44-02b4-84e8-b8ec3a88b93d/uuid memory unit='KiB'1048576/memory currentMemory unit='KiB'1048576/currentMemory vcpu placement='static'1/vcpu os type arch='i686' machine='pc-1.2'hvm/type boot dev='hd'/ /os features acpi/ /features clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/bin/kvm/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/var/lib/one//datastores/0/98/disk.1'/ target dev='hda' bus='ide'/ alias name='ide0-0-0'/ address type='drive' controller='0' bus='0' target='0' unit='0'/ /disk disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/var/lib/one//datastores/0/98/disk.0'/ target dev='hdb' bus='ide'/ alias name='ide0-0-1'/ address type='drive' controller='0' bus='0' target='0' unit='1'/ /disk controller type='usb' index='0' alias name='usb0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x2'/ /controller controller type='ide' index='0' alias name='ide0'/ address type='pci' domain='0x' bus='0x00' slot='0x01' function='0x1'/ /controller interface type='bridge' mac address='02:00:c0:a8:7a:0a'/
Re: [one-users] VNC problem from Sunstone interface
Somehow it is trying to connect with wss :S:10.0.1.125: SSL connection but '/var/lib/one/self.pem' not foundOn sunstone, can you check your user properties (users tab - select user - update properties).In the user template, is there a VNC_WSS variable set? To what value? If so, can you delete it? Reload the sunstone page, logout, login and retry?HectorOn Wed, 07 Nov 2012 10:09:31 +0100, Jan Benadik jan.bena...@atos.net wrote:
Dňa 07.11.2012 08:18, Hector Sanjuan
wrote / napísal(a):
Any chance the "Use Secure WSS" is checked in sunstone
config? Can you check/uncheck and retry with it unchecked just
in case?
Secure WSS wasn't checked, but I tried to check/uncheck and run once
again with unchecked - nothing changed :-(
Otherwise, kill your sunstone proxy and restart it manually:
python
/usr/share/opennebula/websockify/websocketproxy.py
--target-config=/var/lib/one/sunstone_vnc_tokens 29876
1. sunstone stopped, occi stopped
oneadmin@myto-node:~$ ps aux|grep py
oneadmin 12456 0.0 0.0 9516 904 pts/2 S+ 09:56 0:00
grep py
2.
oneadmin@myto-node:/etc/one$ python
/usr/share/opennebula/websockify/websocketproxy.py
--target-config=/var/lib/one/sunstone_vnc_tokens 29876
WebSocket server settings:
- Listen on :29876
- Flash security policy server
- No SSL/TLS support (no cert file)
- proxying from :29876 to targets in
/var/lib/one/sunstone_vnc_tokens
oneadmin@myto-node:~$ ps aux|grep py
oneadmin 12457 0.5 0.1 93056 16800 pts/1 S+ 09:57 0:00
python /usr/share/opennebula/websockify/websocketproxy.py
--target-config=/var/lib/one/sunstone_vnc_tokens 29876
oneadmin 12460 0.0 0.0 9516 908 pts/2 S+ 09:57 0:00
grep py
3. oneadmin@myto-node:~$ sunstone-server start
sunstone-server started
oneadmin@myto-node:~$ ps aux|grep py
oneadmin 12457 0.1 0.1 93056 16800 pts/1 S+ 09:57 0:00
python /usr/share/opennebula/websockify/websocketproxy.py
--target-config=/var/lib/one/sunstone_vnc_tokens 29876
oneadmin 12481 0.9 0.0 0 0 pts/2 Z 09:58 0:00
[python] defunct
oneadmin 12484 0.0 0.0 9516 908 pts/2 S+ 09:58 0:00
grep py
Here seems to be an issue - if websockify process runs in time of
sunstone is starting - python process is defunct. If a
defunct python proces exist in system, VNC server is disconnected
immediately and 10 lines is added to websockify console:
oneadmin@myto-node:~$ python
/usr/share/opennebula/websockify/websocketproxy.py
--target-config=/var/lib/one/sunstone_vnc_tokens 29876
WebSocket server settings:
- Listen on :29876
- Flash security policy server
- No SSL/TLS support (no cert file)
- proxying from :29876 to targets in
/var/lib/one/sunstone_vnc_tokens
1: 10.0.1.125: SSL connection but '/var/lib/one/self.pem'
not found
2: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
3: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
4: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
5: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
6: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
7: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
8: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
9: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
10: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not
found
In /etc/one/sunstone-server there is:
:vnc_proxy_base_port: 29876
:vnc_proxy_path: /usr/share/opennebula/websockify/websocketproxy.py
:vnc_proxy_support_wss: no
:vnc_proxy_cert:
:vnc_proxy_key:
-rwxr-xr-x 1 root root 3691 okt 26 18:13 sunstone-server
if [ -z "$ONE_LOCATION" ]; then
SUNSTONE_PID=/var/run/one/sunstone.pid
SUNSTONE_SERVER=/usr/share/opennebula/sunstone/sunstone-server.rb
SUNSTONE_LOCK_FILE=/var/lock/one/.sunstone.lock
SUNSTONE_LOG=/var/log/one/sunstone.log
SUNSTONE_LOG_ERROR=/var/log/one/sunstone.error
SUNSTONE_CONF=/etc/one/sunstone-server.conf
else
SUNSTONE_PID=$ONE_LOCATION/var/sunstone.pid
SUNSTONE_SERVER=$ONE_LOCATION/lib/sunstone/sunstone-server.rb
SUNSTONE_LOCK_FILE=$ONE_LOCATION/var/.sunstone.lock
SUNSTONE_LOG=$ONE_LOCATION/var/sunstone.log
SUNSTONE_LOG_ERROR=$ONE_LOCATION/var/sunstone.error
SUNSTONE_CONF=$ONE_LOCATION/etc/sunstone-server.conf
fi
setup()
{
TMPDIR=$(grep ^:tmpdir: $SUNSTONE_CONF|awk '{print $2}')
if [ -n "$TMPDIR" ]; then
export TMPDIR
mkdir -p
Re: [one-users] Delete image fail on the LVM type datastore
Hello, I closed the ticket, because everything works for me as expected. I reckon that there must be a configuration issue somewhere. Are you still experiencing this? cheers, Jaime On Fri, Nov 2, 2012 at 5:48 AM, Jaime Melis jme...@opennebula.org wrote: Hi, everthing seems correct. I've opened a bug report in order to review it: http://dev.opennebula.org/issues/1632 cheers, Jaime On Fri, Nov 2, 2012 at 2:43 AM, zouxinzhe zouxin...@gmail.com wrote: ** Hi, here is the information you want # $ onedatastore show 100 DATASTORE 100 INFORMATION ID : 100 NAME : lvm_datastore USER : oneadmin GROUP : oneadmin CLUSTER: - DS_MAD : lvm TM_MAD : lvm BASE PATH : /opt/nebula/ONE/var/datastores/100 PERMISSIONS OWNER : um- GROUP : u-- OTHER : --- DATASTORE TEMPLATE DISK_TYPE=block DS_MAD=lvm TM_MAD=lvm VG_NAME=vg_node176 IMAGES 21 # I canot show images that have been deleted from the OpenNebula.Follow is the image create by the same config file $ oneimage show 21 IMAGE 21 INFORMATION ID : 21 NAME : RedHat3 USER : oneadmin GROUP : oneadmin DATASTORE : lvm_datastore TYPE : OS REGISTER TIME : 11/01 17:41:44 PERSISTENT : No SOURCE : localhost:vg_node176.lv-one-21 PATH : /opt/nebula/images/rhel.5.5.x86_64.raw.small SIZE : 2.5G STATE : rdy RUNNING_VMS: 0 PERMISSIONS OWNER : um- GROUP : --- OTHER : --- IMAGE TEMPLATE DEV_PREFIX=hd # $cat /opt/nebula/ONE/var/remotes/datastore/lvm/lvm.conf # Default volume group VG_NAME=vg-one # Default LVM server host HOST=localhost # Default LV snapshot SIZE DEFAULT_SIZE=512 # -- zouxinzhe *From:* Jaime Melis jme...@opennebula.org *Date:* 2012-10-31 19:00 *To:* 邹欣哲 zouxin...@gmail.com *CC:* Users OpenNebula users@lists.opennebula.org *Subject:* Re: [one-users] Delete image fail on the LVM type datastore Hi, please send us the following information: $ onedatastore show -x lvm_datastore_id $ oneimage show -x image_id (after creating the image and before deleting it) $ cat /var/lib/one/remotes/datastore/lvm/lvm.conf cheers, Jaime On Wed, Oct 31, 2012 at 9:06 AM, 邹欣哲 zouxin...@gmail.com wrote: Hi everyone,I have found several problems when I use LVM datastore on OpenNebula3.8. First,when I delete the image which is registed in the LVM datastore, OpenNebula doesn't remove the lv. Following is error record written in the oned.log: Mon Oct 29 00:30:57 2012 [ReM][D]: Req:3040 UID:0 ImageDelete result SUCCESS, 7 Mon Oct 29 00:30:57 2012 [ImG][D]: Message received: LOG I 7 rm: Removing localhost:/dev/-/- from the image repository Mon Oct 29 00:30:57 2012 [ImM][I]: rm: Removing localhost:/dev/-/- from the image repository Mon Oct 29 00:30:57 2012 [ImG][D]: Message received: LOG E 7 rm: Command sudo lvremove -f -/- failed: lvremove: invalid option -- '/' Mon Oct 29 00:30:57 2012 [ImM][E]: rm: Command sudo lvremove -f -/- failed: lvremove: invalid option -- '/' Mon Oct 29 00:30:57 2012 [ImG][D]: Message received: LOG I 7 Error during parsing of command line. Mon Oct 29 00:30:57 2012 [ImM][I]: Error during parsing of command line. Mon Oct 29 00:30:57 2012 [ImG][D]: Message received: LOG E 7 Error removing localhost:/dev/-/- Mon Oct 29 00:30:57 2012 [ImM][E]: Error removing localhost:/dev/-/- Mon Oct 29 00:30:57 2012 [ImG][D]: Message received: LOG I 7 ExitCode: 3 Mon Oct 29 00:30:57 2012 [ImM][I]: ExitCode: 3 Mon Oct 29 00:30:57 2012 [ImG][D]: Message received: RM FAILURE 7 Error removing localhost:/dev/-/- Mon Oct 29 00:30:57 2012 [ImM][E]: Error removing image from datastore. Manually remove image source - to completely delete the image: Error removing localhost:/dev/-/- *This problem has happened 3 times when I delete 6 images.* Oscar ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Jaime Melis Project Engineer OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | jme...@opennebula.org -- Jaime Melis Project Engineer OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | jme...@opennebula.org -- Jaime Melis Project Engineer OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | jme...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] ZFS datastore driver
Hi, I've created a first version of a datastore driver that support ZFS snapshots to enable instant cloning of a golden image. I've used the idea's from this blog: http://mperedim.wordpress.com/2010/09/26/opennebula-zfs-and-xen-%E2%80%93-part-2-instant-cloning/ The driver that is discussed in this article does not work with ONE 3.6 so I decided to update and rewrite it. I use this driver to allow instant cloning of large persistent images. I create a golden image, upload it to the datastore and create a golden snapshot. This golden snapshot is the basis for the clones that are created for this image. In my setup I use the ssh transfer driver to copy the images to the host after they are cloned. This also takes some time, but for performance reasons I prefer this above the shared driver. When the VM is stopped the image is transferred back to the ZFS server and stored in its own location. I think this driver will also function with the shared transfer driver, enabling almost instant startup of VMs, even with large disks. A few disclaimers: - I don't use this driver in production yet, and I would not advice anyone to do this :) - I'm not a developer, so please feel free to comment on my coding skills :) More info and the tar with the zfs-datastore driver are available below: http://rogierm.redbee.nl/blog/2012/11/08/opennebula-with-zfs-datastore/ Cheers, Rogier ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] VNC problem from Sunstone interface
YES! This was the issue ... There was set VNC_WSS="YES" for oneadmin user, I changed it to "NO", restarted sunstone and everything works. Thanks! By the way - I'm sure I didn't change this properties anytime - did it changed from ONE version 3.8? Jan Dňa 07.11.2012 21:43, Hector Sanjuan wrote / napísal(a): Somehow it is trying to connect with wss :S: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not found On sunstone, can you check your user properties (users tab - select user - update properties). In the user template, is there a VNC_WSS variable set? To what value? If so, can you delete it? Reload the sunstone page, logout, login and retry? Hector On Wed, 07 Nov 2012 10:09:31 +0100, Jan Benadik jan.bena...@atos.net wrote: Dňa 07.11.2012 08:18, Hector Sanjuan wrote / napísal(a): Any chance the "Use Secure WSS" is checked in sunstone config? Can you check/uncheck and retry with it unchecked just in case? Secure WSS wasn't checked, but I tried to check/uncheck and run once again with unchecked - nothing changed :-( Otherwise, kill your sunstone proxy and restart it manually: python /usr/share/opennebula/websockify/websocketproxy.py --target-config=/var/lib/one/sunstone_vnc_tokens 29876 1. sunstone stopped, occi stopped oneadmin@myto-node:~$ ps aux|grep py oneadmin 12456 0.0 0.0 9516 904 pts/2 S+ 09:56 0:00 grep py 2. oneadmin@myto-node:/etc/one$ python /usr/share/opennebula/websockify/websocketproxy.py --target-config=/var/lib/one/sunstone_vnc_tokens 29876 WebSocket server settings: - Listen on :29876 - Flash security policy server - No SSL/TLS support (no cert file) - proxying from :29876 to targets in /var/lib/one/sunstone_vnc_tokens oneadmin@myto-node:~$ ps aux|grep py oneadmin 12457 0.5 0.1 93056 16800 pts/1 S+ 09:57 0:00 python /usr/share/opennebula/websockify/websocketproxy.py --target-config=/var/lib/one/sunstone_vnc_tokens 29876 oneadmin 12460 0.0 0.0 9516 908 pts/2 S+ 09:57 0:00 grep py 3. oneadmin@myto-node:~$ sunstone-server start sunstone-server started oneadmin@myto-node:~$ ps aux|grep py oneadmin 12457 0.1 0.1 93056 16800 pts/1 S+ 09:57 0:00 python /usr/share/opennebula/websockify/websocketproxy.py --target-config=/var/lib/one/sunstone_vnc_tokens 29876 oneadmin 12481 0.9 0.0 0 0 pts/2 Z 09:58 0:00 [python] defunct oneadmin 12484 0.0 0.0 9516 908 pts/2 S+ 09:58 0:00 grep py Here seems to be an issue - if websockify process runs in time of sunstone is starting - python process is defunct. If a defunct python proces exist in system, VNC server is disconnected immediately and 10 lines is added to websockify console: oneadmin@myto-node:~$ python /usr/share/opennebula/websockify/websocketproxy.py --target-config=/var/lib/one/sunstone_vnc_tokens 29876 WebSocket server settings: - Listen on :29876 - Flash security policy server - No SSL/TLS support (no cert file) - proxying from :29876 to targets in /var/lib/one/sunstone_vnc_tokens 1: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not found 2: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not found 3: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not found 4: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not found 5: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not found 6: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not found 7: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not found 8: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not found 9: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not found 10: 10.0.1.125: SSL connection but '/var/lib/one/self.pem' not found In /etc/one/sunstone-server there is: :vnc_proxy_base_port: 29876 :vnc_proxy_path:
