[Beaker-devel] Tool for Inventory gathering
Nick Coghlan
ncoghlan at redhat.com
Tue Jul 16 01:21:47 UTC 2013
On 07/16/2013 10:02 AM, Amit Saha wrote:
>
>
> ----- Original Message -----
>> From: "Nick Coghlan" <ncoghlan at redhat.com>
>> To: beaker-devel at lists.fedorahosted.org
>> Sent: Thursday, July 11, 2013 5:40:10 PM
>> Subject: Re: [Beaker-devel] Tool for Inventory gathering
>>
>> On 07/11/2013 02:12 PM, Dan Callaghan wrote:
>>> The GitHub approach works best if upstream is on GitHub as well though,
>>> so maybe we should ask that before anything else...
>>
>> Bringing the list up to date with today's IRC discussion: Amit has
>> contacted Lyonel offering our assistance in finishing the migration to
>> GitHub (there is already a repo there, but nothing in it).
>
> Lyonel emailed me this morning saying that he has got everything up now here:
> https://github.com/lyonel/lshw
>
>
>>
>> If that happens, then I think Dan's plan will work nicely - we'll
>> maintain beaker-lshw as a fork on GitHub and submit pull requests
>> upstream for any changes we make, while packaging beaker-lshw for our
>> own use to ensure we maintain control over our release cycles.
>
> So, looks like we are set to go.
Yay!
I've been thinking further about this based on our IRC discussion the
other day, and I'm thinking it makes sense to do a few things in the
0.15 time frame (i.e. by the end of August):
1. Create our own lshw fork as beaker-lshw, that we keep close to
upstream lshw (aside from the different name) and submit pull requests
on GitHub whenever we change anything
2. Create a separate beaker-systemscan project on beaker-project.org
that we separate out from
http://git.beaker-project.org/cgit/beaker/tree/Tasks/distribution/inventory/?h=develop
3. Change our inventory task to depend on beaker-systemscan and just
upload the scan results to the Beaker server rather than containing the
scanning logic directly
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane
Testing Solutions Team Lead
Beaker Development Lead (http://beaker-project.org/)
More information about the Beaker-devel
mailing list