Ansible automation to load test-data of various sample applications to aid OCP Migration development efforts.
Velero is required for backups/restores, it can be installed using playbooks from this repo https://github.com/fusor/ocp-velero-ansible
Export KUBECONFIG for example: export KUBECONFIG=~/.kube/config
Set cluster password to env variable like this:
export kubeadmin_password="password"
Run ansible-playbook cake-php.yml to deploy, backup and restore a sample app.
It's also possible to optionally run backup/restore: ansible-playbook cake-php.yml -e with_backup=false -e with_restore=false
There is an option for populating the database with test data: ansible-playbook mysql-pvc.yml -e with_data=true
Loging in to cluster can be enabled by setting PROMPT_LOGIN: export PROMPT_LOGIN=true
We need to keep track of supported and unsupported test cases.
-
Tests cases that are expected to succeed:
- Basic app example -
nginx - Pod -
pod - Image Stream -
mysql-centos7-is - RBAC -
basic-sa-with-role - Route -
route - CRD -
crd - Service -
service - NetworkPolicy -
net-policy- prerequisites needed - Pipeline -
pipeline - Security Context Constraints -
scc - Replica set -
sets - Config map -
config - PVC -
mysql-pvc
- Basic app example -
-
Tests cases that are expected to fail:
- S2I -
cakephp - HA -
ha-mysql,ha-etcd,ha-kafka,ha-etcd-operator
- S2I -
-
Test cases prerequisites
-
NetworkPolicy -
net-policy\net-policy-extended- OCP-3:
networkPluginName: redhat/openshift-ovs-networkpolicyshould be specified in/etc/origin/master/master-config.yaml, or better create new cluster under upshift withopenshiftbundle andos_sdn_network_plugin_nameset toovs-networkpolicy. - OCP-4: comes with default
Networkpolicyplugin, but for editing useoc edit networkconfigand configure as stated in the example https://github.com/openshift/cluster-network-operator#configuring-openshiftsdn
- OCP-3:
-
RBAC
rbac-user-rolesFor running this playbook with user creation runexport RBAC_PREREQ=true
-