You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The cluster node template names are fixed to distroName:distroVersion:aerospikeVersion. As such, if creating a template from a custom image, it is named the same as a template from the standard, discovered image. If one requires to create a cluster using a non-standard image, once, this becomes an issue.
Request: provide an ability to create a cluster as a single flow, skipping template creation, if needed. Or alternative provide an option to custom-name templates and use those custom names. (maybe requiring template create followed by cluster create --template-name xxx type approach). Template names would need to show in template list too.
The text was updated successfully, but these errors were encountered:
The cluster node template names are fixed to distroName:distroVersion:aerospikeVersion. As such, if creating a template from a custom image, it is named the same as a template from the standard, discovered image. If one requires to create a cluster using a non-standard image, once, this becomes an issue.
Request: provide an ability to create a cluster as a single flow, skipping template creation, if needed. Or alternative provide an option to custom-name templates and use those custom names. (maybe requiring
template create
followed bycluster create --template-name xxx
type approach). Template names would need to show intemplate list
too.The text was updated successfully, but these errors were encountered: