public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers3@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: fstests@vger.kernel.org, Eric Biggers <ebiggers@google.com>
Subject: [PATCH] test-appliance: remove gce-run
Date: Mon, 17 Apr 2017 12:59:11 -0700	[thread overview]
Message-ID: <20170417195911.75159-1-ebiggers3@gmail.com> (raw)

From: Eric Biggers <ebiggers@google.com>

The 'gce-run' command is obsolete now that we have 'gce-xfstests shell'.
It also didn't respect the settings in ~/.config/gce-xfstests.

Signed-off-by: Eric Biggers <ebiggers@google.com>
---
 kvm-xfstests/test-appliance/gce-run | 26 --------------------------
 1 file changed, 26 deletions(-)
 delete mode 100755 kvm-xfstests/test-appliance/gce-run

diff --git a/kvm-xfstests/test-appliance/gce-run b/kvm-xfstests/test-appliance/gce-run
deleted file mode 100755
index d8c895d..0000000
--- a/kvm-xfstests/test-appliance/gce-run
+++ /dev/null
@@ -1,26 +0,0 @@
-#!/bin/bash
-
-if test -r config.custom ; then
-   . $(pwd)/config.custom
-fi
-
-if test -z "$GCE_PROJECT" -o -z "$GCE_ZONE"
-then
-	echo "You must configure GCE_PROJECT and GCE_ZONE in"
-	echo "the config.custom file"
-	exit 1
-fi
-
-GS_RW=https://www.googleapis.com/auth/devstorage.read_write
-GS_RO=https://www.googleapis.com/auth/devstorage.read_only
-LOG_WR=https://www.googleapis.com/auth/logging.write
-COMPUTE_RW=https://www.googleapis.com/auth/compute
-
-SCOPES="$GS_RW,$COMPUTE_RW,$LOG_WR"
-
-gcloud compute --project "$GCE_PROJECT" \
-       instances create "xfstests" --zone "$GCE_ZONE" \
-       --machine-type "n1-highcpu-4" --network "default" \
-       --maintenance-policy "MIGRATE" \
-       --scopes "$SCOPES" \
-       --image "xfstests"
-- 
2.12.2.762.g0e3151a226-goog


             reply	other threads:[~2017-04-17 19:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 19:59 Eric Biggers [this message]
2017-04-21  5:51 ` [PATCH] test-appliance: remove gce-run Theodore Ts'o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170417195911.75159-1-ebiggers3@gmail.com \
    --to=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=fstests@vger.kernel.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox