You have a running Oakestra setup (Root and Cluster Orchestrator).
You can access the APIs at <IP_OF_CLUSTER_ORCHESTRATOR>:10000.
When you start Oakestra using the standard installation scripts (as described in the Create Your First Oakestra Orchestrator section), the dashboard is automatically deployed along with the other Oakestra components.
You don’t need to perform any additional steps to deploy the dashboard.
Upon launching the system for the first time, an administrative user is automatically created.
This user can create and manage other users and organizations within the system. More on User Management later.
Click here to view dashboard default credentials
Username: Admin Password: Admin
After setting up the cluster manager, immediately change the password of the admin user!
To log in to an organization, check the Organization login box and enter the organization name. If the box is not checked or the organization
name is left empty, then you will be logged in to the default root organization.
Here you can see the login to the sampleOrga organization.
In Oakestra, there are applications, services, and namespaces. One application can encompass multiple services, and one user can create
multiple applications on one system. Namespaces allow you to create applications and services with the same name in different namespaces,
e.g., production and development.
First, you will have to create an application. Choose a concise name, the namespace, and optionally a description.
if you used the CLI you are already familiar with the SLAs.
While the dashboard still allows you to upload SLAs as a JSON file, it also provides you with an interactive form.
Once you have created an application you can create services. Once again you will have to choose a concise name, a namespace and optionally a description.
However this is far from it; system requirements, environmental variables, connection details and much more can be specified here.
You will have to choose a virtualization method (Container or Unikernel) and tell Oakestra where it can find your code.
Hit save and your service is ready for deployment!
After you registered your services, you can start a deployment. This operations uses the Root and Cluser schedulers to install the application in one of your worker nodes.
You can eihter click “Deploy All” to deploy all the services in your application. Or you can use the service drop down menu to deploy a single instance of a specific service.
Once a service has been created and deployed, you can check on it’s status and other details. Choose a service from the Service List and from the drop-down
menu, choose an instance and click on View Instance Details.
Something Missing?
If you have any new feature ideas or if you find any bugs please open an issue in the GitHub repository.