You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/AdministratorGuide/ServerInstallations/InstallingDiracServer.rst
+40-35Lines changed: 40 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -195,6 +195,12 @@ Couple notes:
195
195
* SAN in your certificates: if you are contacting a machine using its aliases, make sure that all the aliases are in the SubjectAlternativeName (SAN) field of the certificates
196
196
* FQDN in the configuration: SAN normally contains only FQDN, so make sure you use the FQDN in the CS as well (e.g. ``mymachine.cern.ch`` and not ``mymachine``)
197
197
198
+
199
+
User (admin) certificate
200
+
------------------------
201
+
202
+
The user installing the server should have their own certificate: it will be used for administration.
203
+
198
204
.. _using_own_CA:
199
205
200
206
-----------------
@@ -266,41 +272,31 @@ be taken based on the Python version you wish to install.
266
272
# it can be used to cover more than one VO in the grid sense.
267
273
# If you are going to setup DIRAC as a multi-VO instance, remove the VirtualOrganization parameter.
268
274
VirtualOrganization = Name of your VO
269
-
# Site name
275
+
# Server name
270
276
SiteName = DIRAC.HostName.ch
271
277
272
278
# Flag to skip download of CAs, on the first Server of your installation you need to get CAs
273
-
# installed by some external means
279
+
# installed by some external means, so do not change this flag.
274
280
SkipCADownload = yes
275
-
# Flag to use the server certificates
281
+
# Flag to use the server certificates. Do not change this flag.
276
282
UseServerCertificate = yes
277
-
# Configuration Server URL (This should point to the URL of at least one valid Configuration
278
-
# Service in your installation, for the primary server it should not used )
@@ -376,11 +371,13 @@ of the status of running DIRAC services, e.g.::
376
371
Name : Runit Uptime PID
377
372
Configuration_Server : Run 41 30268
378
373
Framework_SystemAdministrator : Run 21 30339
374
+
Framework_ComponentMonitoring : Run 21 30341
375
+
ResourceStatus_ResourceStatus : Run 21 30349
379
376
Tornado_Tornado : Run 11 30340
380
377
381
378
382
-
Now the basic services - Configuration, SystemAdministrator, TornadoComponentMonitoring and TornadoResourceStatus - are installed,
383
-
or at least their DBs should be installed, and their services up and running.
379
+
Now the basic services - Configuration, SystemAdministrator, ComponentMonitoring and ResourceStatus - are installed,
380
+
or at least their DBs should be installed, and the services connecting to them up and running.
384
381
385
382
There are anyway a couple more steps that should be done to fully activate the ComponentMonitoring and the ResourceStatus.
386
383
These steps can be found in the respective administration sessions of this documentation:
@@ -390,8 +387,7 @@ These steps can be found in the respective administration sessions of this docum
390
387
391
388
but, no hurry: you can do it later.
392
389
393
-
The rest of the installation can proceed using the DIRAC Administrator interface,
394
-
either command line (System Administrator Console) or using Web Portal (eventually, not available yet).
390
+
The rest of the installation can proceed using the DIRAC Administrator interface CLI.
395
391
396
392
It is also possible to include any number of additional systems, services, agents and databases to be installed by ``install_site.sh``.
397
393
@@ -407,11 +403,22 @@ It is also possible to include any number of additional systems, services, agent
407
403
killall runsv svlogd
408
404
killall runsvdir
409
405
406
+
407
+
Now it is time to add the necessary services for a minimal installation. In order to do so:
408
+
409
+
- install a client as described in the users' guide. Remember to use the same user certificate that you defined as "AdminUser".
410
+
- get a proxy using `dirac-proxy-init -g dirac_admin --no-upload`
411
+
- start the `dirac-admin-sysadmin-cli --host=$your_server_host` and inside install the services "Framework/BundleDelivery", "Framework/ProxyManager" (see instructions on the use of this CLI below)
412
+
- exit the CLI, and simply run `dirac-proxy-init`
413
+
414
+
410
415
.. _install_additional_server:
411
416
412
417
Additional server installation
413
418
------------------------------
414
419
420
+
Additional servers can be installed for redundacy purposes. This operation can always be done later, so for now the suggestion is to skip to the next session.
421
+
415
422
To add a new server to an already existing DIRAC Installation the procedure is similar to the one above.
416
423
You should perform all the preliminary steps to prepare the host for the installation. One additional
417
424
operation is the registration of the new host in the already functional Configuration Service.
@@ -444,8 +451,6 @@ operation is the registration of the new host in the already functional Configur
444
451
# Service in your installation, for the primary server it should not used)
0 commit comments