Hi,
You can install 3.6 directly, and the upgrade process will upgrade
automatically to 3.4 and then 3.6.
The 3.4 brought a lot of storage backend changes, and the upgrade requires
to shutdown or delete all your VMs; they cannot be stopped.
Regards
--
Carlos Martín, MSc
Project Engineer
Hello Carlos,
To be completely clear :
1/ Download 3..6 installation package
2/ DELETE all VMs.
3/ Stop Sunstone etc
4/ Backup DB Config and /etc/one
5/ Installation of 3.6
6/ Update 3.6 config files with previous parameters
7/ Update DB
8/ Copy images etc... to their new location (to avoid
Hi,
Datastores were introduced in 3.4. Unless there is a good reason not to,
I'd suggest you to upgrade to the latest 3.6 version.
Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center Virtualization
www.OpenNebula.org | cmar...@opennebula.org |
Hello Carlos,
As you might have read it, i'm using ONE 3.2 packaged in Ubuntu 12.04.
onedatastore show isn't a supported command of this version... Or at
least I get a command not found
How could I retrieve this info from ?
Regards
CyD
Thanks in advance.
Cyrille
Cyrille Duverne
Blog :
Hi,
What I need to know are the DS_MAD and TM_MAD datastore drivers for the
system Datastore 0, and the Datastore where the images are registered (I
guess 'default', 1). You can get them using the 'onedatastore show' command.
Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The
Hi,
I can't reproduce this behaviour.
I'm using the drivers -,shared for the system datastore; and fs,shared for
the default datastore. What drivers are you using? Are your images
persistent?
About the CLI-Sunstone commands consistency, both end calling the ruby OCA
and then the core, so they
Hello Carlos,
Thanks for your quick answer.
I'm using KVM and my images are only clones...
Regards
Cyrille
Mardi 04/09/2012 à 15:14 Carlos Martín Sánchez a écrit:
Hi,
I can't reproduce this behaviour.
I'm using the drivers -,shared for the system datastore; and fs,shared
for the default
Hello All,
I've faced a strange behaviour with Sunstone.
1/ I created a VM using Sunstone
2/ I modified the VM to be consistent with my new config
3/ I launched a onevm saveas directly from the Hypervisor
4/ I chmoded the image dor my current user
5/ The new image was ready after a shutdown of
