Changes between Version 23 and Version 24 of FlowVisor


Ignore:
Timestamp:
09/05/13 16:27:39 (6 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FlowVisor

    v23 v24  
    3939== Version ==
    4040
    41 The GPO had recommended version 1.0.8 for GENI sites, but we've since found some showstopper issues with it, and are not recommending uprading at this time to sites running 0.8.17.
    42 
    43 Sites that haven't yet upgraded are mostly running 0.8.17; existing GENI racks may be running older versions of 0.8.
     41The GPO currently recommends version 0.8.17 for GENI sites.
     42
     43The GPO had briefly recommended version 1.0.8 for GENI sites, but we've since found some showstopper issues with it, and are not at this time recommending it.
     44
     45Most sites are running 0.8.17, except for the few who upgraded to 1.0.8; some GENI racks may also be running older versions of 0.8.
    4446
    4547=== GENI deployment process ===
     
    8385(That last line is just to remove the warning about the XMLRPC interface being deprecated; we know, and don't need a reminder every time we run fvctl.)
    8486
    85 The rest of this page assumes that you've done this, and that `fvctl` runs the XML version of fvctl.
     87The rest of this page assumes that you've done this, and that `fvctl` runs the XML version of fvctl (and is thus also compatible with FV 0.8.)
    8688
    8789== Initial configuration ==
    8890
    89 The default configuration of !FlowVisor is generally suitable for GENI sites, except that we recommend the XMLRPC API for now. (See above for more info, including commands to make `/usr/bin/fvctl` point to the XML version.)
     91The default configuration of !FlowVisor is generally suitable for GENI sites, except that we recommend tuning the log level to 'WARN'.
    9092
    9193=== Admin password ===
     
    104106
    105107The rest of this page assumes that you've done that.
     108
     109=== Log level ===
     110
     111The default log level for !FlowVisor is too verbose. To change it, edit `/etc/flowvisor/fvlog.config`, changing the log4j.rootCategory setting to "WARN", e.g.
     112
     113{{{
     114sudo sed -i -e 's/log4j.rootCategory=[A-Z]*,/log4j.rootCategory=WARN,/' /etc/flowvisor/fvlog.config
     115}}}
     116
     117(and then restart !FlowVisor)
    106118
    107119=== Version holding ===