Closed Bug 837967 Opened 13 years ago Closed 13 years ago

Kickstart reporting replica

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mpressman, Assigned: rbryce)

References

Details

Can we get the new socorro reporting blade server and storage blade kickstarted. https://inventory.mozilla.org/en-US/systems/racks/?location=12&status=&rack=280&allocation= Asset #'s: 15536 15535
Assignee: server-ops → rbryce
hostname: tp-socoro01-reporting01.phx1.mozilla.com vlan: 70 Server is Kickstarted, and puppetized. I formatted the storage blade in raid 5 with 3.0 Tb of storage. I just need to know if that is the correct raid config. As well as, where to mount the Storage Blade. /data??
Can we use the new DNS labeling? tp-socorro01 is the old one which we moved away from. socorro-reporting1.db.phx1.mozilla.com for example.
(In reply to Dumitru Gherman [:dumitru] from comment #2) > Can we use the new DNS labeling? tp-socorro01 is the old one which we moved > away from. > socorro-reporting1.db.phx1.mozilla.com for example. dumitru: thanks for pointing that out. Fixed! tp-socoro01-reporting01.phx1.mozilla.com -> socorro-reporting1.db.phx1.mozilla.com
(In reply to Rick Bryce [:rbryce] from comment #1) > hostname: tp-socoro01-reporting01.phx1.mozilla.com > vlan: 70 > > Server is Kickstarted, and puppetized. I formatted the storage blade in > raid 5 with 3.0 Tb of storage. I just need to know if that is the correct > raid config. As well as, where to mount the Storage Blade. /data?? Thanks! We prefer /pgdata for the volume name. What is the disk configuration on that system?
Filesystem Size Used Avail Use% Mounted on /dev/sda3 273G 1.5G 257G 1% / tmpfs 7.8G 0 7.8G 0% /dev/shm /dev/sda1 985M 65M 871M 7% /boot /dev/sdb1 2.8T 33M 2.8T 1% /pgdata
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Changed /pgdata raid array to RAID 5 w/ drive 12 as the HotSpare
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.