Skip to main content

Features

The following is a list of features for Ori Global Cloud (OGC) platform:

  1. User Sign-up: Automated sign-in of new users to the platform and help to familiarize them with its features and capabilities.
  2. Role-based access control : Users can be assigned roles and permissions to manage the access and authorization of different users.
  3. Clusters: Users can easily onboard and integrate Kubernetes clusters into the platform. OGC supports multiple cloud platforms and K8s technologies.
  4. Projects: Users can create and manage projects within the platform, allowing them to organize and manage their applications and services.
  5. Packages: Users can package their applications as self-contained, portable units, making it easy to deploy and orchestrate them across different cloud environments.
  6. Deployments: Users can deploy their packaged applications across different Clusters in multiple cloud environments, including platforms such as AWS, Azure and Google Cloud.
  7. Monitoring and Troubleshooting: Users can monitor and troubleshoot their applications, including viewing logs and performance metrics.
  8. Microservices Architecture: OGC is built on a microservices architecture, which makes it highly scalable and adaptable.

User Sign-up​

The user onboarding process for OGC is designed to be simple and straightforward. The first step is to sign up for an account on the OGC platform. This can be done by visiting the OGC website and filling out a registration form. When the user signs-up up to OGC, for the first time, they will have an Owner (role) within their Organisation, providing them administrative privileges. The user will be given access to the OGC documentation and tutorials, so they can become familiar with the platform's features and functionality. Once the user is familiar with the platform, they can start onboarding clusters and packaging and deploying their applications using OGC's intuitive user interface and powerful orchestration features.

User Access Management​

OGC's user access management feature provides a flexible and secure way to manage access to the platform, ensuring that only authorized users have access to the resources they need to perform their tasks, while maintaining compliance and security requirements. The platform provides granular access controls that can be used to restrict access to specific features based on the role of the user. This feature provides the ability to create users and assigning them different roles with varying levels of access and permissions, such as read-only or full administrative access. You will assign user roles, Owner, Editor or Viewer at the time of user creation. Once a user is created on the platform they will receive an invitation to join. Users are authenticated via their email and password and access can be revoked at any time by the administrator.

Please read our step-by-step Quickstart guide on Organisations to learn more about how to add users to your organisation and the roles to set the right permissions.

Clusters​

A Cluster is your Ori entity that encapsulates all the information that OGC needs about remote compute clusters owned by your organisation. By interacting with the Clusters associated with your organisation, you and your team can perform the required fleet management tasks.

Currently, only Kubernetes (K8s) clusters are supported by OGC, and so most of the Cluster properties and associations map fairly directly to Kubernetes constructs.

If you're looking to onboard your organisation's K8 cluster to the Ori platform, the process is simple and straightforward. With just a few clicks, remote access is enabled and you can begin leveraging the platform's features for fleet management and resource management of your cluster. Ultimately, onboarding your own cluster with Ori makes managing K8s deployments simpler and more efficient than ever before.

Learn how Bring-Your-Own-Cluster works on OGC.

Projects​

A project entity is an essential part of OGC because it enables you to create projects, manage packages and application deployment. The project allows you store resources specific and related to the project, such as packages, application deployment configurations, and user-defined secrets. Its also allows you to configure and access images from registries like Docker Hub and private Registries with ease.

A project allows you to have greater control over your packages and its associated resources.

To create a new Project follow our guide on Projects.

Packages​

A package is a way to deploy applications on the Ori platform. It offers an explicit declaration of all the information required to deploy and manage a modern, cloud-native “application” across multiple clusters. A package encapsulates all the necessary applications, route policies, environment variables, and mounts necessary for a containerized application to run. It enables users to quickly and easily deploy applications without having to think about every single detail related to running an application or service in a containerized environment.

Selectors​

Selectors are key-value pair included in a Workload definition and used by the Orchestrator to determine where a Workload can be deployed during Planning. Selectors are matched to Labels on Nodes to determine whether specific Nodes are suitable for running specific Workloads.

By simplifying the deployment process of applications on the Ori platform, using packages eliminates manual configuration and helps you save considerable time and effort.

View our guide on Packages to understand how packages are created, configured and deployed on OGC.

Deployments​

Deployments on OGC encapsulates all the information about a single deployment of a Package. It involves deploying applications across K8 clusters matching the policies to handle workloads with ease. Deployment is organised into three parts: plans, statuses and workloads. During a deployment it is essential to keep track of all three elements to make sure that packages are correctly configured.

Deployment Planning state is a vital preliminary state before the deployment transitions to other states. During planning, the OGC orchestrator evaluates the capabilities of available clusters against the requirements of a Deployment to produce a Plan.

Deployment Plan​

A deployment plan is a set of information required to instantiate a Deployment into a Cluster. It includes definitions and locations of container instances, supporting services, VPN connections etc. which will need creation and configuration. A Plan is transient, and is discarded when a Deployment is and the Running state.

Workloads​

In OGC, workloads are referred to as running items within a Deployment.

View OGC's quick start guide to learn how Deployments can be managed on OGC.