v4.1.2

Features

• Extended addon to include
  • test-bind-autoscaler - A non intrusive test that goes through the process of adding and removing a test-bind-autoscaler service broker to and from your cf deployment. @itsouvalas
  • update-autoscaler - updates autoscaler service broker with any changes made on service_broker_username, service_broker_password and/or service_broker_domain. @itsouvalas
• Extend tests to include the aforementioned addons

Release updates:

Name	Version	Changed
app-autoscaler	5.4.0	no
bosh-dns-aliases	0.0.3	no
bpm	1.1.9	no
loggregator-agent	3.9	no
postgres	29	no
routing	0.223.0	no

v4.1.1

Features

• Using upstream 5.4.0 @genesis-bot

Upstream includes pr 701 which addresses the issue on using the correct JDK_HOME in prestart and in other scripts which is configured.

Release updates:

Name	Version	Changed
app-autoscaler	5.4.0	yes
bosh-dns-aliases	0.0.3	no
bpm	1.1.9	no
loggregator-agent	3.9	no
postgres	29	no
routing	0.223.0	no

v4.0.2

Features

• Using upstream 5.3.2 @genesis-bot
• Upstream includes database migration fix for MySQL @itsouvalas

Release updates:

Name	Version	Changed
app-autoscaler	5.3.2	yes
bosh-dns-aliases	0.0.3	no
bpm	1.1.9	no
loggregator-agent	3.9	no
postgres	29	no
routing	0.223.0	no

v4.0.1

Chores

• Bumped to major version 4.x.x as 3.0.1 should have already
• Updated upstream release reference version
• Updated corresponding tests
• Added upstream operations files

Release updates:

Name	Version	Changed
app-autoscaler	5.1.0	no
bosh-dns-aliases	0.0.3	no
bpm	1.1.9	no
loggregator-agent	3.9	no
postgres	29	no
routing	0.223.0	no

v3.0.1

Breaking Changes

This uses the latest upstream version 5.x.x which Drops support for CF CLI v6 and add support for v8 in the acceptance tests

Features

• Using upstream 5.1.0 @genesis-bot
• Added config-autoscaler @itsouvalas

Chores

• removed reference to xenial stemcells @JasonTheMain
• updated ci pipeline configuration to match new concourse environment @itsouvalas

Release updates:

Name	Version	Changed
app-autoscaler	5.1.0	yes
bosh-dns-aliases	0.0.3	no
bpm	1.1.9	no
loggregator-agent	3.9	no
postgres	29	no
routing	0.223.0	no

v3.0.0

Breaking Changes

Given the recent changes introduced on Fix loggregator tls agen/rlp mixup this release interferes with the upgrade process from 2.0.1. Another release or relevant instructions will be added once resolved/identified.

Features

• Using upstream 4.0.0
• Added bionic support on all instances

Bug Fixes

• Fixes issue where pull upstream would fail to retrieve the corresponding release
• Fixes issue where the overlay would ignore the deployment and network provided for nats under bosh-dns-aliases addons and the deployment for route registrar job under specific instance groups

Release updates:

Name	Version	Changed
app-autoscaler	4.0.0	yes
bosh-dns-aliases	0.0.3	no
bpm	1.1.9	yes
loggregator-agent	3.9	no
postgres	29	yes
routing	0.223.0	yes

v2.0.1 - Fixes Bosh DNS Runtime Config Issue

Bug Fix

Fixes issue where deploy would fail due to kit not using Bosh DNS runtime config.

v2.0.0 - Give Database Persistent Disk

Attention Required

• The 1.0.0 version of the kit was released without allocating the local
  postgres database node a persistent disk. If you are not using an external
  database, this can easily lead to loss of autoscaler service data. This is
  fixed in this version of the kit - please follow the following instructions
  to avoid data loss. Do not panic. Everything is going to be okay.

Taking a Backup of the Existing Database

Make sure you take this backup before upgrading the kit!

• bosh ssh onto the postgres_autoscaler of the deployment.
• become root with sudo -i
• Run the following to take a backup /var/vcap/packages/postgres-9.6.6/bin/pg_dumpall -U vcap >/tmp/pg_dump.sql
• Fetch the backup from the VM by exiting the VM and running bosh -e <envname> -d <depname> scp postgres_autoscaler:/tmp/pg_dump.sql ~/autoscaler_pg_dump.sql

Upgrade the Kit

• Bump the kit number in your environment file to this version and deploy it with genesis deploy <envname>

Restore the Database

Now you have a fresh, empty database. Let's put the data back.

• Upload the backup you took to the VM with bosh -e <envname> -d <depname> scp ~/autoscaler_pg_dump.sql postgres_autoscaler:/tmp/
• SSH onto the postgres_autoscaler VM with bosh ssh
• Become root with sudo -i
• Perform the restore with /var/vcap/packages/postgres-9.6.6/bin/psql -U vcap postgres </tmp/autoscaler_pg_dump.sql

After this, service should be restored and the database should have a persistent disk.

Additional Features

• The kit will now generate 10 year CA certs when creating a new deployment.

v1.0.0

Initial Release

Please read manual for usage.

This kit is intended to be used with v2.x versions of cf-genesis-kit, but can be used with v1.x versions by adding the cf-v1-support feature along with the required information.

v1.0.0-rc4 Preview Release

Release candidate preview release.

This kit is expecting to be used in conjuction with a deployment of cf-genesis-kit based on v2.0.0-rc5 or higher.

This update completes the new hook as well as adds the setup-cf-plugin addon.