-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bill,
It sounds like it thinks it has copied over the files but somehow hasn't successfully done so. Can you send the contents of vcld.log for a reservation that fails? To get just the contents for a single reservation, you can find the request id either on the Reservations page (if you have the "view debug information" additional user permission) or on the dashboard. Then, run grep <request id> /var/log/vcld.log on the management node, replacing <request id> with the actual id. We can then have a look through the log to see if we can help more. Josh On Wednesday, July 20, 2016 1:35:23 PM Doran, William wrote: > Thanks Josh. That seemed to work. I can see the old images in the new VCL > installation. However, when launching an image, it fails. The logs > indicate that the VM is unable to be started (the VMHost is ESXi5.5). Upon > further investigation, I see that files are copied into the VMWorkingPath, > however, they seem to be very small (for example, the delta.vmdk in only a > few thousand bytes. When I look in the dirs for the former vcl > installation, I see that they are several GBs. Any ideas or > recommendations on what to check? > > Thanks! > -Bill > > -----Original Message----- > From: Josh Thompson [mailto:[email protected]] > Sent: Monday, June 27, 2016 4:00 PM > To: [email protected] > Subject: Re: transferring vcl images to another vcl system > > - gpg control packet > William, > > To import the images, you'll need to do some database work. The following > instructions assume you haven't already created any images in the new > system. You'll encounter some problems with the image.id and > imagerevision.id if you have already created some images (these are > embedded in the actual image disk files). Backup the new system's database > before doing this. > > 1) dump these tables from the old system: image, imagemeta, imagerevision > 2) import those dumps into the new system (you'll probably need to delete > the noimage entry either from the new system or from the dumps so that you > don't get a conflict) 3) on the VCL site, create an image group you will > put all of them in (I'll call it "Imported Images") 4) create records in > the resource table: > INSERT INTO resource (resourcetypeid, subid) SELECT 13, id FROM image; > 5) add all of them to the image group: > INSERT INTO resourcegroupmemebers (resourceid, resourcegroupid) SELECT > resource.id, resourcegroup.id FROM resource, resourcegroup WHERE > resource.resourcetypeid = 13 AND resource.subid != (SELECT id FROM image > WHERE name = 'noimage') AND resourcegroup.name = 'Imported Images' AND > resourcegroup.resourcetypeid = 13 6) You should now see all of the images > on the VCL site (possibly after logging out/back in), assuming your use > account has access to the image group created in #3 > > Let us know how it works out for you. > > Josh > > On Monday, June 27, 2016 1:51:41 PM Doran, William wrote: > > Hello, > > I currently admin a running/working VCL installation using v2.3.2, and > > am > > > working on bringing up a completely new installation using the latest > > stable release. Is there an easy way to transfer the existing VCL > > images > > > from the running/working 2.3.2 installation to the new installation? > > Any > > > pointers on where to start with this would be greatly appreciated! > > > > Thanks in advance! > > -- > ------------------------------- > Josh Thompson > VCL Developer > North Carolina State University > > my GPG/PGP key can be found at pgp.mit.edu > > All electronic mail messages in connection with State business which are > sent to or received by this account are subject to the NC Public Records > Law and may be disclosed to third parties. - -- - ------------------------------- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAleSTh4ACgkQV/LQcNdtPQNkYQCfUKZSiLguasWM7ivxTUeTrWoJ n9UAnjLtY+e1h1O475hofKQfTyA97JlH =+Lbu -----END PGP SIGNATURE-----
