Tags:
create new tag
, view all tags
-- TomLehman - 2013-11-12

MAXREGIONAL.S5.a: Continue to support the stitching interoperation and testing between GENI Racks/Aggregates, and across network infrastructures such as Internet2 ION, AL2S, regional networks, and other networks that may be available for GENI stitching use.

Status:

During this period we continued supporting stitching activities in a variety of environments. This include stitching between GENI Racks across ION and as well as stitching to iMinds in Belgium. The iMinds infrastructure is currently connected to ION via static configuration of VLANs across GEANT and the Belgium National network. For the general stitching across ION we worked with Internet2 to upgrade the ION AM to a newer version of the MAX Aggregate Manager software. We also worked with the GPO to define an ION AM Software Release Plan. A high level overview of that plans is included below.

We also continued our discussions with Internet2 regarding support for stitching on AL2S. They are making progress but there is still more for them to complete. There is some indication that Internet2 may be ready to test AL2S GENI stitching sometime in May 2014.
We also supported the GPO in the deployment of a new monitoring infrastructure. This included deploying the GPO provided software infrastructure on the MAX Aggregate.

ION AM Software Release and Upgrade Steps-v2:

1. The released/installed version is identified by a SVN branch version number. Currently ION is running this version:

https://svn.maxgigapop.net/svn/geni-aggregate/branches/r2.0/

A tarball from svn export is also included here:

https://wiki.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingSoftware

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 changes
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 branch in SVN for the ION AM
  • This web site will be updated with the new software release information:
  • Summarize the SFA and MyPLC 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/MyPLC 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.

Edit | Attach | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r4 - 2014-04-18 - TomLehman
 
  • Edit
  • Attach
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback