Re: Problem for Chaos Lemur
Hi Paul, thank you for your quick response. I added the VSPHERE_HOST settings but it failed to restart. Refer to attached screenshot ' configuration.png '. Also I attached the log file 'restart.log'.toggle quoted messageShow quoted text
It seems to be a connect issue but I tried to connect the VSPHERE host via vSphere client with the below information:
And it can connect to the host successfully. Any help will be appreciated.
From: cf-dev-bounces(a)lists.cloudfoundry.org [mailto:cf-dev-bounces(a)lists.cloudfoundry.org] On Behalf Of Paul Harris
Sent: Saturday, May 16, 2015 12:57 AM
Subject: Re: [cf-dev] Problem for Chaos Lemur
DRYRUN mode does everything the same as normal operation *except* for the actual deletion, so if Chaos Lemur is reporting unexpected names it's a problem with some other part of your config, not DRYRUN. From your environment variables it seems you haven't configured it to access your underlying infrastructure, either AWS or VSphere. You need to provide credentials for one of those:
AWS_ACCESSKEYID & AWS_SECRETACCESSKEY, or
VSPHERE_HOST & VSPHERE_PASSWORD & VSPHERE_USERNAME
Give that a go and it should work, but be aware that if DRYRUN is not true then you will lose VMs!
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Problem-for-Chaos-Lemur-tp90p96.html
Sent from the CF Dev mailing list archive at Nabble.com.
cf-dev mailing list