This repo contains tools for creating BOSH stemcells. A stemcell is a bootable disk image that is used as a template by a BOSH Director to create VMs.
git clone [email protected]:cloudfoundry/bosh-linux-stemcell-builder.git
cd bosh-linux-stemcell-builder
git checkout ubuntu-jammy/master
mkdir -p tmp
docker run \
--privileged \
-v "$(pwd):/opt/bosh" \
--workdir /opt/bosh \
--user=1000:1000 \
-it \
bosh/os-image-stemcell-builder:jammy
# You're now in the the Docker container
gem install bundler
bundle
# build OS image
bundle exec rake stemcell:build_os_image[ubuntu,jammy,$PWD/tmp/ubuntu_base_image.tgz] # build OS image
# build vSphere stemcell
bundle exec rake stemcell:build_with_local_os_image[vsphere,esxi,ubuntu,jammy,$PWD/tmp/ubuntu_base_image.tgz]When building a vSphere stemcell, you must download VMware-ovftool-*.bundle
and place it in the ci/docker/os-image-stemcell-builder-jammy/ directory. See
External Assets for download instructions.
An OS image is a tarball that contains a snapshot of an OS filesystem, including the libraries and system utilities needed by the BOSH agent; however, it does not contain the BOSH agent nor the virtualization tools: a subsequent Rake task adds the BOSH agent and a set of virtualization tools to the base OS image to produce a stemcell.
The OS Image should be rebuilt when you are making changes to the packages installed in the operating system or when making changes to the configuration of those packages.
bundle exec rake stemcell:build_os_image[ubuntu,jammy,$PWD/tmp/ubuntu_base_image.tgz]The arguments to the stemcell:build_os_image rake task follow:
operating_system_name(ubuntu): identifies which type of OS to fetch. Determines which package repository and packaging tool will be used to download and assemble the files. Currently, onlyubuntuis recognized.operating_system_version(jammy): an identifier that the system may use to decide which release of the OS to download. Acceptable values depend on the operating system. Forubuntu, usejammy.os_image_path($PWD/tmp/ubuntu_base_image.tgz): the path to write the finished OS image tarball to. If a file exists at this path already, it will be overwritten without warning.
Rebuild the stemcell when you are making and testing BOSH-specific changes such as a new BOSH agent.
bundle exec rake stemcell:build_with_local_os_image[vsphere,esxi,ubuntu,jammy,$PWD/tmp/ubuntu_base_image.tgz,"0.0.8"]The arguments to stemcell:build_with_local_os_image are:
infrastructure_name: Which IaaS you are producing the stemcell for. Determines which virtualization tools to package on top of the stemcell.hypervisor_name: Depending on what the IAAS supports, which hypervisor to target:aws→xen-hvm,azure→hyperv,google→kvm,openstack→kvm,vsphere→esxioperating_system_name(ubuntu): Type of OS. Same asstemcell:build_os_image. Can optionally include a variant suffix (jammy-fips)operating_system_version(jammy): OS release. Same asos_image_path($PWD/tmp/ubuntu_base_image.tgz): Path to base OS image produced instemcell:build_os_imagebuild_number(0.0.8): Stemcell version. Pro-tip: take the version number of the most recent release and add one, e.g.: "0.0.7" → "0.0.8". If not specified, it will default to "0000".
You can find the resulting stemcell in the tmp/ directory of the host, or in
the /opt/bosh/tmp directory in the Docker container. Using the above example,
the stemcell would be at
tmp/bosh-stemcell-0.0.8-vsphere-esxi-ubuntu-jammy-go_agent.tgz. You can
upload the stemcell to a vSphere BOSH Director:
bosh upload-stemcell tmp/bosh-stemcell-0.0.8-vsphere-esxi-ubuntu-jammy-go_agent.tgz[Fixme: update Testing section to Jammy]
The OS tests are meant to be run against the OS environment to which they
belong. When you run the stemcell:build_os_image rake task, it will create a
.raw OS image that it runs the OS specific tests against. You will need to run
the rake task the first time you create your docker container, but everytime
after, as long as you do not destroy the container, you should be able to run
the specific tests.
To run the ubuntu_jammy_spec.rb tests (assuming you've already built the OS
image at the tmp/ubuntu_base_image.tgz and you're within the Docker
container):
cd /opt/bosh/bosh-stemcell
OS_IMAGE=/opt/bosh/tmp/ubuntu_base_image.tgz bundle exec rspec -fd spec/os_image/ubuntu_jammy_spec.rb
When you run the stemcell:build_with_local_os_image or stemcell:build rake
task, it will create a stemcell that it runs the stemcell specific tests
against. You will need to run the rake task the first time you create your
docker container, but everytime after, as long as you do not destroy the
container, you should be able to run the specific tests:
cd /opt/bosh/bosh-stemcell; \
STEMCELL_IMAGE=/mnt/stemcells/vsphere/esxi/ubuntu/work/work/vsphere-esxi-ubuntu.raw \
STEMCELL_WORKDIR=/mnt/stemcells/vsphere/esxi/ubuntu/work/work/chroot \
OS_NAME=ubuntu \
bundle exec rspec -fd --tag ~exclude_on_vsphere \
spec/os_image/ubuntu_jammy_spec.rb \
spec/stemcells/ubuntu_jammy_spec.rb \
spec/stemcells/go_agent_spec.rb \
spec/stemcells/vsphere_spec.rb \
spec/stemcells/stig_spec.rb \
spec/stemcells/cis_spec.rbIn pursuit of more robustly testing, we wrote our testing library for stemcell contents, called ShelloutTypes.
The ShelloutTypes code has its own unit tests, but require root privileges and
an ubuntu chroot environment to run. For this reason, we use the
bosh/main-ubuntu-chroot docker image for unit tests. To run these unit tests
locally, run:
bundle install --local
cd /opt/bosh/bosh-stemcell
OS_IMAGE=/opt/bosh/tmp/ubuntu_base_image.tgz bundle exec rspec spec/ --tag shellout_typesIf on macOS, run:
OSX=true OS_IMAGE=/opt/bosh/tmp/ubuntu_base_image.tgz bundle exec rspec spec/ --tag shellout_typesThe BOSH Linux Stemcell Builder code itself can be tested with the following command's:
bundle install --local
cd /opt/bosh/bosh-stemcell
bundle exec rspec spec/If you find yourself debugging any of the above processes, here is what you need to know:
-
Most of the action happens in Bash scripts, which are referred to as stages, and can be found in
stemcell_builder/stages/<stage_name>/apply.sh. -
While debugging a particular stage that is failing, you can resume the process from that stage by adding
resume_from=<stage_name>to the end of yourbundle exec rakecommand. When a stage'sapply.shfails, you should see a message of the formCan't find stage '<stage>' to resume from. Aborting.so you know which stage failed and where you can resume from after fixing the problem. Please use caution as stages are not guaranteed to be idempotent.Example usage:
bundle exec rake stemcell:build_os_image[ubuntu,jammy,$PWD/tmp/ubuntu_base_image.tgz] resume_from=rsyslog_config
- If the OS image has been built and so long as you only make test case
modifications you can rerun the tests (without rebuilding OS image). Details
in section
How to run tests for OS Images - If the Stemcell has been built and you are only updating tests, you do not
need to re-build the stemcell. You can simply rerun the tests (without
rebuilding Stemcell. Details in section
How to run tests for Stemcell - It's possible to verify OS/Stemcell changes without making a deployment using
the stemcell. For a vSphere-specific Ubuntu stemcell, the filesytem is
available at
/mnt/stemcells/vsphere/esxi/ubuntu/work/work/chroot
The ovftool installer from VMWare can be found at my.vmware.com.
The ovftool installer must be copied into the ci/docker/os-image-stemcell-builder-jammy next to the Dockerfile or you will receive the error
Step 24/30 : ADD ${OVF_TOOL_INSTALLER} /tmp/ovftool_installer.bundle
ADD failed: stat /var/lib/docker/tmp/docker-builder389354746/VMware-ovftool-4.1.0-2459827-lin.x86_64.bundle: no such file or directory
The Docker image is published to
bosh/os-image-stemcell-builder.
You will need the ovftool installer present on your filesystem.
Rebuild the container with the build script...
./build os-image-stemcell-builder
When ready, push to DockerHub and use the credentials from LastPass...
cd os-image-stemcell-builder
./push
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent