Quoting Jay Taylor (j...@jaytaylor.com): > Hey Serge, > > > On Tue, Aug 20, 2013 at 1:55 PM, Serge Hallyn <serge.hal...@ubuntu.com>wrote: > > > Hi, > > > > one idea that has been brought up is to support 'aliases'. So if you're > > locally building a daily pristine container, say at 'c-2013-08-20', > > you might want to then have a 'c-latest' alias or link pointing to the > > latest container, so you can always just > > > > sudo lxc-clone -o c-latest -n test1 -s > > > > The most obvious idea would be to use a symbolic link. However, while > > that mostly works, it's actually not perfect - lxc_container_new() > > will be called with the name you passed in (c-latest), not with the > > symlinked name. > > > > Another idea would be to support a $lxcpath/$lxcname/config consisting > > of only 'lxc.alias = c-2013-0820'. > > > > Do people have any other ideas? > > > > I'm thinking symbolic link may be the simplest thing to support - > > lxc_container_new() could immediately readlink() to get the real > > container name. > > > > I like the idea of using a symlink - it'd make it simple and intuitive to > understand what's going on. > > What would happen when you run lxc-destroy on an alias? Will it destroy > the symlink or the container being pointed to?
Good question :) The easier thing would be to make it destroy what is being pointed to. But I'm not sure right now - is that behavior weird, or useful? ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
