User Tools

Site Tools


documentation:configguide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
documentation:configguide [2016/02/04 12:14]
Christopher Price
documentation:configguide [2016/02/08 14:58] (current)
Ryota Mibu [Document structure]
Line 25: Line 25:
 All project specific files to be compiled into the Installation and Configuration guide must be stored in your projects configguide folder, templates for these files can be found in the opnfvdocs repo. All project specific files to be compiled into the Installation and Configuration guide must be stored in your projects configguide folder, templates for these files can be found in the opnfvdocs repo.
  
-| Installation and Configuration guide directory: |''<​repo>/​docs/​configguide/''​| +| Installation and Configuration guide directory: |''<​repo>/​docs/​configguide/''​
-| Installer configuration guide: ​                 |''<​repo>/​docs/​configguide/​installerconfig.rst''​| +| Installer configuration guide: ​                 |''<​repo>/​docs/​configguide/​installerconfig.rst''​|[[https://​gerrit.opnfv.org/​gerrit/​gitweb?​p=opnfvdocs.git;​a=blob;​f=docs/​configguide/​installerconfig.rst;​hb=HEAD|template]]
-| Feature configuration guide: ​                   |''<​repo>/​docs/​configguide/​featureconfig.rst''​| +| Feature configuration guide: ​                   |''<​repo>/​docs/​configguide/​featureconfig.rst''​|[[https://​gerrit.opnfv.org/​gerrit/​gitweb?​p=opnfvdocs.git;​a=blob;​f=docs/​configguide/​featureconfig.rst;​hb=HEAD|template]]
-| Post installation procedures: ​                  ​|''<​repo>/​docs/​configguide/​postinstall.rst''​|+| Post installation procedures: ​                  ​|''<​repo>/​docs/​configguide/​postinstall.rst''​|[[https://​gerrit.opnfv.org/​gerrit/​gitweb?​p=opnfvdocs.git;​a=blob;​f=docs/​configguide/​postinstall.rst;​hb=HEAD|template]]|
  
 ==== Including your Documentation ==== ==== Including your Documentation ====
Line 41: Line 41:
  
  
-You should then add the relevant information to the template that will explain the configuration of your feature and instructions for validating that the feature was enabled successfully //like checking the results of specific test cases//.+You should then add the relevant information to the template that will explain the configuration of your feature and instructions for validating that the feature was enabled successfully //like checking the results of specific test cases//.  Be sure to maintain the creative commons license from the template and ensure all your documentation files include the license information.
  
 Once your installer or feature documentation is ready you should ensure they are compiled into the master file by adding them to the master files in the opnfvdocs repository. ​ The index.rst file is structured in such a way that it will pull composite material via a staging file, staging files are identifiable by the "​-"​ in their file names. ​ Examples of the staging files are feature-config.rst,​ installer-config.rst and post-install.rst. ​ You should add references to your input documents in the correct locations in these staging files. ​ The relevant staging files for compiling project specific information are: Once your installer or feature documentation is ready you should ensure they are compiled into the master file by adding them to the master files in the opnfvdocs repository. ​ The index.rst file is structured in such a way that it will pull composite material via a staging file, staging files are identifiable by the "​-"​ in their file names. ​ Examples of the staging files are feature-config.rst,​ installer-config.rst and post-install.rst. ​ You should add references to your input documents in the correct locations in these staging files. ​ The relevant staging files for compiling project specific information are:
documentation/configguide.1454588084.txt.gz · Last modified: 2016/02/04 12:14 by Christopher Price