You are on page 1of 8

Youtravel IBE

Migration to Azure
1. Shared file storage
Mounted directory using common SMB protocol.

REPLACES: Current Lisweb hosted NAS shared disk.

● Setup
● Migrate already uploaded files
● Mount to docker containers
2. Cosmos DB (with Mongo API)
REPLACES: Current Lisweb self managed two MongoDB instances.
1 QA single server
1 Live replica with 3 servers.

● Create 1 Cosmos DB instance for all


● Create Live / QA / Dev databases in this shared instance
● Migrate existing data
● Replica / High availability / Backups ???

More info: https://docs.microsoft.com/en-us/azure/cosmos-db/create-mongodb-dotnet


3. Docker Registry
Setup an azure cloud hosted Docker Registry.

REPLACES: Current Gitlab’s private docker registry.

● Setup
● Fix Gitlab CI script to push docker image builds to azure private registry
4. Docker App Services
REPLACES: 5 Lisweb self-managed VMs (3 live, 2 qa)

● Create and configure Azure Web App Service for IBE to replace current lisweb
self-managed VMs. (1 service with 3 configs or 3 separate services???)
● Containerized IBE (already done, but needs a little more config)
5. Scheduled tasks
REPLACES: 1 Lisweb VM with scheduler IBE app + clearer management + code

● Setup for hotel list, destinations (http request to IBE with secret key)
● Setup for hotel groups hotel details (http request to IBE with secret key)
● Setup for airports ???
● IBE development: Authorize http requests with secret auth key in url
6. Replace Gitlab CI with Azure DevOps ???

REPLACES: Gitlab CI

● Setup build steps in Azure


● Setup Git Push Web hooks
7. IBE DevOps management
● Create Azure Resource Group for all IBE components:
(storage, mongodb, containers, docker registry etc...)
● Create user accounts with permissions to monitor/manage the IBE resource group

You might also like