Getting Started Tutorial: Building An Open Source XCP-NG & Xen Orchestra Virtualization Lab

time here for warning systems and we're going to talk about building an open source lab using XC PNG including how the virtual networking works inside of it if you all learn more about me and my company head over to Lauren systems comm there's a high risk button right up at the top if you want to support this channel in other ways there is affiliate links well on the side of our website and down below this video to get you deals and discounts on products and services we talked about on this channel that does include shirts because this question seems to come up a lot in the comments and what do you get the shirts there's an affiliate link for the shirts over on teespring if you like any of the search that we have or ones you've seen elsewhere that are available on our store you can order them here shipping is pretty much all over the place teespring takes care of all that for us alright XC PNG is the fully open source hypervisor I've talked about a lot on this channel but I wanted to give you a getting started video now I have videos that are referenced that go in-depth on other topics but this is the basics of getting you started this is an fully open source product and it does offer paid support if you want it we're going to talk about it from the concept of building your own lab which means we're going to use the open source unsupported versions of this you can get support from their forums and have discussions they do offer you know a good community it actually they have quite a big community as they point out here 23000 forum posted over 90,000 downloads of this and 3,400 forum contributors so there you have a very active very healthy online community which is great if you're looking for basic help so I think this is a great product with a great community to build your system on but it also does work in the production environments of large scale enterprises and that's also why I want to start with what is Zen Orchestra what is the architecture of this and what is then project so Zen project is the actual hypervisor itself but not the whole thing then Orchestra is an orchestrating tool that runs on top of it so you have EXO a the Zen server which is over here XC PNG but EXO a actually supports both the Citrix one and the open-source one from here Citrix has their own version this is separate from sick tricks but Citrix does pull just so you know the same XenServer at the core and Zen server itself at the core is if you're wondering just hop hop it it is this is still the primary hypervisor within Amazon and I know Amazon uses more than one but this the Zen core not EXCI P&G but the Zen core is a big part of the hypervisor system that's used in enterprise things like Amazon and XC PNG is used very frequently like I said in large production environments all right we'll start at the hardware level and picking out a server means well some you know guesswork sometimes for things they do have a hypervisor hardware compatibility list generally speaking it does work on a very broad range of hardware but will it work is it hardware compatibility certified that matters a lot in the enterprise market and I just chose a Dell server but I mean they have a lot more than just Dell in here and they're bringing up Dell because by one of the affiliates down below is tech supply direct and they do offer discounts and for example I just did a video with the Dell our six-thirty it's 100% compatible with XenServer it's on the list here you can spec one out and I have a separate review I did of this it's a good server to run this on but obviously if you're building a lab it kind of comes on to whatever you have so even if you don't have a system that matches this hardware compatibility list it doesn't mean it won't run specifically the lab server we're building here is on an AMD FX processor with 24 gigs in RAM and an SSD and some random motherboard we had I purposely built it one out of spare parts I had to to show that yes it'll work with things that aren't even on the list but anytime you go off list with it there could be potentially compatibility issues and there's workarounds for some of those compatible shoes that you can discuss in the forums now architecture wise this is where sometimes it's a little bit confusing and this is an important part of the video that's I wanted to start with when you're loading XC PNG which we will go through the loading process of XO a is an orchestra the preferred way to control and manage the server's is a VM that runs within it this is different than some other projects and I'll bring up proxmox I don't really use proxmox but of course I'm familiar with it they integrated all into one system and that's just a different architectural design to load it and have the management platform be within it Xen has been done differently for a long time and one of the reasons that is scalability so you can have a scene system running xoa 1vm wherever that VM lives as a matter of fact it doesn't have to live inside of a Zen server but traditionally you do it's one of the servers you have running on there you can eat but I could be running it directly even on my computer right here if I wanted to it's a web-based application and there's instructions and we'll get to the host on how to build it or you can just download it from them but from one server you can run many many Zen servers so from a concept of that you can even and they have options to work remotely I can have a Zen server running it's an orchestra server running here at my office and VPN into other clients that are remotely and manage all of their VMs with it so Zen Orchestra offers a large amount of flexibility and scalability by doing it this way so you can have all these machines deployed and even if they're completely separate pools for example so you pool resources together so you take a series of physical Zen servers and you create a resource pool so you can do things like high availability or just easily don't move VMs around between those resource pools Zen Orchestra can connect different pools together and move machines between them and this is really easy for us because we have our main production pool and we have our lab pool I'm gonna be focusing on the lab pool but I can use one instance as an orchestra to manage both poles very easily and move VMs between them even though the server's don't have to know each other Zen orchestra will handle the introduction so to speak of the server's so they can speak to each other and pass VMs around between them provided they're all on the same version of XC PNG I do bring that up because there's sometimes compatibility issue if you have one on a newer one and one on the older one older will go to newer but newer doesn't always go to older two can sometimes be compatibility so it's always best when they're on the same but Zen orchestra can handle talking to pools that are at different versions so even if some are older versions you haven't get on rut grading and some write new words an orchestra will communicate with them all right so first thing is it was downloaded pretty easy grab the ISO and install it I've already physically loaded it on hardware but what I'm going to do now is walk you through what it looks like to go with to the load and what the options are to choose I want to boots you've got two options standard boot or advance we're going to look at the Advanced Options and what these are is if you have certain edge cases like install or upgrade alternate kernel options council etc there's a couple different things if you have an edge case and like I said if you have certain hardware compatibilities you may want to try one of the other kernels or the install to G that's for some of the rise in systems that there's some working out compatibility issues with and same with some of the epic so let's go back over here and we're just going to go through the standard install go through the boot and solar here so press ENTER and I'll fast-forward through this while the boots once the boots you presented with you know kind of a basic style older as I have sent around for a while Linux tile installer press enter next you know pretty basic here check for existing products I've loaded this demo before so it's gonna find an existing one now one of the nice things about how this works we're gonna perform a clean install but it also sees backups on here when you do the upgrades you actually will upgrade them when there's full releases the same way you put the drive in and you install over the top and it performs an upgrade but it keeps the backup this is a great way to do it because whenever you are doing this you can always go back and just pop the drive in and if it doesn't go well restore from that backup but we're gonna go ahead and delete put a clean installation in here we're not worried about the backup now hardware wise this has got an 80 gig hard drive in it this is the demo one the machine the hardware we built it on has 120 gig SSD in it I put two in this particular system to show you that there's an option comes up for software raid so I do have the ability if I wanted to hit software raid and I can raid two systems together or two drops sorry two drives together to make a raid if I wanted to we're not going to put this demo I just want to show you that was an option there and if you're using Enterprise Hardware you can also present a single large drive like with the Dell raid utility would be an example like I did in my Dell or six-thirty review 2x e PNG and just have it install there now XE PG slices apart for the operating system and will take the remaining hard drive whatever size that is and leave it for storage for the VMS as a local storage there are ways later to add more storage to it or you can start putting all the drives together themselves there's a couple different options you can think about for doing this but you at least want to install it on one drive itself maybe one smaller SSD that's on the system but it'll still take the leftover doesn't use and allow you to use it as local storage now this is the part where it's going to ask about the local storage essentially we could merge these together and put them both in here and storage for now for simplicity we're going to do it as EXT cuz this is gonna match the physical hardware when we get there I prefer the ext file base maybe slower but then provisioning I can't really say and you can go look in the forum's there's barely any noticeable speed difference between lbm or EXT especially because now the newer versions are using EXT for the previous versions we're using ext3 so i don't think there's much of a difference anymore and but my preference because I'm more familiar with managing the ext system I'm less familiar with LVM is the xt plus it supports the thin provisioning that's okay local media scanning live dangerous and skip verification of the media it doesn't really matter because we're gonna change it and this is just the demo for install static is probably your preferred so 1 I 2 & 6 8 3 . when OH - OH - 10 works for you match it to your network settings when we're free you can work this as DCP if you want but it's probably easier to find the system if you statically assign it to an unused address give it a name whatever your preferences choose a time zone we'll skip this for now but you can put Europe I think it is it think that's the right one put a proper time server in there and hit install this will take a little while it's going to go through the installation eject and reboot depending on speed your hardware this may take about five to 15 minutes to install like I said wild variation comes with how fast your heart rate it's really fast driver install faster so now we're gonna get out of this and show you what the next step is to forgetting the setup all right once the system is loaded you go to http one 92168 three to ten the IP address we assigned to the system it says welcome to XC p and g 8.10 now as of 8.1 leisa there's no management interface here to actually manage the system but it gives you some options for a quick deploy your download before we do either one of those is SH into the system so root at 192 168 3.13 210 and we're going to do a yum upgrade okay no updates son this is actually cuz I've already done the upgrades on here the first time you log in there's probably going to be some updates depending on when you downloaded what version you downloaded and if there's been any updates but the good news is from the command line it's better to do it before you load anything just yum upgrade it runs through the upgrade process and then you just can do a shut down ya shahr now and it'll restart so we're also gonna pull this up now if you were to plug in directly to the machine that this is running on right now and this is what you would see the status display the network management etc and this interface this is what's actually on the screen right now as far as like if it boot it up but you don't really have to do anything with this and pretty much the machine right now let's sing our lab and it's headless it doesn't have a monitor plugged in at all so let's go back over here and talk about quick deploy so the two options for management are as an orchestra the older one and I've talked about this in my older videos but don't really use it at all anymore is xcp and G Center a matter of fact with the 8.1 please note it make sure you have the latest version because they just fixed a bunch of bugs where it was trying to pull some of the wrong updates for it um this is the lesser maintained and lesser featured system and it doesn't have as many features as an orchestra does so Zen Orchestra has everything like it's a pretty extensive everything from backups and continuous replication and all the different bells and whistles including a lot of advanced networking options but of course they have a paid version versus a pre version let's talk about that when you run the deploy it's going to run right here and we'll put in the password connect and put an IP address and this is really slick it goes through here if you can see all the different networks that are on this room we'll get to those in a second it's gonna see normally just the main network you put any IP address you want to sign to this and it's gonna load and launch the free version I was in Orchestra and they have a comparison for what's in your free package and things like that limited support but it does work you don't get all the cool auto patching rolling snapshot full backup features and all the cold reporting features on the starter you do get 15 days of premium included with it which is pretty cool so you can actually use it to play around and see what all the full features are but being that this is a lab the concept is let's build it all from sources now they have all the details and all the documentation in their documentation here on how to build it from sources it's actually really cool and they did a nice job of documentation overall but they also like I said details how to do this or you can go here and this is the Zen Orchestra updater Zen installer from sources and this is a github script I have full instructions on how to do and use this on my video that'll leave a link to how to build Zen orchestra from sources using Zen Orchestra and salt updater okay people say they can't find the video I don't know how to make it any clearer but I will link it down below it's pretty easy to find so for how to build it from sources using this update tool works really well it makes it really easy they also have docker images if you don't want to take the time to compile so let's go over here first thing you want to do after you have it loaded is get Zen Orchestra running and that quick to plays probably an easy way to do it once you have that running you're gonna want to build a VM but you're probably asking well how do I at least get one ISO on here so I could build the VM well I do recommend doing the quick deploy for it and I'll show you how to set up local ISOs this is actually not my favorite way to put these on here but if we're talking about a single lab server this will definitely get you started so this is how you create a local ISO repository now we're going to assume you already loaded the xoa appliance and the EXO appliance system the free one with the quick deploy here completely will let you do this without even activating the trial you can add this local I figured I'd show how this works real quick when you go here to create a repository and we'll walk through the system so we're going to go new and we'll say new storage select the host which is the XE PNG lab and we're going to say we want a local ISIL repository path to directory well or SSH tin over here we'll call it local ISO local i/o so now we're gonna go ahead and find something to download and I'm pulling this from the Debian page we'll just copy this link here the ISO folder and rules type W get to polyp you could use whatever tool to get this in here what we did is in the root of this system we've added this particular ISO now the problem you may run into is there's a limited amount of storage in the local system and that limited amount of storage means well you're not going to be able to put too many ices in here and you could cause problems so this is not my favorite way to do it but it is a way at least you can start getting some ISOs on the system but I want to show that this is possible and how this part worked - an LS and PWDs or a local ISO right here let's copy that and we see that there's one W and ISO in there so where's the path locally so we hit create well actually give it a name call it like local ISO here create well please fill out the description there we go we look at what drives right here there we go pretty much one disc one simple system in there not a big deal if you want to put a few more in there but like I said there's a little bit about of storage that's how you would do that and then to create a new VM you go over here to new VM select the pool select a template we're gonna say he Debian 10 because that's what we download it in there and then you would select the ISO and there's our local I so now I a VC have a lot more ISOs in here we're going to talk about the better way to do it so right here's that w1 if we wanted to go ahead and create it and we could go through the load process and build up am not going to do that we're going to go back over here to storage pools and let's go get rid of the local ISO one remove it connect it yep yeah it's stuck because they ruined something it was stuck because they thought something was using it takes a second and now it's gone alright so if you go back over here to storages I have this FreeNAS I so the way this got on there pretty simple this is a FreeNAS server with a bunch of ISOs in it now this can be this is just as SMB mount but this can be done in a few different ways so we're gonna go to new storage post storage name select the value and you have local NFS or SMB you put it in the server name now this can be your Windows server if you have all your ISO files on a Windows server and you have an open share or a share with a username and password on there you put all filled all this in and create and it will read all those on it it only has to be a read-only sherek sits just pulling the iso files so this is another option for getting all the ices in the better options because I have so much storage on my FreeNAS now what about adding other local storage well I'm not gonna die too deep into that because we have some available local storage for things but kind of the same thing when you're adding a new storage so we're gonna go ahead and look at the existing storage again and we'll look at this right here this is my FreeNAS named dozer and mount dozer bent layout so let's go ahead and show you how you add one of those we're going to go new storage again select host FreeNAS NFS it's just an NFS share the basic options of NFS share will login and look at those real quick we'll choose fess 192.168 default NFS version at this little query and look it found all the different ones that are available on there that I have including the lab VM which is actually not a good idea to add the same one twice that would probably create some problems so I'm not going to do that but this you kind of get an idea that's pretty easy way to do that now what does it look like just really quick and FreeNAS and you can do this with Synology you can do this with really anything that supports NFS and here's the Zen lab VM chair we're gonna edit advanced mode check the box that says all directories make sure it has permission to readwrite access into that storage like I said whatever you're using for storage that will work few other options that are inside of the XenServer we're gonna go back up here it does have and I've covered this before how to set up I scuzzy on there LVM local ZFS local so they've built in ZFS if you have a bunch of drives you can go to the command line and time together with ZFS I think you have a separate video on that LVM or simple ext local so if you just have a device you can just point it at that device and it will create an ext file system or you can create an exe file system on it and pointed at the device after you create it that you've attached so there's plenty of options to dive into inter documentation to pretty good on it so once those pieces are taken care of let's jump into the networking part now there's two pieces to the networking it's sometimes a little bit confusing but let's could break down and explain it by starting over here this is my layout this is my XC PNG lab system running in AMD I put the processor to someone Alaska it's an fx 8320 with 24 gigs and RAM in a single 120 gig SSD on there so the hypervisor and all the VMS live inside of this one physical box the network card in here happens to be an Intel x5 20 10 gig card there's a lot of different 10 gig cards that work I like the Intel ones because they seem to be very very compatible this is going to my unify switch a unify switch is set up as a trunk port which means all VLANs are passed across here that's an important thing to remember so all VLANs and that is also the native network is the one 92168 3.1 network that's native VLAN one and I bring it's up because we're gonna talk about not just how to create a network but also how to create a couple VLANs in there but it is important to know it's a single physical network connection but we're gonna create VLANs inside of here and show you how they work and they're already defined either in the unified switch and the PF sense or just the unified switch that's going to vary with some of the switching equipment but at least you should be defining those VLANs within there if you want them to work on the port's we're also going to talk about the private networking features that are in here let's go back over to this and look at kind of the IP layout of what we have set up so my Pia sense manages the one 92683 network and the one two seven two network I do have defined but not managing pfSense it's only defined as VLANs and I unify VLAN 20 VLAN 100 billion 200 I just created these so I have some extra VLANs for doing things where I may want something in the physical side of the server to come out to a physical port I mean doing those later in advanced videos just want to mention they exist but you do have to have these defined in your switching equipment and that's because we're gonna be running pfSense inside of here as our lab which you've seen me do before if you watch this channel and that's how I get pfSense inside the system to talk to outside systems is by splitting off these VLANs but physically the lab servers like I said one physical Ethernet cable connected at 10 gigs so there's the assignments we have here's the lab server itself the X C PNG and this is a virtual machine running on it these an orchestra and it's a dot 28 so let's dive into the networking side of things now please note I am using the fully compiled version like I have a reference to my other video of Xen orchestra that being said I did compile it with the flags and you can look through the details when you set it up or use a docker image to say make sure all the plugins are there this is important because if you don't have some of the plugins specifically the plugins related to the Sdn controller you wouldn't be able to do some of the steps in this video because the Sdn controller has to be turned on so if you did compile it that way great you just have to turn the Sdn controller on if you try to create a network with out that turned on it prompts you with a link to the instructions of how to turn that on so let's go over to the networking under host and we can see the network interfaces right here this is the one that's assigned the other ones can all be left alone you assign them to the VMS but you don't have to sign anything more than a single IP address within the actual physical XC PNG machine but you notice I can't edit these networks so that seems kind of odd right well not really and ignore the fact that for my lab demo we did set it to DHCP instead of static because I wanted PF sense to handle that so if anyone wants to point that out that I said set it to the other way yes you can set the static but I choose DHCP that way I can manage everything with my pfSense just FYI and you can see it's connected at ten gig but then we have VLAN 20 10 gig storage let's go ahead and add another network now even though I can't edit them here let's talk about exactly how we add them and where they end up so you over here to network select the pool and if we had more than when pool collected it would give me all the options for later pools you can see which ones are plugged in and eath 0 is the one we want to use and we're going to call this 69 because the VLAN tag is it is not the MTU I'm sorry 69 can leave the MTU at default if you want to tweak it they do give the option to leave it at default unless you know what you're doing there so we just name this VLAN 69 to make it simple we'll go ahead and create Network all right we're gonna do another new network it's like pool it does have bonding options if you were to select multiple interfaces that is an option in case one what that is up there so you can bond them together studio 100 create Network and we'll do one last one just so we match what we had in the sheet over there over here to network you actually 200 copy and paste thing here 202 honored 200 now we're going to go to home pools and we edit all the networks from the pool this is where you can actually change and set settings on these and use them and rename them to something different if you want and the reason you edit them in the pool is so all the hosts have matching network interfaces in that pool and let's show you that in production so if we go over here we go over to my production pool here and we look at the network interfaces and let's say we have this as his dot 3 general network not in use studio 200 lab network let's edit this one to say lab network so we'll put this as lab network and I have in here go to the hose you can see that Network is now in this host and that network is in the other host as well so what this allows you to do is create it in one location and this automatically gets propagated to the other ones pretty straightforward but if you're even if this is a host of one it's still the way the practices are of doing that one important thing the network order has to match in order for this to work properly so eath SERO is plugged into and trunked all on my main system just like it is on my lab system so both of my servers the xcxc PNG running on the six-thirty and the other one go over your back to host 720 both have a matching set of network interfaces plugged in the same way for the network it's there's ways to rearrange them it can get a little tricky but generally if you're putting them in you want eath SERO on each computer to be plugged into the same network that way if you pass any VMS between there's not any weird things that happen and same goes for each subsequent network interface the cards can be different types of cards they should just be plugged into the same network interfaces so this is a little side note on when you're building the machines but it's something that is fairly important to do when you're doing that because you're naming them all in the pool all right back to the system here so now that we have those networks built let's talk about building one more network and that's a private one so the private networks are different so the VLANs work fine for when you have the system and we'll go the system requirements here the VLANs are for when you want a network of course to pass through your network and searching equipment but sometimes maybe you don't necessarily want it to openly pass through there and there's a couple different options so they have VX LANs and encrypted GRE tunnels I've already got one VX LAN created on there and you can create one VX LAN or one GRE tunnel and it has an encryption option and you can if there was more than one pool we have the add pool option these are kind of neat because what this allows you to do is have an extended Software Defined Networking controller and you can find this they have information on it but one Sdn controller three different pools many different hosts that can talk to each other through an encrypted tunnel now this is an interesting way you can build out a pool and have inner communications between the VMS and tied to a back-end VX land that's all encrypted and you're able to pass this data back and forth as if it's kind of a almost like a VPN but it's actually at the network layer so everything goes across there and this is sometimes used in data centers but when you're building out something kind of specific for yourself and you want to play with a lab and you say I want to lock down don't let it leave into my networking equipment but this particular VM needs to stay behind whatever firewall we put in front of it and we will demo how to setup pfsense in front of it that's one of the other options they have in here it's pretty pretty neat I'm not going to dive deep into it other than yes it's pretty easy to create and pretty easy to maintain and the reason you still tie it to an adapter so it knows what it after to leave and go out through the system when you're setting it up so that is definitely an option in there all right let's go over to PF sense now and we're gonna say filter none to show all the VMS that are on this machine right now and we'll go over here to the pfSense lab setup and let's look at the networking so we have the VLAN 69 which lets us change it so we'll have it plugged into ten gig Naida which give is it a 192 168 3 dot address on there and then I said studio 100 and studio 200 now the studio 100 200 are not defined in my PF sense they are just VLANs defined in my switching equipment and this allows me if I want to put any ports on my switch to trunk it to that particular VLAN tag I guess a tag 100 tie it to one of the switch ports and then the PF sense in here will then feed any devices that are outside of my network for my lab testing and this is how we do some of the demo videos that you see in our studio so we're go ahead and fire this up now as far as getting pfSense on XC PNG they have a tutorial right here right in their blog post about how to do it they have entries in our wiki on how to do it and I will comment on this there's two approaches to setting up VLANs and I definitely by far as it says here the easiest solution and perhaps the officially supported approach for XC PNG when you do this dom0 hands all the VLAN tagging what that means is as we were doing in creating all those network interfaces each one of those network interfaces is attached to the main XC PNG system and in its handling the VLANs and PF sense which should be booted up now it is I'll go ahead and log into it it does not see these as VLANs but as actual adapters so by handling it inside of here and we'll look login a PF central quick it does not see these as VLANs here so if we look at interface assignments we go over here to VLANs there's no VLAN tagging going on here everything's treated as an interface so instead of adding more VLANs to here even though they are because there's only one physical adapter on our XC PNG machine and everything else is trunked out with the VLANs and that's how we're slicing these up to build out the separate networks you don't actually define them here there is some information on here and ways to do it but it's it's kind of I don't know it doesn't seem as well supported it's more challenging to do that and I don't think you gain any benefit from it other than you be able to define and play with VLANs inside of pfsense here but that like I said kind of a one-off thing I mention it but I prefer to do it the way that I have this set up but when was the first interface land land to ignore this this is for another demo but these are the interfaces that we have attached that we have right here so you can see that the second one down X n 2 has the 40 network on pfsense so we should be able to go over here network and we'll attach it to the studio 100 so now we've attached this the studio 100 and will boot up this Debian server Debian on my labs over here and it now is behind the PF sense and should get an IP address once it boots boot it up let's walk into it and it has one 92168 40.1 one nine big over here in a pfSense services DCP server Hey look there is the debian lab assigned 192 168 40.1 1:9 pretty easy enough to find there and what if we wanted to change it what if we want to put it on the other network well it's actually pretty easy week over here to network we'll change it to the studio 200 option you and now it has 10.10 dot one one so that was and we'll just shoot over here go back over here to pfSense you can see that's the other network inside of pfSense the xn to network adapter that's attached to that pretty straightforward to do now the only tricky problem I have had and pfSense might get angry if I do this is it let's go ahead and change it so let's try that lab the X LAN sometimes pfSense yep it didn't like that so let's see if it actually worked sometimes you do have to change when you change the network after restart pfSense not all the time but some of the time I've had this happen yep they still thinks it's disconnected so you just have to reboot it so will reboot pfsense real quick and it'll come right back up and running so let's go ahead and reboot it it doesn't like the network adapters on pfSense being changed without a restart I'm not sure what the workaround for that is or if there's some driver I'm missing but I did follow the instructions and I do see that happening it does have as you can see and it's stopping right now the Zen guest utility is running in the background but that still happens so we'll let this reboot real quick all right pfSense is rebooted logged in and now we changed the network to this lab the X land so we're not going to go through the whole demo of extending this VX ion across other pools but just to show you basically if we take and go to the VMS here and now this server will move it over to that VX land here there we go and we still have the ten address and we should be able to get out and we're on the internet so we can ping things we can get out of the internet things are resolving never it works really fine now the one other network typed is worth mentioning in here we can go to the pools likes to be in lab go to networks is the host internal management network networks on which guests will be assigned a private link local IP which can be used to talk to the Zen API these are kind of neat because this is local only to one physical host so you can tie things to this particular adapter and this will allow you to have communication only inside of this particular machine so it doesn't have anything else but you can tie this once again to pfSense and then build your networks behind it and everything flows back out of PF sense now the other question that comes up a lot is what if I want to virtualize my PF sense and run it inside of here well if you may notice I labeled a couple of these not in use not in use and that's just kind of a general housecleaning I do when I set them up if I don't have and there's nothing plugged into these other network interfaces like eath 1 and E 2 how old is them is not in use but what if I wanted to use them and what if I wanted to use it for my cable modem to plug in in my virtualized pfSense so I can have it all over twice myself I prefer to run pfSense on real hardware that way if I'm ever troubleshooting something I did inside of XenServer and it didn't boot for some reason I have easy internet access but if you insist and want to run it this way you could call this cable modem and the reason you might want to call it cable modem maybe a ble modem is you would take this and assign it to the LAN and calling a cable modem would help you hopefully not accidentally assign it somewhere else so if we were in here and we seen it and we go networks and if you if you assigned it cable modem you would go huh I'm assigning something a network called cable modem so if you label it like that it's a good clear way to let you know where to assign it to and where would you assign it pfsense pretty straightforward you go here and you would change the native network and we're using a native network cuz this is essentially double netted as my lab system but I would change this to cable modem because vfi Vif number zero is right here it's the first network in it or if you're looking in the council you'll see that it's X and n0 inside a PF sense and this signed here via DHCP now in case you're wondering can't you assign more than one thing to your cable modem yes and it's essentially the same as when you come out of the cable modem and you plug it into your switch any type of switch and then plug more systems into it what happens next is really based on the support level you have with whoever your cabled writers or really if you're doing this and you're getting like let's say a fiber handoff that does give you a whole block of IPs yes you could assign them all through here or even have XC PNG and have that one port that we labeled cable modem attached to multiple PF senses or multiple different things that you have virtualized inside of here maybe you want to have a server have a direct public address that's another way to handle it so there are some different use cases that do work if you want it publicly done just be careful when you're doing that because what you don't want is because obviously it's so easy to go here and go to the network and swap these two really any network pretty quickly you don't want someone to accidentally do that and accidentally take a server that's supposed to be private for local communication and just throw it out into public Internet but that's pretty much it there for setting up the networking pretty straightforward now anything else you do from here I've gotten and got videos on how to do the backups how to do the config backup restores settings setting up the remotes and there's a lot of other features that are in here that obviously you can play with there's importing BMS importing just a disk and setting up you know new servers new storage new VMs and I have other ones on how the entire hae process works where we took several servers tied them together to a single resource pool put it in a chain showed how it auto failed over between them now because this is a self compiled version like I said it does have any support if you want to use in production they do have a purchase option and if you decide if you're playing with this in your lab and you want to run this at your business there is paid support for both XE P&G and Zen Orchestra and support packages available that do help out the developers of this that is the way they monetize is they make money selling support packages for the whole system if you want to use it in production but it's a pretty awesome system I've been using it for a while we've got a lot of clients running this in production I'm really happy with it it's been an excellent project in 100% open source so all the features and I've talked about some of the other ones details before like the V motion that you see in the esx/esxi world does work inside here they have the Zen motion as they call it so I can move in transition live servers between pools and a lot of those other bells and whistles including doing snapshots and snapshots with memory so you can snapshot something in place and grab live memory for backup so there's so many features I can probably go on another hour but I won't if you look through my videos I have a few more on there and of course they got plenty of documentation you can go through and do some your own reading and they have a very lively community and forum where you can also have discussions as well so Ari Dan thank you hopefully this was helpful and thank you for making it to the end of the video if you like this video please give it a thumbs up if you like to see more content from the channel hit the subscribe button and hit the bell icon if you like youtube to notify you when new videos come out if you like to hire us head over to Lauren system's comm fill out our contact page and let us know what we can help you with and what projects you like us to work together on if you want to carry on the discussion hetero to forum style or insistence comm where we can carry on the discussion about this video other videos or other tech topics in general even suggestions for new videos they're accepted right there on our forums which are free also if you like to help the channel on other ways head over to our affiliate page we have a lot of great tech offers for you and once again thanks for watching and see you next time

Channel: Lawrence Systems

Views: 76,205

Rating: 4.9451265 out of 5

Keywords: lawrencesystems, XCP-NG & Xen Orchestra, open source lab, open source, lab, source, data, diy, open source virtualization, virtualization, hypervisor, xen, xenserver, xen server, virtual server, xcp-ng, xen orchestra, linux, virtual machine

Id: q-jKs62b6Co

Length: 41min 42sec (2502 seconds)

Published: Wed Apr 15 2020