Dear As we said some weeks ago, we need you to create dedicated instances in the testbed to be used later for the OIL. Some instruction about how to deploy VMs and create images, can be found in [1]. Thus, you need: 1.- To deploy a Global instance in the testbed. This Global instance needs to have the sanity checks passed to check everythin is ok 2.- To create an image from the Global Instance if possible 3.- Testbed people deploy a new instance for the lab from the image. In case, you cannot create an image, you should do a new installation. After testbed people have deployed the lab instance, you should check it is working. In addition, according to Juanjo's mail I would to report about the mandatory and optional GEs status. Please have a look at your GE and do whatever is needed. Thanks, Henar FI-WARE GEs (see note 1) GE implementation product(s) name(s) (see note 4) / owner To be made available in FI-LAB data updated on (UC): Image/testbed status Cloud Chapter Cloud Portal - / UPM Mandatory Cloud infrastructure Ready. To be deployed in the OIL DataCenter Resource Management - / IBM Mandatory Cloud infrastructure Deploying Object Storage - / Intel Mandatory Cloud infrastructure To be deployed in the OIL Software Deployment and Configuration (SDC) Sagitta / TID Mandatory Cloud infrastructure Ready. To be deployed in the OIL PaaS Manager Pegasus / TID Mandatory Cloud infrastructure Ready. To be deployed in the OIL Data Chapter Complex Event Processing (CEP) IBM PROactive Technology ONline (PROTON)/ IBM Mandatory imagen: cep-r2.3.3.0-img Sanity checks and image ready Publish/Subscribe Broker Context Awareness Platform / Telecom Italia Optional no image Publish/Subscribe Broker (see note 5) Orion Context Broker / Telefonica Mandatory orion-psb-image-R2 Sanity checks and image ready BigData Analysis COSMOS / Telefonica Mandatory check if to be deployed by images or recipes Compressed Domain Video Analysis Codoan / Siemens Mandatory no image Sanity checks for global instance. No dedicated instance Media-enhanced Query Broker QueryBroker / Siemens Optional no image Sanity checks for global instance. No dedicated instance Apps Chapter Service Description Repository Service Description Repository / SAP Mandatory (required for Store) no image Sanity checks for global instance. No dedicated instance Service Registry Service Registry / SAP Mandatory (required for Store) no image Sanity checks for global instance. No dedicated instance Marketplace (part of Business Framework) Marketplace / SAP Optional (check with UPM-Soriano if required for store) no image Sanity checks for global instance. No dedicated instance Store (part of Business Framework) - / UPM Mandatory Business Model/Business Elements (part of Business Framework) BEMES / iMinds Optional No deployed Revenue Shareing (part of Business Framework) - / TID Mandatory no image Sanity checks for global instance. No dedicated instance Light Semantic Composition Light Semantic Composition Editor - COMPEL/ ATOS Optional No deployed Application Mashup WireCloud / UPM Mandatory no image Sanity checks for global instance. No dedicated instance IoT Chapter (Backend) Configuration Management Orion Context Broker - TID Mandatory no sanity checks passed. Url not working (Backend) IoT Broker IoT Broker - NEC Mandatory no sanity checks passed. Url not working (Backend) Device Management IDAS DCA - TID Mandatory no sanity checks passed. Url not working Security Chapter Security Monitoring Service Level SIEM (SLS) / ATOS; Attack Path Engine/Thales Mandatory no sanity checks passed. Url not working Identity Management - / UPM Mandatory Cloud infrastructure To be deployed in the OIL Access Control - / Thales Mandatory no sanity checks passed. Url not working Content-based Security (Opt) CBS / Thales Optional no sanity checks passed. Url not working I2ND Chapter [1] https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V2_Operation_Cockpit#Creating_an_image_from_your_GE De: fiware-ge-owners-bounces at lists.fi-ware.eu [mailto:fiware-ge-owners-bounces at lists.fi-ware.eu] En nombre de HENAR MUÑOZ FRUTOS Enviado el: viernes, 12 de julio de 2013 12:51 Para: fiware-ge-owners at lists.fi-ware.eu CC: fiware-testbed at lists.fi-ware.eu Asunto: [Fiware-ge-owners] Preparing GEs for the OIL Dear all In order to make easier the installation of the GEs in the OIL, let's try to create image from the Global Instance when you have created it. Thus: - When you install your software, take into account that it should be installed as a service, and it should not have any configuration property which depends on the current IP. - before creating your image, you need to remove the file /etc/udev/rules.d/70-persistent-net.rules. - After that, you can go Edit your Instance, and create an snapshot of your instance - Once the snapshot has been created, go to Edit it and specify the snapshot as public. In this case, your snapshot will be an image which everybody can instantiate. - Finally, deploy a VM from your image, and check everything is ok. Please, don't forget to install your GE in the testbed and update the cockpit Thanks in advance, Regards, Henar De: HENAR MUÑOZ FRUTOS Enviado el: miércoles, 10 de julio de 2013 10:22 Para: 'fiware-ge-owners at lists.fi-ware.eu' CC: 'fiware-testbed at lists.fi-ware.eu' Asunto: Installation of GEs in the testbed Dear GE owners As you know, we need to have the GEs installed in the testbed, the sanity checks passed and the information introduced in the catalogue by the end of this month. The way to monitor this task is the cockpit [1]. Just to let you know, there are % progress column, one for the Global Instance status and the other one for the Dedicated Instance: - 1.- A GE as a global instance means as a service. It is going to be a GE instance which is going to be shared by all the UCs, and whose service endpoint is going to appear in the catalogue. For Global instances, we have the following progress status: o 40% VM deploy: You should deploy a VM in the testbed to install your GE software. For installing a VM in the testbed, please have a look at the wiki [2]. o 60%: GE installed. You have installed the GE software in the VM o 70%: sanity checks passed. Testbed people has passed the sanity checks of your GE o 80%: Your GE is correctly in the catalogue - 2.- A GE as a dedicated instance. In this case, each UC can have an instance of your GE. To get this, you can create an image from your dedicated instance, using the Cloud capabilities or creating recipes. It is going to be a webminar on 17th for explaining how. According to it, the status for dedicated instances is: o 20=image generated: You have created the GE image by using the Cloud capabilities. o 30: image ok: Testbed people check that this image is ok, deploy a VM from this image and passing sanity checks o 40=recipes generated: You have create the recipes o 50: recipes ok: Testbed people check that the recipes are ok. o 60: Information in the catalogue. The information is stores in the catalogue. Thus, please update the cockpit with your GE status. If you have any doubt, you can contact me. Thanks, Regards, Henar [1] https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V2_Implementation_Cockpit#Cockpit [2] https://forge.fi-ware.eu/plugins/mediawiki/wiki/testbed/index.php/Testbed_V2_Operation_Cockpit ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-testbed/attachments/20130813/53c263f1/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy