This document provides an overview of the FIWARE Lab cloud hosting service and FIWARE blueprint management. It describes how to create an account, deploy virtual machine instances, manage security groups, and launch blueprints which allow defining and deploying multi-tier application architectures on virtual servers. Blueprints can specify different software components and the servers they are deployed on, and are managed through a catalog interface that allows installing software, editing attributes, and deploying blueprint instances.

1. FIWARE and FIWARE Lab Service Offer
Fernando López
Telefonica I+D.
fernando.lopezaguilar@telefonica.com, @flopezaguilar (twitter)
http://tinyurl.com/fiware-lab-offer

2. Content
• Introduction to FI-LAB Cloud Hosting.
• Blueprints management.
• Catalogue & Marketplace.
• Reference Information.
2

3. FIWARE Lab Cloud Hosting
• Create your account in lab.fiware.eu.
• Enter in the Cloud Portal.
• Create your keypair (private key).
• Deploy your instance.
• Add a public IP.
• Open ports to the VM.
3

4. Add new user
4
Enter your email and password
to access to the FI-LAB.
If you do not have it or forgot it,
sign up or request for a new one.

5. Cloud Portal
5

6. Security
6
You must create a keypair
to access to the servers.

7. Security groups
7
Open ports in your VM.

8. Allocate IP to project
8
Allocate new IP

9. Launch Instances
9
Launch new
instance

10. Allocate Floating IP
10

11. Create a volume & Attach it to a server
11

12. Create a volume & Attach it to a server
12

13. Create container
13

14. Upload object
14

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

16. Deploy example
Blueprint template: fiware1
• 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 (e.g. tomcat, 2-5 servers).
• Blueprint Instance: Deployed in the
Servers: 2-5
Tier 1: Tomcat testbed.
Server: 1 Server: 1
Context Broker
Tier 2: Context Broker Tier 3: MongoDB
Context Broker
16

17. Blueprints management
17
You can open the Catalog of
Blueprint Template or create one
from the scratch.

18. Blueprints management
18
You must select a Keypair
to access to those servers.
You should specify the
maximum, minimum and current
number of servers

19. Blueprints management
19
Install software pressing
the mouse right click.
Edit special attributes like
default port.

20. FIWARE Catalogue (http://catalogue.fiware.org)
20

21. Where to obtain more information
21

22. Where to obtain more information
22

23. Where to obtain more information
23

24. Where to obtain more information
24

25. Where to obtain more information
25

26. Marketplace & Resource Catalogue
• The Marketplace is the enter point to discover, recommend and
use the services.
• The users can manage their own services (services as SaaS and
PaaS).
• There are three main services to be discovered in the catalogue:
• Generic Enablers (FIWARE Catalogue).
• Specific Enablers (XIFI repository).
• Other services (such as the presence of Sensor Network, Mobile
Network and, in general, other features different from the bare
data center).
• Integrated with the external repository as the FIWARE catalogue.
• integrated with the DCA and the Federation Identity Management.
26

27. Thanks!
Join us!
www.lab.fiware.org