Concepts of Roving Edge Infrastructure

Describes Roving Edge Infrastructure concepts related to its features and functionality.

Be familiar with these concepts before setting up and using your Roving Edge Infrastructure service and 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 the 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 Device Console: The web browser-based user interface for interacting with your Roving Edge Infrastructure device.

Roving Edge Infrastructure

The following resources and concepts are related to the Roving Edge Infrastructure service and Roving Edge Infrastructure 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.

  • Roving Edge Ultra (Ultra): A single battery-powered Roving Edge Infrastructure device capable of being carried by an individual. Ultra provides a highly-portable and rugged edge computing device you can use in indoor and outdoor environments. The device requires minimal protection from the elements, and is able to operate without consistent access to power. Ultra has less storage and computing capabilities than a traditional RED.

  • 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 or Roving Edge Ultra device. A node can be single, or as part of a cluster. See Roving Edge Device Nodes and Roving Edge Ultra Nodes.

  • Standalone Cluster: The Roving Edge Infrastructure service resource that represents a group of 5 REDs working together in the same environment or network. See Roving Edge Standalone Clusters.

  • Workload: The object storage bucket or compute custom image that is being provisioned from your Oracle Cloud Infrastructure tenancy to your REDs. See the topic for attaching a workload to your particular Roving Edge Infrastructure device node or cluster, for example, Attaching a Workload to Roving Edge Device Node.

  • Data Sync: Transmission of object storage data between buckets on your Roving Edge Infrastructure devices and your Oracle Cloud Infrastructure tenancy. This update allows you to synchronize data between the RED and Oracle Cloud Infrastructure cloud, and perform software updates. See Data Sync Tasks.

  • Device Software Version Management: The process of updating the operating system version of your device¬†to a later version. You can also revert your device software to the previously-installed version. See Device Software Versions.

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 Roving Edge Infrastructure device features and functionality. All users have Administrator privileges. See Users.

  • Group: A collection of users. Features and functionality applied to a group affects all member users. Roving Edge Infrastructure device nodes and clusters only use a single default group. You cannot create more groups. See User Groups for Roving Edge Infrastructure Devices.

  • Policies: A document that specifies who can access which resources, and how. Access is granted at the group and compartment level, which means you can write a policy that gives a group a specific type of access within a specific compartment, or to the tenancy itself. See Policies for Managing Roving Edge Infrastructure.

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 Instances.

  • Image: A template of a virtual hard drive. The image determines the operating system and other software for an instance. See Images.

  • 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 Volumes.

  • 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.

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 Buckets.

  • Object: A file or unstructured data you upload to a bucket. See Objects.

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 Volumes.

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 Networks.

  • 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 Subnets.