Perf server initial documentation; mostly placeholder now.

Perf server initial documentation; mostly placeholder now.

BUG=skia:
TBR=rmistry

Committed: https://skia.googlesource.com/buildbot/+/df1a19beb97ed159eefe38d6c82ee5c141856781

[benchen, 2014-06-04 13:47:14]

This is just to get things started. Will edit along the way.

[rmistry, 2014-06-04 13:59:18]

https://codereview.chromium.org/316923002/diff/1/compute_engine_scripts/perfs...
File compute_engine_scripts/perfserver/vm_setup_server.sh (right):

https://codereview.chromium.org/316923002/diff/1/compute_engine_scripts/perfs...
compute_engine_scripts/perfserver/vm_setup_server.sh:5: # Copyright 2014 Google
Inc. All Rights Reserved.
Lets also create two more scripts in this directory called vm_create_server.sh
and vm_delete_server.sh.

https://codereview.chromium.org/316923002/diff/1/perf/server/README.md
File perf/server/README.md (right):

https://codereview.chromium.org/316923002/diff/1/perf/server/README.md#newcode8
perf/server/README.md:8: 
We can instead point from here to a README file in compute_engine_scripts that
will contain information on how to create, setup and delete this server
referring to the corresponding scripts.

https://codereview.chromium.org/316923002/diff/1/perf/server/README.md#newcode16
perf/server/README.md:16: --persistent_boot_disk

This command is going to be the one that will be in vm_create_server.sh but the
constants will be used from
https://skia.googlesource.com/buildbot/+/master/compute_engine_scripts/buildb...

https://codereview.chromium.org/316923002/diff/1/perf/server/README.md#newcode22
perf/server/README.md:22: gcutil --project=google.com:skia-buildbots ssh
--ssh_user=default skia-perf-b
We should try to avoid hardcoding these values because if we migrate due to a
PCR then this may become skia-perf-a.

[borenet, 2014-06-04 14:04:46]

https://codereview.chromium.org/316923002/diff/1/compute_engine_scripts/perfs...
File compute_engine_scripts/perfserver/vm_setup_server.sh (right):

https://codereview.chromium.org/316923002/diff/1/compute_engine_scripts/perfs...
compute_engine_scripts/perfserver/vm_setup_server.sh:5: # Copyright 2014 Google
Inc. All Rights Reserved.
Also, should probably use the same copyright header we use everywhere else:

# Copyright (c) 2014 The Chromium Authors. All rights reserved.
# Use of this source code is governed by a BSD-style license that can be
# found in the LICENSE file.

[benchen, 2014-06-04 15:23:31]

No I have a better idea on where to put what. PTAL, thanks!

https://codereview.chromium.org/316923002/diff/1/compute_engine_scripts/perfs...
File compute_engine_scripts/perfserver/vm_setup_server.sh (right):

https://codereview.chromium.org/316923002/diff/1/compute_engine_scripts/perfs...
compute_engine_scripts/perfserver/vm_setup_server.sh:5: # Copyright 2014 Google
Inc. All Rights Reserved.
On 2014/06/04 13:59:18, rmistry wrote:
> Lets also create two more scripts in this directory called vm_create_server.sh
> and vm_delete_server.sh.

Done.

https://codereview.chromium.org/316923002/diff/1/perf/server/README.md
File perf/server/README.md (right):

https://codereview.chromium.org/316923002/diff/1/perf/server/README.md#newcode8
perf/server/README.md:8: 
On 2014/06/04 13:59:18, rmistry wrote:
> We can instead point from here to a README file in compute_engine_scripts that
> will contain information on how to create, setup and delete this server
> referring to the corresponding scripts.

Done.

https://codereview.chromium.org/316923002/diff/1/perf/server/README.md#newcode16
perf/server/README.md:16: --persistent_boot_disk
Got it. Is it fine to share and put new constants under buildbots, or we should
have a new vm_config?
On 2014/06/04 13:59:18, rmistry wrote:
> 
> This command is going to be the one that will be in vm_create_server.sh but
the
> constants will be used from
>
https://skia.googlesource.com/buildbot/+/master/compute_engine_scripts/buildb...

https://codereview.chromium.org/316923002/diff/1/perf/server/README.md#newcode22
perf/server/README.md:22: gcutil --project=google.com:skia-buildbots ssh
--ssh_user=default skia-perf-b
I see, will figure out how it is done currently.
On 2014/06/04 13:59:18, rmistry wrote:
> We should try to avoid hardcoding these values because if we migrate due to a
> PCR then this may become skia-perf-a.

[benchen, 2014-06-04 15:24:05]

oops, I meant "NOW I have a better idea..."

[rmistry, 2014-06-04 15:26:45]

https://codereview.chromium.org/316923002/diff/1/perf/server/README.md
File perf/server/README.md (right):

https://codereview.chromium.org/316923002/diff/1/perf/server/README.md#newcode16
perf/server/README.md:16: --persistent_boot_disk
On 2014/06/04 15:23:32, benchen wrote:
> Got it. Is it fine to share and put new constants under buildbots, or we
should
> have a new vm_config?

Should be fine to share vm_config and put new constants there.

> On 2014/06/04 13:59:18, rmistry wrote:
> > 
> > This command is going to be the one that will be in vm_create_server.sh but
> the
> > constants will be used from
> >
>
https://skia.googlesource.com/buildbot/+/master/compute_engine_scripts/buildb...
>

[benchen, 2014-06-04 16:06:43]

Submitting the placeholders now.

[benchen, 2014-06-04 16:06:53]

The CQ bit was checked by bensong@google.com

[commit-bot: I haz the power, 2014-06-04 16:07:44]

CQ is trying da patch. Follow status at
 https://skia-tree-status.appspot.com/cq/bensong@google.com/316923002/40001

[commit-bot: I haz the power, 2014-06-04 16:07:57]

Change committed as df1a19beb97ed159eefe38d6c82ee5c141856781