Skip to content

Commit

Permalink
Adding scenarios sub folders to container creation (#337)
Browse files Browse the repository at this point in the history
* adding scenarios sub folders to container creation
* adding req
* trying other package installations
* more specific versions
* removing vsphere
* adding wheel
* put vmware back

Fixes: #335 
Signed-off-by: Sandro Bonazzola <[email protected]>
Co-authored-by: Sandro Bonazzola <[email protected]>
  • Loading branch information
paigerube14 and sandrobonazzola authored Oct 14, 2022
1 parent 66eb541 commit da74933
Show file tree
Hide file tree
Showing 3 changed files with 23 additions and 7 deletions.
8 changes: 5 additions & 3 deletions containers/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,10 @@ To run containerized Kraken as a Kubernetes/OpenShift Deployment, follow these s
4. Create a ConfigMap named kube-config using `kubectl create configmap kube-config --from-file=<path_to_kubeconfig>`
5. Create a ConfigMap named kraken-config using `kubectl create configmap kraken-config --from-file=<path_to_kraken_config>`
6. Create a ConfigMap named scenarios-config using `kubectl create configmap scenarios-config --from-file=<path_to_scenarios_folder>`
7. Create a service account to run the kraken pod `kubectl create serviceaccount useroot`.
8. In Openshift, add privileges to service account and execute `oc adm policy add-scc-to-user privileged -z useroot`.
9. Create a Job using `kubectl apply -f kraken.yml` and monitor the status using `oc get jobs` and `oc get pods`.
7. Create a ConfigMap named scenarios-openshift-config using `kubectl create configmap scenarios-openshift-config --from-file=<path_to_scenarios_openshift_folder>`
8. Create a ConfigMap named scenarios-kube-config using `kubectl create configmap scenarios-kube-config --from-file=<path_to_scenarios_kube_folder>`
9. Create a service account to run the kraken pod `kubectl create serviceaccount useroot`.
10. In Openshift, add privileges to service account and execute `oc adm policy add-scc-to-user privileged -z useroot`.
11. Create a Job using `kubectl apply -f kraken.yml` and monitor the status using `oc get jobs` and `oc get pods`.

NOTE: It is not recommended to run Kraken internal to the cluster as the pod which is running Kraken might get disrupted.
10 changes: 10 additions & 0 deletions containers/kraken.yml
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,10 @@ spec:
name: kraken-config
- mountPath: "/root/kraken/scenarios"
name: scenarios-config
- mountPath: "/root/kraken/scenarios/openshift"
name: scenarios-openshift-config
- mountPath: "/root/kraken/scenarios/kube"
name: scenarios-kube-config
restartPolicy: Never
volumes:
- name: config
Expand All @@ -37,3 +41,9 @@ spec:
- name: scenarios-config
configMap:
name: scenarios-config
- name: scenarios-openshift-config
configMap:
name: scenarios-openshift-config
- name: scenarios-kube-config
configMap:
name: scenarios-kube-config
12 changes: 8 additions & 4 deletions requirements.txt
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,11 @@ docker-compose
jinja2==3.0.3
itsdangerous==2.0.1
werkzeug==2.0.3
aliyun-python-sdk-core-v3>=2.13.33
aliyun-python-sdk-ecs>=4.24.25
arcaflow-plugin-sdk==0.3.0
git+https://github.com/vmware/[email protected]
lxml >= 4.3.0
pyVmomi >= 6.7
zope.interface==5.4.0
aliyun-python-sdk-core==2.13.36
aliyun-python-sdk-ecs==4.24.25
arcaflow-plugin-sdk
wheel
git+https://github.com/vmware/[email protected]

0 comments on commit da74933

Please sign in to comment.