Calm: MySQL Blueprint¶

Creating Blueprint¶

From Prism Central > Apps (Prism Central > Calm if you’re running 5.8.1 or later), select Blueprints from the sidebar and click + Create Application Blueprint.

Specify CalmIntro<INITIALS> in the Blueprint Name field. Enter a Description in the Description field. Select Calm from the Project drop down menu and click Proceed.

Click Proceed to continue.

Click Credentials > and depending on which track you’re on, do one of the two following steps:

Cloud Track:

• Credential Name - CENTOS
• Username - centos
• Secret - Key
• Key - Paste in your private key from the previous lesson

Local Track:

• Credential Name - CENTOS
• Username - root
• Secret - Password
• Password - nutanix/4u

Click Save, and then Back.

Click Save to save your Blueprint.

Setting Variables¶

Variables allow extensibility of Blueprints, meaning a single Blueprint can be used for multiple purposes and environments depending on the configuration of its variables. Variables can either be static values saved as part of the Blueprint or they can be specified at Runtime (when the Blueprint is launched). By default, variables are stored in plaintext and visible in the Configuration Pane. Setting a variable as Secret will mask the value and is ideal for variables such as passwords.

Variables can be used in scripts executed against objects using the @@{variable_name}@@ construct. Calm will expand and replace the variable with the appropriate value before sending to the VM.

In the Configuration Pane under Variable List, fill out the following fields:

Click Save.

Adding a Downloadable Image¶

All VMs in AHV are based off of a disk image. You have the option of selecting an image that’s already managed by Prism Central (Local Track), or specifying a Downloadable Image via a URI (Cloud Track). If the latter is chosen, during the application deployment Prism Central will automatically download and create the image specified. If an image with the same URI already exists on the cluster, it will skip the download and use that instead.

If you’re on the Cloud Track, then follow these steps. If you’re on the Local Track, skip to the next section (Adding DB Service). Near the top, click Configuration > Downloadable Image Configuration and fill out the following fields:

• Package Name - CentOS_7_Cloud
• Description - CentOS 7 Cloud Image
• Image Name - CentOS_7_Cloud
• Image Type - Disk Image
• Architecture - X86_64
• Source URI - http://download.nutanix.com/calm/CentOS-7-x86_64-GenericCloud.qcow2
• Product Name - CentOS
• Product Version - 7

Click Back and then Save.

Adding DB Service¶

In Application Overview > Services, click .

Note Service1 appears in the Workspace and the Configuration Pane reflects the configuration of the selected Service.

Fill out the following fields:

• Service Name - MySQL
• Name - MySQLAHV

• Cloud - Nutanix

• OS - Linux

• VM Name - MYSQL-@@{calm_array_index}@@-@@{calm_time}@@

• Image

  • Cloud Track - CentOS_7_Cloud
  • Local Track - CentOS

• Device Type - Disk

• Device Bus - SCSI

• Select Bootable

• vCPUs - 2

• Cores per vCPU - 1

• Memory (GiB) - 4

• Guest Customization - Depending on your track:

  • Cloud Track - Select Guest Customization

    • Leave Cloud-init selected and paste in the following script

      #cloud-config
      users:
        - name: centos
          ssh-authorized-keys:
            - @@{INSTANCE_PUBLIC_KEY}@@
          sudo: ['ALL=(ALL) NOPASSWD:ALL']
      

  • Local Track - Leave Guest Customization Unselected

• Select under Network Adapters (NICs)

• NIC - Primary

• Credential - CENTOS

Click Save and ensure no errors or warnings pop-up. If they do, resolve the issue, and Save again.

With the MySQL service icon selected in the workspace window, scroll to the top of the Configuration Panel, click Package. Name the Package as MYSQL_PACKAGE, and then click the Configure install button.

On the Blueprint Canvas section, a Package Install field will pop up next to the MySQL Service tile:

Click on the + Task button, and fill out the following fields on the Configuration Panel on the right:

• Name Task - Install_sql
• Type - Execute
• Script Type - Shell
• Credential - CENTOS

Copy and paste the following script into the Script field:

#!/bin/bash
set -ex

sudo yum install -y "http://repo.mysql.com/mysql-community-release-el7.rpm"
sudo yum update -y
sudo setenforce 0
sudo sed -i 's/enforcing/disabled/g' /etc/selinux/config /etc/selinux/config
sudo systemctl stop firewalld || true
sudo systemctl disable firewalld || true
sudo yum install -y mysql-community-server.x86_64

sudo /bin/systemctl start mysqld
sudo /bin/systemctl enable mysqld

#Mysql secure installation
mysql -u root<<-EOF

UPDATE mysql.user SET Password=PASSWORD('@@{Mysql_password}@@') WHERE User='@@{Mysql_user}@@';
DELETE FROM mysql.user WHERE User='@@{Mysql_user}@@' AND Host NOT IN ('localhost', '127.0.0.1', '::1');
DELETE FROM mysql.user WHERE User='';
DELETE FROM mysql.db WHERE Db='test' OR Db='test\_%';

FLUSH PRIVILEGES;
EOF

mysql -u @@{Mysql_user}@@ -p@@{Mysql_password}@@ <<-EOF
CREATE DATABASE @@{Database_name}@@;
GRANT ALL PRIVILEGES ON homestead.* TO '@@{Database_name}@@'@'%' identified by 'secret';

FLUSH PRIVILEGES;
EOF

Select the MySQL service icon in the workspace window again and scroll to the top of the Configuration Panel, click Package.

• Click - Configure Uninstall
• Click - + Task
• Name Task - Uninstall_sql
• Type - Execute
• Script Type - Shell
• Credential - CENTOS

Copy and paste the following script into the Script field:

#!/bin/bash
echo "Goodbye!"

Click Save. You will be prompted with specific errors if there are validation issues such as missing fields or unacceptable characters.

Launching the Blueprint¶

From the toolbar at the top of the Blueprint Editor, click Launch.

In the Name of the Application field, specify a unique name (e.g. CalmMySQL*<INITIALS>*-1).

Click Create.

You will be taken directly to the Applications page to monitor the provisioning of your Blueprint.

Select Audit > Create to view the progress of your application. After MySQLAHV - Check Login is complete, select PackageInstallTask to view the real time output of your installation script.

Note the status changes to Running after the Blueprint has been successfully provisioned.