The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "GGUS:Change Implementation"
| Line 2: | Line 2: | ||
This is the GGUS change implementation process. For general information see the [[GGUS]] documentation pages. | This is the GGUS change implementation process. For general information see the [[GGUS]] documentation pages. | ||
=== | ====Requesting changes==== | ||
GGUS system consists of 3 instances: development, test and production. | Changes can be requested by submitting a ticket in either [https://rt.egi.eu/rt/Dashboards/2636/GGUS-Requirements GGUS EGI RT tracker] or [https://its.cern.ch/jira/browse/GGUS GGUS WLCG JIRA tracker]. | ||
All changes including patch installation for the OS are done on development instance first. | Alternatively a [https://ggus.eu/index.php?mode=ticket_submit|GGUS ticket] can be submitted. The GGUS team will then submit tickets in RT and JIRA for the record. | ||
In the next step changes are propagated to the test instances for intensive testing by GGUS team and by users from the communities if necessary. | |||
====Implementation process==== | |||
GGUS system consists of 3 instances: development, test and production.<br> | |||
All changes including patch installation for the OS are done on development instance first.<br> | |||
In the next step changes are propagated to the test instances for intensive testing by GGUS team and by users from the communities if necessary.<br> | |||
In case no problems occure on test instances changes are [[GGUS:Release Schedule|scheduled]] for installation on production instances. | In case no problems occure on test instances changes are [[GGUS:Release Schedule|scheduled]] for installation on production instances. | ||
===Software version and patch installation=== | ====Software version and patch installation==== | ||
GGUS software is under control of a version control system. | GGUS software is under control of a version control system.<br> | ||
For installation all changes are packaged in rpm files which are installed using package manager yum. | For installation all changes are packaged in rpm files which are installed using package manager yum.<br> | ||
This allows to keep control on the installed patches and roll back easily in case of unexpected problems after a change. | This allows to keep control on the installed patches and roll back easily in case of unexpected problems after a change. | ||
====Adding or removing support units==== | |||
Support units can be added or removed on the fly. This does not require a formal change.<br> | |||
However a ticket in [https://rt.egi.eu/rt/Dashboards/2636/GGUS-Requirements GGUS EGI RT tracker] and [https://its.cern.ch/jira/browse/GGUS GGUS WLCG JIRA tracker] are required for the record. These tracker tickets are part of the [https://ggus.eu/index.php?mode=release_notes GGUS release notes] of the next GGUS release. | |||
Revision as of 13:23, 12 January 2017
GGUS wiki / GGUS Documentation
GGUS – Global Grid User Support
This is the GGUS change implementation process. For general information see the GGUS documentation pages.
Requesting changes
Changes can be requested by submitting a ticket in either GGUS EGI RT tracker or GGUS WLCG JIRA tracker. Alternatively a ticket can be submitted. The GGUS team will then submit tickets in RT and JIRA for the record.
Implementation process
GGUS system consists of 3 instances: development, test and production.
All changes including patch installation for the OS are done on development instance first.
In the next step changes are propagated to the test instances for intensive testing by GGUS team and by users from the communities if necessary.
In case no problems occure on test instances changes are scheduled for installation on production instances.
Software version and patch installation
GGUS software is under control of a version control system.
For installation all changes are packaged in rpm files which are installed using package manager yum.
This allows to keep control on the installed patches and roll back easily in case of unexpected problems after a change.
Adding or removing support units
Support units can be added or removed on the fly. This does not require a formal change.
However a ticket in GGUS EGI RT tracker and GGUS WLCG JIRA tracker are required for the record. These tracker tickets are part of the GGUS release notes of the next GGUS release.