one_knight_scripting

@one_knight_scripting@lemmy.world

• ⁨Comment⁩ on ⁨Starting to self host⁩ ⁨⁨1⁩ ⁨day⁩ ago⁩:

  One more advanced hypervisor that I would recommend is Apache Cloudstack. Requires a little more networking though.

• ⁨Comment⁩ on ⁨Starting to self host⁩ ⁨⁨1⁩ ⁨day⁩ ago⁩:

  I’m curious where you are from and what hardware for self hosting you have. I also want to know what you are interested in self-hosting or learning.

  For me, my home lab started with networking. Yours doesn’t have to. For me, I had already achieved a standing time and was working to become a network engineer. Where are you on your path? In truth, starting with the network is not the best, mine required dedicated equipment: a firewall(UDM), switching(ubiquiti), and access points. This is expensive, so perhaps not the best place to stay.

  I would say that a good place to stay is with virtualization and a hypervisor. A hypervisor is intended to run virtual machines. I think starting with a hypervisor is a good idea because once you have a hypervisor, you can experiment with just about anything you want. Windows, Linux, docker, wherever your exploration takes you.

  Now, I would say the cheapest way to do this kinda depends on you. Do you have a .edu email address? If so, you should be able to receive free licensing for Windows Server through Microsoft imagine (previously called dreamspark). If not, do you have Windows 10/11 pro edition? I would say that Windows server may require dedicated hardware, but if you are already running Windows pro, then your daily driver pc will be capable of running hyper-v.

  If you have an old spare computer, you can make it a dedicated hypervisor with either the Windows Server option, or in my opinion the preferable Proxmox. Proxmox may take a little time to get acclimated to since it is Linux command line, but you already have experience with that on the pihole.

  Those are my recommended next steps to take. Though, there is plenty more that you can do. As others have said docker is a cool way to make some of this happen. I personally hate docker on Windows(it’s weird and I just want the command line not a UI). But you should easily be able to spin up Windows Subsystem for Linux, install docker and docker compose and get started there without needing any additional hardware. You could also do the same using hyper-v if you prefer and have a pro license.

  Regardless of what direction you choose to go, you can go far, you can succeed, and you can thrive. And if you run into any issues, post them here. Selfhosted has your back, and we are all rooting for you.

  Side Note: Hyper-v used to only be available on Windows Pro, but if someone knows for sure that it is available on home please let me know and I will update my post.

• ⁨Comment⁩ on ⁨Help me selfhosted, I'm in over my head!⁩ ⁨⁨5⁩ ⁨days⁩ ago⁩:

  I’m picturing open stack being fairly similar to Cloudstack? Cloudstack is nice, but does require some odd networking.

• ⁨Comment⁩ on ⁨Help me selfhosted, I'm in over my head!⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  oOooo… Quite interesting.

  If you are intending to use it, I have some thoughts about the way that you should get it setup and running.

  First thing I would look into is getting the iDrac reset and working. iDrac is intended to allow you to view the display of the server without connecting a monitor, simply use a web page. It also allows you to power on/off the server remotely even if it is frozen or off. It is a simple web interface that allows you to control it.

  After that, I have some questions about your intention for this server. If you are intending to use this server as a hypervisor, I would like to take just a moment to shill for Apache Cloudstack. I recently setup a server running this and it is going absolutely wonderfully. The reason I chose to use it is it is more open to DevOps workloads, by default compatible with Terraform and takes literally 5 minutes to setup an entire Kubernetes cluster. However, the networking behind it is a bit more advanced and if you want more detail just ask me. For now, suffice it to say that it is capable of running 201 vlans protected by virtual routers.

  If that is too much to bite off for a hypervisor at one time, then Proxmox is the way to go. You can probably see a few videos from Linus Tech Tips involving that software. It has much simpler networking and can get you up and running in no time.

  Finally, if you are intending to learn something a little more professionally viable, then I would talk to your boss about utilizing an unused VMWare license or perhaps working with Hyper-V(my least favorite option).

  If you do intend a Hypervisor, then I would highly recommend setting up a raid. Now, the type of RAID depends highly on what you want. RAID 5 will probably work for a homelab, but I would still recommend a RAID 10. RAID 5 gives you more storage space, but I like the performance benefits of a RAID 10. I think that it is very important when multiple virtual devices are sharing the same storage. You can read more about the various RAID levels here: www.prepressure.com/library/technology/raid

• ⁨Comment⁩ on ⁨Post your bandwidth usage⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  I seed what you did there.

• ⁨Comment⁩ on ⁨Half-Life 2 peaks at 52,000 concurrent players, 20 years after its release⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  You just changed my life.

• ⁨Comment⁩ on ⁨If you already know Docker CLI, is there a reason to use Portainer?⁩ ⁨⁨5⁩ ⁨months⁩ ago⁩:

  Wow. What an awesome wife. I think I just discovered a new relationship goal.

• ⁨Comment⁩ on ⁨Microsoft Edge gets "unfair advantage", browser makers claim⁩ ⁨⁨5⁩ ⁨months⁩ ago⁩:

  Take your upvote and gtfo. Lol

• ⁨Comment⁩ on ⁨Best Guest VM Filesystem for NTFS Host⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Yeah, I’d just like to ask why it has to be NTFS as well. I want to help you to the best of my ability.

  Now in terms of what you are trying to accomplish, it would sincerely help to know what kind of server you are trying to create and what you want it to accomplish so I can help you with the design. It would also help to know what hypervisor you are using to read those VM disks. Now, for the sake of the rest of this post, I’m going to assume that you are simply creating a Linux server meant to share those disks with a hyper-v hypervisor (to ensure we discuss the worst case… Lol… but also because I think the only reason you need NTFS is to support a Windows hypervisor).

  Now if that assumption is correct, I would still ask why the filesystem must be NTFS. If all you need is a share for the files then why does the filesystem even matter? In my opinion, the worst case scenario that you have is a samba share which shares these files over as a Windows share. Now Windows is capable of better sharing utilizing either iscsi or NFS. None of these three sharing solutions (samba, iscsi, NFS) require an NTFS filesystem. Though I will admit that there may be some other thing that causes an issue with the potential of these solutions.

  Anyways, not to pry, I want to help you though but a little more detail would significantly help with helping you find a solution.