Migrating Incrementally

How to shift from your existing environment to Facets Managed environments incrementally

Introduction

Whether you are trying Facets Control Plane or migrating from your existing setup to Facets, Lift-and-Shift is never desirable! In this Section, you will learn how to incrementally migrate to Facets managed environments.

582582

Co-existing environments

The diagram above represents a typical set up. You would already have the left side of the set up, i.e., the internal platform of yours would be already powering the environments, say 3 environments in this case, Dev, QA and Production.

:one: Set up Facets Control Plane (If not done already)
:two: As shown in the example, initiate an empty Git repo and commit stack.json, features.json and create 3 empty environments.
*Note that these new environments can be in a complete new cloud accounts as well.
:three: Peer (see below) the new facets managed environments with your existing environments
:four: Pick one of the existing services in your existing cluster and add to the Blueprint and deploy it to facets managed environments. Because of the peering the service can discover the dependent services of your existing environment and vice versa.

Peering

:one: In your Blueprint create a folder path additional_peering/instances . Create a file and name it say existing_cluster.json

{
  "disabled": true,
  "name": "existingcluster",
  "accountId": "na",
  "vcpId": "na",
  "cidr": "na",
  "region":"na"
}

Note, if there aren't any result in the search results, the previous commit might not be read by the Facets Control Plane. In that case navigate to the Blueprint page and click on "Sync With Git" :point-down:

16381638

:two: In your Facets Control Plane, navigate to the desired Facets managed environment. Click on the "Overrides" section on the left navigation and Search for "additional".

35423542

This will open up the json file that we just committed. Provide the existing VPC details of the environment it should be peered with.

:three: In the next release, the peering connection request will have to be approved from the cloud console.

:+1: That's it and now your services can talk to each other bi-directionally.


Did this page help you?