foreman_guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
foreman_guide [2015/03/09 20:01] Tim Rozet |
foreman_guide [2015/04/07 22:26] (current) Daniel Farrell [Install Foreman] Better formatting for complex Foreman install command |
||
|---|---|---|---|
| Line 75: | Line 75: | ||
| Now run the installer with the right arguments for your setup: | Now run the installer with the right arguments for your setup: | ||
| - | ''sudo foreman-installer \\ | + | <code> |
| + | sudo foreman-installer \\ | ||
| --enable-foreman-proxy \\ | --enable-foreman-proxy \\ | ||
| --foreman-proxy-tftp=true \\ | --foreman-proxy-tftp=true \\ | ||
| Line 91: | Line 92: | ||
| --foreman-proxy-foreman-base-url=https://localhost \\ | --foreman-proxy-foreman-base-url=https://localhost \\ | ||
| --foreman-proxy-oauth-consumer-key=ag9QcrzYTZQVhsnuEb8zYVc6taL4jmXj \\ | --foreman-proxy-oauth-consumer-key=ag9QcrzYTZQVhsnuEb8zYVc6taL4jmXj \\ | ||
| - | --foreman-proxy-oauth-consumer-secret=CWieWvBUMrfsvSc88UcmNTtrGtSzUCCf'' | + | --foreman-proxy-oauth-consumer-secret=CWieWvBUMrfsvSc88UcmNTtrGtSzUCCf |
| + | </code> | ||
| You should see the following | You should see the following | ||
| - | Installing Done [100%] [...........................................................................................] | + | <code> |
| Success! | Success! | ||
| * Foreman is running at https://foreman.localdomain | * Foreman is running at https://foreman.localdomain | ||
| Line 102: | Line 104: | ||
| * Puppetmaster is running at port 8140 | * Puppetmaster is running at port 8140 | ||
| The full log is at /var/log/foreman-installer/foreman-installer.log | The full log is at /var/log/foreman-installer/foreman-installer.log | ||
| + | </code> | ||
| Please notice the above message gives you the credentials to the Foreman GUI. | Please notice the above message gives you the credentials to the Foreman GUI. | ||
| Line 128: | Line 130: | ||
| ===Adminstrator Settings=== | ===Adminstrator Settings=== | ||
| - | First make sure that your host is in a trusted puppet master, go to Administer in the top right -> Settings and search for **trusted_puppetmaster_hosts**. Then edit the value (keeping in mind it needs to be an array, so maintain the square brackets) with the foreman.localdomain value for your foreman server. | + | First make sure that your host is in a trusted puppet master, go to Administer in the top right -> Settings and search for "trusted_puppetmaster_hosts". Then edit the value (keeping in mind it needs to be an array, so maintain the square brackets) with the foreman.localdomain value for your foreman server. |
| To stop Foreman from modifying your configured network settings for each host, you should configure this setting. From the Foreman GUI, go to Administer in the top right -> Settings -> Provisioning Tab -> ignore_puppet_facts_for_provisioning = true. | To stop Foreman from modifying your configured network settings for each host, you should configure this setting. From the Foreman GUI, go to Administer in the top right -> Settings -> Provisioning Tab -> ignore_puppet_facts_for_provisioning = true. | ||
| Line 152: | Line 154: | ||
| ===Global Parameters=== | ===Global Parameters=== | ||
| - | trozet fill this out. | + | Global parameters are variables that are used by Foreman as well as for the OPNFV puppet class. They can be found by going to Configure -> Global Parameters. Please reference the variables listed in the [[https://wiki.opnfv.org/quickstack_opnfv_puppet_guide#running_puppet_modules | puppet modules guide]] if you wish to use the OPNFV puppet module to deploy ODL + OpenStack. |
| ===Create HostGroups in Foreman=== | ===Create HostGroups in Foreman=== | ||
| - | HostGroups are used to classify different types of hosts we want to provision. For OpenStack purposes we classify a node as compute, network, or control. See the opendaylight info at the top of this page if you want to combine any of these nodes to a single host (i.e. network+control into one host). To configure HostGroups in Foreman: | + | HostGroups are used to classify different types of hosts we want to provision. For OPNFV purposes we classify a node as compute or controller+networker. It is supported to create three separate nodes (compute, control, network) but for hte purposes of OPNFV we are consolodating controller+networker into one node. To configure HostGroups in Foreman: |
| - Configure -> HostGroup | - Configure -> HostGroup | ||
| Line 162: | Line 164: | ||
| - Network tab-> select the management subnet you created | - Network tab-> select the management subnet you created | ||
| - Operating System tab -> Operating System = CentOS7 you defined, Media = CentOS mirror, Partition table= Kickstart default | - Operating System tab -> Operating System = CentOS7 you defined, Media = CentOS mirror, Partition table= Kickstart default | ||
| - | - Submit, repeat for Control and Network groups. | + | - Submit, repeat for trystack::controller_networker (control+network node). |
| ===Create Host in Foreman=== | ===Create Host in Foreman=== | ||
| Line 173: | Line 175: | ||
| - You can now click on your host and click Build (B). On the servers next pxe boot it will build off of foreman using kickstart default. Interested in using Foreman to control your hardware? See below. | - You can now click on your host and click Build (B). On the servers next pxe boot it will build off of foreman using kickstart default. Interested in using Foreman to control your hardware? See below. | ||
| - | ===Host Changes=== | + | ===Host Global Parameter Overriding=== |
| + | This section is applicable if using Global Parameters. It goes over what variable needs to be overriden if using the OPNFV puppet modules. | ||
| If using the same server hardware or VMs throughout your environment then you can get away with just setting the private interface name as the global value for ovs_tunnel_if (since they will all be the same name). However if you use different model servers or different NIC interfaces you need to override this parameter per host. To do this in Foreman Web GUI: | If using the same server hardware or VMs throughout your environment then you can get away with just setting the private interface name as the global value for ovs_tunnel_if (since they will all be the same name). However if you use different model servers or different NIC interfaces you need to override this parameter per host. To do this in Foreman Web GUI: | ||
| Line 196: | Line 199: | ||
| - Now on the left pane, BMC should show up. Click it and you should see hte Chassis Power state. | - Now on the left pane, BMC should show up. Click it and you should see hte Chassis Power state. | ||
| - You now have the option when you "Build" to tell Foreman to reboot the server now. | - You now have the option when you "Build" to tell Foreman to reboot the server now. | ||
| - | |||
foreman_guide.1425931263.txt.gz · Last modified: 2015/03/09 20:01 by Tim Rozet
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
