Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Training 2022 Linux team/
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Training session Tetra team on CDIL understanding. Dated 05 Nov 2022 - Tetra Support Staff - Biswajit Banerjee== {{#ev:youtube|rcygPCtb9f4|640}} '''Video summary:''' [MIXED/PARTIAL TRANSCRIPT QUALITY - patchy throughout with long silent gaps] "Training session Tetra team on CDIL understanding" -- an architecture discovery/handoff session for client CDIL, similar in format to the ISGEC session on this same page. The presenter explains that unlike other clients, CDIL's environment wasn't handed over with documentation -- the team had to independently discover what existed (mail, "Diamond" application, backup setup) rather than being briefed on it, describing this as a first-time situation requiring active reverse-engineering of the architecture rather than a walkthrough of known documentation. Covers a Chandigarh/Shimla dual-location setup (two servers with fixed IPs that can't be changed, one acting as a base/primary server), TetraControl as the monitoring/chat platform used to track this and other environments, and an application running on Tomcat as its backend (traffic hits an Nginx/proxy layer in front, which forwards to Tomcat, rather than users hitting the app server directly). Also touches on a disk-space risk -- a log or data directory at risk of filling up, where clearing it would resolve the space issue but at the cost of taking the affected service down, so it's treated as a last-resort fix rather than routine maintenance. Given how patchy the transcript is throughout, this summary reflects only the clearly identifiable topics, not a complete architecture walkthrough.
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)