Create a Data Infrastructure

This topic describes how to create a Data Infrastructure in Oracle Data Infrastructure Cloud@Customer.

Procedure

Perform the following steps in the Console.

  1. On the Data Infrastructures list page, select Create Data Infrastructure.

    If you need help finding the list page, see List Data Infrastructures.

  2. In the Create Data Infrastructure page, provide the following details.

    • Display name: Enter a name. The display name is a user-friendly name that you can use to identify the Data Infrastructure. The name doesn’t need to be unique, because an Oracle Cloud Identifier (OCID) uniquely identifies the Data Infrastructure.

    • Create in compartment: From the available list, select the compartment in which you want the Data Infrastructure. By default, the current compartment is selected.

    • Region: Displays the region in which you are creating the Data Infrastructure. To use a different region, select it from the Regions menu at the top of the Console.

      Consider the following factors before selecting the region:

      • Consider any business policies or regulations that preclude the use of a particular region. For example, you can be required to maintain all operations within national boundaries.

      • Consider the physical proximity of the region to your data center. Needless extra physical separation adds unnecessary latency to network communications between Oracle Cloud and your data center.

      The region of the Data Infrastructure cannot be changed after the Data Infrastructure is created. Therefore, ensure that you select the most appropriate region.

    • Hardware specification:

      • System model: From the available list, select a system model. The Data Infrastructure system model and storage combine to define the amount of OCPU, memory, and storage resources that are available in the Data Infrastructure. The following system model is currently available:
        • X11-HA 2x: This has the following configuration:
          • Server: 2
          • Total OCPUs: 128
          • Memory: 768 GB per server
          • Total Memory: 1.5 TB

      • High Performance storage: From the available list, select a storage configuration. The following storage configurations are currently available:

        • 6x 7.68 TB SSDs (default)
        • 12x 7.68 TB SSDs
        • 18x 7.68 TB SSDs
        • 24x 7.68 TB SSDs

    • Storage configuration:

      Oracle Data Infrastructure Cloud@Customer uses Oracle Automatic Storage Management (ASM) to manage storage. Configure the data storage allocation, review the automatically calculated recovery area storage, and specify the storage reserved for VM file systems.

      • Data Storage (+DATA): Enter the percentage of block storage to allocate to the Data Infrastructure. You cannot change the +DATA allocation after the Data Infrastructure is activated.
      • Recovery Area Storage (+RECO): Displays the percentage of storage allocated to the recovery area. The +RECO allocation is automatically adjusted based on the selected +DATA allocation. You cannot change the +RECO allocation after the Data Infrastructure is activated.
      • VM Storage: Enter the amount of storage to reserve for VM file systems. This storage is reserved within the +DATA allocation. The minimum value is 512 GB. You can change the VM storage after provisioning, subject to available space in the +DATA allocation.
      • Summary: Displays the selected storage allocations in TB.

    • Site network details:

      • Control plane network:

        The control plane network is a subnet on your data center network that provides connectivity to OCI. Configure the following settings:

        • VLAN ID: Enter a VLAN ID if the network uses VLAN tagging and trunked switch ports. Leave this field empty if the network uses access ports or VLAN tagging is not used.
        • Control Plane Proxy Service (CPS) VM1 IP Address: Enter the IP address of the network interface that connects the first Control Plane Proxy Service (CPS) VM to your data center network.
        • Control Plane Proxy Service (CPS) VM2 IP Address: Enter the IP address of the network interface that connects the second Control Plane Proxy Service (CPS) VM to your data center network.
        • Netmask: From the available list, select the IP netmask for the control plane network.
        • Gateway: Enter the IP address of the control plane network gateway.

        • HTTP Proxy: (Optional) Enter the data center HTTP proxy in the following format, where server is the server name, domain is the domain name, and port is the assigned port.

          http://server.domain:port

          For example:

          http://proxy.example.com:80

          When possible, Oracle recommends configuring an HTTP proxy to enhance security.

      • DNS and NTP services:

        Each Data Infrastructure requires access to Domain Name System (DNS) and Network Time Protocol (NTP) services. Configure the following DNS and NTP server settings:

        • DNS Servers: Enter the IP address of a DNS server that is accessible from the control plane network. You can specify up to three DNS servers.

          To add more DNS servers, select + Another DNS Server.

        • NTP Servers: Enter the IP address of an NTP server that is accessible from the control plane network. You can specify up to three NTP servers.

          To add more NTP servers, select + Another NTP Server.

      • System network:

        The system network is a private network within the Data Infrastructure and is not connected to your data center network. It carries Oracle Automatic Storage Management (ASM) traffic, high-performance interconnect traffic, and internal management traffic.

        • CIDR Block for system network: Enter the IP address range for the system network in CIDR notation.

      • Network bonding mode:

        By default, both the client and backup networks use active-backup bonding (mode 1). You can configure each network to use a different bonding mode. For example, you can configure the client network to use active-backup bonding (mode 1) and the backup network to use LACP (mode 4, IEEE 802.3ad).

        • Enable LACP for Client Network: Turn on to configure the client network to use LACP (mode 4, IEEE 802.3ad). When off, the client network uses active-backup bonding (mode 1).

        • Enable LACP for Backup Network: Turn on to configure the backup network to use LACP (mode 4, IEEE 802.3ad). When off, the backup network uses active-backup bonding (mode 1).

    • Configure maintenance:

      Configure the maintenance method for the Data Infrastructure. Oracle manages maintenance according to the selected method. Oracle notifies the Data Infrastructure maintenance contacts when automatic maintenance is scheduled. You can subscribe to OCI Notifications events to receive maintenance notifications and track maintenance progress.

      • Configure automatic maintenance:

        Configure automatic maintenance according to the Oracle-published maintenance schedule. To specify the maintenance method, select Configure maintenance, and in the Configure maintenance panel, provide the following details.

        • Custom action before performing maintenance on servers: Turn on to perform custom actions before Oracle starts maintenance on the servers. Oracle waits for the configured timeout before starting maintenance on each server.

        • Custom action wait time (in minutes): Enter the number of minutes that Oracle waits before starting maintenance on the servers. The custom action timeout applies only to VM Clusters. You can specify a timeout between 15 and 120 minutes before server patching starts. During this time, you can perform any required custom actions. If you need additional time, you can update the timeout by selecting Edit maintenance window.

          • Default: 30 minutes
          • Minimum: 15 minutes
          • Maximum: 120 minutes

      • Provide maintenance contacts:

        Maintenance contacts are used for service request communications related to hardware replacement and other maintenance events. Ensure that the primary contact is the same contact that was used to register the User Group associated with this Data Infrastructure.

        • Primary contact name: Enter the name of the primary contact.

        • Email: Enter the email address of the primary contact.

        • Phone: Enter the phone number of the primary contact.

        • Provide additional secondary maintenance contacts: Optionally, you can add secondary maintenance contacts. Turn on to enter the name, email address, and phone number for each additional contact.

          To add another secondary contact, select + Another contact. You can add up to 10 maintenance contacts.

    • Advanced Options: Expand to provide additional details.

      • Tags: Expand Tags to add tag details for this resource. You can add free-form tags or defined tags to this resource. You must have permission to use the tag namespace for defined tags. For more information about using tags to manage your resources, see Tags. Tags can be applied later or at any time to a resource.

  3. Select Create Data Infrastructure.

If all required inputs are valid, Data Infrastructure creation starts and the Infrastructure Details page appears. After successful creation, the Data Infrastructure enters the Requires Validation state. The Data Infrastructure details page describes the next step in the provisioning process.