@january1073 @kenji eben, und deshalb habe ich sogar nen #CloudExit mit begleitet...
@january1073 @kenji eben, und deshalb habe ich sogar nen #CloudExit mit begleitet...
@CursedSilicon @drscriptt @Tvorsk @jima @qlp not really.
@werawelt @PC_Fluesterer Ja, und wegen solcher shice habe ich auch schon nen #CloudExit eines Unternehmens begleitet.
@neurovagrant @Viss #Funfact: I did work on a #CloudExit for a company in 2020 as they wanted to cut costs and investing into #OwnHardware & #Colocation was demed the best choice.
#decloud was also seen as a necessity to protect against #CorporateEspionage!
@anne_twain nodds in agreement
I helped (fmr.) employers to #CloudExit several times...
@MattHatton consider #JTL?
Can testify as someone who used to work for them several years ago. These guys are legit and did a #CloudExit cuz the numbers said so!
@doerk Natürlich wird sowas immer teurer sein...
Ich habe 2020 schon Firmen geholfen, nen "Cloud Exit" zu machen und konsequent inhouse zu konsolidieren.
Außerdem erlaubt es Kontrolle und Compliance mit Datenschutz und IT-Sicherheit, welche Firmen mit Niederlassungen (oder auch nur Zweigstellen, nicht nur Sitz!) in den USA [wie auch "V.R." China] nicht einhalten können, weil Cloud Act das denen verbietet!
@uastronomer it's something I.did implement in the past (abeit #KVM + #Proxmox, but the steps are similar enough):
You can seperate #Storage and #Compute given you have a Storage-LAN that is fast enough (and does at least 9k if not 64k Jumbo Frames) and have the "Compute Nodes" entirely #diskless (booting via #iPXE from the #SAN) and then mount the storage via #iSCSI or #Ceph.
Did a bigger project (easily 8-digits in hardware, as per MSRP) where a Employer/Client did #CloudExit amidst escalating costs and #ROI being within quarters (if not months at the predicted growth rate)...