Difference between revisions of "Configuration management"

From VyOS Wiki
Jump to: navigation, search
(Configuration Terminology)
(Configuration Terminology)
Line 1: Line 1:
 
{{TOC right}}
 
{{TOC right}}
  
= Configuration Terminology =
+
= Configuration Overview =
 +
 
 +
== Configuration Terminology ==
  
 
A VyOS system has three major types of configurations:
 
A VyOS system has three major types of configurations:

Revision as of 12:31, 30 August 2017

Configuration Overview

Configuration Terminology

A VyOS system has three major types of configurations:

Active or running configuration
The active or running configuration is the system configuration that is loaded and currently being used by VyOS.
Working configuration
The working configuration is the configuration which is currently being modified in configuration mode. Changes made to the working configuration do not go into effect until the changes are committed with the commit command. At which time the working configuration will become the active or running configuration.
Saved configuration
A saved configuration is a configuration saved to a file using the save command. There can be multiple configuration files. The default or "boot" configuration is saved and loaded from the file config.boot.

Configuration Information Location

Saved configuration files are stored in the directory /config. The boot configuration is named config.boot. The config directory has a number of sub-directories:

  • archive
  • auth
  • scripts
  • support
  • url-filtering
  • user-data
archive
The archive directory stores archived versions of the configuration
auth
The auth directory stores security related information referenced in the configuration tree. OpenVPN and IPSec certificates and RSA/IPSec keys. This structure can be added/extended and it is the recommended best practice to add any custom security related data in this directory. For example, X.509 certificates or certificate authorities should be added to appropriate sub-directories under the auth directory. This ensures that security information is preserved during the upgrade process.
scripts
The scripts directory store scripts referenced from within the configuration nodes. Used for VRRP transition scripts and WAN load-balancing. It is a recommended best practice to add scripts to this directory to ensure that they are preserved during a system upgrade.
support
The support directory stores system information created by the show tech-support save command.
url-filtering
The url-filtering directory stores the files and URL-filtering database on which the web proxy and URL filtering depend.
user-data
The user-data directory stores user scripts and data. It is a recommended best practice to store user scripts and data in this directory to ensure that it is preserved during system upgrades.