Skip to content

Commit f235a92

Browse files
author
Alan Christie
committed
- Added missing role-subdirectory!
1 parent 2e2e9e4 commit f235a92

File tree

14 files changed

+9
-9
lines changed

14 files changed

+9
-9
lines changed

.yamllint

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ yaml-files:
77

88
ignore: |
99
.github/
10-
roles/jupyter-operator/templates/deployment.yaml.j2
10+
roles/operator/templates/deployment.yaml.j2
1111

1212
rules:
1313
indentation:

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Python packages that is used by the **Informatics Matters Data Manager API**
1414
to create Jupyter Notebooks for the Data manager service.
1515

1616
The operator's Custom Resource Definition (CRD) can be found in
17-
`roles/jupyter-operator/files`.
17+
`roles/operator/files`.
1818

1919
By default, the operator creates instances using the Jupyter image: -
2020

@@ -38,12 +38,12 @@ The following will build an operator image with the tag `1.0.0-alpha.1`: -
3838

3939
## Deploying into the Data Manager API
4040
We use [Ansible] 3 and community modules in [Ansible Galaxy] as the deployment
41-
mechanism, using the `jupyter-operator` Ansible role in this repository and a
41+
mechanism, using the `operator` Ansible role in this repository and a
4242
Kubernetes config (KUBECONFIG). All of this is done via a suitable Python
4343
environment using the requirements in the root of the project...
4444

45-
$ python -m venv ~/.venv/jupyter-operator
46-
$ source ~/.venv/jupyter-operator/bin/activate
45+
$ python -m venv ~/.venv/data-manager-jupyter-operator
46+
$ source ~/.venv/data-manager-jupyter-operator/bin/activate
4747
$ pip install --upgrade pip
4848
$ pip install -r requirements.txt
4949
$ ansible-galaxy install -r requirements.yaml
@@ -83,7 +83,7 @@ You will need: -
8383
reference: `custom_resource['status']['jupyter']['notebook']['url']`.
8484

8585
> Our CRD already contains suitable annotations
86-
(see `roles/jupyter-operator/files/crd.yaml`), so there's nothing more to
86+
(see `roles/operator/files/crd.yaml`), so there's nothing more to
8787
do here once you've deployed it (using Ansible in our case,
8888
as described earlier).
8989

@@ -129,7 +129,7 @@ and run using a user and group that is assigned by the Data Manager API.
129129

130130
> See our handling of these values in the `create()` function
131131
of our `operator/handlers.py` and their definitions
132-
in `roles/jupyter-operator/files/crd.yaml`
132+
in `roles/operator/files/crd.yaml`
133133

134134
## Storage volume
135135
In order to place Data-Manager Project files the **CRD** must
@@ -141,7 +141,7 @@ expose the following properties through its schema's: -
141141
These will be expected to provide a suitable volume mount within the
142142
application **Pod** for the Project files.
143143

144-
> See our use of these values in `roles/jupyter-operator/files/crd.yaml`.
144+
> See our use of these values in `roles/operator/files/crd.yaml`.
145145
146146
## Instance certificate variables
147147
Applications can use the DM-API ingress, if they use path-based routing,
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

0 commit comments

Comments
 (0)