How mike99mac/zlma works
Project Type and Purpose
• The project is a specialized administration platform that integrates a web interface, RESTful API, and numerous command-line utilities. Its main goal is to modernize z/VM administration by replacing legacy interfaces (like 3270 green screens) with modern, browser-based interfaces and command-line operations.
• It is built to manage Linux servers on z/VM, with components for both read-only display (e.g., dashboards, server status) and restricted write operations (e.g., issuing commands, updating configurations).
File Structure Analysis
• Top-level files such as LICENSE, README.md, and RELEASE-NOTES.md indicate that this is a mature, documented project.
• The “srv” directory holds the web-facing elements:
• srv/www/zlma contains the web UI pages and scripts (e.g., home.py, finder.py, restapi.py) that deliver the read-only interface and REST endpoints.
• srv/www/zlmarw houses web scripts for read-write capabilities, including console command interfaces, VIF (Virtual Image Facility) operations, and command modules (e.g., vifcmd.py, vifdisk*.py).
• The “usr/local/sbin” directory contains several command-line tools and utilities (zlma, vif, cpcommand, etc.) that perform heavy lifting for DB updates, command dispatch, and interfacing with external systems.
• Additional configuration and initialization files (e.g., zlma.conf, instzlma, zlmainfo) indicate that the system centralizes its settings and installation procedures.
• Supplementary files like the Apache configuration examples and installation scripts further define the deployment architecture.
Insights from the README
• The README offers a clear overview of key components: a relational database for configuration management data, multiple Linux command-line tools (zlma, vif, console-related commands), a RESTful API, and web interfaces for administration.
• It explains the architectural goals (modern, centralized, simple, well-architected, and secure) and details the responsibilities assigned to the Web UI (presentation), command-line interfaces (processing and backend operations), and REST API (cross-LPAR communication).
• The document describes how SSH is used for remote command execution and how the system’s security is handled via limited privileges and audit-trail logging.