<?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: EBS volume and OS in Cloudbreak on AWS in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/EBS-volume-and-OS-in-Cloudbreak-on-AWS/m-p/149381#M40513</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've been testing(and failing) with changing the the Cluster OS images to RHEL 6.7 since we have a support agreement with RedHat. I was using the hack that I found on this forum where you change the etc/aws-images.yml. It sounds like you I am going in the wrong direction here. &lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;</description>
    <pubDate>Wed, 14 Sep 2016 20:58:51 GMT</pubDate>
    <dc:creator>william_prender</dc:creator>
    <dc:date>2016-09-14T20:58:51Z</dc:date>
    <item>
      <title>EBS volume and OS in Cloudbreak on AWS</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/EBS-volume-and-OS-in-Cloudbreak-on-AWS/m-p/149379#M40511</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Quick questions regarding cloud break on aws:&lt;/P&gt;&lt;P&gt;1. For the HDP nodes, can you change OS to ubuntu or is default RHEL 6/7?&lt;/P&gt;&lt;P&gt;2. Any recommendations around attaching st1 EBS volumes? Should I just do that as a separate process? looks like latest version of cloudbreak allows only magnetic/ssd&lt;/P&gt;&lt;P&gt;3. What is the best approach to adding services? Should we do it in ambari or change the ambari blueprint?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Tue, 13 Sep 2016 22:57:41 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/EBS-volume-and-OS-in-Cloudbreak-on-AWS/m-p/149379#M40511</guid>
      <dc:creator>mliem</dc:creator>
      <dc:date>2016-09-13T22:57:41Z</dc:date>
    </item>
    <item>
      <title>Re: EBS volume and OS in Cloudbreak on AWS</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/EBS-volume-and-OS-in-Cloudbreak-on-AWS/m-p/149380#M40512</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/11088/mliem.html" nodeid="11088"&gt;@mliem&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;1. The short answer is that we can't change the os. Longer one: you could create a custom Cloudbreak image based on ubuntu, but it's not advised and not supported.&lt;/P&gt;&lt;P&gt;2. From Cloudbreak version 1.4 you can choose 'Throughput Optimized HDD (&lt;CODE&gt;st1&lt;/CODE&gt;)' under 'manage templates'&lt;/P&gt;&lt;P&gt;3. Changing the blueprint is recommended, but it won't change already running instances&lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2016 16:52:47 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/EBS-volume-and-OS-in-Cloudbreak-on-AWS/m-p/149380#M40512</guid>
      <dc:creator>bbihari</dc:creator>
      <dc:date>2016-09-14T16:52:47Z</dc:date>
    </item>
    <item>
      <title>Re: EBS volume and OS in Cloudbreak on AWS</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/EBS-volume-and-OS-in-Cloudbreak-on-AWS/m-p/149381#M40513</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've been testing(and failing) with changing the the Cluster OS images to RHEL 6.7 since we have a support agreement with RedHat. I was using the hack that I found on this forum where you change the etc/aws-images.yml. It sounds like you I am going in the wrong direction here. &lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Wed, 14 Sep 2016 20:58:51 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/EBS-volume-and-OS-in-Cloudbreak-on-AWS/m-p/149381#M40513</guid>
      <dc:creator>william_prender</dc:creator>
      <dc:date>2016-09-14T20:58:51Z</dc:date>
    </item>
  </channel>
</rss>

