We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.
We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.
Thanks for collaborating with us!
Within the current deployment configuration of A2HA, the minimum number of nodes needed for an A2HA cluster is 9 systems:
bastion/management nodes: 1
Automate Front-End Nodes: 1
Chef Infra Server Front-End Nodes: 1
ElasticSearch Nodes: 3
PostgreSQL Nodes: 3
The minimum node count requirements can be quite a leap from existing Chef Infra Server ha/backend/tiered deployments and A2HA is intended to be the ultimate replacement for these solutions. It would be greatly helpful to reduce the minimum number of nodes for smaller deployments or distributed environments where multiple Chef Infra Server clusters might be required (such as regional deployments or DMZ deployments).
As an example solution to this, A2HA could allow for colocation of services on the same node, that could reduce the minimum number of nodes from 9 to 4 ( 1 management node and 3 clustered nodes which run services)
I have a customer who have 15 Tiered Chef Infra Server Deployments with 2 FrontEnd and 1 BackEnd Server. So reducing the minimum requirement will be crucial for them as they are one of the top Tier Customer.
Attachments Open full size