diff options
author | Greg Blomquist <gblomqui@gblomqui.usersys.redhat.com> | 2008-07-14 01:05:44 -0400 |
---|---|---|
committer | Greg Blomquist <gblomqui@gblomqui.usersys.redhat.com> | 2008-07-14 01:05:44 -0400 |
commit | 3da06481387e7294e92b65813cc0aa44ec1e3e00 (patch) | |
tree | 3d950bb536456a578b23a02eeffd4f2a38039c11 /genome-docs/genome-docs-1.0.0/en-US/MachineTypes.xml | |
parent | ab3472e761bb5b1f26c70a0d2a2629980245167b (diff) | |
download | tools-3da06481387e7294e92b65813cc0aa44ec1e3e00.tar.gz tools-3da06481387e7294e92b65813cc0aa44ec1e3e00.tar.xz tools-3da06481387e7294e92b65813cc0aa44ec1e3e00.zip |
Adding QuickStart section
Starting Cloudmasterd documentation
Other Changes include:
* Fixing up some of the references to "repo machines"...changing to "Genome Appliance"
Diffstat (limited to 'genome-docs/genome-docs-1.0.0/en-US/MachineTypes.xml')
-rw-r--r-- | genome-docs/genome-docs-1.0.0/en-US/MachineTypes.xml | 110 |
1 files changed, 81 insertions, 29 deletions
diff --git a/genome-docs/genome-docs-1.0.0/en-US/MachineTypes.xml b/genome-docs/genome-docs-1.0.0/en-US/MachineTypes.xml index b33a11c..3cfeef4 100644 --- a/genome-docs/genome-docs-1.0.0/en-US/MachineTypes.xml +++ b/genome-docs/genome-docs-1.0.0/en-US/MachineTypes.xml @@ -13,27 +13,48 @@ </para> <section id="genome-cloud-appliance"> - <title>Cloud</title> + <title>Cloud Appliance</title> <para> - The Host machine type is used to host Xen + The Cloud Appliance is used to host Xen guests in the &PRODUCT; environment. - </para> - <para> - Features: - <itemizedlist> - <listitem><para>Virtualization (Either Xen or KVM)</para></listitem> - <listitem><para>&PRODUCT; tooling for managing the cloud</para></listitem> - </itemizedlist> - </para> - </section> - - <section id="genome-RepoMachineType"> - <title>Genome</title> + </para> + <section id="genome-cloud-appliance-systemreqs"> + <title>System Requirements</title> + <variablelist> + <varlistentry> + <term>CPU</term> + <listitem><simpara>1GHz</simpara></listitem> + </varlistentry> + <varlistentry> + <term>Memory</term> + <listitem><simpara>This depends on the number of cloud members you plan on hosting. We recommend 1.5G of RAM to start.</simpara></listitem> + </varlistentry> + <varlistentry> + <term>System architecture</term> + <listitem><simpara>A cloud appliance can be installed on either i386 or x86_64 architectures.</simpara></listitem> + </varlistentry> + <varlistentry> + <term>Storage</term> + <listitem><simpara>This depends on how many cloud members you plan on hosting. We recommend 100G of hard drive space to start.</simpara></listitem> + </varlistentry> + </variablelist> + <important><simpara>Cloud Appliances should only be installed on a Physical Machine and not a Virtual Machine</simpara></important> + </section> + <section> + <title>Features</title> + <itemizedlist> + <listitem><para>Virtualization (Either Xen or KVM)</para></listitem> + <listitem><para>&PRODUCT; tooling for managing the cloud</para></listitem> + </itemizedlist> + </section> + </section> + <section id="genome-appliance"> + <title>Genome Appliance</title> <para> - Genome appliances are the center of development in the - &PRODUCT; environment. In a nutshell they are the + The Genome Appliance is the center of development in the + &PRODUCT; environment. In a nutshell it is the self-contained provisioning, configuration and artifact - store. For this reason these machines are + store. For this reason Genome Appliances are generally not considered volatile. </para> @@ -46,19 +67,50 @@ <note> <title>Note</title> <para> - There was a time when Repo - machines were able to be + There was a time when Genome + Appliances were able to be created via <application><link linkend="genome-GenomeBootstrap">genome-bootstrap</link> </application>. This led to several "chicken and the egg" sorts of problems. For this reason the method for - provisioning Repo machines was + provisioning Genome Appliances was switched to RPM. </para> </note> - </para> + </para> + + + <section id="genome-appliance-systemreqs"> + <title>Minimum System Requirements</title> + <variablelist> + <varlistentry> + <term>CPU</term> + <listitem><simpara>1GHz</simpara></listitem> + </varlistentry> + <varlistentry> + <term>Memory</term> + <listitem><simpara>512M RAM</simpara></listitem> + </varlistentry> + <varlistentry> + <term>System architecture</term> + <listitem> + <simpara> + A Genome Appliance can be installed on either i386 or x86_64 architectures. + </simpara> + </listitem> + </varlistentry> + <varlistentry> + <term>Storage</term> + <listitem> + <simpara> + This depends on how many distros you plan on hosting in cobbler. We recommend 50G of hard drive space to start. + </simpara> + </listitem> + </varlistentry> + </variablelist> + </section> <section> <title>Features</title> @@ -101,14 +153,14 @@ </section> <section> - <title>Repo machine cloning</title> + <title>Genome Appliance cloning</title> <para> - The state of a particular Repo machine can be + The state of a particular Genome Appliance can be described by the content stored under /var/www/cobbler and /pub/git. Cloning a - particular Repo is really just a matter of + particular Genome Appliance is really just a matter of getting the correct bit from those locations - onto a new Repo machine. + onto a new Genome Appliance. </para> <para> @@ -155,7 +207,7 @@ </section> <section id="genome-repo-machine-customization"> - <title>Repo machine customization</title> + <title>Genome Appliance customization</title> <para> The &REPORPM; is designed to get users up and running with a known working configuration. @@ -192,7 +244,7 @@ <para> The reason this works is because by default - the Repo appliance's + the Genome Appliance's <application>puppet</application> external nodes script includes two classes: @@ -214,8 +266,8 @@ <application>puppet</application> classes matched with an operating system (or more precisely, a <application>cobbler</application> profile). The list - of machines that can be provisioned from a given Repo - machine can be found when using the <link + of machines that can be provisioned from a given Genome + Appliance can be found when using the <link linkend="genome-GenomeBootstrap">genome-bootstrap</link> wizard or the <link linkend="genome-Genomed">genomed</link> UI. |