Clouds & Deployments
Introduction
After you deploy your source code and resources, you can operate and conduct IT Ops as well as check the metric analytics for all deployed services in every environment.
The behavior differs between environments based on the infrastructure you have select for the environment you are working in.
Bare Metal
This infrastructure only supports running service maintenance operations if your services are created using SOAJS Framework.
The interface visualizes the cloud of microservices deployed as well as the cloud awareness among them and provides you with list of maintenance operations that you can run on each service.
If you need to restart the microservices or pull and apply code updates on them, you need to do that yourself.
Now since you will handle deploying, starting and restarting microservices, the wizard provides a Download Profile Button, that downloads a copy of the Profile to use for this environment whenever you are launching a new service so that this service can reach the core database and pull the registry of the environment it will run in.
Container Technology
If the infrastructure uses container technology, in addition to visualizing the cloud of deployed microservices, the interface also displays the metrics of each deployed service, the number of replicated instances and several IT Operations that you can run on these services.
Operation Name | Category | Available in SOAJS For | Description |
|---|---|---|---|
Inspect | SOAJS | Service - Controller - Daemon | Inspect the Catalog Recipe that was used to deploy this service. |
Scale | SOAJS | Service - Controller - Daemon | Scale the service Horizontally by adding or removing instances. |
Auto-scale | SOAJS | Service - Controller - Daemon | Automatically scale the service by adding or removing instances based on the CPU usage percentage. |
Delete | SOAJS | Service - Controller - Daemon | Delete the service and all its instances. |
Logs Monitoring | SOAJS | Service - Controller - Daemon | Monitor the Logs of every instance of a service. |
Restart Service | SOAJS | Service - Controller - Daemon | Restart a service using the same catalog recipe that was use to create it. Mostly used to pull code updates after service was deployed. |
Heartbeat | SOAJS | Service - Controller - Daemon | Checks if the service/daemon is alive |
Reload Registry | SOAJS | Service - Controller - Daemon | Reloads the Registry (Environment) configuration |
Reload Provision | SOAJS | Service - Daemon | Reloads the ACL and custom tenant configuration ( servicesConfig ) |
Awareness Status | SOAJS | Controller | Reloads the Awareness of the Controller |
Load Daemon Status | SOAJS | Daemon | Return information about the Daemon Status |
Reload Daemon Configuration | SOAJS | Daemon | Reload the Daemon's Group Configuration |
Redeploy Service | SOAJS | Service - Controller - Daemon - Nginx | Redeploys a container, read here for more information in case of a catalog recipe update and here in case of an image update. |
Node Management
Container Technology also supports Nodes Management where Nodes refer to the machines that host containers when using container technology.
Click on the Nodes tab and based on the container technology you selected in infrastructure, the interface will provide the supported management operations accordingly.
Node Management - Docker Swarm Technology | Node Management - Kubernetes Technology |
|---|---|
| |
Virtual Machines
Virtual Machines have a dedicated Tab in this interface where you can visualize all layers created for this environment and conduct multiple IT Operations on them.
Each Virtual Machine layer is tagged with the cloud provider it was created on and contains the instances that belong to it.
Every instance in a virtual machine layer represents an actual virtual machine at the provider and you can conduct IT Ops on it such as: start - stop - restart .... etc