userspace:centos_6.3
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
userspace:centos_6.3 [2013/02/06 20:29] SisterOfMercy |
userspace:centos_6.3 [2021/08/23 08:37] (current) |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| // | // | ||
| With a different DHCP server you will have to look for the correct commands.\\ | With a different DHCP server you will have to look for the correct commands.\\ | ||
| - | (insert | + | The static lease looks a bit like this (with DD-WRT): |
| + | {{http:// | ||
| I use [[http:// | I use [[http:// | ||
| Line 51: | Line 53: | ||
| </ | </ | ||
| - | ===== iptables | + | ===== Iptables |
| - | To make OPSI work correctly we have to open some ports on the firewall. I can never remember the iptables commands, and with Spacewalk I deployed the following to: / | + | To make OPSI work correctly we have to open some ports on the firewall. I can never remember the iptables commands, and with Spacewalk I deployed the following to: / |
| + | |||
| + | //(In my case, after clean installation of Centos 6.3 the path of the file is not the same. On my machine the file is located at: / | ||
| <code winst> | <code winst> | ||
| # Firewall configuration written by system-config-firewall | # Firewall configuration written by system-config-firewall | ||
| Line 82: | Line 86: | ||
| TCP ports 4441 and 4447 are of course used by OPSI.\\ | TCP ports 4441 and 4447 are of course used by OPSI.\\ | ||
| - | ===== opsi configuration ===== | + | ===== OPSI configuration ===== |
| Now we are going to edit the opsi configuration files:\\ | Now we are going to edit the opsi configuration files:\\ | ||
| This is / | This is / | ||
| Line 150: | Line 154: | ||
| / | / | ||
| </ | </ | ||
| - | |||
| - | We also have to install a Java runtime:\\ | ||
| - | <code winst> | ||
| - | yum install java-1.7.0-openjdk | ||
| - | update-alternatives --config java | ||
| - | </ | ||
| - | |||
| - | I did not have any problems with this OpenJDK runtime. However, if you wish, you could install the Sun Java Runtime. If you download the rpm from the [[http:// | ||
| - | After installation I think the alternatives can be installed with these commands (perhaps you have to change the version number. No warranty, I just nicked this off some website I found):\\ | ||
| - | <code winst> | ||
| - | alternatives --install / | ||
| - | alternatives --install / | ||
| - | </code | ||
| - | Of course, don't use these commands when you think the OpenJDK runtime will work for you!\\ | ||
| To set the password of the pcpatch user, we use this command:\\ | To set the password of the pcpatch user, we use this command:\\ | ||
| Line 271: | Line 261: | ||
| If I have transcribed my notes correctly you now have a working OPSI server!\\ | If I have transcribed my notes correctly you now have a working OPSI server!\\ | ||
| - | If not, it isn't my fault! ;-) | + | If not, it isn't my fault! ;-)\\ |
| + | \\ | ||
| + | I was talking with the nice people at uib.de, and it seems the mysql backend can be used for hardware and software audit purposes, without a license. When I find the time I will expand this entry to include the mysql configuration. | ||
| + | |||
| + | ==== Change to mysql for inventory ==== | ||
| + | |||
| + | |||
| + | That's right and we recommend to use the mysql-Database for inventory-functions. To change from file-backend to mysql for the inventory data, you must at first install the mysql-server. If you don't have done before, you can use the following commands: | ||
| + | |||
| + | <code bash> | ||
| + | yum install mysql-server | ||
| + | / | ||
| + | mysql_secure_installation | ||
| + | chkconfig mysqld on | ||
| + | </ | ||
| + | |||
| + | No you can run opsi-setup to configure your mysql-database (create a opsi database, create opsi user, set privileges and patch backend-configuration file from opsi.) For the next step you need the root password, that you have set with the command: mysql_secure_installation: | ||
| + | |||
| + | <code bash> | ||
| + | opsi-setup --configure-mysql | ||
| + | </ | ||
| + | |||
| + | Now you must configure the opsi-Dispatcher to use mysql for Hard- and Software Inventory (You should set the licensemanagement to mysql-server too. If you don't use opsi-licensemanagement, | ||
| + | |||
| + | < | ||
| + | / | ||
| + | </ | ||
| + | |||
| + | The important entries are the following: | ||
| + | |||
| + | |||
| + | backend_.* | ||
| + | ...\\ | ||
| + | license.* | ||
| + | softwareLicense.* | ||
| + | audit.* | ||
| + | ...\\ | ||
| + | |||
| + | After a new init-current-config and a webservice-restart your Inventory-data should be written in mysql: | ||
| + | |||
| + | <code bash> | ||
| + | opsi-setup --init-current-config | ||
| + | / | ||
| + | / | ||
| + | </ | ||
| + | |||
| + | **Finally your right, to use mysql for the Inventorydata, | ||
| + | |||
userspace/centos_6.3.1360182560.txt.gz · Last modified: 2021/08/23 08:37 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
