Configuration tips and tricks: Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
== Introduction == | == Introduction == | ||
We've been here: all those acronyms, variable names and definitions may be overwhelming. | We've all been here: all those acronyms, variable names and definitions may be overwhelming. | ||
These guidelines | These guidelines help users to discover the power of nGeniusONE and explore its full potential. | ||
| | ||
| Line 12: | Line 12: | ||
=== Captitals === | === Captitals === | ||
Use as much as possible UPPER CASE for naming appliactions,communities, services ... . Don't use spaces; replace them with underscore '_" or hyphen "-". | |||
| |||
=== Meaningfull names === | |||
Use meaingfull names for naming appliactions,communities, services ... . | |||
Don't use space; replace with underscore '_" or hyphen "-". | |||
| | ||
| Line 18: | Line 26: | ||
=== Prefixes === | === Prefixes === | ||
The use of prefix will clarify which varable is used on reports. It allows for easy filtering and alphabetic ordening of longer lists. | |||
==== Service Configuration ==== | ==== Module Service Configuration ==== | ||
*as_ = Application Service | *as_ = Application Service | ||
*ns_ = Network Service | *ns_ = Network Service | ||
* | * | ||
Module Global Settings | |||
*ls_ = Location Key | *ls_ = Location Key of type Site | ||
*lv_ = Location Key | *lv_ = Location Key of type VLAN | ||
*lr_ = Location Key of type VRF | |||
*cc_ = Client Community | *cc_ = Client Community | ||
*sc_ = Server Community | *sc_ = Server Community | ||
*tc_ = Telephony Community | *tc_ = Telephony Community | ||
*ap_ = Application | *ap_ = Application | ||
*ag_ = Application Group | *ag_ = Application Group | ||
| Line 41: | Line 49: | ||
=== Policies === | === Policies === | ||
In most cases, people from different teams will | In most cases, people from different teams will be involved during the configuration and updating of nGeniusONE. | ||
Even in small teams, it is very important to create a set of rules or | Even in small teams, it is very important to create a set of rules, guidelines or policies on how to create applications, services etc. | ||
It will also prevent | It will also prevent duplicate configurations that only take resources from nGeniusONE without adding more visibility. | ||
| | ||
Revision as of 07:32, 9 May 2019
Introduction
We've all been here: all those acronyms, variable names and definitions may be overwhelming.
These guidelines help users to discover the power of nGeniusONE and explore its full potential.
Solution
Captitals
Use as much as possible UPPER CASE for naming appliactions,communities, services ... . Don't use spaces; replace them with underscore '_" or hyphen "-".
Meaningfull names
Use meaingfull names for naming appliactions,communities, services ... .
Don't use space; replace with underscore '_" or hyphen "-".
Prefixes
The use of prefix will clarify which varable is used on reports. It allows for easy filtering and alphabetic ordening of longer lists.
Module Service Configuration
- as_ = Application Service
- ns_ = Network Service
Module Global Settings
- ls_ = Location Key of type Site
- lv_ = Location Key of type VLAN
- lr_ = Location Key of type VRF
- cc_ = Client Community
- sc_ = Server Community
- tc_ = Telephony Community
- ap_ = Application
- ag_ = Application Group
Policies
In most cases, people from different teams will be involved during the configuration and updating of nGeniusONE.
Even in small teams, it is very important to create a set of rules, guidelines or policies on how to create applications, services etc.
It will also prevent duplicate configurations that only take resources from nGeniusONE without adding more visibility.