summaryrefslogtreecommitdiffstats
path: root/genome-docs/genome-docs-1.0.0/en-US/genome.ent
blob: 253584e21d6ecec1d91a8dd6c3a50cc052ecf3b2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
<!ENTITY PRODUCT "Genome">
<!ENTITY BOOKID "genome">
<!ENTITY YEAR "2008">
<!ENTITY HOLDER "Red Hat">
<!ENTITY BOOTSTRAPFACTFILE "<filename>/usr/lib/ruby/facter/bootstrap.rb</filename>">
<!ENTITY PUPPETCONFFILE "<filename>/etc/puppet/puppet.conf</filename>">
<!ENTITY PUPPETSSLDIR "<filename>/var/lib/puppet/ssl</filename>">
<!ENTITY FIRSTBOOTFILE "<filename>/usr/sbin/genome-firstboot</filename>">
<!ENTITY GENOMEPASSWORD "password">
<!ENTITY GENOMEUSER "<emphasis>genome</emphasis>">
<!ENTITY GENOMEREPO "genome-repo.usersys.redhat.com">
<!ENTITY BOOTSTRAPRPM "rubygem-genome-bootstrap">
<!ENTITY BOOTSTRAPTOOL "<application>genome-bootstrap</application>">
<!ENTITY REPORPM "<application>genome-repo</application> RPM">
<!ENTITY GENOMETRAC "<ulink url=&#34;https://engineering.redhat.com/trac/IT_Architecture/&#34;>IT Architecture Trac</ulink>">
<!ENTITY JBOSSDEVBOOTSTRAPEXAMPLE "
			<screen>
# genome-bootstrap
Enter your Genome repo machine name (leave off the '-repo'): arch
Your machine name is the part right before the Genome type.
For example, 'sso1-build.usersys.redhat.com' has a machine name of 'sso1'.
If you do not specify a machine name it will default to your kerberos name.
Enter machine name? (y/n)
y
Machine name: bleanhar-test
To see a description of these machine types visit: http://arch-repo.usersys.redhat.com/genome/machine_types.html
1. jboss
2. jboss-proxy
3. jboss-mysql
4. jboss-dev
5. bpel-build
6. splunk
7. repo
8. rails
9. selenium-queue
10. host
11. hudson
12. ldap
13. knowledge-jboss
14. knowledge-build
15. knowledge-mysql
Select your machine type:  4
Enter your kerberos username: bleanhar
Configure this machine with Red Hat DDNS? (y/n)
y
Do you know the DDNS hash for this machine? (y/n)
n
Enter your kerberos password to setup DDNS: *********
Fetching DDNS hash...
Hash not found for bleanhar-test-jboss-dev
Requesting a new hash
Fetching DDNS hash...
1. CSB-RHEL5U1-i386
2. GenomeHost-RHEL5U1-i386
3. Host-F8-i386
4. LargeGenomeGuest-RHEL5U1-i386
5. NormalGenomeGuest-F8-i386
6. NormalGenomeGuest-RHEL5U1-i386
7. SmallGenomeGuest-RHEL5U1-i386
Select your cobbler profile (This determines the OS):  5
Now you need to enter some parameters what will be used to configure this machine.
Most of the defaults will work out fine for development.
Description: The puppetmaster used for all configuration.  If you are provisioning a Repo machine, this should be it's FQDN
Enter value for puppetserver: |arch-repo.usersys.redhat.com|
Description: server used for syslogd.  Another safe value is the FQDN of an Genome host machine.
Enter value for logserver: |localhost|
Description: The cobbler server to configure for all yum dependencies
Enter value for cobbler: |arch-repo.usersys.redhat.com|
Description: This is Genome user. If any work cannot be performed system-wide it will be done for this user
Enter value for user: |it|
Description: The environment this machine will be configured for.  Eventually others will be supported by for now the default value is what you want.
Enter value for env: |sandbox|
Description: The machine hosting the bare git repositories for this machine.  This fact is also used at bootstrap time.
Enter value for gitserver: |arch-repo.usersys.redhat.com|
Description: The machines running the jboss apps context. This can be a comma separated list if you want to proxy multiple machines or it can be a single machine.
Enter value for jboss_apps_hosts: |bleanhar-test-jboss.usersys.redhat.com|                                    Description: The machines running the jboss apps context. This can be a comma separated list if you want to proxy multiple machines or it can be a single machine.
Enter value for jboss_wapps_hosts: |bleanhar-test-jboss.usersys.redhat.com|
Description: The machines running the jboss apps context. This can be a comma separated list if you want to proxy multiple machines or it can be a single machine.
Enter value for jboss_wsvc_hosts: |bleanhar-test-jboss.usersys.redhat.com|
Description: The machines running the jboss apps context. This can be a comma separated list if you want to proxy multiple machines or it can be a single machine.
Enter value for jboss_svc_hosts: |bleanhar-test-jboss.usersys.redhat.com|
Description: Maven repo used for maven dependencies
Enter value for maven_repo: |arch-repo.usersys.redhat.com|
Description: The MySQL server where JBoss Messaging persists messages.
Enter value for messaging_server: |bleanhar-test-jboss-dev.usersys.redhat.com|
Description: The MySQL server where the JBossESB message datastore resides.
Enter value for datastore_server: |bleanhar-test-jboss-dev.usersys.redhat.com|
Description: Multicast address used for hajndi, tree caches, etc.  All machines in the cluster must use the same adddress.  It MUST be unique across clusters.
Enter value for multicast_address: |228.1.2.6|
Description: Apache proxy for the tomcat stack.  Uses mod_proxy_ajp and is suitable for development.  This fact also represents the publically available redhat.com machine.
Enter value for proxy: |bleanhar-test-jboss-dev.usersys.redhat.com|
Description: The type of Mysql server. The default is the only type suitable for development at the moment
Enter value for mysql_type: |standalone|
Description: Server ID for MySQL Replication.  The default is fine if you are using a standalone mysql type.
Enter value for mysql_server_id: |1|
Enter addition facts? (y/n)
n

                        </screen>
">