Re: Migrating Bosh-Acceptance-Tests to v2 manifests
Mike Lloyd <mike@...>
Charles and Belinda,
Is there a reason Azure and Openstack are still untested?
From: cf-bosh@... <cf-bosh@...> On Behalf Of via Lists.Cloudfoundry.Org
Sent: Wednesday, April 24, 2019 5:46 PM
Cc: Belinda Liu <bliu@...>; Morgan Fine <mfine@...>
Subject: [cf-bosh] Migrating Bosh-Acceptance-Tests to v2 manifests
Hi Bosh community,
tldr; BATs is now on v2 manifests. If you run BATs in your pipeline, please try running against the v2_manifest branch before it is merged into master and let us know if you have any feedback. Hopefully it should just work.
We are migrating BATs (https://github.com/cloudfoundry/bosh-acceptance-tests) to use v2 manifests + cloud config. Using v2 manifest to deploy on bosh has been the standard for a while, but BATs has never been updated. We hope to deprecate v1 manifests very soon and need to upgrade BATs. Much of the v1 manifest that relates to vms, networks, disks etc is now in cloud config in the v2 world.
Specifically, the BATs previously had deployment manifest templates for every IaaS. We have migrated the IaaS details into IaaS specific cloud configs instead, and all BATs will deploy a generic deployment manifest. These can all be found in https://github.com/cloudfoundry/bosh-acceptance-tests/tree/v2_manifest/templates with the `cloud-config-` prefix.
We tested vSphere, AWS, GCP, and Warden in our own pipelines, but Azure and Openstack remain untested. BATs also has an Oracle configuration which we did not touch. Additionally, BATs can be configured with a variety of different network topologies, and we only tested a few. Ideally these changes should not affect anyone, but there may be some unforeseen issues. If you are a CPI author and have feedback on these changes, please reach out to the BOSH Director team. Otherwise, these changes will be merged into master next week.
Thanks in advance for your feedback,
Charles and Belinda, BOSH Director team (SF)