Configuring PPaaS
Follow the instructions below to configure PPaaS:
Some steps are marked as optional as they are not applicable to all IaaS.
Therefore, only execute the instructions that correspond to the IaaS being used!
- Step 1 - Install Prerequisites
- Step 2 - Setup a Kubernetes Cluster (Optional)
- Step 3 - Setup Puppet Master (Optional)
- Step 4 - Create a cartridge base image (Optional)
- Step 5 - Disable the mock IaaS
- Step 6 - Carryout additional IaaS configurations (Optional)
- Step 7 - Configure the Cloud Controller (Optional)
- Step 8 - Define the Message Broker IP (Optional)
Step 1 - Install Prerequisites
Ensure that the following prerequisites have been met based on your environment and IaaS.
Install the prerequisites listed below.
Oracle Java SE Development Kit (JDK)
Apache ActiveMQ
For more information on the prerequisites, see Prerequisites.
Download the Private PaaS binary distribution from the PPaaS product page and unzip it.
Step 2 - Setup a Kubernetes Cluster (Optional)
This step is only mandatory if you are using Kubernetes.
You can setup a Kubernetes cluster using one of the following approaches:
Step 3 - Setup Puppet Master (Optional)
This step is only mandatory if you are deploying PPaaS on a Virtual Machine (e.g., EC2, OpenStack, GCE).
Puppet is an open source configuration management utility. In Private PaaS, Puppet has been used as the orchestration layer. Private PaaS does not have any templates, configurations in puppet, it consists only of the product distributions. Puppet acts as a file server while the Configurator does the configuration in runtime.
Follow the instructions below to setup the Puppet Master.
Step 1 - Configure Puppet Master
Step 2 - Update the cartridge-config.properties
file
Update the values of the following parameters in the cartridge-config.properties
file, which is in the <PRIVATE_PAAS_HOME>/repository/conf
directory.
The values are as follows:
[PUPPET_IP] -
The IP address of the running Puppet instance.[PUPPET_HOST_NAME] -
The host name of the running Puppet instance.
Step 4 - Create a cartridge base image (Optional)
This step is only mandatory if you are deploying PPaaS on a Virtual Machine (e.g., EC2, OpenStack, GCE).
Step 5 - Disable the mock IaaS
Mock IaaS is enabled by default. Therefore, if you are running PPaaS on another IaaS, you need to disable the Mock IaaS.
Follow the instructions below to disable the Mock IaaS:
Navigate to the
<PRIVATE_PAAS_HOME>/repository/conf/mock-iaas.xml
file and disable the Mock IaaS.<mock-iaas enabled="false">
Navigate to the
<PRIVATE_PAAS_HOME>/repository/deployment/server/webapps
directory and delete themock-iaas.war
file.When Private PaaS is run the
mock-iaas.wa
r is extracted and themock-iaas
folder is created. Therefore, if you have run PPaaS previously, delete themock-iaas
folder as well.
Step 6 - Carryout additional IaaS configurations (Optional)
This step is only applicable if you are using GCE.
When working on GCE carryout the following instructions:
Step 7 - Configure the Cloud Controller (Optional)
This step is only mandatory if you are deploying PPaaS on a Virtual Machine (e.g., EC2, OpenStack, GCE).
Step 8 - Define the Message Broker IP (Optional)
This step is only mandatory if you have setup the Message Broker (MB), in this case ActiveMQ, in a separate host.
If you have setup ActiveMQ, which is the PPaaS Message Broker, in a separate host you need to define the Message Broker IP, so that the MB can communicate with PPaaS.