BOSH Release / Re-using package dependencies


Sylvain Gibier
 

Hi,

Cf-release has a submodule src/capi-release release, and symlink the package and jobs into cf-release.
I'm trying to accomplish something similar with one of my custom BOSH release, but every time I tried to build the release, it complains for not finding the package's blobs.

Any steps ? Approach to do something similar ? My aim is to provide BOSH release overlay, instead of cloning a given BOSH release just to add a new job for instance.

Cheers,

Sylvain


James Hunt <james@...>
 

On Mon, Oct 17, 2016 at 12:17:58PM -0000, Sylvain Gibier wrote:
Hi,

Cf-release has a submodule src/capi-release release, and symlink the package and jobs into cf-release.
I'm trying to accomplish something similar with one of my custom BOSH release, but every time I tried to build the release, it complains for not finding the package's blobs.

Any steps ? Approach to do something similar ? My aim is to provide BOSH release overlay, instead of cloning a given BOSH release just to add a new job for instance.
Do you actually need to include the upstream BOSH release in your
BOSH release? You can co-locate multiple releases in a single
deployment, if you just need to build "add-on" functionality...

--
James Hunt
@iamjameshunt
https://www.jameshunt.us


Amit Kumar Gupta
 

Hey Sylvain,

I would second James's question. cf-release submodules other releases for
historical reasons. We're moving to shipping a manifest that simply
composes multiple releases [cf-deployment
<https://github.com/cloudfoundry/cf-deployment/blob/9788d5904739af50adef614bc9690d10a28849d1/cf-deployment.yml#L1245-L1293>],
but we are supporting the existing "monolith release" workflow for the time
being until we're fully ready to ship the newer solution. Are you sure you
really need to submodule other releases?

[cf-deployment]
https://github.com/cloudfoundry/cf-deployment/blob/9788d5904739af50adef614bc9690d10a28849d1/cf-deployment.yml#L1245-L1293

Best,
Amit

On Mon, Oct 17, 2016 at 6:12 AM, James Hunt <james(a)jameshunt.us> wrote:

On Mon, Oct 17, 2016 at 12:17:58PM -0000, Sylvain Gibier wrote:
Hi,

Cf-release has a submodule src/capi-release release, and symlink the
package and jobs into cf-release.
I'm trying to accomplish something similar with one of my custom BOSH
release, but every time I tried to build the release, it complains for not
finding the package's blobs.

Any steps ? Approach to do something similar ? My aim is to provide BOSH
release overlay, instead of cloning a given BOSH release just to add a new
job for instance.

Do you actually need to include the upstream BOSH release in your
BOSH release? You can co-locate multiple releases in a single
deployment, if you just need to build "add-on" functionality...

--
James Hunt
@iamjameshunt
https://www.jameshunt.us