In trying the command below, the newly created subprofile doesn't look
anything like the parent when doing a report against it.
[root@ronin ~]# cobbler profile report --name=Centos4.7-i386
profile : Centos4.7-i386
distro : Centos4.7-i386
comment :
created : Thu Jan 1 01:00:00 1970
dhcp tag : default
enable menu : True
kernel options : {}
kickstart : /etc/cobbler/legacy.ks
ks metadata : {}
mgmt classes : []
modified : Thu Jan 1 01:00:00 1970
name servers : []
owners : ['admin']
post kernel options : {}
redhat mgmt key : <<inherit>>
repos : []
server : <<inherit>>
template_files : {}
virt bridge : xenbr0
virt cpus : 1
virt file size : 10
virt path :
virt ram : 512
virt type : qemu
[root@ronin ~]# cobbler profile add --name=test --inherit='Centos4.7-i386'
[root@ronin ~]# cobbler profile report --name=test
profile : test
parent : Centos4.7-i386
comment :
created : Sun Feb 1 08:35:24 2009
dhcp tag : <<inherit>>
enable menu : False
kernel options : <<inherit>>
kickstart : <<inherit>>
ks metadata : <<inherit>>
mgmt classes : ['<<inherit>>']
modified : Sun Feb 1 08:35:24 2009
name servers : <<inherit>>
owners : ['admin']
post kernel options : <<inherit>>
redhat mgmt key : <<inherit>>
repos : <<inherit>>
server : <<inherit>>
template_files : {}
virt bridge : <<inherit>>
virt cpus : <<inherit>>
virt file size : <<inherit>>
virt path : <<inherit>>
virt ram : <<inherit>>
virt type : <<inherit>>
I expected to see anything defined in the parent as part of the new
profile. Is that not a correct expectation or did I do something
blatantly wrong?
Thanks
Corey
On Sat, Jan 31, 2009 at 2:47 AM, Christopher Johnston
<cjohnstonwork(a)gmail.com> wrote:
Something like this can be done, I wasnt aware of this feature which
is
quite useful for us as we may have different profiles for various clock=
settings or scheduler=, things of that nature.
root@xenguest02:/etc# cobbler profile add --name=test
--inherit=Fedora-9-x86_64 --distro=Fedora-9-x86_64