Skip to content

Instantly share code, notes, and snippets.

@jriguera

jriguera/bosh_release.md

Last active March 8, 2016 12:29
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jriguera/610fb7c18baab7446cbf to your computer and use it in GitHub Desktop.
Save jriguera/610fb7c18baab7446cbf to your computer and use it in GitHub Desktop.
Download ZIP
Creating bosh releases
Raw
bosh_release.md

Start here: http://mariash.github.io/learn-bosh/, then goto: http://bosh.io/docs/create-release.html

  1. Prepare the environment with bosh lite.
  2. Create the workspace for the new release: bosh init release <release_name>
  3. Create the source packages to compile: bosh generate package <package_name>
  4. After defining the compilation steps, add the source packages bosh add blob <package.tgz> <package_name>
  5. Create the job (or jobs) to run: bosh generate job <job_name> and write the monit, spec and startup files
  6. Create a manifest for the new project: http://bosh.io/docs/deployment-manifest.html, using cd templates && make_manifest warden. Option: copy from another simple release like: https://github.com/cloudfoundry-community/carbon-c-relay-boshrelease
  7. bosh status has to be pointing to the deployment manifest created before.
  8. bosh create release --force && bosh upload release && bosh deploy
  9. Errors?, bosh task N --debug where N is the director task number.
  10. If job did not start or you want to see how it works, ssh to the container with: bosh ssh --strict_host_key_checking no
  11. Inside the vm/container go to /var/vcap/jobs/JOB/. To see monit status: sudo /var/vcap/bosh/bin/monit status. Logs, pids, should be in /var/vcap/sys

Once everything is done, create the release wihout --force and upload to S3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment