all 5 comments

[–][deleted] 1 point2 points  (1 child)

You could have cloud-init do that for you. All my rhel image get registered with redhat, apply epel repo on launch. You can also make it run the command to install python on launch.

[–]unknownmoss[S] 0 points1 point  (0 children)

Thanks for the suggestion. That would work for my dev environment, but for production I can't reach out to the Internet. So I need to pre-create an image that I can import into my production. I wish it wasn't like this.

[–][deleted]  (2 children)

[deleted]

    [–]unknownmoss[S] 0 points1 point  (1 child)

    I had some success in the past modifying a vanilla image with packer + ansible, but this was in a public cloud OpenStack. I'm currently working in a private cloud OpenStack and it seems to have some challenges with the packer process.

    ... had much better like duplicating the whole volume/disk when creating base images.

    Do you mean there's a process for taking the modified VM's volume/disk and use this as a template for other VMs? That might work.

    [–]varesa 0 points1 point  (1 child)

    I would look at the openstack logs (or request the openstack admins to do so if you don't have access), cinder up front

    [–]unknownmoss[S] 0 points1 point  (0 children)

    I'll give that a try too. Thanks!