Re: [lxc-devel] liblxc, lxc-browse()
On 04/15/2011 06:43 PM, Greg Kurz 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 ? François-Xavier ? Sauf indication contraire ci-dessus: Compagnie IBM France Siège Social : Tour Descartes, 2, avenue Gambetta, La Défense 5, 92400 Courbevoie RCS Nanterre 552 118 465 Forme Sociale : S.A.S. Capital Social : 542.737.118 ? SIREN/SIRET : 552 118 465 02430 -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
Re: [lxc-devel] Status of usability of lxc
On Tue, Mar 22, 2011 at 10:20 AM, Nathan McSween wrote: > Can I get a quick rundown of what is implemented w.r.t UID/GID > containerization, is it safe yet to give containerized root to an > everyday user without huge security issues? Drop all dangerous capabilities and mount /proc read-only. HTH, //richard > -- > Xperia(TM) PLAY > It's a major breakthrough. An authentic gaming > smartphone on the nation's most reliable network. > And it wants your games. > http://p.sf.net/sfu/verizon-sfdev > ___ > Lxc-devel mailing list > Lxc-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lxc-devel > -- Thanks, //richard -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
Re: [lxc-devel] liblxc, lxc-browse()
Oops, forgot to CC the mailing list! here's my answer: On Fri, Apr 15, 2011 at 9:58 AM, Francois-Xavier Bourlet 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 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 gk...@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 -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev ___ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
