|
1 | 1 | ifdef::context[:parent-context: {context}]
|
2 | 2 |
|
3 |
| -[id="Installing_Server_Connected_{context}"] |
4 |
| -= Installing {ProjectServer} |
5 |
| - |
6 |
| -ifdef::satellite[] |
7 |
| -When you install {ProjectServer} from a connected network, you can obtain packages and receive updates directly from the Red Hat Content Delivery Network. |
8 |
| - |
9 |
| -NOTE: You cannot register {ProjectServer} to itself. |
10 |
| - |
11 |
| -Use the following procedures to install {ProjectServer}, perform the initial configuration, and import subscription manifests. |
12 |
| -For more information on subscription manifests, see {ContentManagementDocURL}Managing_Red_Hat_Subscriptions_content-management[Managing Red Hat Subscriptions] in _{ContentManagementDocTitle}_. |
13 |
| -endif::[] |
14 |
| - |
15 |
| -ifndef::satellite[] |
16 |
| -Use the following procedures to install {ProjectServer} and perform the initial configuration. |
17 |
| -endif::[] |
18 |
| - |
19 |
| -ifdef::foreman-el[] |
20 |
| -On {EL}, you can install {Project} with or without the Katello plug-in. |
21 |
| -If you are a new user, consider installing {Project} with the Katello plug-in. |
22 |
| -endif::[] |
23 |
| - |
24 |
| -Note that the {Project} installation script is based on Puppet, which means that if you run the installation script more than once, it might overwrite any manual configuration changes. |
25 |
| - |
26 |
| -To avoid this and determine which future changes apply, use the `--noop` argument when you run the installation script. |
27 |
| -This argument ensures that no actual changes are made. |
28 |
| -Potential changes are written to `{installer-log-file}`. |
29 |
| - |
30 |
| -Files are always backed up and so you can revert any unwanted changes. |
31 |
| -For example, in the foreman-installer logs, you can see an entry similar to the following about Filebucket: |
32 |
| - |
33 |
| -[options="wrap"] |
34 |
| ----- |
35 |
| -/Stage[main]/Dhcp/File[/etc/dhcp/dhcpd.conf]: Filebucketed /etc/dhcp/dhcpd.conf to puppet with sum 622d9820b8e764ab124367c68f5fa3a1 |
36 |
| ----- |
37 |
| - |
38 |
| -You can restore the previous file as follows: |
39 |
| - |
40 |
| -[options="wrap"] |
41 |
| ----- |
42 |
| -# puppet filebucket -l \ |
43 |
| -restore /etc/dhcp/dhcpd.conf 622d9820b8e764ab124367c68f5fa3a1 |
44 |
| ----- |
| 3 | +include::modules/con_installing-server.adoc[] |
45 | 4 |
|
46 | 5 | ifdef::satellite,katello,orcharhino[]
|
47 | 6 | include::modules/proc_configuring-http-proxy-to-connect-to-cdn.adoc[leveloffset=+1]
|
@@ -72,16 +31,7 @@ ifdef::satellite[]
|
72 | 31 | include::modules/proc_installing-the-sos-package.adoc[leveloffset=+1]
|
73 | 32 | endif::[]
|
74 | 33 |
|
75 |
| -[id="configuring-server_{context}"] |
76 |
| -== Configuring {ProjectServer} |
77 |
| - |
78 |
| -Install {ProjectServer} using the `{foreman-installer}` installation script. |
79 |
| - |
80 |
| -This method is performed by running the installation script with one or more command options. |
81 |
| -The command options override the corresponding default initial configuration options and are recorded in the {Project} answer file. |
82 |
| -You can run the script as often as needed to configure any necessary options. |
83 |
| - |
84 |
| -NOTE: Depending on the options that you use when running the {Project} installer, the configuration can take several minutes to complete. |
| 34 | +include::modules/con_configuring-server.adoc[leveloffset=+1] |
85 | 35 |
|
86 | 36 | include::modules/proc_configuring-installation.adoc[leveloffset=+2]
|
87 | 37 |
|
|
0 commit comments