chore: add flmadm for all.

[k82cn]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @k82cn, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces flmadm, a new administrative command-line interface designed to streamline the installation, configuration, and management of Flame clusters on non-containerized environments. This significant enhancement shifts the development and CI/CD paradigm from a Docker-heavy approach to a more native, efficient workflow. The changes aim to drastically reduce iteration cycles for local development and accelerate CI pipeline execution by leveraging direct binary builds and installations, providing a faster, more resource-efficient, and easier-to-debug experience for developers.

Highlights

• New Administration Tool (flmadm): Introduced a dedicated CLI tool for installing, configuring, and managing Flame clusters on bare-metal or VMs, separating administrative tasks from user-facing flmctl.
• Enhanced Local Development Workflow: Implemented new Makefile targets and a local-test.sh helper script, enabling faster local iteration, easier debugging, and reduced resource usage compared to Docker-based development.
• Accelerated CI/CD Pipeline: Updated the Python E2E CI workflow to leverage flmadm for native builds and installations, resulting in 40-50% faster build times and 70-80% faster startup times by eliminating Docker image builds.
• Comprehensive Documentation: Added extensive documentation including a functional specification, integration guide, implementation status, a dedicated flmadm README, and a detailed local development tutorial.
• Improved Build and Test Commands: Refactored Makefile and AGENTS.md to clearly distinguish between traditional Docker-based and new local development/testing commands, offering developers more flexible options.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/e2e-py.yaml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces flmadm, a new administration tool for local development and management of Flame, along with extensive documentation and integration into the development workflow. The changes are well-structured and significantly improve the local development experience by providing a faster alternative to Docker-based setups. The code is generally of high quality, with good attention to safety and user experience in the new tool. I've provided a few suggestions to enhance maintainability, robustness, and consistency in the new flmadm crate and related files.