Making a Lab Request
Ericsson OPNFV Lab
Updated 5/4/2016
Overview
 The following slides will guide you through the process of doing the following:
 Overview of the Lab Request Process
 Process Inputs – Things you will need to provide in JIRA
 Lab Request Description Example – How to Describe your Lab request
 Creating a Linux Foundation Account (Required to make the Jira Tickets)
 Downloading Generating your Key with Putty Gen (Windows) or Linux
 Creating your JIRA ticket
 Sample JIRA Ticket Screen
Montreal OPNFV LAB Request Process
Jira Ticket
Created and
Assigned
Lab Released
•Booking
renewed via JIRA
or ticket closed.
Lab In Use
Lab Request
Validated
Lab Staged
and Delivered
OPNFV Lab Request Process Inputs
All lab access and hardware requests should be done via a JIRA ticket. All OPNFV users
require a Linux Foundation account in order to be able to create JIRA requests within the
OPNFV PHAROS Lab Community.
 All requestors of access/resources should become familiar with this page
https://wiki.opnfv.org/display/pharos/Pharos+Home
Each of the OPNFV Community labs provides its own unique access method. As such, each
Lab Access request should include the following:
 A SSH KEY for each user that is requesting access – shared keys/accounts are not allowed
 A PGP KEY for each user that is requesting access – this will allow for encrypted transmission
of credentials and information when required.
 Expected Duration of Lab Usage (generally 6-8 week cycles depending on the lab)
 Each User should also provide the following in their request:
 Full name, Email address, Project Name, PTL Name (if applicable)
Sample Lab Request Description
When making your JIRA ticket, the following information (at a minimum) should
be outlined in the ticket
Lab Type
(PHAROS)
•BASELINE
•ODL(VXLAN)
•DPDK
•SR-IOV
•BONDED
Target Release
(OPNFV)
•Arno
•Brahmaputra
•Colorado
Method/Density
•Bare Metal
•Virtual
•CPU/RAM/DISK
Topology
•# Controllers
•# Computes
•# SDNc
CI / Test Suite
Info
•CI integration
needed?
•Yardstick,
Functest, Rally,
Tempest
needed?
Creating a LF account
 All OPNFV users must have a LF account, in order to satisfy NDA and other
rules as well as to be able to make JIRA tickets, contribute to the Wiki,
update on projects, etc.
 Go to the following link to create your account (note: in general you should
use your work email, not social media)
 https://identity.linuxfoundation.org/user?destination=cas/login
Download Putty Gen and Generate a
Key
 Use the following link to download PuttyGen (this is needed to create a key
for use with the lab with Putty – you can use whatever other method you
like to generate and attached your id_rsa.pub key).
https://the.earth.li/~sgtatham/putty/latest/x86/puttygen.exe
You need to attach the key created in PuttyGen (or if you generated it elsewhere)
to the JIRA ticket – one per user, no shared accounts. You can refer to the following
video on how to generate a key with putty Gen.
https://www.youtube.com/watch?v=-92wEg68SKQ
Creating your JIRA Ticket
Here are the steps for making your ticket:
- All JIRA requests for labs should be made under the PHAROS project.
1. Create a new issue in Jira with type Task (https://jira.opnfv.org/projects/PHAROS/summary)
2. Assign Priority as: Blocker; Critical; Major; Minor; Trivial
3. Select applicable release Version: e.g. Brahmaputra
4. Use Component to assign as:
a) POD Access Request (Request to add/remove an individuals (VPN) access for a community lab)
b) POD Connectivity Request (Request to add/remove lab firewall rules to connect POD to remote
service e.g. CI)
c) POD Hardware Request (Request to add/remove POD hardware e.g. NIC, memory, ...)
d) POD Network Request (Request to add/remove/change POD or Host network configuration)
e) POD Issue (Report an issue with a POD for the lab owner to troubleshoot)
f) Adding labels helps (FUEL, RELEASE, etc)
5. Assign ticket to Lab Resp. (See here https://wiki.opnfv.org/pharos?&#community_test_labs)
What will happen next
 You can view the status of your ticket in JIRA always and should receive
and email when your request is updated.
 Depending on the time in a given release cycle, turnaround time on lab
requests may vary.