Michael DeHaan wrote:
> Dustin Black wrote:
>
>> I've imported a slew of operating system shares into cobbler as so:
>>
>> # cobbler import --mirror=/install_images/mnt --name=CBLR
>> --available-as=http://10.0.0.1/install_images/mnt
>>
>> I've then created some custom profiles using the imported distros and
>> pointing to a specific new kickstart file.
>>
>> Later, I've added some other OS shares to /install_images/mnt, and
>> performed the cobbler import command again to add the new distros to
>> cobbler. When I run this second import, the kickstarts for the custom
>> profiles are reset back to the sample.ks or sample_end.ks files.
>>
>> Is this expected behavior, and if so, what should I be doing
>> differently?
>>
>> Regards,
>> Dustin L. Black, RHCE
>> _______________________________________________
>> cobbler mailing list
>> cobbler(a)lists.fedorahosted.org
>>
https://fedorahosted.org/mailman/listinfo/cobbler
>>
>>
> The idea of running cobbler import against the same distro/profile name
> is undefined (at least, in my eyes), so we have the opportunity to
> define it.
>
> We could either:
>
> (A) fail the import... or
> (B) just let it redo the rsync and leave the other variables intact
>
> It seems like you'd like B, which also seems better to me, so what we
> want to do I believe is make sure that if an object of the same name
> exists we edit that object, rather than making a new one and overwriting
> it. This way, cobbler import becomes a handy way to redo the rsync.
>
> Does this sound right?
>
> That all being said, I'm still not sure of the use case of wanting to
> redo the rsync, unless possibly the distro has been respun with
> something like pungi/Revisor? Let me know.
>
> As you mentioned it, that seems like a bug to me.
>
> --Michael
>
>
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/cobbler
>
Option B is definitely what I'm looking for.
I'm running cobbler import against a directory containing many
sub-directories where the distro install images are mounted, so it picks
all of them up at once, adding each distro and its standard and xen
profiles.
Definitely. That was one of the reasons I wrote import like that to
begin with (we have a very large NFS directory with all of our trees on it).
If I later make more distro install images available via this
directory
structure, I want to use cobbler import to add those new distros and
profiles en masse, but I don't want to disturb the distros previously
imported.
In particular, I would say that the import mechanism shouldn't be
touching the custom profiles, even if it were going to reset the default
profiles that are created.
-Dustin
_______________________________________________
cobbler mailing list
cobbler(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler