Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
Blueprint overview/Introduction

...

MECM Components:

  • Dashboard: Monitoring and Visualisation of platform and applications.Rules management The dashboard provides user interface for the mecm services where edge nodes, APPLCM can be registered and apps can be distributed.
  • Workflow / Policy
  • Database: Postgres db common DB
  • IAAS Adapter
  • Host Selection
  • Catalog: Provides application package management
  • Common DB: Persistent Database.

AppStore:

  • Portal
  • Appstore Services
  • Repo

Developer Platform:

  • Tools
  • Workspace
  • DB: Persistent Database
  • : Provide policy to take action based on analytics like application relocation.
  • Database: Open source PostgreSQL database is being used to store the information, Recommended version is 12.3.
  • IAAS Adapter: Will retreive the query mep capabilities and kpi information from prometheus and also upload config, remove config, instantiate, terminate,and query an application.
  • Host Selection: Repsonbile for selection of host for deployment.
  • Catalog:  Catalog displays the deatils of on hosts and applications.
  • Common DB: Persistent Database.

AppStore:

  • Portal: Portal provides the user interface to publish and launch App applications. and has option for user to comment on the application in comment section and give ratings.
  • Appstore Services: App Store services where uploading an App package and verifies the upload.
  • PGDB : Open source PostgreSQL database is being used to store the information, Recommended version is 12.3.

Developer Platform:

  • Tools: Developer tools are used in Plugin Management, Plugin Life Cycle and grading systems making it more convenient for developers to develop applications and integrate them into the edgegallery platform.
  • Workspace: Developers manage their own Application development process by creating projects or migrating projects. Developers can manage project, app package and test task management.
  • PG DB: PostgreSQL database version 12.2 is being used.

EDGE Node Components:

MEP:

...

  • Front End: AppStore is a market for developers to publish and launch App applications. Appstore FE provides the registration interface to the new user and once login the store home is visible, where user can upload the application package across various industry domains and displays the list of application along with the deatils. User has option to comment on the application in comment section and give ratings. Deleting option is also available in "My App/My APP" section.
  • Appstore Backend: AppStore is a market for developers to publish and launch App applications. After uploading an App package, it must pass the test first. Only the apps that pass the test can be officially launched. Appstore FE provides platform to upload the application package across various industry domains and displays the list of packages.
  • Postgres DB: The AppStore database uses an open source PostgreSQL database, and the recommended version is 12.2. Which Stores app information, application package information and review details of the application.

...

  • aPaaS:
    • Defect Detection Service: This is a service to detect the defect when PCB images provided
    • Object Detection Service: This service can be used by developer app for various Object detection for example Bottle detection and count for Retail store inventory.
  • PaaS:
    • Vault: Vault is a tool for securely accessing secrets. A secret is anything that you want to tightly control access to, such as API keys, passwords, certificates, and more. Vault provides a unified interface to any secret while providing tight access control and recording a detailed audit log.
    • Cert Management: cert-manager is a native Kubernetes certificate management controller. It can help with issuing certificates from a variety of sources, such as Let’s Encrypt, HashiCorp Vault, Venafi, a simple signing key pair, or self signed. It will ensure certificates are valid and up to date, and attempt to renew certificates at a configured time before expiry.
    • OpenEBS: OpenEBS is a Kubernetes native hyperconverged storage solution. OpenEBS consumes the storage (disks, SSDs, cloud volumes, etc) available on the Kubernetes worker nodes to dynamically provision Kubernetes Persistent Volumes.

      OpenEBS can provision different type of Local PV for Stateful Workloads like Cassandra, MongoDB, Elastic, etc that are distributed in nature and have high availiability built into them. Depending on the type of storage attached to your Kubernetes worker nodes, you can select from Dynamic Local PV - Hostpath, Device, ZFS or Rawfile.

    • Velero: Velero is an open source tool to safely backup and restore, perform disaster recovery, and migrate Kubernetes cluster resources and persistent volumes.
    • Influx DB: Time series data base for user applications data.
    • Prometheus Agent: cAdvisor, NodeExporter
  • MEP Services:
    • DNS:  The MEP platform provides the domain name resolution services to the applications deployed in the EdgeGallery MEC, which can be utilized by the device applications in UE. MEC platform receives the DNS configurations from the MEC management, which includes the FQDN(Fully Qualified Domain Name), IP address and related entries. MEC applications can later query or modify the state of these configurations.
    • MEP server: MEP platform services like service registry, discovery, DNS, traffic rules etc.  MEP provides service registration, update, delete, and query related API interfaces. Applications can register, update, delete, and query services through LDVS-MEP.  The service registry provides visibility of the services available on the MEC server. It uses the concept of loose coupling of services, providing flexibility in application deployment. In addition, the service registry presents service availability (status of the service) together with the related interfaces and versions. It is used by applications to discover and locate the end-points for the services they require, and to publish their own service end-point for other applications to use. The access to the service registry is controlled (authenticated and authorised).
  • AppLCM: LCM controller and K8s plugin.  Handles the application life cylce, where lcmController is mainly communicates with K8s plugin to upload config, remove config, instantiate, terminate,and query an application. It also provides APIs to query mep capabilities and kpi information from prometheus.

...