2012-07-13T04:16:00ZOriginally Posted by CCP Navigator
![]()
![]()
etc
2012-07-13T04:16:00ZOriginally Posted by CCP Navigator
![]()
![]()
etc
we will upgrades
Make isk with PICountries do not exist where I am from. The discovery of the Higgs boson led to limitless power, the elimination of poverty and Kit-Kats for everyone. It is a communist chocolate hellhole and I'm here to stop it ever happening.
The Great Tracking Nerf v0.1
My fav ECM alternative
I remember the days when downtimes used to last longer than 10 minutes... My drinks tasted much better since I had time to piss in more suitable containers.
Originally Posted by Random hopeful w-space dweller
what's the problem?
Now I have a T2 gun. Ho, ho, ho.
SHC '10 and proud.
Applied Creations is recruiting. Mystic Volundar says, "It could be you! " =D
*shrug*
1.5 hours to upgrade the firmware on hundreds of high performance switches, followed by 1 hour to handle a hardware migration the day after is rather ballsy, but if they can pull it off then hat's off to them.
I'm fairly sure it is closer to 4 switches.
Edit - Might be just 2 actually: http://community.eveonline.com/devbl...a=blog&bid=769
/
![]()
Are we just being hyperbolic or have we all forgotten about the era of one hour daily down-times already?
Train long skills, hurr durr.
/seems like they have their hardware shit together these days. I haven't been boot.ini'd in like years.
So nobody at CCP knows how to upgrade infrastructure? Why the hell would you try to upgrade everything in one shot? This is something they should be able todo without any service interruption.
Perhaps because the switches/routers in question require the same rev of firmware? This isn't far fetched because of switch stacks, failover, or other such features that require multiple chassis to play nice together in a integrated way. It's hard to know without details, though.
TBH it's the mandatory software upgrade that's telling. Either something's old enough to EOL, or they need some feature, or the supplier is dictating to them in termps of patch schedules & has them by the balls, jumping through hoops, a vendor lock-in proprietary setup.
Yeah, in theory, protocols and standards would let various hardware work together, at least be compatible across firmware versions of the same hardware.
Hello? Oh, hello! I'm sorry it's a very bad line. No, no no... but that's not possible, she was sealed in to the Seventh Obelisk after the prayer meeting. Well, no, I get that it's important... an Egyptian Goddess loose on the Orient Express. In Space. Give us a mo....
... don't worry about a thing, your Majesty; we're on our way.
I think CCPs hardware guys are their most competent. TQs Hardware has hardly ever if ever been a problem. If they feel confident to pull it off in that timeframe, I would actually trust them.
Boot.ini wasn't something the TQ server guys screwed up.
nevar forget
Bookmarks