Deploying Private PaaS Locally with Mock IaaS

The Mock IaaS feature in Private PaaS simulates the basic features that it requires from an IaaS. Thereby, providing a cost effective way of trying out Private PaaS. The WSO2 Private PaaS can be installed with the Mock IaaS either on a single Java virtual machine (JVM) or in a distributed setup using multiple JVMs.

• Install Private PaaS with the Mock IaaS in a single JVM setup
• Install Private PaaS with the Mock IaaS in a distributed setup

Install Private PaaS with the Mock IaaS in a single JVM setup

Follow the instructions below to install Private PaaS with the Mock IaaS in a single JVM setup:

1. Ensure that all the following prerequisites have been met based on your environment and IaaS.

   You only need to install Maven, JDK, Git and Apache ActiveMQ when working on a Mock IaaS.

   1. Install the required applications and set the Maven environment variable.

      For more information on the prerequisites, see Prerequisites.

   2. Download the Private PaaS binary distribution (wso2ppaas-x.x.x.zip where x.x.x is the version of the product) and unzip it.

      You can access the binary distribution by using any of the following methods:

      • Method 1 - Download the Private PaaS binary distribution from here and unzip it.

        This method is recommend.

      • Methods 2 - Build the Private PaaS source to obtain the binary distribution and unzip it.

         Click here for instructions

        1. Checkout the source from the Private PaaS remote repository, to a folder of your choice. 

           git clone https://github.com/wso2/product-private-paas.git <LOCAL_FOLDER_PATH> 

           
           For example: 

           git clone https://github.com/wso2/product-private-paas.git /Users/testuser/Documents/myLocalRepo

        2. Navigate to the folder in your computer to which the code base is cloned:
           cd <LOCAL_FOLDER_PATH> 
           
           Example:
           cd /Users/testuser/Documents/myLocalRepo

        3. Clone the respective tag that corresponds to the version of the code base:  
git checkout -b <REMOTE_BRANCH/TAG> <LOCAL_BRANCH>
git checkout -b v4.1.0 v4.1.0


           The local branch name should be identical to the remote branch name.

        4. Build the Private PaaS source using Maven.

           mvn clean install

           If you are building the source for the very first time, the building process will take a considerable amount of time. However, when building from source you can avoid running all the unit tests to make this process faster.

           mvn clean install -Dmaven.test.skip=true 

        5. Obtain the Private PaaS binary distribution from the <PRIVATE_PAAS_SOURCE_HOME>/products/ppaas/modules/distribution/target directory and unzip it.

   3. Start ActiveMQ.

      Follow the steps given below to start ActiveMQ:

      1. Download and unzip ActiveMQ.

      2. Navigate to the <ACTIVEMQ_HOME>/bin directory, which is in the unzipped ActiveMQ distribution.

      3. Run the following command to start ActiveMQ.

         ./activemq start

2. Navigate to the <PRIVATE_PAAS_HOME>/bin directory, which is in the unzipped Private PaaS distribution.

   cd  <PRIVATE_PAAS_HOME>/bin/

3. Start the Private PaaS Server. 

   ./wso2server.sh

Install Private PaaS with the Mock IaaS in a distributed setup

The Mock IaaS is started in a distributed setup only when it is needed to test clustering. When Mock IaaS is started in a distributed setup, Private PaaS Manager (SM), Cloud Controller (CC), Auto-scaler (AS) and the Mock IaaS are started on separate servers.  Follow the instructions below to install Private PaaS with the Mock IaaS in a distributed setup, which utilizes multiple Java virtual machines (JVMs):

1. Ensure that all the following prerequisites have been met based on your environment and IaaS.

   You only need to install Maven, JDK, Git and Apache ActiveMQ when working on a Mock IaaS.

   For more information on the prerequisites, see Prerequisites.

2. Configure and start the Mock IaaS.

   Follow the instructions below to configure and start the Mock IaaS:

   1. Configure the Cloud Controller (CC). 

      Update the Private PaaS host and port of the Mock iaaS API endpoint in the  <PRIVATE_PAAS_HOME>/repository/conf/cloud-controller.xml file, and comment the IaaS provider details that are not being used.

       <iaasProvider type="mock" name="Mock">
         <className>org.apache.stratos.cloud.controller.iaases.mock.MockIaas</className>
         <provider>mock</provider>
         <identity svns:secretAlias="cloud.controller.mock.identity">identity</identity>
         <credential svns:secretAlias="cloud.controller.mock.credential">credential</credential>
         <property name="api.endpoint" value="https://localhost:9443/mock-iaas/api" />
      </iaasProvider>
      </iaasProviders>

      The default Private PaaS host is localhost and the port is 9443. However, when the CC port offset is 1, the Private PaaS port should be changed to 9444. 

   2. Navigate to the  <PRIVATE_PAAS_HOME>/bin directory, which is in the unzipped Private PaaS distribution.

      cd <PRIVATE_PAAS_HOME>/bin/

   3. Start the Private PaaS distribution with the mock-iaas server profile.

      ./wso2server.sh -Dprofile=mock-iaas

3. Install Private PaaS Manager, Cloud Controller and Auto-scaler on separate Java virtual machines. For more information, see Installing Private PaaS in a Distributed Setup Using the Installer.