[et-mgmt-tools] Cobbler install/kickstart question

[Michael DeHaan]

Maute, Kevin P CTR AFRL/VAOO wrote:
> Michael,
>
> When you say DVD import do you literally mean DVD?  I created a HD
> filesystem which was the standard copy of all the Server CDs DLed from
> RHN.  I actually DID get a DVD from the RHCT class I took last month
> :-).  And, yes I did do a cobbler import as we discussed previously.
>   

Either one works as long as the directory layout is basically the same.

> Also, I removed all the distros and profiles that cobbler created (using
> cobbler {distro,profile} remove!) and recreated them.  I just noticed
> the dates in /var/www/cobbler/ks_mirror has old dates for the repodata &
> repoview dirs.  Is this copying the repo metadata from my local repo or
> creating new dirs? 
>   
Those might be the creation dates of the files on the CD media. Rsync is 
being invoked with
-a.


> Lastly, I did retain the variables in the original ks template from
> /etc/cobbler.  In the "output" ks file I see the comment about the add'l
> repos but the $yum_repo_stanza appears to be empty as there is no value
> on the next line.  BTW, $yum_config_stanza does expand to "wget ..." so
> it is expanding "some" vars.  I assume $kickstart_done is a sentinel
> variable as it also does not generate any strings.
>
>   

It seems like the import process did not find the cluster repos from the 
DVD import.

If that is not working, one way to do get the same content would be to 
just add them as regular yum repositories
in cobbler.

cobbler repo add --name=rhel5i386clustering 
--mirror=/path/to/DVD/source/Clustering
# repeat for other source repos
cobbler repo add --name=epel5i386testing 
--mirror=http://download.fedora.redhat.com/pub/epel/testing/5/i386/
cobbler reposync
cobbler repo edit --name=rhel5i386clustering --keep-updated=0
cobbler profile edit --name=rhel-5-i386 --repos="rhel5i386clustering 
rhel5i386epeltesting"
cobbler sync

Notice though that there are some fixes to repo management in 0.6.1 
(especially related to non-http/ftp mirrors), so that's
something to be aware of.

> I tried again (@clustering) and still get grief.
>
> Stepping back, what I would like is not only the clustering and later vt
> support but also EPEL as well.  Interestingly, everytime I do a distro
> and profile I DO get the correspondnig xen one as well.  
>   

See above on the epel bits. Those work via "cobbler repo add" as do any 
arbitrary yum repo.

Admitedly I would have expected your RHEL 5 clustering repo to be added 
automatically in the kickstarts and I'll do some
testing on my end to make sure that feature still works.

>   
>> -----Original Message-----
>> From: et-mgmt-tools-bounces at redhat.com 
>> [mailto:et-mgmt-tools-bounces at redhat.com] On Behalf Of Michael DeHaan
>> Sent: Wednesday, August 29, 2007 10:50 AM
>> To: Fedora/Linux Management Tools
>> Subject: Re: [et-mgmt-tools] Cobbler install/kickstart question
>>
>> Maute, Kevin P CTR AFRL/VAOO wrote:
>>     
>>> Folks,
>>>
>>> Be kind to a newbie. Michael has been a big help but now I need to 
>>> expand my net.
>>>
>>> I am moving at a pretty good pace now that I found cobbler 
>>>       
>> but I am a 
>>     
>>> bit stuck. I am trying to get kickstart to recognize the 
>>>       
>> RPMs in the 
>>     
>>> Cluster dir of RHEL5 Sever. It shows up correctly in my 
>>>       
>> local repo but 
>>     
>>> everytime I add it to my ks package list I get the dreaded 
>>> Abort/Continue dialog. I realize this might be better asked on the 
>>> kickstart list BUT I thought I would start here since I see 
>>>       
>> a lot of 
>>     
>>> virtualization activity which from a kickstart perspective 
>>>       
>> is probably 
>>     
>>> similar...
>>>
>>>       
>> This sounds like a good question for this list to me, 
>> especially if it 
>> involves setting up RHEL 5 with your Cobbler boot server.
>>
>> Quick question -- Did you start your configuration with an DVD import 
>> using "cobbler import" ? If so, cobbler should be keeping 
>> track of the 
>> individual "split" repos for RHEL5, and making them available in the 
>> kickstart file. It should have also ran createrepo on each split 
>> repository such that it has correct yum metadata.
>>
>> Basically if you look at the rendered kickstart file in 
>> /var/www/cobbler/kickstarts/$name (this is the output of cobbler, not 
>> the input), you should see a couple of extra "repo"
>> lines that represent the additional repos that have been attached.
>>
>> If you are not using a kickstart template based off one of 
>> the ones that 
>> shipped in cobbler (/etc/cobbler/*.ks) you may be missing the 
>> directive 
>> ($yum_repo_stanza) that allows
>> for attaching of these associated repos automatically. To see what 
>> kickstart template you are using, run "cobbler profile report 
>> $profilename".
>>
>> --Michael
>>
>>
>>     
>>> Thanks,
>>> Kevin
>>>
>>>
>>> *--------------------------------------------*
>>> *Kevin Maute*
>>> Sr. Linux/Unix System Administrator
>>> RCF Information Systems
>>> AFRL/VAOO Contractor
>>> 937.255.1810
>>> kevin.maute at wpafb.af.mil
>>>
>>>
>>>       
>> --------------------------------------------------------------
>> ----------
>>     
>>> _______________________________________________
>>> et-mgmt-tools mailing list
>>> et-mgmt-tools at redhat.com
>>> https://www.redhat.com/mailman/listinfo/et-mgmt-tools
>>>       
>> _______________________________________________
>> et-mgmt-tools mailing list
>> et-mgmt-tools at redhat.com
>> https://www.redhat.com/mailman/listinfo/et-mgmt-tools
>>
>>     
>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools at redhat.com
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools
>