To create a database deployment on MySQL Cloud Service, use the Create MySQL Cloud Service wizard as described in the following procedure.
Before You Begin
Before you create a MySQL Server deployment on MySQL Cloud Service, ensure you have created the following:
An SSH public/private key pair
When creating a MySQL Server deployment, you must associate an SSH public key with the compute infrastructure supporting the deployment. You can upload a file containing the public key value or you can paste in the value of a public key.
An SSH public key is used for authentication when you use an SSH client to connect to a compute node associated with the deployment. When you connect, you must provide the private key that matches the public key.
Note:
It is also possible to create an SSH key pair in the Create MySQL Cloud Service Instance wizard.A cloud storage backup location (Optional)
If you want to automatically back up your database to cloud storage, you must associate it with a cloud storage backup location. The type of location you specify depends on the infrastructure the deployment is built on:
Oracle Cloud Infrastructure: cloud backups are stored in an Oracle Cloud Infrastructure Object Storage bucket. You must create a storage bucket before you create database deployments configured to back up to cloud storage.
Oracle Cloud Infrastructure Classic: cloud backups are stored in an Oracle Cloud Infrastructure Object Storage Classic container. You can create the container beforehand and provide the wizard with information about it, or you can have the wizard create the container for you.
Note:
The Cloud Storage Container field of the Create New Instance wizard on Oracle Cloud Infrastructure Classic is now populated with a default, valid URL, and a default container name, MySQLCS. This container is created the first time you create a new instance. To use a different container name, edit the url to remove the default container name, and replace with the desired name.
The container becomes associated with MySQL Cloud Service. Once associated with MySQL Cloud Service, the container becomes part of your subscription (or trial) rather than part of an Oracle IaaS Public Cloud Services subscription (or trial).
Whether you create the container beforehand or have the wizard do it for you, you are prompted for the following information about the container:
The name of the container
The user name and password of a user who has read/write access to the container
Note:
Do not use the Oracle Cloud Infrastructure Object Storage Classic container that you are using to back up MySQL Cloud Service databases for any other purpose. For example, do not also use it to back up Oracle Java Cloud Service instances. Using the container for multiple purposes can result in billing errors.Procedure
To create a MySQL Server deployment on MySQL Cloud Service:
Open the MySQL Cloud Service console.
For detailed instructions, see Accessing MySQL Cloud Service Console.
Click Create Instance.
The Create MySQL Cloud Service wizard starts and the Create New Instance page is displayed. The Create New Instance wizard is divided into Instance, Service Details, and Confirm pages
On the Instance section, specify the following information for your MySQL Server deployment:
Instance Name—enter a name for your MySQL Server deployment. This name:
Must not exceed 50 characters.
Must start with a letter.
Must contain only letters, numbers, or hyphens.
Must not contain any other special characters.
Must be unique within the identity domain.
Description—enter a description for your MySQL Server deployment. (Optional)
Email Address—provide an email address for updates on the provisioning status.
Metering Frequency—determines the type of metering used to determine billing for resources used by this instance. Currently, only Hourly is supported by MySQL Cloud Service.
Region—name of the Compute Region. (Available only if your identity domain is enabled for regions.)
The region for the database deployment. If you choose a region that supports Oracle Cloud Infrastructure, the Availability Domain and Subnet fields are displayed, and the deployment will be created on Oracle Cloud Infrastructure. Otherwise, the deployment will be created on Oracle Cloud Infrastructure Classic.
Choose No Preference to let MySQL Cloud Service choose an Oracle Cloud Infrastructure Classic region for you. The Default Data Region you defined when setting up your account is used.
Availability Domain— (Available only on Oracle Cloud Infrastructure) The availability domain, within the selected region, where your deployment is placed.
Subnet— (Available only on Oracle Cloud Infrastructure) The subnet (within the availability domain) which determine network access to the deployment.
IP Network— (Available only on Oracle Cloud Infrastructure)
(Available only if you selected a region and defined one or more IP networks created in that region using Oracle Cloud Infrastructure Compute Classic.)
Select the IP network where you want the database deployment placed. Choose No Preference to use the default shared network provided by Oracle Cloud Infrastructure Compute Classic.
For more information about IP networks, see these topics in Using Oracle Cloud Infrastructure Compute Classic:
Tags—metadata used to identify instances. Select the required tags from the drop-down list, or create the required tags. Tags can be defined as a comma-separated list of keys, or as a key:value pairs. For example: productionDB,owner:John,admin:John. You can search and filter on tags from the Instances page. You can also define tags after the instance is created, from the Instance Overview page.
For more information, see Managing Tags.
Then, click Next to navigate to the Service Details section.
Note:
An asterisk adjacent to a field name indicates that the field is required.In the Configuration section, select the name, description, and compute shape of your MySQL Server deployment and provide an SSH public key to access the compute infrastructure supporting the deployment.
Shape—select a compute shape from the list of supported OCPU (Oracle CPU) and RAM combinations. For more information, see Computing Power.
Note:
It is possible to scale the shape up or down, depending on your requirements. For more information, see Scaling MySQL Cloud Service.SSH Public Key—provide the SSH public key to be used for authentication when using an SSH client to connect to a compute node that is associated with your MySQL Server deployment.
Click Edit to specify the public key, either by uploading a file containing the public key value or by pasting in the value of a public key.
If you paste in the value, make sure the value does not contain line breaks or end with a line break.
Click Create a New Key and Enter to generate and download a new SSH key pair.
Use High Performance Storage—select to use high-performance storage for the Data, Redo, and Binlog volumes. This is solid state drive storage.
Reserved IPs—select the reserved IP address you want to assign to this service. To assign any of the Reserved IP addresses, select Assign Automatically. For more information on reserved IP addresses, see IP Reservations
This field is displayed only if a Region was selected on the preceding screen, and the IP Network field was set to No Preference.
In the MySQL Configuration section, select the amount of data storage, administrator user, administrator password, database schema name.
Usable Database Storage (GB)—enter the amount of storage you want for database data (in GB). The default is 25, the maximum is 1024.
Note:
If you do not define local backup storage, the maximum available is 2TB.Administration User—enter the administration user name. The default value is root. This value must:
Must be between 2 and 32 characters.
Must start with a letter.
Must contain only letters, numbers, or this symbol: _ (underscore).
Administration Password and Confirm Password—enter and then reenter a password for administrative access to the MySQL Server.
The password you enter:
Must be 8 to 30 characters in length.
Must contain at least one lowercase letter
Must contain at least one uppercase letter
Must contain at least one number
Must contain at least one of these symbols: _ (underscore), # (hash sign), or $ (dollar sign).
Database Schema Name—enter a name for the database instance(s). This name:
Must not exceed 64 characters. Can contain letters, numbers and special characters (_,$).
Must start with a letter, underscore (_), or dollar sign ($).
Must contain only letters, numbers, or these symbols: _ (underscore), # (hash sign), or $ (dollar sign).
Server Character Set—select the required character set from the drop-down menu.
Note:
Although the default character set for MySQL is latin1, MySQL Cloud Service uses utf8mb4 by default.Timezone—select the timezone for the MySQL server. The default value, SYSTEM, sets the timezone to that used by the compute node. SeeSupported Timezones for a complete list.
MySQL Port—define the port on which the server listens. The range of available ports is 3200 to 3399. The default is 3306.
Configure Enterprise Monitor—select Yes to configure a MySQL Enterprise Monitor installation on this instance. Select No to carry on without installing MySQL Enterprise Monitor.
Note:
If you intend to install MySQL Enterprise Monitor, it is strongly recommended that you dedicate a single MySQL Cloud Service instance to this installation. It is also recommended that this MySQL Server deployed on that instance is not used for any other purpose than the MySQL Enterprise Monitor’s repository. A compute node shape of OC3 is the recommended minimum.Note:
If MySQL Enterprise Monitor is provisioned, you must also enable the default access rule, ora_p2admin_em. If this access rule is not enabled, it is not possible to access MySQL Enterprise Monitor.If you select Yes, the following fields are displayed:
Manager User—enter the name of the MySQL Enterprise Monitor’s Manager user. This is the user who configures the installation, adds users, and so on.
Manager Password—enter and confirm a password for the Manager User.
The password you enter:
Must be 8 to 30 characters in length.
Must contain at least one lowercase letter
Must contain at least one uppercase letter
Must contain at least one number
Must contain at least one of these symbols: _ (underscore), # (hash sign), or $ (dollar sign).
Agent User—enter the name of the Agent User. This user is used by the MySQL Enterprise Agents to connect to the MySQL Service Manager and relay the information collected about the host on which the agent is installed and any MySQL instances installed on that host.
Note:
No agent installations are provided at this time. It is currently only possible to install the MySQL Enterprise Service Manager, which can monitor any MySQL instances, local or remote, using a built-in agent.. If you want to monitor MySQL instances installed on other MySQL Cloud Service instances, you can configure the MySQL Service Manager to monitor them, but cannot monitor a remote host’s operating system, file system, or network interfaces. Although agent installations are not currently possible, it is mandatory to define an Agent User and Password to properly configure the MySQL Enterprise Monitor. These parameters can be changed later.Agent Password—enter, and confirm, the agent password.
In the Backup and Recovery Configuration section, choose a backup option for the database deployment and, depending on your choice, provide information about the Oracle Storage Cloud Service container where cloud backups are to be stored.
Note:
It is not possible to change the backup location after the service is created.Backup Destination—select how backups are to be configured:
Both Cloud Storage and Local Storage—backups are configured to be created automatically and stored both on local storage and on an Oracle Storage Cloud Service container.
None—backups are not configured.
Cloud Storage Only—backups are configured to be created automatically and stored in an Oracle Storage Cloud Service container. No local backup is created for this option.
If you select Cloud Storage Only or Both Cloud Storage and Local Storage, the Cloud Storage Container, User Name and Password fields are displayed:
Cloud Storage Container—The URL where backups to cloud storage are to be stored:
For database deployments in Oracle Cloud Infrastructure, enter the URL of an existing Oracle Cloud Infrastructure Object Storage bucket. The URL is of the form:
https://swiftobjectstorage.region.oraclecloud.com/v1/namespace/bucket
For example:
https://swiftobjectstorage.us-phoenix-1.oraclecloud.com/v1/mycompany/mybucket
You must create this storage bucket before you begin creating the database deployment. See Object Storage API in Oracle Cloud Infrastructure documentation.
For database deployments in Oracle Cloud Infrastructure Classic, the field is populated by default with the URL of an Oracle Cloud Infrastructure Object Storage Classic container. The URL is of the general form:
https://storage-instance-specifier/container
Note:
If the account does not include an Object Storage service entitlement or if the region selected is an Oracle Cloud Infrastructure region, the container field is not autopopulated.To use a container other than the default, MySQLCS, replace the default container name with the desired name. The new name can be an existing container, or you can create a new container by adding the new name to the URL, and selecting Create Cloud Storage Container.
Note:
Do not use the storage container that you are using to back up MySQL Cloud Service deployments to cloud storage for any other purpose. For example, do not also use it to back up Oracle Java Cloud Service instances to cloud storage. Using the container for multiple purposes can result in billing errors.
To determine the storage-instance-specifier value for your account, see About REST URLs for Oracle Storage Cloud Service Resources in Using Oracle Cloud Infrastructure Object Storage Classic. If this container doesn’t exist, use the Create Cloud Storage Container checkbox to create it.
Cloud Storage User Name—A user with read/write (and creation, if necessary) access to the location specified in Cloud Storage Container:
For database deployments in Oracle Cloud Infrastructure, enter the user name you use to sign in to the Oracle Cloud Infrastructure console.
For database deployments in Oracle Cloud Infrastructure Classic, enter the Oracle Cloud user name of the administrator of the Oracle Cloud Infrastructure Object Storage Classic container specified in Cloud Storage Container. Usually, this is your Oracle Cloud user name.
For database deployments in Oracle Cloud Infrastructure, enter the Auth Token generated in Oracle Cloud Infrastructure for the user that you specified. For more information, see Prerequisites for Oracle Platform Services on Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation..
For database deployments in Oracle Cloud Infrastructure Classic, enter the password of the Oracle Cloud user specified in Cloud Storage User Name.
Create Cloud Storage Container— (Not available on Oracle Cloud Infrastructure) Create a new Oracle Cloud Infrastructure Object Storage Classic container as part of the database deployment creation. Specify the container name and the Cloud Storage user name and password in the preceding fields. Enabled by default.
To populate, or initialize, the new database with the data stored in an existing backup, in cloud storage, select Yes in the Create Instance from Existing Backup field and do the following:
Note:
This process supports MySQL Enterprise Backup Full or TTS, compressed, single-file backups, with the .mbi extension, or mysqldump’s logical backups, gzipped (*.sql.gz).Backup File Cloud Storage Path—enter the path to the backup file. The following path types are permitted:
For deployments in Oracle Cloud Infrastructure, enter the URL of an existing Oracle Cloud Infrastructure Object Storage bucket. The URL is of the form:
https://swiftobjectstorage.region.oraclecloud.com/v1/namespace/bucket/backupFileName
For example:
https://swiftobjectstorage.us-phoenix-1.oraclecloud.com/v1/mycompany/mybucket
You must create this storage bucket before you begin creating the database deployment. See Object Storage API in Oracle Cloud Infrastructure documentation.
For database deployments in Oracle Cloud Infrastructure Classic, the URL is of the general form:
https://storage-instance-specifier/container/backupFileName
To determine the storage-instance-specifier value for your account, see About REST URLs for Oracle Storage Cloud Service Resources in Using Oracle Cloud Infrastructure Object Storage Classic.
Username—username of the user with read access to the container specified.
Password—password of the user specified in Username.
Note:
You must define adequate storage space in the Usable Database Storage field. If the usable storage is less than the size of the backup used, an error is displayed.On the Confirmation page, review the information listed. If you are satisfied with the information, click Create.
If you need to change the information, use the navigation bar or Back button at the top of the wizard to step back through the pages in the wizard. Click Cancel to cancel out of the wizard without creating a new database deployment.