- Jan 2, 2016
- 130
- 253
@AdrianX
The network is four servers that currently physically reside at my datacenter in Moses Lake, WA, They are under four public IPs that I'm currently paying for on a shared symmetric 1 Gbps internet connection. You can ping them at rome.toom.im, troy.toom.im, athens.toom.im, and memphis.toom.im. (Ancient Mediterranean cities was the naming theme.) They can stay at my facility until at least April 1st, 2020, and possibly until April 1, 2021, depending on how long we continue to operate that facility. After that, we will probably want to move them somewhere else. That's not a big deal, operating costs are low.
Most of the tests that I've been doing with them so far only require a significant amount of LAN bandwidth, electricity, and hearing protection (those things are LOUD), so relocating them elsewhere should be pretty easy. I have them on global IPv4 addresses right now, but they can be migrated to running on IPv6 and/or port-forwarded/NATted IPv4 with some effort. So long term, they can be very cheap to maintain. Like, $30-$100/month plus whatever labor is needed.
I and my employees will maintain them as long as they are at my datacenter, because I can and it's easy and cheap. I may also maintain them afterwards if they're moved somewhere else.
I don't understand what you're suggesting with the leasing agreement. The main cost here is the skilled labor needed to write and run the tests, not the hardware itself. $4k is peanuts. Who would be responsible for implementing those tests? BU? Me? Me on half of BU?
I also don't like the idea of trying to turn this into a profitable business relationship. I wanted to make a test setup, so I did. I want other devs to have access to this test setup, so I'm offering devs access to these rigs. (By the way, devs, message me if you want to play around with these things! Send me an ssh pubkey and I'll make you an account.) If BU wants to reimburse me for my expenses, that's cool. If not, that's cool too. Either way doesn't really matter -- it's not a lot of money.
The network is four servers that currently physically reside at my datacenter in Moses Lake, WA, They are under four public IPs that I'm currently paying for on a shared symmetric 1 Gbps internet connection. You can ping them at rome.toom.im, troy.toom.im, athens.toom.im, and memphis.toom.im. (Ancient Mediterranean cities was the naming theme.) They can stay at my facility until at least April 1st, 2020, and possibly until April 1, 2021, depending on how long we continue to operate that facility. After that, we will probably want to move them somewhere else. That's not a big deal, operating costs are low.
Most of the tests that I've been doing with them so far only require a significant amount of LAN bandwidth, electricity, and hearing protection (those things are LOUD), so relocating them elsewhere should be pretty easy. I have them on global IPv4 addresses right now, but they can be migrated to running on IPv6 and/or port-forwarded/NATted IPv4 with some effort. So long term, they can be very cheap to maintain. Like, $30-$100/month plus whatever labor is needed.
I and my employees will maintain them as long as they are at my datacenter, because I can and it's easy and cheap. I may also maintain them afterwards if they're moved somewhere else.
I don't understand what you're suggesting with the leasing agreement. The main cost here is the skilled labor needed to write and run the tests, not the hardware itself. $4k is peanuts. Who would be responsible for implementing those tests? BU? Me? Me on half of BU?
I also don't like the idea of trying to turn this into a profitable business relationship. I wanted to make a test setup, so I did. I want other devs to have access to this test setup, so I'm offering devs access to these rigs. (By the way, devs, message me if you want to play around with these things! Send me an ssh pubkey and I'll make you an account.) If BU wants to reimburse me for my expenses, that's cool. If not, that's cool too. Either way doesn't really matter -- it's not a lot of money.
Last edited:
