-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
100% To Do, 0% In Progress, 0% Done
Feature Overview
...
Goals
We should emphasize ease of use for non-developer users and single pane through ACM UI.
The feature is about adding bulk action capabilities through the ACM UI, enabling users to select a group of resources, cross-clusters, and perform various operations on them efficiently.
The feature should provide:
- Basic actions - Not only for VMs (e.g., power operations, snapshot creation, deletion, cloning, label updates, resource allocation updates, migrations).
- Advanced workflows for customers requiring more complex operations, such as:
- Integrations with external systems (e.g., creating tickets or approvals).
- Scheduling actions for specific times.
- Executing policy-driven custom scripts.
- Be able to run the actions from Perses table panel dashboards and from Search.
This feature will significantly enhance operational efficiency, reduce manual overhead, and offer flexibility to meet diverse customer needs in managing their workloads.
- As a System Admin/SRE , I need the ability to select multiple resources (e.g., VMs, deployments, or pods) and perform bulk operations such as powering them on/off, creating snapshots, or updating configurations to save time and streamline routine tasks.
- As a System Admin/SRE, I need the flexibility to define and customize bulk actions to accommodate complex workflows, such as requiring approval steps, integrating with external ticketing systems, or scheduling operations during predefined maintenance windows, to ensure adherence to organizational policies and operational constraints.
We should consider this could be valuable also in the single cluster use case and perhaps this UI integration can be done as an add-on that can be installed on single clusters as well as ACM.
Proposal document Extend ACM Clusters Resources Management with Ansible Automation Platform stack integration
Requirements
This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.
| Requirement | Notes | isMvp? |
|---|---|---|
| The solution must provide RBAC support | Only users with appropriate permissions should be able to view or run specific bulk actions, ensuring secure and compliant operations. | YES |
| Provide feedback on action status | Users must receive real-time feedback about the status of the actions they triggered, including progress, completion, and error messages if applicable. | YES |
| Track who ran the actions | Log the identity of the user or system initiating the actions for traceability. | YES |
| Track resources targeted by the actions | Record which resources were affected, including their namespace and type (e.g., VMs, deployments). | YES |
| Record the result of each action | Capture whether the action succeeded, failed, or partially succeeded for individual resources in the group. | YES |
| Maintain a history of bulk actions | Provide a view of past bulk actions for inspection, auditing, and troubleshooting purposes. | YES |
| Allow customizable bulk actions | Support the addition of user-defined workflows (e.g., external approvals or custom scripts) that can be integrated as bulk actions in the UI. | NO |
| Support scheduling of actions | Enable users to schedule bulk actions for a specific date and time, especially for maintenance operations. | NO |
| Provide action previews | Allow users to preview the impact of their bulk actions (e.g., list the resources to be affected) before finalizing the operation. | YES |
| Offer filtering and selection capabilities | Allow users to filter resources by criteria such as labels, status, namespace, or type and easily select them for bulk actions. | YES |
| Include confirmation prompts | Display confirmation dialogs before executing bulk actions to prevent accidental operations on critical resources. | YES |
| Support integration with external systems | Allow integration with external ticketing or approval systems (e.g., ServiceNow) to enforce organizational workflows. | NO |
| Provide multi-cluster support | Ensure bulk actions can operate across multiple clusters managed by ACM. | YES |
| Enable rollback for failed actions | Implement rollback mechanisms or suggest recovery options if an action fails midway through execution. | NO |
(Optional) Use Cases
This Section:
- Main success scenarios - high-level user stories
- Alternate flow/scenarios - high-level user stories
- ...
Questions to answer
- ...
Out of Scope
- ...
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
Assumptions
- ...
Customer Considerations
- ...
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)? - Does this feature have a doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content
Strategy. - What concepts do customers need to understand to be successful in
[action]? - How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available. - What is the doc impact (New Content, Updates to existing content, or
Release Note)?
- is related to
-
-
- New
-
- relates to
-
-
- Backlog
-
-
CNV-51648 [cont] Plan Day2 Virtual Machines lifecycle management at scale support with ACM
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
