{"id":3548,"date":"2016-12-13T19:49:18","date_gmt":"2016-12-13T18:49:18","guid":{"rendered":"https:\/\/www.devco.net\/?p=3548"},"modified":"2016-12-13T19:49:18","modified_gmt":"2016-12-13T18:49:18","slug":"an-update-on-my-choria-project","status":"publish","type":"post","link":"https:\/\/www.devco.net\/archives\/2016\/12\/13\/an-update-on-my-choria-project.php","title":{"rendered":"An update on my Choria project"},"content":{"rendered":"

Some time ago I mentioned that I am working on improving the MCollective Deployment story<\/a>.<\/p>\n

I started a project called Choria<\/a> that aimed to massively improve the deployment UX and yield a secure and stable MCollective setup for those using Puppet 4.<\/p>\n

The aim is to make installation quick and secure, towards that it seems a common end to end install from scratch by someone new to project using a clustered NATS setup can take less than a hour, this is a huge improvement.<\/p>\n

Further I’ve had really good user feedback, especially around NATS. One user reports 2000 nodes on a single NATS server consuming 300MB RAM and it being very performant, much more so than the previous setup.<\/p>\n

It’s been a few months, this is whats changed:<\/p>\n