Administering Devices

Describes how to administer your Roving Edge Infrastructure devices.

After each Roving Edge Infrastructure device is configured to work on your network, access and begin administering it.

Accessing the Device Console

  1. Open a supported browser and access the Device Console by entering the IP address you configured for it.

  2. Log into the Device Console using the "root" username and the password you specified when creating your node or cluster order.

    The Device Console user interface appears. The System Health page displays information on your overall Roving Edge Infrastructure environment, including your compute instances, amount of object storage space, and other service-related information. You can also perform typical tasks here, such as creating an instance or setting up a virtual network.

    You can display the System Health page at any time by clicking the "Oracle Roving Edge Infrastructure" link in the banner at the top of the browser.

    See Monitoring System Health for more information.

Adding Users

After accessing the Roving Edge Infrastructure devices from your browser, a typical first step is to add the additional users who will be able to access and use the device.

  1. Open the navigation menu and select Identity Management > Users.

    The Users page appears. All users are listed in tabular form.

  2. Click Create User.

    The Create User dialog box appears.

  3. Enter the following:

    • Name: A unique name or email address for the user. The name must be unique across all users in your tenancy. You cannot change this value later. The name must meet the following requirements: No spaces. Only Basic Latin letters (ASCII), numerals, hyphens, periods, underscores, +, and @.

    • Description: This value could be the user's full name, a nickname, or other descriptive information. You can change this value later.

  4. Click Create.

    The newly created user appears in the User page.

    Next, you must access a secret key from the new user's UI console OAuth 2.0 client credential and forward it to the intended user. This key is the user's login password for accessing the Device Console.

  5. Click the user entry in the User page.

    The User Details page appears.

  6. Click OAuth 2.0 Client Credentials on the left side of the page.

    The OAuth 2.0 Client Credentials page appears.

    By default, only the UI-console-oauth-credential is present in the list of OAuth 2.0 client credentials for a newly created user.

  7. Click UI-console-oauth-credential.

    The UI-console-oauth-credential Details page appears.

  8. Click Regenerate Secret.

    The Regenerate OAuth 2.0 Client Credential dialog box appears, displaying the new password for the user.

  9. Copy the generated secret and store it for your records. You cannot display this secret key after the dialog box is closed.

  10. Click Close to close the dialog box.

  11. Forward the secret key to the intended user.

    This key acts as the initial password for the user. The user can reset their Device Console login password by repeating the steps to regenerate a secret key within their user account.

Note

All users who can access a Roving Edge Infrastructure device have full administration privileges for that device.

See Users for Roving Edge Infrastructure for more information.

Modify a user account with different access configurations such as auth token and API key management. See User Credentials for Roving Edge Infrastructure for more information.

Creating a Virtual Cloud Network

After creating your users, create a virtual cloud network (VCN) within which the users will operate.

  1. Open the navigation menu and select Networking > Virtual Cloud Networks.

    The Virtual Cloud Networks page appears. All virtual cloud networks (VCNs) are listed in tabular form.

  2. (optional) Select a State from the list to limit the VCNs displayed to that state.

  3. Click Create VCN.

    The Create a Virtual Cloud Network dialog box appears.

  4. Enter the following:
    • Name: A descriptive name for the VCN. It doesn't have to be unique, and it cannot be changed later in the Console (but you can change it with the API). Avoid entering confidential information.

    • CIDR Block: A single, contiguous CIDR block for the VCN. For example: 172.16.0.0/16. You cannot change this value later.

    • DNS Resolution: Check Use DNS Hostnames in this VCN if you want to enable this functionality. Checking this option is required for assignment of DNS hostnames to hosts in the VCN. Enabling this option is required if you plan to use the VCN's default DNS feature (called the Internet and VCN Resolver).

      If enabled, you can specify a DNS label for the VCN, otherwise, the Console generates one for you. The dialog box automatically displays the corresponding DNS Domain Name for the VCN (<VCN DNS label>.oraclevcn.com).

  5. Click Create VCN.

See Virtual Cloud Networks (VCNs) for Roving Edge Infrastructure for more information.

Creating a Subnet

After you create your virtual cloud network, create a subnet.

  1. Open the navigation menu and select Networking > Virtual Cloud Networks.

    The Virtual Cloud Networks page appears. All virtual cloud networks (VCNs) are listed in tabular form.

  2. (optional) Select a State from the list to limit the VCNs displayed to that state.

  3. Click the VCN under which you want to create a subnet.

  4. Click Create Subnet.

  5. In the Create Subnet dialog box, specify the resources to associate with the subnet. By default, the subnet is created in the current compartment, and you can choose the resources from the same compartment.

    Enter the following:

    • Name: A friendly name for the subnet. It doesn't have to be unique, and it cannot be changed later in the Console (but you can change it with the API). Avoid entering confidential information.

    • CIDR Block: A single, contiguous CIDR block for the subnet (for example, 172.16.0.0/24). Ensure that the CIDR block is within the cloud network's CIDR block and does not overlap with any other subnets. You cannot change this value later.

    • Use DNS Hostnames in this SUBNET: This option is available only if you provided a DNS label for the VCN during creation. The option is required for assignment of DNS hostnames to hosts in the subnet. Enabling this option is required if you plan to use the VCN's default DNS feature (called the Internet and VCN Resolver).

      If the check box is selected, you can specify a DNS label for the subnet, otherwise the Console generates one for you. The dialog box automatically displays the corresponding DNS Label for the subnet (<subnet_DNS_label>.<VCN_DNS_label>.oraclevcn.com).

    • DHCP Options: The set of DHCP options to associate with the subnet.

  6. Click Create Subnet. The subnet is then created and displayed on the Subnets page in the compartment you chose.

See Subnets for Roving Edge Infrastructure for more information.

Importing an Image

After having set up your network, you can import an image onto your device.

  1. Open the navigation menu and select Compute > Images.

    The Custom Images page appears. All images are listed in tabular form.

  2. (Optional) Select a State from the list to limit the images displayed to that state.

  3. Click Import Image.

    The Import Image dialog box appears.

  4. Enter a Name for the image.

  5. Select the Operating System:

    • For Linux images, select Linux.

    • For Windows images, select Windows. Select the Operating System Version, and then certify that the selected operating system complies with Microsoft licensing agreements.

  6. Select the Bucket that contains the image.

  7. Select the image file from the Object Name list.

  8. Select the Image Type option:

    • QCOW2

    • OCI

  9. Click Import Image.

See Custom Images for Roving Edge Infrastructure for more information.

Viewing Activity Logs

Each Roving Edge Infrastructure device or cluster maintains authentication event and data access logs locally. These logs are stored in the object storage bucket "orei-request-logs" and are retained for 365 days from the time of creation. Logs are generated hourly and compressed as a .gz file in the bucket. Download the log file you want to view and extract it on your local host.
Note

The log entry file objects are read-only. You cannot delete them within the bucket.

  1. Open the navigation menu and select Object Storage > Object Storage.

    The Buckets page appears. All buckets are listed in tabular form.

  2. Click "orei-request-logs."

    The Bucket Details page for orei-request-logs appears.

  3. Find the log file you want to view under Objects. The most recent log appears at the top.
  4. Select the Actions icon (Action icon) associated with the log file object you want to view and click Download.

    The compressed log entry file is downloaded to your local host.

  5. Move the downloaded file to where you want to view it and extract it using an extraction tool. Now you can review the Roving Edge Device's activity logging.

What's Next?

After you have completed the tasks associated with administering Oracle Cloud Infrastructure devices, continue on to Creating and Launching Instances.