Closed Bug 1440873 Opened 4 years ago Closed 3 years ago

Setup sea-mini-osx64-5

Categories

(SeaMonkey :: Release Engineering, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ewong, Assigned: ewong)

Details

Attachments

(1 file)

With the completion of bug 1432706 and me having access to the new mini,
it's now time to set it up.

sea-master1 can ping sea-mini-osx64-5 and vice versa.

Now..

1) Add sea-mini-osx64-5's ip to the master's /etc/hosts and point it
   to sea-mini-osx64-5.community.scl3.mozilla.com.
   *note: probably easier to ask netops to add it to the dns setup,
          but since scl3 is going away, no point.
   -- > Done <--

2) add sea-master1.community.scl3.mozilla.com to the new mini's /etc/hosts
   [again, a temp thing until we get a dns thing going]

3) actually set up buildbot on the master. [this is going to be a toughie]
(In reply to Edmund Wong (:ewong) from comment #0)
> With the completion of bug 1432706 and me having access to the new mini,
> it's now time to set it up.
> 
> sea-master1 can ping sea-mini-osx64-5 and vice versa.
> 
> Now..
> 
> 1) Add sea-mini-osx64-5's ip to the master's /etc/hosts and point it
>    to sea-mini-osx64-5.community.scl3.mozilla.com.
>    *note: probably easier to ask netops to add it to the dns setup,
>           but since scl3 is going away, no point.
>    -- > Done <--
> 
> 2) add sea-master1.community.scl3.mozilla.com to the new mini's /etc/hosts
>    [again, a temp thing until we get a dns thing going]
> 
> 3) actually set up buildbot on the master. [this is going to be a toughie]

please disregard #3.  When I was writing that, I believe my mode of thought
was "setting up the new master" instead of "setting up the new mini".
note: this patch was manually applied to the master.
Attachment #8954257 - Flags: review?(frgrahl)
Attachment #8954257 - Flags: review?(frgrahl) → review+
sea-mini-osx64-5 is setup and hooked up to the new infra as
sea-mini-osx64-1.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.