btzq opened a new issue, #9041:
URL: https://github.com/apache/cloudstack/issues/9041
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Feature Idea
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
Instance Lifecycle
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
N/A
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
As an Admin, if i have a need to use Instance Lifecycle Operations, 95% of
the time, it is for a group of VMs with similar natures.
Right now, the implementation of the 'Schedule Lifecycle Operations' feature
is done on a per vm basis.
This means, user needs to go to each VM individually, and configure a
scheduler. In this case, if i have 100 VMs that needs to have a scheduled
restart, id have to manually configure it 100 times, the same settings.
Its because of this, i personally use Ansible + Semaphore with a cron job to
achieve this, and not the schedule feature in cloudstack.
As a feature request, i would like to request to enhance VMs in a 'Instance
Group' to be allowed to share the same scheduled job. That way, as a user, it
would be much more easier to use, manage and troubleshoot.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
None
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
Able to Bulk Operate a VM Schedule job using Instance Groups
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
User needs to go to each VM individually, and configure a scheduler
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
