Set up the nginx servers for handling *.skia.org traffic.

Set up the nginx servers for handling *.skia.org traffic.

Note that for now we use *.skiadev.org, which is just a placeholder until we get *.skia.org DNS entries straightened out.

Note that this doesn't have SSL certs which will also have to wait until after the *.skia.org DNS change is done.

stepahan - for the nginx config.
rmistry  - for the rest of the files.

You can see this live at skiadev.org and perf.skiadev.org.

See also the READM.md file for the design of the traffic
handling.

BUG=skia:

Committed: https://skia.googlesource.com/buildbot/+/783a3c45917b4c9b9823e4cb91987d7c5d623f8e

[jcgregorio, 2015-01-05 15:50:25]

jcgregorio@google.com changed reviewers:
+ rmistry@google.com, stephana@google.com

[stephana, 2015-01-05 16:09:29]

On 2015/01/05 16:02:44, jcgregorio wrote:

lgtm

[rmistry, 2015-01-05 19:25:34]

LGTM

https://codereview.chromium.org/819473004/diff/40001/compute_engine_scripts/s...
File compute_engine_scripts/skfe/vm_create_instance.sh (right):

https://codereview.chromium.org/819473004/diff/40001/compute_engine_scripts/s...
compute_engine_scripts/skfe/vm_create_instance.sh:19: --machine-type
n1-standard-4 \
Store machine type in vm_config.sh to be consistent with other
compute_engine_scripts.

[jcgregorio, 2015-01-05 20:13:18]

https://codereview.chromium.org/819473004/diff/40001/compute_engine_scripts/s...
File compute_engine_scripts/skfe/vm_create_instance.sh (right):

https://codereview.chromium.org/819473004/diff/40001/compute_engine_scripts/s...
compute_engine_scripts/skfe/vm_create_instance.sh:19: --machine-type
n1-standard-4 \
On 2015/01/05 19:25:34, rmistry wrote:
> Store machine type in vm_config.sh to be consistent with other
> compute_engine_scripts.

Done.

[jcgregorio, 2015-01-05 20:13:22]

The CQ bit was checked by jcgregorio@google.com

[commit-bot: I haz the power, 2015-01-05 20:13:42]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/819473004/60001

[commit-bot: I haz the power, 2015-01-05 20:13:50]

Committed patchset #4 (id:60001) as
https://skia.googlesource.com/buildbot/+/783a3c45917b4c9b9823e4cb91987d7c5d62...

[tfarina, 2015-01-10 18:28:52]

https://codereview.chromium.org/819473004/diff/60001/skfe/sys/skia_org
File skfe/sys/skia_org (right):

https://codereview.chromium.org/819473004/diff/60001/skfe/sys/skia_org#newcode3
skfe/sys/skia_org:3: server_name skiadev.org www.skiadev.org;
do we need access_log and error_log?

https://codereview.chromium.org/819473004/diff/60001/skfe/sys/skia_org#newcode4
skfe/sys/skia_org:4: 
where is the ssl protection configuration? I know port 80 is for http. I'm just
curious to know where the 443 is handled now.

[jcgregorio, 2015-01-12 12:25:03]

https://codereview.chromium.org/819473004/diff/60001/skfe/sys/skia_org
File skfe/sys/skia_org (right):

https://codereview.chromium.org/819473004/diff/60001/skfe/sys/skia_org#newcode3
skfe/sys/skia_org:3: server_name skiadev.org www.skiadev.org;
On 2015/01/10 18:28:52, tfarina wrote:
> do we need access_log and error_log?

The default behavior is fine.

https://codereview.chromium.org/819473004/diff/60001/skfe/sys/skia_org#newcode4
skfe/sys/skia_org:4: 
On 2015/01/10 18:28:52, tfarina wrote:
> where is the ssl protection configuration? I know port 80 is for http. I'm
just
> curious to know where the 443 is handled now.

SSL config will be done later once these servers start handling skia.org
traffic.