<commit_before>Cloudera Director on Google Cloud Platform
==========================================

1. First, create a Google Compute Engine VM instance and install Cloudera
   Director in a single step:

  ```bash
  gcloud compute instances create {{VM}} \
      --project {{PROJECT}} \
      --zone {{ZONE}} \
      --machine-type n1-standard-1 \
      --image centos-6 \
      --metadata-from-file startup-script=director.sh
  ```

  where:

  * `{{VM}}` is the name of the VM instance to create, e.g., `cloudera-director`
  * `{{PROJECT}}` is your
    [project id](https://cloud.google.com/storage/docs/projects?hl=en#projectid),
    e.g., `curious-lemming-42`
  * `{{ZONE}}` is a Google Compute Engine zone, e.g., `us-central1-f`
  * the [`director.sh`](director.sh) script is located in this directory

  You can monitor the console of your VM to see when the Cloudera Director is
  ready to accept requests either via the [Developers
  Console](https://cloud.google.com/console) at the following URL:

  ```
  https://console.developers.google.com/project/{{PROJECT}}/compute/instancesDetail/zones/{{ZONE}}/instances/{{VM}}/console#end
  ```

  or via the command-line:

  ```bash
  gcloud compute instances get-serial-port-output {{VM}} \
      --project {{PROJECT}} \
      --zone {{ZONE}}
  ```

2. Once you see the following line in the serial output:

   ```
   Cloudera Director is now ready.
   ```

   you can create a [SOCKS proxy](https://github.com/mbrukman/cloud-launcher/blob/master/howto/secure-connection.md#socks-proxy-over-ssh)
   to establish a secure connection to Cloudera Director on Google Compute
   Engine.

   Then, follow the directions in that howto to configure your web browser to
   use that secure connection to access Cloudera Director and other software
   that will be deployed alongside, such as Cloudera Manager and the Hadoop
   stack.
<commit_msg>Add `compute-rw` scope to enable creating VMs.<commit_after>Cloudera Director on Google Cloud Platform
==========================================

1. First, create a Google Compute Engine VM instance and install Cloudera
   Director in a single step:

  ```bash
  gcloud compute instances create {{VM}} \
      --project {{PROJECT}} \
      --zone {{ZONE}} \
      --machine-type n1-standard-1 \
      --scopes compute-rw \
      --image centos-6 \
      --metadata-from-file startup-script=director.sh
  ```

  where:

  * `{{VM}}` is the name of the VM instance to create, e.g., `cloudera-director`
  * `{{PROJECT}}` is your
    [project id](https://cloud.google.com/storage/docs/projects?hl=en#projectid),
    e.g., `curious-lemming-42`
  * `{{ZONE}}` is a Google Compute Engine zone, e.g., `us-central1-f`
  * the [`director.sh`](director.sh) script is located in this directory

  You can monitor the console of your VM to see when the Cloudera Director is
  ready to accept requests either via the [Developers
  Console](https://cloud.google.com/console) at the following URL:

  ```
  https://console.developers.google.com/project/{{PROJECT}}/compute/instancesDetail/zones/{{ZONE}}/instances/{{VM}}/console#end
  ```

  or via the command-line:

  ```bash
  gcloud compute instances get-serial-port-output {{VM}} \
      --project {{PROJECT}} \
      --zone {{ZONE}}
  ```

2. Once you see the following line in the serial output:

   ```
   Cloudera Director is now ready.
   ```

   you can create a [SOCKS proxy](https://github.com/mbrukman/cloud-launcher/blob/master/howto/secure-connection.md#socks-proxy-over-ssh)
   to establish a secure connection to Cloudera Director on Google Compute
   Engine.

   Then, follow the directions in that howto to configure your web browser to
   use that secure connection to access Cloudera Director and other software
   that will be deployed alongside, such as Cloudera Manager and the Hadoop
   stack.

{'fraction_non_alphanumeric': 0.14081579631073005, 'fraction_numerical': 0.004156923876331515, 'mean_word_length': 3.3552036199095023, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1358359', 'n_tokens_mistral': 1207, 'n_tokens_neox': 1144, 'n_words': 388}