looking for another thread. Really awesome work!
- Brian
@brianmmcclain
On Sunday, May 13, 2012 6:30:32 PM UTC-4, Dr Nic Williams wrote:
The full step-by-step for creating a postgres-only release is at
https://gist.github.com/2690511
Nic
------------------------------
Dr Nic Williams - VP Developer Evangelism
[image: Engine Yard]
The Leading Platform as a Service
Mobile: 415 860 2185
Skype: nicwilliams
Twitter: @drnic
------------------------------
On Sunday, May 13, 2012 at 2:45 PM, Dr Nic Williams wrote:
The quickest way to get some bits and pieces into a new release is to
take it from an existing release (perhaps someone wants to start a
catalogue system?). And the bosh release with the most goodies in it is
cf-release (Cloud Foundry).
I added an "extract" command to bosh-gen to pull out a job and all its
dependent packages from a target release.
For example, to create a new release and include the postgres job/packages:
$ cd /tmp
$ gerrit clone ssh://reviews.cloudfoundry.org:29418/cf-release
$ cd cf-release
$ bosh sync blobs
Syncing blobs...
… wait ages…
$ cd /path/to/releases
$ bosh-gen new newproject
$ cd newproject
$ bosh-gen extract /tmp/cf-release postgres
You can also quickly create an initial deployment manifest for a release,
deploy and thus trigger the package compilation:
$ bosh status
# get the bosh UUID
$ bosh-gen manifest example-dev . UUID
$ bosh deploy
There is a strong chance that compilation might fail if you haven't set
the correct properties in the manifest. Unfortunately I can't easily
extract what all the required/optional properties are from jobs at the
moment (I can look for <% .. %> but that's not 100%). Nor do most jobs
(any?) document what properties you can set for them. I might propose a
jobs/NAME/properties schema file in the future.
Nonetheless, "bosh-gen extract" and "bosh-gen manifest" are quite handy.
Nic
------------------------------
Dr Nic Williams - VP Developer Evangelism
[image: Engine Yard]
The Leading Platform as a Service
Mobile: 415 860 2185
Skype: nicwilliams
Twitter: @drnic
------------------------------
The full step-by-step for creating a postgres-only release is at
https://gist.github.com/2690511
Nic
------------------------------
Dr Nic Williams - VP Developer Evangelism
[image: Engine Yard]
The Leading Platform as a Service
Mobile: 415 860 2185
Skype: nicwilliams
Twitter: @drnic
------------------------------
On Sunday, May 13, 2012 at 2:45 PM, Dr Nic Williams wrote:
The quickest way to get some bits and pieces into a new release is to
take it from an existing release (perhaps someone wants to start a
catalogue system?). And the bosh release with the most goodies in it is
cf-release (Cloud Foundry).
I added an "extract" command to bosh-gen to pull out a job and all its
dependent packages from a target release.
For example, to create a new release and include the postgres job/packages:
$ cd /tmp
$ gerrit clone ssh://reviews.cloudfoundry.org:29418/cf-release
$ cd cf-release
$ bosh sync blobs
Syncing blobs...
… wait ages…
$ cd /path/to/releases
$ bosh-gen new newproject
$ cd newproject
$ bosh-gen extract /tmp/cf-release postgres
You can also quickly create an initial deployment manifest for a release,
deploy and thus trigger the package compilation:
$ bosh status
# get the bosh UUID
$ bosh-gen manifest example-dev . UUID
$ bosh deploy
There is a strong chance that compilation might fail if you haven't set
the correct properties in the manifest. Unfortunately I can't easily
extract what all the required/optional properties are from jobs at the
moment (I can look for <% .. %> but that's not 100%). Nor do most jobs
(any?) document what properties you can set for them. I might propose a
jobs/NAME/properties schema file in the future.
Nonetheless, "bosh-gen extract" and "bosh-gen manifest" are quite handy.
Nic
------------------------------
Dr Nic Williams - VP Developer Evangelism
[image: Engine Yard]
The Leading Platform as a Service
Mobile: 415 860 2185
Skype: nicwilliams
Twitter: @drnic
------------------------------
