Automatic user configuration - Revision history

Alex Buts: /* Historic Automatic user configuration */

2023-01-09T17:12:24Z

Historic Automatic user configuration

Alex Buts at 17:11, 9 January 2023

2023-01-09T17:11:54Z

Alex Buts: /* Automatic user configuration */

2023-01-09T17:11:29Z

Automatic user configuration

Alex Buts: /* Automatic user configuration */

2023-01-09T16:57:11Z

Automatic user configuration

Alex Buts: /* Automatic user configuration */

2017-03-22T18:15:25Z

Automatic user configuration

Alex Buts: /* ISISOMPUTE User creation workflow */

2016-10-10T17:09:05Z

ISISOMPUTE User creation workflow

Alex Buts: /* ISISOMPUTE User creation workflow */

2016-07-04T09:38:20Z

ISISOMPUTE User creation workflow

Alex Buts: /* ISISOMPUTE User creation workflow */

2016-07-04T09:37:35Z

ISISOMPUTE User creation workflow

Alex Buts: /* Automatic user configuration */

2016-06-22T12:24:51Z

Automatic user configuration

Alex Buts: /* Automatic user configuration */

2016-06-22T12:24:17Z

Automatic user configuration

← Older revision		Revision as of 17:12, 9 January 2023
Line 1:		Line 1:
	On 01/01/2023 this information become outdated. [mailto:support@analysis.stfc.ac.uk IDAaaS Support Analysis team] is solely responsible for auto-configuring IDAaaS machines. The information below is remaining for references purposes and stating how it used to work in the past.		On 01/01/2023 this information become outdated. [mailto:support@analysis.stfc.ac.uk IDAaaS Support Analysis team] is solely responsible for auto-configuring IDAaaS machines. The information below is remaining for references purposes and stating how it used to work in the past.

−	== ~~Historic Automatic~~ user configuration ==	+	== Historical automatic user configuration procedure ==

← Older revision		Revision as of 17:11, 9 January 2023
Line 1:		Line 1:
−	== Automatic user configuration ==	+	On 01/01/2023 this information become outdated. [mailto:support@analysis.stfc.ac.uk IDAaaS Support Analysis team] is solely responsible for auto-configuring IDAaaS machines. The information below is remaining for references purposes and stating how it used to work in the past.
		+
		+	== Historic Automatic user configuration ==

−	On 01/01/2023 this information become outdated. [mailto:support@analysis.stfc.ac.uk IDAaaS Support Analysis team] is solely responsible for auto-configuring IDAaaS machines. The information below is remaining for references purposes and stating how it used to work in the past.

	When an experiment is approved and scheduled by instrument scientist, [http://www.isis.stfc.ac.uk/user-office/ User office] assigns a user with his/her federal ID, which allows user to access ISIS network including [https://isis.analysis.stfc.ac.uk/workspaces/ IDAaaS virtual machines] and provides appropriate information to [Catalog service], giving the user rights to access the data through the Catalog.		When an experiment is approved and scheduled by instrument scientist, [http://www.isis.stfc.ac.uk/user-office/ User office] assigns a user with his/her federal ID, which allows user to access ISIS network including [https://isis.analysis.stfc.ac.uk/workspaces/ IDAaaS virtual machines] and provides appropriate information to [Catalog service], giving the user rights to access the data through the Catalog.

← Older revision		Revision as of 17:11, 9 January 2023
Line 1:		Line 1:
	== Automatic user configuration ==		== Automatic user configuration ==
		+
		+	On 01/01/2023 this information become outdated. [mailto:support@analysis.stfc.ac.uk IDAaaS Support Analysis team] is solely responsible for auto-configuring IDAaaS machines. The information below is remaining for references purposes and stating how it used to work in the past.

	When an experiment is approved and scheduled by instrument scientist, [http://www.isis.stfc.ac.uk/user-office/ User office] assigns a user with his/her federal ID, which allows user to access ISIS network including [https://isis.analysis.stfc.ac.uk/workspaces/ IDAaaS virtual machines] and provides appropriate information to [Catalog service], giving the user rights to access the data through the Catalog.		When an experiment is approved and scheduled by instrument scientist, [http://www.isis.stfc.ac.uk/user-office/ User office] assigns a user with his/her federal ID, which allows user to access ISIS network including [https://isis.analysis.stfc.ac.uk/workspaces/ IDAaaS virtual machines] and provides appropriate information to [Catalog service], giving the user rights to access the data through the Catalog.

@@ Line 1: / Line 1: @@
 == Automatic user configuration ==
-When an experiment is approved and scheduled by instrument scientist, [http://www.isis.stfc.ac.uk/user-office/ User office] assigns a user with his/her federal ID, which allows user to access ISIS network including [http://isiscompute.nd.rl.ac.uk/ isiscompute servers] and provides appropriate information to [Catalog service], giving the user rights to access the data through the Catalog.
+When an experiment is approved and scheduled by instrument scientist, [http://www.isis.stfc.ac.uk/user-office/ User office] assigns a user with his/her federal ID, which allows user to access ISIS network including [https://isis.analysis.stfc.ac.uk/workspaces/ IDAaaS virtual machines] and provides appropriate information to [Catalog service], giving the user rights to access the data through the Catalog.
 At some stage, special [http://icatingest2.isis.cclrc.ac.uk/excitations.txt information file], which defines the participants of the experiments and the scientists who have access to the data of this experiment is placed on the [http://icatingest2.isis.cclrc.ac.uk/excitations.txt internal server] where it is accessed and automatically processed by [https://github.com/FITLinuxSupport/analysisscripts/blob/master/Build_Mantid_config.py issicompute configuration script]. The format of the file is .json and the sample contents is provided below.

@@ Line 1: / Line 1: @@
 == Automatic user configuration ==
-When an experiment is approved and scheduled by instrument scientist, [http://www.isis.stfc.ac.uk/user-office/ User office] assigns a user with his/her federal ID, which allows user to access ISIS network including [http://www.isis.stfc.ac.uk/groups/excitations/data-analysis-computers/connecting-to-isiscomputendrlacuk-using-nomachine15120.html isiscompute servers] and provides appropriate information to [Catalog service], giving the user rights to access the data through the Catalog.
+When an experiment is approved and scheduled by instrument scientist, [http://www.isis.stfc.ac.uk/user-office/ User office] assigns a user with his/her federal ID, which allows user to access ISIS network including [http://isiscompute.nd.rl.ac.uk/ isiscompute servers] and provides appropriate information to [Catalog service], giving the user rights to access the data through the Catalog.
 At some stage, special [http://icatingest2.isis.cclrc.ac.uk/excitations.txt information file], which defines the participants of the experiments and the scientists who have access to the data of this experiment is placed on the [http://icatingest2.isis.cclrc.ac.uk/excitations.txt internal server] where it is accessed and automatically processed by [https://github.com/FITLinuxSupport/analysisscripts/blob/master/Build_Mantid_config.py issicompute configuration script]. The format of the file is .json and the sample contents is provided below.

@@ Line 58: / Line 58: @@
 # Emails user office to create&renew FedID-s
 # Generates [http://icatingest2.isis.cclrc.ac.uk/excitations.txt information file] containing RB number, Instrument, Cycle, visitors names & FedIDs
-| Hannah Griffin
+| Contact responsible from [mailto:isisdata@stfc.ac.uk data acquisition support group]
 |-
 | 6

@@ Line 19: / Line 19: @@
 [[File:UserConfigWorkflow.png|1000px]]
-Less visual but more detailed description of the workflow is provided in the table below. The number of the rows in the table correspond to the number of the blocks in the diagram above.
+Less visual but more detailed description of the workflow is provided in the table below. The number of the row in the table corresponds to the number of the block in the diagram above.
 {| class="wikitable" style="color:blue;

← Older revision		Revision as of 12:24, 22 June 2016
Line 7:		Line 7:
	The automatic isiscompute configuration script runs twice a day on [https://isiscompute.nd.rl.ac.uk/nxwebplayer isiscompue server] processing the information file, creating user accounts and appropriate RB folders and giving users permissions to access their RB folders on the basis of the information file. [mailto:alex.buts@stfc.ac.uk Alex Buts] and [https://www.facilities.rl.ac.uk/itsupport/default.aspx FBU IT support] [mailto:FITServiceDesk@stfc.ac.uk FBU IT support (Jeffs Warren)] have access and can modify this script. At the final stage this script runs [https://github.com/mantidproject/mantid/blob/master/scripts/Inelastic/Direct/ISISDirecInelasticConfig.py the Mantid configuration script for inelastic instruments], which configures each user's Mantid to use appropriate [[Experimental Data]], [[Instrument parameters and Instrument definitions]], necessary to reduce experimental data. It also provides users with initial version of [[Reduction scripts]], which users should modify to their requests according to the [http://shadow.nd.rl.ac.uk/wiki/idr/index.php/ISIS_direct_reduction_script_description. description], using help of their instrument scientist if necessary. [mailto:alex.buts@stfc.ac.uk Alex Buts] is responsible for maintaining this script.		The automatic isiscompute configuration script runs twice a day on [https://isiscompute.nd.rl.ac.uk/nxwebplayer isiscompue server] processing the information file, creating user accounts and appropriate RB folders and giving users permissions to access their RB folders on the basis of the information file. [mailto:alex.buts@stfc.ac.uk Alex Buts] and [https://www.facilities.rl.ac.uk/itsupport/default.aspx FBU IT support] [mailto:FITServiceDesk@stfc.ac.uk FBU IT support (Jeffs Warren)] have access and can modify this script. At the final stage this script runs [https://github.com/mantidproject/mantid/blob/master/scripts/Inelastic/Direct/ISISDirecInelasticConfig.py the Mantid configuration script for inelastic instruments], which configures each user's Mantid to use appropriate [[Experimental Data]], [[Instrument parameters and Instrument definitions]], necessary to reduce experimental data. It also provides users with initial version of [[Reduction scripts]], which users should modify to their requests according to the [http://shadow.nd.rl.ac.uk/wiki/idr/index.php/ISIS_direct_reduction_script_description. description], using help of their instrument scientist if necessary. [mailto:alex.buts@stfc.ac.uk Alex Buts] is responsible for maintaining this script.

−	When initial [[Reduction scripts]] are copied to user's RB folder from the [https://github.com/mantidproject/scriptrepository/tree/master/direct_inelastic Mantid Script Repository] sample folder, script date is set to the experiment start date and the time -- exact midnight of the start date. Configuration script running twice a day checks this date and if it does not changed, replaces the existing script with the script, found in the Mantid Script Repository sample folder. If somebody touched the copied script, its date and time changes and [https://github.com/mantidproject/mantid/blob/master/scripts/Inelastic/Direct/ISISDirecInelasticConfig.py autoconfiguration script] stops replacing the file.	+	When initial [[Reduction scripts]] are copied to user's RB folder from the [https://github.com/mantidproject/scriptrepository/tree/master/direct_inelastic Mantid Script Repository] sample folder, script date is set to the experiment start date and the time -- to the exact midnight of the start date. Configuration script running twice a day checks this date and if it does not changed, replaces the existing script with the script, found in the Mantid Script Repository sample folder. If somebody touched the copied script, its date and time changes and [https://github.com/mantidproject/mantid/blob/master/scripts/Inelastic/Direct/ISISDirecInelasticConfig.py autoconfiguration script] stops replacing the file.