Sign inSign up

dpb587/boshua

By dpb587

•Updated over 7 years ago

For providing, using, and inspecting artifacts of BOSH.

Image
0

8.4K

dpb587/boshua repository overview

⁠boshua

For providing, using, and inspecting artifacts of BOSH⁠.

bosh unofficial artifacts

⁠Goals

  • provide consistent ways to generate and store metadata about releases, compilations, and stemcells
  • support private and public configurations with access to different sets of resources
  • deprecate one-off, duplicated scripts which have historically implemented these processes
  • allow compiled releases to be dynamically discovered and avoid hard-coding references
  • support just-in-time release compilations, shared across environments
  • focus on CLI and API extensibility to enable this as a building block
  • support both local and remote execution of any commands

⁠Core Concepts

First, let's define some of the terminology this uses...

  • Artifact - an artifact represents something of interest and generally refers to a permanent blob of data somewhere (e.g. a BOSH release tarball stored on Amazon S3). Artifacts are usually identified by a couple pieces of canonical information (e.g. name, version, URI, checksum). There are several primary types of artifacts, each represented by a top-level CLI command or API endpoint.
    • Stemcell - a particular version of a BOSH stemcell for a given IaaS
    • Release - a particular version of a BOSH release
      • Compilation - a particular version of a BOSH release that has been compiled against a particular stemcell or OS and version
    • Labels - used to label artifacts for logical categorization. For hierarchical taxonomies, path-style values with forward slashes can be used. Some standardized label conventions are...
      • repo/* - to identify the source of the release; e.g. repo/github.com/dpb587/openvpn-bosh-release
      • stability/(alpha|beta|rc|stable) - identify stability of artifacts
      • tag/* - general, tag-based navigation; e.g. tag/cpi, tag/networking
      • deprecated - to identify artifacts which are deprecated
  • Analysis - an artifact is independently useful, but there is often much more information which can be derived from it (e.g. what OS packages are included in a particular stemcell version). Analysis results are generated metadata which is affiliated with a particular artifact.
    • Analyzer - analyzers are used to generate specific types of metadata about an artifact. Each artifact type has several builtin analyzers.
    • Formatters - formatters are tools for interpreting the raw results and providing them in a more meaningful way. Most analyzers have several builtin formatters.
  • Datastore - a datastore is something which can find and/or store details about artifacts and analysis in a permanent way (e.g. a BOSH release repository having release information). Each artifact type has several supported datastores, and datastores can delegate to other, possibly remote datastores (e.g. through APIs).
  • Scheduler - a scheduler is used for executing work when results are not already available (e.g. compiling a release). Several types of schedulers are supported to support running work locally or in Docker, remotely on Concourse, or remotely through an API.
  • Provider - a specific implementation of a datastore or scheduler. Providers are configured through the config file and their provider-specific options.

⁠Usage

CLI/API remains in beta and subject to change.

⁠CLI

The primary tool is the boshua⁠ CLI. Generally, -h should be used to learn more about specific commands and available options.

The first level of commands are primarily geared towards specific artifacts (e.g. release, stemcell)...

$ boshua -h
Available commands:
  release     For working with releases
  stemcell    For working with stemcells

When working with a specific artifact type, several flags can be used for finding specific versions of the artifact...

$ boshua release -h
[release command options]
      --release=          The release in name/version format
      --release-name=     The release name
      --release-version=  The release version
      --release-checksum= The release checksum
      --release-url=      The release source URL
      --release-label=    The label(s) to filter releases by

Further subcommands can be used which deal with a specific artifact type...

$ boshua release --release=openvpn/5.1.0 -h
Available commands:
  analysis        For analyzing the release artifact
  analyzers       For showing the supported analyzers
  artifact        For showing the release artifact
  compilation     For working with compiled releases
  datastore       For interacting with release datastores
  download        For downloading the release locally
  upload-release  For uploading the release to BOSH

Most notably, these subcommands are common across most artifacts: analysis, analyzers, artifact, datastore, and download.

The analysis subcommands have some shared usage as well...

$ boshua release --release=openvpn/5.1.0 analysis -h
[analysis command options]
      --analyzer=         The analyzer name

Available commands:
  artifact       For showing the analysis artifact
  download       For downloading the analysis locally
  results        For showing the results of an analysis

For more specific examples, see below.

⁠Releases

Finding the tarball of a release...

$ boshua release --release=openvpn/5.0.0
file   openvpn-5.0.0.tgz
url    https://s3-external-1.amazonaws.com/dpb587-bosh-release-openvpn-us-east-1/artifacts/release/1b77cbd51a3debefcb06f2ad5311d872f056dbe9
sha1   1b77cbd51a3debefcb06f2ad5311d872f056dbe9
sha256 02965881f86b36b311768b154dadbef4522a8cccb81e1b6531c7db05848869aa

Showing the release.MF data of a release...

$ boshua release --release=openvpn/5.0.0 analysis --analyzer=releasemanifests.v1 results -- spec --release
name: openvpn
version: 5.0.0
commit_hash: 0f8966c
uncommitted_changes: false
...

Showing the properties for a job of a release...

$ boshua release --release=openvpn/5.0.0 analysis --analyzer=releasemanifests.v1 results -- properties --job=openvpn
server     VPN IP and netmask (basis of the IP pool which the server will allocate to clients)
tls_cipher A colon-separated list of allowable TLS ciphers
tls_crl    Certificate Revocation List (`X509 CRL`, including the begin/end markers)
dh_pem     Diffie-Hellmann Key (`DH PARAMETERS`, including the begin/end markers)
...
⁠Compilations

Getting the compilation of a release on a stemcell...

$ boshua release --release=openvpn/4.1.0 compilation --os=ubuntu-trusty/3468.13
file   openvpn-4.1.0-on-ubuntu-trusty-stemcell-3468.13.tgz
url    https://s3-external-1.amazonaws.com/dpb587-bosh-release-openvpn-us-east-1/compiled_releases/openvpn/openvpn-4.1.0-on-ubuntu-trusty-stemcell-3468.13-compiled-1.20171209113453.0.tgz
sha1   d278e2a37c486beabd0a9ffd2426e58b38172842
sha256 02120c9f1d084e232c0a996f7fa54e0e41c8b53c72cdb1003085108311929362

Uploading the compilation to the director (or showing the command to)...

$ boshua release --release=openvpn/4.1.0 compilation --os=ubuntu-trusty/3468.13 upload-release --cmd
bosh upload-release --name=openvpn --version=4.1.0 \
  https://s3-external-1.amazonaws.com/dpb587-bosh-release-openvpn-us-east-1/compiled_releases/openvpn/openvpn-4.1.0-on-ubuntu-trusty-stemcell-3468.13-compiled-1.20171209113453.0.tgz \
  --sha1=d278e2a37c486beabd0a9ffd2426e58b38172842 \
  --stemcell=ubuntu-trusty/3468.13

Getting an ops file for using the compiled release in a manifest...

$ boshua release --release=openvpn/4.1.0 compilation --os=ubuntu-trusty/3468.13 ops-file
- path: /releases/name=openvpn?
  type: replace
  value:
    name: openvpn
    sha1: md5:9cc79bee6180ef5e9f9b96606bf252bd
    stemcell:
      os: ubuntu-trusty
      version: "3468.13"
    url: https://s3-external-1.amazonaws.com/dpb587-bosh-release-openvpn-us-east-1/compiled_releases/openvpn/openvpn-4.1.0-on-ubuntu-trusty-stemcell-3468.13-compiled-1.20171209113453.0.tgz
    version: 4.1.0

Showing the checksums of the files of a compiled release...

$ boshua release --release=openvpn/4.1.0 compilation --os=ubuntu-trusty/3468.12 analysis --analyzer=releaseartifactfiles.v1 results -- sha1sum
...
7edc92307679f49446037387effa6c642c05e2e0  compiled_packages/openvpn.tgz!share/doc/openvpn/COPYRIGHT.GPL
67766b2d0c67c36841e77c6b05673a702559371b  compiled_packages/openvpn.tgz!share/doc/openvpn/COPYING
99e42912c49c8cd676000c00f2dd51c1795cb4f4  compiled_packages/openvpn.tgz!share/man/man8/openvpn.8
e0ebceb7f4f638aca7210001c828d6f889a8128f  compiled_packages/openvpn.tgz!lib/openvpn/plugins/openvpn-plugin-down-root.so
6eb2e481af90d6060a61a889a8641dc1e5e75331  compiled_packages/openvpn.tgz!lib/openvpn/plugins/openvpn-plugin-down-root.la
⁠Stemcells

Finding the tarball of a stemcell...

$ boshua stemcell --stemcell=bosh-aws-xen-hvm-ubuntu-trusty-go_agent/3541.12 --stemcell-flavor=light
file  light-bosh-stemcell-3541.12-aws-xen-hvm-ubuntu-trusty-go_agent.tgz
url   https://s3.amazonaws.com/bosh-aws-light-stemcells/light-bosh-stemcell-3541.12-aws-xen-hvm-ubuntu-trusty-go_agent.tgz
sha1  e2f9840e7ed3eb2ccdf4c39f3a7b49e35e1ad8ec
sha256 23884d534e4f5f946234ff3caf4240f20a37473b6afa0fcb5ba0f5bca3f9de3c

Show the filesystem of a stemcell...

$ boshua stemcell --stemcell=bosh-aws-xen-hvm-ubuntu-trusty-go_agent/3541.12 --stemcell-flavor=light analysis --analyzer=stemcellimagefiles.v1 results -- ls
drwxr-xr-x - root root       0 Apr  6 18:43 /bin
-rwxr-xr-x - root root 1021112 May 16  2017 /bin/bash
-rwxr-xr-x - root root   31152 Oct 21  2013 /bin/bunzip2
-rwxr-xr-x - root root   31152 Oct 21  2013 /bin/bzcat
lrwxrwxrwx - root root       6 Oct 21  2013 /bin/bzcmp -> bzdiff
...

Show the packages of a stemcell...

$ boshua stemcell --stemcell=bosh-aws-xen-hvm-ubuntu-trusty-go_agent/3541.12 --stemcell-flavor=light analysis --analyzer=stemcellpackages.v1 results -- contents
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                Version                                    Architecture Description
+++-===================================-==========================================-============-===============================================================================
ii  adduser                             3.113+nmu3ubuntu3                          all          add and remove users and groups
ii  anacron                             2.3-20ubuntu1                              amd64        cron-like program that doesn't go by time
ii  apparmor                            2.10.95-0ubuntu2.6~14.04.3                 amd64        user-space parser utility for AppArmor
ii  apparmor-utils                      2.10.95-0ubuntu2.6~14.04.3                 amd64        utilities for controlling AppArmor
ii  apt                                 1.0.1ubuntu2.17                            amd64        commandline package manager
...
⁠Deployment Manifests

Convert a manifest referencing release sources to compiled releases...

$ bosh deploy <( boshua deployment use-compiled-releases < manifest.yml )
  - name: openvpn
    version: 5.1.0
-   sha1: b42eb85e5f074c26b065956cc9b8a6d69208f8a0
+   sha1: sha512:ea3c1185076d52b87064951e91dd8885ca62f045dd4e1a17305e6a90a1901cb8d89ea097773e232bdbca2455be746672ea7be93371915597c574cb6933b7c13b
-   url: https://s3-external-1.amazonaws.com/dpb587-bosh-release-openvpn-us-east-1/artifacts/release/b42eb85e5f074c26b065956cc9b8a6d69208f8a0
+   url: https://s3-external-1.amazonaws.com/dpb587-test-20140414a-us-east-1/compiled-release/2f/474fe4787338086f4e0cb34207c3f687dabe16
+   stemcell:
+     os: ubuntu-trusty
+     version: '3586.27'

Some caveats for automatically converting manifests...

  • explicit versions must be used for releases and stemcells (not latest or x.latest)
  • releases should specify canonical properties (e.g. absolute URLs or tarball checksums)
  • manifests with multiple stemcells are not supported

By default, if a compilation is not already available and it can be scheduled, this command will queue and block until the shared compilation artifact becomes available.

⁠Analysis

There are several built-in analyzers which can also be used directly, although they are typically used indirectly when using the analysis subcommands of specific artifact types (results from using these generic commands are not stored). Analysis results are JSON streams of objects.

Generate a raw analysis with the generate subcommand...

$ boshua analysis generate --analyzer=releasemanifests.v1 openvpn-4.2.1.tgz | jq -c keys | head -n1
["parsed","path","raw"]

The formatter subcommand provides direct access to built-in formatters which can parse analysis results into more meaningful output...

$ boshua analysis formatter stemcellimagefiles.v1 -h
Available commands:
  ls         Show an ls-style list of files
  sha1sum    Show sha1 checksums (aliases: shasum)
  sha256sum  Show sha256 checksums
  sha512sum  Show sha512 checksums

Pass the results of a previous analysis via STDIN to use it...

$ boshua analysis formatter releasemanifests.v1 properties --job=openvpn < releasemanifests.v1.jsonl

The previous command is equivalent to the following examples due to how the results subcommand of individual artifacts works...

$ boshua release --release=openvpn/5.1.0 analysis --analyzer=releasemanifests.v1 results -- properties --job=openvpn
$ boshua release --release=openvpn/5.1.0 analysis --analyzer=releasemanifests.v1 results --raw | boshua analysis formatter releasemanifests.v1 properties --job=openvpn
⁠Analyzers

The following default analyzers are included...

  • releaseartifactfiles.v1 - extract file stats and checksums from a release tarball and its embedded tarballs
  • releasemanifests.v1 - extract release.MF and job spec data from a release tarball
  • stemcellimagefiles.v1 - extract file stats and checksums from the embedded image of a stemcell tarball
  • stemcellmanifest.v1 - extract stemcell.MF data from a stemcell tarball
  • stemcellpackages.v1 - extract and parse packages.txt data from a stemcell tarball
⁠Server

The CLI provides an HTTP server to allow remote querying and execution of commands. By default, it will listen on 127.0.0.1:4508.

$ boshua server
⁠CLI Downloads

The /cli/ endpoint can be used for providing binaries for download.

⁠Web UI

The /ui/ endpoint can be used for hosting simple HTML pages which may use the API.

⁠GraphQL API

The /api/v2/graphql endpoint provides a GraphQL API with query and mutation support.

⁠Query: release

Get information about a release...

{
  release(name: String, version: String, url: String, checksum: String, labels: [String]) {
    name
    version
    labels

    tarball { #artifact }

    compilation(os: String, version: String) {
      tarball { #artifact }
      analysis { #analysis }
    }

    analysis {
      results(analyzers: [String]) {
        analyzer
        artifact { #artifact }
      }
    }
  }
}
⁠Query: stemcell

Get information about a stemcell...

{
  stemcell(iaas: String, hypervisor: String, os: String, version: String, diskFormat: String, flavor: String, labels: [String]) {
    iaas
    hypervisor
    os
    flavor
    diskFormat
    version

    tarball { #artifact }
    analysis { #analysis }
  }
}
⁠Mutation: scheduleCompilation

Schedule compilation for a release...

mutation {
  scheduleReleaseCompilation(name: String, version: String, url: String, checksum: String, osName: String, osVersion: String) {
    status
  }
}
⁠Mutation: scheduleStemcellAnalysis

Schedule analysis of a stemcell...

mutation {
  scheduleStemcellAnalysis( #stemcellParams, analyzer: String) {
    status
  }
}
⁠Mutation: scheduleReleaseAnalysis

Schedule analysis of a stemcell...

mutation {
  scheduleReleaseAnalysis( #releaseParams, analyzer: String) {
    status
  }
}
⁠Mutation: scheduleReleaseCompilationAnalysis

Schedule analysis of a stemcell...

mutation {
  scheduleReleaseAnalysis( #releaseParams, #releaseCompilationParams, analyzer: String) {
    status
  }
}
⁠Library

Library usage is not yet trivial. See some of the examples in the main⁠ packages for now.

⁠Configuration

The default configuration lives in ~/.config/boshua/config.yml - a YAML file describing the various datastores that boshua can reference. See the partial documentation in config/config.go⁠ or examples in doc/config/examples⁠.

When a remote server is available, $BOSHUA_SERVER or --default-server may be used to automatically configure remote lookups and avoid the need for a configuration file. When building boshua⁠, a default server can be embedded with link options⁠ and the main.defaultServer variable.

⁠Stemcell Providers
⁠Release Providers
⁠Release Compilation Providers
⁠Scheduler Providers

⁠Extra Tools

⁠stemcellpackagediff

The stemcellpackagediff⁠ is a standalone CLI which uses the stemcellpackages.v1 analyzer to compare packages between two versions of a stemcell.

stemcellpackagediff ubuntu-xenial 97.12 97.15
~ intel-microcode (3.20180807a.0ubuntu0.16.04.1; was 3.20180425.1~ubuntu0.16.04.2)
~ linux-generic-hwe-16.04-edge (4.15.0.33.54; was 4.15.0.32.53)
- linux-headers-4.15.0-32 (4.15.0-32.35~16.04.1)
- linux-headers-4.15.0-32-generic (4.15.0-32.35~16.04.1)
+ linux-headers-4.15.0-33 (4.15.0-33.36~16.04.1)
+ linux-headers-4.15.0-33-generic (4.15.0-33.36~16.04.1)
~ linux-headers-generic-hwe-16.04-edge (4.15.0.33.54; was 4.15.0.32.53)
- linux-image-4.15.0-32-generic (4.15.0-32.35~16.04.1)
+ linux-image-4.15.0-33-generic (4.15.0-33.36~16.04.1)
~ linux-image-generic-hwe-16.04-edge (4.15.0.33.54; was 4.15.0.32.53)
~ linux-libc-dev:amd64 (4.4.0-134.160; was 4.4.0-133.159)
- linux-modules-4.15.0-32-generic (4.15.0-32.35~16.04.1)
+ linux-modules-4.15.0-33-generic (4.15.0-33.36~16.04.1)
- linux-modules-extra-4.15.0-32-generic (4.15.0-32.35~16.04.1)
+ linux-modules-extra-4.15.0-33-generic (4.15.0-33.36~16.04.1)

It supports a --format argument where markdown (below) or json can be used to customize the output.

PackageOld VersionNew Version
intel-microcode3.20180425.1~ubuntu0.16.04.23.20180807a.0ubuntu0.16.04.1
linux-generic-hwe-16.04-edge4.15.0.32.534.15.0.33.54
linux-headers-4.15.0-324.15.0-32.35~16.04.1–
linux-headers-4.15.0-32-generic4.15.0-32.35~16.04.1–
linux-headers-4.15.0-33–4.15.0-33.36~16.04.1
linux-headers-4.15.0-33-generic–4.15.0-33.36~16.04.1
linux-headers-generic-hwe-16.04-edge4.15.0.32.534.15.0.33.54
linux-image-4.15.0-32-generic4.15.0-32.35~16.04.1–
linux-image-4.15.0-33-generic–4.15.0-33.36~16.04.1
linux-image-generic-hwe-16.04-edge4.15.0.32.534.15.0.33.54
linux-libc-dev:amd644.4.0-133.1594.4.0-134.160
linux-modules-4.15.0-32-generic4.15.0-32.35~16.04.1–
linux-modules-4.15.0-33-generic–4.15.0-33.36~16.04.1
linux-modules-extra-4.15.0-32-generic4.15.0-32.35~16.04.1–
linux-modules-extra-4.15.0-33-generic–4.15.0-33.36~16.04.1

⁠Development

⁠Futures

  • ... datastore filter ~> versions
  • analysis generate --analyzer=x ?> analysis generate x
  • configurable analyzers
  • api download mirror/proxy
  • nicer wrapper libraries - r, _ := boshua.Release("openvpn/5.1.0"); p, _ := r.Packages(); return p[0].Name
  • testing
  • webui

⁠History

This project is the amalgamation of several former, smaller projects; but now focused on CLI+API, public+private deployability, and dynamic execution.

  • bosh-stemcell-metadata-scripts⁠ - repository of scripts for extracting package lists, filesystem details, and metadata from stemcells
  • bosh-stemcell-metadata⁠ - repository of pre-computed results from bosh-stemcell-metadata-scripts for specific stemcell lines
  • bosh-release-compiler⁠ - simple repository of tasks for compiling releases with concourse
  • bosh-compiled-releases⁠ - repository for tracking compiled releases from shared environments or imported from external sources, and CLI for rewriting deployment manifests to use them

⁠License

MIT License⁠

Tag summary

Content type

Image

Digest

Size

108.6 MB

Last updated

over 7 years ago

docker pull dpb587/boshua