Changes between Version 3 and Version 4 of SfaInstallGEC9Demos


Ignore:
Timestamp:
10/13/10 16:37:32 (9 years ago)
Author:
chaos@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SfaInstallGEC9Demos

    v3 v4  
    44
    55We recommend sites use the tag `sfa-geni-gec9` from the PlanetLab GIT repository.
     6
     7IF you were already running an older version of SFA, including RPM-based versions sfa-0.9-14 or earlier, you will need to remove all old sfi credentials to handle a credential format change.  NOTE: if those credentials were used to create any slivers which are still active, you may lose the ability to modify those slivers.  Please contact the GPO before upgrading if this is a concern for you.  If you were already running a more recent SFA, this upgrade should be harmless, though it's always good to proceed with caution around any upgrade.
    68
    79= Variables =
     
    6971
    7072= Step 4: Configure SFA =
     73
     74== Step 4A: Clean old certificates if you were already running SFA ==
     75
     76IF you were already running an older version of SFA, including RPM-based versions sfa-0.9-14 or earlier, you will need to remove all old sfi credentials to handle a credential format change.  NOTE: if those credentials were used to create any slivers which are still active, you may lose the ability to modify those slivers.
     77
     78{{{
     79sudo /etc/init.d/sfa stop
     80sudo sfa-nuke-plc.py
     81sudo rm /etc/sfa/trusted_roots/*.gid
     82sudo rm -rf /var/lib/sfa/
     83rm ~/.sfi/*.gid
     84rm ~/.sfi/*.cert
     85rm ~/.sfi/*.cred
     86}}}
     87
     88== Step 4B: Create new configuration if this is the first time SFA has run on this PLC ==
    7189
    7290Note that many of these configuration options require variables taken from your myplc configuration itself.  See [#Variables] for details.