Install, initialize, and configure your cloud.
The minimum supported configuration for a cloud includes two cloud partners and one cloud arbiter, with high availability enabled. Cloud partners are cloud servers that are identical and oversee all activity between hosts and servers in the cloud. Each cloud partner and the cloud arbiter must be on separate computers, to ensure that if one computer fails, your cloud continues to run. As well, both cloud partners must be running on the same operating system and have Internet connectivity so that they can send usage data to the Usage Server, and they are expected to be running all the time. They also must have access to your SMTP servers to send alert emails.
Timezone synchronization You install the cloud host software on three computers. Computers running cloud hosts must have UTC times synchronized to within 30 seconds of each other.
Host name restrictions By default, the host name is the computer name. Host names can only contain the following characters: a-z, A-Z, 0-9, minus sign (-), period (.), and underscore (_). A host is named according to the computer that it runs on.
Firewalls must allow TCP/IP connections On each host you add to the cloud, configure the firewall to allow TCP/IP connections to the TCP/IP, HTTP, and HTTPS ports used by each cloud server installed on the host. Similarly, configure any firewalls on or between a host that is used to connect to any cloud server to allow TCP/IP connections to the TCP/IP, HTTP, and HTTPS ports used by the cloud server.
If your firewall blocks incoming connections by application, configure your firewall to allow connections to the dbsrv16 executable. Additionally, if your firewall blocks outgoing connections by application, configure your firewall to allow outgoing connections from all cloud executables.
If firewalls are not configured properly, connections could fail, resulting in your cloud not operating correctly.
Cloud Console requires Adobe Flash The Cloud Console, the main user interface for administering the cloud, requires Adobe Flash. Install Adobe Flash on any cloud host where cloud administration is performed.
Context and remarks
You have designated the three computers that are going to act as cloud partners and cloud arbiter, and are now ready to install the cloud software on the first computer.
You set several passwords during the install process, some of which cannot be changed for the life of the cloud. Consider recording the passwords you specify and storing them in a safe place.
Run the cloud installer as the root user.
Visit http://response.sybase.com/forms/SQLAOnDemandReg to request SAP Sybase SQL Anywhere, on-demand edition 1.0 Support Package 3. You receive an email containing a registration key and a link for downloading the software.
Download the software and run the installer (setup), accepting all defaults. When prompted, specify the key that was provided to you when you registered.
The default cloud installation directory is /opt/saondemand100/.
After the installation is complete, the setup program prompts you to create a cloud. Accept the prompt.
The installer launches the Cloud Initialization utility found in the cloud installation directory. For example: /opt/saondemand100/sa-linux64-x64-126.96.36.19941-188.8.131.5296/bin64s/dbcloudinit).
Do not run this utility after your cloud is up and running unless you intend to remove your existing cloud and create a new one. All existing cloud data (including tenant databases) are deleted; this process is irreversible. Before running this utility, delete all your hosts except your last cloud partner, and stop the cloud.
For the Enter the cloud name prompt, give your cloud a name.
The cloud name must conform to the rules for cloud object names. See Restrictions and notes for identifiers and cloud object names.
For the Enter the two-letter language code for the cloud language prompt, enter the language you want your cloud to use.
Create the cloud administrator by providing a user ID, password, and full name for the cloud administrator.
For the Select how this host will be addressed by the cloud prompt, specify dynamic or static host addressing. If you are unsure what to specify, check with your system administrator to find out how addressing is configured for your network.
For the Enter the user account name the cloud server should run as prompt, specify which Linux user account the cloud will run from.
Do not run the cloud from the root user account in a production system.
For port settings, if you specified a non-root user in the previous step, the default port settings for HTTP and HTTPS are: TCP/IP: 2638, HTTP: 40800, HTTPS: 40400. For the root user, the default port settings are: TCP/IP: 2638, HTTP: 80, and HTTPS: 443.
If an error is returned indicating that a port number is already in use, change the value to an available port.
For the Enter the encryption key prompt, specify an encryption key. The encryption key is restricted to 7-bit ASCII characters to ensure that it can be represented in all cloud host operating systems and character sets. The encryption key is used to encrypt the cloud. By default the cloud uses RSA encryption. To use FIPS encryption, you can accept Do you want to use FIPS-approved encryption? You cannot alter the FIPS encryption option once the cloud is created.
For the Enter the secure feature key prompt, specify a secure feature key to use for the cloud.
The secure feature key is used to enforce tenant database isolation. The secure feature key is restricted to 7-bit ASCII characters and it must have a length between 6 and 128 characters. Secure feature keys cannot:
The secure feature key is used to enforce tenant database isolation.
For the Choose a certificate to be used by the cloud prompt, specify the certificate to use for the cloud. If you do not have a certificate, the cloud creates one for you (RSA encryption with a 2048 bit key).
The cloud uses certificates to secure communication between cloud servers and with the Cloud Console. Unsigned certificates can cause certificate warnings in your browser when you attempt to access the Cloud Console. It is safe to ignore these warnings in a development environment. However, for increased security in your production environment, consider using a signed certificate instead.
You are about to create a host install that is used to install cloud software on the computers you have designated to be the second cloud partner and the cloud
arbiter. You use the Create Host Install web site (
https://host-name:port-number/dbcloud/addhost) to create host installs. The Create Host Install web page creates a file called dbcloudaddhost, which you run on the two computers. dbcloudaddhost is not the host install itself. Instead, it is a file that, when run, pulls the host install software you created down from
the cloud and runs it.
Each host install is specific to an operating system and bitness. The following instructions assume that the computer you designate for the cloud arbiter has the same operating system and bitness as the partners, so you create a single host install that you run on the remaining two computers. If the bitness is not the same, create two host installs (use the Create host install web site twice), specifying the appropriate bitness, accordingly. If the arbiter server is to run on a different operating system, then download the cloud software for that operating system to the cloud.
On the computer where you installed the first cloud partner, in the Cloud Console, click Hosts.
On the Hosts panel, click Create host install. If prompted, accept the certificate and continue.
If you cannot access the Cloud Console, you can navigate to
For Host install type, select Multiple use because you are going to use the install more than once. Once on the computer that will serve as cloud partner, and once on the computer that will serve as the cloud arbiter.
For Valid for (days), specify the number of days the install will remain available before it is removed from where it is stored in the cloud, or accept the default (recommended).
In the Install can be run on, select Restricted and enter the names and/or IP addresses for the computers that will host the second cloud partner and the cloud arbiter (recommended), or accept the default, Unrestricted - can be run on any machine.
For Install version, select the platform/bitness of the host where you are going to run the host install.
For Installation directories, specify the location to install the software and cloud data, or accept the defaults (recommended).
For Server ports, accept the default ports that cloud servers will use (recommended), or specify different ports.
Leave Create and start a cloud server on the host selected.
Click Create and Download to create and download the dbcloudaddhost file. The file is downloaded to the default download location for your browser.
Run the following command:
chmod +x dbcloudaddhost
Copy dbcloudaddhost to the computers that will host the second cloud partner and the cloud arbiter, and run it.
Specify your cloud user name and password when prompted.
dbcloudaddhost performs the following operations:
Downloads the correct cloud software from the cloud to the host you are installing
Installs the cloud host software
Adds the host to the cloud
Creates and starts a cloud server
Cleans up local install files
After you have run dbcloudaddhost on both computers, log in to the Cloud Console from a browser with Adobe Flash installed to confirm that the cloud now has three cloud servers running.
In the Cloud Console, click Overview.
Locate the High Availability section, and click the Configure high availability link provided beneath it.
On the Cloud High Availability window, set the cloud partner and the cloud arbiter by selecting the cloud servers running on the hosts you installed, then click Finish.
High availability is now configured and enabled for your cloud, and cloud setup is complete. You can start adding tenant databases to your cloud.
Discuss this page in DocCommentXchange.
|Copyright © 2013, SAP AG or an SAP affiliate company - SAP Sybase SQL Anywhere, on-demand edition 1.0 Support Package 3|