Re: [Lxc-users] Batch invocation of apt-get?
Milan Zamazal writes: >> "TWB" == Trent W Buck writes: > > TWB> Sounds like you want a change management system, like puppet or > TWB> cfengine. > > I just run about 20 virtual servers / containers, each of them running a > different kind of service, so these tools are apparently not for me. > > TWB> By blowing away and rebuilding containers that aren't in > TWB> production (which I have fully scripted), and by ssh'ing into > TWB> containers that are in production. > > OK, so it seems there is no special tool to do it. In such a case I can > use something similar as you. Another way might be to initiate > automated upgrades from the host, e.g. by putting something into > .../CONTAINER/etc/cron.d/ or so when upgrades should be performed; this > would also make stopped host to perform the upgrade as soon as they are > started. For Ubuntu/Debian, at least, automatic application of security (or all) updates via a daily cron job is an already-solved problem. IIRC you want to look into the "unattended-upgrades" package. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Batch invocation of apt-get?
> "TWB" == Trent W Buck writes: TWB> Sounds like you want a change management system, like puppet or TWB> cfengine. I just run about 20 virtual servers / containers, each of them running a different kind of service, so these tools are apparently not for me. TWB> By blowing away and rebuilding containers that aren't in TWB> production (which I have fully scripted), and by ssh'ing into TWB> containers that are in production. OK, so it seems there is no special tool to do it. In such a case I can use something similar as you. Another way might be to initiate automated upgrades from the host, e.g. by putting something into .../CONTAINER/etc/cron.d/ or so when upgrades should be performed; this would also make stopped host to perform the upgrade as soon as they are started. Thank you for help. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Batch invocation of apt-get?
Milan Zamazal writes: > I migrate from VServer to Linux Containers on Debian 6.0. I can't find > any vapt-get equivalent in order to be able to upgrade all running > containers at once. I wouldn't like to handle each container manually > with lxc-console nor to stop the containers (so that I can use > lxc-execute) nor to run sshd in the containers. Sounds like you want a change management system, like puppet or cfengine. > How do you do it? By blowing away and rebuilding containers that aren't in production (which I have fully scripted), and by ssh'ing into containers that are in production. I only have a couple dozen containers; if I had hundreds I would be using puppet. -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
