Great job BOSH team 👏🏻

Mounika, Forgot password is a functionality which can be implemented in different ways. On backend it will use change password API call to make the changes. Thanks

Hi Mounika, Try this http://docs.cloudfoundry.org/api/uaa/version/4.19.0/index.html#change-user-password Thanks Ronak

Hi, As the error says compilation block in missing in manifest. Add compilation block and redeploy. Thanks Ronak

Hemant, Unless there is a shared configuration which changes when you add a new instance, Bosh will not trigger deploy on your remaining instances. Can you paste your manifest here (masking secrets)?

Hi Arpit, That operation require director should be able to talk to the internet, if not you can download stemcell on your local system and then upload using the tarball. Thanks Ronak ᐧ wrote:

Hi Diego , you can try a something which helped me 1. Do bosh upload stemcell 2. While uploading and when getting stuck at 96% , open a new terminal and login into vagrant vm with vagrant ssh & do mon

Hi Alexander, This mailing list is for OSS issues , you can redirect your query to pivotal support. Thanks Ronak alexander.widak(a)deltatree.de> wrote:

Hi Lukas , Not that one 😅 This one https://en.wikipedia.org/wiki/Control_knob

Stanley , For now you can also turn few knobs on bosh health monitor 1. Increase agent poll timeout <http://bosh.io/jobs/health_monitor?source=github.com/cloudfoundry/bosh&version=257.9#p=hm.intervals

Hi Sundar, If you are referring to cf release jobs than they already have drain scripts which take care of clean shutdown and restart . so if you have sufficient amount of instances running , to keep

Hi Sankeerth, check for the missing properties in global property block, check if below properties exists in your intermediate manifest or not. properties: cc: external_port: ?? ( you can add this por

Hi Nishant , You can explore "alias" feature of bosh cli, so if you have 2 deployment diego & cf what you can do is Create alias for each deployment : bosh alias diego "deployment $HOME/cfv2/diego-rel

Ramon can you check the know_hosts file in .ssh dir of your home dir . -- View this message in context: http://cf-bosh.70367.x6.nabble.com/cf-bosh-Offending-RSA-key-when-we-do-bosh-ssh-tp1284p1297.htm

Hi Ramon, Are you able to locate your .bosh directory ?? Usually it is created in same directory where .bosh_config file is created. config path for .bosh_config should be there on output of bosh stat

Remove the old key using : ssh-keygen -f "/home/vcap/.bosh/tmp/ 9ca7fd9f-dcf5-4739-98de-b4f4f607ad28_known_hosts" -R 172.21.28.17 and then try again with "bosh ssh --strict_host_key_checking no" wrote

Hi Rahul, /info endpoint is failing so the issue can be on cloud controller or routers or load balancer. If you are using HAproxy as load balancer then bosh ssh into haproxy and check if it is failing

Hi Animesh , You can specify different availability_zone property with two different resource pool and deploy cc's to these resource pool. Thanks Ronak

Hello , We are open sourcing one of our bosh release : Dotfile bosh release https://github.com/rakutentech/dotfiles-boshrelease Inspired by cloudfoundry-community/root-env-boshrelease, dotfiles-boshre

Hello, I Agree that it will be helpful for Openstack deployments but having something like this in CPI will only be helpful when native Openstack LBaaS api are used . For custom ELB deployments it wil