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
  • What is update stack operation?
  • Command
  • Frequently Asked Questions
Export as PDF
  1. Onboard Your Service
  2. Operating Service & Components

Updating the no. of stacks of application component

Currently, we are only supporting addition of new stacks. We are working on the feature - reduction of no. of stacks.

What is update stack operation?

Currently the process of updating stack is manual and no dynamic way of provisioning the same is available. This documents describes the programmatic way of achieving addition of new stacks.

Command

odin operate component --name YourApplicationComponentName --service YourServiceName --env YourEnvName --operation update-stack --options='{"num_lbs":YourDesiredNumberOfTotalStack,"auto_routing": false}'

Important: When using the num_lbs parameter in the options, remember to input the total number of stacks you want to end up with, not the number of stacks you want to add.

Option
Type
Descrption

operation

String

It takes the input of the operation you want to perform, in this case update-stack.

service

String

Service name for which the operation to be performed.

name

String

Application component name for which the operation to be performed.

env

String

Environment name where the operation is to be performed.

options

Json

  1. num_lbs: This parameter will take the final no. of stacks that you want to achieve. E.g: If you want to add 2 stacks to your currently available 1 stack, hence value of this parameter would be 3. Please note, the value of num_lbs has to be higher than your current no. of stack.

  2. auto_routing: This parameter can take only one of these two values : True and False. Depending on your requirement, please select the value. Please note, if auto_routing is set to false, you have to manually route the traffic to the new stack. However, auto_routing, if set to true, will automatically start routing traffic to your new stack.

Frequently Asked Questions

  1. How do I use auto_routing in option?

    It can take only one of these two values : True and False. Depending on your requirement, please select the value. Please note that if auto_routing is set to false, you have to manually route the traffic to the new stack. However, auto_routing, if set to true, will automatically start routing traffic to your new stack.

  2. Can I reduce the number of stacks by providing the value of num_lbs lower than current no. of stacks?

    No. The value of num_lbs has to be higher than your current no. of stack.

  3. Will I need to configure the newly made stacks as per my application?

    No, the stacks will be configured exactly as your current stack. You do not have to configure anything out of the box.

  4. What do I do if I face any issue or get an error?

    If you are facing an issue with adding a stack, kindly raise an issue in #dss_odin_feedback.

PreviousDownscaling a Passive StackNextDev <> QA iteration

Last updated 1 year ago