| Author |
Thread Statistics | Show CCP posts - 12 post(s) |
|
Sharkbait
   |
Posted - 2006.11.22 15:44:00 -
[1]
Basically on Thursday 23rd of November we plan to put the revelations code branch onto TQ and test a few basic things.
Server startup (does the server start up correctly).
Market startup (does the market services start correctly).
Agent missions (is it possible to use agents as intended).
Session changes (can you jump between systems, lose your ship, swap ships etc).
These are some of the main problems we have everytime we do such a big patch. With the release of Dragon, the problems we had was that the server wouldnĘt start correctly and when that was fixed the **** market wouldnĘt start in all regions. With the tests we have planned, we hope to iron out these problems and catch them before we do the full release.
We have a battle plan in office exactly how we are going to do this. The server will remain closed, so only CCP personal can connect. The main reason for this is we only have a 10 min time frame, so we do not want any lag and we will not be using TQĘs database, we will be using SISIĘs. ItĘs not possible to use TQĘs database because it would mean updating it to the revelations code branch and that simply isnĘt possible as we need to revert TQ back to dragon.
Hopefully if all goes well we can do this on Thursday, Friday and Monday. We really hope we will find any problems we might have on the Thursday, Friday then have a stable test on the Monday and do more advanced tests after that. Helping to make deployment a smooth ride.
Normal operations of TQ will continue as normal. The cluster will be started at 11:45 and will allow connections about 12:00.
As a lot of you peeps have been around some time now, you will understand why we want and need to do this.
Spank You later |
|
|
Huitzilopochtli Tlaloc
Forum Moderator
Interstellar Services Department
|
Posted - 2006.11.22 15:47:00 -
[2]
Good luck finding all thouse bugs, though im sure you dont need it  . Sounds like a wise precaution after dragon problems.
- Thanks Hutch.
____
forum rules | Email us
They call me "Hutch" because my name is well... long
Actually we call you "Hutch" because people might get the wrong idea of 'God of Young Boys' - Cortes, sigjacker extrodinaire
You can't match my sig-jacking skills Cortes!! Oh and we call you Hutch because your the anti-Hitch - Petwraith |
|
|
Eldo Davip
Forum Moderator
Interstellar Services Department
|
Posted - 2006.11.22 17:39:00 -
[3]
Glad to see new measures being taken to improve patch day! Goodluck Sharky!
___
Email Us (Report a bad post) | Forum Rules | Website
EvE +NLINE - T+TALHELLDEATH SUPPORTER
|
|
|
Sharkbait
|
Posted - 2006.11.22 21:47:00 -
[4]
i'll be honest. it's not been done before and we don't know for sure it will help us. but unless we try, we gain nothing. if it doesn't work only thing we have lost is a few hour in the day for a few people. got to be worth it imo.
however, if it works. well it will make deployment smoother and it's something CCP can do for other large patches
Spank You later |
|
|
Valar
|
Posted - 2006.11.23 09:09:00 -
[5]
 Originally by: Ralitge boyter
How certain are you that after the upgrade the downgrade will be just as smooth?
As far as I know there has never been a downgrade of TQ like that, so we might just loose a day or two of TQ due to issues downgrading and starting up the market or the agent missions and so on.
Anyway I'll see about sacrificing a goat or two and of course setting a very long skill in training. 
Well, you don't have to worry. We are not actually upgrading anything or changing anything thats related to the normal operation of TQ. We will deploy the Kali code in a separate folder on the cluster, running on a separate database server, so the normal TQ code/database will not be touched at all. All we have to do to revert is to kill the Kali processes on the cluster and start up TQ like normally.
------
Valar
Database admin - Server operations team
CCP Games
How to write a good bugreport |
|
|
Sharkbait
|
Posted - 2006.11.23 10:18:00 -
[6]
ok we are finalizing the setup now and will be ready in 10 mins or so. there is 3 of us who will be reviewing the logs for errors after we have finished. i will ofcourse keep you updated with information as we get the information.
Spank You later |
|
|
Sharkbait
|
Posted - 2006.11.23 11:48:00 -
[7]
ok. status.
we had problems. we tried 3 startup's and none of them worked. while this sounds bad, it's really good as we might have had these problems when we deployed. me, zulupark and nozh are reading the logs now and i will try to give you more information.
Spank You later |
|
|
Sharkbait
|
Posted - 2006.11.23 12:00:00 -
[8]
TQ is now back online running Dragon code branch and allowing connections
Spank You later |
|
|
Sharkbait
|
Posted - 2006.11.23 23:03:00 -
[9]
ok some of the problems we had today have been sorted and will not effect us on deployment. we are doing another run tomorrow, hopefully we can get the server started. if not then i'm 99% sure that it will be something else we will have on deployment day.
anyways we will see. fingers crossed guys and gals
Spank You later |
|
|
Sharkbait
|
Posted - 2006.11.24 14:02:00 -
[10]
hit a few problems today, we kept having nodes dying on startup. not sure why yet but it's being looked into. looks like these tests are worth us doing 
hopefully we can maybe get some more done this weekend, but i need to get clearance from the higher powers for that.
Spank You later |
|
|
Sharkbait
|
Posted - 2006.11.25 15:14:00 -
[11]
we are not able to do them this weekend. part of the problem we are having is a firewall between sisi's database and the network TQ is on. security on the network is very high in the office and even higher in the server room in london. TQ and sisi are on different networks and are only linked through a firewall. this firewall is causing us problems. we are going to try again on monday and see if we can do it then.
Spank You later |
|
|
Sharkbait
|
Posted - 2006.12.03 16:09:00 -
[12]
sry forgot to respond to this post, been very busy 
basically the tests we tried to do was almost worthless we think. the firewall was causing some problems and it's quite possible some of the errors we saw in the logs was due to the firewall. it's also possible that there might have been errors in the logfiles that also happened on deployment night, but i dismissed them and blamed them on the firewall. there was 1 problem we had on the trials that i'm 50% sure we had on deployment night, basically it's the information passed between each node at startup was too high and screwing things up, this did happen on the trials but it could have been the firewall blocking the information and therefore screwing the nodes up.
anyways as we didn't effect TQ's normal operations with the trials, it's very possible the higher powers will let us try this again. over the next month or 2 we will be looking at a way we can try this again and maybe use the method for the 2nd part of revelations.
Spank You later |
|
| |
|