Brief description how to use FIWARE Lab Cloud to deploy your resources and the differents steps and recomendations that you have to follow to resolve any problem

1. Setting up your virtual infrastructure
using FIWARE Lab Cloud
Fernando López Aguilar
FIWARE Cloud and Platform Senior Expert
fernando.lopez@fiware.org
@flopezaguilar

2. Content
 FIWARE Lab Cloud Hosting: Overview and Architecture
 FIWARE Lab: Basic functionalities
• FIWARE Identity Services
• FIWARE Compute Services
• FIWARE Storage Services
 FIWARE Lab: PaaS, working with Blueprints
 Reference Information
1

3. FIWARE Lab Cloud Hosting: Overview
and Architecture
2

4. FIWARE Lab Cloud Hosting
3

5. FIWARE Lab Cloud Hosting
4
Cloud Portal
PaaS
SDC Monitoring
Account

6. Summary
 Account: Manages identity and organizations; provides
authentication and authorization for other services (OpenStack
Keystone).
 Compute: Manages the lifecycle of compute instances.
Responsibilities include spawning, scheduling and decommissioning
of VMs (OpenStack Nova).
 Network: Enable Network-Connectivity-as-a-Service for other
services, e.g. Compute, (OpenStack Neutron).
 Storage:
• Persistent block storage for running compute instances (OpenStack
Cinder).
• Stores and retrieves arbitrary unstructured data object and provide
storage for other services, e.g. Image, (OpenStack Swift).
5

7. Summary
 Image: Stores and retrieves VM disk images used by compute
(OpenStack Glance).
 Monitoring: Monitoring information about VMs
 SDC: Deploying Software in VMs
 PaaS Manager
• Working with regions
• Creating Tiers and deploying Blueprints
6

8. FIWARE Lab Cloud – Multiregion
7

9. FIWARE Lab Cloud – Multiregion
8
http://fi-health.lab.fiware.org/

10. Basic functionalities: Identity Services
9

11. Identity Services
 Creating an account
• https://account.lab.fiware.org
 Understanding account categories
 Understanding organizations
• Mapped to OS tenants
 Signing in in Cloud Portal
• https://cloud.lab.fi-ware.org
• SSO
10

12. Add new user
11
Enter your email and password
to access to the FIWARE Lab.
If you do not have it or forgot it,
sign up or request for a new one.

13. Create new account
12
You can ask for a trial account.
In case there will be not,
you will obtain a basic account

14. FIWARE Lab Account Categories
13
Trial
Basic Community
1
2
3
4
5
6
7

15. Asking for a community account upgrade
14

16. Asking for a community account upgrade
15

17. Basic functionalities: Compute Services
16

18. FIWARE Lab Cloud Hosting: basic
functionalities
 Create your keypair (private key).
 Create security group (incoming ports to VM, e.g. 22 for ssh)
 Deploy your instance
• choice from a library of predefined images, e.g. Centros, Ubuntu, etc.
• choice flavor of resource configuration.
• choice security group.
• choice keypair to ssh into VM.
• specify configuration scripts (optional).
 Associate public IP with the instance.
17

19. Create keypair
18
You must create a keypair
to access to the servers.

20. Create keypair
19
You must create a keypair
to access to the servers.

21. Create keypair
20
You must create a keypair
to access to the servers.

22. How to connect from
Windows (I)
 Install PuTTY and PuTTYgen from http://www.putty.org/
 Convert your Keypair to PPK
• Start PuTTYgen (e.g. From the Start menu, click All Programs > PuTTY
> PuTTYgen)
• Click Load and select the Keypair file (e.g. my_cert.pem). You’ll need to
display All Files (*.*) to see your Keypair.
• Click Open. And select the destination path and name of your PPK file.
21

23. How to connect from
Windows (II)
 Connect to your instance
• Start PuTTY.
• Put the public IP of your instance (default
SSH port is 22).
 Configure it to use your Keypair
• Open the Auth submenu (Connection >
SSH > Auth)
• Select the recently generated Private key
file (PPK file).
22

24. How to obtain your public key from pem file
 Secure to have the proper permissions:
$ chmod 600 private.pem
 Create the public key:
$ ssh-keygen –y –f private.pem >> publickey.pub
 Add the public key to your system
$ cat publickey.pub >> ~/.ssh/id_rsa.pub
23

25. How to import your public key into
OpenStack
 Just go to the .ssh directory and
execute
$cat ~/.ssh/id_rsa.pub
 Copy and Paste the content in the
‘Public Key’ textarea.
 Assign a keypair name
 Press Import Keypair.
24

26. Security groups
25
Create a Security Group

27. Security groups
26

28. Create and edit Security Group rules
27

29. Create and edit Security Group rules
28

30. Launch Instances
29
Launch new
instance

31. Launch Instances
30

32. Launch Instances
31

33. Launch Instances
32

34. Launch Instances
33
Do not change
anything here

35. Launch Instances
34

36. Instances Overview
35

37. Allocate IP to Project
36
Allocate new IP

38. Allocate IP to Project
37
Allocate new IP

39. Allocate IP to Project
38

40. Allocate IP to Project
39

41. Allocate IP to Project
40

42. Access to the instance
41

43. Basic functionalities: Storage Services
42

44. FIWARE Lab Cloud Hosting: storage
functionalities
 Create volumes
 Attach volume to servers
 Configure the instance to detect the new volume
 Create containers in the object storage
 Upload objects into your containers
 Object Storage API
43

45. Create a volume
44

46. Attach a volume to an instance
45

47. Volume attached
46

48. See the new volume with fdisk
47

49. Create a partition table on our new volume
48

50. Create a ext3 file system
49

51. Mounting our new volume.
 Create a mount point called /data and mount /dev/vdb1
$ sudo mkdir /data
$ sudo mount /dev/vdb1 /data
 At this point, the volume’s storage is accessible to Linux.
 Modify /etc/fstab to allow remounts the volume on restarts.
50

52. Check the created volume
51

53. Object Storage: Create a container
52

54. Upload an object into the container
53

55. Upload an object to the container
54

56. Extended functionalities: PaaS, working
with Blueprints
55

57. FIWARE Lab Cloud Hosting
 Deploying components for your application.
 Create blueprint templates.
 Create Tiers on a blueprint template.
 Launch blueprint templates -> create blueprint instances
 See details of the blueprint instance
 Check the SW installed on the blueprint instance
56

58. Real scenario
 Users want to define lots of parameters.
• Password, ports, default installation.
 Users want to install several things in the same server.
• Tomcat + git, tomcat + java + git, …
 Users need to deploy complex environment.
• One server for Tomcat, another for MySQL, …
 Some parameters are unknown before instantiate the system.
57

59. Deploying components for your application
 Deploying applications and not only Servers.
 Ad hoc installation (not template usage).
 Managing applications in Servers (install, uninstall, configure,
snapshot…).
 Deploying different environments for that applications.
58

60. Deploy example  Blueprint Template: platform specification to
be deployed.
59
Blueprint template: fiware1
Tier 1: Tomcat
Tier 2: Context Broker Tier 3: MongoDB
Server: 1 Server: 1
Servers: 2-5
Context Broker
Context Broker
Blueprint instance: fiware1-instance
 Blueprint Template: platform specification to
be deployed.
 Tier: Each kind of software and server to be
deployed.
 Blueprint Template: platform specification to
be deployed.
 Tier: Each kind of software and server to be
deployed.
 Each Tier can be deployed in one or several
servers.
 Blueprint Template: platform specification to
be deployed.
 Tier: Each kind of software and server to be
deployed.
 Each Tier can be deployed in one or several
servers.
 Blueprint Instance: Deployed in the testbed.

61. Create a new blueprint template
60
Press the option
“Blueprint Templates”
from menu
You can open the Catalog of
Blueprint Template or create one
from the scratch.

62. Create a new blueprint template
61
You should introduce the
“Name” and the “Description”.

63. Add tiers
62
To add new Tier, press
“demo-template” name.

64. Add tiers
63
After press “Add Tier” you see
this windows to define
the servers of this tier.
You must select a Keypair
to access to those servers.
You should specify the
maximum, minimum and current
number of servers

65. Add software in tier
64
Install software pressing
the mouse right click.

66. Add software in tier
65
Edit special attributes like
default port.

67. Add software in tier
66

68. Connect network
67
Drag&Drop the network
to connect the tier..
Introduce an alias to connect
together several tiers.

69. Topology
68

70. Launch a Blueprint Template, Blueprint Instance
69
Press “Action” and select
“Launch Template” to launch
the Instance.

71. Launch a Blueprint Template, Blueprint Instance
70
You should specify the “Name”
and “Description” for
your blueprint.

72. Launch a Blueprint Template, Blueprint Instance
71
Firstly, the deployment
of infrastructure.

73. Launch a Blueprint Template, Blueprint Instance
72
Secondly, the installation
of the software.

74. Launch a Blueprint Template, Blueprint Instance
73
Finally, if all was ok.
Pressing the name you can
see the tiers of this blueprint.

75. 74
Launch a Blueprint Template, Blueprint Instance
Press it to get information
of your server.

76. 75
Launch a Blueprint Template, Blueprint Instance

77. 76
Launch a Blueprint Template, Blueprint Instance

78. 77
Launch a Blueprint Template, Blueprint Instance

79. Reference information
78

80. Documentation
 FIWARE Cloud Portal:
• Documentation: http://catalogue.fi-ware.org/enablers/self-service-
interfaces-cloud-portal-upm
 FIWARE Cloud Infrastructure
• Account: http://catalogue.fi-ware.org/enablers/identity-management-
keyrock
• SDC: http://catalogue.fi-ware.org/enablers/software-deployment-
configuration-sagitta
• PaaS Manager: http://catalogue.fi-ware.org/enablers/paas-manager-
pegasus
 FIWARE eLearning Platform
• http://edu.fi-ware.org/
79

81. 80

82. 81
If you have any question or problem contact to
fiware-lab-help@lists.fiware.org
You can go to stackoverflow and ask question
with the tag fiware

83. Thank you!
http://fiware.org
Follow @FIWARE on Twitter
82

84. Thank you!
http://fiware.org
Follow @FIWARE on Twitter