1433427145-Setting Up A Virtual Cluster - ADM 201
1433427145-Setting Up A Virtual Cluster - ADM 201
1433427145-Setting Up A Virtual Cluster - ADM 201
May 2015
Contents
Setting Up a Virtual Cluster on GCP (Google Cloud Platform)
10
12
14
14
15
May 2015
3. Complete
the
Google
Cloud
Platform
Starter
Credit
form,
populating
all
required
fields.
You
must
enter
a
valid
email
address
to
which
you
have
ready
access,
as
you
will
be
sent
a
redemption
code.
When
the
fields
are
complete,
enter
the
CAPTCHA
phrase
and
click
Submit.
4. Check
your
email
account
for
an
email
from
[email protected],
and
click
on
the
Redeem
now
button
in
the
email.
5. Read
and
agree
to
the
terms
of
service.
May 2015
6. Click
the
create
a
billing
account
link,
which
will
open
a
new
browser
tab
(keep
the
Redeem
promotion
code
tab
open
while
you
set
up
the
billing
account).
NOTE:
You
will
need
to
provide
a
credit
card
as
part
of
the
billing
account,
however,
you
will
not
be
billed.
When
your
$500
credit
is
depleted,
your
instances
will
be
paused
and
youll
have
the
option
to
upgrade
to
a
paid
account.
7. Provide
the
required
information,
then
click
Accept
and
start
free
trial
at
the
bottom
of
the
page.
This
will
automatically
create
a
project
called
My
First
Project.
Wait
until
the
page
refreshes
and
you
see
the
Project
Dashboard.
8. Go
back
to
the
Redeem
Promotion
Code
brower
tab
and
click
Continue.
The
Promotion
Code
field
should
populate
automatically
with
the
code
that
was
sent
to
your
email
address.
Click
Continue,
then
Redeem,
and
then
Done.
This
will
bring
you
back
to
the
Google
Developers
Console,
in
the
billing
view.
You
can
view
account
billing
any
time
by
clicking
the
gear
icon
in
the
upper
right
and
selecting
Billing
accounts.
NOTE:
It
can
take
up
to
48
hours
for
the
credit
to
appear
on
your
account,
though
it
is
generally
much
faster.
2. Click
on
the
pen
to
the
right
of
the
My
First
Project
line.
Change
the
name
to
mapr-training,
and
click
Rename.
3. Click
the
project
name
to
open
the
project
dashboard.
In
the
left-side
pane,
click
APIs
&
auth
and
then
APIs.
This
will
take
you
to
a
list
of
APIs
that
can
be
enabled.
4. In
the
Google
Cloud
APIs
section,
click
Compute
Engine
API,
then
Enable
API.
Wait
while
the
Google
Compute
Engine
is
enabled.
5. In
the
left-side
pane,
click
Overview
and
wait
for
the
screen
to
refresh.
Look
for
the
Project
ID
at
the
top
of
the
main
pane
(for
example,
Project
ID:
peak-orbit-96011).
Remember
the
Project
ID,
as
you
will
need
it
at
a
later
step.
May 2015
2. Follow
the
instructions
for
Installation
on
Windows
using
Cygwin.
3. Leave
the
default
settings
for
the
Cygwin
installer
(install
from
internet,
root
directory,
install
for
all
users,
local
package
directory,
direct
connection),
and
pick
a
mirror
site.
This
will
launch
a
window
that
allows
you
to
select
Cygwin
packages.
NOTE:
For
these
instructions
to
work
properly,
you
must
install
the
optional
packages
listed
in
the
next
step.
May 2015
4. For
the
following
packages,
toggle
the
installation
setting
from
skip
to
the
version
number
(for
example,
2.1.4-1):
o
5. Proceed
with
the
installation
and
let
it
run
until
it
finishes.
This
may
take
some
time.
6. Launch
Cygwin
from
Start
>
All
Programs
>
Cygwin
>
Cygwin
Terminal.
7. At
the
Cygwin
command
prompt
enter:
curl
https://sdk.cloud.google.com
|
bash
This
downloads
the
Google
Cloud
SDK
and
will
install
it
on
your
system.
8. After
the
installation
completes,
restart
the
Cygwin
terminal
by
typing
exit
at
the
prompt
and
re-launching
Cygwin. Enter
the
following
command
at
the
terminal
prompt
to
authenticate:
gcloud
auth
login
--no-launch-browser
The
command
will
generate
a
link,
and
then
wait
for
you
to
enter
a
verification
code.
Follow
these
steps
to
authenticate:
a. Copy
the
link
that
is
generated
by
the
command.
b. Open
a
new
web
browser
window
and
paste
the
link
into
the
address
bar.
Grant
the
requested
permissions.
The
page
that
displays
will
show
your
verification
code.
c. Copy
the
code
and
paste
this
back
into
the
Cygwin
terminal
at
the
Enter
verification
code:
prompt.
If
the
terminal
prompts
with
a
request
to
create
a
subdirectory
called
gce
under
the
home
directory,
authorize
the
request.
May 2015
2. At
the
terminal
prompt
change
to
the
gce
directory,
which
contains
the
MapR
scripts:
$
cd
gce
4. At
the
terminal
prompt,
enter
this
command
to
make
mapr-training
the
active
project:
$
gcloud
config
set
project
mapr-training
5. If
you
have
any
anti-virus
or
firewall
software
running,
disable
that
now.
6. At
the
terminal
prompt,
enter
the
command
below
to
launch
a
standard
MapR
cluster
that
can
be
used
for
training.
Note
the
following:
The
<Project
ID>
argument
is
the
Project
ID
of
your
Google
Cloud
project
(for
example,
peak-orbit-96011).
You
can
obtain
the
Project
ID
from
the
Overview
section
of
the
Google
Developers
Console.
For <cluster name>, you can specify any name that you want.
The
command
may
generate
some
warnings
of
the
format
WARNING:
Lists
should
be
separated
by
commas.
If
these
warnings
appear,
they
can
be
ignored.
3. From
the
left-side
menu
select
Compute
>
Compute
Engine
>
VM
Instances.
On
the
screen
that
appears,
you
will
see
a
status
view
showing
the
nodes
that
you
just
set
up.
To
the
far
right,
there
will
be
a
button
labeled
SSH.
To
launch
a
new
terminal
window
that
will
perform
passwordless
SSH
login
and
authentication
into
the
MapR
cluster,
simply
click
on
the
appropriate
SSH
button.
May 2015
May 2015
3. Enter
your
email
address,
select
the
I
am
a
new
user
radio
button,
and
click
Sign
in
using
our
secure
server.
4. Fill
out
the
Login
Credentials
web
form,
and
then
click
Continue.
5. Fill
out
the
Contact
Information
web
form
and
click
Create
Account
and
Continue.
6. Fill
out
the
Payment
Information
web
form
and
click
Continue.
7. Fill
out
the
Identity
Verification
web
form
and
click
Call
Me
Now.
Once
you
reply
to
the
phone
call
using
your
4-digit
code
from
this
web
form,
click
Continue
to
select
your
Support
Plan.
8. Fill
out
the
Support
Plan
web
form
(note
you
will
not
need
support
services
from
Amazon
in
order
to
run
the
labs
in
this
class).
Then
click
Continue.
Your
AWS
account
is
now
provisioned
and
you
can
begin
setting
up
the
virtual
machines
for
your
course.
May 2015
10. In
the
Virtual
Private
Cloud
section
of
your
navigation
pane,
click
Route
Tables.
11. Click
Create
Route
table
and
fill
out
the
web
form
as
follows:
a. Name
tag:
mapr-odt-routes
b. VPC:
mapr-odt-vpc
Then
click
Yes,
Create.
12. In
the
Virtual
Private
Cloud
section
of
your
navigation
pane,
click
Internet
Gateways.
13. Click
Create
Internet
Gateway
and
fill
out
the
web
form
as
follows:
a. Name
tag:
mapr-odt-gw
b. Click
Yes,
Create
c. Select
the
checkbox
next
to
the
mapr-odt-gw
object
and
click
Attach
to
VPC
d. From
the
VPC
drop-down
list,
select
mapr-odt-
vpc
and
click
Yes,
Attach
14. In
the
Virtual
Private
Cloud
section
of
your
navigation
pane,
click
Route
Tables.
15. Select
the
mapr-odt-routes
object
and
select
the
Routes
tab.
Click
Edit
and
fill
out
the
web
form
as
follows:
a. Designation:
0.0.0.0/0
b. Target:
mapr-odt-gw
Then
click
Save.
16. In
the
Virtual
Private
Cloud
section
of
your
navigation
pane,
click
Subnets.
17. Select
the
mapr-odt-subnets
object
and
select
the
Route
Table
tab.
Click
Edit
and
fill
out
the
web
form
as
follows:
a. From
the
Change
To
drop-down
list,
select
mapr-odt-routes.
b. Click
Save.
10
May 2015
5. From
the
drop-down
list
in
the
upper
right-hand
corner
of
the
EC2
web
page
(just
to
the
right
of
your
name),
select
the
availability
zone
nearest
to
where
you
are
physical
located.
Note
that
an
availability
zone
will
already
be
selected
based
on
the
contact
information
you
provided
when
you
provisioned
your
AWS
account.
6. In
the
INSTANCES
section
of
the
navigation
page,
click
the
Instances
link.
7. Click
Launch
Instance.
8. In
the
Step
1:
Choose
an
Amazon
Machine
Image
web
page,
scroll
down
to
the
bottom
of
the
page
and
select
the
64-bit
version
of
an
image
of
Red
Hat
version
6.4
or
6.5.
Note:
Red
Hat
7.0
is
NOT
currently
supported.
9. In
the
Step
2:
Choose
an
Instance
Type
web
page,
select
the
checkbox
for
m3.large,
then
click
Next:
Configure
Instance
Details.
10. In
the
Step
3:
Configure
Instance
Details
web
page,
fill
out
the
form
as
follows:
a. Number
of
instances:
3
b. Purchasing
option:
leave
Request
Spot
Instances
unchecked
c. Network:
mapr-odt-vpc
d. Subnet:
mapr-odt-subnet
e. Auto-assign
Public
IP:
enabled
f.
j.
11
May 2015
From
the
Type
drop-down
list,
select
All
ICMP.
From
the
Source
drop-down
list,
select
Anywhere.
Select
Create
a
new
key
pair
and
enter
mapr-odt-keypair
in
the
Key
pair
name:
text
field.
Then,
click
the
Download
Key
Pair
button.
OR
Select
Select
an
existing
key
pair
and
select
the
key
pair
from
the
key
pair
name
drop-
down
list.
IMPORTANT:
make
sure
you
save
a
copy
of
the
new
or
existing
key
pair
file
in
a
location
where
you
can
reference
it
throughout
your
training.
If
you
lose
this
file,
you
will
lose
access
to
your
AWS
instances
and
will
have
to
create
new
ones.
16. Click
Launch
Instances.
17. In
the
Launch
Status
web
page,
click
View
Instances.
18. Wait
for
the
instances
to
appear
in
the
running
state,
and
for
the
status
checks
to
complete.
19. Log
the
IP
address
of
the
VMs
for
later
use.
12
May 2015
8. In
the
Step
2:
Choose
an
Instance
Type
web
page,
select
the
checkbox
for
t1.micro,
then
click
Next:
Configure
Instance
Details.
9. In
the
Step
3:
Configure
Instance
Details
web
page,
fill
out
the
form
as
follows:
a. Number
of
instances:
1
b. Purchasing
option:
leave
Request
Spot
Instances
unchecked
c. Network:
mapr-odt-vpc
d. Subnet:
mapr-odt-subnet
e. Auto-assign
Public
IP:
enabled
f.
j.
13
May 2015
4. Log
in
as
ec2-user:
$
ssh
i
mapr-odt-keypair.pem
ec2-user@<VM
IP
Address>
6. Determine
and
log
the
internal
IP
address
of
the
VM
instance,
and
save
the
result:
#
hostname
14
May 2015
3. In
the
Compute
section
of
your
AWS
management
console,
click
the
EC2
link.
4. In
the
INSTANCES
section
of
the
left-side
navigation
pane,
click
the
Instances
link.
5. Select
the
instances
that
you
want
to
stop,
click
on
Actions,
and
select
Stop.
6. Click
Yes,
Stop.
To
restart
the
instances,
repeat
these
steps
but
select
Start
in
step
5.
Remember,
you
should
check
the
Public
IP
settings
of
your
VMs
and
note
any
changes
to
your
IP
address.
The
internal
IP
addresses
will
remain
consistent,
so
the
Passwordless
ssh
and
Hadoop
software
will
still
function
normally.
15