If you are one of those organisations that run any sort of middleware like JBoss / Wildfly, WebLogic, Tomcat, WebSphere, etc. (either on-prem, IaaS, EC2, Azure, wherever) you will have invested in a Continuous Integration/Continuous Delivery tool to support your development and operations. And if you have, there’s a good chance this includes Jenkins.
Philip Leaper, a Talos product developer for Tech Data chats to Ajay Amrite about developing Talos toolkits.
Talos is a really effective tool for managing middleware configurations for WebSphere Application Server, Tomcat, WildFly, F5 Big IP, and many more. It is also a framework that can be built upon and extended by anyone who sees an opportunity to create something that adds value to their customers and others in the software development community.
What is meant by hybrid cloud?
A hybrid cloud is an infrastructure solution that combines any of; on-premise physical machines, on-premise private cloud and public cloud elements. For example you might use RedHat virtual machines provided by both an on-premise VMWare vSphere and also virtual images from Amazon Web Services. There are some permutations which can allow a user to define setup criteria, in order to short-cut the setup process, but essentially these are all just ways of creating machines to form part of your infrastructure. As has been said before “there is no cloud, it’s just someone else’s computer”.
DevOps – current state of play
The most important thing in development projects is to get going quickly, both in terms of getting to market (before someone else does with a competing idea) and getting fingers on the keyboard. All too often a good business idea or opportunity is missed because the infrastructure is not ready to support the product – or even the development of the product. The agile method (the development approach of choice for most modern projects) tells us “release early, release often”, and while the methodology and Project Management governing it goes a certain way toward enforcing this approach, it can’t be achieved without tools and a certain infrastructure type. Developers have for a long time had automated build and deploy, unit testing, performance testing and feedback into the next iteration of development (e.g. did your last commit break anything? Did it slow the system down? Does it provide the functionality it is supposed to) – and for a long time (even now in a lot of cases) this was supported by a team of ‘Ops Guys’ whose job it was to make sure that the infrastructure could keep up – with no such diligent approach to managing infrastructure changes.