Creating our own cf-release

[Nicholas Terry]

So we are trying to create our own release, but we ultimately don't want to host the public blobs, just our own custom blobs. Is there a way to be able to create a release that gets the upstream cf-release blobs, but also allows us to get our own blobs from our own blobstore?

[Dr Nic Williams]

Currently there isn't.

Is the hosting of the 1G+ of blobs a substantial burden? Or is the feature request a "nice thing to have"?

Nic

On Wed, Jan 2, 2013 at 4:01 PM, Nicholas Terry <nick.i...@gmail.com> wrote:

So we are trying to create our own release, but we ultimately don't want to host the public blobs, just our own custom blobs. Is there a way to be able to create a release that gets the upstream cf-release blobs, but also allows us to get our own blobs from our own blobstore?

--

Dr Nic Williams

http://drnicwilliams.com

cell +1 (415) 860-2185

[Nicholas Terry]

Its just, we are having issues recreating the blobs.yml for our s3 bucket. The items are uploaded, but we dont have a mapping of blob id to filename. and we dont want to have to manually create it every time.

[Dr Nic Williams]

I've not been following 100% the process you're going through to recreate cf-release.

Perhaps try bosh-gen, which includes the ability to sync blobs from one release to another.

bosh-gen new my-cf-release

cd my-cf-release

bosh-gen extract-job /path/to/cf-release/jobs/cloud_controller

bosh-gen extract-job /path/to/cf-release/jobs/nats

bosh upload blobs

etc

Let me know how that goes for you. If it doesn't work, I'll make it work :)

Nic

[Martin Englund]

Nick,

what you want is composite releases, where you can do a deployment
using two different releases, i.e. the public cf-release & your own
private release.

Just update your deployment manifest from:

release:
name: your-release
version: x

to:

releases:
- name: cf-release
version: latest
- name: your-release
version: x

/M

--
cheers,
/Martin
--
Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
"The question is not if you are paranoid, it is if you are paranoid enough."

[Dr Nic Williams]

Martin, does it fail gracefully if both releases have a "cloud_controller" job or will it randomly pick one or pick on from the first release in the list?

Nic

[Martin Englund]

It'll take the first cloud_controller found in the order you defined
the releases (releases is an array)

/M

[Nicholas Terry]

AWESOME!!!! A composite release seems like EXACTLY what i need!!!!

[Dr Nic Williams]

We have an happy customer!! :)

[Joseph Noall]

Martin,

Can this still work if a package or job in the first release has a dependency on a package from the second release?  Or does that prevent you from being able to create the releases?

On Thursday, January 3, 2013 1:45:46 AM UTC-7, Martin Englund wrote:

[Martin Englund]

bosh create release will fail if you have unresolvable dependencies

/M

[Dr Nic Williams]

Martin, if 

* cf-release has a package "dea_ruby19" (v10), and a job "cloud_controller" and

*  mypersonal-release has a package dea_ruby19 (v2), and a job "my_cloud_controller"

Will the bosh agent job spec know to get the correct blob for the correct release?

If the two jobs are run on the same VM via colocation, then will both /var/vcap/data/packages/10/dea_ruby  and /var/vcap/data/packages/2/dea_ruby be installed? Which one will /var/vcap/packages/dea_ruby symlink to?

Nic

[Martin Englund]

Ask Oleg ;)

I'll have to check the source...

/M

[Nicholas Terry]

So I get the following error when deploying:

Error 140001: Cannot tell what release job `debian_nfs_server' supposed to use, please reference an existing release 

I have two releases, cf-release and my own release (called fs-appcloud). fs-appcloud does not have the debian_nfs-server job in it, and the cf-release does. What am I missing? Do I need to add an item to the job definition in my deployment manifest?

[Oleg Shaldybin]

It's currently not possible to collocate jobs from different releases.

--
Best,
Oleg

[Dr Nic Williams]

Thx Oleg. I don't think its a big ask to say "put your own release on your own VM" :)