[one-users] "onevm saveas" compromised one.db

Duverne, Cyrille cyrille.duverne at euranova.eu
Fri Sep 14 06:44:26 PDT 2012


Hello,

Thanks Carlos, I'll keep you posted of the result :)

Regards
Cyrille

Vendredi 14/09/2012 à 15:22 Carlos Martín Sánchez a écrit:

Hi,

I have just realized that you are going to upgrade from the ubuntu
repository packages to the package distributed by us.
The main difference is that your opennebula is installed from
different sub packages, and our package includes everything in one
deb.

I'm not sure if apt will find any conflicts, you may need to uninstall
& install the new one...

To be absolutely sure that you will be able to recover your current
installation, backup the whole /var/lib/one, /etc/one and one_auth
files.

The rest of the procedure is as you describe. And yes, all users,
templates, vnets are preserved.

Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center
Virtualizationwww.OpenNebula.org [1] | cmartin at opennebula.org |
@OpenNebula [2] [3]

On Fri, Sep 14, 2012 at 11:44 AM, Duverne, Cyrille  wrote:

 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 symbolic links
issues)
9/ Launch Sunstone etc...

My images will still be present, so will be my templates etc... ?

Thanks in advance
Cyrille

Vendredi 14/09/2012 à 11:40 Carlos Martín Sánchez a écrit:

 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
OpenNebula - The Open-source Solution for Data Center
Virtualizationwww.OpenNebula.org [1] | cmartin at opennebula.org |
@OpenNebula [2] [3]

On Thu, Sep 13, 2012 at 5:59 PM, Duverne, Cyrille  wrote:

 Hello Carlos,

Thanks a lot,

If I understood well the upgrade guide, I have to go from 3.2 to 3.4
and to 3.4 to 3.6 ?
If so, I read that I have to shutdown or delete all active VMs, should
I just stop them ?

Thanks in advance
Cyrille

Lundi 10/09/2012 à 12:36 Carlos Martín Sánchez a écrit:

 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
Virtualizationwww.OpenNebula.org [1] | cmartin at opennebula.org |
@OpenNebula [2] [3]

On Fri, Sep 7, 2012 at 8:38 AM, Duverne, Cyrille  wrote:

 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 : http://blog.cduverne.com
Twitter : @CydsWorld

"Imagination is more important than Knowledge"
Albert Einstein

Mercredi 05/09/2012 à 12:34 Carlos Martín Sánchez a écrit:

 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 Open-source Solution for Data Center Virtualization
www.OpenNebula.org [1] | cmartin at opennebula.org | @OpenNebula [2] [3]

On Tue, Sep 4, 2012 at 5:55 PM, Duverne, Cyrille  wrote:

 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 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 should always have the same  outcome.

Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open-source Solution for Data Center
Virtualizationwww.OpenNebula.org [1] | cmartin at opennebula.org |
@OpenNebula [2] [3]

On Mon, Aug 27, 2012 at 10:10 AM, Duverne, Cyrille  wrote:

 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 the VM
6/ I created a new VM using this new image
7/ modified it again
8/ Launched a "onevm saveas" with the same image name and the command
passed
9/ I found 2 images with the same name (different ownership) 
10/ The 2nd image has never been ready.
11/ I removed the most recent image
12/ The remaining image is compromised and can't be found on the disk
because pointing to a file that has been deleted in the process.

I know that a saveas command is available on sunstone but I'd like to
test the consistence between actions done via oneadmin in the CLI and
on Sunstone.

Have you ever experienced this ?

_______________________________________________
Users mailing list
Users at lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org



Links:
------
[1] http://www.OpenNebula.org
[2] http://twitter.com/opennebula
[3] mailto:cmartin at opennebula.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120914/9ced4906/attachment-0002.htm>


More information about the Users mailing list