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 amoeba.yml config file in the app repo would specify a node template and concurrency setting. The deploy tools would automatically provision new nodes based on this template and configure a load balancer accordingly.
The main issue is that the node provision/bootstrap/push process needs to be stable and "trusted" enough to work on a wide scale without manual intervention. It would be useful to also have it autoconfigure a centralized reporting system like mmonit or just rsyslog, so that the sysadmin can easily track down any failures, etc.
The text was updated successfully, but these errors were encountered:
The amoeba.yml config file in the app repo would specify a node template and concurrency setting. The deploy tools would automatically provision new nodes based on this template and configure a load balancer accordingly.
The main issue is that the node provision/bootstrap/push process needs to be stable and "trusted" enough to work on a wide scale without manual intervention. It would be useful to also have it autoconfigure a centralized reporting system like mmonit or just rsyslog, so that the sysadmin can easily track down any failures, etc.
The text was updated successfully, but these errors were encountered: