wiki:JOhrenSandbox/GIMINotes8.1.2012

Notes from Post-GEC14 testing of GIMI


Status of All Tests


8/1/2012 Test execution notes have been moved to GIMIAcceptanceTests/GIMITest8.1.2012

Release Management concerns

As GENI experimenters and operators start to use GIMI and the code evolves, there are some release management issues that we should consider.

  1. Code Delivery
    • How will updates be delivered to the end users?
      • Packages? Tarballs? Repository?
    • What should be included in these releases?
    • Where will these be published?
  • OML/OMF will be delivered in their respective packages
  • hook script will be in the OML repository. Delivered in OML server package??
  • visualization script (and supporting scripts)? ED file and supporting scripts?
  1. Versions
    • How will GIMI releases be named?
    • As users report problems and we create tickets, we will need to identify what version of the software was used so the issue can be reproduced and troubleshooted.
    • What versions do we need to track? What dependencies do we have? (e.g. OML server 2.8, iperf-oml2)
  2. Image Updates
    • How often will new static images be created?
      • Shortly before each GEC
    • How will updates be handled between static image releases? Postboot scripts?
      • Yes
    • How does the user identify which image they are running? Can they tell from within the running node?
Last modified 9 years ago Last modified on 08/15/12 14:27:09

Attachments (1)

Download all attachments as: .zip