Difference between revisions of "1.0 Release Notes"
From GCube System
Manuele.simi (Talk | contribs) (New page: gCore <code>1.0</code> introduces the following changes: ====Changes Related to the gHN==== :* ''distribution'': there are now two distributions of the gHN, secure and standard distributi...) |
Manuele.simi (Talk | contribs) |
||
Line 4: | Line 4: | ||
:* ''distribution'': there are now two distributions of the gHN, secure and standard distribution | :* ''distribution'': there are now two distributions of the gHN, secure and standard distribution | ||
::* the secure distribution includes Local Services and Libraries from the standard onf plus: | ::* the secure distribution includes Local Services and Libraries from the standard onf plus: | ||
− | :::* | + | :::* enhanced <code>Delegation</code> service, in charge for providing local services with delegated credentials |
− | :::* | + | :::* enhanced <code>Security</code> library, with support for authentication and authorisation of gCube calls and policies management. |
:::* new <code>gcore-stop-container</code> script, to shutdown a secure container | :::* new <code>gcore-stop-container</code> script, to shutdown a secure container | ||
Line 11: | Line 11: | ||
::* the <code>GHNConfig.xml</code> has been extended with two additional configuration parameters: | ::* the <code>GHNConfig.xml</code> has been extended with two additional configuration parameters: | ||
:::* '''allowedScopes''', letting the Site Manager to decide to which VOs the gHN can be joined in the future (upon VO Manager decisions) | :::* '''allowedScopes''', letting the Site Manager to decide to which VOs the gHN can be joined in the future (upon VO Manager decisions) | ||
− | :::* '''trustedGHNSynchInterval''', how often the gHN refreshes the list of trusted | + | :::* '''trustedGHNSynchInterval''', how often the gHN refreshes the list of trusted gHNs (in seconds). |
Both of the are taken into consideration only in case of secure distribution. | Both of the are taken into consideration only in case of secure distribution. | ||
+ | ::* <code>$X509_USER_PROXY</code> environment variable is now exploited to contact the gContainer from outside the process. It is expected to contain a valid proxy accepted by the local gContainer process. | ||
====Changes Related to Services ==== | ====Changes Related to Services ==== | ||
Line 18: | Line 19: | ||
====Changes Related to the Documentation ==== | ====Changes Related to the Documentation ==== | ||
− | :* ''new/revised sections in the | + | :* ''new/revised sections in the Administrator's Guide''. |
− | :: | + | :: Administrator's Guide has an enriched [[Administrator_Guide#Configuration| configuration]] section on how to setup a secure gHN. |
Revision as of 16:41, 4 February 2010
gCore 1.0
introduces the following changes:
Changes Related to the gHN
- distribution: there are now two distributions of the gHN, secure and standard distribution
- the secure distribution includes Local Services and Libraries from the standard onf plus:
- enhanced
Delegation
service, in charge for providing local services with delegated credentials - enhanced
Security
library, with support for authentication and authorisation of gCube calls and policies management. - new
gcore-stop-container
script, to shutdown a secure container
- enhanced
- configuration
- the
GHNConfig.xml
has been extended with two additional configuration parameters:
- allowedScopes, letting the Site Manager to decide to which VOs the gHN can be joined in the future (upon VO Manager decisions)
- trustedGHNSynchInterval, how often the gHN refreshes the list of trusted gHNs (in seconds).
- the
Both of the are taken into consideration only in case of secure distribution.
-
$X509_USER_PROXY
environment variable is now exploited to contact the gContainer from outside the process. It is expected to contain a valid proxy accepted by the local gContainer process.
-
Changes Related to Services
None
Changes Related to the Documentation
- new/revised sections in the Administrator's Guide.
- Administrator's Guide has an enriched configuration section on how to setup a secure gHN.