1. 18 Feb, 2013 1 commit
  2. 13 Feb, 2013 1 commit
  3. 11 Feb, 2013 6 commits
    • Update Lua API · 83c98d82
      Dwight Engen authored
      Add [gs]et_config_path from API to Lua binding. Add additional optional
      parameter to container_new(). Add tests for these new Lua API bindings.
      Commit 2a59a681 changed the meaning of lxc_path_get() in the binding,
      causing lua script breakage. Reinstate original behavior of
      lxc_path_get() and rename it to lxc_default_config_path_get() to make
      its intent clearer.
      Signed-off-by: 's avatarDwight Engen <dwight.engen@oracle.com>
      Acked-by: 's avatarStéphane Graber <stgraber@ubuntu.com>
    • pass lxcpath to lxc_command · 13f5be62
      Serge Hallyn authored
      The previous lxcpath patches added support for a custom LXCPATH set
      through a system-wide configuration file.
      
      This was also exposed through the C api, so that a custom lxcpath could
      be set at the container object instanciation time, or set at runtime.
      
      However the command sock filename was always located under the global
      lxcpath, which could be confusing, and would be a problem for users
      with insufficient perms to the system-wide lxc path (i.e. if setting
      lxcpath to $HOME/lxcbase).  This patch changes that by passing the
      lxcpath to all callers of lxc_command().
      
      It remains to add an lxcpath command line argument to most of the
      command line tools (which are not using the C api) - lxc-start,
      lxc-info, lxc-stop, etc.
      
      At this point it becomes tempting to do something like
      
      	c = lxc.Container("r1", "/var/lib/lxc")
      	c2 = lxc.Container("r1", "$HOME/lxcbase")
      
      However, that's problematic - those two will use the same directory
      names for cgroup directories.
      
      What would be the best way to handle this?  One way (which I kind
      of like) is to give up on naming the cgroups after the container.
      use mkstemp for the cgroup name, let lxc keep track of the cgroup
      name based on the command socket, and make users use lxc-cgroup to get
      and change settings.
      
      Other ideas?
      Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
      Acked-by: 's avatarStéphane Graber <stgraber@ubuntu.com>
    • python-lxc: Update for new calls · edb09f8d
      Stéphane Graber authored
      Add the two new calls to the API and add the new container_path
      parameter to the constructor (optional).
      
      This also extends list_containers to support the config_path parameter.
      At this point none of the actual tools are changed to make use of those
      as we'll probably want to make sure all the tools get the extra option
      at once.
      Signed-off-by: 's avatarStéphane Graber <stgraber@ubuntu.com>
      Tested-by: 's avatarSerge E. Hallyn <serge.hallyn@ubuntu.com>
      Acked-by: 's avatarSerge E. Hallyn <serge.hallyn@ubuntu.com>
    • lxc api: fix some config_path oddities · afeecbba
      Serge Hallyn authored
      1. When calling c->set_config_path(), update configfile.  I.e. if we
      are setting the config_path to /var/lib/lxc, then the configfile should
      be changed to /var/lib/lxc/$container/config
      
      2. Add an optional configpath argument to lxc_container_new.  If NULL,
      then the default will be used (as before).  If set, then the passed-in
      path will be used.  This way you can do
      
      	c1 = lxc.Container("r1", "/var/lib/lxc");
      	c2 = lxc.Container("r2", "/home/user/lxcbase");
      
      (Note I did *not* implement the python or lua binding to pass that
      argument along)
      Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
      Acked-by: 's avatarStéphane Graber <stgraber@ubuntu.com>
    • lxc-create: Improve the layout of the config · 35fef4e6
      Stéphane Graber authored
      This simply adds an extra blank line between the original lxc config
      and the template generated options.
      
      In typical use cases, this means that we'll now get the header, then
      a blank line, then default.conf content, then a blank line and finally
      the template generated config.
      
      The wording of the header is also changed slightly so that it fits in
      the usual 80 columns.
      Signed-off-by: 's avatarStéphane Graber <stgraber@ubuntu.com>
      Acked-by: 's avatarSerge E. Hallyn <serge.hallyn@ubuntu.com>
    • Add missing manpages · 4019712d
      Stéphane Graber authored
      This introduces manpages for:
       - lxc-checkconfig
       - lxc-device
       - lxc-info
       - lxc-netstat
       - lxc-shutdown (wasn't in Makefile)
       - lxc-start-ephemeral
       - lxc-version
      
      This commit also sorts configure.ac and Makefile.am.
      Signed-off-by: 's avatarStéphane Graber <stgraber@ubuntu.com>
      Acked-by: 's avatarSerge E. Hallyn <serge.hallyn@ubuntu.com>
  4. 08 Feb, 2013 6 commits
  5. 06 Feb, 2013 2 commits
  6. 28 Jan, 2013 5 commits
    • add lua binding for the lxc API · f080ffd7
      Dwight Engen authored
      The lua binding is based closely on the python binding. Also included are
      a test program for excercising the binding, and an lxc-top utility for
      showing statistics on running containers.
      Signed-off-by: 's avatarDwight Engen <dwight.engen@oracle.com>
      Acked-by: 's avatarStéphane Graber <stgraber@ubuntu.com>
    • setup_mount_entries: ignore mount failure if 'optional' · 68c152ef
      Serge Hallyn authored
      If 'optional' is in the mount options, then avoid failure in
      mount().
      
      Experiments suggest we could just do this checking data at
      mount_entry(), but that feels less proper than using
      hasmntopt() against the mntent.
      Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
      Acked-by: 's avatarStéphane Graber <stgraber@ubuntu.com>
    • use a default per-container logfile · 5e1e7aaf
      Serge Hallyn authored
      Until now, if a lxc-* (i.e. lxc-start) command did not specify a logfile
      (with -o logfile), the default was effectively 'none'.  With this patch,
      the default becomes a per-container log file.
      
      If a container config file specifies 'lxc.logfile', that will override
      the default.  If a '-o logfile' argument is specifed at lxc-start,
      then that will override both the default and the configuration file
      entry.  Finally, '-o none' can be used to avoid having a logfile at
      all (in other words, the previous default), and that will override
      a lxc.logfile entry in the container configuration file.
      
      If the user does not have rights to open the default, then 'none' will
      be used.  However, in that case an error will show up on console.  (We
      can work on removing that if it annoys people, but I think it is
      helpful, at least while we're still ironing this set out)  If the user
      or container configuration file specified a logfile, and the user does
      not have rights to open the default, then the action will fail.
      
      One slight "mis-behavior" which I have not fixed (and may not fix) is
      that if a lxc.logfile is specified, the default logfile will still
      get created before we read the configuration file to find out there
      is a lxc.logfile entry.
      
      changelog:  Jan 24:
      
       add --enable-configpath-log configure option
      
       When we log to /var/lib/lxc/$container/$container.log, several things
       need to be done differently than when we log into /var/log/lxc (for
       instance).  So give it a configure option so we know what to do
      
       When the user specifies a logfile, we bail if we can't open it.  But
       when opening the default logfile, the user may not have rights to
       open it, so in that case ignore it and continue as if using 'none'.
      
       When using /var/lib/lxc/$c/$c.log, we use $LOGPATH/$name/$name.log.
       Otherwise, we use $LOGPATH/$name.log.
      
       When using /var/lib/lxc/$c/$c.log, don't try to create the log path
       /var/lib/lxc/$c.  It can only not exist if the container doesn't
       exist.  We don't want to create the directory in that case.  When
       using /var/log/lxc, then we do want to create the path if it does
       not exist.
      Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
      Acked-by: 's avatarStéphane Graber <stgraber@ubuntu.com>
    • oracle template: fix sudo lxc-create on ubuntu · 1ff8a460
      Dwight Engen authored
      rpm on ubuntu puts the rpm db under $HOME, which wont be /root if
      sudo is used
      Signed-off-by: 's avatarDwight Engen <dwight.engen@oracle.com>
      Acked-by: 's avatarStéphane Graber <stgraber@ubuntu.com>
  7. 23 Jan, 2013 3 commits
  8. 22 Jan, 2013 4 commits
  9. 21 Jan, 2013 1 commit
  10. 15 Jan, 2013 7 commits
  11. 14 Jan, 2013 2 commits
    • MAKEDEV call, add autodev hooks, add environment variables for hook scripts. · f7bee6c6
      Michael H. Warfield authored
      Ok...  Here's the patch again.  Since Serge is removing the loglevel
      structure member, this patch no longer references that element.
      
      From the original description:
      
      1) Removes run_makedev() and the call to it from conf.c per discussion.
      
      2) Adds an lxc.hook.autodev hook.
      
      Note: This hook is very close (one routine level abstracted) from where
      the run_makedev was called.  Anyone really rrreeeaaalllyyy needing
      MAKEDEV can add it in with a small shim script to do whatever they want
      under whatever distro they're using, so no functionality is lost there.
      
      3) Added a number of environment variables for all the hook scripts to
      reference to assist in execution.  Things like LXC_ROOTFS_MOUNT could be
      very useful but others were added as well.  Room for more if anyone has
      an itch.  All in one spot in lxc_start.c.
      
      4) clearenv and putenv( "container=lxc" ) calls were moved to just after
      the "start" hook in the container just prior to actually firing up the
      container so we could use environment variables prior to that and have
      them flushed them before firing up init.  Nice side effect is that you
      can define environment variables and then call lxc-start and have them
      show up in those hooks scripts.
      
      5) I actually DID update the man page for lxc.conf!  I guess I lied when
      I said I wouldn't get that done.
      
      [... and ...]
      
      I added the rcfile to the lxc_conf structure as suggested and moved the
      setenv bundle from lxc-start.c over to start.c just prior to calling
      run_lxc_hooks for the pre-start hook.
      Signed-off-by: 's avatarMichael H. Warfield <mhw@WittsEnd.com>
      Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
    • remove logfile and loglevel from struct lxc_conf · 9ea87d5d
      Serge Hallyn authored
      The options are still supported in the lxc configuration file.
      However they are stored only in local variables in src/lxc/log.c,
      which can be read using two new functions:
      	int lxc_log_get_level(void);
      	const char *lxc_log_get_file(void);
      
      Changelog: jan 14:
       have lxc_log_init use lxc_log_set_file(), have lxc_log_set_file() take
       a const char *, and have it keep its own strdup'd copy of the filename.
      Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
  12. 13 Jan, 2013 1 commit
  13. 11 Jan, 2013 1 commit