Changes between Version 139 and Version 140 of Doc/gLite/TemplateCustomization


Ignore:
Timestamp:
Dec 16, 2009, 8:42:53 PM (16 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/gLite/TemplateCustomization

    v139 v140  
    925925This is critical for the security to restrict the number of people allowed access to the VOBOX. By default, only people with the VO SW manager role can log into the VO box. To change this configuration, refer to section on [#MappingofVOMSgroupsrolesintogrid-mapfile VOMS groups/roles mapping], but be sure you really need to allow other roles as it can give unwanted users access to privilege services.
    926926
    927 The configuration templates for the VOBOX enforce there is only one VO configured for acess to VOBOX specific services. This VO is declared using the `VOS` variable, as for other machine types. If you want to give other VOs access to the VOBOX for the management and operation of the VOBOX, you need to explicitly allow them using the variable `VOBOX_OPERATION_VOS`. This variable is a list of VOs considered as operation VOs. By default, this list is only VO `ops`. If the VOs listed in this variable are not listed in  `VOS`, they are automatically added.
     927The configuration templates for the VOBOX enforce there is only one VO configured for acess to VOBOX specific services. This VO must be declared using the `VOS` variable, as for other machine types. If you want to give other VOs access to the VOBOX for the management and operation of the VOBOX, you need to explicitly allow them using the variable `VOBOX_OPERATION_VOS`. This variable is a list of VOs considered as operation VOs. By default, this list is only VO `ops`. If the VOs listed in this variable are not listed in  `VOS`, they are automatically added.
     928
     929There are some other variables available to tune the VOBOX configuration but the default should generally be appropriate. The main ones are:
     930 * `VOBOX_TCP_MAX_BUFFER_SIZE`: the maximum TCP buffer size to use. This is critical to reach good performances on high speed network. Default: 8388608.
     931 * `VOBOX_TCP_MAX_BACKLOG`: another critical TCP congestion control parameter to reach high throughput and good performances. Default: 250000.
    928932
    929933In addition, most of the configuration variables available for the UI, in particular those related to gsissh server, apply for VOBOX too. In particular, it is generally necessary to [#CustomizingDefaultEnvironment define] the default MyProxy server (`MYPROXY_DEFAULT_SERVER`).