GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
If budgets are stretched, Hyper-V is a very cost effective solution. Any veteran MS Windows administrators will have little issue in getting to grips with this. If you are familiar with VMware solutions, then you may find Hyper-V a little frustrating as it does lack some of the functionality of those products, however nothing that will prevent you from managing your virtual workloads and estate. Since rolling out Hyper-V 2019 we have had no real issues with it; ESXi seemed to have more issues and was less forgiving with hardware compatibility.
Easy to use GUI - very easy for someone with sufficient Windows experience - not necessarily a system administrator.
Provisioning VMs with different OSes - we mostly rely on different flavors of Windows Server, but having a few *nix distributions was not that difficult.
Managing virtual networks - we usually have 1 or 2 VLANs for our business purposes, but we are happy with the outcomes.
The only issue I have with Hyper-V is I am unable to use Veeam on my Windows 2016 Server to backup my FreeBSD HAProxy VM.
There is some sort of checkpoint issue that I have been unable to figure out, but it works just fine on my Windows 2012 Servers. I do believe this is a Microsoft issue and not a Veeam issue though.
Another thing that could be useful that Hyper-V does not have would be some sort of GUI that shows the status of all the VM's on a given server to help us manage them easier and know what is going on. However, I do have Zabbix for this and that does a good job at monitoring all my servers.
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
Cheap and easy is the name of the game. It has great support, it doesn't require additional licenses, it works the same if it is a cluster or stand-alone, and all the servers can be centrally managed from a system center virtual machine manager server, even when located at remote sites.
It is very easy to configure new virtual machines and manage them. But you have to use different interfaces to perform various tasks. Especially as soon as it comes to clustering you have to use at least two different interfaces (Hyper-V Manager and Failover-Cluster Manager) to perform all necessary tasks. The newly released Windows Admin Center is a way into the right direction to get all management tasks into one single interface.
In the past 2 years our Hyper-V servers have only had a handful of instances where the VM's on them were unreachable and the physical Hyper-V server had to be restarted. One time this was due to a RAM issue with the physical box and was resolved when we stopped using dynamic memory in Hyper-V. The other times were after updates were installed and the physical box was not restarted after the updates were installed.
Hyper-V itself works quickly and rarely gave performance issues but this can be more attributed to the physical server specifications that the actual Hyper-V software in my opinion as Hyper-V technically just utilizes config files such as xml, and a data drive file (VHD, VHDX, etc) to perform its' duties.
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
Hyper-V is greatly supported by techs around the world. There are tons of forums, help websites and individuals ready to answer questions. I've never needed to contact Microsoft for help...because help is so easy to find out there. Do a search online for anything related to Hyper-V and you will certainly find an article with spelled out steps on how to do what you are looking to do.
We had in person training from a third party and while it was very in depth it was at a beginner's level and by the time we received the training we had advanced past this level so it was monotonous and redundant at that point. It was good training though and would have provided a solid foundation for learning the rest of Hyper-V had I had it from the beginning.
The training was easy to read and find. There were good examples in the training and it is plentiful if you use third party resources also. It is not perfect as sometimes you may have a specific question and have to spend time learning or in the rare case you get an error you might have to research that error code which could have multiple causes.
initial configuration of hyper-v is intuitive to anyone familiar with windows and roles for basic items like single server deployments, storage and basic networking. the majority of the problems were with implementing advanced features like high availability and more complex networking. There is a lot of documentation on how to do it but it is not seamless, even to experienced virtualization professionals.
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different. The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy. It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
VMware is the pioneer of virtualization but when you compare it with Hyper-V, VMware lacks the flexibility of hardware customization and configuration options Hyper-V has also GPU virtualization still not adequate for both platforms. VMware has better graphical interface and control options for virtual machines. Another advantage VMware has is it does not need a dedicated os GUI base installation only needs small resources and can easily install on any host.
Nothing is perfect but Hyper-V does a great job of showing the necessary data to users to ensure that there is enough resources to perform essential functions. You can also select what fields show on the management console which is helpful for a quick glance. There are notifications that can be set up and if things go unnoticed and a Hyper-V server runs out of a resource it will safely and quickly shut down the VM's it needs to in order to ensure no Hardware failure or unnecessary data loss.
Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
Hyper-V has provided for an extremely cost-effective virtual environment with disaster recovery. For the size of our business, it's all we need to ensure our desired level of continuity of services and protection against hardware failures.
Since we are a Windows shop, deploying Hyper-V means we don't have the added cost of a hypervisor, since it's included in the cost of the Windows Server license. It's all we needed to achieve our goal of running all our virtual machines on a single server with another, less expensive server on tap for replication and failover.
We wanted easy deployment and management with disaster recovery while having the ability to leverage our years of Windows SysAdmin experience. Hyper-V fit the bill.
