9Am - 4pm All day working session on ESX remediation.� yay.� lunch provided.� Slick and Skipper were there.�
I had a 'flexible workplace' meeting today but I bailed on it because I had to do this ESX thing.� It was a whole lot more important.� I did send a late decline message answering the question they asked.�
PFF:
Email from Matt T. asking about the Tomcat to Was Migration for Prod.� Someone says that our environment doens't recover well after "change controls".� Needs to know why.
This is the first I've heard of that.� Nobody has ever told me that we have any issues after change controls.� What change controls?� What kinds of problems are we seeing?� What do you mean Tomcat doesn't recover well after a change control?� WTF?
I shot an email back stating as such.�
Saw Matt in the hallway of P2 near war room and explained the situation with his email.� It's all over the place that we're having issues after CC, but nobody tells ME about it?� I need to know what the issues are.� He says after recent change control windows something has happened that caused the PFF apps to behave funny.� Tomcat specifically.� I said that other changes can't really affect their env. because they're isolated.� Other than their systems authenticate against the prod portal LDAP servers.� He will get back to me.
ESX Meeting:
All the players were there.��� Slick, Skipper, Hooper,� Margie, Cartman, Grandpa Simpson, Thug, and of course yours truly.
We spend the morning arguing over items above our process.� Discussing what items we have to provide to the architects so they can provide it to the Salty Dogs who run the joint.
We get almost nothing done other than to auger in the point that management makes bad decisions based on information they get from the architects that is apparently not based on any sort of reality because they never ask the engineers who can never build a proper environment because expectations are unrealistic.
ok.� I get it.� Let's fucking move on already.
Noonish, break for lunch.� We actually carpooled everybody together and drove over to Pita Jungle to share lunch.� That was kooky stuff.� I never met people who hadn't eaten baba ganouj before and were visibly shaken by the sight of it.�
Misc:
Next up was Mr. T copying me on a thread from Matt on estimates for time in executing the cutover from Tomcat to WAS.� (Because Ash won't support Tomcat even though he knew for 5 months that it was coming and could have prepared.)
I estimated 8 hours for my time.� Becky estimated 40 for hers.� All I really have to do is unmount the volume I have currently attached to /opt and remount it over to /apps.� Make the changes in fstab and give it a reboot.� I might drop in some patches too while I'm at it.� That should allow me enough room for Becky to add WAS to the systems and grow them a bit.�
Howard copied me on an email that went to Grandpa Simpson and Cartman.� tkt454879� Needs ports open between monitoring systems & all WAS/Portal boxes.� Needs by Jun 12.� Nothing for me here folks, I don't fuck with firewalls.
Mr. T told everybody to get signed up for Sametime because I'm W@H till October and IM rules.
After Lunch, ESX Meeting:
I decided enough was enough and I got up and took control of the board and meeting.� I started a flow chart and walked us through my idea of a typical build cycle.� Our current system is nothing like this, but this is what I want to see.
Project initiate feeds to architecture, architecture needs to consult with various heads of State.� Those are such countries as SAN, Systems, Security, Network, Applications, Backups, Facilities, Deveopment, and the like.� They are nations unto themselves.
The architecture guys (I think of them as gnomes) collect the info we provide and then take it back for review.� That allows them to get more accurate estimates of time, cost, development, etc.
The Salty Dogs who run the Ship can then make a better decision about which direction they want to sail us in.� (And I have to say, the guys who run this ship are some pretty alright fellows.)
Now at that point, you get a Go/No-Go decision.� The heads of State are clued in about a new project in the spec cycle, and can gauge growth capacity vs expectations, and get a good idea of what sort of budgeting they need to consider.
Each head of State needs to know their process and have it documented.� That's what we need to do.� Everybody document what they need and where their calculations are and what the dependencies are and get back together next week, Friday the mother-farkin-13th to discuss.
We get unanimous approval of my process and concepts, agree on the meeting time I propose and we're done for the day.� Meeting adjourned.
MTG : Portal LDAP slowness troubleshooting Friday 6/6 2-3pm
Sent email to Oliver about swapping out my laptop from an x60 to a t60 so I can get a second monitor with a decent resolution.�
4:13pm Slick sent visio & meeting minutes from the meeting
Drive home.
Add comment
