Skip to content

Commit 49ff4f4

Browse files
authored
Merge pull request #95 from epics-containers/md
tidy up new-k8s-beamline tutorial some more
2 parents 769f1b4 + 8eca803 commit 49ff4f4

File tree

1 file changed

+7
-11
lines changed

1 file changed

+7
-11
lines changed

docs/tutorials/setup_k8s_new_beamline.md

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -27,17 +27,13 @@ a namespace configured for use by the beamline. See the previous tutorial
2727
for how to set one up if you do not have this already.
2828

2929
:::{note}
30-
DLS users: these instructions are for the BL46P beamline. This beamline
31-
already exists at DLS, so you could just skip ahead to creating the
32-
example IOC. You will need to ask the cloud team for permission on
33-
cluster `pollux`, namespace `p46-iocs` to do this.
34-
Go to this URL to request access:
35-
<https://jira.diamond.ac.uk/servicedesk/customer/portal/2/create/92>
36-
37-
HOWEVER, these instructions can be also used to setup any
38-
new beamline at DLS - just substitute the beamline name where appropriate.
39-
You will need to have a beamline cluster already created for the
40-
beamline by the cloud team and have requested access via the URL above.
30+
DLS users: these instructions are for the BL46P beamline. Which is a training beamline.
31+
32+
To setup the beamline repo for other beamlines you will need to change the answers to the copier template questions.
33+
34+
35+
At present DLS users will need to request access to the cluster for each beamline you want to work on. The following link is for making such a request but you will need someone who already has access to make the request for you:
36+
<https://jira.diamond.ac.uk/servicedesk/customer/portal/2/create/92> (ask giles if you don't know who to ask for this access.)
4137
:::
4238

4339
## Create a new beamline repository

0 commit comments

Comments
 (0)