[lxc-devel] liblxc, lxc-browse()

Francois-Xavier Bourlet francois-xavier.bourlet at dotcloud.com
Mon May 2 17:29:55 UTC 2011


Hello,

Any news about a possible integration of my patch?

On Tue, Apr 19, 2011 at 12:57 PM, Francois-Xavier Bourlet
<francois-xavier.bourlet at dotcloud.com> wrote:
> Oops, forgot to CC the mailing list!
>
> here's my answer:
>
> On Fri, Apr 15, 2011 at 9:58 AM, Francois-Xavier Bourlet
> <francois-xavier.bourlet at dotcloud.com> wrote:
>> Yes I confirm what Gregory said. The purpose is to run some user code
>> for each container (based on the name of it) for who link to the LXC
>> library.
>>
>> I am actually working on a library to provide statistics about LXC
>> containers, and I need an "C" way to browse containers. To keep the
>> code manageable I would prefer to move the logic of the browse itself
>> into liblxc. So every future modification of LibLXC would be
>> transparent for every application browsing containers.
>>
>> Using an hard path is not acceptable and using a lxc_getpath() way is
>> not so much better.
>>
>> If you have any other idea feel free to express it, I am open to any suggestion.
>>
>> Thanks
>>
>> On Fri, Apr 15, 2011 at 9:43 AM, Greg Kurz <gkurz at fr.ibm.com> wrote:
>>> On Fri, 2011-04-15 at 10:00 -0500, Rob Landley wrote:
>>>> On 04/13/2011 12:49 PM, Francois-Xavier Bourlet wrote:
>>>> > Hi,
>>>> >
>>>> > Here's a patch with the purpose adding a way to browse containers trough liblxc.
>>>>
>>>> What does "browse" mean in this context?
>>>>
>>>
>>> By reading the code, "browse" seems to mean "run some user code with a
>>> user provided context for each container".
>>>
>>>> > I added the function lxc-browse, that simply call back a function with
>>>> > the container name as parameter.
>>>>
>>>> So, get a list of the containers?  Like lxc-ls?
>>>>
>>>> > It help to abstract how to browse containers without needed to know
>>>> > the underlaying structure of LXC.
>>>>
>>>> for i in $(lxc-ls); do lxc-info -n $i; done
>>>>
>>>> I don't understand the purpose of this patch.
>>>>
>>>
>>> I guess this patch offers a for-each-container feature for users that
>>> link directly into liblxc rather than using lxc commands.
>>>
>>> Francois-Xavier, do you confirm ?
>>>
>>> --
>>> Gregory Kurz                                     gkurz at fr.ibm.com
>>> Software Engineer @ IBM/Meiosys                  http://www.ibm.com
>>> Tel +33 (0)534 638 479                           Fax +33 (0)561 400 420
>>>
>>> "Anarchy is about taking complete responsibility for yourself."
>>>        Alan Moore.
>>>
>>>
>>
>>
>>
>> --
>> François-Xavier Bourlet
>>
>
>
>
> --
> François-Xavier Bourlet
>



-- 
François-Xavier Bourlet




More information about the lxc-devel mailing list