Michael,
Good job thinking through that problem. What vcld does to deal with
it is to add some lines to rc.local that will parse the private IP,
update what is in sshd_config, and restart sshd on the private
interface.
Josh
On Thu, Jun 21, 2012 at 6:19 PM, Michael Jinks wrote:
> We're still tr
Hello all,
I looked around a little bit but didn't see any documentation on how to delete
images (and their associated files).
Through all of my testing I've wound up creating quite a few images and I'd
like to clean things up before continuing.
What I have been able to do is this:
In VCL:
In
Hi Adam,
You're correct that VCL does not delete the original VMDK source image
files.
Regards,
Mike
--
*Mike Haudenschild*
Education Systems Manager
Longsight Group
(740) 599-5005 x809
m...@longsight.com
www.longsight.com
On Fri, Jun 22, 2012 at 1:46 PM, Hechler, Adam wrote:
> Hello all,**
Mike,
So is it safe to just delete them? What about the records in the database? Can
I delete the associated records in the image and imagerevision tables?
Adam
From: Mike Haudenschild [mailto:m...@longsight.com]
Sent: Friday, June 22, 2012 2:28 PM
To: vcl-user@incubator.apache.org
Subject: Re
Hi Adam,
If you're 100% positive you'll never use the image again, go ahead and
delete the VMDK files from the repo. Depending upon your VM Host config,
the VMDKs may have been copied from the repo into working local directories
on your ESXi boxes, as well.
I'd hesitate to delete from the databa