Jenkins is an open source automation server. Jenkins provides hundreds of plugins to support building, deploying and automating any project. As an extensible automation server, Jenkins can be used as a simple CI server or turned into a continuous delivery hub for any project.
N/A
SolarWinds Virtualization Manager (VMAN)
Score 10.0 out of 10
N/A
SolarWinds® Virtualization Manager (VMAN) is a tool for monitoring, performance management, capacity planning and optimization for on-premises or cloud-based virtual environments. It also integrates with other SolarWinds products.
Jenkins is a highly customizable CI/CD tool with excellent community support. One can use Jenkins to build and deploy monolith services to microservices with ease. It can handle multiple "builds" per agent simultaneously, but the process can be resource hungry, and you need some impressive specs server for that. With Jenkins, you can automate almost any task. Also, as it is an open source, we can save a load of money by not spending on enterprise CI/CD tools.
On the whole, Solarwinds Virtualization Manager (VMAN) is an excellent product which gives us a single point to monitor our virtual environment. After our initial trial I was sold on the product and what it had to offer. Immediately after implementing VMAN, we were able to spot virtual machines with old snapshots which were never deleted and no longer needed, we could spot virtual machines which either had over allocated resources or under allocated resources meaning we could make changes and fine tune them for best performance. We could also monitor virtual machine latency, IOPS, and show us where our bottlenecks were.
Automated Builds: Jenkins is configured to monitor the version control system for new pull requests. Once a pull request is created, Jenkins automatically triggers a build process. It checks out the code, compiles it, and performs any necessary build steps specified in the configuration.
Unit Testing: Jenkins runs the suite of unit tests defined for the project. These tests verify the functionality of individual components and catch any regressions or errors. If any unit tests fail, Jenkins marks the build as unsuccessful, and the developer is notified to fix the issues.
Code Analysis: Jenkins integrates with code analysis tools like SonarQube or Checkstyle. It analyzes the code for quality, adherence to coding standards, and potential bugs or vulnerabilities. The results are reported back to the developer and the product review team for further inspection.
I created custom dashboards, to view the different elements of the virtual environment. For example, you can view the number of online VMs and those off, or disconnected. You can also choose to see the status of every virtual cluster, the storage disk usage on every VM, the RAM usage, CPU usage.
I used this application to see the growth of virtual memory in each cluster and accordingly do forecasting for future growth. A capacity planner included in this application would help in doing accurate estimations and setting a future upgrade budget.
Another powerful tool was the customized reports, where i could generate reports on any element of the VM or cluster. Reports can be exported to Excel or PDF and are very useful for sharing information with colleagues and management.
Alerts can be customized. For example, you can set a rule to get an email alert if any virtual server RAM usage exceeds 85% and send a text message if RAM usage exceeds 90% for more than 10 minutes.
We did have issues during the setup, with successfully connecting to some of our hosts and vCenters and we found support were just sending us back to articles we had already read, it was also taking long periods before getting a response. The issue is still ongoing, in fact.
We have a certain buy-in as we have made a lot of integrations and useful tools around jenkins, so it would cost us quite some time to change to another tool. Besides that, it is very versatile, and once you have things set up, it feels unnecessary to change tool. It is also a plus that it is open source.
Currently, there is no other tool that gives us what we need to monitor a geographically disperse environment with multiple non-related instances of VM clusters. In addition, the level of reporting, historical data trending, and alerting that VMAN provides is essential for our business process. Lastly, the effort to customize and set up any monitoring system is not trivial. This makes switching to any other product very difficult without being able to clearly demonstrate a ROI.
Jenkins streamlines development and provides end to end automated integration and deployment. It even supports Docker and Kubernetes using which container instances can be managed effectively. It is easy to add documentation and apply role based access to files and services using Jenkins giving full control to the users. Any deviation can be easily tracked using the audit logs.
SolarWinds VMAN is easy to use for everyone. When I say everyone which literally means anyone e.g. Virtualization Environment SME, Consultant, Support Team, Management Officers etc. Anyone who have worked on IT technologies could easily deploy SolarWinds by reading videos, Thwack posts or Virtual Classrooms (Custom Success Centers) - this makes this application easy to operation and for maintenance support is always there.
No, when we integrated this with GitHub, it becomes more easy and smart to manage and control our workforce. Our distributed workforce is now streamlined to a single bucket. All of our codes and production outputs are now automatically synced with all the workers. There are many cases when our in-house team makes changes in the release, our remote workers make another release with other environment variables. So it is better to get all of the work in control.
As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
SolarWinds gives good support. I have never had a time when i was working through a support case where I did not get the support I needed for the required issues to be resolved. I have always had resolutions from SolarWinds support. They are top notch. Issues once had are no more.
It is worth well the time to setup Jenkins in a docker container. It is also well worth to take the time to move any "Jenkins configuration" into Jenkinsfiles and not take shortcuts.
Its really the best product on the market for someone looking to have total control over their VM environment. anyone interested should download a demo and try it, I know you will buy it after you do. It changing the way you have to manage on a daily basis
Overall, Jenkins is the easiest platform for someone who has no experience to come in and use effectively. We can get a junior engineer into Jenkins, give them access, and point them in the right direction with minimal hand-holding. The competing products I have used (TravisCI/GitLab/Azure) provide other options but can obfuscate the process due to the lack of straightforward simplicity. In other areas (capability, power, customization), Jenkins keeps up with the competition and, in some areas, like customization, exceeds others.
The operation began using Nagios XI, after a year of use, and based on the results obtained, we realized that what our client wanted was not fully met. Our client asked us to use WhatsUp, however, SolarWinds covered in a more efficient way what was required by our client (IT) and even more.
VMAN has been used for reports provided to executive-level meetings. These reports showed our growth patterns, allowing for easier decisions on purchasing additional hardware.
VMAN has provided a positive impact on allowing for near real-time monitoring of resources, able to pinpoint when services are using more memory than expected, not running at all, or other options as defined.
VMAN was purchased to help monitor our VMware platform, the added abilities for AWS allowed us to migrate clients from on-prem to cloud-based with the same views.
