Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
theodolite
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Analyze
Contributor analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Sören Henning
theodolite
Merge requests
!80
Add volume claim for OCI plus access pod
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
Add volume claim for OCI plus access pod
oci-volumes
into
master
Overview
0
Commits
5
Pipelines
4
Changes
4
Merged
Sören Henning
requested to merge
oci-volumes
into
master
4 years ago
Overview
0
Commits
5
Pipelines
4
Changes
4
Expand
Volume definition and an access pod are added. Open points are:
Pod should be converted to a deployment (or restarted on failure, see
#132
)
Some documentation should be added
Fixes
#128 (closed)
Edited
4 years ago
by
Sören Henning
0
0
Merge request reports
Compare
master
version 3
a5a6312b
4 years ago
version 2
4373ed44
4 years ago
version 1
85d93f6b
4 years ago
master (base)
and
latest version
latest version
967edaf3
5 commits,
4 years ago
version 3
a5a6312b
1 commit,
4 years ago
version 2
4373ed44
1 commit,
4 years ago
version 1
85d93f6b
1 commit,
4 years ago
4 files
+
92
−
2
Inline
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
Files
4
Search (e.g. *.vue) (Ctrl+P)
execution/README.md
+
31
−
2
Options
@@ -170,18 +170,47 @@ access (e.g. via SSH) to one of your cluster nodes.
You first need to create a directory on a selected node where all benchmark results should be stored. Next, modify
`infrastructure/kubernetes/volume-local.yaml`
by setting
`<node-name>`
to your selected node. (This node will most
likely also execute the
[
Theodolite job
](
#Execution
)
.) Further, you have to set
`path`
to the directory on the node you just created. To deploy
you volume run:
you
r
volume run:
```
sh
kubectl apply
-f
infrastructure/kubernetes/volume-local.yaml
```
##### *Oracle Cloud Infrastructure* volume
When you are running in the Oracle Cloud, you can provision a persistent volume claim by attaching a volume from the
Oracle Cloud Infrastructure Block Volume service. To create your volume, run:
```
sh
kubectl apply
-f
infrastructure/kubernetes/volume-oci.yaml
```
More information can be found in the official documentation:
[
Oracle Cloud Infrastructure: Creating a Persistent Volume Claim
](
https://docs.oracle.com/en-us/iaas/Content/ContEng/Tasks/contengcreatingpersistentvolumeclaim.htm
)
##### Other volumes
To use volumes provided by public cloud providers or network-based file systems, you can use the definitions in
To use volumes provided by
other
public cloud providers or network-based file systems, you can use the definitions in
`infrastructure/kubernetes/`
as a starting point. See the offical
[
volumes documentation
](
https://kubernetes.io/docs/concepts/storage/volumes/
)
for additional information.
##### Accessing benchmark results via Kubernetes
In cases where you do not have direct access to the underlying storage infrasturcture of your volume (e.g., if your
admin configures a local or hostPath volume for you and you do not have SSH access to the node), you can deploy our
Theodolite results access deployment:
```
sh
kubectl apply
-f
infrastructure/kubernetes/volume-access.yaml
```
It allows you to browse the benchmark results or copy files your Kubernetes client via the following commands:
```
sh
kubectl
exec
-it
$(
kubectl get pods
-o
=
name
-l
app
=
theodolite-results-access
)
--
sh
kubectl
cp
$(
kubectl get pods
--no-headers
-o
custom-columns
=
":metadata.name"
-l
app
=
theodolite-results-access
)
:app/results <target-dir>
```
## Execution
Loading