in which IT makes my life living hell
So today, at long last, I succeeded in a task I set out to do on March 24th but which, due to the almost impenetrable SEP (Someone Else's Problem) fields surrounding IT at my company, took an egregiously long time for me to complete.
I'm so verklempt.
I cannot even tell you how many tcpdumps, traceroutes, tcptraceroutes, iptables and failed rsyncs I have conducted over the past 4.5 months and shoved in various stubbornly clueless IT Guys' faces saying HERE, SEE? YOUR SWITCH IS THE ISSUE. GO THOU AND FIXIT. Only to get one hop further down the line to another problem child.
Why networks so hard, IT? Remember: this is your job. This is the only thing they pay you to do!
But finally, yesterday, I succeeded in pushing our test repository to the DMZ (demilitarized zone) servers halfway between the dev network and production, which is where I get off the train: the production servers then pull from the DMZ in a kind of delicate, prissy white-gloved "secure" transfer and plop all the files onto a filesystem into which I have zero visibility.
Which meant, of course, when the developer I'm doing this for ran the first software update test yesterday and got a 404 error, I wasn't able to give him any directory listing or paths or anything to help debug the issue. Instead, I had to open yet ANOTHER ticket, this time with the folks in charge of the destination servers in production.
Fortunately, these guys work in the same office as me. They are brilliant and reasonable (and cute, although that might still by my ovaries talking) and very easy to deal with. And so we just sat on chat for two straight 4 hour sessions until we ironed it all out. In between learning he was a totally lapsed Mormon and really likes subreddit, we cleaned up the pull script and found a caching issue and restarted the white gloves.
And then I let the dev loose on the result, only to have him say: new error! bad path!
But he sent me a comprehensive error message, and I pointed to his path and said: you fail! You forgot to include the machine architecture! bwah!
And he fixed it, and it was Good. At 6:30 p.m. I reached the end of my 4.5 month journey and called my ticket verified, exactly 13 days before my deadline. Which, except for IT? Should only have taken me 3 days *total*.
Oh, IT. They're outsourced, of course.
[ X-posted to Dreamwidth with
comments | How to use OpenID ]
I'm so verklempt.
I cannot even tell you how many tcpdumps, traceroutes, tcptraceroutes, iptables and failed rsyncs I have conducted over the past 4.5 months and shoved in various stubbornly clueless IT Guys' faces saying HERE, SEE? YOUR SWITCH IS THE ISSUE. GO THOU AND FIXIT. Only to get one hop further down the line to another problem child.
Why networks so hard, IT? Remember: this is your job. This is the only thing they pay you to do!
But finally, yesterday, I succeeded in pushing our test repository to the DMZ (demilitarized zone) servers halfway between the dev network and production, which is where I get off the train: the production servers then pull from the DMZ in a kind of delicate, prissy white-gloved "secure" transfer and plop all the files onto a filesystem into which I have zero visibility.
Which meant, of course, when the developer I'm doing this for ran the first software update test yesterday and got a 404 error, I wasn't able to give him any directory listing or paths or anything to help debug the issue. Instead, I had to open yet ANOTHER ticket, this time with the folks in charge of the destination servers in production.
Fortunately, these guys work in the same office as me. They are brilliant and reasonable (and cute, although that might still by my ovaries talking) and very easy to deal with. And so we just sat on chat for two straight 4 hour sessions until we ironed it all out. In between learning he was a totally lapsed Mormon and really likes subreddit, we cleaned up the pull script and found a caching issue and restarted the white gloves.
And then I let the dev loose on the result, only to have him say: new error! bad path!
But he sent me a comprehensive error message, and I pointed to his path and said: you fail! You forgot to include the machine architecture! bwah!
And he fixed it, and it was Good. At 6:30 p.m. I reached the end of my 4.5 month journey and called my ticket verified, exactly 13 days before my deadline. Which, except for IT? Should only have taken me 3 days *total*.
Oh, IT. They're outsourced, of course.
[ X-posted to Dreamwidth with
comments | How to use OpenID ]