Difference between revisions of "Techinc Infra"
| (18 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
|picture=NETWORK-Physical-Servers.svg | |picture=NETWORK-Physical-Servers.svg | ||
|ProjectSkills=Networking, Security, Planning | |ProjectSkills=Networking, Security, Planning | ||
| − | |ProjectStatus= | + | |ProjectStatus=Dormant |
|ProjectNiche=Software | |ProjectNiche=Software | ||
|ProjectPurpose=Infrastructure | |ProjectPurpose=Infrastructure | ||
}} | }} | ||
| − | This Project is the birth of stable, fast, reliable infra withen techinc. | + | This Project is the birth of stable, fast, reliable infra withen techinc, this project will allow members to have VPSES, CTF Practice Servers, A cups printserver that worked when its needed,maybe the ti wiki oneday. |
| − | What has been done: | + | <b> What has been done: </b> |
Hypervisor RED is up and configured. <br> | Hypervisor RED is up and configured. <br> | ||
| Line 22: | Line 22: | ||
Monitoring VM <br> | Monitoring VM <br> | ||
| − | What needs to be done: <br> | + | <b> What needs to be done: </b> <br> |
LDAP Migration<br> | LDAP Migration<br> | ||
| Line 30: | Line 30: | ||
Backup and Recovery <br> | Backup and Recovery <br> | ||
Cluster Failover <br> | Cluster Failover <br> | ||
| + | Cable labling of the Currant TI Environment<br> | ||
| + | Checking if Documentation makes sense <br> | ||
| + | IRC Bot for the monitoring Server <br> | ||
| + | LTSP Server <br> | ||
| + | |||
| + | <b> The following diagram is a design of how the currant infra is </b> <br> | ||
| + | Bonding = LACP Trunk (Link Aggregation) for this document i will refer to this practice as LACP Trunk(s) or LACP Trunking <br> | ||
| + | Orange Circles = an indication that all the lines (interfaces) in the circle are apart of the same LACP Trunk <br> | ||
| + | White space with a Server icon in it = Means That all the items in that whitespace are physical connected/bound to that Physical Server. | ||
| + | |||
| + | [[file:NETWORK-Physical-Servers.svg|1000px]] | ||
| + | |||
| + | <b> Future Possible Concepts </b> | ||
| + | |||
| + | Concept A the Core, Access, Distribution with single link fault tolarance between switches on the Core and Distibution Level. | ||
| + | |||
| + | [[File:Network Concept A .svg|1000px]] | ||
Latest revision as of 02:06, 15 February 2017
| Projects | |
|---|---|
| |
| Participants | |
| Skills | Networking, Security, Planning |
| Status | Dormant |
| Niche | Software |
| Purpose | Infrastructure |
This Project is the birth of stable, fast, reliable infra withen techinc, this project will allow members to have VPSES, CTF Practice Servers, A cups printserver that worked when its needed,maybe the ti wiki oneday.
What has been done:
Hypervisor RED is up and configured.
Hypervisor BLUE is up and configured.
LACP between core switch and glassroom switch is up.
Fiber and Power has been pulled to glassroom.
Basic Documentation.
LACP Between hypervisors and the Glassroom Switch is up.
Remote Powerbars control
Powerbars are on two seperate groups in TI.
Shardik VM
Webserver VM
Monitoring VM
What needs to be done:
LDAP Migration
RADUIS Migration
Administration server - Documentation/Passwords
CUPS Print Server for the space Printers.
Backup and Recovery
Cluster Failover
Cable labling of the Currant TI Environment
Checking if Documentation makes sense
IRC Bot for the monitoring Server
LTSP Server
The following diagram is a design of how the currant infra is
Bonding = LACP Trunk (Link Aggregation) for this document i will refer to this practice as LACP Trunk(s) or LACP Trunking
Orange Circles = an indication that all the lines (interfaces) in the circle are apart of the same LACP Trunk
White space with a Server icon in it = Means That all the items in that whitespace are physical connected/bound to that Physical Server.
Future Possible Concepts
Concept A the Core, Access, Distribution with single link fault tolarance between switches on the Core and Distibution Level.
