<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Blog Post: How to make sure Network virtualisation works? in NSO Developer Hub Discussions</title>
    <link>https://community.cisco.com/t5/nso-developer-hub-discussions/blog-post-how-to-make-sure-network-virtualisation-works/m-p/3597582#M2256</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Volker Tegtmeier has written &lt;A href="http://blogs.cisco.com/sp/how-to-make-sure-network-virtualisation-works?utm_source=feedburner&amp;amp;utm_medium=feed&amp;amp;utm_campaign=Feed%3A+CiscoBlogSp360ServiceProvider+%28SP360%3A+Service+Provider%29" target="_blank"&gt;this blog post&lt;/A&gt;, where he concludes that&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;– Many service providers are seeing virtualisation as a strategic way of sustainably meeting new customer demands.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;– But virtualisation alone is not the answer – if not implemented in the right way, it can actually lead to more complexity.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;– A successful virtual network combines a reliable infrastructure with powerful automation.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;– An orchestration engine is the key to making this possible, because it can take a broad overview of the network, allocating resources where they’re most needed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;– Our industry-leading Network Services Orchestrator provides end-to-end automation across virtual and hybrid networks, enabling providers to reduce the time it takes to deploy new services.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Mar 2019 11:54:41 GMT</pubDate>
    <dc:creator>KJ Rossavik</dc:creator>
    <dc:date>2019-03-01T11:54:41Z</dc:date>
    <item>
      <title>Blog Post: How to make sure Network virtualisation works?</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/blog-post-how-to-make-sure-network-virtualisation-works/m-p/3597582#M2256</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Volker Tegtmeier has written &lt;A href="http://blogs.cisco.com/sp/how-to-make-sure-network-virtualisation-works?utm_source=feedburner&amp;amp;utm_medium=feed&amp;amp;utm_campaign=Feed%3A+CiscoBlogSp360ServiceProvider+%28SP360%3A+Service+Provider%29" target="_blank"&gt;this blog post&lt;/A&gt;, where he concludes that&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;– Many service providers are seeing virtualisation as a strategic way of sustainably meeting new customer demands.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;– But virtualisation alone is not the answer – if not implemented in the right way, it can actually lead to more complexity.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;– A successful virtual network combines a reliable infrastructure with powerful automation.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;– An orchestration engine is the key to making this possible, because it can take a broad overview of the network, allocating resources where they’re most needed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;– Our industry-leading Network Services Orchestrator provides end-to-end automation across virtual and hybrid networks, enabling providers to reduce the time it takes to deploy new services.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2019 11:54:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/blog-post-how-to-make-sure-network-virtualisation-works/m-p/3597582#M2256</guid>
      <dc:creator>KJ Rossavik</dc:creator>
      <dc:date>2019-03-01T11:54:41Z</dc:date>
    </item>
  </channel>
</rss>

