CloudBroker usage
Zoltán Farkas
MTA SZTAKI LPDS
[email protected]
SCI-BUS is supported by the FP7 Capacities Programme under contract nr RI-283481
Outline
• Tutorial part:
– Define BIFI OpenStack resource access in
CloudBroker
– Deploy a new software in a BIFI OpenStack image
– Configure the new software in CloudBroker
• (Hands-on part:
– Modify existing AutoDock workflow to run on the
CloudBroker Platform
– Skipped: CloudBroker Platform update breaks
gUSE’s CloudBroker support)
Targeted audience
• Mostly system administrators
• Partly workflow developers
• Required knowledge:
– Linux
– Eucalyptus tools (euca-* commands)
– General concept about cloud systems
Configure BIFI access in
CloudBroker I.
• First, let’s get our EC2 credentials:
– Log in through http://dpm-arg.bifi.unizar.es
– Click „Settings” in the top
– Select „EC2 Credentials” at the left
– Click „Download EC2 Credentials”
– The zip contains a file called ‘ec2rc.sh’, with all the
necessary information
Configure BIFI access in
CloudBroker II.
• Next, define a new resource in CloudBroker:
–
–
–
–
–
–
–
–
–
–
–
Log in through https://scibus.cloudbroker.com/
Click „Resources” -> „New”
„Resource type” should be „OpenStack EC2”
Enter some specifier
„Account ID” should be the value of EC2_USER_ID in ec2rc.sh
„Access key ID” should be the value of EC2_ACCESS_KEY in ec2rc.sh
„Secret access key” should be the value of EC2_SECRET_KEY in
ec2rc.sh
Click on „Expert options”
Set „Maximum nodes” to e.g. 10
Set „API URL” to the value of EC2_URL in ec2rc.sh
Click „Save”
Configure BIFI access in
CloudBroker III.
• Next, define a new instance type:
–
–
–
–
–
–
–
–
–
Click „Instance types” -> „New”
Set some „Human readable name”
Select the „Resource” as defined earlier
Set „Architecture”
Set „CPUs”, „CPU cores”, „Memory [GB]” and „API name”
accroding to OpenStack’s flavor type
Click „Expert options”
Set „Maximum nodes”
Set „Root storage” and „Instance storage” according to
OpenStack’s flavor type
Click „Save”
Configure BIFI access in
CloudBroker IV.
• Next, define a new region:
– Click „Regions” -> „New”
– Set some „Human readable name”
– Select the „Resource” as defined earlier
– Click „Expert options”
– Set „Maximum nodes”
– Set „Storage” to the storage you’d like to use
– Click „Save”
Configure BIFI access in
CloudBroker V.
• Now, activate everything:
– Region
– Instance type
– Resource
Status
• At this point, we have a new resource defined
that is connected to a specific account within
BIFI’s OpenStack cloud
• Next step: set up a new virtual machine image
with some software in BIFI’s OpenStack cloud,
and define a new Software/Executable for that
in CloudBroker
Deploy a new software I.
• First, we’re going to start a new VM:
– Log in through http://dpm-arg.bifi.unizar.es
– Click „Images & Snapshots”
– Select an image or instance (matching your
requirements) and start it
• Select and upload a keypair to have ssh access to the
machine
– You can assign a public IP to the VM under
„Access & Security”
Deploy a new software II.
• Next, enter the VM and install the software:
– Check your VM’s public IP
– In case of Ubuntu, log in with user ‘ubuntu’ and
your ssh key
– Perform the installation:
• apt-get install …
• wget …
• yum install …
– Remember the installation prefix and name of
your executable!
Deploy a new software III.
• Finally, create a new image:
– Under „Instances & Volumes”, below „Actions”,
select „Snapshot”
– Under „Images & Snapshots”, wait as long as your
new „Instance Snapshot” becomes „Active”
– Under „Actions”, select „Edit”
– Click „Update Image”
– Get the image’s ID using euca-describe-images
Status
• We have the BIFI OpenStack access defined as
a resource within the CloudBroker Platform
• We have the software deployed on an image
in BIFI’s OpenStack cloud
• Next, we will define a software for this in the
CloudBroker Platform
CloudBroker Software definition
I.
• First, define the Software:
– Log in through https://scibus.cloudbroker.com/
– Go to „Software” / „New”
– Define a „Product” and a „Version”
– Click „Save”
CloudBroker Software definition
II.
• Next, define the Executable:
– Go to „Software” / „Executables” / „New”
– For „Software”, select the previously defined
software
– Set „Binary” to the name (basename) of the
executable you deployed on the VM
CloudBroker Software definition
III.
• Next, define the Deployment:
– First, activate the software: under „Software”, under
„Actions” select „Deploy”
– Go to „Software” / „Deployments” / „New”
– Set everything according to your settings
– „Installation directory” should be the path where your
executable resides on the VM
– Click „Expert Options”
– Set the „Image ID” as queried by euca-describe-images
– Set „Username” (‘ubuntu’ in case of Ubuntu)
CloudBroker Software definition
IV.
• Finally, activate:
– The deployment
– The Software
Status
• Our BIFI access is defined as a resources
within CloudBroker
• We have deployed a new software on a BIFI
VM image
• The software is ready-to-use from within
CloudBroker
Video tutorial URLs
• CloudBroker Platform Demo:
– http://youtu.be/sxW59GxVUzQ
• BIFI software deployment:
– http://youtu.be/sf5VyUIGYqk
• CloudBroker Resource definition:
– http://youtu.be/saQLsYTlpr0
• CloudBroker Software definition:
– http://youtu.be/baLasIf-vNc
• Custom jobs from WS-PGRADE in CloudBroker:
– http://youtu.bezAzzD81IrtU