Fixing install and OAuth

Some fixes for the setup script, and add the ability to use a service account when accessing the data from GCE.

BUG=skia:

Committed: https://skia.googlesource.com/buildbot/+/8233bb584ddeef982aa2ffa132c5573d558ab1b6

[benchen, 2014-06-16 20:07:36]

lgtm

[mtklein, 2014-06-16 20:25:11]

https://codereview.chromium.org/335183002/diff/60001/perf/server/data.go
File perf/server/data.go (right):

https://codereview.chromium.org/335183002/diff/60001/perf/server/data.go#newc...
perf/server/data.go:20: "code.google.com/p/goauth2/compute/serviceaccount"
Am I thinking using a service account is roughly like running things on borg as
a group rather than as a user?  If so, how do we tell it which service account
to use?

[jcgregorio, 2014-06-16 20:33:47]

https://codereview.chromium.org/335183002/diff/60001/perf/server/data.go
File perf/server/data.go (right):

https://codereview.chromium.org/335183002/diff/60001/perf/server/data.go#newc...
perf/server/data.go:20: "code.google.com/p/goauth2/compute/serviceaccount"
There's a service account associated with the cloud console project 

  https://console.developers.google.com/project/31977622648

As long as you create a VM instance with bigquery enabled then the service
account credentials will have access to bigquery. There is an account name
associated with that client you can lookup at the link above, but you don't need
to know that when using the service account, the metadata server keeps track of
that. Details here:

  https://developers.google.com/compute/docs/authentication


On 2014/06/16 20:25:11, mtklein wrote:
> Am I thinking using a service account is roughly like running things on borg
as
> a group rather than as a user?  If so, how do we tell it which service account
> to use?

[mtklein, 2014-06-16 20:39:29]

On 2014/06/16 20:33:47, jcgregorio wrote:
> https://codereview.chromium.org/335183002/diff/60001/perf/server/data.go
> File perf/server/data.go (right):
> 
>
https://codereview.chromium.org/335183002/diff/60001/perf/server/data.go#newc...
> perf/server/data.go:20: "code.google.com/p/goauth2/compute/serviceaccount"
> There's a service account associated with the cloud console project 
> 
>   https://console.developers.google.com/project/31977622648
> 
> As long as you create a VM instance with bigquery enabled then the service
> account credentials will have access to bigquery. There is an account name
> associated with that client you can lookup at the link above, but you don't
need
> to know that when using the service account, the metadata server keeps track
of
> that. Details here:
> 
>   https://developers.google.com/compute/docs/authentication
> 
> 
> On 2014/06/16 20:25:11, mtklein wrote:
> > Am I thinking using a service account is roughly like running things on borg
> as
> > a group rather than as a user?  If so, how do we tell it which service
account
> > to use?

Neat, LGTM.

[jcgregorio, 2014-06-16 20:41:53]

The CQ bit was checked by jcgregorio@google.com

[commit-bot: I haz the power, 2014-06-16 20:42:12]

CQ is trying da patch. Follow status at
 https://skia-tree-status.appspot.com/cq/jcgregorio@google.com/335183002/60001

[commit-bot: I haz the power, 2014-06-16 20:42:20]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-06-16 20:42:21]

Failed to apply patch for perf/server/setup/continue_install:
While running git apply --index -p1;
  error: patch failed: perf/server/setup/continue_install:17
  error: perf/server/setup/continue_install: patch does not apply

Patch:       perf/server/setup/continue_install
Index: perf/server/setup/continue_install
diff --git a/perf/server/setup/continue_install
b/perf/server/setup/continue_install
index
d46b2bbba015a9377de6b05482810faa24278636..42be09be8c882672174748416a2fa4954fc07a68
100644
--- a/perf/server/setup/continue_install
+++ b/perf/server/setup/continue_install
@@ -17,12 +17,18 @@ else
 fi
 
 
-if [-d buildbot]; then
+if [ -d buildbot ]; then
   (cd buildbot && git pull);
 else
   git clone https://skia.googlesource.com/buildbot
 fi
 
+if [ -d skia ]; then
+  (cd skia && git pull);
+else
+  git clone https://skia.googlesource.com/skia
+fi
+
 mkdir=$HOME/golib
 export GOROOT=$HOME/go
 export GOPATH=$HOME/golib
@@ -30,4 +36,4 @@ export PATH=$PATH:$GOROOT/bin
 
 cd ~/buildbot/perf/server
 go get -d
-go build perf.go
+go build -o perf

[jcgregorio, 2014-06-16 20:46:22]

On 2014/06/16 20:42:21, I haz the power (commit-bot) wrote:
> Failed to apply patch for perf/server/setup/continue_install:
> While running git apply --index -p1;
>   error: patch failed: perf/server/setup/continue_install:17
>   error: perf/server/setup/continue_install: patch does not apply
> 
> Patch:       perf/server/setup/continue_install
> Index: perf/server/setup/continue_install
> diff --git a/perf/server/setup/continue_install
> b/perf/server/setup/continue_install
> index
>
d46b2bbba015a9377de6b05482810faa24278636..42be09be8c882672174748416a2fa4954fc07a68
> 100644
> --- a/perf/server/setup/continue_install
> +++ b/perf/server/setup/continue_install
> @@ -17,12 +17,18 @@ else
>  fi
>  
>  
> -if [-d buildbot]; then
> +if [ -d buildbot ]; then
>    (cd buildbot && git pull);
>  else
>    git clone https://skia.googlesource.com/buildbot
>  fi
>  
> +if [ -d skia ]; then
> +  (cd skia && git pull);
> +else
> +  git clone https://skia.googlesource.com/skia
> +fi
> +
>  mkdir=$HOME/golib
>  export GOROOT=$HOME/go
>  export GOPATH=$HOME/golib
> @@ -30,4 +36,4 @@ export PATH=$PATH:$GOROOT/bin
>  
>  cd ~/buildbot/perf/server
>  go get -d
> -go build perf.go
> +go build -o perf

Rebased and trying again.

[jcgregorio, 2014-06-16 20:46:25]

The CQ bit was checked by jcgregorio@google.com

[commit-bot: I haz the power, 2014-06-16 20:47:12]

CQ is trying da patch. Follow status at
 https://skia-tree-status.appspot.com/cq/jcgregorio@google.com/335183002/80001

[commit-bot: I haz the power, 2014-06-16 20:47:22]

Change committed as 8233bb584ddeef982aa2ffa132c5573d558ab1b6