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!
During a recent upgrade exercise in dev of the a2 infra (from 4.2.47 to 4.4.10) we discovered that all chef servers - and PG and OS nodes too - were all offlined at the same time for an upgrade - effectively an outage for client converges.
Is it possible to implement a rolling upgrade for all the components?
Also, during the same exercise it was discovered OS upgrade failed because we needed to include /sbin or /usr/sbin (rhel) in a2ra users PATH, as OS upgrade attempts to execute sysctl command.
Would be helpful to check for this during pre-upgrade checklist and to abort with an helpful message.