Rover User Guide

Roving Edge Infrastructure
Developer and User Guide

January 08, 2021
Copyright
Copyright © 2016, 2020, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and
disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement
or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute,
exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find
any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf
of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any
programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial
computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental
regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any
operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be
subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
Government.
This software or hardware is developed for general use in a variety of information management applications. It is
not developed or intended for use in any inherently dangerous applications, including applications that may create a
risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible
to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation
and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous
applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their
respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used
under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD
logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a
registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and
services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an
applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any
loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set
forth in an applicable agreement between you and Oracle.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For
information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/
lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Cloud Infrastructure Roving Edge Infrastructure Developer and User Guide iii
Table of contents
Contents
Chapter 1 Introduction.............................................................................................8
Overview of Oracle Roving Edge Infrastructure................................................................................................. 8
Key Features......................................................................................................................................................... 8
Prerequisites.......................................................................................................................................................... 9
Differences from Oracle Cloud Infrastructure..................................................................................................... 9
Roving Edge Infrastructure Concepts................................................................................................................ 10
Supported Regions.............................................................................................................................................. 11
Service Limits..................................................................................................................................................... 12
Device Specifications..........................................................................................................................................12
Accessing Roving Edge Infrastructure...............................................................................................................12
Oracle Cloud Infrastructure Console......................................................................................................12
Roving Edge Device Console................................................................................................................ 12
Command Line Interface........................................................................................................................ 12
API...........................................................................................................................................................14
Chapter 2 Getting Started......................................................................................16

Setting Policies................................................................................................................................................... 16
Requesting Devices.............................................................................................................................................17
Creating a Node Resource......................................................................................................................17
Creating a Cluster Resource...................................................................................................................19
Determining Device Storage Capacity................................................................................................... 21
Viewing Your Request Status................................................................................................................ 21
How Oracle Provisions Your Request................................................................................................... 21
Setting Up Devices............................................................................................................................................. 21
Receiving and Inspecting Devices......................................................................................................... 21
Setting Up Terminal Emulation............................................................................................................. 22
Connecting Devices to Your Network................................................................................................... 22
Unlocking Devices..................................................................................................................................22
Configuring Devices............................................................................................................................... 23
Administering Devices........................................................................................................................................23
Accessing the RED Console.................................................................................................................. 23
Adding Users.......................................................................................................................................... 23
Creating a Virtual Cloud Network......................................................................................................... 24
Creating a Subnet................................................................................................................................... 25
Importing an Image................................................................................................................................ 25
Viewing Activity Logs........................................................................................................................... 26
Creating and Launching Instances..................................................................................................................... 26
Creating a Block Volume.......................................................................................................................27
Attaching the Block Volume..................................................................................................................28
Managing Files Using Object Storage............................................................................................................... 28
Creating a Bucket................................................................................................................................... 28
Upload Objects to Your Bucket.............................................................................................................29
Viewing Object Details.......................................................................................................................... 29
Downloading Objects from Your Bucket.............................................................................................. 29
Deleting Objects......................................................................................................................................30
Deleting Buckets.....................................................................................................................................30
Syncing Your Data............................................................................................................................................. 30
iv
Table of contents
Chapter 3 Ordering and Management................................................................. 32

Node Management.............................................................................................................................................. 32
Creating Nodes........................................................................................................................................32
Listing Nodes.......................................................................................................................................... 37
Getting Node Details.............................................................................................................................. 37
Editing Nodes......................................................................................................................................... 38
Deleting Nodes........................................................................................................................................38
Moving Nodes Between Compartments.................................................................................................39
Cluster Management........................................................................................................................................... 40
Creating Clusters.....................................................................................................................................40
Submitting Cluster Requests.................................................................................................................. 43
Listing Clusters....................................................................................................................................... 43
Getting Cluster Details........................................................................................................................... 44
Editing Clusters.......................................................................................................................................44
Deleting Clusters.....................................................................................................................................45
Moving Clusters Between Compartments..............................................................................................46
Device Monitoring.............................................................................................................................................. 46
Monitoring System Health......................................................................................................................46
Monitoring Roving Edge Devices..........................................................................................................47
Device Software Version Management..............................................................................................................47
To update the RED software..................................................................................................................47
To roll back the RED software.............................................................................................................. 47
Chapter 4 On-Device Services............................................................................... 50

Identity and Access Management...................................................................................................................... 50
User Management................................................................................................................................... 50
User Credential Management................................................................................................................. 54
Compute Virtual Machine Infrastructure........................................................................................................... 64
Instance Management............................................................................................................................. 64
Image Management.................................................................................................................................75
Boot Volume Management.....................................................................................................................82
Console History Capture Management.................................................................................................. 87
Object Storage.....................................................................................................................................................89
Bucket Management............................................................................................................................... 89
Object Management................................................................................................................................ 91
Block Volume Management...............................................................................................................................96
Creating Block Volumes........................................................................................................................ 96
Listing Block Volumes...........................................................................................................................97
Getting Block Volume Details............................................................................................................... 97
Renaming Block Volumes......................................................................................................................98
Deleting Block Volumes........................................................................................................................ 98
Block Volume Attachment Management............................................................................................... 99
Networking........................................................................................................................................................102
Virtual Cloud Network (VCN) Management.......................................................................................102
Subnet Management..............................................................................................................................105
Virtual Network Interface Card (VNIC) Management........................................................................ 108
Data Sync Task Management...........................................................................................................................114
Creating Data Sync Tasks.................................................................................................................... 115
Listing Data Sync Tasks.......................................................................................................................115
Getting Data Sync Task Details...........................................................................................................116
Editing Data Sync Tasks...................................................................................................................... 116
Deleting Data Sync Tasks.................................................................................................................... 116
Starting Data Sync Tasks..................................................................................................................... 116
v
Table of contents
Stopping Data Sync Tasks................................................................................................................... 117

Glossary........................................................................................................................................ 118
Release Notes............................................................................................................................... 130
vi
Table of contents
vii
Introduction
Chapter
1
Introduction
This chapter introduces you to Rover and describes it features and functionality.
Overview of Oracle Roving Edge Infrastructure

Oracle Roving Edge Infrastructure is a cloud-integrated service that puts fundamental Oracle Cloud Infrastructure
services where data is generated and consumed regardless of network connectivity. The key component is the Roving
Edge Device (RED) - a portable high-powered server that has been ruggedized to operate in remote and austere
environments. You can order single REDs, or 5-15 REDs clustered together by way of a switch for greater capacity
and durability.
Roving Edge Infrastructure is the extension of your Oracle Cloud Infrastructure tenancy. You request to have virtual
machines and objects from your tenancy loaded onto a RED by creating and configuring a Node or Cluster resource
in Oracle Cloud Infrastructure.
The REDs arrive preconfigured and ready for use. Just power the devices up, configure the network settings, and
connect to your local network. With Roving Edge Infrastructure, you can also synchronize object storage data
between your REDs and Oracle Cloud Infrastructure tenancy.
Common uses for Roving Edge Infrastructure include:
• Storage and processing of large volumes of images, video, audio, and internet of things (IoT) sensor data
generated in environments where WAN connection is latent or unavailable. You can pre-process, filter, compress,
and secure the data locally, then transfer it to Oracle Cloud Infrastructure where it can be further processed in the
cloud.
• Compute and IO intensive applications, where low latency is paramount, such as tactical reconnaissance or 5G
communications.
• Machine learning, where models trained in the cloud are running in disconnected locations to improve efficiency,
intelligence and productivity.
• Remote computing requiring elevated security and airtight containment of data.
• Low-latency Oracle Database and Analytics workloads, with more Oracle applications optimized over time.
• Data collection and migration of large sets of object and DBMS data into Oracle Cloud, at faster speeds and lower
cost than a WAN transfer.
Key Features
Key features of Roving Edge Infrastructure include:
• Each RED is contained in a military grade ruggedized case for remote and austere environments.
• High-performance computing and storage capabilities that operate with intermittent or no internet connectivity.
• REDs are highly portable and can be set up and taken down as needed.
• You can set up 5-15 REDs as a cluster to increase your compute or storage capacity as needed.
• You can synchronize your object storage datasets with your Oracle Cloud Infrastructure tenancy after the edge
node is reconnected to your home OCI region.
Oracle Cloud Infrastructure Roving Edge Infrastructure Developer and User Guide 8
Introduction
• The RED, either as a single device or clustered together, provides the storage and compute power to run virtual
machines where you can perform analytics, machine learning, and location-based services.
Prerequisites
This section describes prerequisites for requesting and using the Roving Edge Infrastructure service and its associated
Roving Edge Devices.
Knowledge Requirements
Using the Roving Edge Infrastructure service and Roving Edge Devices (REDs) has the following knowledge
requirements:
• Experience and understanding of Oracle Cloud Infrastructure services and features. Be comfortable creating
and managing service resources such as compute instances, object storage buckets, and Identity and Access
Management (IAM) tasks before ordering REDs.
• Expertise in hardware device integration, including cabling and switching. If you are integrating a cluster of
REDs, you need a Layer 2 switch and an administrator who understands how to set up a Layer 2 network for the
cluster.
Oracle Cloud Infrastructure Requirements

Before you can order and set up REDs within your environment, you must perform the following prerequisite tasks:
• Establish an existing Oracle Cloud Infrastructure tenancy.
• Determine what Oracle Cloud Infrastructure-based workloads (buckets and instances) you want to be installed on
the REDs.
• Determine whether you need a single RED or a cluster 5-15 devices to meet your needs.
Differences from Oracle Cloud Infrastructure

Roving Edge Infrastructure differs from Oracle Cloud Infrastructure in the following ways:
• All Roving Edge Infrastructure users have administrator access.
• These items only have a single default option:
• Compartment
• Object storage namespace
• Availability domain
• Fault domain
• Region
• Tenancy
• User group
Introduction
• These Oracle Cloud Infrastructure features are not supported (and not limited to) on Roving Edge Devices:
• Tagging
• Moving resources to a different compartment (only a single default compartment is available)
• Object versioning
• Object storage replication
• Object storage retention rules
• Copying objects
• Object storage bucket re-encryption
• Bulk deletion of object versions
• Listing object versions
• iSCSI block volumes (default is paravirtualized)
• Getting namespace metadata details
Roving Edge Infrastructure Concepts

Be familiar with these concepts before setting up and using your Roving Edge Infrastructure service and Roving Edge
Devices.
General
• Oracle Cloud Infrastructure: The Infrastructure as a Service (IaaS) platform within which the Roving Edge
Infrastructure and the other services operate.
• Oracle Cloud Infrastructure Console: The web browser-based user interface for interacting with Oracle Cloud
Infrastructure.
• Command Line Interface: The method of running Oracle Cloud Infrastructure service features and functionality
using text-based commands from a command prompt window.
• API: The method of running Oracle Cloud Infrastructure service features and functionality programmatically
application programming interface (API) commands.
Roving Edge Infrastructure

The following resources and concepts are related to the Roving Edge Infrastructure service and Roving Edge Devices.
• Roving Edge Infrastructure: The Oracle Cloud Infrastructure service that allows you to operate cloud-based
workloads outside of the data center.
• Roving Edge Device (RED): A high-powered and portable server that can run core IaaS services optimized for
remote computing and storage. REDs can be ordered as single nodes or as a cluster, in which case storage and
compute capacity and durability increases. REDs are sometimes referred to as "device" in this documentation.
• Provisioning: The process of loading the required data onto the REDs from the Oracle Cloud Infrastructure
compartment and buckets you specify.
• Node: The Roving Edge Infrastructure service resource that represents a single RED. A node can be single, or as
part of a cluster. See Node Management on page 32.
• Cluster: The Roving Edge Infrastructure service resource that represents a group of 5-15 Roving Edge Devices
(RED)s working together in the same environment or network. See Cluster Management on page 40.
• Workload: The object storage bucket or compute custom image that is being provisioned from your Oracle Cloud
Infrastructure tenancy to your REDs. See Attaching Workloads on page 33.
• Data Sync: Bi-directional transmission of object storage data between REDs and your Oracle Cloud Infrastructure
tenancy. This update allows you to synchronize data between the RED and cloud, and perform software updates.
See Data Sync Task Management on page 114.
• System Upgrades and Rollbacks: The process of upgrading the operating system and on-device services of a
RED to a later version. You can also roll back the current operating system to the previous version. See Device
Software Version Management on page 47.
Introduction
Identity and Access

The following identity and access resources have been optimized for use with Roving Edge Infrastructure:
• User: A user account that can access RED features and functionality. All users have Admin privileges. See User
Management on page 50.
Compute Virtual Machine

The following compute virtual machine (VM) resources have been optimized for use with Roving Edge
Infrastructure:
• Instance: A virtual machine (VM) host running in a RED. See Instance Management on page 64.
• Image: A template of a virtual hard drive. The image determines the operating system and other software for an
instance. See Image Management on page 75.
• Shape: A template that determines the number of CPUs, amount of memory, and other resources that are allocated
to an instance.
• Boot Volume: A detachable boot volume device that contains the image used to boot a compute instance. See
Boot Volume Management on page 82.
• Console History Capture: The capture of serial console data for an instance. The data is useful for checking the
status of the instance or diagnosing problems. See Console History Capture Management on page 87.
Object Storage
The following object storage resources have been optimized for use with Roving Edge Infrastructure:
• Bucket: A repository for storing objects in a compartment within an object storage namespace. See Bucket
Management on page 89.
• Object: A file or unstructured data you upload to a bucket. See Object Management on page 91.
Block Storage
The following block storage resources have been optimized for use with Roving Edge Infrastructure:
• Block Volume: A detachable block storage device that allows you to dynamically expand the storage capacity of
an instance. See Block Volume Management on page 96.
Virtual Networking
The following virtual networking resources have been optimized for use with Roving Edge Infrastructure:
• Virtual Cloud Network (VCN): A virtual, private network that you set up in Oracle data centers. See Virtual
Cloud Network (VCN) Management on page 102.
• Subnet: Subdivisions you define in a VCN (for example, 10.0.0.0/24 and 10.0.1.0/24). Subnets contain virtual
network interface cards (VNICs), which attach to instances. See Subnet Management on page 105.
• Virtual Network Interface Card (VNIC): A virtual network component that enables an instance to connect to a
VCN and determines how the instance connects with endpoints inside and outside the VCN. See Virtual Network
Interface Card (VNIC) Management on page 69.
Supported Regions
The Roving Edge Infrastructure service is supported in the following regions:
• US-Gov-Ashburn-1 (RIC)
• US-Gov-Chicago-1 (PIA)
• US-Gov-Phoenix-1 (TUS)
• US-Langley-1 (LFI)
• US-Luke-1 (LUK)
Introduction
Service Limits
The Roving Edge Infrastructure service has the following limits:
• Roving Edge Devices: You can request either a single device (Node resource) or a cluster of 5-15 devices
(Cluster resource). You cannot request both nodes and clusters simultaneously.
• Object size: You can request files up to 5 TB to be provisioned onto a Roving Edge Device. Files larger than 5
TB are skipped in the import process.
• File name length: You can request files with names of up to 1024 characters for upload into your Object Storage
bucket.
Device Specifications
The following table lists the specifications of the Roving Edge Devices:
Attribute Description
Block Storage/Object Storage 61 TB NVMe for object, block, and file system storage.
CPU/RAM/GPU 2U server with 40 OCPUs, 512 GB RAM
Ports Dual port 100 GbE (QSFP28) + dual port 1/10 GbE
(RJ45)
Security Tamper-evident seals. Built-in TPM.
Dimensions 21" L x 17" W x 3.5" H
Weight 38 lbs
Accessing Roving Edge Infrastructure

You can access Roving Edge Infrastructure features and functionality using the following methods:
Oracle Cloud Infrastructure Console

You can create and manage your nodes and cluster resources using the Oracle Cloud Infrastructure Console. Here is
where you make your requests for Roving Edge Devices and specify the workloads that determine the provision of
these devices.
Note:
You must have internet access to access the Oracle Cloud Infrastructure
Console, including the help.
Roving Edge Device Console

Use the browser-based RED Console to manage your workloads, perform tasks, and monitor your system health.
No internet access is required to access the RED Console. You can synchronize your object storage data using a
connection to your home region.
The RED Console retains the look and feel of the Oracle Cloud Infrastructure Console, and allows you to manage and
control the on-box services on your RED.
Command Line Interface

The Oracle Cloud Infrastructure Command Line Interface (CLI) provides a set of command line-based tools for
configuring and running Roving Edge Infrastructure tasks. Use the CLI as an alternative to running commands
Introduction
from the RED Console. Sometimes you must use the CLI to complete certain tasks where no Console equivalent is
available.
Use CLIs both to perform Roving Edge Infrastructure service tasks within the Oracle Cloud Infrastructure cloud.
These tasks can include requesting nodes and clusters, and running tasks directly on REDs. Install the CLI separately
on each RED. CLIs installed on REDs run locally within your environment and do not require internet access.
Minimum Required CLI Version

The minimum CLI version required for Roving Edge Infrastructure is 2.12.1.
Determining CLI Versions

Access the following URL to see the currently available version of the CLI:
https://github.com/oracle/oci-cli/blob/master/CHANGELOG.rst
Enter the following command at the prompt to see the version of the CLI currently installed on your machine:
oci --version
If you have a version on your machine older than the version currently available, install the latest version.
Note:
Always update to the latest version of the CLI. The CLI is not updated
automatically, and you can only access new or updated CLI features by
installing the current version.
Updating Your Hosts File

Open your /etc/hosts file and add an <ip_address> <rover_host_name> entry for your RED. For
example:
10.0.1.8 rover.mycompany.com
Installing the CLI

Installation and configuration of the CLIs is described in detail in Command Line Interface (CLI) topic in the Oracle
Cloud Infrastructure documentation.
Using the CLI

You can specify CLI options using the following commands:
• --option <value> or
• --option=<value>
The basic CLI syntax is:
oci <resource> <action> <options>
This syntax is applied to the following:
• oci is the shortened CLI command name
• os bucket is an example of a <resource>
• create is an example of an <action>
• Other strings are <options>
Introduction
The following command to create a transfer job shows a typical CLI command construct.
oci os bucket create --name MyBucket
Note:
In the previous examples, provide a friendly name for the transfer job using
the ##name option. Avoid entering confidential information as part of the
display name.
Accessing Command Line Interface Help

All CLI help commands have an associated help component you can access from the command line. To view the help,
enter any command followed by the --help or -h option. For example:
oci os bucket --help
API
Roving Edge Infrastructure provides REST APIs for most of its supported features and functionality. API Reference
and Endpoints provides endpoint details and links to the available API reference documents. For general information
about using the API, see REST APIs in the Oracle Cloud Infrastructure documentation.
Note:
You must have internet access to access the API documentation residing on
Oracle Cloud Infrastructure.
Introduction
Getting Started
Chapter
2
Getting Started
Setting Policies
Before ordering your nodes and clusters, you must set up your policies in Oracle Cloud Infrastructure to allow the
required user access to various features and functionality associated with Roving Edge Infrastructure.
Allowing Access to Roving Edge Infrastructure Resources

Create these policies to allow users the access to the compartment and level of read/write access using the following
syntax:
allow group <group> to manage|use|read|inspect rover-family in

compartment <oci_compartment>
The following access options apply:

• manage: create, list, get, update, delete
• use: list, get, update
• read: list, get
• inspect: list
For example, if you wanted to allow a group of users to manage all Roving Edge Infrastructure resources in the
compartment "finance" in Oracle Cloud Infrastructure, use the following:
allow group rover-admins to manage rover-family in compartment finance
Narrow the policy to Roving Edge Infrastructure Node or Cluster resources with either of the following:
allow group rover-admins to manage rover-nodes in compartment finance
allow group rover-admins to manage rover-clusters in compartment finance
Allowing the Roving Edge Infrastructure Service to Read Buckets and Objects in your
Compartments
Setting this policy is required to grant the Roving Edge Infrastructure service read access to the buckets being
attached as workloads in your node or cluster request. This read access policy allows the generation of a manifest
file containing the information about the objects you want synced to your Roving Edge Devices. Using our "finance"
compartment example, the policy you set would be:
allow service rover to read object-family in compartment finance
Getting Started
Note:
You give read access to all the compartments associated with all your
workload buckets. For example, if you had two bucket workloads, one in
compartment "finance" and the other in compartment "accounts," you would
set this policy for both the compartments.
Enabling Data Loading to Read Buckets and Objects in your Compartments

Each Roving Edge Infrastructure node functions as a resource in Oracle Cloud Infrastructure, requiring permission to
read/write buckets in your compartments within your tenancy for data sync tasks. After a node or cluster is submitted
for provisioning, create a dynamic group containing the single node or the all the nodes in the cluster. See Managing
Dynamic Groups for more information on how to create dynamic groups.
Set the simplest matching rule for a dynamic group as:
All {resource.type='rovernode'}
Grant this dynamic-group a policy to be able to read/write to buckets, for example:
allow dyanmic-group roving-edge-nodes to manage object-family in compartment

finance
Note:
Include manage in your policy to use the data sync feature on your cluster
or node to create a bucket or upload objects to your bucket in Oracle Cloud
Infrastructure.
What's Next?
After you have set up your policies, continue on to Requesting Devices on page 17.
Requesting Devices
This section describes how to place your initial request for Roving Edge Infrastructure Roving Edge Devices nodes or
clusters.
Open the navigation menu. Under Hybrid Cloud, go to Roving Edge Infrastructure > Overview. The Roving Edge
Infrastructure page appears. This page provides an easy start point to create nodes and clusters. From this page, you
can also access the Roving Edge Infrastructure documentation.
Creating a Node Resource

To create a node resource, use the Nodes feature within the Roving Edge Infrastructure service. The node resource
serves as a request for a RED loaded with the workload you select.
While creating your node resource, you also create individual workloads that specify what content you want
preloaded in the RED. Each workload points to a specific compute image or object storage bucket within your
tenancy. You can include content from multiple compute image or object storage buckets by including multiple
workloads in your nodes resource, one content source per workload.
1. Open the navigation menu. Under Hybrid Cloud, go to Roving Edge Infrastructure > Nodes.
The Nodes page appears.
2. Select the Compartment from the list.
All nodes in that compartment are listed in tabular form.
Getting Started
3. Click Create Node.

The Create Node dialog box appears.
4. Enter the name of the node in the Node Name box.
The node you created is added to the list of nodes.
6. Click the node you added from the list.
The Details page for your node appears.
7. Click Edit.
The Update Node dialog box appears.
8. Provide the following information:
• Super User Password: Enter and confirm the password.
• Unlock Passphrase: Enter and confirm the passphrase used to unlock the Roving Edge Device associated with
this node.
• Shipping Method: Choose one of the options:
• Let Oracle ship it to you
Complete the following shipping information:
• Point of Contact
• Care Of
• Company Name
• Recipient Phone
• Recipient Email
• Country
• Address Line 1
• Address Line 2
• City/Locality
• State/Province/Region
• Zip/Postal Code
• Pick up from an Oracle facility
9. Click Update Node.
Attaching a Workload for a Node

3. (optional) Select a State from the list to limit the nodes displayed to that state.
4. Click the link for the node for which you are attaching the workload.
The Node Details dialog box appears.
5. Click Workloads under Resources. A list of workloads appears.
6. Click Select Workload at the top of the workloads list.
The Select Workload dialog box appears.
Getting Started

• Type: Select one of the following options:
• Bucket
Complete the following:
• Compartment: Select the compartment in your tenancy containing your object storage bucket.
• Bucket Name: Enter the name of the bucket where the files for the selected workload reside. The
bucket name is what appears under the Name column in the Workload list.
• Prefix: Enter a string to use for matching against the start of object names in a list query.
• Range Start: Enter a value to which object names returned by a list query must be greater or equal.
• Range End: Enter a value to which object names returned by a list query must be less.
• Compute
• Compartment: Select the compartment in your tenancy containing your virtual machine (VM) image.
• VM Image: Select one of the VM images available in the compartment.
8. Click Attach Workload.
The selected workload appears in the Workload list.
See Node Management on page 32 for more information on nodes resources.
Creating a Cluster Resource

Use the Cluster feature within the Oracle Cloud Infrastructure to create a cluster resource representing 5-15 individual
REDs using a Layer 2 switch. Creating a cluster resource serves as a request for a group of RED pre-loaded with the
workload you request.
While creating your cluster resource, you also create individual workloads that specify what content you want
preloaded in the cluster. Each workload points to a specific compute image or object storage bucket within your
tenancy. You can include content from multiple compute image or object storage buckets by including multiple
workloads in your nodes resource, one content source per workload.
1. Open the navigation menu. Under Hybrid Cloud, go to Roving Edge Infrastructure > Clusters.
The Clusters page appears.
All clusters in that compartment are listed in tabular form.
3. Click Create Cluster.
The Create Cluster dialog box appears.
4. Enter the name of the cluster in the Cluster Name box.
5. Enter how many nodes you want for the cluster. You can choose between 5-15 nodes for an individual cluster.
6. Click Create.
The cluster you created is added to the list of clusters.
The Details page for your cluster appears.
7. Click Edit.
The Edit Cluster dialog box appears.
Getting Started

• Unlock Passphrase: Enter and confirm the passphrase used to unlock the Roving Edge Devices associated
with this cluster.
• Shipping Method - choose one of the options:
• Care Of
• Company Name
• Recipient Phone
• Recipient Email
• Country
• Address Line 1
• Address Line 2
• City/Locality
• Zip/Postal Code
9. Click Edit.
Attaching a Workload for a Cluster

3. (optional) Select a State from the list to limit the clusters displayed to that state.
• Bucket
• Compute
Getting Started

See Cluster Management on page 40 for more information on cluster resources.
Determining Device Storage Capacity

A Node resource has a total usable capacity of 43 TB allocated for all services. During the provisioning of the
selected workloads, that total capacity is reduced to 36 TB allocated for object storage bucket workloads. In addition,
4 TB is available for VM images.
A Cluster resource has a total storage capacity of 175-700 TB allocated for all services, depending on the number
of nodes the cluster contains. During the provisioning of the selected workloads, that total capacity is reduced to
147-589 TB for object storage bucket workloads. In addition, another 20-60 TB is available for VM images.
These amounts are displayed in the Node and Cluster resources when you attach your workloads. As more workloads
are attached, the amount of available space is recalculated.
Viewing Your Request Status

When you complete your request and submit it, you can review the state of the request by access the nodes or cluster
details. Initially, your request has a status of Pending Approval. After Oracle approves the node request, the pre-
loading on content onto your RED can begin. Your request status changes to Provisioning.
How Oracle Provisions Your Request

Provisioning is where Oracle takes your approved node request and performs the following tasks on the RED you are
to receive:
• Install the operating system and other host software required by each REDs.
• Configure encryption on the RED's storage.
• Load the image and bucket data specified in the workloads associated with the node request.
Note:
Each RED is wiped clean of data using NIST 800-88 standards before
provisioning begins.
When provisioning is completed, the RED is delivered to you or made available for pickup at an Oracle facility
based on your preferences. Next, you can physically integrate the RED into your computing environment and begin
configuration.
What's Next?
After you have completed the tasks associated with requesting Roving Edge Devices, continue on to Setting Up
Devices on page 21.
Setting Up Devices
Follow the instructions in this section to receive, inspect, and configure your Roving Edge Devices for use in your
environment.
Receiving and Inspecting Devices

When you take possession of your REDs, your Roving Edge Infrastructure node or cluster request is updated to
Delivered status in the Oracle Cloud Infrastructure Console for your tenancy. The date and time it was received are
also included.
Getting Started
Perform the following tasks when you first receive your REDs, including inspecting the device and ensuring there has
been no tampering.
1. Visually inspect the RED shipping container for any damage, tampering, or missing ties before opening it.
2. Compare the serial number that appears on all the security ties with the serial number listed in the Oracle Cloud
Infrastructure Console. This serial number is listed in the Details section of the node or cluster request.
3. Unpack and visually inspect each RED for any tampering or damage.
Report any damage or concerns to Oracle using an SR ticket.
Note:
Do not connect or further handle a RED you feel is damaged, compromised,

or otherwise unacceptable.
Setting Up Terminal Emulation

Use the following guidance for setting up your terminal emulation.
Oracle recommends the following terminal emulation software depending on your host operating system:
• PuTTY for Windows
• ZOC for OS X
• PuTTY or Minicom for Linux
Configure the following terminal emulator software settings:
• Baud Rate: 115200
• Emulation: VT102
• Handshaking: Disabled/off
• RTS/DTS: Disabled/off
Note:
PuTTY does not allow you to configure all of these settings individually.
However, you can configure the PuTTY default settings by selecting the
Serial connection type and specifying "115200" for the Serial Line baud
speed. This configuration is sufficient to use PuTTY as a terminal emulator
for the appliance.
Connecting Devices to Your Network

After you receive your REDs and they have passed inspection, connect them to your local network through the RJ-45
serial port. Maximum data rate is 100 Mbps. Clusters run over the SFP28 ports on the Mellanox CX-5 card using
AOC cables.
You need a controlling host computer, such as a laptop, running terminal emulation software such as PuTTY to
perform this task. See Setting Up Terminal Emulation on page 22.
1. Connect the provided USB-to-DB-9 serial cable from the RED serial port to a controlling host using terminal
emulation.
2. Power up the RED.
Unlocking Devices
By default, a RED arrives in a locked state. After you have connected the RED to your network, you must unlock
the device using an unlock passphrase obtained from the device's node resource in Oracle Cloud Infrastructure.
Also, anytime you reboot the RED it reverts to a locked state. Receiving a "Device is locked" message after trying to
connect to an API endpoint is indicative that the RED is in a locked state. Unlock the RED to proceed.
Your RED must be running and connected to your controlling host running terminal emulation software such as
PuTTY to unlock the device. See Setting Up Terminal Emulation on page 22.
Getting Started
1. Connect to the Oracle Cloud Infrastructure Console for your tenancy.

2. Access the node or cluster request within the Roving Edge Infrastructure service.
3. Locate the unlock passphrase, which is listed in the Details section of your node or cluster resource.
4. Access the RED using terminal emulation.
You are prompted to provide the unlock passphrase.
5. Enter the unlock passphrase.
The RED now accepts your commands.
Configuring Devices
After you have entered your unlock passphrase and have full access to the device, configure its settings through your
controlling host.
1. Using terminal emulation, select the Configure the Network menu option and follow the prompts to set up the
network connection. These tasks include entering the public IP address, subnet mask length, and gateway IP
address.
2. Reboot the RED.
Upon restart, the RED connects to the network through the serial port.
3. Reconnect and reconfigure the network as needed.
What's Next?
After you have completed the tasks associated with setting up Roving Edge Devices, continue on to Administering
Devices on page 23.
Administering Devices
After the device is configured to work on your network, access the device and begin administering it.
Accessing the RED Console

1. Open a supported browser and access the RED Console by entering the IP address you configured for it.
2. Log into the RED Console using the "root" username and the password you specified when creating your node or
cluster order.
The RED 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 on page 46 for more information.
Adding Users
After accessing the Roving Edge Device 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.
Getting Started
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 RED 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 RED Console login password by
repeating the steps to regenerate a secret key within their user account.
Note:
All users who can access Roving Edge Device have full administration
privileges.
See User Management on page 50 for more information.
You can modify a user account with different access configurations such as auth token and API key management. See
User Credential Management on page 54 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.
Getting Started

• 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, and 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).
See Virtual Cloud Network (VCN) Management on page 102 for more information.
Creating a Subnet
After you create your virtual cloud network, create a subnet.
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 (for example, a route table).
By default, the subnet is created in the current compartment, and you can choose the resources from the same
compartment. Click the click here link in the dialog box if you want to enable compartment selection for the
subnet and each of those resources.
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
• 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, and
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 Subnet Management on page 105 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.
Getting Started
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
See Image Management on page 75 for more information.
Viewing Activity Logs

Each Roving Edge Device or cluster of devices 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 ( ) 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 Roving Edge Devices, continue on to Creating and
Launching Instances on page 26.
Creating and Launching Instances

Having completed administrating your REDs, you can now start running tasks using the on-device services and the
data provisioned to your devices. Start by creating and launching a compute instance.
1. Open the navigation menu and select Compute > Instances.
The Instances page appears. All instances are listed in tabular form.
2. Click Create Instance.
The Create Compute Instance dialog box appears.
Getting Started
3. Complete the following:

• Name: Enter a name for the instance.
• Image or operating system: Click Change Image.
The Browse All Images dialog box appears. Select an entry from the Custom Images tab and click Select
Image. The image you selected is displayed in the Image or operating system box.
• Shape: Click Change Shape.
The Browse All Shapes dialog box appears. Select a Standard or Specialty shape type, then select one of the
corresponding shapes that appear. Click Select Shape. The shape you selected is displayed in the Shape box.
• Select a virtual cloud network: Select a virtual cloud network from the list.
• Select a subnet: Select a subnet associated with the virtual cloud network from the list.
• IP address: Select an IP address option:
• Assign a public IP address (if selected, an IP address from the external CIDR is used)
• Do not assign a public IP address
• Specify a custom boot volume size: Check if you do not want to use the default boot volume size. Enter the
size in the Boot volume size box.
• SSH key: Select an SSH key option:
• Choose SSH key file: Click browse to a location and navigate to your SSH key file where you can select
it for upload. You can also drag the file into the SSH keys box.
• Paste SSH keys: Copy and paste the SSH key directly into the SSH keys box.
Note:
If the original image had the user keys on it, the new keys might not be
added to the resulting instance, depending on the image specifics.
4. Click Create.
Upon creation of the instance, the Instance Details page opens automatically.
5. Review the contents of the Instance Details page. It contains information such as its current state (indicated by the
image in the upper left corner), IP addresses used, the image used, shape settings. You can view the boot volume,
and attached VNICs by clicking their respective links in the lower left corner.
Creation of the instance can take several minutes. During this time, the state is "Provisioning." When the creation
is complete, the state changes to "Running." This state indicates that the instance is now launched.
See Instance Management on page 64 for more information.
Creating a Block Volume

After you have created and launched your initial instance, create a block volume that you can attach to the instance.
1. Open the navigation menu and select Block Storage > Block Volumes.
The Block Volumes page appears. All block volumes are listed in tabular form.
2. (optional) Select a State from the list to limit the block volumes displayed to that state.
3. Click Create Block Volume.
The Create Block Volume dialog box appears.
• Name: A user-friendly name or description.
• Size: Must be between 50 GB and 6 TB. You can choose in 1 GB increments within this range. The default is
1024 GB. If you choose a size outside of your service limit, you might be prompted to request an increase.
5. (optional) Check View detail page after this block volume is created to display the Details page for this block
volume after you create it.
Getting Started

The volume is ready to attach after its icon no longer lists it as "Provisioning" in the volume list.
Attaching the Block Volume

After you have created your block volume, attach it to the instance you previously created and launched.
2. (optional) Select a State from the list to limit the instances displayed to that state.
3. Click the instance to which you want to attach a block volume under Instances.
4. Click Attached Block Volumes in the lower left corner.
The Attached Block Volumes list appears. All attached block volumes are listed in tabular form.
5. Click Attach Block Volume.
The Attach Block Volume dialog box appears. By default, the attached block volume type is Paravirtualized.
6. Choose the volume selection option:
• Select Volume: Select the volume from the Block Volume list.
• Enter Volume OCID: Enter the OCID into the Block Volume OCID box.
7. Select the access type:
• Read/Write
• Read-only
8. Click Attach.
The block volume appears in the Attached Block Volume list.
What's Next?
After you have completed the tasks associated with creating and launching instances Roving Edge Devices, continue
on to Managing Files Using Object Storage on page 28.
Managing Files Using Object Storage

Now you are ready to work with your object storage resources and content. Each Roving Edge Devicecontains a
single default compartment in which you can create and manage buckets and the objects (files) they contain.
Creating a Bucket
Create a bucket within object storage where you can store and retrieve files.
2. Click Create Bucket.
The Create Bucket dialog box appears.
3. Enter a name in the Bucket Name box.
The system generates a default bucket name that reflects the current year, month, day, and time, for example
bucket-20190306-1359. If you change this default to any other bucket name, use letters, numbers, dashes,
underscores, and periods. Avoid entering confidential information.
4. Click Create.
The bucket is created immediately and you can start uploading objects.
Getting Started
Upload Objects to Your Bucket

The bucket you just created now appears in the list of buckets in the Buckets page. Access the bucket and upload
objects (files) into it.
2. Click the bucket to which you want to upload objects.
The Bucket Details page appears.
All objects are listed in tabular form.
3. Click Upload.
The Upload Objects dialog box appears.
Note:
Checking objects in the Objects list and then clicking Upload does not
automatically upload those files. Select files you want to upload in the
Upload Objects dialog box.
4. (optional) Specify an Object Name Prefix value. This prefix value is prepended to each one of the files you
upload. You can specify the following prefix strings:
• Prefix strings without a delimiter for matching purposes to perform allowed bulk operations
5. Select the group of objects you want to upload using any combination of the following methods:
• Drag and drop one or more files from your computer.
• Click the select files link and select the files you want to upload.
The files you select to upload are displayed in a list. If you decide that you do not want to upload a particular file,
click the X to the right of the file name.
If the files you select to upload are already stored in the bucket or folder with the same name, the Console displays
messages warning you of an overwrite.
6. Click Upload.
The selected objects are uploaded and displayed in the list of objects in the bucket.
7. Click Close to return to the Bucket Details page.
Viewing Object Details

After you have uploaded an object into your object storage bucket, you can view its details.
2. Click the bucket whose details you want to get.
Alternately, select the Actions icon ( ) for the object whose details you want to get and click View Bucket
Details.
The Bucket Details page appears. All objects are listed in tabular form.
3.
Select the Actions icon ( ) for the object whose details you want to get and click View Object Details.
The Object Details dialog box appears.
Downloading Objects from Your Bucket

You can download objects in a bucket to your local computer.
Getting Started
3.
4. Click Download.
Alternately, you can select the Actions icon ( ) for the object in the Objects page and click Download.
The object is downloaded to your local computer in the default download location.
Deleting Objects
You can delete an object that you have uploaded to your object storage bucket.
2. Click the bucket containing the object you want to delete.
Alternately, select the Actions icon ( ) for the bucket in the Buckets page and click View Bucket Details.
All buckets are listed in tabular form
3. Check each object that you want to delete.
4. Click Delete Objects.
To delete a single object, select the Actions icon ( ) for that object in the Buckets page and click Delete.
5. Confirm the deletion when prompted.
Deleting Buckets
Finally, rounding out our review of object storage tasks, you can delete the bucket you originally created.
2. Click the bucket that you want to delete. The Bucket Details page appears.
3. Click Delete.
Alternately, you can select the Actions icon ( ) for the bucket whose objects you want to list and click Delete.
What's Next?
After you have completed the tasks associated with managing files using object storage, continue on to Syncing Your
Data on page 30.
Syncing Your Data

Syncing the data between your REDs and your Oracle Cloud Infrastructure tenancy is an important task you must do
regularly. Syncing occurs bi-directionally to accomplish the following:
Getting Started
• RED-to-Oracle Cloud Infrastructure: Upload data to your Oracle Cloud Infrastructure object storage buckets for
processing and long-term storage, freeing space on the devices.
• Oracle Cloud Infrastructure-to-RED: Download data residing in the object storage buckets in your Oracle Cloud
Infrastructure tenancy to the devices. Also update system files for the device and its browser-based user interface.
1. Open the navigation menu and select Data Sync.
The Data Sync Tasks page appears. All data synchronization tasks are listed in tabular form.
2. Click Create Task.
The Create Tasks dialog box appears.
• Select the sync direction:
• From RED to OCI: Pull objects from the cloud to the Roving Edge Device (RED)
• From OCI to RED: Push objects from the RED to the cloud
• Enter the Compartment ID.
This value is the OCID associated with the Oracle Cloud Infrastructure compartment in which your object
storage bucket resides. You can find this OCID in the Details page of your compartment in the Oracle Cloud
Infrastructure Console.
• Enter the OCI Bucket Name.
This value is the name of the object storage bucket containing the data on Oracle Cloud Infrastructure with
which you are synchronizing with your data. You can find a list of your buckets in the Object Storage page in
the Oracle Cloud Infrastructure Console.
• Select one of the following options under RED Bucket:
Select an existing bucket: Select an existing bucket from the list.
Create a new bucket: Enter the name of the bucket you are creating.
• (optional) Check Sync on Create to begin the synchronization after the task is created.
4. Click Create.
If you checked the Sync on Create option, the data sync task begins immediately. If you did not check this
option, you can start the data sync task by checking the task in the Data Sync Tasks page and clicking Start.
For RED-to-OCI data syncs, click the Destination Bucket link for the task you just ran after it completes. The
Bucket Details page appears, listing those files that were downloaded into it.
For OCI-to-RED data syncs, click the Source Bucket link for the task you just ran after it completes. The Bucket
Details page appears, listing those files that were uploaded from your RED to your Oracle Cloud Infrastructure
destination.
See Data Sync Task Management on page 114 for more information.
What's Next?
You have completed the Getting Started section. The remainder of this documentation describes the various features
and services available to using the Roving Edge Infrastructure services and the Roving Edge Devices.
Ordering and Management
Chapter
3
This chapter describes ordering Rover through Oracle Cloud Infrastructure and how to perform the intial set up tasks.
Node Management
A Roving Edge Infrastructure node is a resource representing a request for a single Roving Edge Device (RED)
provisioned with workloads (object storage buckets and compute instances) sourced from your Oracle Cloud
Infrastructure tenancy.
A node resource includes the following:
• User-defined RED node name
• Shipping information (delivery to customer site or pickup from Oracle facility)
• Customer contact information
• Customer site address
• One or more selected workloads, consisting of object storage, and compute instances residing on your Oracle
Cloud Infrastructure tenancy. That content is preloaded onto the node and then made available to you by the
delivery method you specify.
Creating Nodes
Use one of the following methods to create a node.
To create a node using the Console

The Nodes page appears.
The Create Node dialog box appears.
4. Enter the name of the node in the Node Name box.
The node you created is added to the list of nodes.
6. Click the node you added from the list.
The Details page for your node appears.
7. Click Edit.

• Unlock Passphrase: Enter and confirm the passphrase used to unlock the Roving Edge Device associated with
this node.
• Shipping Method: Choose one of the options:
• Care Of
• Company Name
• Recipient Phone
• Recipient Email
• Country
• Address Line 1
• Address Line 2
• City/Locality
• Zip/Postal Code
To create a node using the CLI

Enter the following command:
oci rover node create --compartment-id compartment-id --display-

name display-name [OPTIONS]
See the CLI online help for a list of options:
oci rover node create --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover node create
command.
To create a node using the API

Use the CreateRoverNode method to create a node using the API. See CreateRoverNode in the Oracle Cloud
Infrastructure documentation for a complete description.
Attaching Workloads
Workloads determine the Oracle Cloud Infrastructure-based content that is included when a Node resource is
provisioned. When you request a Node resource for provisioning, you attach the available workloads associated with
that node for inclusion. When your device arrives, it contains the content from the workloads you specified at the time
of provisioning.
Workloads are managed as a resource within the node, and you can attach, edit, and delete them similar to other
resources. Each node's Details page contains a link for viewing the associated workloads. The workloads are
displayed in tabular form, and you can view the details of each workload, and perform tasks on them.
When you attach a workload, you specify the Oracle Cloud Infrastructure compartment and object storage bucket in
which the content you want resides within your tenancy. You can also specify filters that ensure only the files you
want are included.
To attach a workload using the Console

• Bucket
• Compute
To attach a workload using the CLI
oci rover node add-workload --compartment-id compartment-id --node-

id node_id --type "bucket" [OPTIONS]
oci rover node add-workload --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover node add-workload
command.
To attach a workload using the API
Use the RoverWorkload definition with the CreateRoverNode endpoint to create your workload.
RoverWorkload:
description: Rover workload
type: object
required:
- id
- compartmentId
- workloadType
properties:
name:
description: Name of the Rover Workload
type: string
compartmentId:
description: The OCID of the compartment containing the workload.
type: string
id:
description: The Unique Oracle ID (OCID) that is immutable on
creation.
type: string
size:
description: Size of the workload.
type: string
objectCount:
description: Number of objects in a workload.
type: string
prefix:
description: Prefix to filter objects in case it is a bucket.
type: string
rangeStart:
description: Start of the range in a bucket.
type: string
rangeEnd:
description: End of the range in a bucket.
type: string
workloadType:
description: The type of workload
type: string
Listing Workloads
Use one of the following methods to display a list of workloads associated with a node.
To get a list of workloads using the Console
3. Click the link for the node for which you are selecting the workload.
4. Click Workloads under Resources.
All workloads are listed in tabular form.
To get a list of workloads using the CLI
oci rover node list-workload --node-id node_id [OPTIONS]
oci rover node list-workload --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover node list-workload
command.
To get a list of workloads using the API
Use the nodeWorkloads attribute under CreateRoverNodeDetails to display a list of workloads associated with the
node.
Deleting Workloads
Use one of the following methods to delete a workload associated with a node.
To delete a workload using the Console
3. Click the link for the node whose workload you want to delete.
5.
Click the Actions icon ( ) for the workload you want to delete and select Delete.
To delete a workload using the CLI
oci rover node delete-workload --node-id node_id [OPTIONS]
oci rover node delete-workload --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover node delete-
workload command.
To delete a workload using the API???
TBD
Submitting Node Requests

Use one of the following methods to submit a request for a node provisioned with the workloads you specify.
To submit a node request using the Console
3. Click the link for the node you are requesting being provisioned.
4. Click Submit for Provisioning.
To submit a node request using the CLI
oci rover node request-approval --node-id node_id [OPTIONS]
oci rover node request-approval --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover node request-
approval command.
To submit a node request using the API???

TBD
Listing Nodes
Use one of the following methods to display a list of nodes in your tenancy.
To list the nodes using the Console

To list the nodes using the CLI

oci rover node list --compartment-id compartment-id [OPTIONS]
oci rover node list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover node list
command.
To list the nodes using the API

Use the ListRoverNodes method to display a list of nodes using the API. See ListRoverNodes in the Oracle Cloud
Getting Node Details

Use one of the following methods to display the details of a selected node.
To get the details of a node using the Console

4. Click the link for the node whose details you want to get.
To get the details of a node using the CLI

oci rover node show --node-id node_id [OPTIONS]
oci rover node show --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover node show
command.
To get the details of a node using the API

Use the GetRoverNode method to display the details of a node using the API. See GetRoverNode in the Oracle
Cloud Infrastructure documentation for a complete description.
Editing Nodes
Use one of the following methods to edit and update the settings of a selected node.
To edit a node using the Console

4. Click the node that you want to edit.
5. Click Edit.
6. Make your edits.
To edit a node using the CLI

oci rover node update --display-name display-name --node-id node_id

[OPTIONS]
oci rover node update --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover node update
command.
To edit a node using the API

Use the UpdateRoverNode method to edit a node using the API. See UpdateRoverNode in the Oracle Cloud
Deleting Nodes
Use one of the following methods to delete a selected node.
To delete a node using the Console

4. Click the link for the node you want to delete.
5. Click Delete.
Alternatively, you can click the Actions icon ( ), and then click Delete.
To delete a node using the CLI

oci rover node delete --node-id node_id [OPTIONS]
oci rover node delete --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover node delete
command.
To delete a node using the API

Use the DeleteRoverNode method to delete a node using the API. See DeleteRoverNode in the Oracle Cloud
Moving Nodes Between Compartments

Use one of the following methods to move a selected node to a different compartment.
To move a node to a different compartment using the Console

4. Click the node you want to move to a different compartment.
5. Click Move Resource.
The Move Resource to a Different Compartment dialog box appears.
6. Select the compartment to which you want to move your node from the Choose New Compartment list.
To move a node to a different compartment using the CLI

oci rover node change-compartment --compartment-id compartment_id --node-

id node_id [OPTIONS]
oci rover node change-compartment --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover node change-
compartment command.
To move a node to a different compartment using the API

Use the ChangeRoverNodeCompartment method to move a node to a different compartment using the API. See
ChangeRoverNodeCompartment in the Oracle Cloud Infrastructure documentation for a complete description.
Cluster Management
A Roving Edge Infrastructure cluster is an Oracle Cloud Infrastructure service resource representing a group of 5-15
REDs (represented in Oracle Cloud Infrastructure as nodes) connected with a Layer 2 switch. Each RED is preloaded
with user-specified data provisioned from an object storage bucket within the user's tenancy.
A cluster resource includes the following:
• User-defined cluster name
• Number of RED nodes included in the cluster
• Shipping information (delivery to customer site or pickup from Oracle facility)
• Customer contact information
• Customer site address
• One or more selected workloads, consisting of content residing in specified buckets residing on your Oracle Cloud
Infrastructure tenancy. That content is preloaded onto the node and then made available to you by the delivery
method you specify.
Creating Clusters
Use one of the following methods to create a cluster.
To create a cluster using the Console

The Clusters page appears.
3. Click Create Cluster.
The Create Cluster dialog box appears.
4. Enter the name of the cluster in the Cluster Name box.
5. Enter how many nodes you want for the cluster. You can choose between 5-15 nodes for an individual cluster.
6. Click Create.
The cluster you created is added to the list of clusters.
The Details page for your cluster appears.
7. Click Edit.

• Unlock Passphrase: Enter and confirm the passphrase used to unlock the Roving Edge Devices associated
with this cluster.
• Shipping Method - choose one of the options:
• Care Of
• Company Name
• Recipient Phone
• Recipient Email
• Country
• Address Line 1
• Address Line 2
• City/Locality
• Zip/Postal Code
9. Click Edit.
To create a cluster using the CLI

oci rover cluster create --cluster-size cluster_size --compartment-

id compartment_ID --display-name display_name [OPTIONS]
oci rover cluster create --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover cluster create
command.
To create a cluster using the API

Use the CreateRoverCluster method to create a cluster using the API. See CreateRoverCluster in the Oracle Cloud
Attaching Workloads
Workloads determine the Oracle Cloud Infrastructure-based content that is included in a cluster of nodes when
a Cluster resource is provisioned. When you request a node for provisioning, you attach the available workloads
associated with that node resource for inclusion. When your device arrives, it contains the content from the workloads
you specified at the time of provisioning.
Workloads are managed as a resource within the node, and you can attach, edit, and delete them similar to other
resources. Each node's Details page contains a link for viewing the associated workloads. The workloads are
displayed in tabular form, and you can view the details of each workload, and perform tasks on them.
When you attach a workload, you specify the Oracle Cloud Infrastructure compartment and object storage bucket in
which the content you want resides within your tenancy. You can also specify filters that ensure only the files you
want are included.
To attach a workload using the Console

• Bucket
• Compute
Listing Workloads
Use one of the following methods to display a list of workloads associated with a node as part of a cluster.
To list the workloads using the Console
3. Click the cluster for which you are selecting the workload.
The Cluster Details dialog box.
To list the workloads using the CLI
oci rover cluster list-workload --cluster-id cluster_id [OPTIONS]
oci rover cluster list-workload --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover cluster list-
workload command.
To list the workloads using the API
Use the clusterWorkloads attribute under CreateRoverClusterDetails to display a list of workloads associated with
the cluster.
Deleting Workloads
Use one of the following methods to delete a workload associated with a node as part of a cluster.
To delete a workload using the Console
3. Click the cluster whose workload you want to delete.
The Cluster Details dialog box.
5.
Click the Actions icon ( ) for the workload you want to delete, and then click Delete.
To delete a workload using the CLI
oci rover cluster delete-workload --cluster-id cluster_id [OPTIONS]
See the CLI online help for a list of options.
oci rover cluster delete-workload --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover cluster delete-
workload command.
To delete a workload using the API???
TBD
Submitting Cluster Requests

Use one of the following methods to submit a cluster request.
Listing Clusters
Use one of the following methods to display a list of clusters in your tenancy.
To list the clusters using the Console

To list the clusters using the CLI

oci rover cluster list --compartment-id compartment-id [OPTIONS]
See the CLI online help for a list of options.
oci rover cluster list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover cluster list
command.
To list the clusters using the API

Use the ListRoverClusters method to display a list of clusters using the API. See ListRoverClusters in the Oracle
Getting Cluster Details

Use one of the following methods to get the details of a selected cluster.
To get the details of a cluster using the Console

4. Click the cluster whose details you want to get.
The Cluster Details page appears.
To get the details of a cluster using the CLI

oci rover cluster show --cluster-id cluster_id [OPTIONS]
oci rover cluster show --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover cluster show
command.
To get the details of a cluster using the API

Use the GetRoverCluster method to display the details of a cluster using the API. See GetRoverCluster in the Oracle
Editing Clusters
Use one of the following methods to edit and update the settings of a selected cluster.
To edit a cluster using the Console

4. Click the cluster that you want to edit.

The Cluster Details page appears.
5. Click Edit.
Alternately, click the Actions icon ( ) for the cluster you want to edit and select Edit.
6. Make your edits.
7. Click Save.
To edit a cluster using the CLI

oci rover cluster update --cluster-id cluster_id [OPTIONS]
oci rover cluster update --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover cluster update
command.
To edit a cluster using the API

Use the UpdateRoverCluster method to edit a cluster using the API. See UpdateRoverCluster in the Oracle Cloud
Deleting Clusters
Use one of the following methods to delete a selected cluster.
To delete a cluster using the Console

1. Open the navigation menu. Under Core Infrastructure, go to Rover and click Rover Clusters.
4. Click the cluster you want to delete.
The Cluster Details dialog box appears.
5. Click Delete.
Alternately, click the Actions icon ( ) for the cluster you want to delete and select Delete.
To delete a cluster using the CLI

oci rover cluster delete --cluster-id cluster-id [OPTIONS]
oci rover cluster delete --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover cluster delete
command.
To delete a cluster using the API

Use the DeleteRoverCluster method to edit a cluster using the API. See DeleteRoverCluster in the Oracle Cloud
Moving Clusters Between Compartments

Use one of the following methods to move a selected node to a different compartment.
To move a cluster to a different compartment using the Console

4. Click the cluster you want to move to a different compartment.
The Cluster Details dialog box appears.
The Move Resource to a Different Compartment dialog box appears.
6. Select the compartment to which you want to move your cluster from the Choose New Compartment list.
To move a cluster to a different compartment using the CLI

oci rover cluster change-compartment --cluster-id cluster_id --compartment-

id compartment_id [OPTIONS]
oci rover cluster change-compartment --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci rover cluster change-
compartment command.
To move a cluster to a different compartment using the API

Use the ChangeRoverClusterCompartment method to move a cluster to a different compartment using the API.
See ChangeRoverClusterCompartment in the Oracle Cloud Infrastructure documentation for a complete description.
Device Monitoring
This section describes how to monitor your Roving Edge Device health and status from the RED Console.
Monitoring System Health

The System Health page displays information on your overall Roving Edge Infrastructure environment, including
the status of your services, your compute instances, the 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.
Clicking any of the panels takes you to the appropriate page to get more information or perform a task.
The System Health page appears by default when you first access the RED Console. 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.
Monitoring Roving Edge Devices

Use the monitoring feature to view the status of all your Roving Edge Devices collectively. The state of each service
is displayed.
1. Open the navigation menu and select Monitoring.
Alternately, you can select the System Status icon ( ) and click View Monitoring Info from System Status
panel that appears.
The Monitoring page appears, displaying the service and feature status of all your Roving Edge Devices in tabular
format. The status options for each item are:
• Available
• Degraded
• Unavailable
• Unknown
Device Software Version Management

This section describes how to update your Roving Edge Device operating software to the latest version or revert to a
previous software version using the RED Console.
To update the RED software

Note:
Software update versions are not cumulative to the preceding versions. If

your device is more than one software version behind the latest version, you
must update to each subsequent version individually until you are current
with the latest version.
Shut down any running virtual machines (VMs) before updating the system software on a RED.
1.
Select the System Status icon ( ) located in the upper right corner of the RED Console.
The System Upgrades dialog box appears, indicating any available software updates. It also displays your current
software version and version number of the software upgrade.
2. Click Download Update.
The software version you selected is downloaded onto your RED. The System Upgrade dialog box indicates when
the download is complete and ready for installation
3. Click Install Update.
The software update is installed on the RED. The System Upgrades dialog box indicates when the installation is
complete.
To roll back the RED software

You can only roll back a device's system software once per software version. If you have already rolled back your
system software from what had been your current version, you cannot roll the system software back a subsequent time
to revert to an even earlier software version.
1.
Select the System Status icon ( ) located in the upper right corner of the RED Console.
The System Upgrades dialog box appears, indicating whether a software upgrade is available. It also displays your
current software version and version number of the software upgrade.
2. Click the rollback icon in the upper right corner of the System Upgrades box.
The System Upgrades box displays your current software version and the version to which you can roll back.
Note:
The rollback icon only is present in the System Upgrades box if rolling
back the current system software is an option. If your device is still running
its initial system software, the roll back icon is not present because no prior
software version to which you can roll back.
3. Click Roll Back.
Your RED's software is rolled back to the previous version. The System Upgrades box indicates that a newer
software version (the one you from which you just rolled back) is available.
On-Device Services
Chapter
4
On-Device Services
This chapter describes how to use the services available to you through your Rover node or cluster.
Identity and Access Management

This section describes the following Roving Edge Infrastructure on-device resources related to Identity and Access
Management (IAM):
• Users
• User Credentials
User Management
See Managing Users in the Oracle Cloud Infrastructure documentation for more information on this feature.
Creating Users
Use one of the following methods to create a user.
To create a user using the RED Console
2. Click Create User.
The Create User dialog box appears.
• 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 RED Console.
5. Click the user entry in the User page.
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.
On-Device Services
7. Click UI-console-oauth-credential.
The UI-console-oauth-credential Details page appears.
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 RED Console login password by
repeating the steps to regenerate a secret key within their user account.
New users created through the RED Console are automatically assigned to the default Administrators group. Now you
need to give the user the credentials they need. See User Credential Management on page 54.
To create a user using the CLI
oci iam user create [OPTIONS]
oci iam user create --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam user create
command.
To create a user using the API
Use the CreateUser method to create a user using the API. See CreateUser in the Oracle Cloud Infrastructure
documentation for a complete description.
Listing Users
Use one of the following methods to list the users.
To list the users using the RED Console
Open the navigation menu and select Identity Management > Users.
To list the users using the CLI
oci iam user list [OPTIONS]
oci iam user list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam user list command.
To list the users using the API
Use the ListUsers method to display a list of users using the API. See ListUsers in the Oracle Cloud Infrastructure
Getting User Details

Use one of the following methods to get the details of a user.
On-Device Services
To get the details of a user using the RED Console

2. Click the user whose details you want to get.
Alternately, select the Actions icon ( ) for the user whose details you want to get and click View Details.
To get the details of a user using the CLI
oci iam user get [OPTIONS]
oci iam user get --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam user get command.
To get the details of a user using the API
Use the GetUser method to display a list of details for a user using the API. See GetUser in the Oracle Cloud
Editing Users
Use one of the following methods to edit a user.
To edit a user using the RED Console
3. Click Edit User.
Alternately, you can select the Actions icon ( ) for the user you want to edit and click Edit.
The Edit User dialog box appears.
4. Make your edits.
5. Click Save Changes.
To edit a user using the CLI
oci iam user update [OPTIONS]
oci iam user update --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam user update
command.
To edit a user using the API
Use the UpdateUser method to edit a user using the API. See UpdateUser in the Oracle Cloud Infrastructure
On-Device Services
Deleting Users
Use one of the following methods to delete a user.
To delete a user using the RED Console
2. Click the user you want to delete.
The User Details page opens.
3. Click Delete.
Alternately, select the Actions icon ( ) for the user you want to delete and click Delete.
To delete a user using the CLI
oci iam user delete [OPTIONS]
oci iam user delete --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam user delete
command.
To delete a user using the API
Use the DeleteUser method to delete a user using the API. See DeleteUser in the Oracle Cloud Infrastructure
Listing User Member Groups

Use one of the following methods to list the user member groups.
To list the user member groups using the RED Console
2. Click Groups.
The Groups page appears. All groups are listed in tabular form.
3. Click the group whose users you want to list.
The Group Details page appears. All group members are listed in tabular form.
To list the user member groups using the CLI
oci iam user list-groups [OPTIONS]
See the CLI online help for a list of options. You can also refer to the Oracle Cloud Infrastructure documentation for a
complete description of the oci iam user list-groups command.
To list the user members in a groups using the API
Use the ListUserGroupMemberships method to list the users members in a group a user using the API. See
ListUserGroupMemberships in the Oracle Cloud Infrastructure documentation for a complete description.
Updating User Capabilities

Use one of the following methods to update a user's capabilities. You can make updates to the following user
capabilities:
On-Device Services
• API Keys
• Auth Token
• Customer Secret Keys
• OAUTH 2.0 Client Credentials
See About User Capabilities in the Oracle Cloud Infrastructure documentation for more information on this feature.
To update a user's capabilities using the RED Console
3. Click Edit User Capabilities.
The Edit User Capabilities dialog box appears.
4. Make changes to any of the following capabilities:
• API Keys
• Auth Token
• Customer Secret Keys
• OAuth 2.0 Client Credentials
To update a user's capabilities using the CLI
oci iam user update-user-capabilities [OPTIONS]
oci iam user update-user-capabilities --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam user update-user-
capabilities command.
To update a user's capabilities using the API
Use the UpdateUserCapabilities method to edit a list of oauth user token using the API. See UpdateUserCapabilities
in the Oracle Cloud Infrastructure documentation for a complete description.
User Credential Management

See Managing User Credentials in the Oracle Cloud Infrastructure documentation for more information on this
feature.
Auth Token Management

See Working with Auth Tokens in the Oracle Cloud Infrastructure documentation for more information on this
feature.
You need the following information from the OAuth 2.0 client credential "UI-console-oauth-credential" that was
generated when the user resource was created:
• The generated secret
• The OCID of the OAuth 2.0 client credential
• The scope and audience (fully qualified scope)
See OAuth 2.0 Client Credentials Management on page 58.
On-Device Services
Creating Auth Tokens

Use one of the following methods to create an auth token.
If you are an administrator creating an auth token for another user, you need to securely deliver it to the user by
providing it verbally, printing it out, or sending it through a secure email service.
To create an auth token using the RED Console
2. Click the user for which you want to create an auth token.
3. Click Auth Tokens under Resources.
The Auth Tokens list appears. All auth tokens are listed in tabular form.
4. Click Generate Token.
The Generate Token dialog box appears.
5. Enter a Description that indicates what this token is for, for example, "Swift password token."
6. Click Generate Token.
The new token string is displayed.
7. Copy the token string immediately, because you cannot retrieve it again after closing the dialog box.
To create an auth token using the CLI
oci iam auth-token create [OPTIONS]
oci iam auth-token create --help
You can also refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam auth-
token create command.
To create an auth tokens using the API
Use the CreateAuthToken method to create an auth token using the API. See CreateAuthToken in the Oracle Cloud
Listing Auth Tokens
Use one of the following methods to list the auth tokens.
To list the auth tokens using the RED Console
To list the auth tokens using the CLI
oci iam auth-token list [OPTIONS]
On-Device Services
oci iam auth-token list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam auth-token list
command.
To list the auth tokens using the API
Use the ListAuthTokens method to display a list of auth tokens using the API. See ListAuthTokens in the Oracle
Deleting Auth Tokens
Use one of the following methods to delete an auth token.
Deleting an auth token makes it no longer valid for accessing third-party APIs.
To delete an auth token using the RED Console
4.
Select the Actions icon ( ) for the auth token you want to delete and click Delete.
To delete an auth token using the CLI
oci iam auth-token delete [OPTIONS]
oci iam auth-token delete --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam auth-token delete
command.
To delete an auth token using the API
Use the DeleteAuthToken method to delete an auth token using the API. See DeleteAuthToken in the Oracle Cloud
API Key Management

See Working with Console Passwords and API Keys in the Oracle Cloud Infrastructure documentation for more
information on this feature.
Uploading API Signing Keys
Use one of the following methods to upload an API signing key to a user account.
To upload an API signing key using the RED Console
On-Device Services
3. Click API Keys under Resources.

The API Keys list appears. All API keys are listed in tabular form.
4. Click Add Public Key.
The Add Public Key dialog box appears.
5. Select one of the following options:
• Choose Public Key File: Drag and drop a key file into the Public Key box or click select one to navigate to a
location in your network where you can select a key file.
Note:
All public key files must have the .pem extension.

• Paste Public Keys: Copy and paste the public key into the Public Key box.
6. Click Add.
1. View the user's details:
2. For the API key you want to delete, click Edit.
3. Make your changes and click Save.
To upload an API signing key using the CLI
oci iam user api-key upload [OPTIONS]
oci iam user api-key upload --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam user api-key upload
command.
To upload an API signing key using the API
Use the UploadApiKey method to edit API signing keys using the API. See UploadApiKey in the Oracle Cloud
Listing API Signing Keys
Use one of the following methods to list the API signing keys.
To list the API signing keys using the RED Console
2. Click the user for which you want to create an API key.
The API Keys list appears. All API keys are listed in tabular form.
To list API signing keys using the CLI
oci iam user api-key list [OPTIONS]
oci iam user api-key list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam user api-key list
command.
On-Device Services
To list API signing keys using the API

Use the ListApiKeys method to display a list of API signing keys a group using the API. See ListApiKeys in the
Oracle Cloud Infrastructure documentation for a complete description.
Deleting API Signing Keys
Use one of the following methods to delete an API signing key.
To delete API signing keys using the RED Console
The AOI Keys list appears. All API keys are listed in tabular form.
4.
Select the Actions icon ( ) for the API key you want to delete and click Delete.
To delete API signing keys using the CLI
oci iam user api-key delete [OPTIONS]
oci iam user api-key delete --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam user api-key delete
command.
To delete API signing keys using the API
Use the DeleteApiKey method to delete an API signing key using the API. See DeleteApiKey in the Oracle Cloud
OAuth 2.0 Client Credentials Management

The single default OAuth 2.0 client credential "UI-console-oauth-credential" is generated when a user is added. This
client credential is required for the user to login to a RED Console.
You can view this entry in the list of OAuth 2.0 client credentials under the within the Details page of a user resource
and view its details. You cannot update or delete this credential, nor can you create additional ones for the user.
You need the following information from the OAuth 2.0 client credential for the token request:
• The scope and audience (fully-qualified scope)
See Working with OAuth 2.0 Client Credentials in the Oracle Cloud Infrastructure documentation for more
Creating OAuth 2.0 Client Credentials
Use one of the following methods to create an OAuth 2.0 client credential for a user.
To create an OAuth 2.0 client credential using the RED Console
On-Device Services
3. Click OAuth 2.0 Client Credentials under Resources.
The OAuth 2.0 Client Credentials list appears. All OAuth 2.0 Client Credentials are listed in tabular form.
4. Click Generate OAuth 2.0 Client Credentials.
The OAuth 2.0 Client Credentials dialog box appears.
5. Enter a Name and Description for this credential..
6. Add the URI for the OAuth 2.0 audience and scope to which this credential will provide access.
7. Click + Another Scope to add more permissions to this credential.
Click X to delete an entry. You must have at least one Audience/Scope entry for the OAuth 2.0 credential.
8. Click Generate.
You will need the following information from the credential for the token request:
• The scope and audience (fully-qualifed scope)
To create an OAuth 2.0 client credential using the CLI
oci iam user oauth2-credential create [OPTIONS]
complete description of the oci iam user oauth2-credential create command.
To create an OAuth 2.0 client credential using the API
Use the CreateOAuthClientCredential method to create an OAuth 2.0 client credential using the API. See
CreateOAuthClientCredential in the Oracle Cloud Infrastructure documentation for a complete description.
Listing OAuth 2.0 Client Credentials
Use one of the following methods to list the OAuth 2.0 client credentials for a user.
The single default OAuth 2.0 client credential "UI-console-oauth-credential" is generated when a user is added. This
is the only OAuth 2.0 client credential allowed for a user.
To list the OAuth 2.0 client credentials using the RED Console
To list the OAuth 2.0 client credentials using the CLI
oci iam user oauth2-credential list [OPTIONS]
oci iam user oauth2-credential list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam user oauth2-
credential list command.
On-Device Services
To list the OAuth 2.0 client credentials using the API

Use the ListOAuthClientCredentials method to display a list of oauth user tokens using the API. See
ListOAuthClientCredentials in the Oracle Cloud Infrastructure documentation for a complete description.
Updating OAuth 2.0 Client Credentials
Use one of the following methods to update an OAuth 2.0 client credential for a user.
You can make the following updates to an OAuth 2.0 client credential:
• Edit the description
• Regenerate the secret
• Add, modify, or delete scopes
To update an OAuth 2.0 client credential using the RED Console
2. Click the user for which you want to update an OAuth 2.0 credential.
4. Click the OAuth 2.0 credential you want to update.
The Edit OAuth 2.0 Client Credential dialog box appears.
Alternatively, select the Actions icon ( ) for the OAuth 2.0 user credential you want to update and click View
Details.
5. Click Edit Description if you want to update it.
The Edit Description dialog box appears.
6. Update the description.
8. Click Regenerate Secret if you want to update your secret.
The Regenerate OAuth 2.0 Client Credential dialog box appears.
Caution:
If you generate a new secret for this client credential, the previously
generated secret will be invalid and requests made with the previous secret
will be denied access to target scopes.
10. Click Add Scopes if you want to add scopes to the OAuth 2.0 client credentials.
The Add Scopes dialog box appears.
11. Add the URI for the OAuth 2.0 audience and scope to which this credential will provide access .
Click X to delete an entry. You must have at least one Audience/Scope entry for the OAuth 2.0 credential.
13. Check any scopes from the list that you want to delete.
14. Click Delete.
To update an OAuth 2.0 client credential using the CLI
oci iam user oauth2-credential update [OPTIONS]
complete description of the oci iam user oauth2-credential update command.
On-Device Services
To update an OAuth 2.0 client credential using the API

Use the UpdateOAuthClientCredential method to edit an oauth user token using the API. See
UpdateOAuthClientCredential in the Oracle Cloud Infrastructure documentation for a complete description.
Deleting Oauth 2.0 Client Credentials
Use one of the following methods to delete an OAuth 2.0 client credential for a user.
Deleting an OAuth 2.0 client credential using the RED Console
4. Click the OAuth 2.0 credential you want to update.
Alternatively, select the Actions icon ( ) for the auth token you want to delete and click View Details.
The Edit OAuth 2.0 Client Credential dialog box appears.
5. Click Delete.
Alternatively, select the Actions icon ( ) for the OAuth 2.0 credential you want to delete and click Delete.
Deleting an OAuth 2.0 client credential using the CLI
oci iam user oauth2-credential delete [OPTIONS]
complete description of the oci iam user oauth2-credential delete command.
Deleting an OAuth 2.0 client credential using the API
Use the DeleteOAuthClientCredential method to edit an oauth user token using the API. See
DeleteOAuthClientCredential in the Oracle Cloud Infrastructure documentation for a complete description.
Customer Secret Keys Management

A Customer Secret key consists of an Access Key/Secret key pair. Oracle automatically generates the Access Key
when you or your administrator generates the Secret Key to create the Customer Secret key.
See Working with Customer Secret Keys in the Oracle Cloud Infrastructure documentation for more information on
this feature.
Creating Customer Secret Keys
Use one of the following methods to create a customer secret key.
To create a customer secret key using the RED Console
2. Click Customer Secret Keys under Resources.
The Customer Secret Keys list appears. All customer secret keys are listed in tabular form.
3. Click Generate Secret Key.
The Generate Secret Key dialog box appears.
4. Enter a name for the secret key.
On-Device Services
5. Click Generate Secret Key.

The generated Secret Key is displayed in the Generate Secret Key dialog box. At the same time, Oracle
generates the Access Key that is paired with the Secret Key. The newly generated Customer Secret key is added
to the list of Customer Secret Keys.
6. Copy the Secret Key immediately, because you cannot retrieve the Secret Key again after closing the dialog box
for security reasons.
If you are an administrator creating a Secret Key for another user, you need to securely deliver it to the user by
providing it verbally, printing it out, or sending it through a secure email service.
7. Click Close.
8. To show or copy the Access Key, click the Show or Copy action to the left of the Name of a particular Customer
Secret key.
To create a customer secret key using the CLI
oci iam customer-secret-key create [OPTIONS]
oci iam customer-secret-key create --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci iam customer-secret-key
create command.
To create a customer secret key using the API
Use the CreateCustomerSecretKey method to create a customer secret key using the API. See
CreateCustomerSecretKey in the Oracle Cloud Infrastructure documentation for a complete description.
Listing Customer Secret Keys
Use one of the following methods to display a list of customer secret keys.
To list the customer secret keys using the RED Console
To list the customer secret keys using the CLI
oci iam customer-secret-key list [OPTIONS]
oci iam customer-secret-key list --help
list command.
To list the customer secret keys using the API
Use the ListCustomerSecretKeys method to display a list of customer secret keys using the API. See
ListCustomerSecretKeys in the Oracle Cloud Infrastructure documentation for a complete description.
Editing Customer Secret Keys
Use one of the following methods to edit customer secret keys.
On-Device Services
To edit a customer secret key using the RED Console???

2. Click the user whose customer secret key you want to edit.
4. Click the secret key you want to edit.
The Customer Secret Key dialog box appears.
5. Click Edit.
Alternatively, select the Actions icon ( ) for the customer secret key you want to edit and click Edit.
6. The Edit Customer Secret Key dialog box appears.
Make your edits.
7. Click Save.
To edit a customer secret key using the CLI
oci iam customer-secret-key update [OPTIONS]
oci iam customer-secret-key update --help
update command.
To edit a customer secret key using the API
Use the UpdateCustomerSecretKey method to edit a customer secret key using the API. See
UpdateCustomerSecretKey in the Oracle Cloud Infrastructure documentation for a complete description.
Deleting Customer Secret Keys
Use one of the following methods to delete customer secret keys.
To delete a customer secret key using the RED Console
2. Click the user whose customer secret key you want to delete.
4. Click the secret key you want to delete.
The Customer Secret Key dialog box appears.
5. Click Delete.
Alternatively, select the Actions icon ( ) for the customer secret key you want to delete and click Delete.
On-Device Services
To delete a customer secret key using the CLI
oci iam customer-secret-key delete [OPTIONS]
oci iam customer-secret-key delete --help
delete command.
To delete a customer secret key using the API
Use the DeleteCustomerSecretKey method to delete customer secret keys using the API. See
DeleteCustomerSecretKey in the Oracle Cloud Infrastructure documentation for a complete description.
Compute Virtual Machine Infrastructure

This section describes the following Roving Edge Infrastructureon-device services related to compute virtual machine
(VM) infrastructure:
• Instances
• Images
• Boot Volumes
• Console History Capture
Instance Management
See Creating an Instance in the Oracle Cloud Infrastructure documentation for more information on this feature.
Creating Instances
Use one of the following methods to create an instance.
To create and launch an instance using the RED Console
2. Click Create Instance.
The Create Compute Instance dialog box appears.
On-Device Services

• Name: Enter a name for the instance.
• Image or operating system: Click Change Image.
The Browse All Images dialog box appears. Select an entry from the Custom Images tab and click Select
Image. The image you selected is displayed in the Image or operating system box.
• Shape: Click Change Shape.
The Browse All Shapes dialog box appears. Select a Standard or Specialty shape type, then select one of the
corresponding shapes that appear. Click Select Shape. The shape you selected is displayed in the Shape box.
• Select a virtual cloud network: Select a virtual cloud network from the list.
• Select a subnet: Select a subnet associated with the virtual cloud network from the list.
• IP address: Select an IP address option:
• Assign a public IP address (if selected, an IP address from the external CIDR is used)
• Do not assign a public IP address
• Specify a custom boot volume size: Check if you do not want to use the default boot volume size. Enter the
size in the Boot volume size box.
• SSH key: Select an SSH key option:
• Choose SSH key file: Click browse to a location and navigate to your SSH key file where you can select
it for upload. You can also drag the file into the SSH keys box.
• Paste SSH keys: Copy and paste the SSH key directly into the SSH keys box.
Note:
If the original image had the user keys on it, the new keys might not be
added to the resulting instance, depending on the image specifics.
4. Click Create.
Upon creation of the instance, the Instance Details page opens automatically.
5. Review the contents of the Instance Details page. It contains information such as its current state (indicated by the
image in the upper left corner), IP addresses used, the image used, shape settings. You can view the boot volume,
and attached VNICs by clicking their respective links in the lower left corner.
Creation of the instance can take several minutes. During this time, the state is "Provisioning." When the creation
is complete, the state changes to "Running." This state indicates that the instance is now launched.
Note:
Your instance capacity is limited by the available cores and available

memory. If you see "out of capacity" messages on instance creation,
terminate some of the existing instances that are not used and try again.
Stopped instances count toward the resources used. Terminate the instance to
free up the resources.
To create and launch an instance using the CLI
oci compute instance launch [OPTIONS]
oci compute instance launch --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute instance launch
command.
On-Device Services
To create and launch an instance using the API

Use the LaunchInstance method to create an instance using the API. See LaunchInstance in the Oracle Cloud
Listing Instances
Use one of the following methods to list the instances.
To list instances using the RED Console
To list instances using the CLI
oci compute instance list [OPTIONS]
oci compute instance list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute instance list
command.
To list instances using the API
Use the ListInstances method to display a list of instances using the API. See ListInstances in the Oracle Cloud
Getting Instance Details

Use one of the following methods to get the details of an instance.
To get the details of an instance using the RED Console
3. Click on the Instance entry whose details you want to get.
The Details page for that instance appears.
To get the details of an instance using the CLI
oci compute instance get [OPTIONS]
oci compute instance get --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute instance get
command.
To get the details of an instance using the API
Use the GetInstance method to display the details of an instance using the API. See GetInstance in the Oracle Cloud
Renaming Instances
Use one of the following methods to rename an instance.
On-Device Services
To rename an instance using the RED Console

3. Click on the instance entry whose details you want to get.
The Instance Details page appears.
4. Click More Actions and select Edit Name
The Edit Name dialog box appears.
.
5. Rename the instance.
To rename an instance using the CLI
oci compute instance update [OPTIONS]
oci compute instance update --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute instance update
command.
To rename an instance using the API
Use the UpdateInstance method to edit an instance using the API. See UpdateInstance in the Oracle Cloud
Terminating Instances
Use one of the following methods to terminate an instance.
To terminate an instance using the RED Console
3. Click on the instance entry that you want to terminate.
4. Click More Actions and select Terminate.
5. Confirm the termination when prompted.
To terminate an instance using the CLI
oci compute instance terminate [OPTIONS]
oci compute instance terminate --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute instance
terminate command.
To terminate an instance using the API
Use the TerminateInstance method to terminate an instance using the API. See TerminateInstance in the Oracle
Cloud Infrastructure documentation for a complete description of this API endpoint.
On-Device Services
Powering On and Off Instances

Use one of the following methods to power on and off an instance. See Stopping and Starting an Instance in the
Oracle Cloud Infrastructure documentation for more information on this feature.
To power on and off an instances using the RED Console
3. Click on the instance entry that you want to power on or off.
4. Click one of the following actions:
• Start: Restarts a stopped instance.
• Stop: Gracefully shuts down the instance by sending a shutdown command to the operating system.
Note:
If the applications that run on the instance take a long time to shut down,
they could be improperly stopped, resulting in data corruption. To avoid
this, shut down the instance using the commands available in the OS
before you stop the instance using the Console.
• Reboot: Gracefully reboots the instance by sending a shutdown command to the operating system, and then
powers the instance back on.
To power on and off an instances using the CLI
oci compute instance action [OPTIONS]
oci compute instance action --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute instance action
command.
To power on and off an instances using the API
Use the InstanceAction method to power on and off an instance using the API. See InstanceAction in the Oracle
Getting Windows Instance Credentials

Use one of the following methods to get Windows instance credentials. See Connecting to Your Windows Instance in
the Oracle Cloud Infrastructure documentation for more information on this feature.
To get Windows instance credentials using the RED Console
To get Windows instance credentials using the CLI
oci compute instance get-windows-initial-creds [OPTIONS]
oci compute instance get-windows-initial-creds --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute instance get-
windows-initial-creds command.
On-Device Services
To get Windows instance credentials using the API???
Listing Shapes
Use one of the following methods to list shapes. See Changing the Shape of an Instance in the Oracle Cloud
Infrastructure documentation for more information on this feature.
To list the shapes using the RED Console
3. Click on the instance entry that you want to detach and delete a VNIC.
4. Click Edit.
5. Click Edit Shape.
A list of the shapes is displayed.
To list the shapes using the CLI
oci compute shape list [OPTIONS]
complete description of the oci compute shape list command.
To list the shapes using the API
Use the ListShapes method to list shapes using the API. See ListShapes in the Oracle Cloud Infrastructure
Virtual Network Interface Card (VNIC) Management

See Virtual Network Interface Cards (VNICs) in the Oracle Cloud Infrastructure documentation for more information
on this feature.
Creating and Attaching VNICs
Use one of the following methods to create and attach a VNIC.
To create and attach a VNIC using the RED Console
3. Click on the instance entry that you want to create and attach a VNIC.
4. Under Resources, click Attached VNICs.
The primary VNIC and any secondary VNICs attached to the instance are displayed.
5. Click Create VNIC.
On-Device Services
6. In the Create VNIC dialog box, you specify which VCN and subnet to put the VNIC in. By default, the VNIC
will be created in the current compartment. You can choose a VCN and subnet from the same compartment or a
different compartment.
• Name: A friendly name for the secondary VNIC. The name doesn't have to be unique, and you can change it
later. Avoid entering confidential information.
• Virtual cloud network: The VCN that contains the subnet of interest.
• Network: Select Normal Setup: Subnet.
• Subnet: The subnet of interest. The secondary VNIC must be in the same availability domain as the instance's
primary VNIC, so the subnet list includes any regional subnets or AD-specific subnets in the primary VNIC's
availability domain.
• Physical NIC: Only relevant if this is a bare metal instance with two active physical NICs. Select which one
you want the secondary VNIC to use. When you later view the instance's details and the list of VNICs attached
to the instance, they'll be grouped by NIC 0 and NIC 1.
• Use network security groups to control traffic: Select this check box to add the secondary VNIC to at least
one network security group (NSG) of your choice. NSGs have security rules that apply only to the VNICs in
that NSG.
• Skip source/destination check: By default, this check box is NOT selected, which means the VNIC performs
the source/destination check. Only select this check box if you want the VNIC to be able to forward traffic.
• Private IP Address: Optional. An available private IP address of your choice from the subnet's CIDR
(otherwise the private IP address is automatically assigned).
• Assign a public IP address: Whether to assign a public IP address to the VNIC's primary private IP.
Available only if the subnet is public. Choose this option to specify an existing reserved public IP address
by name, or to create a new reserved IP address by assigning a name and selecting a source IP pool for the
address. If you don't select an IP pool you've created, the default Oracle IP pool is used.
• Hostname: Optional. A hostname to be used for DNS within the cloud network. Available only if the VCN
and subnet both have DNS labels.
• Show Tagging Options: If you have permissions to create a resource, then you also have permissions to apply
free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace.
If you are not sure if you should apply tags, then skip this option (you can apply tags later) or ask your
administrator.
7. Click Submit. The secondary VNIC is created and then displayed on the Attached VNICs page for the instance.
It can take several seconds before the secondary VNIC appears on the page.
8. Configure the OS to use the VNIC.
To create and attach a VNIC using the CLI
oci compute instance attach-vnic [OPTIONS]
oci compute instance attach-vnic --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute instance attach-
vnic command.
To create and attach a VNIC using the API
Use the AttachVnic method to create and attach a VNIC using the API. See AttachVnic in the Oracle Cloud
Listing VNIC Attachments
Use one of the following methods to list VNIC attachments in a specified compartment. See Virtual Network
Interface Cards (VNICs) in the Oracle Cloud Infrastructure documentation for more information on this feature.
On-Device Services
To list the VNIC attachments using the RED Console

3. Click on the instance entry that you want to list VNIC attachments.
4. Click Attached VNICs under Resources.
The primary VNIC and any secondary VNICs attached to the instance are listed. If the instance has two active
physical NICs, the VNICs are grouped by NIC 0 and NIC 1.
To list the VNIC attachments for a compartment using the CLI
oci compute vnic-attachment list [OPTIONS]
oci compute vnic-attachment list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute vnic-attachment
list command.
To list VNIC attachments for an instance using the CLI
oci compute instance list-vnics [OPTIONS]
oci compute instance list-vnics --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute instance list-
vnics command.
To list the VNIC attachments using the API
Use the ListVnicAttachments method to display a list of VNIC attachments in a compartment using the API.
See ListVnicAttachments in the Oracle Cloud Infrastructure documentation for a complete description of this API
endpoint.
Getting VNIC Details
Use one of the following methods to get the details of a VNIC. Use this to get the VNIC's private IP address, MAC
address, optional public IP address, optional DNS hostname, and other properties.
To get the details of a VNIC using the CLI
oci network vnic get [OPTIONS]
oci network vnic get --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vnic get
command.
To get the details of a VNIC using the API
Use the GetVnic method to display the details of a VNIC using the API. See GetVnic in the Oracle Cloud
Infrastructure documentation for a complete description of this API endpoint.
On-Device Services
Getting VNIC Attachment Details

Use one of the following methods to get the details of a VNIC attachment. Use this to get the VNIC's VLAN tag and
other properties. See Virtual Network Interface Cards (VNICs) in the Oracle Cloud Infrastructure documentation for
more information on this feature.
To get the details of a VNIC attachment using the RED Console
3. Click the instance associated with the VNIC to which you want to assign a secondary private ID.
5. Click the VNIC whose details you want to get.
The VNIC Details page appears.
To get the details of a VNIC attachment using the CLI
oci compute vnic-attachment get [OPTIONS]
oci compute vnic-attachment get --help
get command.
To get the details of a VNIC attachment using the API
Use the GetVnicAttachment method to VNIC attachment details using the API. See GetVnicAttachment in the
Editing VNICs
Use one of the following methods to edit a VNIC.
To edit a VNIC using the RED Console
3. Click the instance associated with the VNIC you want to edit.
5. Click the VNIC you want to edit.
6. Click Edit.
Alternately, select the Actions icon ( ) for the VNIC you want to edit and click Edit.
The Edit VNIC dialog box appears.
7. Make your edits.
On-Device Services
8. Click Save Changes

.
To edit a VNIC using the CLI
oci network vnic update [OPTIONS]
oci network vnic update --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vnic update
command.
To edit a VNIC using the API
Use the UpdateVnic method to display the details of a VNIC using the API. See UpdateVnic in the Oracle Cloud
Detaching and Deleting VNICs
Use one of the following methods to delete and detach an instance.
To detach and delete a VNIC using the RED Console
5.
Select the Actions icon ( ) for the VNIC you want to delete and click Delete.
6. Confirm when prompted.
It takes typically a few seconds before the VNIC is deleted.
If the secondary VNIC is on a Linux instance: If you then run the provided script in Linux: Configuring the OS for
Secondary VNICs, it removes the secondary VNIC from the OS configuration.
To detach and delete a VNIC using the CLI
oci compute instance detach-vnic [OPTIONS]
oci compute instance detach-vnic --help
detach-vnic command.
To detach and delete a VNIC using the API
Use the DetachVnic method to detach and delete a VNIC using the API. See DetachVnic in the Oracle Cloud
Assigning Secondary Private IPs for VNICs
Use one of the following methods to assign a secondary private IP for a VNIC.
On-Device Services
To assign a secondary private IP for a VNIC using the RED Console

5. Click the VNIC to which you want to assign a secondary private IP.
6. Click IP Addresses under Resources.
The VNIC's primary private IP and any secondary private IPs are displayed.
7. Click Assign Secondary Private IP Address.
The Assign Secondary Private IP Address dialog box appears.
• Unassign if already assigned to another VNIC: Select this check box to force reassignment of the IP address
if it's already assigned to another VNIC in the subnet. Relevant only if you specify a private IP address in the
preceding field.
• Public IP Type: Whether to assign a public IP address. Available only if the VNIC is in a public subnet.
9. Click Assign.
The secondary private IP is created and then displayed on the IP Addresses page for the VNIC.
10. Configure the IP address:
• For instances running a variant of Linux, see Linux: Details about Secondary IP Addresses.
• For Windows instances, see Windows: Details about Secondary IP Addresses.
To assign a secondary private IP for a VNIC using the CLI
oci network vnic assign-private-ip [OPTIONS]
oci network vnic assign-private-ip --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vnic assign-
private-ip command.
To assign a secondary private IP for a VNIC using the API
Use the CreatePrivateIp method to assign a secondary private IP for a VNIC using the API. See CreatePrivateIp in
the Oracle Cloud Infrastructure documentation for a complete description.
Unassigning Secondary Private IPs for VNICs
Use one of the following methods to unassign a secondary private IP for a VNIC.
Prerequisite: Oracle recommends removing the IP address from the OS configuration before deleting it from the
VNIC. See Linux: Details about Secondary IP Addresses or Windows: Details about Secondary IP Addresses.
On-Device Services
To unassign a secondary private IP for a VNIC using the RED Console

7. The VNIC's primary private IP and any secondary private IPs are displayed in tabular form.
8.
Select the Actions icon ( ) for the private IP you want to delete and click Delete.
The private IP address is returned to the pool of available addresses in the subnet.
To unassign a secondary private IP for a VNIC using the CLI
oci network vnic unassign-private-ip [OPTIONS]
oci network vnic unassign-private-ip --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vnic unassign-
private-ip command.
To unassign a secondary private IP for a VNIC using the API
Use the DeletePrivateIp method to assign a secondary private IP for a VNIC using the API. See DeletePrivateIp in
Image Management
See Managing Custom Images in the Oracle Cloud Infrastructure documentation for more information on this feature.
Creating Images
Use one of the following methods to create an image.
To create an image using the RED Console???Comment
The Custom Images page appears. All custom images are listed in tabular form.
2. Click the instance that you want to use as the basis for the custom image.
3. Click More Actions, and then click Create Custom Image.
4. In the Create in Compartment list, select the compartment to create the custom image in.
5. Enter a Name for the image. You can change the name later, if needed. You cannot use the name of an Oracle-
provided image for a custom image.
6. Show Tagging Options: If you have permissions to create a resource, then you also have permissions to apply
free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. If
you are not sure if you should apply tags, then skip this option (you can apply tags later) or ask your administrator.
7. Click Create Custom Image.To track the progress of the operation, you can monitor the associated work request.
On-Device Services
Note
If you see a message indicating that you are at the limit for custom images, you must delete at least one image before
you can create another. Or, you can request a service limit increase.
To create an image using the CLI
oci compute image create [OPTIONS]
complete description of the oci compute image create command.
To create an image using the API
Use the CreateImage method to create an image using the API. See CreateImage in the Oracle Cloud Infrastructure
Listing Images
Use one of the following methods to list custom images.
To list the images using the RED Console
2. Select a State from the list to limit the custom images displayed to that state.
To list the images using the CLI
oci compute image list [OPTIONS]
oci compute image list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute image list
command.
To list the images using the API
Use the ListImages method to list images using the API. See ListImages in the Oracle Cloud Infrastructure
Getting Image Details

Use one of the following methods to get the details of an image.
To get the details of a image using the RED Console
2. (optional) Select a State from the list to limit the images displayed to that state.
3. Click the image entry whose details you want to get.
The Details page for that image appears.
To get the details of an image using the CLI
oci compute image get [OPTIONS]
oci compute image get --help
On-Device Services
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute image get
command.
To get the details of an image using the API
Use the GetImage method to get details of an image using the API. See GetImage in the Oracle Cloud Infrastructure
Editing Images
Use one of the following methods to edit an image.
To edit an image using the RED Console
The details of that image are displayed.
4. Click Edit Details.
5. Make your edits.
Note:
After you add shape compatibility to an image, test the image on the shape to
ensure that the image actually works on the shape. Some images (especially
Windows) might never be cross-compatible with other shapes because of
driver or hardware differences.
To edit an image using the CLI
oci compute image update [OPTIONS]
oci compute image update --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute image update
command.
To edit an image using the API
Use the UpdateImage method to edit an image using the API. See UpdateImage in the Oracle Cloud Infrastructure
Removing Images
Use one of the following methods to remove an image.
To remove an image using the RED Console
2. (optional) Select a State from the list to limit the custom images displayed to that state.
3. Click the custom image entry whose details you want to get.
The Details page for that custom image appears.
4. Click Delete.
On-Device Services
To remove an image using the CLI
oci compute image delete [OPTIONS]
oci compute image delete --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute image delete
command.
To remove an image using the API
Use the DeleteImage method to remove an image using the API. See DeleteImage in the Oracle Cloud Infrastructure
Adding Image Shape Compatibility Entries

Use one of the following methods to add an image shape compatibility entry.
To add an image shape compatibility entry using the RED Console
3. Click the custom image entry whose details you want to get.
The Details page for that custom image appears.
5. Add and compatible shapes for the custom image.
6. To configure the minimum and maximum number of OCPUs that users can select when they use this image on a
flexible shape, click the down arrow in the row for the shape, and then enter the minimum and maximum OCPU
counts.
Note:
After you add shape compatibility to an image, test the image on the
shape to ensure that the image actually works on the shape. Some images
(especially Windows) might never be cross-compatible with other shapes
because of driver or hardware differences.
To add an image shape compatibility entry using the CLI
oci compute image-shape-compatibility-entry add [OPTIONS]
oci compute image-shape-compatibility-entry add --help
You can also refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute
image-shape-compatibility-entry add command.
To add an image shape compatibility entry using the API
Use the AddImageShapeCompatibilityEntry method to add an image shape compatibility entry using the API. See
AddImageShapeCompatibilityEntry in the Oracle Cloud Infrastructure documentation.
Listing Image Shape Compatibility Entries

Use one of the following methods to list image shape compatibility entries.
On-Device Services
To list the image shape compatibility entries using the RED Console
5. The list of compatible shapes for the image is displayed.
To list the image shape compatibility entries using the CLI
oci compute image-shape-compatibility-entry list [OPTIONS]
oci compute image-shape-compatibility-entry list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute image-shape-
compatibility-entry list command.
To list the image shape compatibility entries using the API
Use the ListImageShapeCompatibilityEntries method to list image shape compatibility entries using the API. See
ListImageShapeCompatibilityEntries in the Oracle Cloud Infrastructure documentation.
Getting Image Shape Compatibility Entry Details

Use one of the following methods to get the details of an image shape compatibility entry.
To get the details of an image shape compatibility entry using the RED Console???
5. Click on a compatible shape entry to get its details.
To get the details of an image shape compatibility entry using the CLI
oci compute image-shape-compatibility-entry get [OPTIONS]
oci compute image-shape-compatibility-entry get --help
compatibility-entry get command.
To get the details of an image shape compatibility entry using the API
Use the GetImageShapeCompatibilityEntry method to get details of an image shape compatibility entry using
the API. See GetImageShapeCompatibilityEntry in the Oracle Cloud Infrastructure documentation for a complete
description.
On-Device Services
Removing Image Shape Compatibility Entries

Use one of the following methods to remove an image shape compatibility entry.
To remove an image shape compatibility entry using the RED Console
5. Remove the compatible shape entry.
To remove an image shape compatibility entry using the CLI
oci compute image-shape-compatibility-entry remove [OPTIONS]
oci compute image-shape-compatibility-entry remove --help
compatibility-entry remove command.
To remove an image shape compatibility entry using the API
Use the RemoveImageShapeCompatibilityEntry method to remove an image shape compatibility entry using the
API. See RemoveImageShapeCompatibilityEntry in the Oracle Cloud Infrastructure documentation for a complete
description.
Image Import/Export Management

See Image Import/Export in the Oracle Cloud Infrastructure documentation for more information on this feature.
Importing Images
Use one of the following methods to import images from object storage.
By default, all images are imported from object storage.
To import an image using the RED Console
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
On-Device Services

After you click Import Image, you'll see the imported image in the Custom Images list for the compartment, with a
state of Importing. To track the progress of the operation, you can monitor the associated work request.
When the import completes successfully, the state changes to Available. If the state does not change, or no entry
appears in the Custom Images list, the import failed. If the import failed, ensure you have read access to the Object
Storage object, and that the object contains a supported image.
To import an image using the CLI
oci compute image import from-object [OPTIONS]
oci compute image import from-object --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute image import
from-object command.
To import an object storage using the API
Use the CreateImage method and specify ImageSourceDetails in the request body to import an image from object
storage using the API. See CreateImage and ImageSourceDetails in the Oracle Cloud Infrastructure documentation
for a complete description.
Importing Images from Object Storage using URI???
Use one of the following methods to import images from object storage using URI.
To import an images from object storage using URI using the RED Console???
To import an images from object storage using URI using the CLI
oci compute image export to-object-uri [OPTIONS]
complete description of the oci compute image export to-object-uri command.
To import an images from object storage using URI using the API
???
Exporting Images to Object Storage
Use one of the following methods to export images to object storage.
To export an image to object storage using the RED Console
3. Click the image that you want to export to object storage.
4. Click Export.
5. Specify the Object Storage location to export the image to:
• Export to an Object Storage bucket: Select a bucket and enter a name for the exported image.
• Export to an Object Storage URL: Enter the Object Storage URL.
6. Click Export Image.
After you click Export Image, the image state changes to Exporting. You can still launch instances while the image
is exporting, but you can't delete the image until the export has finished. To track the progress of the operation, you
can monitor the associated work request. For more information, see Using the Console to View Work Requests.
On-Device Services
When the export is complete, the image state changes to Available. If the image state changes to Available, but you
don't see the exported image in the Object Storage location you specified, this means that the export failed, and you
will need to go through the steps again to export the image.
To export an image to cbject storage using the CLI
oci compute image export to-object [OPTIONS]
complete description of the oci compute image export to-object command.
To export an image to object storage using the CLI
Use the ExportImage endpoint to export an image to object storage using the API. See ExportImage in the Oracle
Exporting Images to Object Storage using URI???
Use one of the following methods to import images from object storage using URI.
To export images to object storage using URI using the RED Console
To export images to object storage using URI using the CLI
oci compute image export to-object-uri [OPTIONS]
complete description of the oci compute image export to-object-uri command.
To export images to object storage using URI using the API
???
Boot Volume Management

When you launch a virtual machine (VM) instance based on an Oracle-provided image or custom image, a new boot
volume for the instance is created. That boot volume is associated with that instance until you terminate the instance.
When you terminate the instance, you can preserve the boot volume and its data.
See Boot Volumes in the Oracle Cloud Infrastructure documentation for more information on this feature.
Creating Boot Volumes

Use one of the following methods to create a boot volume. See Boot Volumes in the Oracle Cloud Infrastructure
documentation for more information on this feature.
To create a boot volume using the CLI
oci bv boot-volume create [OPTIONS]
oci bv boot-volume create --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci bv boot-volume create
command.
To create a boot volume using the API
Use the CreateBootVolume method to review a boot volume using the API. See CreateBootVolume in the Oracle
On-Device Services
Listing Boot Volumes

Use one of the following methods to list the boot volumes. See Listing Boot Volumes in the Oracle Cloud
To list the boot volumes using the RED Console
1. Open the navigation menu and select Compute > Boot Volumes.
The Boot Volumes page appears. All boot volumes are listed in tabular form.
2. (optional) Select a State from the list to limit the boot volumes displayed to that state.
To list the boot volumes using the CLI
oci bv boot-volume list [OPTIONS]
oci bv boot-volume list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci bv boot-volume list
command.
To list the boot volumes using the API
Use the ListBootVolume method to display the list of boot volumes using the API. See ListBootVolume in the
Getting Boot Volume Details

Use one of the following methods to get the details of a boot volume. See Listing Boot Volumes in the Oracle Cloud
To get the details of a boot volume using the RED Console
3. Click the boot volume whose details you want to get.
Alternately, select the Actions icon ( ) for the boot volume whose details you want to get and click View Boot
Volume Details.
The Boot Volume Details page appears.
The instance associated with the boot volume is listed in the Attached Instance field. If the value for this field
displays the following message, the boot volume has been detached from the associated instance, or the instance
has been terminated while the boot volume was preserved.
None in this Compartment.
To get the details of a boot volume using the CLI
oci bv boot-volume get [OPTIONS]
oci bv boot-volume get --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci bv boot-volume get
command.
On-Device Services
To get the details of a boot volume using the API

Use the GetBootVolume method to display the details of a boot volume using the API. See GetBootVolume in the
Renaming Boot Volumes

You can rename the a boot volume. See Boot Volumes in the Oracle Cloud Infrastructure documentation for more
To rename boot volumes using the RED Console
3. Click the boot volume you want to rename.
Alternately, select the Actions icon ( ) for the boot volume you want to rename and click Edit.
The Edit Boot Volume dialog box appears.
4. Rename the boot volume.
To rename boot volumes using the CLI
oci bv boot-volume update [OPTIONS]
oci bv boot-volume update --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci bv boot-volume update
[OPTIONS] command.
To rename boot volumes using the API
Use the UpdateBootVolume method to edit a boot volume using the API. See UpdateBootVolume in the Oracle
Deleting Boot Volumes

Use one of the following methods to delete a boot volume. See Deleting a Boot Volume in the Oracle Cloud
Important:
You cannot undo this operation. Any data on a volume will be permanently
deleted once the volume is deleted. You will also not be able to restart the
associated instance.
To delete a boot volume using the RED Console
3. Click the boot volume that you want to delete.
4. Click Terminate.
Alternately, select the Actions icon ( ) for the boot volume you want to delete and click Terminate.
On-Device Services

To delete a boot volume using the CLI
oci bv boot-volume delete [OPTIONS]
oci bv boot-volume delete --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci bv boot-volume delete
command.
To delete a boot volume using the API
Use the DeleteBootVolume method to delete a boot volume using the API. See DeleteBootVolume in the Oracle
Attaching Boot Volumes

Use one of the following methods to attach a boot volume to an instance.
Note:
You can attach a boot volume only to a stopped instance.

To attach a boot volume using the RED Console
1. Open the navigation menu and select Compute > Instance.
3. Click the instance to which you want to attach the boot volume.
4. Click Boot Volume in the lower left corner.
The Boot Volumes list appears in tabular form.
5.
Click the Actions icon ( ), and then click Attach Boot Volume. Confirm when prompted.
You can start the instance when the boot volume's state is Attached.
To attach a boot volume using the CLI
oci compute boot-volume-attachment attach [OPTIONS]
oci compute boot-volume-attachment attach --help
boot-volume-attachment attach command.
To attach a boot volume using the API
Use the AttachBootVolume method to attach a boot volume using the API. See AttachBootVolume in the Oracle
Detaching Boot Volume Attachments

Use one of the following methods to detach a boot volume from an instance.
On-Device Services
Note:
You can detach a boot volume only from a stopped instance.

To detach a boot volume using the RED Console
3. Click the instance from which you want to detach the boot volume.
5.
Click the Actions icon ( ) for the boot volume, and then click Detach Boot Volume. Confirm when prompted.
To detach a boot volume using the CLI
oci compute boot-volume-attachment detach [OPTIONS]
oci compute boot-volume-attachment detach --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute boot-volume-
attachment detach command.
To detach a boot volume using the API
Use the DetachBootVolume method to detach a boot volume using the API. See DetachBootVolume in the Oracle
Listing Boot Volume Attachments

Use one of the following methods to list the boot volumes attached to an instance.
To list boot volume attachments using the RED Console
3. Click the instance whose attached boot volumes you want to list.
To list boot volume attachments using the CLI
oci compute boot-volume-attachment list [OPTIONS]
oci compute boot-volume-attachment list --help
boot-volume-attachment list command.
On-Device Services
To list boot volume attachments using the API

Use the ListBootVolumeAttachments method to list boot volumes using the API. See ListBootVolumeAttachments
Getting Boot Volume Attachment Details

Use one of the following methods to get the details of a boot volume attached to an instance.
To get the details of a boot volume attachment using the RED Console
3. Click the instance whose attached boot volume details you want to get.
5. Click on the boot volume entry whose details you want to get.
Alternately, click the Actions icon ( ) for the boot volume, and then select View Boot Volume Details.
To get the details of a boot volume using the CLI
oci compute boot-volume-attachment get [OPTIONS]
oci compute boot-volume-attachment get --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute boot-volume-
attachment get command.
To get the details of a boot volume using the API
Use the GetBootVolumeAttachment method to get the details of a boot volume using the API. See
GetBootVolumeAttachment in the Oracle Cloud Infrastructure documentation for a complete description.
Console History Capture Management

See Displaying the Console for an Instance in the Oracle Cloud Infrastructure documentation for more information on
this feature.
Note:
Console history capture is only available using CLI and API.
Capturing Console History Capture

Use one of the following methods to capture the console history.
To capture the Console history using the CLI
oci compute console-history capture [OPTIONS]
oci compute console-history capture --help
On-Device Services
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute console-history
capture command.
To capture the Console history using the API
Use the CaptureConsoleHistory method to capture the Console history using the API. See CaptureConsoleHistory in
Listing Console History Capture

Use one of the following methods to list console history captures.
To list Console history capture using the CLI
oci compute console-history list [OPTIONS]
oci compute console-history list --help
list command.
To list Console history capture using the API
Use the ListConsoleHistories method to list Console history captures using the API. See ListConsoleHistories in the
Getting Console History Metadata Details

Use one of the following methods to get the metadata details of a console history capture.
To get the details of a Console history capture's metadat using the CLI
oci compute console-history get [OPTIONS]
oci compute console-history get --help
get command.
To get the details of a Console history capture's metadata using the API
Use the GetConsoleHistory method to get details of Console history metadata using the API. See GetConsoleHistory
Getting Console History Content Details

Use one of the following methods to get the content details of a console history capture.
To get the details of a Console history capture's content using the CLI
oci compute console-history get-content [OPTIONS]
oci compute console-history get-content --help
get-content command.
On-Device Services
To get the details of a Console history capture's content using the API
Use the GetConsoleHistoryContent method to get the details of Console history content using the API. See
GetConsoleHistoryContent in the Oracle Cloud Infrastructure documentation for a complete description.
Editing Console History Metadata

Use one of the following methods to edit the metadata of a console history capture.
To edit the Console history metadata using the CLI
oci compute console-history update [OPTIONS]
oci compute console-history update --help
update command.
To edit the Console history metadata using the API
Use the UpdateConsoleHistory method to edit Console history metadata using the API. See UpdateConsoleHistory
Deleting Console History Captures

Use one of the following methods to delete a console history capture.
To deleting a Console history capture using the CLI
oci compute console-history delete [OPTIONS]
oci compute console-history delete --help
delete command.
To deleting a Console history capture using the API
Use the DeleteConsoleHistory method to delete Console history capture using the API. See DeleteConsoleHistory in
Object Storage
This section describes the following Roving Edge Infrastructureon-device services related to object storage:
• Buckets
• Objects
Bucket Management
See Managing Buckets in the Oracle Cloud Infrastructure documentation for more information on this feature.
Creating Buckets
Use one of the following methods to create a bucket.
On-Device Services
To create a bucket using the RED Console

2. Click Create Bucket.
The Create Bucket dialog box appears.
3. Enter a name in the Bucket Name box.
The system generates a default bucket name that reflects the current year, month, day, and time, for example
bucket-20190306-1359. If you change this default to any other bucket name, use letters, numbers, dashes,
underscores, and periods. Avoid entering confidential information.
4. Click Create.
The bucket is created immediately and you can start uploading objects.
To create a bucket using the CLI
oci os bucket create [OPTIONS]
oci os bucket create --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os bucket create
command.
To create a bucket using the API
Use the CreateBucket method to create a bucket using the API. See CreateBucket in the Oracle Cloud Infrastructure
Listing Buckets
Use one of the following methods to list buckets. The list contains only summary fields for the bucket and does not
contain fields like the user-defined metadata.
To list the buckets using the RED Console
Open the navigation menu and select Object Storage > Object Storage.
To list the buckets using the CLI
oci os bucket list [OPTIONS]
oci os bucket list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os bucket list command.
To list the buckets using the API
Use the ListBuckets method to list the buckets using the API. See ListBuckets in the Oracle Cloud Infrastructure
Getting Bucket Details

Use one of the following methods to get the details of a bucket.
On-Device Services
To get the details of a bucket using the RED Console

Alternately, you can select the Actions icon ( ) associated with the bucket in the Buckets page and click View
Bucket Details.
To get the details of a bucket using the CLI
oci os bucket get [OPTIONS]
oci os bucket get --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os bucket get command.
To get the details of a bucket using the API
Use the GetBucket method to display the details of a bucket using the API. See GetBucket in the Oracle Cloud
Deleting Buckets
Use one of the following methods to delete a bucket. The bucket must be empty before you can delete it.
To delete a bucket using the RED Console
2. Click the bucket that you want to delete. The Bucket Details page appears.
3. Click Delete.
Alternately, you can select the Actions icon ( ) for the bucket whose objects you want to list and click Delete.
To delete a bucket using the CLI
oci os bucket delete [OPTIONS]
oci os bucket delete --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os bucket delete
command.
To delete a bucket using the API
Use the DeleteBucket method to delete a bucket using the API. See DeleteBucket in the Oracle Cloud Infrastructure
Object Management
See Managing Objects in the Oracle Cloud Infrastructure documentation for more information on this feature.
On-Device Services
Listing Objects
Use one of the following methods to list the objects.
To list the objects using the RED Console
Alternately, you can select the Actions icon ( ) for the bucket whose objects you want to list and click View
Bucket Details.
To list the objects using the CLI
oci os object list [OPTIONS]
oci os object list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os object list command.
To list the objects using the API
Use the ListObjects method to display a list of objects using the API. See ListObjects in the Oracle Cloud
Getting Object Details

Use one of the following methods to get the details of an object.
To get the details of an object using the RED Console
Alternately, select the Actions icon ( ) for the object whose details you want to get and click View Bucket
Details.
The Bucket Details page appears. All objects are listed in tabular form.
3.
To get the details of an object using the CLI
oci os object head [OPTIONS]
oci os object head --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os object head
command.
On-Device Services
To get the details of an object using the API

Use the HeadObject method to display the details of an object using the API. See HeadObject in the Oracle Cloud
Uploading Objects
Use one of the following methods to upload objects.
To upload an object to a bucket using the RED Console
The RED Console uses multipart uploads to upload objects larger than 64 MiB.
2. Click the bucket to which you want to upload objects.
3. Click Upload.
The Upload Objects dialog box appears.
Note:
Checking objects in the Objects list and then clicking Upload does not
automatically upload those files. Select files you want to upload in the
Upload Objects dialog box.
4. (optional) Specify an Object Name Prefix value. This prefix value is prepended to each one of the files you
upload. You can specify the following prefix strings:
• Prefix strings without a delimiter for matching purposes to perform allowed bulk operations
5. Select the group of objects you want to upload using any combination of the following methods:
• Drag and drop one or more files from your computer.
• Click the select files link and select the files you want to upload.
The files you select to upload are displayed in a list. If you decide that you do not want to upload a particular file,
click the X to the right of the file name.
If the files you select to upload are already stored in the bucket or folder with the same name, the Console displays
messages warning you of an overwrite.
6. Click Upload.
The selected objects are uploaded and displayed in the list of objects in the bucket.
7. Click Close to return to the Bucket Details page.
To upload an object to a bucket using the CLI
oci os object put [OPTIONS]
oci os object put --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os object put command.
To upload an object to a bucket using the API
Use the PutObject method to upload an object to a bucket using the API. See PutObject in the Oracle Cloud
On-Device Services
Downloading Objects
Use one of the following methods to download objects. See Managing Objects in the Oracle Cloud Infrastructure
To download an object using the RED Console
3.
4. Click Download.
Alternately, you can select the Actions icon ( ) for the object in the Objects page and click Download.
The object is downloaded to your local computer in the default download location.
To download an object using the CLI
oci os object get [OPTIONS]
oci os object get --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os object get command.
To download an object using the API
Use the GetObject method to download an object using the API. See GetObject in the Oracle Cloud Infrastructure
Deleting Objects
Use one of the following methods to delete objects.
To delete an object using the RED Console
2. Click the bucket containing the object you want to delete.
Alternately, select the Actions icon ( ) for the bucket in the Buckets page and click View Bucket Details.
All buckets are listed in tabular form
3. Check each object that you want to delete.
4. Click Delete Objects.
To delete a single object, select the Actions icon ( ) for that object in the Buckets page and click Delete.
On-Device Services
To delete an object using the CLI
oci os object delete [OPTIONS]
oci os object delete --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os object delete
command.
To delete an object using the API
Use the DeleteObject method to delete an object using the API. See DeleteObject in the Oracle Cloud Infrastructure
Bulk Object Management

Use the following methods to upload, download, and delete objects in bulk.
To bulk upload objects using the CLI
oci os object bulk-upload [OPTIONS]
oci os object bulk-upload --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os object bulk-upload
command.
To bulk download objects using the CLI
oci os object bulk-download [OPTIONS]
oci os object bulk-download --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os object bulk-download
command.
To bulk delete objects using the CLI
oci os object bulk-delete [OPTIONS]
oci os object bulk-delete --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os object bulk-delete
command.
Multipart Upload Tasks

See Using Multipart Uploads in the Oracle Cloud Infrastructure documentation for more information on this feature.
Listing Multipart Uploads
Use one of the following methods to list the multipart uploads.
On-Device Services
To list multipart uploads using the CLI
oci os multipart list [OPTIONS]
oci os multipart list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os multipart list
command.
To list multipart uploads using the API
Use the ListMultipartUploads endpoint to display a list of multipart uploads using the API. See
ListMultipartUploads in the Oracle Cloud Infrastructure documentation for a complete description.
Aborting Multipart Uploads
Use one of the following methods to abort a multipart upload.
To abort a multipart upload using the CLI
oci os multipart abort [OPTIONS]
oci os multipart abort --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci os multipart abort
command.
To abort a multipart upload using the API
Use the AbortMultipartUpload endpoint to abort a multipart upload using the API. See AbortMultipartUpload in the
Block Volume Management

See Overview of Block Volume in the Oracle Cloud Infrastructure documentation for more information on this
service.
Creating Block Volumes

Use one of the following methods to create a block volume. Volumes can be created in sizes ranging from 50 GB
(51200 MB) to 6 TB (6291456 MB), in 1 GB (1024 MB) increments. By default, volumes are 300 GB (307200 MB).
See Creating a Volume in the Oracle Cloud Infrastructure documentation for more information on this feature.
To create a block volume using the RED Console

The Create Block Volume dialog box appears.
• Name: A user-friendly name or description.
• Size: Must be between 50 GB and 6 TB. You can choose in 1 GB increments within this range. The default is
1024 GB. If you choose a size outside of your service limit, you might be prompted to request an increase.
On-Device Services
5. (optional) Check View detail page after this block volume is created to display the Details page for this block
volume after you create it.
The volume is ready to attach after its icon no longer lists it as "Provisioning" in the volume list.
To create a block volume using the CLI
oci bv volume create [OPTIONS]
oci bv volume create --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci bv volume create
command.
To create a block volume using the API

Use the CreateVolume method to create a block volume using the API. See CreateVolume in the Oracle Cloud
Listing Block Volumes

Use one of the following methods to list the block volumes. See Listing Volumes in the Oracle Cloud Infrastructure
To list the block volumes using the RED Console

To list the block volumes using the CLI
oci bv volume list [OPTIONS]
oci bv volume list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci bv volume list
command.
To list the block volumes using the API

Use the ListVolumes method to display a list of block volumes using the API. See ListVolumes in the Oracle Cloud
Getting Block Volume Details

Use one of the following methods to get the details of a block volume. See Listing Volumes in the Oracle Cloud
To get the details of a block volume using the RED Console

On-Device Services
3. Click the block volume whose details you want to get.
Alternately, select the Actions icon ( ) for the block volume whose details you want to get and click View Block
Volume Details.
To get the details of a block volume using the CLI
oci bv volume get [OPTIONS]
oci bv volume get --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci bv volume get
command.
To get the details of a block volume using the API

Use the GetVolume method to display the details of a block volume using the API. See GetVolume in the Oracle
Renaming Block Volumes

Use one of the following methods to rename a block volume. See Renaming a Volume in the Oracle Cloud
To rename a block volume from the RED Console

3. Click the block volume you want to rename.
Alternately, select the Actions icon ( ) for the block volume you want to rename and click Edit.
The Edit Block Volume dialog box appears.
4. Enter the block volume's new name in the Name box.
To rename a block volume using the CLI
oci bv volume update [OPTIONS]
complete description of the oci bv volume update command.
To rename a block volume using the API

Use the UpdateVolume method to rename a volume's display name using the API. See UpdateVolume in the Oracle
Deleting Block Volumes

Use one of the following methods to delete a block volume. The volume cannot have an active connection to an
instance. See Deleting a Volume in the Oracle Cloud Infrastructure documentation for more information on this
feature.
On-Device Services
Caution:
All data on the volume will be permanently lost when the volume is deleted.
To delete a block volume using the RED Console

1. Open the navigation menu and select Compute > Block Volumes.
3. Click the block volume that you want to delete.
The Block Volume Details page appears.
4. Click Terminate.
Alternately, select the Actions icon ( ) for the block volume you want to delete and click Terminate.
To delete a block volume using the CLI
oci bv volume delete [OPTIONS]
oci bv volume delete --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci bv volume delete
command.
To delete a block volume using the API

Use the DeleteVolume method to delete a volume using the API. See DeleteVolume in the Oracle Cloud
Block Volume Attachment Management

See Overview of Block Volume in the Oracle Cloud Infrastructure documentation for more information on this
feature.
Attaching Block Volumes

Use one of the following methods to attach block volumes. See Attaching a Volume in the Oracle Cloud
To attach a block volume using the RED Console
The Attached Block Volumes list appears. All attached block volumes are listed in tabular form.
5. Click Attach Block Volume.
The Attach Block Volume dialog box appears. By default, the attached block volume type is Paravirtualized.
6. Choose the volume selection option:
• Select Volume: Select the volume from the Block Volume list.
• Enter Volume OCID: Enter the OCID into the Block Volume OCID box.
On-Device Services
7. Select the access type:

• Read/Write
• Read-only
8. Click Attach.
The block volume appears in the Attached Block Volume list.
To attach a block volume using the CLI
oci compute volume-attachment attach [OPTIONS]
oci compute volume-attachment attach --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute volume-
attachment attach command.
To attach a block volume using the API
Use the AttachVolume method to attach a block volume using the API. See AttachVolume in the Oracle Cloud
Detaching Block Volumes

Use one of the following methods to detach block volumes. See Detaching a Volume in the Oracle Cloud
To detach a block volume using the RED Console
3. Click the instance from which you want to detach the volume under Instances.
All attached block volumes are listed in tabular form.
5.
Select the Actions icon ( ) for the block volume you want to detach and click Detach.
6. Confirm the detachment when prompted.
To detach a block volume using the CLI
oci compute volume-attachment detach [OPTIONS]
oci compute volume-attachment detach --help
attachment detach command.
To detach a block volume using the API
Use the DetachVolume endpoint to detach a block volume using the API. See DetachVolume in the Oracle Cloud
On-Device Services
Listing Block Volume Attachments

Use one of the following methods to list block volumes. See Listing Volume Attachments in the Oracle Cloud
To list block volume attachments using the RED Console
To list block volume attachments using the CLI
oci compute volume-attachment list [OPTIONS]
oci compute volume-attachment list --help
attachment list command.
To list block volume attachments using the API
Use the ListVolumeAttachments method to list block volume attachments using the API. See
ListVolumeAttachments in the Oracle Cloud Infrastructure documentation for a complete description.
Getting Block Volume Attachment Details

Use one of the following methods to get the details of a block volume. See Listing Volume Attachments in the Oracle
Cloud Infrastructure documentation for more information on this feature.
To get the details of a block volume attachment using the RED Console
3. Click the instance to which you want to attach a block volume.
5. Click on the block volume entry whose details you want to get.
The Details page for that block volume appears.
To get the details of a block volume attachment using the CLI
oci compute volume-attachment get [OPTIONS]
oci compute volume-attachment get --help
attachment get command.
On-Device Services
To get the details of a block volume attachment using the API

Use the GetVolumeAttachment method to get the details of a block volume attachments using the API. See
GetVolumeAttachment in the Oracle Cloud Infrastructure documentation for a complete description.
Networking
This section describes the following Roving Edge Infrastructure on-device services related to networking:
• Virtual Cloud Network (VCN) Management on page 102
• Subnet Management on page 105
• Virtual Network Interface Card (VNIC) Management on page 69
Virtual Cloud Network (VCN) Management

See Overview of VCNs and Subnets in the Oracle Cloud Infrastructure documentation for more information on this
feature.
Creating VCNs
Use one of the following methods to create a VCN.
These procedures create a VCN without any subnets or gateways for access. You must manually create the subnets
and other resources before you can use the VCN.
To create a VCN using the RED Console
The Create a Virtual Cloud Network dialog box appears.
• Name: A descriptive name for the VCN. It doesn't have to be unique, and it cannot be changed later in the
• 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, and 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).
Next, create one or more subnets in the cloud network. See Subnet Management on page 105.
To create a VCN using the CLI
oci network vcn create [OPTIONS]
oci network vcn create --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vcn create
command.
On-Device Services
To create a VCN using the API

Use the CreateVcn method to create a VCN using the API. See CreateVcn in the Oracle Cloud Infrastructure
Listing VCNs
Use one of the following methods to list the subnets.
To list the VCNs using the RED Console
To list the VCNs using the CLI
oci network vcn list [OPTIONS]
oci network vcn list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vcn list
command.
To the list VCNs using the API
Use the ListVcn method to display a list of VCNs using the API. See ListVcn in the Oracle Cloud Infrastructure
Getting VCN Details

Use one of the following methods to get the details of a VCN.
To get the details of a VCN using the RED Console
3. Click the VCN whose details you want to get.
Alternately, select the Actions icon ( ) for the VCN whose details you want to get and click View VCN Details.
The VCN Details page appears.
To get the details of a VCN using the CLI
oci network vcn get [OPTIONS]
oci network vcn get --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vcn get
command.
To get the details of a VCN using the API
Use the GetVcn method to display the details of a VCN using the API. See GetVcn in the Oracle Cloud Infrastructure
On-Device Services
Editing VCNs
Use one of the following methods to a VCN.
To edit a VCN using the RED Console
3. Click the VCN you want to edit.
4. Click Edit.
Alternately, select the Actions icon ( ) for the VCN whose details you want to get and click Edit.
The Edit VCN dialog box appears.
5. Make your edits.
To edit a VCN using the CLI
oci network vcn update [OPTIONS]
oci network vcn update --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vcn update
command.
To edit a VCN using the API
Use the UpdateVcn method to edit a VCN using the API. See UpdateVcn in the Oracle Cloud Infrastructure
Deleting VCNs
Use one of the following methods to delete a VCN.
To delete a VCN using the RED Console
3. Click the VCN you want to delete.
4. Click Terminate.
Alternately, select the Actions icon ( ) for the VCN you want to delete and click Terminate.
To delete a VCN using the CLI
oci network vcn delete [OPTIONS]
oci network vcn delete --help
On-Device Services
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vcn delete
command.
To delete a VCN using the API
Use the DeleteVcn method to delete a VCN using the API. See DeleteVcn in the Oracle Cloud Infrastructure
Subnet Management
See Overview of VCNs and Subnets in the Oracle Cloud Infrastructure documentation for more information on this
feature.
Creating Subnets
Use one of the following methods to create a subnet.
To create a subnet using the RED Console
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 (for example, a route table).
By default, the subnet is created in the current compartment, and you can choose the resources from the same
compartment. Click the click here link in the dialog box if you want to enable compartment selection for the
subnet and each of those resources.
• Name: A friendly name for the subnet. It doesn't have to be unique, and it cannot be changed later in the
• 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, and
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.
To create a subnet using the CLI
oci network subnet create [OPTIONS]
oci network subnet create --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network subnet create
command.
On-Device Services
To create a subnet using the API

Use the CreateSubnet method to create a subnet using the API. See CreateSubnet in the Oracle Cloud Infrastructure
Listing Subnets
Use one of the following methods to list the subnets.
To list the subnets using the RED Console
3. Click the VCN whose subnets you want to list.
4. Click Subnets.
All subnets are listed in tabular form.
To list the subnets using the CLI
oci network subnet list [OPTIONS]
oci network subnet list --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network subnet list
command.
To list the subnets using the API
Use the ListSubnets method to display a list of subnets using the API. See ListSubnets in the Oracle Cloud
Getting Subnet Details

Use one of the following methods to get the details of a subnet.
To get the details of a subnet using the RED Console
4. Click Subnets.
5. Click the subnet whose details you want to get.
Alternately, select the Actions icon ( ) for the subnet whose details you want to get and click View Subnet
Details.
The Subnet Details page appears.
To get the details of a subnet using the CLI
oci network subnet get [OPTIONS]
On-Device Services
oci network subnet get --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network subnet get
command.
To get the details of a subnet using the API
Use the GetSubnet method to display the details of a subnet using the API. See GetSubnet in the Oracle Cloud
Editing Subnets
You can change these characteristics of a subnet:
• Name
• Which set of DHCP options the subnet uses
• Which route table the subnet uses
• Which security lists the subnet uses
Use one of the following methods to edit a subnet.
To edit a subnets using the RED Console
4. Click Subnets.
Alternately, select the Actions icon ( ) for the subnet whose details you want to get and click View Subnet
Details.
6. Click Edit.
Alternately, select the Actions icon ( ) for the subnet you want to edit and click Edit.
The Edit Subnet dialog box appears.
7. Make your edits.
To edit a subnets using the CLI
oci network subnet update [OPTIONS]
oci network subnet update --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network subnet update
command.
On-Device Services
To edit a subnets using the API

Use the UpdateSubnet method to edit a subnet using the API. See UpdateSubnet in the Oracle Cloud Infrastructure
Deleting Subnets
Use one of the following methods to delete a subnet.
If the subnet is empty, its state changes to TERMINATING briefly and then TERMINATED. If the subnet is not
empty, you get an error indicating that there are still instances or other resources in it that you must delete first.
To delete a subnet using the RED Console
4. Click Subnets.
Alternately, select the Actions icon ( ) for the subnet you want to delete and click View Subnet Details.
6. Click Terminate.
Alternately, select the Actions icon ( ) for the subnet you want to delete and click Terminate.
To delete a subnet using the CLI
oci network subnet delete [OPTIONS]
oci network subnet delete --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network subnet delete
command.
To delete a subnet using the API
Use the DeleteSubnet method to delete a subnet using the API. See DeleteSubnet in the Oracle Cloud Infrastructure
Virtual Network Interface Card (VNIC) Management

See Virtual Network Interface Cards (VNICs) in the Oracle Cloud Infrastructure documentation for more information
on this feature.
Creating and Attaching VNICs

Use one of the following methods to create and attach a VNIC.
To create and attach a VNIC using the RED Console
On-Device Services
3. Click on the instance entry that you want to create and attach a VNIC.
4. Under Resources, click Attached VNICs.
5. Click Create VNIC.
6. In the Create VNIC dialog box, you specify which VCN and subnet to put the VNIC in. By default, the VNIC
will be created in the current compartment. You can choose a VCN and subnet from the same compartment or a
different compartment.
• Name: A friendly name for the secondary VNIC. The name doesn't have to be unique, and you can change it
later. Avoid entering confidential information.
• Virtual cloud network: The VCN that contains the subnet of interest.
• Network: Select Normal Setup: Subnet.
• Subnet: The subnet of interest. The secondary VNIC must be in the same availability domain as the instance's
primary VNIC, so the subnet list includes any regional subnets or AD-specific subnets in the primary VNIC's
availability domain.
• Physical NIC: Only relevant if this is a bare metal instance with two active physical NICs. Select which one
you want the secondary VNIC to use. When you later view the instance's details and the list of VNICs attached
to the instance, they'll be grouped by NIC 0 and NIC 1.
• Use network security groups to control traffic: Select this check box to add the secondary VNIC to at least
one network security group (NSG) of your choice. NSGs have security rules that apply only to the VNICs in
that NSG.
• Skip source/destination check: By default, this check box is NOT selected, which means the VNIC performs
the source/destination check. Only select this check box if you want the VNIC to be able to forward traffic.
• Assign a public IP address: Whether to assign a public IP address to the VNIC's primary private IP.
Available only if the subnet is public. Choose this option to specify an existing reserved public IP address
by name, or to create a new reserved IP address by assigning a name and selecting a source IP pool for the
address. If you don't select an IP pool you've created, the default Oracle IP pool is used.
• Show Tagging Options: If you have permissions to create a resource, then you also have permissions to apply
free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace.
If you are not sure if you should apply tags, then skip this option (you can apply tags later) or ask your
administrator.
7. Click Submit. The secondary VNIC is created and then displayed on the Attached VNICs page for the instance.
It can take several seconds before the secondary VNIC appears on the page.
8. Configure the OS to use the VNIC.
To create and attach a VNIC using the CLI
oci compute instance attach-vnic [OPTIONS]
oci compute instance attach-vnic --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute instance attach-
vnic command.
On-Device Services
To create and attach a VNIC using the API

Use the AttachVnic method to create and attach a VNIC using the API. See AttachVnic in the Oracle Cloud
Listing VNIC Attachments

Use one of the following methods to list VNIC attachments in a specified compartment. See Virtual Network
Interface Cards (VNICs) in the Oracle Cloud Infrastructure documentation for more information on this feature.
To list the VNIC attachments using the RED Console
3. Click on the instance entry that you want to list VNIC attachments.
To list the VNIC attachments for a compartment using the CLI
oci compute vnic-attachment list [OPTIONS]
oci compute vnic-attachment list --help
list command.
To list VNIC attachments for an instance using the CLI
oci compute instance list-vnics [OPTIONS]
oci compute instance list-vnics --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci compute instance list-
vnics command.
To list the VNIC attachments using the API
Use the ListVnicAttachments method to display a list of VNIC attachments in a compartment using the API.
See ListVnicAttachments in the Oracle Cloud Infrastructure documentation for a complete description of this API
endpoint.
Getting VNIC Details

Use one of the following methods to get the details of a VNIC. Use this to get the VNIC's private IP address, MAC
address, optional public IP address, optional DNS hostname, and other properties.
To get the details of a VNIC using the CLI
oci network vnic get [OPTIONS]
On-Device Services
oci network vnic get --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vnic get
command.
To get the details of a VNIC using the API
Use the GetVnic method to display the details of a VNIC using the API. See GetVnic in the Oracle Cloud
Getting VNIC Attachment Details

Use one of the following methods to get the details of a VNIC attachment. Use this to get the VNIC's VLAN tag and
other properties. See Virtual Network Interface Cards (VNICs) in the Oracle Cloud Infrastructure documentation for
more information on this feature.
To get the details of a VNIC attachment using the RED Console
5. Click the VNIC whose details you want to get.
To get the details of a VNIC attachment using the CLI
oci compute vnic-attachment get [OPTIONS]
oci compute vnic-attachment get --help
get command.
To get the details of a VNIC attachment using the API
Use the GetVnicAttachment method to VNIC attachment details using the API. See GetVnicAttachment in the
Editing VNICs
Use one of the following methods to edit a VNIC.
To edit a VNIC using the RED Console
3. Click the instance associated with the VNIC you want to edit.
On-Device Services

5. Click the VNIC you want to edit.
6. Click Edit.
Alternately, select the Actions icon ( ) for the VNIC you want to edit and click Edit.
The Edit VNIC dialog box appears.
7. Make your edits.
8. Click Save Changes
.
To edit a VNIC using the CLI
oci network vnic update [OPTIONS]
oci network vnic update --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vnic update
command.
To edit a VNIC using the API
Use the UpdateVnic method to display the details of a VNIC using the API. See UpdateVnic in the Oracle Cloud
Detaching and Deleting VNICs

Use one of the following methods to delete and detach an instance.
To detach and delete a VNIC using the RED Console
5.
Select the Actions icon ( ) for the VNIC you want to delete and click Delete.
6. Confirm when prompted.
It takes typically a few seconds before the VNIC is deleted.
If the secondary VNIC is on a Linux instance: If you then run the provided script in Linux: Configuring the OS for
Secondary VNICs, it removes the secondary VNIC from the OS configuration.
To detach and delete a VNIC using the CLI
oci compute instance detach-vnic [OPTIONS]
On-Device Services
oci compute instance detach-vnic --help
detach-vnic command.
To detach and delete a VNIC using the API
Use the DetachVnic method to detach and delete a VNIC using the API. See DetachVnic in the Oracle Cloud
Assigning Secondary Private IPs for VNICs

Use one of the following methods to assign a secondary private IP for a VNIC.
To assign a secondary private IP for a VNIC using the RED Console
The VNIC's primary private IP and any secondary private IPs are displayed.
7. Click Assign Secondary Private IP Address.
The Assign Secondary Private IP Address dialog box appears.
• Unassign if already assigned to another VNIC: Select this check box to force reassignment of the IP address
if it's already assigned to another VNIC in the subnet. Relevant only if you specify a private IP address in the
preceding field.
• Public IP Type: Whether to assign a public IP address. Available only if the VNIC is in a public subnet.
9. Click Assign.
The secondary private IP is created and then displayed on the IP Addresses page for the VNIC.
10. Configure the IP address:
• For instances running a variant of Linux, see Linux: Details about Secondary IP Addresses.
• For Windows instances, see Windows: Details about Secondary IP Addresses.
To assign a secondary private IP for a VNIC using the CLI
oci network vnic assign-private-ip [OPTIONS]
oci network vnic assign-private-ip --help
On-Device Services
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vnic assign-
private-ip command.
To assign a secondary private IP for a VNIC using the API
Use the CreatePrivateIp method to assign a secondary private IP for a VNIC using the API. See CreatePrivateIp in
Unassigning Secondary Private IPs for VNICs

Use one of the following methods to unassign a secondary private IP for a VNIC.
Prerequisite: Oracle recommends removing the IP address from the OS configuration before deleting it from the
VNIC. See Linux: Details about Secondary IP Addresses or Windows: Details about Secondary IP Addresses.
To unassign a secondary private IP for a VNIC using the RED Console
7. The VNIC's primary private IP and any secondary private IPs are displayed in tabular form.
8.
Select the Actions icon ( ) for the private IP you want to delete and click Delete.
The private IP address is returned to the pool of available addresses in the subnet.
To unassign a secondary private IP for a VNIC using the CLI
oci network vnic unassign-private-ip [OPTIONS]
oci network vnic unassign-private-ip --help
Refer to the Oracle Cloud Infrastructure documentation for a complete description of the oci network vnic unassign-
private-ip command.
To unassign a secondary private IP for a VNIC using the API
Use the DeletePrivateIp method to assign a secondary private IP for a VNIC using the API. See DeletePrivateIp in
Data Sync Task Management

Perform bi-directional data synchronizations on your RED nodes to both push collected data to your Oracle Cloud
Infrastructure tenancy, and also to update the devices with software updates and other essential data.
The following are the prerequisite tasks for performing a bi-directional data synchronization:
• Connect your RED node or cluster to your local site network, such as a site headquarters, and provide a public IP
for the node or cluster.
On-Device Services
• Provide routing using a FastConnect connection to an Oracle Cloud Infrastructure region.

• Specify the object storage buckets on Oracle Cloud Infrastructure that contain the data preloaded on the node
or cluster at the time of provisioning. These buckets are the source and destination of the data being transferred
during the synchronization.
Creating Data Sync Tasks
To create a data sync task using the RED Console

2. Click Create Task.
The Create Tasks dialog box appears.
• Select the sync direction:
• From RED to OCI: Pull objects from the cloud to the Roving Edge Device (RED)
• From OCI to RED: Push objects from the RED to the cloud
• Enter the Compartment ID.
This value is the OCID associated with the Oracle Cloud Infrastructure compartment in which your object
storage bucket resides. You can find this OCID in the Details page of your compartment in the Oracle Cloud
Infrastructure Console.
• Enter the OCI Bucket Name.
This value is the name of the object storage bucket containing the data on Oracle Cloud Infrastructure with
which you are synchronizing with your data. You can find a list of your buckets in the Object Storage page in
the Oracle Cloud Infrastructure Console.
• Select one of the following options under RED Bucket:
Select an existing bucket: Select an existing bucket from the list.
Create a new bucket: Enter the name of the bucket you are creating.
• (optional) Check Sync on Create to begin the synchronization after the task is created.
4. Click Create.
If you checked the Sync on Create option, the data sync task begins immediately. If you did not check this
option, you can start the data sync task by checking the task in the Data Sync Tasks page and clicking Start.
For RED-to-OCI data syncs, click the Destination Bucket link for the task you just ran after it completes. The
Bucket Details page appears, listing those files that were downloaded into it.
For OCI-to-RED data syncs, click the Source Bucket link for the task you just ran after it completes. The Bucket
Details page appears, listing those files that were uploaded from your RED to your Oracle Cloud Infrastructure
destination.
To create a data sync task using the API

Use the CreateTask method to create a data sync task using the API. See ??? in the Oracle Cloud Infrastructure
Listing Data Sync Tasks
To list the data sync tasks using the RED Console

2. (optional) Select a Status from the list to limit the data sync tasks displayed to that status.
On-Device Services
Getting Data Sync Task Details
To get the details of a data sync task using the RED Console
The Data Sync Tasks page appears. All data sync tasks are listed in tabular form.
3.
Select the Actions icon ( ) for the data sync task whose details you want to get and click View Details.
The Task Details page box appears.
To get the details of a data sync task using the API

Use the GetTasks method to get details on one or more data sync tasks. See ??? in the Oracle Cloud Infrastructure
Editing Data Sync Tasks
To edit a data sync task using the RED Console

3.
Select the Actions icon ( ) for the data sync task that you want to edit and click Edit.
The Edit Task dialog box appears.
4. Make your edits.
5. Click Save.
To edit a data sync task using the API

Use the UpdateTask method to edit a data sync task using the API. See ??? in the Oracle Cloud Infrastructure
Deleting Data Sync Tasks
To delete a data sync task using the RED Console

3. Check the data sync tasks you want to delete.
4.
Select the Actions icon ( ) for the data sync task you checked and click Delete.
To delete a data sync task using the API

DeleteTask
Use the DeleteTask method to delete a data sync task using the API. See ??? in the Oracle Cloud Infrastructure
Starting Data Sync Tasks
On-Device Services
To start a data sync task using the RED Console

3. Check the data sync task that you want to start.
4. Click Start.
Alternately, select the Actions icon ( ) for the data sync task that you checked and click Start
5. Confirm the start when prompted.
To start a data sync task using the API

Use the StartDataSync method to get start a data sync task. See ??? in the Oracle Cloud Infrastructure documentation
Stopping Data Sync Tasks

Note:
You can only stop a data sync task that has already started.
To stop a data sync task using the RED Console

3. Check the data sync task that you want to stop.
4. Click Stop.
Alternately, select the Actions icon ( ) for the data sync task that you checked and click Stop.
5. Confirm the stop when prompted.
To stop a data sync task using the API

Use the StopDataSync method to get stop a data sync task. See ??? in the Oracle Cloud Infrastructure documentation
Glossary
Glossary
A
AD-specific subnet
A subnet that is specific to a particular availability domain (AD). Historically all subnets were AD-specific.
Compare with regional subnets, which Oracle recommends over AD-specific subnets.
alarm
The trigger rule and query to evaluate and related configuration, such as notification details to use when the
trigger is breached. Alarms passively monitor your cloud resources using metrics in Monitoring.
API key
A credential for securing requests to the Oracle Cloud Infrastructure REST API.
application (Application Migration)
A combination of the artifacts and configuration deployed on one or more service instances running in the
source environment.
attach
Link a volume and instance together. Allows an instance to connect and mount the volume as a hard drive.
Attribute
An attribute describes a data item with a name and data type. For example, a column in a table or a field in a
file.
auth token
Oracle Cloud Infrastructure-generated token you use to authenticate with third-party APIs, such as a Swift
client.
availability domain
One or more isolated, fault-tolerant Oracle data centers that host cloud resources such as instances, volumes,
and subnets. A region contains one or more availability domains.
B
backend set
A logical entity defined by a list of backend servers, a load balancing policy, and a health check policy.
bare metal IaaS
A cloud infrastructure that allows you to utilize hosted physical hardware, as opposed to traditional software-
based virtual machines, ensuring a high level of security and performance.
block storage volume
A virtual disk that provides persistent storage space for instances in the cloud.
bucket
A logical container for storing objects.
Glossary
C
Category
A category is created in a glossary to group logically related business terms. You can create a category
within a category to group your terms.
CHAP
Stands for Challenge-Handshake-Authentication-Protocol. It is a security protocol used by iSCSI for
authentication between a volume and an instance.
Cloud Block Storage
A service that allows you to add block storage volumes to an instance in order to expand the available
storage on that resource.
cloud network
A virtual version of a traditional network—including CIDRs, subnets, route tables, and gateways—on which
your instance runs.
cluster network
A pool of high performance computing (HPC) instances that are connected with a high-bandwidth, ultra low-
latency network.
compartment
A collection of related resources that can be accessed only by certain groups that have been given permission
by an administrator in your organization.
Compute
A service that lets you provision and manage compute hosts, known as instances.
connect
Make an attached volume usable by an instance's guest OS.
CPE
The router at the edge of your on-premises network. The Networking service also has an object called a CPE,
which is a virtual representation of your edge router. You create that object when setting up VPN Connect
(an IPSec VPN) between Oracle and your on-premises network.
CPE Configuration Helper
A feature of the Oracle Console that generates information that a network engineer can use to configure the
customer-premises equipment (CPE) at their end of a VPN connection.
cross-connect
Used with Oracle Cloud Infrastructure FastConnect, specifically if you're using a third-party provider or
colocated with Oracle in a FastConnect location. A cross-connect is the physical cable connecting your
existing network to Oracle in the FastConnect location.
cross-connect group
Used with Oracle Cloud Infrastructure FastConnect, specifically if you're using a third-party provider or
colocated with Oracle in a FastConnect location. A cross-connect group is a link aggregation group (LAG)
that contains at least one cross-connect.
customer-premises equipment
The router at the edge of your on-premises network. The Networking service also has an object called a CPE,
which is a virtual representation of your edge router. You create that object when setting up VPN Connect
(an IPSec VPN) between Oracle and your on-premises network.
Glossary
D
Data Asset (Data Catalog and Data Integration)
Represents a data source, such as a database, an object store, a file or document store, a message queue, or an
application.
Data Catalog Tags
Tags are free-form labels or keywords you create to be able to logically identify data objects. Tags help in
metadata classification and discovery. You create tags for data assets, data entities, and attributes. Using tags,
you can search for all data objects tagged with a specific tag name.
Data Entity (Data Catalog and Data Integration)
A data entity is a collection of data such as a database table or view, or a single logical file and normally has
many attributes that describe its data.
data point (Monitoring service)
A timestamp-value pair for the specified metric. Example: 2018-05-10T22:19:00Z, 10.4
DB System
A dedicated bare metal instance running Oracle Linux, optimized for running one or more Oracle databases.
A DB System is a Database Service resource.
DHCP options
Configuration information that is automatically provided to the instances when they boot up.
dimension (Monitoring service)
A qualifier provided in a metric definition. Example: Resource identifier (resourceId), provided in the
definitions of oci_computeagent metrics.
display name
A friendly name or description that helps you easily identify the resource.
DRG
An optional virtual router that you can add to your VCN to provide a path for private network traffic between
your VCN and on-premises network.
DRG attachment
When you attach a dynamic routing gateway (DRG) to a virtual cloud network (VCN), the result is a DRG
attachment object. To detach the DRG, you delete that attachment object.
drift (Resource Manager)
Difference between the actual, real-world state of your infrastructure and the stack's last executed
configuration.
dynamic group
A special type of IAM group that contains instances that match rules that you define (thus the membership
can change dynamically as matching instances are terminated or launched). These instances act as "principal"
actors and can make API calls to Oracle Cloud Infrastructure services according to IAM policies that you
write for the dynamic group.
dynamic routing gateway
An optional virtual router that you can add to your VCN to provide a path for private network traffic between
your VCN and on-premises network.
Glossary
E
ephemeral public IP
A public IP address (and related properties) that is temporary and exists for the life of the instance it's
assigned to. It can be assigned only to the primary private IP on a VNIC. Compare with reserved public IP.
Export
Controls how file systems are accessed by NFS clients when they connect to a mount target.
Export Options
A set of parameters that specify the level of access granted to NFS clients when they connect to a mount
target.
F
FastConnect
FastConnect provides an easy way to create a dedicated, private connection between your data center or
existing network and Oracle Cloud Infrastructure. FastConnect provides higher-bandwidth options, and a
more reliable and consistent networking experience compared to internet-based connections.
FastConnect location
A specific data center where you can connect to Oracle Cloud Infrastructure by using FastConnect.
fault domain
A logical grouping of hardware and infrastructure within an availability domain to provide isolation of
resources in case of hardware failure or unexpected software changes.
File System
An organized system of directories and folders where data is stored.
frequency (Monitoring service)
The time period between each posted raw data point for a given metric. (Raw data points are posted by the
metric namespace to the Monitoring service.)
G
Glossary
A glossary is a collection of business concepts in your company. Glossary constitutes of categories and
business terms.
group
A collection of users who all need a particular type of access to a set of resources or compartment.
guest operating system
An operating system installed on a cloud instance.
guest OS
An operating system installed on a cloud instance.
H
Harvest
Process that extracts technical metadata from your connected data sources into your Data Catalog repository.
Glossary
health check
A test to confirm the availability of backend servers.
I
IaaS
A service that allows customers to rapidly scale up or down their computer infrastructure (computing,
storage, or network).
IAM
The service for controlling authentication and authorization of users who need to use your cloud resources.
Identity and Access Management Service
The service for controlling authentication and authorization of users who need to use your cloud resources.
Also called "IAM".
identity provider
A service that provides identifying credentials and authentication for federated users.
IdP
Short for "identity provider", which is a service that provides identifying credentials and authentication for
federated users.
image
A template of a virtual hard drive that determines the operating system and other software for an instance.
Infrastructure-as-a-Service
A service that allows customers to rapidly scale up or down their computer infrastructure (computing,
storage, or network).
instance
A bare metal or virtual machine (VM) compute host. The image used to launch the instance determines its
operating system and other software. The shape specified during the launch process determines the number
of CPUs and memory allocated to the instance.
instance wallet
An Autonomous Database instance wallet contains only credentials and keys for a single database instance.
internet gateway
An optional virtual router that you can add to your VCN. It provides a path for network traffic between your
VCN and the internet.
interval (Monitoring service)
The time window used to convert the given set of raw data points. Example: 5 minutes
IPSec connection
The secure connection between a dynamic routing gateway (DRG) and customer-premises equipment (CPE),
consisting of multiple IPSec tunnels. The IPSec connection is one of the components forming a site-to-site
VPN between a virtual cloud network (VCN) and your on-premises network.
IPv6
An object that contains an IPv6 address and related properties. Currently IPv6 addressing is supported only
in the US Government Cloud. Only instances in IPv6-enabled VCNs and IPv6-enabled subnets can have
IPv6 addresses.
Glossary
IQN
A unique ID assigned to an iSCSI device. Used when connecting a volume to an instance.
iSCSI
A TCP/IP based standard used for communication between a volume and attached instance.
iSCSI Qualified Name
A unique ID assigned to an iSCSI device. Used when connecting a volume to an instance.
K
key pair
A security mechanism consisting of a public key and a private key. Required (for example) for Secure Shell
(SSH) access to an instance.
L
listener
An entity that checks for incoming traffic on the load balancer's public floating IP address.
local peering gateway
A component on a VCN for routing traffic to a locally peered VCN. "Local" peering means the two VCNs
are in the same region. Compare with a remote peering connection.
local VCN peering
The process of connecting two VCNs in the same region so that their resources can communicate without
routing the traffic over the internet or through your on-premises network.
LPG
A component on a VCN for routing traffic to a locally peered VCN. "Local" peering means the two VCNs
are in the same region. Compare with a remote peering connection.
M
message (Notifications and Monitoring services)
An alert published to all subscriptions in the specified topic. Each message is delivered at least once per
subscription.
metric
(Monitoring service) A measurement related to health, capacity, or performance of a given resource.
Example: CpuUtilization
metric definition (Monitoring service)
A set of references, qualifiers, and other information provided by a metric namespace for a given metric.
metric namespace (Monitoring service)
Indicator of the resource, service, or application that emits the metric. Provided in the metric definition.
Example: oci_computeagent
metric stream (Monitoring service)
An individual set of aggregated data for a metric. Typically specific to a resource.
Glossary
migration (Application Migration)

The end-to-end workflow of moving an application from a source environment to Oracle Cloud
Infrastructure.
Monitoring Query Language (Monitoring service)
The syntax used for metric and alarm queries.
Mount Point
A directory from which a client may access a remote File Storage Service file system.
Mount Target
An NFS endpoint that allows a file system to be accessed by clients.
MQL (Monitoring service)
Monitoring Query Language. The syntax used for metric and alarm queries. In the Console, MQL syntax of
queries is displayed in Advanced Mode.
N
NAT gateway
An optional virtual router that you can add to your VCN to perform Network Address Translation (NAT).
A NAT gateway gives cloud resources without public IP addresses access to the internet without exposing
those resources to incoming internet connections.
network security group
One method for implementing security rules in a VCN. A network security group consists of a set of
resources (VNICs or resources with VNICs) and security rules that apply to those resources. See also
security rules and security lists.
network source
A group of IP addresses that can be used in policy to restrict access.
notification destination (Monitoring service)
Protocol and other details for sending messages when the alarm transitions to another state, such as from
"OK" to "FIRING."
NSG
One method for implementing security rules in a VCN. A network security group consists of a set of
resources (VNICs or resources with VNICs) and security rules that apply to those resources. See also
security rules and security lists.
O
object
Any type of data, regardless of content type, is stored as an object. The object is composed of the object itself
and metadata about the object. Each object is stored in a bucket.
OCID
An Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID). This ID is included as part of the
resource's information in both the Console and API.
one-time password
A single-use Console password that Oracle assigns to a new user, or to an existing user who requested a
password reset.
Glossary
Oracle Cloud Identifier

An Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID). This ID is included as part of the
resource's information in both the Console and API.
OTP
A single-use Console password that Oracle assigns to a new user, or to an existing user who requested a
password reset.
P
policy
An IAM document that specifies who has what type of access to your resources. It is used in different ways:
to mean an individual statement written in the policy language; to mean a collection of statements in a single,
named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall
body of policies your organization uses to control access to resources.
policy statement
Policies can contain one or more individual statements. Each statement gives a group a certain type of access
to certain resources in a particular compartment.
primary IP
The private IP that is automatically created and assigned to a VNIC during creation.
primary VNIC
The VNIC that is automatically created and attached to an instance during launch.
private IP
An object that contains a private IPv4 address and related properties such as a hostname for DNS. Each
instance automatically comes with a primary private IP, and you can add secondary ones.
private peering
One of the ways to use FastConnect. Private peering lets you extend your existing infrastructure into a virtual
cloud network (VCN) in Oracle Cloud Infrastructure (for example, to implement a hybrid cloud, or a lift and
shift scenario). Communication across the connection is with IPv4 private addresses (typically RFC 1918).
private subnet
A subnet in which instances are not allowed to have public IP addresses
private virtual circuit
A FastConnect virtual circuit that supports private peering.
public IP
An object that contains a public IP address and related properties. You control whether each private IP on an
instance has an assigned public IP. There are two types: reserved public IPs and ephemeral public IPs.
public peering
One of the way to use FastConnect. Public peering lets your on-premises network access public services
in Oracle Cloud Infrastructure without using the internet. For example, Object Storage, the Oracle Cloud
Infrastructure Console and APIs, or public load balancers in your VCN. Communication across the
connection is with IPv4 public IP addresses. Without FastConnect, the traffic destined for public IP addresses
would be routed over the internet. With FastConnect, that traffic goes over your private physical connection.
public subnet
A subnet in which instances are allowed to have public IP addresses. When you launch an instance in a
public subnet, you specify whether the instance should have a public IP address.
Glossary
public virtual circuit

A FastConnect virtual circuit that supports public peering.
Q
query (Monitoring service)
The expression to evaluate for returning aggregated data. A valid query includes a metric, statistic, and
interval. In the Console, you can view a query in Basic Mode or Advanced Mode. The latter displays the
Monitoring Query Language (MQL) syntax.
R
realm
A logical collection of regions. Realms are isolated from each other and do not share any data. Your tenancy
exists in a single realm and can access the regions that belong to that realm.
region
A collection of availability domains located in a single geographic location.
regional subnet
A subnet that spans all availability domains (ADs) in the region. Oracle recommends using regional subnets
because they are more flexible and make it easier to implement failover across ADs. Compare with AD-
specific subnets.
regional wallet
An Autonomous Database regional wallet contains credentials and keys for all Autonomous Databases in a
specified region.
remote peering connection
A component on a dynamic routing gateway (DRG) for routing traffic to a remotely peered VCN. "Remote"
peering means the two VCNs are in different regions. Compare with a local peering gateway.
remote VCN peering
The process of connecting two VCNs in different regions so that their resources can communicate without
routing their traffic over the internet or through your on-premises network.
reserved public IP
A public IP address (and related properties) that you create in your tenancy and assign to your instances in a
given region as you like. It persists in your tenancy until you delete it. It can be assigned to any private IP on
a given VNIC, not just the primary private IP. Compare with ephemeral private IP.
resolution (Monitoring service)
The period between time windows, or the regularity at which time windows shift. Example: 1 minute
resource
The cloud objects that your company's employees create and use when interacting with Oracle Cloud
Infrastructure.
route table
Virtual route table for your VCN that provides mapping for the traffic from subnets via gateways to external
destinations.
RPC
A component on a dynamic routing gateway (DRG) for routing traffic to a remotely peered VCN. "Remote"
peering means the two VCNs are in different regions. Compare with a local peering gateway.
Glossary
S
secondary IP address
An additional private IP you've added to a VNIC on an instance. Each VNIC automatically comes with a
primary private IP that cannot be removed.
secondary VNIC
An additional VNIC you've added to an instance. Each instance automatically comes with a primary VNIC
that cannot be removed.
security list
One method for implementing security rules in a VCN. A security list consists of security rules that apply to
all resources in any subnet that uses the security list. See also security rules and network security groups.
security rule
Virtual firewall rules for your VCN. Each security rule specifies a type of ingress or egress traffic allowed in
or out of a resource or VNIC. Also see network security groups and security lists.
service gateway
An optional virtual router that you can add to your VCN. The gateway enables on-premises hosts or VCN
hosts to privately access Oracle services (such as Object Storage and Autonomous Database) without
exposing the resources to the public internet.
shape
A template that determines the number of CPUs, amount of memory, and other resources that are allocated to
an instance.
source (Application Migration)
The environment from which the application is being migrated.
statement
Policies can contain one or more individual statements. Each statement gives a group a certain type of access
to certain resources in a particular compartment.
statistic
The aggregation function applied to the given set of raw data points. Example: SUM
subnet
Subdivision of your VCN used to separate your network into multiple smaller, distinct networks.
subscription (Notifications service)
An endpoint for a topic; typically a URL or email address. Published messages are sent to each subscription
for a topic.
suppression (Monitoring service)
A configuration to avoid publishing messages during the specified time range. Useful for suspending alarm
notifications during system maintenance.
Swift password
(Deprecated. Use an auth token to authenticate with your Swift client.) Swift is the OpenStack object store
service. A Swift password enables you to use an existing Swift client with Oracle Cloud Infrastructure Object
Storage.
Glossary
T
tenancy
The root compartment that contains all of your organization's compartments and other Oracle Cloud
Infrastructure cloud resources.
tenant
The name assigned to a particular company's or organization's overall environment. Users provide their
tenant when signing in to the Console.
Term
Terms are the actual definitions of business concepts as agreed upon by different business stakeholders in
your company. You use terms to organize your data entities and attributes.
topic (Notifications service)
A communication channel for sending messages to the subscriptions in the topic.
transit routing
A network setup in which your on-premises network uses a connected virtual cloud network (VCN) to reach
Oracle resources or services beyond that VCN. You connect the on-premises network to the VCN with a
FastConnect private virtual circuit or VPN Connect, and then configure the VCN routing so that traffic
transits through the VCN to its destination beyond the VCN. You can use transit routing to access multiple
VCNs from your on-premises network over a single FastConnect or VPN Connect. Or you can use it to give
your on-premises network private access to Oracle services so that on-premises hosts use their private IP
addresses and the traffic does not go over the internet.
trigger rule (Monitoring service)
The condition that must be met for the alarm to be in the firing state. A trigger rule can be based on a
threshold or absence of a metric.
U
user
An individual employee or system that needs to manage or use your company's Oracle Cloud Infrastructure
resources.
V
VCN
your instance runs.
virtual circuit
Used with Oracle Cloud Infrastructure FastConnect. An isolated network path that runs over one or more
physical network connections to provide a single, logical connection between the edge of your existing
network and Oracle Cloud Infrastructure.
virtual cloud network
your instance runs.
virtual machine
A software-based emulation of a full computer that runs within a physical host computer.
Glossary
virtual network interface card

A VNIC enables an instance to connect to a VCN and determines how the instance connects with endpoints
inside and outside the VCN. Each instance automatically comes with a primary VNIC, and you can add
secondary ones. Other types of cloud resources also automatically get a VNIC upon creation (examples: load
balancers, DB systems).
VM
A software-based emulation of a full computer that runs within a physical host computer.
VNIC
A VNIC enables an instance to connect to a VCN and determines how the instance connects with endpoints
inside and outside the VCN. Each instance automatically comes with a primary VNIC, and you can add
secondary ones. Other types of cloud resources also automatically get a VNIC upon creation (examples: load
balancers, DB systems).
volume
A detachable block storage device that allows you to dynamically expand the storage capacity of an instance.
W
work request
An object that reports on the current state of an asynchronous service request.
Release Notes
Release Notes
You can find the Oracle Cloud Infrastructure Release Notes online.
Release Notes

Rover User Guide

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Rover User Guide

Hochgeladen von

Copyright:

Verfügbare Formate

Roving Edge Infrastructure

Developer and User Guide

Chapter 2 Getting Started......................................................................................16

Chapter 3 Ordering and Management................................................................. 32

Chapter 4 On-Device Services............................................................................... 50

Stopping Data Sync Tasks................................................................................................................... 117

Overview of Oracle Roving Edge Infrastructure

Oracle Cloud Infrastructure Requirements

Differences from Oracle Cloud Infrastructure

Roving Edge Infrastructure Concepts

Roving Edge Infrastructure

Identity and Access

Compute Virtual Machine

Accessing Roving Edge Infrastructure

Oracle Cloud Infrastructure Console

Roving Edge Device Console

Command Line Interface

Minimum Required CLI Version

Determining CLI Versions

Updating Your Hosts File

Installing the CLI

Using the CLI

oci os bucket create --name MyBucket

Accessing Command Line Interface Help

oci os bucket --help

Allowing Access to Roving Edge Infrastructure Resources

allow group <group> to manage|use|read|inspect rover-family in

The following access options apply:

allow group rover-admins to manage rover-family in compartment finance

allow group rover-admins to manage rover-nodes in compartment finance

allow group rover-admins to manage rover-clusters in compartment finance

allow service rover to read object-family in compartment finance

Enabling Data Loading to Read Buckets and Objects in your Compartments

Grant this dynamic-group a policy to be able to read/write to buckets, for example:

allow dyanmic-group roving-edge-nodes to manage object-family in compartment

Creating a Node Resource

3. Click Create Node.

Attaching a Workload for a Node

7. Provide the following information:

Creating a Cluster Resource

8. Provide the following information:

Attaching a Workload for a Cluster

8. Click Attach Workload.

Determining Device Storage Capacity

Viewing Your Request Status

How Oracle Provisions Your Request

Receiving and Inspecting Devices

Do not connect or further handle a RED you feel is damaged, compromised,

Setting Up Terminal Emulation

Connecting Devices to Your Network

1. Connect to the Oracle Cloud Infrastructure Console for your tenancy.

Accessing the RED Console

3. Enter the following:

Creating a Virtual Cloud Network

4. Enter the following:

3. Click Import Image.

Viewing Activity Logs

Creating and Launching Instances

3. Complete the following:

Creating a Block Volume

6. Click Create Block Volume.

Attaching the Block Volume

Managing Files Using Object Storage