Hi all, as i'm using a farm of LXC hosts I want to add a network wire feature to the "API wishlist". In fact, this might be some frontend daemon, which offers remote network access to local LXC in conjunction with a proxy client counterpart, which will locally provide the API of an remote host. To be serious, this network interface will need some kind of authentication.
To allow access to multiple remote hosts, the usage of the LXC-API will need some (optional) address feature. And the userland programs either all need to support an option for this. Or there might be a clever trick to pass it's run to an special proxy program (use 'lxc-proxy remote lxc-foo ...' instead of 'lxc-foo ...') or an environment variable evaluated by the API-lib (use 'lxc_proxy=remote lx-foo ...'). This set of features will allow on to build up an application for centralized LXC cluster status visualization and control. Greetings Guido ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
