Skip to content

Latest commit

 

History

History
191 lines (149 loc) · 6.34 KB

README.md

File metadata and controls

191 lines (149 loc) · 6.34 KB

PSG Event Oct 2017 @ Barcelona

As part of the event some deep dive sessions are planned, please go through this guide to get what is needed.

Preparing for running the labs

Software you need to install or accounts you need to have to be able to carry on the labs during the workshops.

Operating System

You should be able to run the labs if you are running on the following OS choices

  • macOS
  • Windows 10
    • Make sure to enable hardware virtualisation in BIOS
  • Linux e.g. CentOS or Ubuntu

Accounts

These accounts are needed to run through the labs:

  • AWS

    • You will get assigned credentials by your instructor to access AWS to execute the relevant labs
    • AWS Username, AccessKeyId, SecretAccessKey
  • Docker ID for Docker Hub

    • Create a Docker Hub account if you don't have one https://hub.docker.com/
    • Note your docker id and password
    • After you get Docker installed, log in to your Docker Hub

Screenshot

Software

TIBCO

Download TIBCO installers from https://edelivery.tibco.com

install the following software on your machine. ( if you prefer to use a vm to leave your machine neat, make yourself at home ! )

Thirdparty

For Linux users use your package manager for most of these, or follow the links provided below. For macOS users homebrew is a decent option to install thirdparty software https://brew.sh/

I'm including the homebrew commands to download some sofware for those on macOS

If you fancy using a vagrant box which provides some of these components, GO HERE

Option A - local installs

install the following to your machine

Option B - Vagrant box

use vagrant box to have the following preinstalled

  • AWS cli
  • kubectl
  • kops

To use vagrant, please install:

  • Virtualbox - https://www.virtualbox.org/wiki/Downloads (5.1.28)
    brew cask install virtualbox
  • Vagrant - https://www.vagrantup.com/downloads.html
    brew cask install vagrant
    • if you're using vagrant, you might find it useful to copy stuff from your local machine to vagrant box
    vagrant scp /path/to/local.file vagrant-machine-name:/path/to/vagrant/box.file
  • optional - a nice vagrant manager UI on macOS
    brew cask install vagrant-manager

Screenshot To get the vagrant box please do the following

  1. create a directory, name it for e.g. psg_barcelona
  2. cd to the directory, init the vagrant box
vagrant init onlyfreeaccess/BWCE
  1. Setup provider env var (on UNIX-like systems use):
export VAGRANT_DEFAULT_PROVIDER=virtualbox
  1. run this command to start the vagrant box ( You have to be inside the directory e.g. psg_barcelona )
vagrant up

Labs

The following activites need to take place to be able to run the labs

Lab1

In this lab you should end up with a BWCE app. You need to generate BWCE base image, as well as include ems libraries. You can use the following images if you need to

  • BWCE 2.3.1 base image
    docker pull mshahat/bwce:2.3.1
  • BWCE 2.3.1 base image + EMS libs
    docker pull mshahat/bwce:2.3.1.ems
  • BWCE 2.3.1 app
    docker pull mshahat/bw5tobwce:1.0

Lab2

For this lab you need to generate a key pair

  1. Go to https://console.aws.amazon.com/console/home
  2. Use account ID in Lab2 instructions
  3. Use username and password assigned by your instructor --> "username"Tibco123
  4. Once logged in, go to All Services -> Compute -> EC2
  5. On the left bar under Network & Security , go to Key Pairs
  6. Create Key Pair -> Key Pair Name: "username"-keypair ... This will download a .pem file to your machine which is your private key
  7. Use this to generate a public key

Windows

Use Putty key generator to generate your public key

  1. Load private key
  2. click on Generate
  3. copy and paste into a file, save as .pub file

macOS

use ssh-keygen to generate your public key before you do , please make sure to change file permissions

chmod 400 /path/to/your/keypair.pem

then

ssh-keygen -y -f /path/to/your/keypair.pem > /path/to/save/your/public/key/key.pub
  1. Copy AWS private and public key files to the vagrant box. The easiest way to transfer files from the host to the VM is to just put them in the same directory as the Vagrantfile (psg_brcelona) - that directory is automatically mounted under /vagrant in the VM so you can copy or use them directly from the VM."

  2. SSH into the vagrant box

 vagrant ssh
  1. Copy Public and Private Keys from /vagrant to ~/.ssh on vagrant box

  2. Logout

 vagrant logout