- Detailed test plan for IG-ADM-5: Software Update Test
- Page format
- Status of test
- High-level description from test plan
- Step 1: Review relevant rack documentation about software upgrades
- Step 2: Identify one or more software packages to upgrade
- Step 3: For each package, test the software before upgrading it
- Step 4: Upgrade each package
- Step 5: For each package, test the software after upgrading it
Detailed test plan for IG-ADM-5: Software Update Test
This page is GPO's working page for performing IG-ADM-5. It is public for informational purposes, but it is not an official status report. See GENIRacksHome/InstageniRacks/AcceptanceTestStatus for the current status of InstaGENI acceptance tests.
Page format
- The status chart summarizes the state of this test
- The high-level description from test plan contains text copied exactly from the public test plan and acceptance criteria pages.
- The steps contain things i will actually do/verify:
- Steps may be composed of related substeps where i find this useful for clarity
- Each step is either a preparatory step (identified by "(prep)") or a verification step (the default):
- Preparatory steps are just things we have to do. They're not tests of the rack, but are prerequisites for subsequent verification steps
- Verification steps are steps in which we will actually look at rack output and make sure it is as expected. They contain a Using: block, which lists the steps to run the verification, and an Expect: block which lists what outcome is expected for the test to pass.
Status of test
See GENIRacksHome/InstageniRacks/AcceptanceTestStatus for the meanings of test states.
Step | State | Date completed | Open Tickets | Closed Tickets/Comments |
1 | Color(green,Pass)? | 2013-03-14 | ||
2 | Color(green,Pass)? | 2013-03-14 | ||
3 | Color(green,Pass)? | 2013-03-14 | ||
4 | Color(green,Pass)? | 2013-03-14 | ||
5 | Color(green,Pass)? | 2013-03-14 |
High-level description from test plan
In this test, we update software on the rack as a test of the software update procedure.
Procedure
- Review relevant rack documentation about software upgrades.
- Identify one or more software packages to upgrade.
- For each package, test the software before upgrading it.
- Upgrade each package.
- For each package, test the software after upgrading it.
Criteria to verify as part of this test
- VII.07. A site administrator can perform software and OS updates on the rack. (F.5)
Step 1: Review relevant rack documentation about software upgrades
Results of testing Step 1 on 2013-03-14
http://www.protogeni.net/wiki/instageni/software-update-process, has documentation about the InstaGENI software update process; it needs to be fleshed out, but at least there's a page.
Step 2: Identify one or more software packages to upgrade
We decided to upgrade tango-monitor-foam, as documented at http://groups.geni.net/geni/wiki/TangoGeniMonitoring/FoamConfiguration.
Step 3: For each package, test the software before upgrading it
I browsed to https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl?method=aggregate_details;aggregate=foam.instageni.gpolab.bbn.com%3A3626 at 10:39 Eastern, logged in, and observed that the "Last Updated" time was "2013-03-14 14:35:27" (UTC). That's about four minutes in the past, which shows that updates are currently working. I also observed that the "Version" string was "0.8.2". That format shows that the data is being reported by tango-monitor-foam 0.4.
Step 4: Upgrade each package
I followed the instructions at http://groups.geni.net/geni/wiki/TangoGeniMonitoring/FoamConfiguration.
I downloadeded the the tango-monitor-foam_0.5.0-1.deb package file from http://software.geni.net/local-sw/, and copied it into my home directory as ~/tango-monitor-foam_0.5.0-1_all.deb.
Then, I installed tango-monitor-gmoc, following the instructions at http://groups.geni.net/geni/wiki/TangoGeniMonitoring/GmocConfiguration.
I downloaded the tango-monitor-gmoc_1.2.12-1_all.deb package file from http://software.geni.net/local-sw/, and copied it into my home directory as ~/tango-monitor-gmoc_1.2.12-1_all.deb.
Since I'm installing tango-monitor-gmoc as part of a tango-monitor-foam upgrade, I installed both packages at once. On foam.instageni.gpolab.bbn.com:
[10:49:44] jbs@foam.instageni.gpolab.bbn.com:/home/jbs +$ sudo dpkg -i ~/tango-monitor-gmoc_1.2.12-1_all.deb ~/tango-monitor-foam_0.5.0-1_all.deb Selecting previously unselected package tango-monitor-gmoc. (Reading database ... 54595 files and directories currently installed.) Unpacking tango-monitor-gmoc (from .../tango-monitor-gmoc_1.2.12-1_all.deb) ... dpkg: error processing /home/jbs/tango-monitor-gmoc_1.2.12-1_all.deb (--install): trying to overwrite '/usr/local/lib/gmoc.py', which is also in package tango-monitor-foam 0.4-2 Preparing to replace tango-monitor-foam 0.4-2 (using .../tango-monitor-foam_0.5.0-1_all.deb) ... Unpacking replacement tango-monitor-foam ... dpkg: dependency problems prevent configuration of tango-monitor-foam: tango-monitor-foam depends on tango-monitor-gmoc; however: Package tango-monitor-gmoc is not installed. dpkg: error processing tango-monitor-foam (--install): dependency problems - leaving unconfigured Errors were encountered while processing: /home/jbs/tango-monitor-gmoc_1.2.12-1_all.deb tango-monitor-foam [10:49:49] jbs@foam.instageni.gpolab.bbn.com:/home/jbs +$ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libnumber-compare-perl ttf-dejavu-extra ttf-dejavu-core libfile-find-rule-perl libdbi1 librrd4 libcairo2 libthai-data librrds-perl libdatrie1 fontconfig libpixman-1-0 libxml-writer-perl python-rrdtool libxft2 fontconfig-config libthai0 libxrender1 libtext-glob-perl ttf-dejavu libfontconfig1 libpango1.0-0 libxcb-render0 libxcb-shm0 Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: tango-monitor-foam 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? (Reading database ... 54593 files and directories currently installed.) Removing tango-monitor-foam ... dpkg: warning: while removing tango-monitor-foam, directory '/usr/local/lib' not empty so not removed. [10:52:53] jbs@foam.instageni.gpolab.bbn.com:/home/jbs +$ sudo dpkg -i ~/tango-monitor-gmoc_1.2.12-1_all.deb ~/tango-monitor-foam_0.5.0-1_all.deb (Reading database ... 54579 files and directories currently installed.) Unpacking tango-monitor-gmoc (from .../tango-monitor-gmoc_1.2.12-1_all.deb) ... Selecting previously unselected package tango-monitor-foam. Unpacking tango-monitor-foam (from .../tango-monitor-foam_0.5.0-1_all.deb) ... Setting up tango-monitor-gmoc (1.2.12-1) ... Setting up tango-monitor-foam (0.5.0-1) ...
That's all as expected, according to the docs.
None of the other steps from the docs are necessary if you're upgrading rather than installing for the first time.
Step 5: For each package, test the software after upgrading it
I browsed to https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl?method=aggregate_details;aggregate=foam.instageni.gpolab.bbn.com%3A3626 at 11:02 Eastern, and observed that the "Last Updated" time was "2013-03-14 15:00:22" (UTC). That's about two minutes in the past, which shows that updates are still (or again) working.
I also observed that the "Version" string was "foam-0.8.2,flowvisor-0.8.14". That format shows that the data is being reported by tango-monitor-foam 0.5.
So, everything seems to have worked as expected, with no issues.