Add client.webrtc.perf master

Add client.webrtc.perf master

The builders currently added are just samples. They'll be replaced
with actual ones when we've figured out which machines shall be used.

BUG=616531
Committed: https://chromium.googlesource.com/chromium/tools/build/+/c7b17496fe54413e9ba25899bfe94b66cede30a4

[kjellander_chromium, 2016-06-01 18:05:05]

Patchset #1 (id:1) has been deleted

[kjellander_chromium, 2016-06-01 18:10:55]

Patchset #1 (id:20001) has been deleted

[kjellander_chromium, 2016-06-01 18:11:40]

kjellander@chromium.org changed reviewers:
+ stip@chromium.org

[kjellander_chromium, 2016-06-01 18:11:40]

https://codereview.chromium.org/2022343003/diff/40001/masters/master.client.w...
File masters/master.client.webrtc.perf/master_site_config.py (right):

https://codereview.chromium.org/2022343003/diff/40001/masters/master.client.w...
masters/master.client.webrtc.perf/master_site_config.py:11: master_port = 20301
These ports were generated with
$ scripts/tools/mastermap.py --find WebRTCPerf

[ghost stip (do not use), 2016-06-01 18:43:49]

generally lg, but you should really look into builders.pyl:
https://chromium.googlesource.com/infra/infra/+/master/doc/users/services/bui...

https://chromiumcodereview.appspot.com/2022343003/diff/40001/masters/master.c...
File masters/master.client.webrtc.perf/master.cfg (right):

https://chromiumcodereview.appspot.com/2022343003/diff/40001/masters/master.c...
masters/master.client.webrtc.perf/master.cfg:29: c['schedulers'].extend([
you should look into using builders.pyl. it combines the builder/scheduler
configs and slaves.cfg; it's a much nicer interface

https://chromiumcodereview.appspot.com/2022343003/diff/40001/masters/master.c...
File masters/master.client.webrtc.perf/master_site_config.py (right):

https://chromiumcodereview.appspot.com/2022343003/diff/40001/masters/master.c...
masters/master.client.webrtc.perf/master_site_config.py:11: master_port = 20301
On 2016/06/01 18:11:40, kjellander_chromium wrote:
> These ports were generated with
> $ scripts/tools/mastermap.py --find WebRTCPerf

I think friedman@ has to screen the ports now? Things have changed so I'm not
100% sure anymore

[ghost stip (do not use), 2016-06-01 18:43:58]

Description was changed from

==========
Add client.webrtc.perf master

The builders currently added are just samples. They'll be replaced
with actual ones when we've figured out which machines shall be used.

BUG=616531
==========

to

==========
Add client.webrtc.perf master

The builders currently added are just samples. They'll be replaced
with actual ones when we've figured out which machines shall be used.

BUG=616531
==========

[ghost stip (do not use), 2016-06-01 18:43:58]

stip@chromium.org changed reviewers:
+ friedman@chromium.org

[ghost stip (do not use), 2016-06-01 18:44:09]

+ friedman@ in case he needs to screen the ports

[friedman, 2016-06-01 18:46:57]

lgtm

https://chromiumcodereview.appspot.com/2022343003/diff/40001/masters/master.c...
File masters/master.client.webrtc.perf/master_site_config.py (right):

https://chromiumcodereview.appspot.com/2022343003/diff/40001/masters/master.c...
masters/master.client.webrtc.perf/master_site_config.py:11: master_port = 20301
On 2016/06/01 18:43:49, stip wrote:
> On 2016/06/01 18:11:40, kjellander_chromium wrote:
> > These ports were generated with
> > $ scripts/tools/mastermap.py --find WebRTCPerf
> 
> I think friedman@ has to screen the ports now? Things have changed so I'm not
> 100% sure anymore

1-10 used to be reserved but no one had a valid reason why.  If this isn't
overlapping then it's fine to me.

[friedman, 2016-06-01 18:47:10]

On 2016/06/01 18:46:57, friedman wrote:
> lgtm
> 
>
https://chromiumcodereview.appspot.com/2022343003/diff/40001/masters/master.c...
> File masters/master.client.webrtc.perf/master_site_config.py (right):
> 
>
https://chromiumcodereview.appspot.com/2022343003/diff/40001/masters/master.c...
> masters/master.client.webrtc.perf/master_site_config.py:11: master_port =
20301
> On 2016/06/01 18:43:49, stip wrote:
> > On 2016/06/01 18:11:40, kjellander_chromium wrote:
> > > These ports were generated with
> > > $ scripts/tools/mastermap.py --find WebRTCPerf
> > 
> > I think friedman@ has to screen the ports now? Things have changed so I'm
not
> > 100% sure anymore
> 
> 1-10 used to be reserved but no one had a valid reason why.  If this isn't
> overlapping then it's fine to me.

Sorry... lgtm on the port numbers only.

[kjellander_chromium, 2016-06-01 18:50:01]

On 2016/06/01 18:43:49, stip wrote:
> generally lg, but you should really look into builders.pyl:
>
https://chromium.googlesource.com/infra/infra/+/master/doc/users/services/bui...

I'll be happy to, but then I should do it for all our masters. 
Would it be OK to add this for now so I can file tickets for the
database/netscaler setup etc.

>
https://chromiumcodereview.appspot.com/2022343003/diff/40001/masters/master.c...
> File masters/master.client.webrtc.perf/master.cfg (right):
> 
>
https://chromiumcodereview.appspot.com/2022343003/diff/40001/masters/master.c...
> masters/master.client.webrtc.perf/master.cfg:29: c['schedulers'].extend([
> you should look into using builders.pyl. it combines the builder/scheduler
> configs and slaves.cfg; it's a much nicer interface
> 
>
https://chromiumcodereview.appspot.com/2022343003/diff/40001/masters/master.c...
> File masters/master.client.webrtc.perf/master_site_config.py (right):
> 
>
https://chromiumcodereview.appspot.com/2022343003/diff/40001/masters/master.c...
> masters/master.client.webrtc.perf/master_site_config.py:11: master_port =
20301
> On 2016/06/01 18:11:40, kjellander_chromium wrote:
> > These ports were generated with
> > $ scripts/tools/mastermap.py --find WebRTCPerf
> 
> I think friedman@ has to screen the ports now? Things have changed so I'm not
> 100% sure anymore

[ghost stip (do not use), 2016-06-01 23:28:57]

lgtm :)

[kjellander_chromium, 2016-06-02 07:07:37]

The CQ bit was checked by kjellander@chromium.org

[commit-bot: I haz the power, 2016-06-02 07:07:47]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2022343003/40001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/2022343003/40001

[commit-bot: I haz the power, 2016-06-02 07:12:04]

Description was changed from

==========
Add client.webrtc.perf master

The builders currently added are just samples. They'll be replaced
with actual ones when we've figured out which machines shall be used.

BUG=616531
==========

to

==========
Add client.webrtc.perf master

The builders currently added are just samples. They'll be replaced
with actual ones when we've figured out which machines shall be used.

BUG=616531

Committed:
https://chromium.googlesource.com/chromium/tools/build/+/c7b17496fe54413e9ba2...
==========

[commit-bot: I haz the power, 2016-06-02 07:12:06]

Committed patchset #1 (id:40001) as
https://chromium.googlesource.com/chromium/tools/build/+/c7b17496fe54413e9ba2...