Problem for Chaos Lemur


stephen
 

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'.

It seems to be a connect issue but I tried to connect the VSPHERE host via vSphere client with the below information:
VSPHERE_HOST: 10.32.70.119
VSPHERE_PASSWORD: Password
VSPHERE_USERNAME: root

And it can connect to the host successfully. Any help will be appreciated.

-----Original Message-----
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
To: cf-dev(a)lists.cloudfoundry.org
Subject: Re: [cf-dev] Problem for Chaos Lemur

Hi Stephen,

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[1] 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!

Cheers, Paul

[1]: https://github.com/pivotal-cf/chaos-lemur#environment-variables



--
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
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


Paul Harris
 

Hi Stephen,

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[1] 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!

Cheers, Paul

[1]: https://github.com/pivotal-cf/chaos-lemur#environment-variables



--
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.


stephen
 

Hi guys,

I am trying to use the tool Chaos Lemur to do HA test for CF. I got the guide from below link: http://blog.pivotal.io/cloud-foundry-pivotal/products/chaos-lemur-testing-high-availability-on-pivotal-cloud-foundry

My problem is:
Chaos Lemur seems always running in ‘DRYRUN’ mode(which means it does not destroy VMs actually). Below is the log(get from command: cf logs chaos-lemur):

2015-05-13T14:40:00.00+0800 [App/0] OUT [CHAOS LEMUR] INFO f3a09be7-8bc4-4bed-94dc-32f1a3a653f6 Beginning run...
2015-05-13T14:40:00.00+0800 [App/0] OUT [CHAOS LEMUR] INFO f3a09be7-8bc4-4bed-94dc-32f1a3a653f6 Destroyed: [id: id-3, deployment: deployment-3, job: job-3, name: name-3]
2015-05-13T14:40:00.00+0800 [App/0] OUT [CHAOS LEMUR] INFO f3a09be7-8bc4-4bed-94dc-32f1a3a653f6 Destroyed: [id: id-2, deployment: deployment-2, job: job-2, name: name-2]
2015-05-13T14:40:00.00+0800 [App/0] OUT [CHAOS LEMUR] INFO Chaos Lemur Destruction (f3a09be7-8bc4-4bed-94dc-32f1a3a653f6):
2015-05-13T14:40:00.00+0800 [App/0] OUT 2 VMs destroyed:
2015-05-13T14:40:00.00+0800 [App/0] OUT * name-2
2015-05-13T14:40:00.00+0800 [App/0] OUT * name-3

It seems that the tool is running in ‘DRYRUN’ mode because the destroyed ‘id’, ‘deployment’ and ‘job’ seems not be real names. My question is: I already set the environment variable ‘DRYRUN’ as false(also tried not set this variable). Do you have any idea?

Below are my environment variable setting:
User-Provided:
DIRECTOR_HOST: x.x.x.x
DIRECTOR_PASSWORD: admin
DIRECTOR_USERNAME: admin
DRYRUN: false
SCHEDULE: 0 0/5 * * * *
swift-dev_PROBABILITY: 0.5
swift_storage_PROBABILITY: 0.5

‘swift-dev’ is a deployment name and ‘swift_storage’ is a job name under previous deployment. I got the deployment and job from command: bosh vms. It will list all the deployments and their jobs. Is there any problems with my settings? I think if it is because that I do not get the correct ‘deployment’ and ‘job’?



Any help will be highly appreciated!



Stephen Zhou (周红星)
Mobile: +86 13683173521
Email: stephen.zhou(a)emc.com<mailto:Xu_Louie(a)emc.com>