Design, Architecture, and Benefits of the Portal Application Operations Automation Platform

The article introduces the need for a Portal platform to automate application operations, outlining four lifecycle parts: resource management, middleware provisioning, CI/CD pipelines, and monitoring/alerting.

It describes the evolution from OPSDB (built on OpenStack and DNSDB) to a unified Portal that enables OPS, CM, and TC teams to manage hosts, applications, and accounts through a single interface.

Key challenges addressed include fragmented data across multiple systems, lack of developer access to OPS tools, and inaccurate host ownership information.

To solve these, the concept of Appcode is introduced as a universal identifier for any resource (web service, GPU instance, MySQL instance, network device, etc.), enabling consistent attributes like owner, permissions, and billing across systems.

The technical architecture of Portal is built around Appcode, allowing data interconnection among various subsystems.

Portal’s feature set includes:

1. CRUD operations for Appcode.

2. Host request and scaling.

3. Host information view.

4. Host reclamation.

5. Automated Qmonitor configuration.

6. External service navigation.

7. Application deployment.

8. Rich API exposure.

Future outlook envisions expanding Portal’s capabilities and ecosystem.

At the end, a non‑technical announcement about an upcoming React Native conference is included, which is unrelated to the Portal content.