While I believe Community edition will be suitable for most people – I’ve used it for a while -, the reason I went with PRO edition is literally one feature: Hot Linking. Both share the same list of supported images, but the differences are mostly about features. There are two flavors of EVE-NG: Community and PRO. On Bare, it takes roughly 7 minutes from booting to FPC becoming online! Oh and it gets better: vQFX starts in less than 3 minutes for me! That’s huge. Just to give you an example: Booting vMX 17.4R1 over Nested EVE-NG over KVM used to take me ~50mins until everything is up. While you can deploy it over some other platforms (I tested EVE-NG Nested over oVirt), it won’t work as good. It provides the best possible performance for the hosted VMs. I would highly recommend sticking with officially supported deployment options to ensure that you’re getting the best possible performance, as well as support over the community chat.įrom my personal experience: Go for Bare Metal installation. There are many other features that you should definitely check out on their website EVE-NG Deployment OptionsĮVE-NG can be deployed on Bare Metal, as a VM over VMware (ESXi/Workstation/Fusion), or as VM over GCP. You can place the devices, Drag-and-Drop cables to establish connectivity between the devices and select the wanted ports, re-organize and label things, it just does it in a good presentable way that also allows a speedy lab building process.
The User Interface of EVE-NG makes it so that the topology you see does actually work. You have Linux (of course), and you have an increasing list of supported network virtual devices including Juniper, Cisco, F5, and many others. It solves the missing piece of making such labs easier to build, and it does it in an intuitive way.ĮVE-NG supports a whole bunch of disk images to be used when building labs. That’s when EVE-NG came into the picture.Įmulated Virtual Environment – Next Generation (EVE-NG) simplifies the process of running labs containing network devices, and the way to interconnect them with other virtual nodes.
This is also how ESXi does it apparently, and it is a very tedious process that I don’t think I’d want to go through when I want to quickly spin something up to try it. It just didn’t make sense to me that running a back-to-back connection between two devices meant you’d create a bridge and link both VMs on it. Unfortunately, creating such labs over oVirt or even nested over KVM within a linux host can be very tricky and time consuming with lots of moving parts that can easily break it. My problem began when I needed to run labs containing network devices (Juniper vMX, vSRX, Cumulus, VyOS, etc). That’s the spot I realized I needed something fresh that tackles the problem of network devices labs in a smarter way.
I still happily run oVirt today for everything, except Networking Labs. Nested Virtualization and speed to bring VMs up were my two absolutely favorite parts, especially as I started working on Contrail and Openstack. It works well with images, it can be automated, and it does nested virtualization very, very well. ESXi is great, but with time, I kept finding myself doing a lot of the same thing over and over, and although I automated most parts that are repetitive, I felt like I wanted something a bit quicker that just works.įor around two years, oVirt has been my choice for hosting my run-of-the-mill – mostly linux – labs. I’ve went from VMs on my laptop to using XEN on some old machine to VMware ESXi. Here’s a tiny backstory: Looking back into the past five to six years, homelabbing has been one of greatest pleasures to fiddle around and come up with the right setup for whatever I’m learning.
0 kommentar(er)
