Advice on immutable infrastructure

[Sean O'Reilly]

Hi

I am looking for a little advice or to start a discussion around how other people are managing immutable servers using packer.

I would like to build an AMI once using packer and then promote that same image through dev/test/preprod/prod. I would be interested to hear if anyone else is doing this and what strategies they are using to move the AMI between the environments and how they are marking the images as releasable.

Is there a well known pattern I should be following or some best practice?

Regards

Sean

[Dhinesh Kumar T]

Hi Sean, 

It is possible if all environments are in one subscription and also in same region. 

Thanks, 

Dhinesh 

[Sean O'Reilly]

Why only if in same account and region? We can share AMIs across different accounts. What pattern would you use in same account?

Regards

Sean 

[Rickard von Essen]

We build our images once (with CI) and then promote them with tags and copying them to different regions. We only use Packer for creating the image in the staging env, the promotion is completely handled by python/boto3 scripts since it's lifecycle management.

--
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/5d00c6d5-c89e-4d6b-b6e9-d0b2b3f5d642%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Matthew Hooker]

Hey Sean,

I was just watching this talk on packer at pinterest the other day that I think might be interesting for you https://www.youtube.com/watch?v=L-DMwEN_mUk

On Sat, Apr 14, 2018 at 04:20 Rickard von Essen <rickard....@gmail.com> wrote:

We build our images once (with CI) and then promote them with tags and copying them to different regions. We only use Packer for creating the image in the staging env, the promotion is completely handled by python/boto3 scripts since it's lifecycle management.

On 30 March 2018 at 12:07, 'Sean O'Reilly' via Packer <packe...@googlegroups.com> wrote:

Why only if in same account and region? We can share AMIs across different accounts. What pattern would you use in same account?

Regards

Sean 

On Friday, 30 March 2018 10:25:49 UTC+1, Sean O'Reilly wrote:

Hi

I am looking for a little advice or to start a discussion around how other people are managing immutable servers using packer.

I would like to build an AMI once using packer and then promote that same image through dev/test/preprod/prod. I would be interested to hear if anyone else is doing this and what strategies they are using to move the AMI between the environments and how they are marking the images as releasable.

Is there a well known pattern I should be following or some best practice?

Regards

Sean

--
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.

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/5d00c6d5-c89e-4d6b-b6e9-d0b2b3f5d642%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CALz9Rt_As3xNaJBK1ZY44FSWR0i%2BJrC0gWjqTKXUSiNt5ess1A%40mail.gmail.com.

[Sean O'Reilly]

This is exactly the path I was heading down. Just need to work out the logic of when an AMI gets tagged to move through the environments.

Thanks

On Saturday, 14 April 2018 12:20:12 UTC+1, Rickard von Essen wrote:

We build our images once (with CI) and then promote them with tags and copying them to different regions. We only use Packer for creating the image in the staging env, the promotion is completely handled by python/boto3 scripts since it's lifecycle management.

On 30 March 2018 at 12:07, 'Sean O'Reilly' via Packer <packe...@googlegroups.com> wrote:

Why only if in same account and region? We can share AMIs across different accounts. What pattern would you use in same account?

Regards

Sean 

On Friday, 30 March 2018 10:25:49 UTC+1, Sean O'Reilly wrote:

Hi

I am looking for a little advice or to start a discussion around how other people are managing immutable servers using packer.

I would like to build an AMI once using packer and then promote that same image through dev/test/preprod/prod. I would be interested to hear if anyone else is doing this and what strategies they are using to move the AMI between the environments and how they are marking the images as releasable.

Is there a well known pattern I should be following or some best practice?

Regards

Sean

--
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.

[Sean O'Reilly]

Awesome, thanks. I will watch that now.