• Home
  • Archive
  • Disclosure
    • Disclaimer
    • Comment Policy
    • Privacy Policy
  • Just Three
  • Contact
    • Who Am I ?
    • What does Ethereal Mind mean ?

EtherealMind

Software Defined & Intent Based Networking

You are here: Home / Blog / Analysis / Analysis: Example of WAN Orchestration

Analysis: Example of WAN Orchestration

25th February 2015 By Greg Ferro Filed Under: Analysis, Design

I wanted to draw attention to this WAN Orchestration demonstration video from Nuage Networks to highlight that you don’t need to become a programmer to bring orchestration to your network.

Its worth a 3 minute watch to get some new ideas on how to simplify ownership and management of a large WAN. analysis-logo-opt

I reject the idea that NetOps means every engineer needs to be coding in Python. That simply doesn’t scale. A very few people will use Python to provide customisation of platforms and frameworks like Nuage Networks Networks, VMware NSX and Glue Networks. But most of us will make things work just fine with orchestration products that will automate the network for us.

This is the deliverable that Software Defined Networking will bring you.

Other Posts in This Series

  1. Analysis: CloudFlare Keyless SSL Scales Down Internet Connections (13th March 2015)
  2. Analysis: Marriot Court Case Highlights the Problems of WiFi Services (12th March 2015)
  3. Analysis: Example of WAN Orchestration (25th February 2015)

About Greg Ferro

Human Infrastructure for Data Networks. 25 year survivor of Corporate IT in many verticals, tens of employers working on a wide range of networking solutions and products.

Host of the Packet Pushers Podcast on data networking at http://packetpushers.net- now the largest networking podcast on the Internet.

My personal blog at http://gregferro.com

Comments

  1. Adeel Ahmad says

    25th February 2015 at 11:22 +0000

    I agree with you, however in my opinion the majority of network engineers need to face that it’s no longer acceptable just knowing the CLI of a particular vendor so well. The importance of deep understanding of network protocols and overall network design has become more profound.

    I ‘d like to know your opinion on this and where you think the direction of the most network engineers should be?

    • Wanos says

      17th March 2015 at 00:05 +0000

      I am not so sure the majority of networks engineers need to code. Sure it can be hugely valuable in some cases. The more mature technology becomes, the less low level coding is involved, as illustrated by this article.

Network Break Podcast

Network Break is round table podcast on news, views and industry events. Join Ethan, Drew and myself as we talk about what happened this week in networking. In the time it takes to have a coffee.

Packet Pushers Weekly

A podcast on Data Networking where we talk nerdy about technology, recent events, conduct interviews and more. We look at technology, the industry and our daily work lives every week.

Our motto: Too Much Networking Would Never Be Enough!

Find Me on Social Media

  • LinkedIn
  • RSS
  • Twitter
  • YouTube

Return to top of page

Copyright Greg Ferro 2008-2019 - Thanks for reading my site, it's been good to have you here.

Opinions, Views and Ideas expressed here are my own and do not represent any employer, vendor or sponsor.Full disclosure