FAQ
Version 10 (Ohad Levy, 09/08/2009 05:28 am)
| 1 | 3 | Ohad Levy | h1. Frequently Asked Questions |
|---|---|---|---|
| 2 | 3 | Ohad Levy | |
| 3 | 3 | Ohad Levy | |
| 4 | 2 | Ohad Levy | {{toc}} |
| 5 | 2 | Ohad Levy | |
| 6 | 5 | Ohad Levy | h1. I'm not using Storeconfigs, how can I still use Torque? |
| 7 | 1 | ||
| 8 | 1 | Torque does not require puppet storeconfigs, however, Torque can work with puppet db schema natively as Torque extends it. |
|
| 9 | 1 | ||
| 10 | 1 | If you just want to import hosts inventory (facts), you can use the rake task: |
|
| 11 | 1 | <pre>RAILS_ENV=production rake puppet:import:hosts_and_facts</pre> |
|
| 12 | 1 | This will import your exists facts yaml file (defaults to vardir/yaml/facts), if you wish to import from another directory use: |
|
| 13 | 1 | <pre>RAILS_ENV=production rake puppet:import:hosts_and_facts dir=/my/dir/with/yaml/files</pre> |
|
| 14 | 1 | ||
| 15 | 4 | Ohad Levy | *NOTE:* its probably a good idea to clean up your yaml file directory, as you might have a lot of old data in there. |
| 16 | 1 | ||
| 17 | 5 | Ohad Levy | h1. I'm using Storeconfigs, how can I populate various settings in Torque that are required for hands free (unattended) installations? |
| 18 | 1 | ||
| 19 | 1 | <pre>RAILS_ENV=production rake puppet:migrate:populate_hosts</pre> |
|
| 20 | 1 | This will try to auto-generate all operating systems, puppet environments etc into Torque's DB. |
|
| 21 | 1 | ||
| 22 | 5 | Ohad Levy | h1. How do I use unattended installations (Kickstart, jumpstart, preseed)? |
| 23 | 1 | ||
| 24 | 10 | Ohad Levy | see [[Unattended installations]] |
| 25 | 5 | Ohad Levy | h2. PuppetCA |
| 26 | 1 | ||
| 27 | 1 | Torque will enable host autosign during provisioning time, that means, the user which executes Torque must have: |
|
| 28 | 1 | 1. write access to /etc/puppet/autosign.conf |
|
| 29 | 1 | 2. sudo access to run puppetca |
|
| 30 | 1 | ||
| 31 | 1 | Once a host (which is enabled for build) is requesting a kickstart/jumpstart etc than an entry would be created in the autosign.conf file. |
|
| 32 | 1 | Each operating system will run puppetd after the OS installation but before the first reboot, this will acquire the puppet certificate, then the host will notify Torque that it has finished the installation, and Torque will remove the entry from the autosign file automatically. |
|
| 33 | 1 | ||
| 34 | 1 | ||
| 35 | 5 | Ohad Levy | h1. How do I use Torque with Puppet external nodes? |
| 36 | 1 | ||
| 37 | 8 | Ohad Levy | see [[External Nodes]] |
| 38 | 1 | ||
| 39 | 5 | Ohad Levy | h1. Where is the DB?! |
| 40 | 1 | ||
| 41 | 1 | By default, Torque will use sqlite3 as a database, its configuration can be found at |
|
| 42 | 1 | <pre>config/database.yml</pre> |
|
| 43 | 1 | By default, the database can be found at the db subdirectory. |
|
| 44 | 1 | Torque is a rails application, therefor, anything that is supported under RAILS (sqlite, mysql, postsql, oracle etc) can be used. |
|
| 45 | 1 | ||
| 46 | 5 | Ohad Levy | h1. What about other operating systems? |
| 47 | 1 | ||
| 48 | 1 | Torque currently supports RedHat/Fedora, Debian/Ubuntu and Solaris Jumpstart |
|
| 49 | 1 | it has been successfully tested on CentOS 3,4,5 Fedora 10-11, Ubuntu 9.04 and Solaris 8-10 on Sparc. |
|
| 50 | 1 | ||
| 51 | 1 | If you have any other operating system you would like to see added to Torque, please contact us and we would be happy to add it. |
|
| 52 | 1 | ||
| 53 | 1 | for Jumpstart support, as Solaris doesn't support nativity accessing the profile data dynamically, its required to create some workarounds |
|
| 54 | 1 | example for those are found at the *extras/jumpstart* directory. |
|
| 55 | 1 | You may find the dynamic profile and dynamic finish at the following URL's: |
|
| 56 | 1 | <pre><code>http://Torquehost:3000/unattended/jumpstart_profile |
|
| 57 | 1 | http://Torquehost:3000/unattended/jumpstart_finish</code></pre> |
|
| 58 | 1 | ||
| 59 | 1 | It is also required to add vendor options to your dhcp server if you plan to boot from network on the sparc platform. |
