On Fri, Dec 4, 2015 at 8:59 AM, Michal Skrivanek < michal.skrivanek@redhat.com> wrote:
On 02 Dec 2015, at 08:43, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Wed, Dec 2, 2015 at 8:18 AM, Shahar Havivi <shaharh@redhat.com> wrote:
On 01.12.15 17:26, Gianluca Cecchi wrote:
OK, I'm trying using classic network instead of NetworkManager. But right before running the "make template" action, do I have to run
any
of "sys-unconfig" and/or "virt-sysprep" tools? No you don't need to run this tools.
OK. Understood.
you don’t have to, but you’ll get a better, cleaner, template if you’ve been using the original image before (added accounts, installed stuff…things people usually do when preparing a template:) we’re looking into integrating it into UI, as it is quite easy to omit a thing or two when sealing it manually
It may make sense to use it for initialization during deployment as well as a replacement of cloud-init not requiring you to initialize it by running it. You would have to do it yourself, making sure the image is not in use while the operation is ongoing. I think it would also be nice to completely integrate it into “create VM from Template” flow. You would have a ready-to-go VMs customized at the time of creation already, instead of relying on runtime cloud-init
Thanks, michal
Any improvement inside the gui is welcome. Yes, in my template I already created personal users that are then able to authenticate themself with public key in the deployed VM without any problem and I have also Oracle client installed with a specific HammerDB configuration file. So the path is the one you suggested. Thanks, Gianluca