[Thincrust-devel] Re: Auto-discard notification

[Bryan Kearney]

thincrust-devel-bounces at redhat.com wrote:
> The attached message has been automatically discarded.
> 
> 
> ------------------------------------------------------------------------
> 
> Subject:
> Re: [Thincrust-devel] Re: [virt-devel] oVirt Node image build process
> From:
> "Daniel P. Berrange" <berrange at redhat.com>
> Date:
> Thu, 6 Nov 2008 10:25:12 +0000
> To:
> Perry Myers <pmyers at redhat.com>
> 
> To:
> Perry Myers <pmyers at redhat.com>
> CC:
> David Huff <dhuff at redhat.com>, Thincrust tooling devel list 
> <thincrust-devel at redhat.com>, rcm-tools at redhat.com
> 
> 
> On Thu, Nov 06, 2008 at 12:14:20AM -0500, Perry Myers wrote:
>> David Huff wrote:
>>> Perry Myers wrote:
>>>> Daniel P. Berrange wrote:
>>>>> The rpm -qa output of the guest OS is good, but while I remember, we 
>>>>> must
>>>>> also make sure we save the list of RPMs used by the livecd-creator 
>>>>> itself
>>>>> when building the images. We'll need this info in order to determine
>>>>> whether a RPM security update requires us to re-generate a new image.
>>>>>
>>>>> This probably needs the live-creator to output an explicit report of
>>>>> what it installed.
>>>> Agreed.  cc'ing thincrust-devel so that David Huff can add this to his 
>>>> list of things todo for the November code freeze.
>>>>
>>>> What we want is an option for livecd-creator to output a list of RPMs 
>>>> installed in the livecd.  appliance-creator should also expose this 
>>>> functionality.
>>> This will should not be to hard to add, however my initial thought is 
>>> that is information is already included in the kickstart file.  The 
>>> kickstart file includes all info about the created appliance ans as long 
>>> as the same tools and ks file is used the appliance should be reproducible.
>> This is not correct.  The kickstart provides a package list without the 
>> full dependency chain.  So if I include only "appliance-tools" in the 
>> kickstart %packages section that doesn't describe all of the packages that 
>> were installed in the OS due to dependencies.
>>
>> The other thing the kickstart does not provide are the specific versions 
>> installed.
> 
> Indeed - the kickstart package list is mostly useless.
> 
> We also cannot rely on the resulting contents of the /var/lib/rpm database,
> because there may be important packages used during building of the image
> that are later removed in th %post, and we need to know about them.
> 
> The only reliable way to get the listing of packages is to have this
> functionality built-in to the applice/livecd creator tool. It is using
> the YUM api, and can directly extract the actual list of RPMs in the
> packageset.

Daniel:

the goal is to get that in. As a work around, could pungi be used as a 
post process?

-- bk