<?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>question Re: Cloudbreak vs Brooklyn in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-vs-Brooklyn/m-p/115141#M33967</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/10824/babucusat2007.html" nodeid="10824"&gt;@Rambabu Gupta&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Also cloudbreak is better in deploying HDP and Ambari over Cloud Infrastructures. It uses ambari blueprints&lt;/P&gt;</description>
    <pubDate>Wed, 06 Jul 2016 16:14:57 GMT</pubDate>
    <dc:creator>pankaj_singh</dc:creator>
    <dc:date>2016-07-06T16:14:57Z</dc:date>
    <item>
      <title>Cloudbreak vs Brooklyn</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-vs-Brooklyn/m-p/115139#M33965</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;how this technology differentiates itself from other
popularly used ones in the same domain like why and when should one use
CloudBreak over Brooklyn&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jul 2016 15:53:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-vs-Brooklyn/m-p/115139#M33965</guid>
      <dc:creator>babu_cusat2007</dc:creator>
      <dc:date>2016-07-06T15:53:57Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak vs Brooklyn</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-vs-Brooklyn/m-p/115140#M33966</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/10824/babucusat2007.html" nodeid="10824"&gt;@Rambabu Gupta&lt;/A&gt;
&lt;/P&gt;&lt;P&gt;Apache Brooklyn is a tool for deploy applications. You must specify how do you want to deploy the application. This is what Ambari does but in case of Ambari you just have to specify which component must be install on which node (you can specify it as a json file). In case of Brooklyn you have to write the whole process in a configuration file. Cloudbreak is the &lt;STRONG&gt;officially&lt;/STRONG&gt; &lt;STRONG&gt;supported&lt;/STRONG&gt; way to deploy hadoop in the cloud and it is using Ambari to deploy the hadoop cluster on the provisioned nodes.
This is the list of the components which can deploy by Brooklyn &lt;A href="https://brooklyn.apache.org/learnmore/catalog/index.html" target="_blank"&gt;https://brooklyn.apache.org/learnmore/catalog/index.html&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;Brooklyn supporting just Storm as I see but in case of Ambari you can deploy &lt;STRONG&gt;any&lt;/STRONG&gt; hadoop component.&lt;/P&gt;&lt;P&gt;Hope that helps&lt;/P&gt;&lt;P&gt;Br,&lt;/P&gt;&lt;P&gt;Richard&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jul 2016 16:11:32 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-vs-Brooklyn/m-p/115140#M33966</guid>
      <dc:creator>rdoktorics</dc:creator>
      <dc:date>2016-07-06T16:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: Cloudbreak vs Brooklyn</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-vs-Brooklyn/m-p/115141#M33967</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/10824/babucusat2007.html" nodeid="10824"&gt;@Rambabu Gupta&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Also cloudbreak is better in deploying HDP and Ambari over Cloud Infrastructures. It uses ambari blueprints&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jul 2016 16:14:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Cloudbreak-vs-Brooklyn/m-p/115141#M33967</guid>
      <dc:creator>pankaj_singh</dc:creator>
      <dc:date>2016-07-06T16:14:57Z</dc:date>
    </item>
  </channel>
</rss>

