Re: Upgrade Bosh Director
Brandon Hudlemeyer
I haven't seen any documentation on the actual upgrade process. What I have
always done is just update the bosh manifest with the newest information and done a re-deploy like you would if you were updating stemcells being used by other deployments.I have only done this using bosh-init so far I have not tried it with bosh v2 and create-env. I also use the command in the same directory the bosh-state.json file is housed in (not sure this is a requirement but paranoid). update lines in bosh manifest to newest versions: - name: bosh url: https://bosh.io/d/github.com/cloudfoundry/bosh?v=262.1 sha1: c2aaffdb3a9b6ddf2a05d2a865e81e4186741675 - name: bosh-vsphere-cpi url: https://bosh.io/d/github.com/cloudfoundry-incubator/bosh-vsphere-cpi-release?v=41 sha1: 648ba9921739d30763063c80ad7a280e6410a1b6 resource_pools: stemcell: url: https://bosh.io/d/stemcells/bosh-vsphere-esxi-ubuntu-trusty-go_agent?v=3421.9 sha1: f5de77161ee2cc4014cde055c845f7b1cfc9f005 Then: bosh-init deploy bosh.yml (again havent used bosh v2 and create-env for this yet but would be same process basically I believe). On Fri, Jun 30, 2017 at 7:53 AM nitin padalia <padalia.nitin(a)gmail.com> wrote: Hi, |
|