Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Cc: dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org,
	zulcss-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org,
	erkan yanar <erkan.yanar-z+G3R6qIeCAZId6A0yLOdQ@public.gmane.org>,
	Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>,
	"Eric W. Biederman"
	<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>,
	Dave Walker <davewalker-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>,
	Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
	"Trent W. Buck"
	<twb-3AaVwj9c10wJYc8buCWFOBCuuivNXqWP@public.gmane.org>,
	stgraber-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org
Subject: 2011 LXC development mini-conf?
Date: Thu, 10 Mar 2011 10:30:35 -0600	[thread overview]
Message-ID: <20110310163035.GA15508@peq.hallyn.com> (raw)

Hi,

Hi, I'm sending this email to gauge interest in a lxc development
mini-conf this summer.  Last year we had many lxc sessions at the
Ubuntu Developer Conference.  I'm all for doing that again, but
while that gives us 'free' scheduling and logistics and a nice focus
on realistic short-term development goals, I fear making it seem
like ubuntu is trying to hijack lxc, and I don't want to make people
on fedora, gentoo, etc to feel there is a barrier to their
attending (*).  Erkan suggested froscon (http://www.froscon.de/), in
Germany Aug 20-21, as a potential site.

If you're interested in attending and that location is ok with
you, please let me know.  If you're interested in attending and
you'd like to suggest another location, please do so.

The focus of the mini-conf is simple: improve LXC.  That means
the lxc toolsuite itself, kernel features exploitable by lxc,
and system management and integration of lxc.

Below is a start to a potential topic list.  If we were to turn
part of this into a hack-fest, we could probably pound out some
of these right there on site.  I think I like the idea of doing
a half day to go over the topics list - write down who is
interested in doing what and who may have tried/started some
of these before, then spend a day (while intermingling with
froscon) hacking, then a half-day wrapup.  That's just a suggestion
though, and perhaps too unorthodox of one.

Potential topics:
	landscape of current (and likely/hopeful) lxc users and use-cases
		to help prioritize development
	container reboot and shutdown
	per-container dmesg
	user namespaces
	lxc LSM integration
	libvirt
		Serge never wrote the libvirt-lxc wrapper driver
		Sentiment is that libvirt should handle container auto-start and networking
		(Some might argue that)
		Discuss
	container startup debugging
		typical irc 'help' converstations suggest there is a problem
	management interface
		curses-based
		other
	udev and device namespaces
		to prevent udev storms on device hotplug
	checkpoint/restart

thanks,
-serge

(*) There still will be LXC sessions at UDS this May, and I highly
encourage developers and users of/on other distros to attend, if only,
as I will be, online.

             reply	other threads:[~2011-03-10 16:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 16:30 Serge E. Hallyn [this message]
     [not found] ` <20110310163035.GA15508-BtbdaCaBcfOTUehee3IRJA@public.gmane.org>
2011-03-10 17:37   ` 2011 LXC development mini-conf? Dhaval Giani
     [not found]     ` <AANLkTikVn=26ci7gxp=yO3DYMALSHy9tFzspjkbvGpqP-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-11 11:56       ` erkan yanar
     [not found]         ` <1Py0xZ-00056Y-17-z+G3R6qIeCAZId6A0yLOdQ@public.gmane.org>
2011-03-11 11:57           ` Dhaval Giani
     [not found]             ` <AANLkTin94cjqT1c-2_EK-V5i+DGVBFnWsw-Q45_nJ5z6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-11 12:10               ` erkan yanar
2011-03-11 12:59               ` Dave Walker
     [not found]                 ` <4D7A1CCC.10303-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
2011-03-11 13:25                   ` Chuck Short
     [not found]                     ` <20110311082509.71f9795d-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2011-03-11 14:09                       ` Serge E. Hallyn
     [not found]                         ` <20110311140941.GA31430-BtbdaCaBcfOTUehee3IRJA@public.gmane.org>
2011-03-11 14:28                           ` Serge E. Hallyn
     [not found]                             ` <20110311142812.GA10924-BtbdaCaBcfOTUehee3IRJA@public.gmane.org>
2011-03-11 14:36                               ` Daniel Lezcano
     [not found]                                 ` <4D7A3353.40905-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2011-03-12  3:27                                   ` Serge E. Hallyn
2011-03-11 14:20                       ` Dhaval Giani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110310163035.GA15508@peq.hallyn.com \
    --to=serge.hallyn-gewih/nmzzlqt0dzr+alfa@public.gmane.org \
    --cc=clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=davewalker-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
    --cc=dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
    --cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
    --cc=erkan.yanar-z+G3R6qIeCAZId6A0yLOdQ@public.gmane.org \
    --cc=stgraber-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
    --cc=twb-3AaVwj9c10wJYc8buCWFOBCuuivNXqWP@public.gmane.org \
    --cc=zulcss-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox