@JBB said: OKC sounded great, but I gather those plans are on hold?
Oregon, Utah, and Colorado were all being considered. However, the location we'll be launching is Oklahoma City.
OKC Launch
We're going to be doing this location a little bit differently. I wanted to confirm with you guys that this finally is moving forward. I was going to wait until we actually got it done, but it's probably a good idea to gather some feedback at an earlier stage so we can make any requested changes more easily.
This will likely be initially done as an unofficial launch, as we figure things out. So maybe watch out for an interesting sale. We're also doing our own network for the first time and there will be some type of disclaimer about that.
Network - As currently planned
Network will be done with an IPv6 focus, where possible + IPv4 NAT. We may provide dedicated IPv4 at either a high setup cost, or for certain line of services (generally at about +$5/YR extra as per usual but no price lock.)
Lumen on 10Gbps
Cogent on 1Gbps (for now)
OKC-iX (Hurricane Electric, Cloudflare)
Software & Branding - As currently planned.
So as I mentioned, we're going to be doing this location differently and that also includes likely using VirtFusion or some other system that does better with IPv6. These services may end up under their own branding, other than some exceptions. We may also finally want to do proper "cloud" using Fleio/OpenStack.
It will also be the first location where we "officially" try to do IPv6 for the VirMach brand, where we'll have a portion of the servers dedicated to this brand and do it the same way (with SolusVM.)
Hardware - As currently planned
Ryzen - same/similar leftover Ryzen servers.
Epyc - any existing Epyc that we never deployed, plus a few new.
Storage - some limited storage, and central backups.
Rented dedicated servers - see below
We'll be building out dedicated servers to rent to customers directly. The focus will be mainly on Ryzen dedicated servers as planned several years ago. We'll honor these at agreed upon previous pricing for any dedicated server customers that purchased E3 to upgrade to Ryzen (someone remind me on the specific promises so we can try to get this done.) Likely Ryzen 2600 to 3700X, but potentially up to 3800X depending on how the budget is split. We may try to keep the MSRP the same on all variations, kind of like a hybrid grab bag, so they will likely not be "stacked out" but instead balanced, lopsided in some way (more RAM, more CPU, or more disk.) Just got 40 motherboards delivered.
We will also try to do some interesting things with anything left over. We still technically have hundreds of E3's, some E5's, as well as older GPUs.
Colocation Product - As currently planned
I wanted to give a little more information and general planned pricing for this, for anyone interested.
$69/MO - Per 1U/1A 208V/100Mbps (or 50TB @ 1Gbps)
Included per 1U:
1 x PDU Port
2 x switch ports
1x /56 IPv6
Optional additions:
+$25/MO - Each additional 100Mbps 95th
+$175/MO - Upgrade to 1Gbps 95th
+$10/MO - 1 PDU Port
+$8/MO - /29 IPv4 (Subleased)
$120 One-time - /30 IPv4 (Static)
Timeline - As currently planned
We'll likely have the first cabinet ready first or second week of April, with Cogent coming in Mid-April and Lumen by the end of the month. I'm currently trying to decide on routers and have those ordered in as well.
I'll try to push to have at least a few servers set up at this location immediately, so anyone who wants to have their service migrated can do so, if anyone is interested in providing early feedback on the network.
All very interesting.
As always, I'm game to be a Guinea Pig. I have a surplus of VPS in NYC, so easy to find a migration candidate, though IPv4 is my modus operandi.
Available for immediate migration: " AbandonedJaunty-VM" id=721293 (chosen due to single IPv4: a multi-IP is also available should you wish to challenge a SolusVM to Virtfusion migration.)
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Could you please reply my ticket #238520? It has almost been 6 weeks.
If you are busy at your current work, maybe at least tell me in this thread when my ticket will be reviewed so I don't have to check it every day??
@VirMach said:
Oregon, Utah, and Colorado were all being considered. However, the location we'll be launching is Oklahoma City.
I like it!
Network will be done with an IPv6 focus, where possible + IPv4 NAT. We may provide dedicated IPv4 at either a high setup cost, or for certain line of services (generally at about +$5/YR extra as per usual but no price lock.)
Ouch. I like IPv6, but losing IPv4 isn't workable for me yet. I find IPv4 NAT icky.
I'll try to push to have at least a few servers set up at this location immediately, so anyone who wants to have their service migrated can do so, if anyone is interested in providing early feedback on the network.
I'd be fine with migrating early from Chicago to OKC to help test things out, but only with dedicated IPv4.
A little more clarification on how it would work for the "VirMach" portion of OKC.
It'd be exactly the same. We'd used leased IPv4, likely with however frequent renumberings that occur and any limitations. Same control panel, plans, and server specifications. This would just receive "official" IPv6 support as our first location that does for VirMach, and it is planned to be with IPv4 NAT for that portion, with static IPv4 (our own, it could technically still be renumbered at some point but the process more within our control.) This means the IPv6 portion still relies on our in-house system which has not yet been fully coded out.
In regards to IPv6, this still means if you want day one guaranteed support for it and it being treated as the primary connectivity, it'd be under a different sub-brand (it could potentially be done loosely where it's still technically VirMach.)
@AlwaysSkint said: As always, I'm game to be a Guinea Pig. I have a surplus of VPS in NYC, so easy to find a migration candidate, though IPv4 is my modus operandi.
@FrankZ said:
I'm in for OKC as well. Should be interesting.
I look forward to the launch 🚀 🚀
@Wonder_Woman said:
I've got plenty of services to migrate for testing
Only one thing I can think of that would likely be a restriction: it can't be a service with more than one IPv4 for the time being as we're going to be insanely short on them.
@VirMach said: Only one thing I can think of that would likely be a restriction: it can't be a service with more than one IPv4 for the time being as we're going to be insanely short on them.
If Chicago is the preferred, or only location, that can me migrated to OKC I'd be willing to give up my 3 extra IPv4 to do so. An appropriate price reduction would be appreciated, but is not required. If Atlanta, NYC, or Los Angeles can be migrated to OKC then I have single IPv4 VMs that can be used.
@yoursunny said:
It appears that the New York migration has resulted in total data loss.
Booting from Hard Disk...
Boot failed: not a bootable disk
No bootable device.
GParted has detected a 15GB block device without any partition:
SolusVM says the server should have 60GB storage, not 15GB.
We are losing millions per hour.
Ticket Created #122818
It's been one week.
We are losing millions and all we got is a lousy message:
We're currently experiencing communication issues with the server management system. Basic information is displayed below. Full controls will be restored once connectivity is re-established.
OPTIONAL RYZEN UPGRADE
There's no reason for us to set up older hardware if you would prefer to pay an additional amount to upgrade to a Ryzen server instead. We will allow anyone to upgrade their service if desired, when migrating. This must be selected/arranged before migration occurs and cannot be altered at a later time. We will have a set deadline, at a future time per our communication.
Switch to Ryzen 3700X/5600X or Equivalent + NVMe
We will decide on a suitable Ryzen processor. This may range from 6 to 8 cores and generally be in the $200 to $300 price range, with 65W TDP.
Your 2x1TB SSD option will change from SATA to 2x 1TB NVMe SSD.
RAM amount will most likely be 32GB DDR4 but we may provide 64GB DDR4 at an additional cost to be determined based on RAM pricing at time of deployment (+$10-15/MO.)
Additional Cost:
+$350 ONE-TIME | OR | +$200/YR | OR | +$40/MO
These are not meant to be an "upsell" so please do not feel obligated. In fact, this ends up costing us more money so we discourage it
Example:
E3-HDL purchased for $27.30/MO or $273/YR becomes $67.30/MO or $473/YR with no setup fees. Or, optionally remain at $27.30/MO or $273/YR with $350 one-time fee.
@yoursunny said:
It appears that the New York migration has resulted in total data loss.
Booting from Hard Disk...
Boot failed: not a bootable disk
No bootable device.
GParted has detected a 15GB block device without any partition:
SolusVM says the server should have 60GB storage, not 15GB.
We are losing millions per hour.
Ticket Created #122818
It's been one week.
We are losing millions and all we got is a lousy message:
We're currently experiencing communication issues with the server management system. Basic information is displayed below. Full controls will be restored once connectivity is re-established.
We finally got a reply:
We apologize for the billions of dollars in revenue losses. We've assigned this to our Director of Customer Success Engineering, and they should reach out soon to set up a 20-30 minute Zoom call to get this straightened out. I'll provide an update in the next 30 minutes to 36 business hours.
Since we don't have Zoom, we called +1 800 877 2176 the phone number listed on VirmAche website.
The voice identified himself as Mr Ouwye Sofia Lane, the Director of Customer Success Engineering, and told us to pound sand.
Following the suggestion, we went outside to pound sand.
When we came back from the sand pit, the VPS has came back from the dead, and all of the data has been restored.
Can anyone else confirm that netboot.xyz does not work with Virmach anymore.
I've tried on multiple VPS with multiple distributions.
Kernel is fetched, initrd is fetched, and then it just loops right back to the menu.
@abjr said:
Can anyone else confirm that netboot.xyz does not work with Virmach anymore.
I've tried on multiple VPS with multiple distributions.
Kernel is fetched, initrd is fetched, and then it just loops right back to the menu.
just use grub to boot. it hasn't been working for long time
@abjr said:
Can anyone else confirm that netboot.xyz does not work with Virmach anymore.
I've tried on multiple VPS with multiple distributions.
Kernel is fetched, initrd is fetched, and then it just loops right back to the menu.
just use grub to boot. it hasn't been working for long time
Are you suggesting grub can do a network install? This is news to me.
Comments
Oregon, Utah, and Colorado were all being considered. However, the location we'll be launching is Oklahoma City.
OKC Launch
We're going to be doing this location a little bit differently. I wanted to confirm with you guys that this finally is moving forward. I was going to wait until we actually got it done, but it's probably a good idea to gather some feedback at an earlier stage so we can make any requested changes more easily.
This will likely be initially done as an unofficial launch, as we figure things out. So maybe watch out for an interesting sale. We're also doing our own network for the first time and there will be some type of disclaimer about that.
Network - As currently planned
Network will be done with an IPv6 focus, where possible + IPv4 NAT. We may provide dedicated IPv4 at either a high setup cost, or for certain line of services (generally at about +$5/YR extra as per usual but no price lock.)
Software & Branding - As currently planned.
So as I mentioned, we're going to be doing this location differently and that also includes likely using VirtFusion or some other system that does better with IPv6. These services may end up under their own branding, other than some exceptions. We may also finally want to do proper "cloud" using Fleio/OpenStack.
It will also be the first location where we "officially" try to do IPv6 for the VirMach brand, where we'll have a portion of the servers dedicated to this brand and do it the same way (with SolusVM.)
Hardware - As currently planned
We'll be building out dedicated servers to rent to customers directly. The focus will be mainly on Ryzen dedicated servers as planned several years ago. We'll honor these at agreed upon previous pricing for any dedicated server customers that purchased E3 to upgrade to Ryzen (someone remind me on the specific promises so we can try to get this done.) Likely Ryzen 2600 to 3700X, but potentially up to 3800X depending on how the budget is split. We may try to keep the MSRP the same on all variations, kind of like a hybrid grab bag, so they will likely not be "stacked out" but instead balanced, lopsided in some way (more RAM, more CPU, or more disk.) Just got 40 motherboards delivered.
We will also try to do some interesting things with anything left over. We still technically have hundreds of E3's, some E5's, as well as older GPUs.
Colocation Product - As currently planned
I wanted to give a little more information and general planned pricing for this, for anyone interested.
$69/MO - Per 1U/1A 208V/100Mbps (or 50TB @ 1Gbps)
Included per 1U:
Optional additions:
Timeline - As currently planned
We'll likely have the first cabinet ready first or second week of April, with Cogent coming in Mid-April and Lumen by the end of the month. I'm currently trying to decide on routers and have those ordered in as well.
I'll try to push to have at least a few servers set up at this location immediately, so anyone who wants to have their service migrated can do so, if anyone is interested in providing early feedback on the network.
announcing a major product launch on page 361 of a complaints thread...
All very interesting.
As always, I'm game to be a Guinea Pig. I have a surplus of VPS in NYC, so easy to find a migration candidate, though IPv4 is my modus operandi.
Available for immediate migration: " AbandonedJaunty-VM" id=721293 (chosen due to single IPv4: a multi-IP is also available should you wish to challenge a SolusVM to Virtfusion migration.)
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
I'm in for OKC as well. Should be interesting.
I look forward to the launch 🚀 🚀
As with @AlwaysSkint , I'm always game to test.
In for the testing. Lumen is generally prem.
Good luck, fingers crossed!
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals | VirMach Flash Sales Notifier
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
Hello, @VirMach .
Could you please reply my ticket #238520? It has almost been 6 weeks.
If you are busy at your current work, maybe at least tell me in this thread when my ticket will be reviewed so I don't have to check it every day??
I like it!
Ouch. I like IPv6, but losing IPv4 isn't workable for me yet. I find IPv4 NAT icky.
I'd be fine with migrating early from Chicago to OKC to help test things out, but only with dedicated IPv4.
Virtfuuuuuuuuuuuuuuuuuuuuuuusion
I bench YABS 24/7/365 unless it's a leap year.
I am in for OKC @VirMach
I've got plenty of services to migrate for testing
Is 1200GB NVMe server finally here?
Where are the deals?
i'd be happy to migrate anything left in CHI to OKC to beta
Is it routed ?
No hostname left!
A little more clarification on how it would work for the "VirMach" portion of OKC.
It'd be exactly the same. We'd used leased IPv4, likely with however frequent renumberings that occur and any limitations. Same control panel, plans, and server specifications. This would just receive "official" IPv6 support as our first location that does for VirMach, and it is planned to be with IPv4 NAT for that portion, with static IPv4 (our own, it could technically still be renumbered at some point but the process more within our control.) This means the IPv6 portion still relies on our in-house system which has not yet been fully coded out.
In regards to IPv6, this still means if you want day one guaranteed support for it and it being treated as the primary connectivity, it'd be under a different sub-brand (it could potentially be done loosely where it's still technically VirMach.)
Only one thing I can think of that would likely be a restriction: it can't be a service with more than one IPv4 for the time being as we're going to be insanely short on them.
I'll make a weird dedicated server for you and let you know in case you're interested.
We're likely going to to purchase a router, maybe an MX480. Otherwise I'll just plug in the Cogent 1G line into one server directly.
That rules out my remaining Chicago VPS, for now.
Looking forward to seeing what you come up with.
:popcorn:
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
If Chicago is the preferred, or only location, that can me migrated to OKC I'd be willing to give up my 3 extra IPv4 to do so. An appropriate price reduction would be appreciated, but is not required. If Atlanta, NYC, or Los Angeles can be migrated to OKC then I have single IPv4 VMs that can be used.
Damn, I only have one at the locations which I currently have. Guess I have to look for a neat virbot deal to migrate to OKC.
The Ultimate Speedtest Script | Get Instant Alerts on new LES/LET deals | Cheap VPS Deals | VirMach Flash Sales Notifier
FREE KVM VPS - FreeVPS.org | FREE LXC VPS - MicroLXC
@VirMach ,Hello, could you please check my ticket #269887? I am unable to log in to pay my bill. Thank you!
It's been one week.
We are losing millions and all we got is a lousy message:
We're currently experiencing communication issues with the server management system. Basic information is displayed below. Full controls will be restored once connectivity is re-established.
No hostname left!
@Virmach - correction to the above mentioned ID (didn't realise it had 2IP).
Both/either available for migration: 720387 (ATL) & 720538 (NYC)
It wisnae me! A big boy done it and ran away.
NVMe2G for life! until death (the end is nigh)
Good evening
@Virmach, when can we move to OKC?
and what should be in the subject of the ticket, "move this to OKC"?
Feel free to take my handful of idlers extremely important servers left in Chicago and move them to OKC if they abide.
I have too much NYC and... 40 something others.
Hey @VirMach
Please stop the planet! I wish to get off!
We finally got a reply:
We apologize for the billions of dollars in revenue losses. We've assigned this to our Director of Customer Success Engineering, and they should reach out soon to set up a 20-30 minute Zoom call to get this straightened out.
I'll provide an update in the next 30 minutes to 36 business hours.
Since we don't have Zoom, we called +1 800 877 2176 the phone number listed on VirmAche website.
The voice identified himself as Mr Ouwye Sofia Lane, the Director of Customer Success Engineering, and told us to pound sand.
Following the suggestion, we went outside to pound sand.
When we came back from the sand pit, the VPS has came back from the dead, and all of the data has been restored.
No hostname left!
Can anyone else confirm that netboot.xyz does not work with Virmach anymore.
I've tried on multiple VPS with multiple distributions.
Kernel is fetched, initrd is fetched, and then it just loops right back to the menu.
just use grub to boot. it hasn't been working for long time
I bench YABS 24/7/365 unless it's a leap year.
Are you suggesting grub can do a network install? This is news to me.