Table of Contents Previous Next


3 Installing the EDB Ark Console : 3.2 Installing EDB Ark for OpenStack

2.
Navigate to the Admin menu, and then select the Images menu selection.
3.
Click the + Create Image button to open the Create An Image dialog (shown in Figure 3.39).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\04a00845\Screen Shot 2017-05-22 at 7.58.08 AM.png
Figure 3.39 – The Create Image dialog.
Use fields on the Create Image dialog to define the EDB Ark image:
Use the Image Name field to provide a name for the image.
Use the Image Description field to provide a description of the image.
Use the Image Source selector to specify that the source will be an Image File.
Use the Location field to specify the location from which the image will be loaded.
Use the Format drop-down listbox to select QCOW2 - QEMU Emulator.
Enter x86_64 in the Architecture field.
Enter 16 in the Minimum Disk (GB) field.
Enter 4096 in the Minimum RAM (MB) field.
Use the Visibility selector to specify if the image is Public or Private.
Set the Protected field to Yes to indicate that the image may only be deleted by a user with permissions can delete the image.
After completing the dialog, click the Create Image button to create the EDB Ark image. Please note that the process of creating an image may take a while depending on your network conditions. While the image is being created you should not exit the OpenStack dashboard or close your browser tab as it will stop the file transfer.
glance \
--os-username
administrative_user \
--os-password
password \
--os-tenant-name
tenant_name \
--os-auth-url http://
identity_service_name:35357/v2.1
image-create \
--name '
image_name' \
--disk-format qcow2 \
--container-format bare \
--is-public True \
--is-protected True \
--min-disk 16 \
--min-ram 4096 \
--property 'description=
image_details' \
--progress \
--property os_type=linux
/
path_to_image_file
administrative_user is the name of an OpenStack administrative user with sufficient privileges to import the image.
password is the password associated with the administrative user account.
tenant_name is the name of a tenant that the --os-username belongs to; it will be used as part of the OpenStack authentication process.
identity_service_name is the URL of the node hosting the OpenStack keystone authentication service. When importing an image, you should specify port 35357 to ensure that the required operations are available.
image_name is a descriptive name of the EDB Ark image.
image_details is a user-friendly description of the EDB Ark image that you are importing. For example, you might want to specify that you are importing: EDB Ark 2.1 Console on CentOS 6.6 x86_64 Default user: centos
path_to_image_file specifies the location and file name of the EDB Ark image file.
3.
Expand the Project menu, and the Network menu; then, select Security Groups.
4.
Click the + Create Security Group button to open the Create Security Group dialog (shown in Figure 3.40).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\da4c2814\Screen Shot 2017-05-22 at 9.38.29 AM.png
Figure 3.40 – The Create Security Group dialog.
Use the Name field to provide a name for the security group.
Use the Description field to provide a description of the security group.
Click the Create Security Group button to create the security group and continue.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\14b038f9\Screen Shot 2017-05-22 at 9.41.03 AM.png
Figure 3.41 – The new group, displayed in the Security Groups list.
To add rules to the new security group, click the Manage Rules button that is located to the right of the security group name (see Figure 3.41). When the list of security group rules opens (see Figure 3.42), click the + Add Rule button to access a dialog that allows you to add a new rule.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\4bc492c2\Screen Shot 2017-05-22 at 9.42.33 AM.png
Figure 3.42 – The new security group.
To access a list of instances, open the Project menu, then the Compute menu and select Instances. To create a new instance, click the Launch Instance button to open the Launch Instance dialog (shown in Figure 3.43).
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\043b09a8\Screen Shot 2017-05-22 at 9.54.58 AM.png
Figure 3.43 – The Launch Instance dialog.
Use fields on the Launch Instance dialog to describe the EDB Ark instance; on the Details tab:
Use the Instance Name field to provide a name for the instance.
Use the Availability Zone drop-down listbox to specify an availability zone.
Set the Instance Count field to 1.
On the Source tab:
Use the drop-down listbox in the Select Boot Source field to select Image.
Set the Create New Volume selector to No.
Click the up arrow to the right of an instance name to add the image name to the Allocated field; this selects the image as the backing image for the instance.
On the Flavor tab:
On the Network tab:
On the Security Groups tab:
Click the up arrow to the right of a security group name to move the description to the Allocated field; this selects the security group that will be applied to the instance.
On the Key Pair tab:
Click the Create Key Pair button to open a dialog that allows you to create a new keypair or click the Import Key Pair button to open a dialog that allows you to select an existing key pair.
Click the up arrow to the right of a Key Pair name to select the keypair you will use to access the instance.
On the Configuration tab:
Use the Customization Script field to provide a script that sets a password for the console setup dialog:
#!/bin/sh
rm -f /var/ppcd/startup-password.txt
echo "
console_password" > /var/ppcd/startup-password.txt
chown ppcd:ppcd /var/ppcd/startup-password.txt
chmod 600 /var/ppcd/startup-password.txt
Where console_password specifies the password that allows access to the setup dialog.
When the first user connects to the AWS Ark console, they will be required to provide the console_password provided in the script; entering the password will invoke the setup dialog.
console_password is stored in /var/ppcd/startup-password.txt.
Click the Launch Instance button to launch the console instance. When OpenStack finishes creating the instance, it will be displayed in the list on the Instances window.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\15b933e2\Screen Shot 2017-05-22 at 12.58.13 PM.png
Figure 3.44– The Instances dialog.
To assign a floating IP address to the new instance, select Associate Floating IP from the drop-down listbox in the Actions column. When the Manage Floating IP Associations dialog opens (see Figure 3.45), use the IP Address drop-down listbox to select an IP address, or click the + button to allocate a new IP address.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\73b4da5f\Screen Shot 2016-01-06 at 3.00.08 PM.png
Figure 3.45– The Manage Floating IP Associations dialog.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\cbf5425e\Screen Shot 2017-05-05 at 12.10.27 PM.png
When prompted, provide the password specified when launching the console in the Password field and click Deploy Console. The Ark console setup dialog opens as shown in Figure 3.47.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\c16d5523\Screen Shot 2017-05-05 at 12.12.33 PM.png
Use the OpenStack Region field to specify the region in which the OpenStack host resides.
Use the OpenStack Admin Role field to specify the name of the OpenStack administrative role. When a user that is a member of this role connects to the console, the console will display the Ark administrative console (which includes the Admin and DBA tabs).
Use the Identity Service Endpoint field to specify the URL of the OpenStack Keystone Identity Service.
Use the Identity Service Admin Endpoint field to specify the URL of the OpenStack Keystone Administrative Service.
Use the Service Account ID field to specify the name of the OpenStack user account that Ark will use when managing clusters. The account must be a member of and be assigned the admin role for all tenants that are allowed to run Ark clusters.
Use the Service Account Password field to specify the password associated with the OpenStack service account.
The fields in the General properties section set values that control Ark behaviors:
Use the Contact Email Address field to specify the address that will be included in the body of cluster status notification emails.
Use the Email From Address field to specify the return email address specified on cluster status notification emails.
Use the Notification Email field to specify the email address to which email notifications about the status of the Ark console will be sent.
Use the API Timeout field to specify the number of minutes that an authorization token will be valid for use within the API.
Use the WAL Archive Container field to specify the name of the storage container where WAL archives (used for point-in-time recovery) are stored. You must provide a value for this property; once set, this property must not be modified.
Use the Dashboard Docs URL field to specify the location of the content that will be displayed on the Dashboard tab of the Ark console. If your cluster resides on a network with Internet access, set the parameter to DEFAULT to display content (documentation) from EnterpriseDB; to display alternate content, provide the URL of the content. To display no content in the lower half of the Dashboard tab, leave the field blank.
Use the Dashboard Hot Topics URL field to specify the location of the content that will be displayed on the Dashboard tab of the Ark console. If your cluster resides on a network with Internet access, set the parameter to DEFAULT to display content (alerts) from EnterpriseDB; to display alternate content, provide the URL of the content. To display no content across the middle section of the Dashboard tab, leave the field blank.
Use the Storage Bucket field to specify the name of the container that will be used to store files for point-in-time recovery. This location should not change after the initial deployment of the Ark console.
Use the Console Backup Folder field to specify a folder in which the backups will be stored.
Use the Storage Tenant field to provide the name of the tenant in which the backup will be stored.
Use the drop-down listbox in the Timezone field to select the timezone that will be displayed by the Ark console.
To allow access to an OpenStack project, connect to the OpenStack console as an Administrative user and expand the Identity menu; then click the Projects. To modify the access privileges for a project, use the drop-down listbox in the Actions column to the right of the project name to select Modify Groups.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\cb571338\Screen Shot 2017-05-22 at 2.23.04 PM.png
When the Edit Project dialog opens, navigate to the Project Members tab (see Figure 3.48).
When you're finished adding users to a project, click Save to save your changes and exit the dialog.
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\485f96aa\Screen Shot 2017-05-22 at 2.30.03 PM.png
Complete the Create User dialog, providing information for the new user:
Re-enter the password in the Confirm Password field.
Use the drop-down listbox in the Primary Project field to select the project that will be displayed when the user connects. Please note that the Ark service account must have administrative privileges in the selected project.
Use the drop-down listbox in the Role field to specify if the new role is a user or an admin user. Please note that user roles will have sufficient privileges to access the Ark console.
When you've completed the dialog, click the Create User button to create the user and exit the dialog. If the user account is enabled, the new user should now be able to access the Ark console
C:\Users\susan\AppData\Local\Temp\vmware-susan\VMwareDnD\495a8020\Screen Shot 2016-09-12 at 11.43.45 AM.png
Figure 3.50 - The Login dialog.
Enter the name of an administrative user in the User Name field, and the associated password in the Password field, and click Login to connect to the Ark console. If the user name and password provided are members of an OpenStack administrative role, the Ark console will include the DBA tab and the Admin tab (as shown in Figure 3.51).
C:\Users\susan\Desktop\osdashboard.png
Figure 3.51 - The EDB Ark Administrator’s console.
Update the User tab, providing a Notification Email. For more information about the User tab, see the EDB Ark Getting Started Guide.
Use the Admin tab to create the server images and database engines that will be used by non-administrative users. For more information about using the Admin tab, see Section 4.1.

3 Installing the EDB Ark Console : 3.2 Installing EDB Ark for OpenStack

Table of Contents Previous Next