<?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 OS deployment - the missing manual??? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/os-deployment-the-missing-manual/m-p/4022823#M55360</link>
    <description>So - I'm OK with "basic OS deployment" - but I need some assistance with making this _really_ work in a production environment.&lt;BR /&gt;&lt;BR /&gt;IP Addressing:&lt;BR /&gt;I have Blades with 4 NICs - how can I, as part of a RHEL deployment, set the IPs on ALL the NICS short of manually editing the KS file for each server?  Are folks generally doing this with an external DHCP server (which is not an option for me here).&lt;BR /&gt;&lt;BR /&gt;General config data:&lt;BR /&gt;Similarly, what about other "conf" data that is unique per server?  As simple as setting hostname, and as complex as building data for iSCSI connectivity.&lt;BR /&gt;&lt;BR /&gt;Is there a best practice here that folks have found functional???&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Don</description>
    <pubDate>Tue, 19 Jun 2007 09:25:02 GMT</pubDate>
    <dc:creator>Don Vanco - Linux Ninja</dc:creator>
    <dc:date>2007-06-19T09:25:02Z</dc:date>
    <item>
      <title>OS deployment - the missing manual???</title>
      <link>https://community.hpe.com/t5/operating-system-linux/os-deployment-the-missing-manual/m-p/4022823#M55360</link>
      <description>So - I'm OK with "basic OS deployment" - but I need some assistance with making this _really_ work in a production environment.&lt;BR /&gt;&lt;BR /&gt;IP Addressing:&lt;BR /&gt;I have Blades with 4 NICs - how can I, as part of a RHEL deployment, set the IPs on ALL the NICS short of manually editing the KS file for each server?  Are folks generally doing this with an external DHCP server (which is not an option for me here).&lt;BR /&gt;&lt;BR /&gt;General config data:&lt;BR /&gt;Similarly, what about other "conf" data that is unique per server?  As simple as setting hostname, and as complex as building data for iSCSI connectivity.&lt;BR /&gt;&lt;BR /&gt;Is there a best practice here that folks have found functional???&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Don</description>
      <pubDate>Tue, 19 Jun 2007 09:25:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/os-deployment-the-missing-manual/m-p/4022823#M55360</guid>
      <dc:creator>Don Vanco - Linux Ninja</dc:creator>
      <dc:date>2007-06-19T09:25:02Z</dc:date>
    </item>
    <item>
      <title>Re: OS deployment - the missing manual???</title>
      <link>https://community.hpe.com/t5/operating-system-linux/os-deployment-the-missing-manual/m-p/4022824#M55361</link>
      <description>So I've been thinking about scripting -&lt;BR /&gt;&lt;BR /&gt;Is there a logical / predictable / consistent IP addressing schema that ICLE hands out to servers (for the management network) as they are installed?  What about host names?&lt;BR /&gt;&lt;BR /&gt;Is this documented somewhere?&lt;BR /&gt;&lt;BR /&gt;If I can predict an IP range or hostnames I can write a script to scp and/or ssh "echo" config files as I need them</description>
      <pubDate>Tue, 19 Jun 2007 10:44:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/os-deployment-the-missing-manual/m-p/4022824#M55361</guid>
      <dc:creator>Don Vanco - Linux Ninja</dc:creator>
      <dc:date>2007-06-19T10:44:20Z</dc:date>
    </item>
  </channel>
</rss>

