deploying to bosh-lite could be easier

[shalako]

Other bosh releases provide a make-manifest script for bosh-lite.

• found in release-dir/bosh-lite/make-manifest
• discovers director uuid on demand, doesn't save an unnecessary file
• generates manifest, saved in release-dir/bosh-lite/
• sets bosh deployment to the generated manifest

This would turn this:

mkdir -p ~/deployments/bosh-lite
cd ~/workspace/diego-release
./scripts/print-director-stub > ~/deployments/bosh-lite/director.yml
./scripts/generate-deployment-manifest \
    ~/deployments/bosh-lite/director.yml \
    manifest-generation/bosh-lite-stubs/property-overrides.yml \
    manifest-generation/bosh-lite-stubs/instance-count-overrides.yml \
    manifest-generation/bosh-lite-stubs/persistent-disk-overrides.yml \
    manifest-generation/bosh-lite-stubs/iaas-settings.yml \
    manifest-generation/bosh-lite-stubs/additional-jobs.yml \
    ~/deployments/bosh-lite \
    > ~/deployments/bosh-lite/diego.yml
bosh deployment ~/deployments/bosh-lite/diego.yml

Into this:

cd ~/workspace/diego-release
./bosh-lite/make_manifest

Examples:

• cf
• mysql
• riakcs
• tcp routing

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/97863362.

[emalm]

Hi, @shalako,

Yes, we should have easier tooling to generate a Diego manifest for bosh-lite. I've added https://www.pivotaltracker.com/story/show/100917520 to provide a script to do this that's compatible with diego-release's current directory-based method of consuming values from the CF manifest.

Thanks,
Eric

[shalako]

I noticed now there's a script that generates manifests for both cf and diego. While I appreciate the convenience of this one-stop tool, I find it disconcerting that diego is taking over responsibility for my deployment of cf-release. If anything, it should be the other way around. I don't want my cf-release manifest in the diego repo directory.

Also, this approach doesn't pull in a stub for cf-release with sane default security groups (apps should be able to reach the haproxy, in order to reach other apps).

[Amit-PivotalLabs]

The following flow should work now:

bosh target lite

pushd ${CF_RELEASE_DIR}
./scripts/generate-bosh-lite-dev-manifest
popd

pushd ${DIEGO_RELEASE_DIR}
mkdir -p ${MANIFESTS_DIR}
./scripts/print-director-stub > ${MANIFESTS_DIR}/director.yml

./scripts/generate-deployment-manifest
${MANIFESTS_DIR}/director.yml
manifest-generation/bosh-lite-stubs/property-overrides.yml
manifest-generation/bosh-lite-stubs/instance-count-overrides.yml
manifest-generation/bosh-lite-stubs/persistent-disk-overrides.yml
manifest-generation/bosh-lite-stubs/iaas-settings.yml
manifest-generation/bosh-lite-stubs/additional-jobs.yml
${CF_RELEASE_DIR}/bosh-lite/deployments
> ${MANIFESTS_DIR}/diego.yml
popd

Arguably, only the parts inside the pushd ${DIEGO_RELEASE_DIR}/popd need to
exist as a script in diego-release.

I would strongly recommend any scripts that invoke bosh set the
BOSH_USE_BUNDLER environment variable to true, and that dev workstations
update to using a recent bosh CLI.

On Tue, Sep 29, 2015 at 12:36 PM, Shannon Coen notifications@github.com
wrote:

I noticed now there's a script that generates manifests for both cf and
diego. While I appreciate the convenience of this one-stop tool, I find it
disconcerting that diego is taking over responsibility for my deployment of
cf-release. If anything, it should be the other way around. I don't want my
cf-release manifest in the diego repo directory.

Also, this approach doesn't pull in a stub for cf-release with sane
default security groups (apps should be able to reach the haproxy, in order
to reach other apps).

—
Reply to this email directly or view it on GitHub
#54 (comment)
.

[shalako]

I also discovered that the ./scripts/deploy script (step 9) generates the manifest again (step 6).

Can instructions for deploying cf-release please be removed from diego-release? diego-release docs should be concerned with deploying diego only, with notes on dependencies in other releases. Link out to docs for cf-release.

[emalm]

We do have https://www.pivotaltracker.com/story/show/100909114 to defer to cf-release's customary methods for generating a suitable BOSH-lite manifest. It's prioritized, and I expect the team will get to it soon. We do have specific instructions for configuring the CF manifest to support windows cells, too, so unless the cf-release script also becomes aware of that diego-release stub we can't defer entirely to the cf-release documentation.

I too would prefer that either there be a shared directory for coordinated deployment manifests for a given environment, or that if each deployment is principally associated to a specific release, its manifest is stored somewhere in that release's directory.

Thanks,
Eric

[emalm]

Hi, @shalako,

The BOSH-Lite instructions in diego-release have gone through a few more revisions, and now generate the CF manifest only via the canonical scripts/generate-bosh-lite-dev-manifest script in cf-release. The corresponding generation script for the Diego deployment manifest stores it inside of the diego-release directory, and reports its location after generating it.

Thanks,
Eric

[mgcera]

Hi @ematpl,

Currently I don't have much idea of CF but I am trying to install CF on BOSHLite on laptop.

Now I have issues while executing $bosh deploy.

I have logged the details here : https://github.com/cloudfoundry/cf-release/issues/893

Thanks
Mritunjay