Difference between revisions of "Creating a Rack"
(Created page with "If you have a plethora of equipment lying around, you can make your own [Truxton Forensic Rack] solution. This article will discuss how to configure the rack as a Truxton solu...") |
|||
| Line 1: | Line 1: | ||
| − | If you have a plethora of equipment lying around, you can make your own [Truxton Forensic Rack] solution. | + | If you have a plethora of equipment lying around, you can make your own [[Truxton Forensic Rack]] solution. |
This article will discuss how to configure the rack as a Truxton solution. | This article will discuss how to configure the rack as a Truxton solution. | ||
| + | |||
| + | =Equipment= | ||
| + | The number and type of equipment that make up the rack is up to you. | ||
| + | All Truxton needs is Windows OS. | ||
| + | |||
| + | =Storage= | ||
| + | Truxton ETL servers require a single view of [[Depot|depot]] storage. | ||
| + | When an ETL process writes to a depot file, a process on a different machine must be able to read from it. | ||
| + | ETL's require fast IO. | ||
| + | For this reason we leave this to the operating system. | ||
| + | One possible solution is to use [https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/storage-spaces-direct-overview Windows Storage Spaces Direct.] | ||
| + | The remainder of this article will assume that all rack servers will have the mount point for the shares file system to be <code>C:\ClusterStorage</code>. | ||
| + | |||
| + | =Sample Rack= | ||
| + | Let's assume you have three servers lying around. | ||
| + | You might populate the rack thusly: | ||
| + | {| class="wikitable" | ||
| + | |- | ||
| + | | U18 | ||
| + | | [https://en.wikipedia.org/wiki/Network_switch Network Switch] | ||
| + | |- | ||
| + | | U17 | ||
| + | | [https://en.wikipedia.org/wiki/Rackmount_KVM KVM] | ||
| + | |- | ||
| + | | U13 | ||
| + | | Server 3 | ||
| + | |- | ||
| + | | U09 | ||
| + | | Server 2 | ||
| + | |- | ||
| + | | U05 | ||
| + | | Server 1 | ||
| + | |- | ||
| + | | U01 | ||
| + | | [https://en.wikipedia.org/wiki/Uninterruptible_power_supply UPS] | ||
| + | |} | ||
| + | |||
| + | =Responsibilities= | ||
| + | Decide which machines will have which responsibilities. | ||
| + | There are a handful of singleton pieces of Truxton: | ||
| + | # Database | ||
| + | # Message Bus | ||
| + | # Load Status Monitor | ||
Revision as of 15:06, 16 August 2021
If you have a plethora of equipment lying around, you can make your own Truxton Forensic Rack solution. This article will discuss how to configure the rack as a Truxton solution.
Equipment
The number and type of equipment that make up the rack is up to you. All Truxton needs is Windows OS.
Storage
Truxton ETL servers require a single view of depot storage.
When an ETL process writes to a depot file, a process on a different machine must be able to read from it.
ETL's require fast IO.
For this reason we leave this to the operating system.
One possible solution is to use Windows Storage Spaces Direct.
The remainder of this article will assume that all rack servers will have the mount point for the shares file system to be C:\ClusterStorage.
Sample Rack
Let's assume you have three servers lying around. You might populate the rack thusly:
| U18 | Network Switch |
| U17 | KVM |
| U13 | Server 3 |
| U09 | Server 2 |
| U05 | Server 1 |
| U01 | UPS |
Responsibilities
Decide which machines will have which responsibilities. There are a handful of singleton pieces of Truxton:
- Database
- Message Bus
- Load Status Monitor
