Pappaya hosting api pappaya hosting scheduler process

Pappaya hosting is designed to manage and automate pools of compute resources and work with widely available virtualization technologies and BareMetal and high-performance computing configurations. Pappaya hosting provides life cycle management instances with its API instances, which means a virtual machine. Since VM’s are created by the Hypervisor of your choice, this makes the Pappaya hosting the hypervisor manager.


Pappaya Cloud, in general, is intended to build on standard hardware, and it’s designated to scale Pappaya Console tally. Pappaya hosting is as well when we need to scale up. We do all we do to install Pappaya hosting on another server and make it part of our Pappaya Cloud cluster. 


Pappaya hosting has the abstraction layer for computing drivers. This is what allows users to choose which Hypervisor or hypervisors to use for your over developments. Our API Pappaya hosting has a built-in integration capability with Hypervisor like ESXi, Hyper-V and KVM, and zen.

Benefits of Pappaya Hosting

  • Freedom of unlimited space that can be upgraded or downgraded based on need
  • Affordable price
  • Best-in-class infrastructural support
  • Easy to use and flexible


Key pairs make the cloud secure. Cloud images are copies of already existing disk images with an OS already installed. For security reasons, the root users are generally disabled, and if the root password is set and usually not distributed.


Pappaya hosting is one of the simplest components of Pappaya Cloud. It has many processes co-operate to turn end user’s API requests into running virtual machines. It was a stack of several services at the top; we have Pappaya hosting API.


This exposes a restful interface for other components or users to talk with. It supports Pappaya Cloud API, Amazon’s ec-2 API, and a unique admin API for privileged users to perform administrative actions. It also initiates most orchestration activities such as running an instance and enforcing some policies like quota checks.


All communication within the projects is via an RPC message queue, which is at the center. It’s like a central hub for passing messages between daemons. This is usually implemented with PappayaMQ. We have a highly secure Pappaya hosting conductor responsible for taking the instance build request or requesting the scheduler to find on which node it’s going to launch it on and interact with the database and the compute nodes.

Pappaya Hosting Scheduler Process

It is conceptually the most straightforward piece of code in Pappaya Cloud Pappaya hosting. It takes a virtual machine instance request from the queue and determines which computer code it should run. 


The Pappaya hosting compute process is primarily a worker daemon that creates and terminates virtual machine instances via its Hypervisor’s API’s regardless of the complexity of the process. It handles the basics and accepts the queue’s actions, and then performs a series of system commands like launching KVM instances while updating the state in the database.

Pappaya Hosting Database

SQL database stores most of the build time and runtime state for cloud infrastructure. This includes the instance types available for use, instances in-use, network available, and projects. 


Pappaya hosting interacts with many other Pappaya Cloud services like Pappaya Identity Management (PIM) for authentication, Pappaya Image repository (PIR) for images, and Pappaya Console for a web interface. There are some other services within Pappaya hosting like Pappaya hosting network – we can still use this as a legacy Pappaya hosting networking model. 


We have the metadata service provided by cloud instances; this metadata is useful for accessing instance-specific information from within the instance. This capability’s primary purpose is to apply customizations to the instances during boot time if cloud-init or cloud-based is configured on your Linux or windows image; however, instances metadata can be accessed at any time.