Editing Device management using Bcfg2
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 229: | Line 229: | ||
One thing to like in Bcfg2 is that it does not mandate things too much. Third item is an example of that. Bcfg2 allows short-circuiting the Literal layer processing altogether by adding "Bound" in front of the keyword. In a simple cases where what we want exactly is already known already at abstract level this can simplify things. | One thing to like in Bcfg2 is that it does not mandate things too much. Third item is an example of that. Bcfg2 allows short-circuiting the Literal layer processing altogether by adding "Bound" in front of the keyword. In a simple cases where what we want exactly is already known already at abstract level this can simplify things. | ||
- | === Hooking the Device and Bcfg2 | + | === Hooking the Device and Bcfg2 together === |
- | + | Add following line into <code>/var/lib/bcfg2/Metadata/clients.xml</code> | |
<Client uuid="foo" name="bar" profile="maemo" password="xyzzy" pingable="N" location="floating" auth="cert+password"/> | <Client uuid="foo" name="bar" profile="maemo" password="xyzzy" pingable="N" location="floating" auth="cert+password"/> | ||
Line 249: | Line 249: | ||
bcfg2 -I | bcfg2 -I | ||
- | You should | + | You should see a confirmation prompt for each configuration item defined in the samole configuration, due to use of <code>-I</code> option. |
<hr/> | <hr/> |
Learn more about Contributing to the wiki.