|
Using the unique modeling functionality, network designers and architects can define the architectural rules and choices that the operation people can choose from.
|
For example: when an operator deploys a new service via the application, he can choose from the design-, service- and hardware options defined by the designer. These models define the context of what can be chosen by an operator and at the same time generate the relevant network parameters upon execution of the model, such as standardized allocation of ip addresses, vlan numbering etc.
Network engineers ensure that their 'golden configs' are used by the system by turning them into templates. These templates can be ‘parameterized’ and ‘conditionalized', making it possible to have only a few templates to manage a variety of devices and networks. Upon execution, the templates are automatically filled with the right parameters from the database (generated by the models).
Network operations people use the application in a variety of ways, for example to populate new sites and services, verify the generated configs or schedule jobs for execution. Instead of an operator logging into the devices in the network, the application will log into the devices and issue all changes. Important to note is that operations is still fully in control of what happens to the network, but everything is done in a standardized and controlled way using one source of information.
|
Consequently, all configurations and changes are generated according to the original design principles, using the ‘golden configuration’ templates, using one consistent source of network information. Also, with all relationships and parameters explicitly known in the application, (YCE is service and topology aware), it is now very easy to start managing and automating networks and network services instead of individual devices. |