In the last week we had a meeting with two prospects, both of them are in the financial sector with fairly large Engineering organizations. Both these organizations are in the Insurance business and provide a portal for their customers.
These organizations have been in business for many years now and the code base that their Engineering organizations rely on is more than 10 years old. The development cycles mirror most organizations, they work with a main branch that forms the basis of their next release, and parallel development is typically for service packs or bug fixes.
While the development tools being used are the latest – up to date version of Apache / Tomcat, Eclipse, Oracle, the testing methodologies need some updating.
Once the builds are completed, the QA team installs them on the test environment. While one of the organizations is using physical servers for the testing, and the other one uses Virtual instances. The Virtual instances are pretty much used as if they are physical instances, once issued to a developer or a tester, they remain with them for eternity.
Obviously, this setup has led to many problems – some of them
The solution we have proposed, is to first Virtualize the setup, pool all the infrastructure and loan it to individuals only for specific amounts of time, create and use only clean setups for testing and finally, when necessary, provide the ability to reclaim all the infrastructure.
So, is the DevOps or DevTest? DevOps could be Holy Grail or the final destination for Engineering Organizations, but I think before they can get there DevTest is probably the first step. And the solution we have proposed with VMUnify helps these organizations take that first step.
Do you face similar issues in your Engineering Organization? If yes, contact us at email@example.com, we can help you solve it.