
Naming Conventions
21
sudo cobbler system find --profile="abc" | xargs -n1 --replace cobbler
system edit --name={} --profile="def" --netboot-enabled=1
Setting an additional templating variable on a profile without modifying any of the other variables
sudo cobbler profile edit --name=profilename --kopts="variablename=3" --in-
place
Assigning various variables to a system record, disregarding old variables that might be set
sudo cobbler system edit --name=systemname --kopts="selinux=disabled
asdf=jkl"
Setting all new installs of any profile containing webserver as a string to use a profile named RHEL5-
i386 instead of RHEL 4 for any new installs.
sudo cobbler profile find --name="*webserver*" | xargs -n1 --replace
cobbler profile edit --name={} --profile="RHEL5-i386"
Generating a net install ISO to install systems that cannot PXE
sudo cobbler buildiso [--help]
9.4. Naming Conventions
Satellite manipulates Cobbler distributions, profiles, and systems. To help keep data in sync between
itself and Cobbler, Satellite relies on some naming conventions for these object types:
• distributions: $tree_name:$org_id:$org_name (if manually created)
Or $tree_name (if synced by Satellite Sync)
• profiles: $profile_name:$org_id:$org_name
• systems: FIXME
You will encounter these somewhat cryptic looking names if you choose to interact with Cobbler
directly at the command line. Note that it is vitally important that you not alter Satellite generated
names so long as you want to allow Satellite to maintain the objects in question.
Note
Satellite does not create or recognize Cobbler "repo" objects. Satellite's equivalent derives
from its notion of channels and is a function of a layer of logic over them. It takes the form
of a special URL which Cobbler is made to use instead.
Commenti su questo manuale