Closed
Bug 1563340
Opened 5 years ago
Closed 5 years ago
Setup tier3 bsdpy service on bsdpy virtual hosts
Categories
(Infrastructure & Operations :: RelOps: Posix OS, task)
Infrastructure & Operations
RelOps: Posix OS
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dividehex, Assigned: dividehex)
References
Details
Attachments
(1 file)
We will need to setup the bsdpy service on the tier3 releng networks/vlans in mdc1 and mdc2. Once the vhosts are setup they should be fairly easy to provision since the current established hosts are already managed in build-puppet.
|
Assignee | |
Comment 1•5 years ago
|
||
Assignee: nobody → jwatkins
|
|
Assignee | |
Comment 2•5 years ago
|
||
added puppet and repo cnames to point to relative puppet servers. This is needed for kickstart and puppet provisioning.
|
|
Assignee | |
Comment 3•5 years ago
|
||
All 4 bsdpy vhosts have been kickstarted into puppetagain
|
|
Assignee | |
Comment 4•5 years ago
|
||
Once the deploystudio hosts are up and configure, we can generate netboot sets from each datacenter then upload them to the bsdpy hosts respective to their location.
|
|
Assignee | |
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•