Navigation

    TripleA Logo

    TripleA Forum

    • Register
    • Login
    • Search
    • TripleA Website
    • Categories
    • Recent
    • Popular
    • Users
    • Groups
    • Tags

    Dev Status Update (2.7)

    Development
    3
    3
    17
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • LaFayette
      LaFayette Admin last edited by

      On the 2.7 TODO list:

      • launch maps server
      • launch support server
      • make lobby deploy with zero downtime
      • game client should automatically reconnect to lobby on disconnect

      As part of the server work there were some large devops pieces to work through. Getting one server done helps a lot to create a pattern for the others.

      I got the maps-server much further along and started on the support server. It soon became kinda evident that it would be easier if the support & maps-server were just one server.

      In the end, we will have two servers on the backend: "support" + "lobby". Before, we had just one server (lobby). Because it was a server and conveniently set up, we added "support" capabilities to the existing lobby. Part of this effort is to 'move' those capabilities (eg: error reporting) out of the lobby server to the support server. At the same time, the 'map indexing' capabilities that were going to be part of the dedicated 'maps server' will now be wrapped into the 'support server'

      The support server will have the following responsibilities:

      • get maps
      • get latest TripleA version
      • post error reports

      I have completed a blue/green deployment script for the lobby, so it does deploy now with zero downtime. Specifically, a second lobby fires up to take over traffic while the first one is taken down and upgraded, then the new secondary spins down after the first one comes back up.

      Which leaves some work on the client side to automatically reconnect to the lobby. That will make a deployment almost fully transparent.

      So, roadmap:

      • combine support+maps server
      • wrap up devops stuff for the maps server and port that over to the lobby
        operationalize the now single support server. (A) the support (prevously called maps) server had issues the last time it launched. Specifically map indexing broke and stopped. We will want to see the map indexing operate without any crashes for some period of time. (B) bare-bones implementatoin gets teh job done, but we really need a nice way to manage maps tags & be able to see map-indexing status. I think we will want the support server to provide a couple HTML pages to show indexing and provide tag-admin support
      • make game client automatically reconnect to the lobby & do some testing to be sure that a disconnect from lobby is as transparent as possible
      B ubernaut 2 Replies Last reply Reply Quote 3
      • B
        beelee @LaFayette last edited by

        @lafayette

        Right arm RightArm.png

        So we're not quite ready for lobby testing just yet then ?

        1 Reply Last reply Reply Quote 1
        • ubernaut
          ubernaut Moderators @LaFayette last edited by

          @lafayette thanks for all ur hard work! 🙂

          side note, marti has been a mess for a while now can i submit that for attention?

          feel like that issue has a significant user experience impact

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post
          Copyright © 2016-2018 TripleA-Devs | Powered by NodeBB Forums