Jump to content

June 2020 Donations & Finances


Cipher
 Share

Recommended Posts

  • Homecoming Team

Hello everyone!

 

In the upcoming month, we will be making some changes to our hardware infrastructure in order to reduce our long-term operating costs, help us utilize our existing hardware more efficiently, and aid with future development. The up-front cost for these changes will be $1,316.94 broken up as:

  • $971.97/month - purchase of 3x Advance-4 servers configured with:
    • 256GB of memory
    • 2x1920GB NVMe SSDs
    • 1Gbps Private (vRack) bandwidth
  • $344.97 one time setup fee

 

These changes will allow us to remove the following hardware from our current infrastructure:

  • 5x Advance-1 servers ($102.99 each)
  • 2x Advance-2 servers ($108.99 each)
  • 1x Advance-4 server ($377.99)

 

Once the changes have been made and we have removed the older hardware from our infrastructure, the reduction to monthly operating costs will be $138.95.

 


May 2020 Breakdown

Last month we accepted $5,297.72 in donations - $123.40 over our target for the month.

 

Here is the breakdown of what May’s funds went towards:

  • $4,820.39 to OVH for our hosting
  • $199.99 to GoDaddy for the 1-year renewal of the code signing certificate
    • This is the $199.99 withdraw to bank account - this was not charged directly from our PayPal
  • $132.00 for our UPS business address (6-month renewal)
  • $120.69 for our Google G-Suite Business account
  • $75.00 for our 6-month Invision Community software renewal
  • $25.00 for the Paperspace Air instance
  • $10.00 for our Atlassian Jira Cloud instance (10-user)
  • $9.73 for the security / administration software
  • $5.52 for a droplet on DigitalOcean which was used for testing network changes

 

image.png.e065204d6f54337a7f817af569676ec9.png

 


June 2020

We were left with a $49.53 deficit at the end of May due to changing invoice amounts; this amount will be included in the donation target for June to ensure that we maintain our $1,250 contingency fund. Additionally, we have received the latest invoice from our primary law firm totaling $131.59.

 

In total, the donation target for June 2020 is $6,513.87. Here is a breakdown of how the funds are allocated:

  • $4,820.39 to OVH for our hosting
    • + $1,316.94 to make the aforementioned changes to our infrastructure
  • $131.59 to our primary law firm for services rendered
  • $120.69 for our Google G-Suite Business account
  • $49.53 to recoup the deficit from May
  • $30.00 for our 1&1 IONOS domain & outbound email service
  • $25.00 for the Paperspace Air instance
  • $10.00 for our Atlassian Jira Cloud instance (10-user)
  • $9.73 for the security / administration software

 


 

The donation target has been met and donations have been closed. Thank you for the support!

 

Our donation system will be open as of the time of this post with a donation target of $6,513.87 and will automatically close once that target is met.

 

As always, thank you for all of the support!

 

- The Homecoming Team

  • Like 3
  • Thanks 4

Cipher

Homecoming Team

 

If you need help, please submit a support request here or use /petition in-game.

 

Got time to spare? Want to see Homecoming thrive? Consider volunteering as a Game Master!

Link to comment
Share on other sites

Yay! Made it this time!

Mostly on Torchbearer, but if you ever see me on, feel free to say hello!

Astral.Kai - Peacebringer; Dark.Enforcer - Dark/Shield Scrapper; Spark.Enforcer - Electrical/Shield Scrapper; Shadow.Reign - Dark/Regen Brute;

Glitter - Warshade;

And others to be added as I get them up to snuff, lol!

 

Link to comment
Share on other sites

I missed the window for the first time in months.  But, I'm happy that the enthusiasm for CoH, and Homecoming are still so high that the windows close this quickly!  I'll get ya next month!

  • Like 1

What was no more, is REBORN!

Link to comment
Share on other sites

  • Homecoming Team
1 hour ago, Peerless Girl said:

Going to presume one of those will be in Europe, and the other 2 in the US area, one probably for backend/dev stuff or beta servers. Just my guess. But the systems have so many available threads and cores they can divide them up a lot of ways. 

 

All three of these will actually be placed in our NA data center. Read on for more details!

 

Reunion

Reunion's already a bit of the odd one out - we've got a mini-cluster of three hosts in EU for it (the shard host itself, the SQL database host, and the mapserver host). The hardware there is a little bit overprovisioned for Reunion's actual load, but we've found a number of creative additional uses for it to use that spare capacity without affecting player experience (for example, the SQL host also has bulk storage attached and serves as one of our backup tiers and our WSUS update server in addition to its normal SQL duties). We don't have any plans to change the EU cluster at this time since doing so would probably be an increase in costs or decrease in flexibility without any gains.

 

The A1s and the A4

When we originally built the Homecoming cluster a year ago, we allocated physical hardware for each shard's main host, as well as a separate host just for running authentication (the five A1s mentioned above). Since then, we've done a lot of optimization, fixing memory leaks, and profiling to determine how the cluster scales. In addition, all of our beta and prerelease shards (as well as our build servers) are running entirely on the single A4. So we're now a lot more comfortable running more of our game infrastructure on VMs. This will give us a lot more fault tolerance, since if one goes down we can temporarily run its VMs on the other two. Some of you may also recall the authentication issue a few months ago - that was an actual hardware failure on our physical authentication host, and we had to build a new one as a VM on the fly while that was being fixed.

 

The A2s

Not addressed yet are the two A2s - those are our general purpose VM hosts. While they're not struggling to handle the load, they're actually not as flexible as we had hoped:

- They aren't very good at handling our build infrastructure (which wants lots of cores, but these only have six physical cores each).

- We underestimated how much disk space they would need, so we occasionally have to juggle services to avoid a crunch.

- Because two is no better than one in the world of high availability, we have to run backup instances of some of the services on these hosts on other hosts to ensure they are fully reliable.

 

What's Not Changing

Those of you who have kept up with our other technology posts may remember that we have a few other hosts in NA:

- One more A1 which is used as a citadel host (most places would call this a bastion host, but this is CoH)

- Three A3s which are used as SQL database hosts (two hot and one warm spare)

- Six A5s which are used as mapserver hosts

 

None of these are changing at this time. It's not that we're not confident of our ability to run the services of these hosts on VMs, but after analyzing the required capacity and the types of host we can purchase, we didn't feel there would be any significant cost savings while maintaining our desired reliability and performance criteria.

 

The Future

The net result is that the three new A4s will be running the following:

- The authentication server (and warm spares)

- The four NA live shard hosts (and we'll be able to quickly migrate if there is a failure)

- All hosts for beta and prerelease (shard hosts, services hosts, and mapserver hosts)

- Our forums

- Our development infrastructure and build servers

- Our other infrastructure (e.g. petitions/GM tools, system administration, patch and manifest management, CDN, our Kubernetes cluster).

 

The hardware will be better than what we have now:

- We'll have the same number of physical cores (48 - but note that the A4 cores are superior to the ones in the A1s/A2s, and also that many of our current cores are just not in places where it is convenient to use them)

- We'll have more RAM (544GB -> 768GB).

- We'll have more disk space in the right places (4.5TB -> 6TB).

 

TL;DR

- We'll reduce our footprint and long-term costs, increase our flexibility for future changes, and be more robust.

- Nothing is changing in the EU cluster at this time.

 

Finally, thank you all for donating! We wouldn't be here without you.

  • Like 4
  • Thanks 6
Link to comment
Share on other sites

  • Jimmy unpinned and unfeatured this topic

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...