<?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 Re: High Availability support in Software Defined Networking</title>
    <link>https://community.hpe.com/t5/software-defined-networking/high-availability-support/m-p/6229549#M11</link>
    <description>&lt;P&gt;Hi Romain,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The controller supports a 2n+1 database resiliency model.&amp;nbsp; All controllers are active, and support the ability to assign each OF switch to a specific controller.&amp;nbsp; The controllers synchronize among each other using L3.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Applications that use the REST API or do not leverage the database infrastructure run on the master controller.&amp;nbsp; The internal JAVA API supports access to the database for state synchronization, allowing applications to take advantage of the active-active architecture.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards, Dave&lt;/P&gt;&lt;P&gt;(HP)&lt;/P&gt;</description>
    <pubDate>Tue, 08 Oct 2013 06:09:01 GMT</pubDate>
    <dc:creator>Dave_Hawley</dc:creator>
    <dc:date>2013-10-08T06:09:01Z</dc:date>
    <item>
      <title>High Availability support</title>
      <link>https://community.hpe.com/t5/software-defined-networking/high-availability-support/m-p/6225441#M10</link>
      <description>&lt;P&gt;What kind of high availability is supported by the SDN controller ?&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;1 + 1 ? ( active/passive )&lt;/LI&gt;&lt;LI&gt;1 + 1 ? ( active/active with load-sharing and statefull synchronization capabilities )&lt;/LI&gt;&lt;LI&gt;N+ M ? ( all actives with load-sharing and statefull synchronization capabilities )&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What are network constraints for high availibility ?&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;same L2 subnet for all the controller ?&lt;/LI&gt;&lt;LI&gt;Controller can be in different L3 ?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If load-sharing capability is possible, do the SDN controller offer natively distributed statefull capabilities with the use of the JAVA native API ( for SDN app create by tiers ) or is it the responsibility of tiers developpers to handle statefull synchronization&amp;nbsp;between controllers&amp;nbsp;( with PAXOS stuff for example ) ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Romain&lt;/P&gt;</description>
      <pubDate>Thu, 03 Oct 2013 09:26:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/software-defined-networking/high-availability-support/m-p/6225441#M10</guid>
      <dc:creator>Romain_JACOTIN</dc:creator>
      <dc:date>2013-10-03T09:26:45Z</dc:date>
    </item>
    <item>
      <title>Re: High Availability support</title>
      <link>https://community.hpe.com/t5/software-defined-networking/high-availability-support/m-p/6229549#M11</link>
      <description>&lt;P&gt;Hi Romain,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The controller supports a 2n+1 database resiliency model.&amp;nbsp; All controllers are active, and support the ability to assign each OF switch to a specific controller.&amp;nbsp; The controllers synchronize among each other using L3.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Applications that use the REST API or do not leverage the database infrastructure run on the master controller.&amp;nbsp; The internal JAVA API supports access to the database for state synchronization, allowing applications to take advantage of the active-active architecture.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards, Dave&lt;/P&gt;&lt;P&gt;(HP)&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2013 06:09:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/software-defined-networking/high-availability-support/m-p/6229549#M11</guid>
      <dc:creator>Dave_Hawley</dc:creator>
      <dc:date>2013-10-08T06:09:01Z</dc:date>
    </item>
  </channel>
</rss>

