-

Note: You are currently viewing documentation for Moodle 3.10. Up-to-date documentation for the latest stable version of Moodle may be available here: Install-on-IBM-Cloud.

Install-on-IBM-Cloud: Difference between revisions

From MoodleDocs
(Created page with "# Get Apache Airflow on IBM Cloud We will deploy Apache Airflow on an IBM Cloud Kubernetes Cluster * Prerequisites : * You should have an IBM Cloud account, otherwise you...")
 
No edit summary
Line 1: Line 1:
# Get Apache Airflow on IBM Cloud
== Get Moodle on IBM Cloud ==


We will deploy Apache Airflow on an IBM Cloud Kubernetes Cluster


* Prerequisites :
=== We will deploy Moodle on an IBM Cloud Kubernetes Cluster ===
  * You should have an IBM Cloud account, otherwise you can [register here].
 
* Prerequisites  
* You should have an IBM Cloud account, otherwise you can [http://cloud.ibm.com/registration|register here].
    
    
1. Provisioning a new Kubernetes Cluster, if already have one skip to step **2**
Provisioning a new Kubernetes Cluster, if already have one skip to step **2**  
2. Deploying the IBM Cloud Block Storage plug-in, if already have it skip to step **3**
Deploying the IBM Cloud Block Storage plug-in, if already have it skip to step **3**  
3. Deploying Apache Airflow
Deploying Moodle


## Step 1 provisioning a new Kubernetes Cluster
=== Step 1 provisioning a new Kubernetes Cluster ===


* Click the **Catalog** button on the top  
* Click the **Catalog** button on the top  
* Select **Service** from the left in the catalog
* Select **Service** from the left in the catalog
* Search for **Kubernetes Service** and click on it
* Search for **Kubernetes Service** and click on it
![Kubernetes](/kubernetes-select.png)
 
[[File:kubernetes-select.png|thumb]]
 
* At the Kubernetes deployment page, we will specify our deployment details
* At the Kubernetes deployment page, we will specify our deployment details
* Choose a plan **standard** or **free**, the free plan only has one worker node and no subnet, to provision a standard cluster, you will need to upgrade you account to Pay-As-You-Go  
* Choose a plan **standard** or **free**, the free plan only has one worker node and no subnet, to provision a standard cluster, you will need to upgrade you account to Pay-As-You-Go  
  * To upgrade to a Pay-As-You-Go account, complete the following steps:
* To upgrade to a Pay-As-You-Go account, complete the following steps
 
 
          *    In the console, go to Manage > Account.
          *    Select Account settings, and click Add credit card.
          *    Enter your payment information, click Next, and submit your information


  * In the console, go to Manage > Account.
  * Select Account settings, and click Add credit card.
  * Enter your payment information, click Next, and submit your information
* Choose **classic** or **VPC**, read the [docs] and choose the most suitable type for yourself  
* Choose **classic** or **VPC**, read the [docs] and choose the most suitable type for yourself  
  ![VPC](/infra-select.png)
  ![VPC](/infra-select.png)
* Please decide on your deployment's location parameters , for more information please visit [Locations]
* Please decide on your deployment's location parameters , for more information please visit [https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zones#zones|Locations]
  * Choose **Geography** (continent)
* Choose **Geography** (continent)
![continent](/location-geo.png)
![continent](/location-geo.png)
  * Choose **Single** or **Multizone**, in single zone your data is only kept in one datacenter, with Multizone your data is kept on multiple sites for more security
* Choose **Single** or **Multizone**, in single zone your data is only kept in one datacenter, with Multizone your data is kept on multiple sites for more security
![avail](/location-avail.png)
![avail](/location-avail.png)
  * Choose a **Worker Zone** if using Single zones or **Metro** if Multizone
* Choose a **Worker Zone** if using Single zones or **Metro** if Multizone
  ![worker](/location-worker.png)  
  ![worker](/location-worker.png)  
    * If you wish to use Multizone please set up your account with [VRF] or [enable Vlan spanning]
* If you wish to use Multizone please set up your account with [https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zones#zones|VRF] or [https://cloud.ibm.com/docs/vlans?topic=vlans-vlan-spanning#vlan-spanning|enable Vlan spanning]
    * At your current location selection, it is possible there is no Virtual LAN  currently available, then a new Vlan will be created for you
* At your current location selection, it is possible there is no Virtual LAN  currently available, then a new Vlan will be created for you
   
   
* Choose a **Worker node setup** or use the preselected one, set **Worker node amount per zone**
* Choose a **Worker node setup** or use the preselected one, set **Worker node amount per zone**
![worker-pool](/worker-pool.png)
![worker-pool](/worker-pool.png)
* Choose **Master Service Endpoint**, In VRF-enabled accounts, you can choose private-only to make your master accessible on the private network or via VPN tunnel. Choose public-only to make your master publicly accessible. When you have a VRF-enabled account, your cluster is set up by default to use both private and public endpoints. For more information visit [endpoints].
* Choose **Master Service Endpoint**, In VRF-enabled accounts, you can choose private-only to make your master accessible on the private network or via VPN tunnel. Choose public-only to make your master publicly accessible. When you have a VRF-enabled account, your cluster is set up by default to use both private and public endpoints. For more information visit [https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview|endpoints].
![endpoints](/endpoints.png)
![endpoints](/endpoints.png)
* Give cluster a **name**
* Give cluster a **name**


![name-new](/name-new.png)
![name-new](/name-new.png)
* Give desired **tags** to your cluster, for more information visit [tags]
* Give desired **tags** to your cluster, for more information visit [https://cloud.ibm.com/docs/account?topic=account-tag|tags]


![tags-new](/tasg-new.png)
![tags-new](/tasg-new.png)
Line 54: Line 59:
![cluster-ready](/cluster-done.png)
![cluster-ready](/cluster-done.png)


## Step 2 deploy IBM Cloud Block Storage plug-in
===  Step 2 deploy IBM Cloud Block Storage plug-in ===
The Block Storage plug-in is a persistent, high-performance iSCSI storage that you can add to your apps by using Kubernetes Persistent Volumes (PVs).
The Block Storage plug-in is a persistent, high-performance iSCSI storage that you can add to your apps by using Kubernetes Persistent Volumes (PVs).
   
   
Line 69: Line 74:
![block-create](/block-storage-create.png)
![block-create](/block-storage-create.png)


## Step 3 Deploy Apache Airflow
=== Step 3 Deploy Moodle ===


In this step we will deploy Apache Airflow on our cluster  
In this step we will deploy Moodle on our cluster  
    
    
* Click the **Catalog** button on the top  
* Click the **Catalog** button on the top  
* Select **Software** from the left in the catalog
* Select **Software** from the left in the catalog
* Search for **Apache Aifrlow** and click on it
* Search for **Moodle** and click on it
![Search](/search.png)
![Search](/search.png)


Line 86: Line 91:


![Name](/details-name.png)
![Name](/details-name.png)
* Select which resource group you want to use, it is for access controll and billing purposes. For more information please visit [resource groups]
* Select which resource group you want to use, it is for access control and billing purposes. For more information please visit [https://cloud.ibm.com/docs/account?topic=account-account_setup#bp_resourcegroups|resource groups]


![apache-resource](/details-resource.png)
![apache-resource](/details-resource.png)


* Here you can give **tags** to your apache airflow workspace, which will affect your deployment. For more information visit [tags]
* Here you can give **tags** to your apache airflow workspace, which will affect your deployment. For more information visit [https://cloud.ibm.com/docs/account?topic=account-tag|tags]


![apache-tags](/details-tags.png)
![apache-tags](/details-tags.png)
Line 106: Line 111:
![airflow-progress](/in-progress.png)
![airflow-progress](/in-progress.png)


* You apache airflow workspace has been successfully deployed
* Your Moodle workspace has been successfully deployed


![airflow-finsihed](/airflow-done.png)
![airflow-finsihed](/airflow-done.png)


## Verify Apache Airflow installation
===  Verify Moodle installation ===


* Go to [Resources] in your browser  
* Go to [Resources] in your browser  
Line 131: Line 136:
* **Type** in the terminal, please change NAMESPACE to the namespace you choose at the deployment setup:
* **Type** in the terminal, please change NAMESPACE to the namespace you choose at the deployment setup:


```sh
 
$ kubectl get ns
  $ kubectl get ns
```
 
![get-ns](/get-ns.png)
![get-ns](/get-ns.png)


  $ kubectl get pod -n NAMESPACE -o wide


```sh
$ kubectl get pod -n NAMESPACE -o wide
```
![get-pod](/get-pod.png)
![get-pod](/get-pod.png)




```sh
 
$ kubectl get service -n NAMESPACE
  $ kubectl get service -n NAMESPACE
```
 
![get-service](/get-service.png)
![get-service](/get-service.png)




* Your running Apache Airflow services will be visible  
* Your running Moodle services will be visible  




You successfully deployed Apache Airflow on IBM Cloud!
You successfully deployed Moodle on IBM Cloud!

Revision as of 16:23, 2 November 2020

Get Moodle on IBM Cloud

We will deploy Moodle on an IBM Cloud Kubernetes Cluster

  • Prerequisites
  • You should have an IBM Cloud account, otherwise you can here.
  1. Provisioning a new Kubernetes Cluster, if already have one skip to step **2**
  2. Deploying the IBM Cloud Block Storage plug-in, if already have it skip to step **3**
  3. Deploying Moodle

Step 1 provisioning a new Kubernetes Cluster

  • Click the **Catalog** button on the top
  • Select **Service** from the left in the catalog
  • Search for **Kubernetes Service** and click on it
  • At the Kubernetes deployment page, we will specify our deployment details
  • Choose a plan **standard** or **free**, the free plan only has one worker node and no subnet, to provision a standard cluster, you will need to upgrade you account to Pay-As-You-Go
  • To upgrade to a Pay-As-You-Go account, complete the following steps


          *    In the console, go to Manage > Account.
          *    Select Account settings, and click Add credit card.
          *    Enter your payment information, click Next, and submit your information
  • Choose **classic** or **VPC**, read the [docs] and choose the most suitable type for yourself
![VPC](/infra-select.png)
  • Please decide on your deployment's location parameters , for more information please visit [1]
  • Choose **Geography** (continent)

![continent](/location-geo.png)

  • Choose **Single** or **Multizone**, in single zone your data is only kept in one datacenter, with Multizone your data is kept on multiple sites for more security

![avail](/location-avail.png)

  • Choose a **Worker Zone** if using Single zones or **Metro** if Multizone
![worker](/location-worker.png) 
  • If you wish to use Multizone please set up your account with [2] or Vlan spanning
  • At your current location selection, it is possible there is no Virtual LAN currently available, then a new Vlan will be created for you
  • Choose a **Worker node setup** or use the preselected one, set **Worker node amount per zone**

![worker-pool](/worker-pool.png)

  • Choose **Master Service Endpoint**, In VRF-enabled accounts, you can choose private-only to make your master accessible on the private network or via VPN tunnel. Choose public-only to make your master publicly accessible. When you have a VRF-enabled account, your cluster is set up by default to use both private and public endpoints. For more information visit [3].

![endpoints](/endpoints.png)

  • Give cluster a **name**

![name-new](/name-new.png)

  • Give desired **tags** to your cluster, for more information visit [4]

![tags-new](/tasg-new.png)

  • Click **create**

![create-new](/create-new.png)

  • Wait for you cluster to be provisioned

![cluster-prepare](/cluster-prepare.png)

  • Your cluster is ready for usage

![cluster-ready](/cluster-done.png)

Step 2 deploy IBM Cloud Block Storage plug-in

The Block Storage plug-in is a persistent, high-performance iSCSI storage that you can add to your apps by using Kubernetes Persistent Volumes (PVs).

  • Click the **Catalog** button on the top
  • Select **Software** from the catalog
  • Search for **IBM Cloud Block Storage plug-in** and click on it

![Block](/block-search.png)

  • On the application page Click in the _dot_ next to the cluster, you wish to use
  • Click on **Enter or Select Namespace** and choose the default Namespace or use a custom one (if you get error please wait 30 minutes for the cluster to finalize)

![block-c](/block-cluster.png)

  • Give a **name** to this workspace
  • Click **install** and wait for the deployment

![block-create](/block-storage-create.png)

Step 3 Deploy Moodle

In this step we will deploy Moodle on our cluster

  • Click the **Catalog** button on the top
  • Select **Software** from the left in the catalog
  • Search for **Moodle** and click on it

![Search](/search.png)


  • On the application page Click in the _dot_ next to the cluster we just created or use an existing one

![Cluster](/cluster-select.png)

  • Click on **Enter or Select Namespace** and choose one of the default Namespaces or use a custom one

![Namespace](/details-namespace.png)

  • Give a unique **name** to your workspace

![Name](/details-name.png)

  • Select which resource group you want to use, it is for access control and billing purposes. For more information please visit groups

![apache-resource](/details-resource.png)

  • Here you can give **tags** to your apache airflow workspace, which will affect your deployment. For more information visit [5]

![apache-tags](/details-tags.png)

  • Click on **Parameters with default values**, You can set deployment values or use the default ones

![def-val](/parameters.png)

  • Please **tick** the box next to the agreements and click **install**

![Install](/aggreement-create.png)

  • Your apache airflow workspace will start installing, please wait a couple of minutes for the deployment to finish

![airflow-progress](/in-progress.png)

  • Your Moodle workspace has been successfully deployed

![airflow-finsihed](/airflow-done.png)

Verify Moodle installation

  • Go to [Resources] in your browser
  • Click on **Clusters**
  • Click on your Cluster

![Resourcelect](/resource-select.png)

  • Now you are at you cluster's overview, here Click on **Actions** on the top right and click on **Web terminal** from the dropdown menu


![Actions](/cluster-main.png)

  • Click **install**, then wait couple of minutes

![terminal-install](/terminal-install.jpg)

  • Click on **Actions**
  • Click **Web terminal** --> a terminal will open up
  • **Type** in the terminal, please change NAMESPACE to the namespace you choose at the deployment setup:


 $ kubectl get ns

![get-ns](/get-ns.png)

 $ kubectl get pod -n NAMESPACE -o wide 

![get-pod](/get-pod.png)


 $ kubectl get service -n NAMESPACE

![get-service](/get-service.png)


  • Your running Moodle services will be visible


You successfully deployed Moodle on IBM Cloud!