ClusterLabs / ClusterLabs/striker
Have anvil-safe-stop shut down the servers in the reverse of their start order
Open
enhancement
Low Priority Issue
Pre v2.1
- Dominant language
- Perl
- Stars
- 27
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the anvil-safe-stop entry point and the code that records or performs server startup. Trace the current shutdown sequence and identify how its order is represented. Done means the servers shut down in the reverse of their start order, with the relevant existing checks or tests passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100