Fiware cloud developers week brussels
Download as PPTX, PDF0 likes1,274 views
- The FIWARE Lab provides cloud hosting and infrastructure as a service capabilities including compute, network, storage, and PaaS functionality. - It utilizes OpenStack for core infrastructure services including compute (Nova), networking (Neutron), storage (Cinder, Swift), and identity (Keystone). - The PaaS Manager allows users to define templates called Blueprints to deploy multi-tier applications and software stacks across the virtual infrastructure in an automated manner.
Fiware cloud developers week brussels
- 1. FIWARE Cloud Fernando López Telefónica I+D Cloud Architects, FIWARE fernando.lopezaguilar@telefonica.com, @flopezaguilar Kenneth Nagin IBM Cloud Chapter Lead, FIWARE nagin@il.ibm.com
- 2. Content • FIWARE Lab Cloud Hosting: Overview and Architecture • FIWARE Lab: Basic functionalities –FIWARE Compute Services –FIWARE Network Services –FIWARE Storage Services • FIWARE Lab: PaaS, working with Blueprints • Reference Information 2
- 3. FIWARE Lab Cloud Hosting: Overview and Architecture 3
- 4. FIWARE Lab Cloud Hosting 4
- 5. FIWARE Lab Cloud Hosting Cloud Portal PaaS SDC Monitoring Account 5 Compute Object Storage
- 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) • 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 8
- 9. Account • Creating an account – https://account.lab.fi-ware.org • Understanding organizations – Mapped to OS tenants • Signing in in Cloud Portal – https://cloud.lab.fi-ware.org – SSO 9
- 10. Add new user 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. 10
- 11. FIWARE Lab: Basic functionalities 11
- 12. FIWARE Lab: Basic functionalities • Create keypair (private key) • Create security group (incoming ports to VM, e.g. 22 for ssh) • Deploy an instance –choice from a library of predefined images, e.g. Centros, Ubuntu, etc. –choice flavor of resource configuration (vCPU, memory, user disk, ephemeral disk). –choice security group. –choice keypair to ssh into VM. –specify configuration scripts (optional). • Associate public IP with VM. • Create private networks and associate to VMs. • Create storage volumes and attach to VM. 12
- 13. Create keypair You must create a keypair to access to the servers. 13
- 14. Security groups Create a Security Group 14
- 15. Create and edit Security Group rules 15
- 19. Allocate IP to a project Allocate new IP 19
- 22. Access to the instance 22
- 23. FIWARE Network • Multi-tenancy: Do I need to isolate tenants? – Even if you trust them, you might want isolation. – Tenant creates his own network(s) and router(s) allowing complex network topologies for multi-tier applications. • Create private network with subnets. • Create router and interfaces. • Set gateway. • Deploy instance on network. 23
- 24. Create your own network Create a new Network 24
- 25. Add subnet associate to the previous network Add subnet 25
- 26. Add subnet associate to the previous network Add Network Address (CIDR) Define DNS server 26
- 27. Create a router Assign router name 27
- 28. Set gateway Assign a gateway to the router 28
- 30. Assign subnet Double Click on the router name 30
- 32. Assign subnet Select the network to connect 32
- 33. Deploy a new instance: Networking Select the network to connect 33
- 35. Attach a volume to an instance 35
- 37. FIWARE Object Store, i.e. OpenStack Swift • Create container • Upload objects, i.e. files • Download objects • Storlets (to be deployed) – Small computer programs that can be deployed and get executed inside a Swift cluster in an isolated manner. – Bring the compute to the data thus saving on the bandwidth required to bring the data to the compute. – Based on a Swift cluster empowered with the storlet engine Swift middleware and Docker, which allows the execution of user written code inside Swift in an isolated manner.
- 38. Object Storage API • http://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Object_Storage_- _User_and_Programmers_Guide • Authentication to get initial token username='email@company.com' password='mypassword' curl -d '{"auth": {"passwordCredentials": {"username":"'$username'", "password":"'$password'"}}}' -H 'Content-type: aplication/json' http://cloud.lab.fi- ware.org:4730/v2.0/tokens -vvv • Use initial token to get tenant curl -H 'x-auth-token: '$token http://cloud.lab.fi-ware.org:4730/v2.0/tenants • Authenticate tenant to get token for Object Storage curl -d '{"auth": {"passwordCredentials": {"username":"'$username'", "password":"'$password'"}, "tenantId":"'$tenantId'"}}' -H 'Content-type: aplication/json' http://cloud.lab.fi-ware.org:4730/v2.0/tokens • Object Storage URL http://130.206.82.9:8080/v1/AUTH_tenantId 38
- 39. FIWARE Lab: PaaS, working with Blueprints 39
- 40. FIWARE PaaS • 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. 40
- 41. 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. 41
- 42. 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 testbed. Tier 1: Tomcat Tier 2: Context Broker Tier 3: MongoDB Server: 1 Server: 1 Servers: 2-5 Context Broker Context Broker 42
- 43. Create a new blueprint template 43 Press the option “Blueprint Templates” from menu You can open the Catalog of Blueprint Template or create one from the scratch.
- 44. Create a new blueprint template 44 You should introduce the “Name” and the “Description”.
- 45. Add tiers 45 To add new Tier, press “hh-template” name.
- 46. Add tiers 46 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
- 47. Add software in tier 47 Install software pressing the mouse right click.
- 48. Add software in tier 48 Edit special attributes like default port.
- 49. Add software in tier 49
- 50. Connect network 50 Drag&Drop the network to connect the tier.. Introduce an alias to connect together several tiers.
- 51. Topology 51
- 52. Launch a Blueprint Template -> Blueprint Instance 52 Press “Action” and select “Launch Template” to launch the Instance.
- 53. Launch a Blueprint Template -> Blueprint Instance 53 You should specify the “Name” and “Description” for your blueprint.
- 54. Demo 54 Firstly, the deployment of infrastructure.
- 55. Demo 55 Secondly, the installation of the software.
- 56. Demo 56 Finally, if all was ok. Pressing the name you can see the tiers of this blueprint.
- 57. Demo 57 Press it to get information of your server.
- 58. Demo 58
- 60. 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/ • More detailed presentation – Slides: http://tinyurl.com/fiwarelab-cloud 60
- 62. If you have any question or problem contact to fiware-lab-help@lists.fi-ware.org You can go to stackoverflow and ask question with the tag fiware and/or filab. 62
- 64. Thanks!Thanks!