Skip to content
This repository has been archived by the owner on Feb 11, 2020. It is now read-only.

Matrix compatibility automation #387

Open
adrien-barret opened this issue Apr 3, 2019 · 4 comments
Open

Matrix compatibility automation #387

adrien-barret opened this issue Apr 3, 2019 · 4 comments

Comments

@adrien-barret
Copy link

Question

Hi, we use pcf-pipelines to deploy or new sandbox and others env. Some time we got the matrix version problem between stemcell, ert, etc... Shame on us we didn't checked that.
We want to automate and continue to skip that check in our mind.

Possible Fix

Is it possible to add the matrix versions into a file and catch it in the pipeline to set the value with that ?

Regards,

Hk

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

@kcboyle
Copy link
Contributor

kcboyle commented Apr 8, 2019

pcf-pipelines is deprecated, and will be archived before the end of April. The replacement will be the Pivotal product platform automation docs.pivotal.io/platform-automation. It is built primarily on om and offers more stability/configurability than pcf-pipelines.

@adrien-barret
Copy link
Author

Hi @kcboyle
Great news but I thinked from the website, PA was to maintain and not build a new env.

Ops Manager vs Platform Automation for PCF
Ops Manager manages PCF operations manually. Platform Automation for PCF lets you automate the process.
Ops Manager lets you install and configure PCF and PCF products manually. Its UI takes you through the configuration decisions or changes that you need to make in situations such as:

  • Installing PCF for the first time.

But I saw too on the website you can create your director into a docker directly.
Did you get some example, for a new installation using platform automation?

Regards,
Hk

@kcboyle
Copy link
Contributor

kcboyle commented Apr 9, 2019

Platform Automation can absolutely be used to deploy new Ops Managers, yes. The create-vm task does this.

Unlike pcf-pipelines, with Platform Automation you need to build out your pipeline yourself.

http://docs.pivotal.io/platform-automation/v2.1/reference/pipeline.html#installing-ops-manager-and-tiles (Line 199+) gives an example of how you can use the create-vm task in a pipeline.

Another difference is that Platform Automation does not maintain terraform templates. We recommend using the terraforming-* repos that the Pivotal infrastructure team manages. These repos are actively updated, and eliminates the problem of out of date templates in pcf-pipelines. To use these repos, it requires you to maintain your own override.tf for the pieces you cannot consume.
https://github.com/pivotal-cf/terraforming-aws
https://github.com/pivotal-cf/terraforming-gcp
https://github.com/pivotal-cf/terraforming-azure
https://github.com/pivotal-cf/terraforming-vsphere (incomplete)
https://github.com/pivotal-cf/terraforming-openstack

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants