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

Support of more recent OM and ERT versions on OpenStack? #377

Open
hfrenzel opened this issue Dec 17, 2018 · 2 comments
Open

Support of more recent OM and ERT versions on OpenStack? #377

hfrenzel opened this issue Dec 17, 2018 · 2 comments

Comments

@hfrenzel
Copy link

hfrenzel commented Dec 17, 2018

Hi,
is there any plan to support more recent versions of OM & ERT on OpenStack?
According to the release notes of PCF, they will contain at least some security fixes and v2.0 can't be found:

Used ert_major_minor_version: ^2\.0\.[0-9]+$ and opsman_major_minor_version: ^2\.0\.[0-9]+$:

resource script '/opt/resource/check []' failed: exit status 1

stderr:
2018/12/17 17:57:47 Exiting with error: cannot find specified release

Using ert_major_minor_version: ^2\.1\.[0-9]+$ and opsman_major_minor_version: ^2\.1\.[0-9]+$ as written in the example of https://github.com/pivotal-cf/pcf-pipelines/tree/master/install-pcf/openstack#usage the configure-director task failes with undefined method 'service_network=' for <Persistence::Models::Network>

@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 Dec 19, 2018

At this time pcf-pipelines has planned deprecation for early 2019 with a migration path to new tooling that will be officially supported, tested, and maintained.

OpenStack is hard for the team to maintain as none of the members are familiar with the ins and outs of OpenStack, and pcf-pipelines made maintenance of all IaaSs incredibly difficult. pcf-pipelines acts differently based on the IaaS you're using and the OpsMan/PAS version, which makes it brittle.

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