Pappaya Console is the framework that provides a web interface for easy management of instances and other Pappaya Cloud configurations. This makes it one of the popular components of Pappaya Cloud as it is an ideal platform for end-users during self-services.
There are three ways to manage Pappaya Cloud:
- Pappaya Console Dashboard
API, which is more towards programmatic access by third-party software like cloud management or orchestration software.
All these methods use API at the backend to fulfill the user’s demands. There is no other way around it. The standard identity services Pappaya Identity Management (PIM) authenticates all services, and individual services interact with each other through public APIs.
Dashboards and Pappaya Console are two words that can be used interchangeably. There is a technical difference among them, though – Pappaya Console is the underlying framework, and the dashboard is the web interface.
Working of Pappaya Console
Pappaya Console gets those instructions from the user to a specific Pappaya Cloud service during the configuration stage via its API. It gives the instructions of that service with the help of the API.
As the dashboard increases the usability and efficiency of most Pappaya Cloud deployments, it’s a rather critical component of the whole project. The Pappaya Console team is committed to supporting all the officially accepted components included in the Pappaya Cloud.
Suppose any service is adequately designed to integrate with Pappaya Console. In that case, it will have the hooks to connect to Pappaya Console and use the dashboard to manage and configure the services.
Since the dashboard uses APIs behind the senses, it can’t do anything that the API can’t do all the actions taken through the dashboard will result in calls to API to complete the task requested by the end-user. Pappaya Console also allows third party products and services such as billing monitoring and additional management tools for a service provider.
It’s not necessary to have Pappaya Console in all the cases. Provide only API access to a specific environment (Pappaya Console) that will not be needed behind the Pappaya Console, which is doing API call to full fill the commands provided by the dashboard.
By default, the normal standard Pappaya Cloud installation uses a non-encrypted HTTP channel, but one needs to enable SSL support for the dashboard.
Different components of a project
Using project groups is a way to add multiple users and add to the project.
It’s a way for the cloud admin to assign operational limits on the resources that can be consumed by the projects where we can put limits on VCPU’s, RAM, and storage.
Finally, create a project.
Once the user logs in with the demo user, they can navigate to the instance and can create/manage the lifecycle of the instances like reboot, pause, delete the logs, and creation of the snapshot.
We can create and delete the volumes; these are the persistent volumes which we can attach to the instances.
Where we can view the instance snapshots we created.
Working with Pappaya Console is easy as it is GUI, but there is no login prompt for Pappaya Cloud CLI operations. We login to the OS initially, but the Pappaya Cloud and the underlying OS are two different entities. The user’s OS credential doesn’t mean anything to Pappaya Cloud. The CLI is the package installed on the OS, and it translates the commands. Pappaya Cloud CLI client can be used in an all-in-one node or, as an alternative, install the CLI on another node and administer Pappaya Cloud from there.