Tags:
create new tag
, view all tags

Network Stitching Software

Stitching Computation Service (SCS)

DCN Aggregate Manager (AM)

ION AM Software Release and Upgrade Plan

1) The released/installed version is identified by a GIT release tag. Currently ION is running this version:

2) MAX AM Upgrade Procedure
  • MAX Uses a development instance of the MAX AM to test changes as possible in the development environment.
  • The operational MAX AM is upgraded as needed.
  • System Testing. After an upgrade, the MAX AM testing is based on common use case and change specific testing based on experience.
  • If testing was not successful, MAX AM is rolled back to a previous version
  • As a result the above actions, MAX AM will often be running newer software then what ION AM instance is running.
3) ION AM Upgrade Procedure

Any stable version running on the MAX AM is a candidate for ION AM upgrade. When time for an upgrade, the following will be done:

a) MAX will:

  • generate a summary of the new features and changes as compared to the last release
  • provide information on any recommended test cases based on the new features and/or change
b) GPO will conduct testing against the MAX AM. This testing will based on GPOs standard testing procedures and any testing procedures which may be unique to the specific release.

c) If testing in item b is successful, then MAX will do the following:

  • create a release branch (if major release) in rX.Y format and/or release tag in vX.Y.Z format on github for the ION AM
  • This web site will be updated with the new software release information
  • Summarize the SFA version and patch level so that Internet2 can verify that the ION AM is at the proper level. MAX may also provide the specific SFA patches needed.
d) Internet2 will then download the new software and use the standard installation instructions as their guide for the upgrade: e) After the ION AM upgrade, the system is tested. Internet2 and MAX will do some preliminary testing before handing over to GPO to do the formal testing.

f) If testing in item e is not successful, then issues will be resolved, or system will be rolled back to last working configuration.


SCS Software Release and Upgrade Plan

1) The released/installed version is identified by a GIT release tag. Currently the GRNOC Production SCS and MAX Test SCS are running this version:

2) Development SCS Upgrade Procedure
  • MAX also runs a Development SCS. This is an instance of the SCS used to test changes as part of the development environment.
  • The GENI Production SCS is upgraded as needed.
  • System Testing. After an upgrade to the Development SCS, MAX conducts testing based on common use cases and change specific testing based on experience.
  • If testing was not successful, MAX Development SCS rolled back to a previous version
  • As a result the above actions, MAX Development SCS will often be running newer software then what GENI Production SCS instance is running.
3) Production SCS Upgrade Procedure

Any stable version running on the MAX Development SCS is a candidate for Production SCS upgrade. When time for an upgrade, the following will be done:

a) MAX will:

  • generate a summary of the new features and changes as compared to the last release
  • provide information on any recommended test cases based on the new features and/or change
b) GPO will conduct testing against the MAX Development SCS. This testing will based on GPOs standard testing procedures and any testing procedures which may be unique to the specific release.

c) If testing in item b is successful, then MAX will do the following:

d) Internet2 will then download the new software and use the standard installation instructions as their guide for the upgrade:
  • See README file in top level of SCS distribution
    • Any upgrade specific changes to the installation instructions will be provided as needed.
e) After the Production SCS upgrade, the system is tested. Internet2 and MAX will do some preliminary testing before handing over to GPO to do the formal testing.

f) If testing in item e is not successful, then issues will be resolved, or system will be rolled back to last working configuration.


Topic revision: r17 - 2015-05-26 - XiYang
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback