Virtualization Lab Network Setup / Demo using XCP-NG, UniFi, pfsense and Xen Orchestra

part of the reason I love IT is there is so much technology changing all the time it's so easy Moo always something new to learn new angles for things new software coming out but you need a place to test it all and that's why having your own virtual lab to me is a critical piece of infrastructure if you're in ninety at all and I know a lot of my friends who you know have labs at their home even though they work for a large even some of them working for fortune 100 companies still have a either home setup lab or another office setup somewhere they can build demos or wares now sometimes that's in the cloud sometimes it's physical it kind of depends on where your budget lies running it all in the cloud is kind of cool but there is a fee that can come attached that we have a local lab here in our building that we use for testing software it's high do a lot of the YouTube demos so if you're going to do a little bit of a walkthrough now all this is the compilation of all the things that I've talked about on my channel so I've got videos on how to set these up I'm always can do new versions as new version of software comes out but for the most part if you watched and I can link to any of the videos like how to setup XC PNG or how to setup pfSense or how to set up unify this is putting all that together to build the lab because those are the tools that we used inside of here so I'm going to start with yes it says comcastic craptastic I'm not always a huge fan of Comcast but it's what we have here in our area and that's what feeds our main system pfsense so our lab is both a lab and does have some production units in there for things we run other stuff we run in the cloud but today I'm mostly going to be focusing on all the lab stuff and how it works and how we set things up so in pfsense we have a few VLANs defined by IOT network not that we have much IOT stuff but it's mostly for testing VLAN 69 which is our general retail customer people come in network it's still secured but it is segmented off from other things the storage VLAN is not defined inside a PF sense it's literally just for storage and I'll cover that in a second once the 16 port 10 gig unified switch and then these millions come out to the unify where we define them and then it propagates to the other unifies now I do have this other Network which is not something we're really gonna be covering either but it just exists you know if you see it this is like the production network is tattoo and it goes to an unmanaged switch it's not even a VLAN I didn't want anything shared across it it's strictly for production environment and that's where we keep anything production is on that network it's kind of also a stopgap safety that you can't just swap a VLAN port and end up on our production network somehow by accident or by clicking that's part of the reason I set it up that way and it doesn't need to be in a managed switch because we don't really have but a handful of things that we host ourselves here at our office couple knowledge collections of things that's all separate on there so that's why it's not an unmanaged switch Bri Nass is the back-end storage or the 2xc PNG servers they do have a local storage they do have all the extra storage being on these two devices here mostly this one now is just a backup and this one is a primary where we actually have both an iSCSI and an NFS I have both on there mostly because I've done the testing and proved that they're very within a few clicks of each other and percentage points for speed but it's also fair when people ask questions can I do this with I scuzzy having it already configured in FreeNAS and when I do for NES updates I like to say well they're not things work properly I like to test NFS and I scuzzy every time I do an update so I have virtual machines and storage attached both there and we'll get to how that works in a second now a little bit further down is where we have be lien 10 undefined VLAN studio undefined VLAN studio 200 undefined now undefined means when I create networks that are not defined in PF sense and they're defined dynamically based on whatever I attach to them and basically with a VLAN if you're not familiar with them go back and do some reading but because it's definitely a critical knowledge point to have VLANs in here they allow you to take one physical cable and logically divide that network up into multiple pieces and this is obviously really critical for the lab because I want to be able to take a port on a unify or even a virtual port inside of a virtual machine running XC PNG and be able to dynamically change a network within there with out having to go physically move wires if you want to iterate fast you want to load something up build a demo real quick and attach it I want to be able to do that without thinking much about it in terms of ok which cable goes where and things like that so everything we define with the VLANs and the VLANs and the unifier very easy because we have several unify switches here we define it and it propagates everywhere automatically to the other unified switches so terms unify switches though we have a 24 port unify in the rack the 16 port 10 gig unify in the rack then we have a 24 port unify up front and because we have a larger retail area there's also like a couple unmanaged switches and not really relevant to this talk but they're there just to help propagate the 172 network then we have our office computers plugged into some of the unified switches and we have another unifor unified 24 port POV in the studio area and the reason that's there is so we can easily test things in a studio we kind of do we just built a new studio rack which is kind of to extend the testing so it's easy for me in the studio to define a port that may be attached to a virtual machine on its own network with one of these undefined networks with the studio and we'll show you how that works so there's all the definitions here let's talk about a little bit how it looks do I have a full rack tour but I figured I'd grab a photo real quick this is just the basics of you know here's those sfp+ --is that's how we attach the lab in the back end to freenas and they're all on this defined 10 network that's exclusive for just storage having just a standard storage VLAN that doesn't interact at all means I can trust my storage network for the most part that nothing else can get onto that network so they're defined right here they connect to the free NASA's they connect to the XC PNG this allows me to have back-end access at 10 gig to the storage devices so that's how we define the storage in here and there's that unmanaged switch yes it's a tp-link it was on sale and whatever they work perfectly fine like I said this is the lock it down network so to speak because we have nothing but production stuff on there so nothing else every plugged into this and by the way I know someone's going to point out but you should disable all the other ports yeah but once you have physical access you could move things around pull it out but that's a whole different debate that I don't feel like having right now then over here is the unify switch and everything's plugged in we try to keep things nice and neat and defined if you're wondering while there's labels over here this is because they when we forward over to other patch panels this actually brings you to other patch panels in the building so we redefine what ports they are on those patch panels for a label purposes so that's that you stack a servers like I said you can go in-depth on that on the rack video I'll do that and this is a studio rack I have yet to make a video on it but will be soon I'm waiting for some more parts to come in but this is how we can easily define things on this network well this particular one you box right here is a currently running PF sense but is our lab machine so I can just load whatever I want on it and then we've got an extra network card in here that it just because it looks nicer so I plugged into these ports but there's 0 1 2 & 3 as an IG b 0 IG b 1 and what those are just like in PF sense is what it's running right now those are the network ports as are defined so then I label them inside the unify as 2 defined and I'll get to that when we show how the virtual machines work and how we move the networks around now going back to how they're defined and unify so we don't use a USG like i said we have a EF sense at the head end of the network and having a PF sense at the head under the network means you define V lien only when you create networks so there's two buoys to create networks essentially well more than two but for the purposes you can create like a standard network and if you had a USG this would actually create that extra network on a USG device I don't dislike the u.s. cheese I just find them very basic so if you have a lot of advanced things you want to do the US cheese just kind of fall flat and they just have very basic features or a quality product in terms of we haven't any problems with the ones we've deployed but once you start needing a lot of advanced features they don't really have as much advanced features as I like therefore we use 8ya sense at the head end of our network now when you're defining any VLAN you just find it as VLAN only and we can call this VLAN test and you know come before the name hit save and it automatically propagates to all the other switches and you know we try to label these each one but if I need to you know change a label change anything it's really arbitrary and I like the way they've made it very simple and unify to manage setup configuration of VLANs defining VLANs and in moment I defined them like I said it propagates out to everything so it becomes very simple let's look at the switches themselves as a devices so under topology map you can see how each one of these propagates out in house are connected so starts with that switch in iraq which is fed by the yeah cents box we have then goes into our device we call the air rectangle which is just a beta version sent to us back when it was in testing the Wi-Fi base station XG because it's a beta unit it's not the fold to find one but we've been testing it ever since we did a review of that it's pretty cool Wi-Fi that's what provides our 5g Wi-Fi because we actually have this really old 2.4 only and yes it's only connected at 100 because it's that old and I it just still works so we haven't gotten rid of it and just handles the 5 g and this handles the 2.4 in the network so in this closer to the front of the building this is at the back that's why this one's plugged into the rack and this one's plugged in here but once again those VLANs being defined means as soon as I push it out all those VLAN settings come over here to all the switches now when you're setting up unified switches and setting up the VLANs one of the important aspects is that the interconnects between here so from this one to this one to any of these be set to all let me show you what I mean by that when you're defining ports and unify front unify switch I can actually probably can rename it to be you know front in rack if I wanted to but front unify switch you want the profile to be all so here when you're changing VLANs you can see I have the option I could say well it just goes to the land you want everything and it referred to in his trunk ports you want everything from each switch to be forwarded to the next switch so on and so forth that way as these are defined that's forwarding over there oh this is a point of confusion I've seen a few people have where they go I have a hard time understanding why I can't get this switch to work and I'm like do we see a switch profile when they connect between the switches not set to all this is what gets the VLANs to propagate to everything all the way down to the Wi-Fi and that's an important factor because if I wanted to build something in my lab and create it on its own VLAN like one of those undefined VLANs I then have to forward it over somewhere such as the Wi-Fi where you define VLANs in here or it was specific port on one of the unified switches to get something to plug into that you need to be able to define it at those switches that are maybe two switches down and having all all all travel between switches til it gets to the last port you want then you switch the settings to that and that's where we'll cover like the studio switch because we have a few of them very differently defined here now the studio switch off this out what are the ports this is for a demo I have coming up I didn't get a video done youngness also this one's profile is named little bit differently but here is that lab so if we look back at the photo here we see one two and three at the bottom here well three two one and then they're plugged in and we'll go back over to the switch and we see that they're plugged in here so we can see the definition this one's called Studio lab pfSense land - and if you see the profile says Studio 200 VLAN this one says to do 100 VLAN and this one says VLAN 69 so what that's doing is feeding it VLAN 69 so it's going to have and I'll show you I have pfsense running on that's let's log into it and actually walk through that real quick so if we look at the clients it looks to do lab pfsense and there's the IP address of it so it makes it really easy to find because it knows what IPS are plugged into that port so now we're logged into it it's at 172 1669 144 now let's look at what's defining behind it just to make things a little bit easier I defined two networks land and land - 192 168 101 and 200 dot 1 and they're attached to those Studio VLANs so let's look at that a little bit closer go ahead edit and we've got Studio lab pfSense land 1 and the profile of this particular port has been set to studio 100 V Liam now let's cover a couple things real quick about the VLANs like I said some are defined and some are undefined so if we go over here to my main pfSense the only defined VLANs as I said inside a PF sense that are attached to the land port is 69 and 50 the rest of them are just defined and unified for all my lab usage or my storage usage it's not defined here so it does not need to did you find a PF sense because this particular this is my head end pfSense not my lab 1 is not handling those networks I want those labs to be able to be handled for demonstration purposes in one of my lab PF census so this is the lab pfsense assigned 192 168 100 gonna go DCP server and we see enable DHCP now because the port is not a trunk port I don't need a define of some type of B on inside of here - as far as this system is concerned it's just plugged into a physical port so when we go to interfaces assignments I gb0 when I gb one LAN I G B to LAN to look at the photos their physical ports not VLANs so what you do is define them inside a profile so this particular port means VLAN 100 now because VLAN 100 is to find all the way across all the unifies and allow let's go back over to the XC PNG server this is running as an orchestra now we can find that VLAN port so let's find it over here this is just the list of networks and I defined in these studio 100 VLAN Studio 200 VLAN and all these go over each zero and they pull up the map again so essentially easy arrow is this orange line here they're all the same so all these VLANs 3.0 is the main as in the native land these are the ones to find in side of pfSense the headend one and then these are just the defined ones inside the unified so we defined them but then we've taken these VLAN tag 100 tag 200 and VLAN 10 find them and unify and then to find them again here and here's the VLAN tag 100 tag 200 now I know it seems a little complicated but let's watch this in action once you kind of get the concept that these VLANs all on a shared medium all across all of these we're gonna go over here and look at some of the VMs running then we're gonna go and grab my parrot VM Network so currently my parrot VM is at 192 168 3.25 I call it the dot 3 Network that's the native know VLAN so let's go look at the security again into VLAN settings so dot 3 EC row VLAN 0 as in know VLAN not into puts a 0 in there so that's your native network as they call it then we look down there we're gonna look at the studio one studio 100 connected also to EC row same physical cable and we go over here and we see that we can change the network so we're going to click it let's switch to studio 100 and when you do this because I've got these end tools installed you can swap the networks on the fly like this no need to restart the server and it just lets me know that the network went away and came back look at the IP address and now it's defined as 192 168 100 101 and how does that work so let's follow it all the way back so here's the IP address of it we go over here to the studio lab and we see that interfaces that should be land 1 is the new 100 range over here services DHCP server we see the pair at least right here so it's coming all the way through to this physical box right here and it's following through because that physical box plugged in right here and then defined as Studio William V won't be LAN 100 here comes all the way through so we've now taken that physical port we said that physical port is be Liam 100 and the pfSense hands it off and it pipes all the way back accrue while the same network interface that's carrying other aliens and brings it all the way over to here now a side note about VLANs always to remember they are a shared medium even though we're logically defining all these networks across a one physical cable that does not give it any more than the single gigabit of bandwidth that it's able to do but for lab testing but you're not is worried about bandwidth issues they're really great sometimes you do want to sell to find out networks physically separate due to bandwidth and things like that because the internet want to share the medium if you have high capacity demands or get ten gig networks as you can see we can take something running in the studio pipe it back through the entire unified network and back over to our lab and then have this sitting behind the firewall to do any type so demos with and how this computer is connected there but what about connecting it to something local what about building your own virtual machines and labs there well let's look at that too so we're gonna go over here lab and here's my pfsense lab so we'll go ahead and fire this up but before we do let's figure out where the network interfaces that are there though I've got my VLAN 69 I need to feed it so this is actually going to be the LAN side on this one because if as I set up this pfSense lab demo I did it with the first interface being the LAN side and then two lands in between a LAN of Zen is interesting because what you can define was n server pretty easy to do you can say I want to define this so every thing is only inside a sensor and never leaves it so it has its own internal networks that are referred to as hosts only those are great for sandboxing because they never touch the physical Ethernet adapters on it so you can define as many of those as you want and build labs directly in XenServer without them leaving so if you want to do some more thorough testing or test something more dangerous like some type of spyware or virus stuff that's great because it creates a lab that it can't escape besides the other tools that you give it to escape for example you create a virtual firewall and to find it in there so we'll leave this Atlanta as n and by the way it's defined there's ways to get it to bridge across multiple servers we have it in a one physical server so land of Zen - and land of Zen one are both internal only to that particular server because we have two XE p and g servers and then here's this other VLAN 10 as I call it lab undefined so let's go ahead and fire up pfSense lab 2 now it goes back to seeing no IP record until it boots back up there's a guide you can pretty fine find pretty easily pfSense an XC P&G or pfSense and XenServer there's a couple extra things you can add to get more enhanced XenServer tools inside of the PF sense that way it gets the network interface it's there is a freebsd package for it I'll probably cover it in a different video but you can google it and find there's a github instruction for this now this is booting up like normal just like an EPF sense install I'll go ahead and fast forward this all right so now this one's up and running like I said our wanne is the first network interface so we put it in the 172 network you got to get your internet from somewhere the LAN is defined as 192 168 that's that Lambs N and then we have I actually called it IOT I was doing a demo but it's a dot 10 network so we're going to log into that and this is what it looks like logged into it so on the latest version everything's set up firewall make sure we have a DHCP server we doing like said this is all running virtual we have one on land we have one on IOT it's called IOT here but it's like I said I can wait I should probably rename it alright renamed Atlantis essentially what it is for purposes of this demo and let's put something behind it so Land 2 is right there is that's technically the third interface so we have the first second and third so we look at interface assignments xn 0 xn 1 xn 2 look at the network's virtual interface 0 1 & 2 here's all the IP addresses defined now we have to attach them somewhere so this is set to VLAN 10 lab so how do we get my parrot instance behind in the lab well let's go ahead over here we're going to network then we just change it to lab you lab connected look at the council Hey look it gave me the message again and we are now ten dot 10.1 o6 go over here services cheapy server there we are parrot requested via accident - so now I can do any type of testing behind this network and start defining more computers attach them on there and I've done this with Windows and Linux and everything but this is how you build out the labs in terms of that you can just dynamically assign the interface dynamically assign them it's pretty simple but this is how you can iterate fast and spin up different servers and get them done so I actually have an untangle demo the same thing if I wanted to fire up untangle define the networks on the lab now this is where you can create a mess so I'm feeding it off this network and I define a lab VLAN 10 lab here this has its own DHCP server so does pfsense so if you were to do this if you want to know what happens when you do this it's not exciting by the way but being able to whoops being able to define them and put them on the same network allows from all kinds of fun experimentation doing that now you'll get like conflicts and you know troubleshooting and things like that now the other thing you can do is the other way around we have that PF sense in the physical real world that's attached there we could feed and we can like look at this other PF sense that's running this lab to one here network we're feeding it the standard VLAN 69 but we could easily feed it and put it behind another pfSense over here so we could you know double nap them around and put it to studio 100 to 200 and pull from the ports on there etc etc so it's very dynamic having you know the XC PNG servers and having all these VLANs defined it makes it very simple to do this now you may have notice the snapshots here now let's jump into some of the how we build out the machines and how we do things inside the lab here with XC PNG I did this because there was an update I always do a snapshot before an update we're gonna head and delete it I don't need the snapshot anymore and let's talk about how we just managed the virtual machines you head and start from this page right here so we have a couple different tags in here production beams don't mess with these they're all production this is kind of the rule for when I'm doing these if it's tagged production don't mess with it so yes we host invoice ninja in here you just add tags to it whatever tag you want and then you can filter them out later like this I've done reviews as an orchestra I have a lot of things label test and easy enough to use and manage that so just tag all your production stuff so you can like separate that out at least that does help because maybe you shouldn't be running both production air but it's handy because they're kind of related and I've been doing this a long time so I'm fairly careful with all these things so here's my pfsense lab two that I have set up go to the council and we can just go ahead and shut this one down oops you while that's shutting down let's type in the lab that show all the things that I have in here so I have this Debian nine base and then I have this one here because I was doing some testing on the scuzzy disk over here and I've got some real in-depth XC PNG videos to show how to set things up in in great detail but in short what we do is pull up the lab again there's pfSense lab what if we wanted to make another copy of it take it easy so you can actually just hit fast clone and now there's a clone of it that quick and I can it start and now I have a clone that I can define differently council screw up to whatever I want with and when I'm done I can simply destroy it now I'm using these in Orchestra and if you notice at the top here this version is not bundled any support nor updates do with caution I have a video on how you can self compile this for your lab for production or for business they have a paid version that we use for businesses and production that's what we encourage anyone using is to buy but this is the full open-source compiled myself version and I've got a video on how to do that if you look at how to setup the open-source can compile yourself as an orchestra so pretty slick so we're gonna go ahead and let's mess this thing up I just we're gonna go or shutdown destroy this a second r8 it's down remove now we've deleted it it's really nice with xep ng I have found their system ultra easy to use combined with Zen Orchestra to be able to fire a virtual machine I fire up a lot of W machines you create I have this base install and the reason I have a base install is so I can easily keep it up to date and then clone it as needed so we're gonna boot this one up and each one of these is living back on that FreeNAS and dozer and like I said I have a very in-depth video about setting up xcp and G and how to attach devices but here's all my you know shared NFS and I have one on shared I scuzzy counsel whoops really fast so I can make sure this is up-to-date you update it real quick see if there's anything needs to be done nothing needs to be done real quick and let's make some clones so we can just hit fast clone we're doing this in real time and fast frame this fast clone and it names them clone so here's two clones so let's go ahead and start the clones start to be I'm sure and just like that I cloned two instances that I can then build whatever I want to build into them start using for testing load some software or someone said it looks pretty cool to find what network they're on they're gonna default when you clone them to whatever network the base was Devine done but it's arbitrary to go back here and once again I can attach them to whatever network I want to attach and so if this needs to be on this VLAN or it needs to be one of my lab demos it's really dynamic also you got to do this with it shut down well actually I think once the tool is loaded I can do it while it's shut yeah let's define two networks on this one I want the other end of this in here so we're gonna hit create and on the fly because this has the tools loaded I just attached it to the studio 200 added it on her interface and by the way let's see how that looks in here now it has two network interfaces it's gonna get an address on each one in a second okay I have to define it inside the virtual machine itself but you can see it attached the other network interface but it's not set to DCP by default so we'll shut this one down the same thing when I want to delete these or remove these or start them in group yes I should go I can take them take these two VMs start them stop them reboot them migrate them to another machine if I wanted to or remove them or shri boot force you know suspend we're gonna delete both of these I do like this you got to type this out and it won't let you do this either see how illness you copy paste delete two VMs alright I spelled it correctly so it's gonna let me destroy these VMs so next thing is what about brand new VMs how do I create more of them well that's actually pretty simple there's a couple options here so you can import them figure out where you want to land them you can drop OVA or xva files here to import a virtual machine no problem if you are familiar with OVA the open virtualization standard and you can just drag these in and import them that's one way and a lot of different tools sometimes they have them prepped in ready to go other options and one of the ones we use here is sometimes cloning things in so if you need to go from physical to virtual you can do things like set up and boot off of a Clonezilla and bring it in there or whatever tool you want to do cloning and of course the most common way is we're gonna go to new VM here and now we're gonna choose a template that matches and we can choose Windows if you're a Windows person to find a Windows server in here do it like this or go back to Debian and then these are just templates that kind of get you started but they don't have the ISO in here this where you have for the ISOs let me show you a little bit how this works in a storage so here's how we loaded parrot security we chose that it was a Debian based install we called it parrot test how many CPUs we're gonna give it eight CPUs 256 megabytes not enough so we're gonna go ahead and give it four gigs of RAM setup to boot off Parrott what network do we want it attached to go ahead and attach it to this one here for now it's like the storage repository let's put it on this one here the dozer scuzzy but I have there and then of course the local storage options and then give these a name I can add more disks if I wanted to and add more things or probably want at least an 80 gig disk for this show advanced settings this is actually pretty cool to boot VM after creation but you can also create multiple VMs in a man aiming pattern so if you wanted to create five of these at once it will create five of these at once and build them on a naming pattern so named percent ones like you know first index last index we go pair at one pair two pair at three etc etc so if you wanted to do that definitely kind of neat but fairly quick though we can go here and then we're gonna go ahead and hit create now as far as how those isel's got there I'm using Linux so I'm going to show you with my Linux machine here this is just a share an SMB share off of my FreeNAS machine 3.8 and then you put all the ISO files in there that's the one thing about there are ways to get installed within the XenServer itself but they're not officially supported or you can copy the ISOs but if you're building a home lab I would say it's okay to do that if you want to copy the ISO directly onto your Zen server ideally it's supposed to look for SMB mount and pull all the ISOs from the SMB mount so here's our parent completely defined I told it not to start on boot but we can we're going to fire it up real quick go ahead it start and when you're in the disc air I forgot to change the boot order so it's going to try to boot off network first and harddrive then DVD there we go now we can actually if I wanted a boot pair it in a live mode easy enough and away we go we would start install of whatever you want to install now inside of our VMs here we do have a few different Windows ones as well so I've got a couple RM demos I was doing for other stuff just a generic new VM scuzzy test and then a Windows Server 2016 64-bit avail we load sometimes email tools on here and I use them for my YouTube demos but I guess if you can define Linux virtual machines whatever you want and especially with Windows it's wonderful being able to quickly clone them because Windows is much in my opinion much more difficult when you load software you want a clean environment again it's in updates and problems it's easier just to clone each one so you have a base by which to work from so that makes it really easy it's you know when you're setting all this up so let's go back over here to parrot and is still booting live CD but boots up reasonably faster it does seem to be a little slower and I pull things off the SMB shares but so reasonable enough this is all in real time so it took you know I don't know 20 seconds to boot not not that unreasonable based on the machines we're using there's some older ARS Dell are 7/10 so kind of get you an idea though that this is how we quickly spin things up this is how we'll quickly define the labs and then once again I'm just going to go ahead and force shut down this machine because I don't need it running and then we'll go ahead and destroy it as well cuz I don't need the virtual machine I created and it just wiped it off all the systems that it was on and away we go over right back to a nice clean lab and like I said this is the way we handle things on here it's very fast it's very easy and I have a couple more videos that you may see coming on Shinobi and things like that and this is how we define some of those we started with our DBM base and then we forked it over to here so we created this one so this would be another video I do which still has a default password in it that's not a nice thing you can define inside the description sometimes I'll put that like with the default is I'm setting it out makes it convenient it's not a security thing obviously it's a really bad security practice they have anything production like that but what you're doing a demo when I first load something all they did was load it and the default passwords admin because I haven't changed it yet so this is how it's gonna start for the video but hopefully this was enlightening of how we handle some of the labs how we my lab works all the tools were using like I said it's free Nass it's XE PNG with Zen Orchestra as the admin interface but it allows me to iterate fast allows me to you know stand up a machine really quick move from the physical layer in the studio back to the backend layer here and like I said defining a network no time at all I go in here and just redefine a VLAN inside of unify and define the VLAN here and attach it to the Ethernet port and I do it all from my seat right here without getting up I can you know have an idea in my head and filed all the way to and this is why to me you know a virtual labs so important to have in able to you know make all these things happen now a couple comments so and someone's gonna say why not VMware why not proxmox etc etc or why not hyper-v if you are defining a virtual lab you should be if you're working for example to become a VMware certified I would recommend VMware if you just like proxmox better because whatever reasons and I've done a comparison video they're both excellent utilities didn't use procs box this concepts the same it's about being able to have an environment that you can test these things and set them up I'm really comfortable in this environment I think it works really well and we've done a lot of consulting work because we have a similar production only environments at some of our larger clients that are running these end servers and this is all Xen version 7.6 it's still being very actively developed they just announced as of May 22nd 2019 xcp g8 beta release which new updated kernel updated hypervisor updated control domain OS sent to us once again this is all open source they're being very actively developed like I said all the latest patches kernel patches security patches the the project has actually been very very well supported we've been running it now for quite a while I'm really happy with it and the one of the most important things about these virtual labs is making it you know easy to get things done fast and also I like the fact that I can define networks without having to run around plugging a bunch of physical Hardware in all the time and get something done fast so I can spin it up fast and make it into a YouTube video or tutorial or just test out an ID iaf alright I'll leave links to all the build videos that are involved in getting some of this tools set up that I've done previously but this is our tour of our lab 2019 thanks for watching thanks for watching if you like this video give it a thumbs up if you want to subscribe to this channel to see more content hit that subscribe button and nabela icon and maybe YouTube will sense you and notice when we post if you want to hire us for a project that you've seen or discussed in this video head over to Lauren systems comm where we offer both business IT services and consulting services and are excited to help you with whatever project you want to throw at us also if you want to carry on the discussion further ahead over to forums at Lauren systems comm where we can keep the conversation going and if you want to help the channel out in other ways we offer affiliate links below which offer discounts for you and a small cut for us that does help fund this channel and once again thanks again for watching this video and see you next time

Channel: Lawrence Systems

Views: 28,345

Keywords: home lab, home office, virtualization, home virtual, home network, it certification, it home lab, r710, home server lab, Virtualization Lab, home lab virtualization server, server, homelab, lab, home server, linux

Id: o1nwUfHsDHs

Length: 39min 53sec (2393 seconds)

Published: Thu May 23 2019