Introduction

IEC Type3 mainly focus on Android Application running on edge ARM Cloud architecture with GPU/ vGPU Management. Also, ARM cloud games need to have the basic features of "cloud”, such as flexibility , availability everywhere. Based on cloud infrastructure optimized for android application, providing ARM application services.

This document describes the deployment architecture, construction and use of anbox Android container environment. Describes the environment configuration, code download, build and how to use it

How to use this document

This document provides a general deployment about about the contruction of Android container environment, including pre-installation requirements, installation step, uninstall and troubleshooting.

Deployment Architecture

Open

Pre-Installation Requirements

• Hardware Requirements

ARM Server satisfies the Arm Server Ready certified.

• Software Perequisites

N/A

• Database Perequisites

schema scripts: N/A

• Other Installation Requirements

  • Jump Host Requirements：N/A

  • Network Requirements: N/A

  • Bare Metal Node Requirements ：N/A

  • Execution Requirements (Bare Metal Only) ：N/A

Installation High-Level Overview

• Upstream Deployment Guide

  • Upstream Deployment Key Features ：N/A

  • Special Requirements for Upstream Deployments ：N/A

  • Scenarios and Deploy Settings for Upstream Deployments ：N/A

  • Including Upstream Patches with Deployment：N/A

  • Running： N/A

  • Interacting with Containerized Overcloud： N/A

Verifying the Setup as defined the Akraino validation feature project plus any additional testing specific to the blue print

Developer Guide and Troubleshooting

• Utilization of Images

N/A

• Post-deployment Configuration

N/A

• Debugging Failures 

N/A

• Reporting a Bug

N/A

Uninstall Guide

The following method only uses snap to install Anbox. If you want to delete Anbox from the system, you must first delete snap.

Attention：Remove all data stored in the snapshot from the system:

$ snap remove anbox

After deleting the snapshot, you must also delete the installed kernel modules (if installed):

$ sudo apt install ppa-purge

$ sudo ppa-purge ppa:morphis/anbox-support

Upon completion, Anbox will be removed from your system.

Troubleshooting

• If kernels modules successfully loaded, service is running fine, and yet Anbox won't launch with Application manager service is not running yet. Check for the message No space left on device - Failed to enter cgroup in /var/lib/anbox/logs/container.log, you may be running into see this issue: https://github.com/lxc/lxd/issues/6257

• If container started failed

Before the container is started, session-manager needs to be started on the host to start x, input, adb and other related services, and then the container may started successful.

• To build the Anbox runtime itself there is nothing special to know. but when we use cmake as build system. A few build dependencies need to be present on your host system:

  * libdbus
  * google-mock
  * google-test
  * libboost
  * libboost-filesystem
  * libboost-log
  * libboost-iostreams
  * libboost-program-options
  * libboost-system
  * libboost-test
  * libboost-thread
  * libcap
  * libsystemd
  * mesa (libegl1, libgles2)
  * libglm
  * libsdl2
  * libprotobuf
  * protobuf-compiler
  * python2
  * lxc (>= 3.0)

Maintenance

• Blue Print Package Maintenance

  • Software maintenance： N/A 

  • Hardware maintenance：N/A

• Blue Print Deployment Maintenance (N/A)

Frequently Asked Questions

N/A

License

N/A

References

N/A

Definitions, acronyms and abbreviations

N/A