[one-users] Opennebula 3.8 Resource rename

[Alberto Picón Couselo]

We have changed resources names (images, networks, clusters, templates) 
and datastores location correctly using a MySQL editor with opennebula 
stopped.

Thank you very much for your help,
Best Regards,
Alberto Picón

El 19/02/2013 14:51, Carlos Martín Sánchez escribió:
> All the information is read from the DB, so yes, it's possible to 
> change anything you want.
> But there are lots of connections between different resources. For 
> example a VM stores in its xml body not only the host id, but also the 
> hostname, VMM driver...
>
> I wouldn't edit the DB, but if you do, make sure you keep a backup and 
> use onedb fsck tool [1] to fix *some* inconsistencies.
>
> I wonder why do you need to change the IDs, is it something we should 
> support for some reason?
>
> Regards
>
> [1] http://opennebula.org/documentation:rel3.8:onedb
> --
> Carlos Martín, MSc
> Project Engineer
> OpenNebula - The Open-source Solution for Data Center Virtualization
> www.OpenNebula.org <http://www.OpenNebula.org> | 
> cmartin at opennebula.org <mailto:cmartin at opennebula.org> | @OpenNebula 
> <http://twitter.com/opennebula>
>
>
> On Tue, Feb 19, 2013 at 2:25 PM, Vassilis Vatikiotis 
> <vatikiot at iit.demokritos.gr <mailto:vatikiot at iit.demokritos.gr>> wrote:
>
>     Hello,
>
>     regarding your answer, is it possible to also change, in the DB,
>     resources IDs? Of course, within the DB, the IDs have to be consistent
>     so that relationships do not break. Assuming that DB consistency is
>     maintained, would this be possilbe?
>
>     On Tue, Feb 19, 2013 at 2:30 PM, Carlos Martín Sánchez
>     <cmartin at opennebula.org <mailto:cmartin at opennebula.org>> wrote:
>     > Did you stop opennebula before touching the DB?
>     > Otherwise, you will get the list output from the DB, and the
>     individual info
>     > from the cache. This cached information will eventually replace
>     the data in
>     > the DB.
>     >
>     > Regards
>     > --
>     > Carlos Martín, MSc
>     > Project Engineer
>     > OpenNebula - The Open-source Solution for Data Center Virtualization
>     > www.OpenNebula.org <http://www.OpenNebula.org> |
>     cmartin at opennebula.org <mailto:cmartin at opennebula.org> | @OpenNebula
>     >
>     >
>     > On Tue, Feb 19, 2013 at 12:27 PM, Alberto Picón Couselo
>     <alpicon1 at gmail.com <mailto:alpicon1 at gmail.com>>
>     > wrote:
>     >>
>     >> Hi, there.
>     >>
>     >> We would like to change names of resources, for instance, image
>     names
>     >> or cluster names.
>     >>
>     >> For example, we have changed image name information directly in
>     MySQL
>     >> database, changing NAME column and BODY column from image_pool
>     table.
>     >> However, SunStone shows the changes partially. Image data seems
>     to be
>     >> changed in row view, but when we click over it, image details shows
>     >> older information.
>     >>
>     >> We have similar results if we try to change image datastore
>     >> information. We need to change an image from one datastore to
>     another
>     >> without reregistering it. If we change image_pool, datastore
>     >> information, SOURCE, DATASTORE_ID, DATASTORE, tags, Sunstone
>     updates
>     >> the information partially...
>     >>
>     >> Please, can you give us any clue to rename resources?
>     >>
>     >> Best Regards,
>     >> Alberto Picón
>     >> _______________________________________________
>     >> Users mailing list
>     >> Users at lists.opennebula.org <mailto:Users at lists.opennebula.org>
>     >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>     >
>     >
>     >
>     > _______________________________________________
>     > Users mailing list
>     > Users at lists.opennebula.org <mailto:Users at lists.opennebula.org>
>     > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>     >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130220/67037c48/attachment.htm>