[[PageOutline]] '''[wiki:GENIExperimenter/Tutorials/SystematicExprCaseStudy#ATutorialonSystematicExperimentalDesign A Tutorial on Systematic Experimental Design]''' '''[wiki:GENIExperimenter/Tutorials/SystematicExprCaseStudy/InstallSoftware Step I: Single Node]''' '''[wiki:GENIExperimenter/Tutorials/SystematicExprCaseStudy/SmallTopo Step II: Small Topology]''' {{{ #!html
Image Map
}}} = 7. Save RSpec File and Release Resources = == a. Version Control == It is important to save your RSpec at each step. There are three advantages: * First, it is convenient to bring up the same topology with the same configuration whenever there is a need. * Second, we can add more nodes, links, and even more install scripts to existing RSpec, instead of starting all over again. * Third, version control on RSpec is helpful to track errors and debugging issues. So far, we have created four RSpec files for the 4-router topology. If every thing works properly, we can rename `4node-v4.rspec` to `4node-final.rspec` as the final version for the 4node topology for future usage. == a. Tear Down Resources == Since we have saved the RSpec file, we can easily bring up the experiment again. Thus, it is not necessary to keep the resources if we do not need to run the experiment any more. We can release the resources by using either Flack or omni. '''[wiki:GENIExperimenter/Tutorials/SystematicExprCaseStudy/SmallTopo/Execute Small Topology: Execute]''' '''[wiki:GENIExperimenter/Tutorials/SystematicExprCaseStudy/ScalingUp Step III: Scaling Up]'''