Name: cflinuxfs3m
Owner: Cloud Foundry
Description: null
Created: 2018-01-29 17:01:44.0
Updated: 2018-04-30 19:40:23.0
Pushed: 2018-04-30 19:40:22.0
Homepage: null
Size: 43
Language: Ruby
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
This repo contains scripts for creating garden root filesystems.
NOTE: Neither cflinuxfs3m nor Ubuntu 18.04 have been released.
cflinuxfs3m/build/install-packages.sh has a list of packages passed to apt-get install as well.
To create a rootfs for the cflinuxfs3m stack:
This will create the cflinuxfs3m.tar.gz file, which is the artifact used as the rootfs in Cloud Foundry deployments.
To start, clone the repository containing the cflinuxfs3m-rootfs BOSH release:
clone git@github.com:cloudfoundry/cflinuxfs3m-release.git`
flinuxfs3m-release`
Replace the old cflinuxfs3m tarball with the new tarball created above:
f config/blobs.yml
r -p blobs/rootfs
path-to-new-tarball>/cflinuxfs3m.tar.gz blobs/rootfs/cflinuxfs3m-new.tar.gz
Create a dev release and upload it to your BOSH deployment:
create release --force --with-tarball --name cflinuxfs3m-rootfs
upload release <generated-dev-release-tar-file>
If your Diego deployment manifest has version: latest indicated for the cflinuxfs3m-rootfs release, then redeploying your Diego will enable this new rootfs to be used in your app containers.
To run the local tests, just run rspec. If the top level of this repo contains a file named cflinuxfs3m.tar.gz, the tests will be run against this file. Otherwise, make will be run to create a new rootfs.
To test the rootfs BOSH release, see the instructions here
The generation and release of a new rootfs happens on the cflinuxfs3m CI pipeline.
A new stack is generated with make.
A dev BOSH release of that new stack is generated and deployed to the BOSH Lite at cflinuxfs3m.buildpacks.ci.cf-app.com and the rootfs smoke tests run.
CF and Diego are deployed to that BOSH Lite. The cf-acceptance-tests are then run against the deployment.
Once all tests pass and the product manager ships the release, the rootfs tarball can be found as a Github Release, Docker Image, and as a BOSH release. A commit is also made to update the blobs on cf-release develop.