Deploying cloud foundry with BOSH - what does a “bosh delete deployment” clean up?

[Cornelia Davis]

We've just gone through the process of deploying a multi node (34 nodes) cloud foundry using BOSH, with a few hiccups along the way. One in particular was that it took us several "bosh deploy" runs to get through the initial compilation steps. We'd start the bosh deploy, it would start compiling, get through a few components and then fail. There is no doubt that we have some configuration issues with our VMWare based infrastructure and I suspect we are running out of resources. But here is my main question for now.

We were able to get through the compiles by issuing a "bosh delete deployment ourcloud --force" after a failure.

What does this command clear out? It obviously left successfully compiled stuff in place, but what is cleaned? Temporary storage? Anything else?

 

(Cross-posted on stackoverflow)

[Dr Nic Williams]

I also have had the experience when deploying cf-release for the first time. I think I've created a Jira ticket for it.

I don't think it's a resource limit issue - you'd see that error (max of 20 VMs reached; or similar). 

It's really hard to debug without modifying bosh source because the compilation VMs are deleted just at the moment you learn that something is wrong.

Cheers
Nic

Dr Nic Williams
Mobile: +1 415 860 2185
Skype: nicwilliams
Twitter: @drnic

[Dr Nic Williams]

Cornelia, update: I've got a microBOSH based on HEAD and for both stemcell 0.6.4 & 0.6.7 I am no longer getting any timed out errors during compilation of cf-release. Perhaps upgrade your BOSH and see if you see the same improvement?

Nic

--

Dr Nic Williams

http://drnicwilliams.com

cell +1 (415) 860-2185

[daniel....@gmail.com]

OK I was about to post something related, so here's what I know (which isn't much!):
stemcells and releases are not deleted from bosh, only detached from the deployment.
each VM for jobs are deleted.
The properties in your manifest are deleted from the director.

So compiled packages, stemcells, and releases are stored in BOSH.  I wonder how to reset BOSH without destroying / deploying BOSH?

[Dr Nic Williams]

To list stemcells & delete each one:

bosh stemcells

bosh delete stemcell <name> <version>

To list releases and delete each one:

bosh releases

bosh delete release <name>

So you might run:

bosh delete stemcell bosh-stemcell 0.6.7

bosh delete release appcloud

[daniel....@gmail.com]

Thanks,
I was thinking of not being able to delete compiled packages, or getting into some sort of error state.

Also, just now I have come into a problem with deleting a deployment and the only way I know of fixing it is to delete my microBOSH and start again.  See here

[Dr Nic Williams]

Ooh try adding --force to your "delete deployment" command.