You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Standard setup for an e2e test environment on GCE is provided in this directory. The data directory
4
+
should have:
5
+
6
+
*`gce.json` containing the GCE service account credentials to use that have permission to create instances, networks, and a bucket in project `openshift-gce-devel-ci`
7
+
*`ops-mirror.pem` containing the client certificate for the OpenShift ops mirror
8
+
*`ssh-privatekey` (optional) with the private key to use for the GCE instances
9
+
*`ssh-publickey` (optional) a key to use with the above private key
10
+
11
+
See `data/vars.yaml` for the default settings. This depends on the `openshift/origin-gce:latest` image
12
+
which is a pre-built version of the GCE reference architecture and the openshift-ansible playbooks for the
The following ansible variables are commonly used:
34
+
35
+
*`openshift_test_repo` is the URL to a yum repo to use to install
36
+
*`openshift_image_tag` (optional) is the suffix of the image to run with
37
+
*`openshift_pkg_version` (optional) is the exact package value to use `-0.0.1` if installing RPMs that don't match the desired version
38
+
39
+
The following environment variables can be provided
40
+
41
+
*`INSTANCE_PREFIX` is a value that should be unique across all clusters running in the project. It is provided as an env var to allow inventory to be calculated by Ansible.
42
+
*`OPENSHIFT_ANSIBLE_IMAGE` (defaults to `openshift/origin-gce:latest`) the image to deploy from
0 commit comments