Odin
  • Introduction
  • Why Odin?
  • Key Concepts
    • Environment
      • Environment Type
    • Provisioning
      • Provisioning Config for Component Types
    • Component
      • Available Component Types
      • Component Type reference
        • Optimus Components
          • Aerospike [6.3.0.7-1.0.0]
    • Service
      • Know Your Service Definition
    • Versioning
      • Clearing the Confusion: A Simplified Guide to Artifact, Component, and Service Versions
    • Service Sets
    • Labels
  • Reference
    • CLI reference
  • Onboard Your Service
    • Installation
    • Configure
    • Odin -h
    • Getting Started
    • Create Environment
      • Operations on Environment
    • Service Definition
    • Provisioning Config
    • Deploy Service
    • Release Service
    • Optimus Datastore Operations
      • How to use Optimus Datastore in my service?
      • RDS Operations
      • Aerospike Operations
      • Kafka Operations
    • Operating Service & Components
      • Redeploy
        • In Place Deployment
        • Blue Green Deployment
      • Rolling Restart
      • Adding & removing components
      • Revert a deployment for application component
      • Downscaling a Passive Stack
      • Updating the no. of stacks of application component
    • Dev <> QA iteration
    • Frequently Asked Questions
    • Deploy Concrete Service
    • Undeploy Service
    • Delete Environment
    • Appendix
  • How To
    • Define error threshold for canary deployment
    • Add or Remove a component in an already deployed service
    • Integrate mono-repo(cronjobs) with Odin
    • Deploy crontab with Odin
    • Integrate Data pipeline with Odin
    • Push logs to log central
    • Build artifacts for multi module applications
    • Load test with Odin
    • Track Deployments against Commit Ids
    • Deploy Service on Production - Dream11
    • How and when images are created
    • Check logs for deployed infrastructure - Dream11
    • Onboard Stepfunction as a component
    • Onboard Serverless as a component
    • Login to Kubernetes clusters
  • Release Notes
    • 1.2.0-beta.2 - 11 August, 2022
    • Odin October Release
    • Odin 1.2.0 - Nov 9th 2022
    • Odin February Release
Powered by GitBook
On this page
Export as PDF
  1. How To

How and when images are created

This document covers when docker images and AMIs are created.

PreviousDeploy Service on Production - Dream11NextCheck logs for deployed infrastructure - Dream11

Last updated 10 months ago

When a service is defined, the primary component for the same is application component. The deployable docker images or AMIs are created for the application component. Images can be created during either of the mentioned processes : During release or during deployment.

Image creation during release

During release of the service, docker images and AMIs both are created for all the application components using the artifact zip files for the respective application components. During release, the deployment type is not checked and both the images are created. Refer to the document 'Release using Odin' to know how to release a service.

Image creation during deployment

During deployment, based on the deployment type specified for the application component in the provisioning file, the image is created. If the deployment type mentioned is 'container', then a docker image will be created and if the deployment type is 'EC2', then AMI will be created.

Refer to the document '' for the sample provisioning file to know how to specify deployment type. To know how to deploy a service, use the document '.

If there is no change in the application code and the user tries to re-deploy the service, no new image will be created. In this case, Odin will use the already created image and deploy the same. Only if there are changes in the application code, the images are re-created. User might choose to change the components only without changing application code, in that case as well no new image will be created.

Provisioning
Deploy using Odin'