How to build enterprise OS Images with Packer? Part-1

Architecture Decisions based on

http://thomasbartsch.net/sharepoint-2010-architecture-best-practices-puruneps-blog
  1. Does your given software support static configurations?
    Example: Apache Kafka requires a Unique ID per instance of Apache Kafka so we can’t use static configurations because each Apache Kafka will have the same ID and Apache Kafka may not work.
  2. Would you like to configure your system on the fly aka provisioning?
    Example: Since Apache Kafka requires a Unique ID, we can generate this on the fly to not generate an infinite number of OS Images ranging from 1..N using Cloud-Init aka User-Data.
  1. Who will be your end customer of OS Images? is it a Team/Organization/Company/etc?
  2. What are SLAs for your end customer?
  1. What cloud provider would you like to use? AWS/Azure/GCP/etc.
  2. How many programming languages do you know and willing to learn? Bash/YAML*/HCL**/Groovy/Go/Python/etc.
  3. What will be your CI and CD System?
  4. How many security testing tools do you know? Nexpose/AWS Inspector/etc.
  5. What Release Mechanism / Cycle will you follow?
  1. When would you like to deprecate/End the given OS Image?
  2. What will be your EOL contract with your customer?

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store