Hello, You can deploy from current templates, apply updates then shut down and convert the root volume to a template and use that. Not the most elegant. A better way to do it would be to set the templates to update on first boot (can be done via cloud-init or cloudbase-init) or just employ User Data to trigger system updates on a per instance basis.
HTH -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "Yesid Mora" <ym...@o4it.com> > To: users@cloudstack.apache.org > Sent: Friday, 11 December, 2015 15:27:50 > Subject: Update Templates O.S. CloudStack > Hello guys, we need a problem with the update templates because is necessary > register a new template after applying security patches to operating systems, > exist or know other process for update the template that is in the platform? > Or > other mode for update templates (Windows,Linux) > > Thanks > > > > Cordialmente / Best regards, > > > > > > Yesid Mora | Orchestration Engineer | O4IT > > > PBX:+57 (1) 423-5460 Ext 251 | Cel: 3124509565 > > > Cr. 7 #74-56 | Oficina 202 | Bogotá, Colombia > > > www.o4it.com<http://www.o4it.com> | ym...@o4it.com<mailto:ym...@o4it.com> > > > > > > [http://www.o4it.com]<http://www.o4it.com>[http://www.linkedin.com/company/1207504]<http://www.linkedin.com/company/1207504>[https://twitter.com/o4it]<https://twitter.com/o4it>[https://www.facebook.com/o4itofficial]<https://www.facebook.com/o4itofficial>[https://www.youtube.com/user/o4itofficial]<https://www.youtube.com/user/o4itofficial> > > > > > CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for > the sole use of the intended recipient(s) and may contain confidential or > proprietary information. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the intended recipient, immediately > contact the sender by reply e-mail and destroy all copies of the original > message.
