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

Vagrant OpenShift 3.10 Adaption #1069

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

lukeelten
Copy link

What does this PR do?

Adjusted Vagrantfile and provisioning playbook to work with OpenShift 3.10.

Changes to Vagrantfile

  • Increased default VM memory
  • Adjusted generated inventory to run with current installer version
  • Changed provisioned playbooks because they changed the installer playbooks with OpenShift 3.9

Changes to provisioning playbook:

  • Pinned openshift-ansible repository to branch "release-3.10"

How should this be manually tested?

vagrant plugin install vagrant-sshfs landrush vagrant-hostmanager
cd vagrant
vagrant up

See vagrant/README.md for more documentation.

Is there a relevant Issue open for this?

#931

Who would you like to review this?

cc: @e-minguez

Tobias Derksen added 3 commits August 20, 2018 18:33
…ent OpenShift release requires other playbooks to run, fixed provisioner to run correct playbooks
… memory available. Disabled checks for memory and disk space
@openshift-ci-robot openshift-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 21, 2018
@e-minguez
Copy link
Contributor

I'm not sure if we are still doing vagrant stuff. Adding @cooktheryan to the conversation.

@mulcahys
Copy link

@e-minguez are you saying you're dropping support for standing up openshift environments in vagrant?

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

1 similar comment
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 23, 2020
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants