Reply to Thread
Results 1 to 6 of 6

Thread: Procedure for maintenaces

  1. #1
    Jolly Advisor
    Join Date
    Aug 2012
    Location
    At the end of Universe
    Posts
    114
    World
    Sandycove

    Lightbulb Procedure for maintenaces

    Hi,

    I'm going to suggest you just one thing that you can include in your procedure for maintenance and execution of scripts: Create a copy of the DB/Server in a temp space and execute all scripts that you're planning to include during the maintenance.

    Benefits:
    • You can tell if it's going to work as expected
    • You can estimate the time required to do the same in production
    Remember, remember the 25/11? You should have seen what happened on 17/03, 14/04 and 21/04 ...
    29/09 seems to be a major problem...

  2. #2
    Pathfinder
    Join Date
    Oct 2013
    Posts
    1
    World
    Newfoundland
    Howmuch ever testing one does in the test server, things will still break in the production space!

  3. #3
    Jolly Advisor
    Join Date
    Aug 2012
    Location
    At the end of Universe
    Posts
    114
    World
    Sandycove
    Quote Originally Posted by Kismu View Post
    Howmuch ever testing one does in the test server, things will still break in the production space!
    I'm not talking about the test server. I'm talking about the real production environment. If they snapshot it and experiment over the snapshot they'll know what might break or actually take forever to complete.
    Remember, remember the 25/11? You should have seen what happened on 17/03, 14/04 and 21/04 ...
    29/09 seems to be a major problem...

  4. #4
    Committed Clicker
    Join Date
    Jun 2012
    Location
    My island
    Posts
    255
    World
    Sandycove
    This should never have happened.

    The test server doesn't get properly utilized, it goes for days without anyone bothering to check if its even working. Updates which cause problems seem to go unnoticed, random server wipes and an awful pre-build island that most level 50 players would find unacceptable.
    Every player on the test server has the same resources so trade is meaningless, when players need to test new features they have to wait days for explorers to find adventures before being able to test and report bugs. Its no wonder so few people were able to test the recently added adventures.

  5. #5
    Jolly Advisor
    Join Date
    Aug 2012
    Location
    At the end of Universe
    Posts
    114
    World
    Sandycove
    Quote Originally Posted by Peajay View Post
    This should never have happened.

    The test server doesn't get properly utilized, it goes for days without anyone bothering to check if its even working. Updates which cause problems seem to go unnoticed, random server wipes and an awful pre-build island that most level 50 players would find unacceptable.
    Every player on the test server has the same resources so trade is meaningless, when players need to test new features they have to wait days for explorers to find adventures before being able to test and report bugs. Its no wonder so few people were able to test the recently added adventures.
    And again I'm not speaking about the public test server, they can have an internal copy for their own development purposes. Most decent companies follow such procedures.
    Remember, remember the 25/11? You should have seen what happened on 17/03, 14/04 and 21/04 ...
    29/09 seems to be a major problem...

  6. #6
    Ruler of the Land Xibor's Avatar
    Join Date
    Sep 2014
    Location
    New Zealand
    Posts
    1,714
    World
    Sandycove
    Quote Originally Posted by MCLueppers View Post
    And again I'm not speaking about the public test server, they can have an internal copy for their own development purposes. Most decent companies follow such procedures.
    I completely agree. In fact, my specific job is to maintain a QA environment which mirrors the production environment in every possible way (there are always compromises - e.g. I can't have 10k users online to my servers at the same time) but overall the hardware, software, networking, etc. are all mirrors of production. In fact, my test machiens run virtualized on exactly the same hardware as production which is also virtualized exactly the same way. All code is tested in the QA environment first before being deployed to production for the users to pick up.

    I'm in a mainframe environment so I can't speak to the kind of hardware/software used by the game but I know the principles are the same and was quite surprised the developers/operators/administrators clearly had 'no idea' telling me they had not tried it yet - at least not in a comparative environment.
    Sorry, but I've slept since then...

Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Ubisoft uses cookies to ensure that you get the best experience on our websites. By continuing to use this site you agree to accept these cookies. More info on our privacy.