Skip to content

Latest commit

 

History

History
68 lines (52 loc) · 3.91 KB

TERMINOLOGY.md

File metadata and controls

68 lines (52 loc) · 3.91 KB

TERMINOLOGY.md - Lexicon of important terms

It is important to know the lexicon and defintions for key terms used in this document. Docker provides software-defined virtual computing environments.

1 - Docker

The key terms when discussing Docker are:

  • container - a software-defined LINUX operating environment
  • image - a Docker container package file
  • tag - an identifier for a Docker container
  • repository - a SaaS that store and retrieve Docker images by tag
  • namespace - an identifier for a repository collection, authentication, and authorization
  • registry - a SaaS for namespace and repository functions

2 - Open Horizon

The Open Horizon edge fabric is based on Docker

  • device - a Docker-compatible computing environment, e.g. RaspberryPi, VirtualBox virtual machine, nVidia Jetson
  • node - a device with Open Horizon edge fabric and exchange credentials
  • service - a composition of one or more Docker containers, including required services
  • pattern - a composition of one or more services which may be deployed to a node
  • exchange - a SaaS for communications, command, and control of nodes
  • organization - a credentialed identifier in the exchange
  • agreement - documentation of a node's services' successful assignation

2.1 - node

Devices with Docker and the Open Horizon software installed and configured properly. For more information on setting up a device please refer to setup/README.md.

2.2 - service

The Open Horizon edge fabric service is an specification of Docker containers with supporting information. Each service is defined in a JSON configuration file that includes identification, description, variables, deployment, and composition information. For more information on building services, please refer to [SERVICE.md][service-md]

2.3 - pattern

A pattern is a composition of one or more service into a package which can be deployed to a node. Patterns are identified by a unique name in the exchange per organization.

2.4 - exchange

An exchange is a network-service that provides communication, command, control, and management functionality for node, service, and pattern. Access to an exchange requires credentials for a registered organization

2.5 - organization

An organization is a collection of exchange artifacts (e.g. node, service, pattern) and associated users with access control to those artifacts.

2.6 - agreement

Documentation of a successful pattern registration; there is one agreement per service in the pattern, including the services' required services.

3 - Architectures

The Go Language specification is used to identify architectures. The following architectures are recognized:

Identifier Description FROM
amd64 AMD/Intel 64-bit - PC or VM multiarch/ubuntu-core:amd64-xenial
arm ARMv7 - Raspberry Pi Model 3B+ multiarch/ubuntu-core:armhf-bionic
arm64 ARMv8 - nVidia Jetson Nano, TX2, Xavier, .. multiarch/ubuntu-core:arm64-bionic
386 Intel 386 - Pentium SSE2+ multiarch/ubuntu-core:i386-xenial
ppc64le PowerPC 64-bit (little endian) - POWER8+ multiarch/ubuntu-core:ppc64el-xenial
mips64le MIPS 64-bit (little endian) - MIPS III+; 2E/2F
ppc64 PowerPC 64-bit (big endian) - POWER8+
mips64 MIPS 64-bit (big endian) - MIPS III+; MIPS64r2
s390x System390 - z196+
mips MIPS (big endian)
mipsle MIPS (little endian)