Custom user data when creating clusters about asgard HOT 2 CLOSED

👍

from asgard.

Your idea sounds perfectly understandable when using the cloud at small to medium scale a few times. However, the restriction on user data creation in Asgard is intentional and carefully considered. We found that providing a blank slate for users to input their own raw user data for each deployment was too error prone to be justified over time. We've had greater cloud stability since removing the user data textarea, because now Asgard requires automation of a step that is too difficult to do correctly consistently. It's up to the Asgard administrator to customize Asgard's user data generation algorithm so that a reliable user data string will be produced for each and every deployment, in a form that is compatible with the AMIs your organization deploys.

Keep in mind that your override of the user data creation system can call out to a service, a database, or a file where you store your user data template, if it's too long to put in the Groovy code. You as the Asgard admin still have total control over how the user data gets written. The important thing is that once you've taught Asgard how you want your user data to be created, your organization's users don't need to try to get manual user data creation right anymore. They can simply deploy repeatedly as often as needed, trusting Asgard to create the user data properly every time, through the consistent formula you've written.

from asgard.