Objects 2.x : Understanding Deployment and beyond.

Anirudha | Fri, 06/26/2020 - 02:38

There are lot of improvements and new features introduced in Objects 2.x release. Next few blogs we will focus on exploring all these features.

In this video series we will take a close look at how Deployment workflow is improved in latest release. We will also try to understand some of the pre-requisites and will go over Day1 operations that Administrator would perform.

What you need :

  • Prism Central
  • Prism Element (i.e AHV) cluster
  • Atleast 18 IPs.

 

Lets begin the fun :

Few things to note from Video:

  • Objects is enabled on Demand. It does not take up any resources in Prism Central until then.
  • Just 3 screens and 5 inputs from user, for deploying Objects.
  • Objects manager and MSP controller service, both are containerised .
  • Deployment workflow pull the required base VM image and Objects services from Nutanix Portal. Take a look at Network, URL and Ports requirement.
  • Objects supports Darksite deployment, refer Objects Documentation.
  • Software load balancers are deployed out of the box, making overall connectivity easy for end user.
  • Configure IPAM network , required for deployment.
  • Deployment progress gives details information about deployment stages and corresponding progress.
  • Objects lifecycle management is done via Nutanix LCM service. Which gives flexibility to release Objects independently.

Objects is layers architecture. It uses all the goodness from underlying AOS/AHV cluster which is distributed in nature -> Deploys Nutanix Micro-service platform built on Kubernetes -> Then all the Objects services are deployed (which are containerised). Objects endpoint is exposed via Objects software load balancers.