shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

255
active users

#cloudexit

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@january1073" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>january1073</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@kenji" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kenji</span></a></span> eben, und deshalb habe ich sogar nen <a href="https://infosec.space/tags/CloudExit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CloudExit</span></a> mit begleitet...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.restless.systems/@CursedSilicon" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>CursedSilicon</span></a></span> <span class="h-card" translate="no"><a href="https://oldbytes.space/@drscriptt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>drscriptt</span></a></span> <span class="h-card" translate="no"><a href="https://meow.social/@Tvorsk" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Tvorsk</span></a></span> <span class="h-card" translate="no"><a href="https://mspsocial.net/@jima" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jima</span></a></span> <span class="h-card" translate="no"><a href="https://linh.social/@qlp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>qlp</span></a></span> not really.</p><ul><li>I did help a company do <a href="https://infosec.space/tags/CloudExit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CloudExit</span></a>!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://social.tchncs.de/@werawelt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>werawelt</span></a></span> <span class="h-card" translate="no"><a href="https://social.tchncs.de/@PC_Fluesterer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>PC_Fluesterer</span></a></span> Ja, und wegen solcher shice habe ich auch schon nen <a href="https://infosec.space/tags/CloudExit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CloudExit</span></a> eines Unternehmens begleitet.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://masto.deoan.org/@neurovagrant" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>neurovagrant</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@Viss" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Viss</span></a></span> <a href="https://infosec.space/tags/Funfact" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Funfact</span></a>: I did work on a <a href="https://infosec.space/tags/CloudExit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CloudExit</span></a> for a company in 2020 as they wanted to cut costs and investing into <a href="https://infosec.space/tags/OwnHardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OwnHardware</span></a> &amp; <a href="https://infosec.space/tags/Colocation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Colocation</span></a> was demed the best choice.</p><ul><li>Was a cool reference project with brand-spaning new hardware!</li></ul><p><a href="https://infosec.space/tags/decloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>decloud</span></a> was also seen as a necessity to protect against <a href="https://infosec.space/tags/CorporateEspionage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CorporateEspionage</span></a>!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://theblower.au/@anne_twain" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>anne_twain</span></a></span> <em>nodds in agreement</em></p><p>I helped (fmr.) employers to <a href="https://infosec.space/tags/CloudExit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CloudExit</span></a> several times...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://aus.social/@MattHatton" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>MattHatton</span></a></span> consider <a href="https://infosec.space/tags/JTL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JTL</span></a>?</p><ul><li>Cuz they ain't such <em>hype-driven</em> weirdos.</li></ul><p>Can testify as someone who used to work for them several years ago. These guys are legit and did a <a href="https://infosec.space/tags/CloudExit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CloudExit</span></a> cuz the numbers said so!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://nrw.social/@doerk" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>doerk</span></a></span> Natürlich wird sowas immer teurer sein...</p><p>Ich habe 2020 schon Firmen geholfen, nen <em>"Cloud Exit"</em> zu machen und konsequent <em>inhouse</em> zu konsolidieren.</p><ul><li>Das kostet initiell schon was, aber die Investition rentiert sich z.T. binnen weniger Quartale oder gar Monaten!</li></ul><p>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 <em>"V.R."</em> China] nicht einhalten können, weil <em>Cloud Act</em> das denen verbietet!</p><p><a href="https://infosec.space/tags/Cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cloud</span></a> <a href="https://infosec.space/tags/CloudExit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CloudExit</span></a> <a href="https://infosec.space/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelfHosting</span></a> <a href="https://infosec.space/tags/OnSite" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OnSite</span></a> <a href="https://infosec.space/tags/OnPremise" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OnPremise</span></a> <a href="https://infosec.space/tags/Colocation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Colocation</span></a> <a href="https://infosec.space/tags/Housing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Housing</span></a> <a href="https://infosec.space/tags/GAFAMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GAFAMs</span></a> <a href="https://infosec.space/tags/CloudAct" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CloudAct</span></a> <a href="https://infosec.space/tags/GDPR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GDPR</span></a> <a href="https://infosec.space/tags/BDSG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BDSG</span></a> <a href="https://infosec.space/tags/DSGVO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DSGVO</span></a> <a href="https://infosec.space/tags/Datenschutz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Datenschutz</span></a> <a href="https://infosec.space/tags/ITsicherheit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ITsicherheit</span></a> <a href="https://infosec.space/tags/Compliance" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Compliance</span></a> <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ITsec</span></a> <a href="https://infosec.space/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoSec</span></a> <a href="https://infosec.space/tags/OpSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpSec</span></a> <a href="https://infosec.space/tags/ComSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ComSec</span></a> <a href="https://infosec.space/tags/ROI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ROI</span></a> <a href="https://infosec.space/tags/Investment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Investment</span></a> <a href="https://infosec.space/tags/USA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>USA</span></a> <a href="https://infosec.space/tags/PRC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PRC</span></a> <a href="https://infosec.space/tags/China" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>China</span></a> <a href="https://infosec.space/tags/Cyberfaschismus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Cyberfaschismus</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.monoceros.co.za/@uastronomer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>uastronomer</span></a></span> it's something I.did implement in the past (abeit <a href="https://infosec.space/tags/KVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KVM</span></a> + <a href="https://infosec.space/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Proxmox</span></a>, but the steps are similar enough):</p><p>You can seperate <a href="https://infosec.space/tags/Storage" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Storage</span></a> and <a href="https://infosec.space/tags/Compute" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Compute</span></a> given you have a Storage-LAN that is fast enough (and does at least 9k if not 64k Jumbo Frames) and have the <em>"Compute Nodes"</em> entirely <a href="https://infosec.space/tags/diskless" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>diskless</span></a> (booting via <a href="https://infosec.space/tags/iPXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iPXE</span></a> from the <a href="https://infosec.space/tags/SAN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SAN</span></a>) and then mount the storage via <a href="https://infosec.space/tags/iSCSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iSCSI</span></a> or <a href="https://infosec.space/tags/Ceph" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ceph</span></a>.</p><ul><li>Basically it allows you to scale Compute and Storage independently from each other as they are transparent layers and not be confined to limits of a single chassis &amp; it's I/O options...</li></ul><p>Did a bigger project (easily 8-digits in hardware, as per MSRP) where a Employer/Client did <a href="https://infosec.space/tags/CloudExit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CloudExit</span></a> amidst escalating costs and <a href="https://infosec.space/tags/ROI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ROI</span></a> being within quarters (if not months at the predicted growth rate)...</p>