Yes it's global. I think a patch introducing 'lxc.cgroup.use' into the container configuration file, where 'lxc.cgroup.use = /lxc/dev1' would mean use that cgroup (not a pattern) might be good.
-serge Quoting Sébastien Kurtzemann ([email protected]): > lxc.cgroup.pattern is a global directive, no ? > > I can't define it per container ? > so it's not possible to set "custo1.dev" container into /custo1 cgroup > and "custo2.dev" into another /custo2 cgroup > > > 2014-03-20 0:42 GMT+01:00 Serge Hallyn <[email protected]>: > > Quoting Sébastien Kurtzemann ([email protected]): > >> Hi all, > >> > >> My idea is to create a "parent" cgroup which defined customer's > >> ressources like cpu, mem, ... > >> For example I've a cgroup called "customer1" on the subsystem "cpuset" > >> on which I pin the first cpu (cpuset.cpus = 1) > >> > >> In this "parent" cgroup I wanted 3 containers which represent customer > >> environments (dev, preprod, prod) > >> Each environements has specific ressources (dev 20% cpu, preprod 20%, prod > >> 60%) > >> > >> Can we attach these new containers to the existing "parent" cgroup ? > > > > You can set > > > > lxc.cgroup.pattern = /customer/dev/%n > > > > which will put the container into /customer/dev/$name > > > > -serge > > _______________________________________________ > > lxc-users mailing list > > [email protected] > > http://lists.linuxcontainers.org/listinfo/lxc-users > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
