Hi Jo, We have a sample windows bosh release here: https://github.com/cloudfoundry-incubator/sample-windows-bosh-release We're also planning on writing some reference docs about this, so whatever

Thanks Nic, your early feedback on that note was helpful, keep it coming if you have more! wrote:

Amit, this doc has been awesomely helpful to me over the last week or so. I've been steadily upgrading bosh releases. I like them & the deployment manifests a lot

Hi all, "BOSH Links" is a feature which simplifies how data is shared between BOSH-deployed jobs that need to collaborate with one another (e.g. a web server and its backing database). Like many BOSH

We didnt yet publish cpi release with AWS v2 integration (includes ALBs). You are welcome to build a local copy (bosh create release --with-tarball) from

Instead of `lbtargetgroups`, try `lb_target_groups` - the markup formatting on the bosh.io docs page is rendering poorly. Danny -- Danny Berger

Hi, In my cloud config descriptor in the vm_types section I have specified that I want the created via bosh deployment VM instances to be added to a specific load balancer target group using the

We have been using bosh for some time with Ubuntu stemcells on vSphere. We have recently setup Diego cells on Windows using Windows stemcell. Is this the only thing that can be deployed on Windows

Correction: I didn't mean manifest templates, I meant job templates of the installed releases, which are .erb templates, even for releases written in different languages. See e.g. something like

Hi Lynn, The ruby dependencies are necessary for bosh-init, because it renders manifest templates with ruby. See

bosh-init (or the new bosh2 cli's create-env command) will download some yet-to-be-compiled modules called CPIs. Some CPIs are written in Ruby - the ruby itself is also downloaded automatically and

All, I am on the page http://bosh.io/docs/install-bosh-init.html and am wondering what's purpose for this section ? Is this for ruby2? Depending on your platform install following packages: Ubuntu

Thanks ! Good to know. wrote:

We can consider cloudfoundry-community as a contributor, sure! ;-) Technically the Foundation doesn't actually own that GH org, but we love what's happening there! wrote: Chip Childers CTO, Cloud

Chip, When you means "this project", are you including cloudfoundry-community ? of just cloudfoundry repository ? Thanks Gwenn wrote:

Just to chip in, we've helped folks consume updates for their CF deployments that averaged out at a new *thing* (stemcell, release) every 4 days. Having your entire platform pipelined with something

pivotal deploys updated stemcells regularly to PWS. high and critical CVEs have a 48hr goal. we catch up on lows and mediums generally approximately once per month. wrote: -- Thank you, James

Hi, before deploying/upgrading a stemcell in production our security group runs vulnerability scans on our staging deployments. The problem is that by the time we get the stemcell into staging (about

If your deployment have zone1 and zone 2 jobs, the best, safest and easiest way to achieve this is to remove Z2 job in manifest and perform deploy in old bosh. Deploy Z2 job in new bosh. Repeat this

Thanks a lot for the answer, and yes the pain points are those ones... Those are normally not pain points for someone who has already deployed CF for a long time... But for new comers they are quite