VM Installs & RServer Planning
The progress today has seen the separation of the setup processes into pre-deployment (before the relevant web app or API instances and their containers), during and then post-deployment. And the first, VM round of testing has been done on some more of the tools that I've been learning about, including things like rkhunter, apparmor and auditd.
That last one, auditd, is a linux utility that basically monitors events related to files and access, and creates logs for the particular VM. You'll notice that in the top-left of the larger screenshot above is a mention of the potential volume of these logs and their content when we start dealing with more than just a few VM's or local servers. The company that produced that information makes the Sematext tool highlighted, which is designed to run centrally and gather all the logs so they can be manually analysed.
The important point with something like that for me though is how much time and effort would be spent by highly trained professionals just to sort through the info, decide what might have been due to regular (known) internal activity, and what may warrant their attention, when they could be doing something more important with their skills. It's this kind of thing that the planned RServer will help to automate. It will become even more important once the event driven architecture and system analytics start up.
Good learning and progress made, but... like... sheesh 🙂
Stay awesome,
EMH
HOW MOOVPAD IS BEING BUILT
For the overview of how MOOVPAD apps are being developed, the reasoning behind particular decisions during development, policies, and more in relation to all the technical things, please see the link to the left.
This will be an ongoing work in progress, and will always be linked to the bottom of each upcoming Blog post.