Design ≠ Execution
Nowadays, network designs are only very loosely coupled to network execution. There is no structured process how high- and low-level design documents get translated and implemented. It is wide open for interpretation by individual engineers. As a result configuration diversity grows and tasks cannot be automated or shared with team members. Network engineers typically analyse, create and change configurations manually in production.
Change processes are broken, manual and implicit. As a result, design rules are not adhered to. Different information sources exist (the infamous copy/paste activities), knowledge is not shared, best practices not used, and the list goes on. It’s these processes that need to be aligned in order to achieve true network automation and orchestration.
The challenge to solve is how to make all this implicit logic and processes explicit, while at the same time dealing with all the unique requirements that each network has. NetYCE has been able to solve this by bridging the gaps between (specific) design rules with closed-loop and intent-based network configuration changes.
“The focus should be on structuring information and processes between your Design, Build, and Operate activities”
Bridging the gaps!
Welcome to our world! We have been developing and improving the netYCE framework for the last 15 years to tackle today's challenges in network change management. The key lies in segregating and abstracting the information and processes between how you Design, Build and Operate networks. This is what we refer to as Design Driven Networking.
Unified control across legacy, NFV, SDN networks
Every network is different and changing all the time to meet new requirements. And it's unpredictable which new network technology or OSS system is most fashionable next year. NetYCE is perfectly positioned to bridge the gap between these domains and keep your change processes, knowledge and procedures constant.
We are convinced that the networking infrastructures should be fully elastic without any risk of disruption. This level of automation requires a smart degree of abstraction to deal with changes in OSS systems, network vendors or -technologies. NetYCE solves this by storing all your topologies, services and configurations in a vendor agnostic way so these changes can be easily incorporated without having a big impact on your organization.
Design Driven Networking (DDN) is not so much a new technology approach to solving network’s challenges. It is a standardization and process approach, irrespective of the chosen vendors and technologies, covering multiple domains. So how does DDN relate to concepts like SDN, DevOps and OSS systems? Read more below.
Design Driven Networking and SDN
Software Defined Networking (SDN) has gained a lot of interest in the market. Unfortunately, there is also a lot of confusion in the market what SDN is and what it is not. The idea behind SDN is to separate the control plane from network devices, making them new support standards (such as openflow, Netconf and Yang) and have software controllers and applications to ‘program’ network nodes. At the same time, virtualization and network function virtualization (NFV) have emerged as alternatives.
Although these are great new initiatives, the pitfall is that these are all technology oriented and not focusing on standardization of your process control. This is where Design Driven Networking complements SDN and NFV. In fact, one can say that the netYCE framework offers you one Software Defined Network control for all your network domains ranging from traditional legacy-, NFV- and SDN networks. And do this across ANY network vendor. Instead of changing your processes or developing software when implementing a new technology, you can use netYCE' GUI based modelling and all of the framework's tools to control and orchestrate changes across multiple network domains. The biggest added value is that all your processes, standards and architectures remain enforced while implementing something new or migrating services.
Instead of changing your processes or developing software when implementing a new technology, you can use netYCE' GUI based modelling and all of the framework's tools to control and orchestrate changes across multiple network domains. The biggest added value is that all your processes, standards and architectures remain enforced while implementing something new or migrating services.
DevOps for Networking
DevOps is a software development method that stresses communication, collaboration and integration between software developers and IT professionals. It aims to help organizations rapidly produce products and services. The netYCE application is best categorized as your DevOps framework for networking professionals including network architects, designers, engineers and operators.
Instead of having software developers, who lack the required networking knowledge, to develop network automation solutions, now engineers and designers can simply model their design rules to be used and applied by engineers and operators in their day to day operations. Only basic training is required for network designers and engineers. Now software developers only need to be used for NMS/OSS and 3rd party application integrations.
Vendor proprietary network support systems now belong to the past. With netYCE, Network Service Providers and Enterprises can implement a true vendor agnostic solution, irrespective of selected technology or design.
And by using integrations with 3rd party systems such as OSS-, BSS-, IPAM- or server automation systems, netYCE is perfectly positioned as the broker to also streamline NMS processes.