Integration and Degradation

Software projects start modestly enough — a general problem statement that we've set out to solve. But then they grow. And grow. Either the problem changes, or our initial assumptions about how to solve it were so flawed that we just that far off in guessing how difficult the problem actually was. How prepared we were with our existing domain knowledge. How difficult it would be to acquire people with the right skills. Its in these situations that we take a software project, experiencing a deficiency of some sort, and start integrating other software components. It is through this exercise of integration that we're introducing unintended consequences of bringing on new software components.

Enomalism 2.1B2 Getting Close

The second beta release of Enomalism 2.1 is coming soon. Several minor fixes and enhancements have been made throughout the system. Several improvements have been made in the REST API including new user control functionality. Permission handling has been greatly improved in several core modules.

Although the stability fixes have been minimal, a couple noteable features have been added to the second beta. First, during the Enomalism installation process, existing libvirt domains will be imported into Enomalism. This means that any existing machines, created by some other means, can be managed by Enomalism.

Second, if the host Enomalism machine is shut down, the VMs running on that host will now remember their state and automatically start when Enomalism starts again.