Re: [lxc-devel] RFC: aliases

2013-08-21 Thread Serge Hallyn
Quoting S.Çağlar Onur (cag...@10ur.org): > Hey Serge, > > I'm not opposed the idea but just trying to understand the motivation > behind it. We are doing exactly what you described (daily builds uses > somename-date-buildnumber and two symlinks latest and stable points some > containers) and I'm j

Re: [lxc-devel] RFC: aliases

2013-08-21 Thread S . Çağlar Onur
Hey Serge, I'm not opposed the idea but just trying to understand the motivation behind it. We are doing exactly what you described (daily builds uses somename-date-buildnumber and two symlinks latest and stable points some containers) and I'm just using something like following sudo lxc-clone -o

Re: [lxc-devel] RFC: aliases

2013-08-21 Thread Dwight Engen
On Wed, 21 Aug 2013 07:59:11 -0500 Serge Hallyn wrote: > Quoting Christian Seiler (christ...@iwakd.de): [...] > To implement that, we would rename lxc_container_new() to > lxc_container_new_ln() which takes an extra boolean and dereferences > the symlink if the boolean is true, have lxc_container

Re: [lxc-devel] RFC: aliases

2013-08-21 Thread Serge Hallyn
Quoting Christian Seiler (christ...@iwakd.de): > Hi Serge, > > > I'm thinking symbolic link may be the simplest thing to support - > > lxc_container_new() could immediately readlink() to get the real > > container name. > > Yes, I agree, I'd find such a thing very useful. However, it should not >

Re: [lxc-devel] RFC: aliases

2013-08-21 Thread Claudio Kuenzler
> - When showing names (mostly lxc-ls), always show the >real name by default, never the alias. So if /var/lib/lxc >contains the following contents >foo/ >bar/ >baz -> bar >then lxc-ls should only show foo and bar. An additional >option for also s

Re: [lxc-devel] RFC: aliases

2013-08-21 Thread Christian Seiler
Hi Serge, > I'm thinking symbolic link may be the simplest thing to support - > lxc_container_new() could immediately readlink() to get the real > container name. Yes, I agree, I'd find such a thing very useful. However, it should not only be lxc_container_new but also the utilities not using the

Re: [lxc-devel] RFC: aliases

2013-08-20 Thread Jay Taylor
On Tue, Aug 20, 2013 at 4:07 PM, Serge Hallyn wrote: > Quoting Jay Taylor (j...@jaytaylor.com): > > Hey Serge, > > > > > > On Tue, Aug 20, 2013 at 1:55 PM, Serge Hallyn >wrote: > > > > > Hi, > > > > > > one idea that has been brought up is to support 'aliases'. So if > you're > > > locally build

Re: [lxc-devel] RFC: aliases

2013-08-20 Thread Serge Hallyn
Quoting Jay Taylor (j...@jaytaylor.com): > Hey Serge, > > > On Tue, Aug 20, 2013 at 1:55 PM, Serge Hallyn 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 t

Re: [lxc-devel] RFC: aliases

2013-08-20 Thread Jay Taylor
Hey Serge, On Tue, Aug 20, 2013 at 1:55 PM, Serge Hallyn 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 > late

[lxc-devel] RFC: aliases

2013-08-20 Thread Serge Hallyn
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 te