Same source image for multiple Cloud platforms

46 views
Skip to first unread message

Vince Do

unread,
Apr 11, 2017, 4:01:28 AM4/11/17
to Packer
Hello, 

I'm wondering why, as far as I can see, it isn't possible to use the same source image to build multiple custom ones with different Builders.

I would like to start from an ISO or for example an Ubuntu Cloud Image and get as output an image for VMWare one for Openstack and a VirtualBox image. Does someone have an idea if this is somehow possible using Packer?

Best regards,

Vincenzo

Alvaro Miranda Aguilera

unread,
Apr 11, 2017, 4:10:44 AM4/11/17
to packe...@googlegroups.com
Hello

Packer uses a 100% different approach.

Using the same provisioners (scripts/puppter/ansible, etc) will build boxes/vms on different providers (local/cloud) that after provision will be the same (or very similar)

Alvaro.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/79b8352c-da45-4f23-8cc3-159fff8f09b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

Vince Do

unread,
Apr 11, 2017, 4:28:32 AM4/11/17
to Packer
Thank you for your answer. 


On Tuesday, April 11, 2017 at 10:10:44 AM UTC+2, Alvaro Miranda Aguilera wrote:
Hello

Packer uses a 100% different approach.

Using the same provisioners (scripts/puppter/ansible, etc) will build boxes/vms on different providers (local/cloud) that after provision will be the same (or very similar)

Alvaro.
On Tue, Apr 11, 2017 at 10:01 AM, Vince Do <black...@gmail.com> wrote:
Hello, 

I'm wondering why, as far as I can see, it isn't possible to use the same source image to build multiple custom ones with different Builders.

I would like to start from an ISO or for example an Ubuntu Cloud Image and get as output an image for VMWare one for Openstack and a VirtualBox image. Does someone have an idea if this is somehow possible using Packer?

Best regards,

Vincenzo

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.



--
Alvaro

Boran

unread,
Apr 11, 2017, 6:37:02 AM4/11/17
to Packer
Hi,

I was wondering about this too.
Alvaro: But should the starting point not be the same too, i.e. a base ISO or other image, otherwise it would be difficult to get the exact same versions of programs, and the exact same list of packages installed?

Sean


On Tuesday, 11 April 2017 10:10:44 UTC+2, Alvaro Miranda Aguilera wrote:
Hello

Packer uses a 100% different approach.

Using the same provisioners (scripts/puppter/ansible, etc) will build boxes/vms on different providers (local/cloud) that after provision will be the same (or very similar)

Alvaro.
On Tue, Apr 11, 2017 at 10:01 AM, Vince Do <black...@gmail.com> wrote:
Hello, 

I'm wondering why, as far as I can see, it isn't possible to use the same source image to build multiple custom ones with different Builders.

I would like to start from an ISO or for example an Ubuntu Cloud Image and get as output an image for VMWare one for Openstack and a VirtualBox image. Does someone have an idea if this is somehow possible using Packer?

Best regards,

Vincenzo

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.



--
Alvaro

Rickard von Essen

unread,
Apr 11, 2017, 7:14:08 AM4/11/17
to packe...@googlegroups.com
You can often use a local builder for example qemu to build an image and then post-process it to upload it to a cloud provider, but that is a _very_ advanced use case and if you don't get all the specific details for _that_ cloud right you image will be dead in the water. This is something I don't recommend unless you are very clear on the reason why you need to do that. 

The main reason for doing this is that you are the base image provider and there is no base image for a cloud to use.

// Rickard

To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/1cdf1cc8-86ff-4539-902e-4f35cf267314%40googlegroups.com.

Vince Do

unread,
Apr 11, 2017, 7:32:58 AM4/11/17
to Packer
Hello Rickard

first of all thank you for your reply. 

It may be an advanced scenario but I thought that why packer is there, to simplify the image creation process. Otherwise I would just have used the standard Ubuntu Cloud Image. Like for example, imagine I'm running two hosting platforms one on VMWare and one on Openstack and I know exactly how I need to configure my images for them to work on one or the other platform. So why exactly can't I start from a single source image and get different outputs still puzzles me.

Best regards,

Vincenzo 

Rickard von Essen

unread,
Apr 11, 2017, 8:33:56 AM4/11/17
to packe...@googlegroups.com
I didn't say you cant. On the contrary, I said it's possible. For an example see https://github.com/tmclaugh/suitcase

To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/cafb4cfa-be9c-4af2-89f1-437ab0fff024%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages