New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
I'm a fan of having the option to choose between between fast but metered or capped throughput and unmetered.
Yes, I looked into it too before making the decision to deploy, but they were fixed shortly after the CVE was released. https://github.com/komari-monitor/komari/security
It's always a never-ending cat-and-mouse game between attackers and defenders, haha.
I wonder if FreeVPS (KVM NAT) provides the option of Alpine mirroring? Just now I was going to check https://wiki.freevps.org/ but I noticed it was showing HTTP 502. 🤔
Opsie, back up now. Alpine mirroring?
Alpine pre-configured image template, I made a typo.
Ah, yea we have Alpine.
I had a discussion about server specs with Alexhost today. On Monday, I expect to hear more from Alexhost about what they can do. I plan to post another update here after I hear again from Alexhost. But, meanwhile, here is a brief summary of what I imagined might be possible:
/28 = 14 useable IP addresses, one for the server, one for testing, and 12 to give out.
Enough IPv6 IP addresses to give each slot some IPv6.
1 Gbps or 500 Mbps unmetered.
2x Intel Xeon E5-2690 v4, 28 Cores, 56 threads. So approximately 4 threads for each IP (less whatever is needed by the node itself)
64 GB DDR 4 ECC RAM, gives 4 GB to each of the 14 IPs (less whatever is needed by the node); additional memory as a bonus for us!
Enough disk to give each of the 14 slots at least 100 GB. RAID 1 or RAID 10 definitely preferred.
Location: Moldova
If anyone has comments or suggestions, they would be greatly appreciated!
Thanks to Alexhost!
Please let me share a few additional ideas:
Pricing -- Free, yes, no funding needed, but how about asking people who want to hop on the server to post an introduction, a tutorial, or an investigation about what they want to run on the server (or about anything else relevant to our beautiful Low End)?
Almost BDFL-ism -- In my two previous free VPS startups projects (both still going strong!) I tried really hard to respect the Low End community by soliciting opinions, fostering discussion, and passing those projects onward to others. Maybe this time I should be a little more assertive about my own need to learn while also trying to stick with the project longer?
Thanks Alexhost!
@Everyone What do you think? Thanks!
I think that's a good idea. Rather than having one strict requirement (such as "FOSS developer"), more general and flexible requirements would be nice. It also gives you more flexibility with regards to who you onboard.
Sounds good to me! If it's something that lets you learn, you'll probably be motivated to stick with the project longer naturally. If it's free, there's no reason you shouldn't be able to benefit from it as well!
Why do you keep starting the same project over and over, abandoning it, and then starting it again? Why not do something else?
Why a third free VPS project? There already are two and somewhat confusing.
Why was FreeBSD / Bhyve not even mentioned? It does run pretty much any OS and it's fast plus, more importantly, it comes with good infrastructure, and there even are web-panels (which I didn't test yet because I have no need). I've been (and still am) using it for years and it always did what I needed (incl. diverse Linux distros) and never failed me.
@Not_Oles just a random suggestion - what about collaborating ?
FOSSVPS could take the new @alexhost dedi as we already have the expertise in providing services and admin. We could then create the equivalent of a VDS for you and your new users on the dedi.
I would be happy to also provide VDS services on our other existing nodes. The new dedi could also be available for FOSSVPS users so we both benefit and grow.
As far as I am concerned this is all Open Source stuff so have no hesitation in allowing it.
You do whatever you wish on the VDS and we just act as the 'holding' organisation.
This is just a suggestion and obviously it is a lot to think about. I just feel there could be some mileage in exploring the idea. Remember 'small is beautiful' and 'little fish into bigger pools'.
Mike
Please re-read the OP, including note [1] there.
Thanks for suggesting FreeBSD / Bhyve! I appreciate your favorable history with Bhyve! I am glad you have had so much success with it. It's super interesting that Bhyve does run "pretty much any OS."
Personally, I have not yet used Bhyve, so my ignorance makes Bhyve a "grassy path, which wanted wear." (The Road Not Taken, by Robert Frost)
Our list of possibilities now includes at least:
(1) free VPSes made on Debian or Ubunutu with virt-install and cloud-init
(2) free VPSes made with OpenBSD VMM
(3) free VPSes made with NetBSD NVMM
(4) a free service which provides IPv6-only VPSes with IPv4 access
(5) free FreeBSD Jail instances, with linuxulator
(6) free FreeBSD Bhyve instances
Does anybody have additional ideas?
Thanks Alexhost!
Okay, great idea! The possibilities list now includes collaboration with FOSSVPS. Collaboration also is under discussion with Tierhive. Anyone else want to discuss possible collaboration?
(1) free VPSes made on Debian or Ubunutu with virt-install and cloud-init
(2) free VPSes made with OpenBSD VMM
(3) free VPSes made with NetBSD NVMM
(4) a free service which provides IPv6-only VPSes with IPv4 access
(5) free FreeBSD Jail instances, with linuxulator
(6) free FreeBSD Bhyve instances
(7) collaboration with FOSSVPS (provides Proxmox dedicated core VPSes at several locations)
(8) possible collaboration with Tierhive
Thanks especially to Alexhost!
Yet another @Not_Oles project, should be interesting
I thought the point of that poem isn't that the pass less travelled is better, but that it doesn't matter what road you take. And retrospectively it provides some justification for your actions, "I messed up, but that was because I was in uncharted territory" or "I messed up, but that wasn't my fault because I was following the commonly accepted wisdom at the time" or "Look how great I am, I didn't do that stupid thing that everyone else did".
Why does every new operating system need to be a new project with a new name? Why can't it just be a generation 1 server, a generation 2 server, or a generation 3 server?
2) and 7)
use these dedicated cores to nest *bsd vm
Alexhost considered again, and said they have to pass for now.
Best wishes to everyone here!
Thanks Alexhost!
Thanks especially to @forest, @lgctt, and others who tried to help!
Perhaps if you wrote up a detailed plan and purpose along with specific specs, you could post a request for sponsors and other providers might consider it. You'll have more luck with a specific plan than anything vague or ambiguous.
anything beyond "hey let come up with a reason for provider to give me a free box quick" might be good