Ok, la semana que viene actualizaremos la versión de ese portal. Probablemente tenga una versión antigua. Saludos, Javier. On 15 April 2014 08:50, HENAR MUÑOZ FRUTOS <henar at tid.es> wrote: > Hola > > > > Parece que hay problemas con el portal de la 61 y lanza 10 peticiones cada > vez que se solicita algo. Me suena que en FI-LAB alguna vez también ha > pasado lo mismo. Lo podeis mirar? > > Gracias, > > Henar > > > > *De:* pallav.gupta at orange.com [mailto:pallav.gupta at orange.com] > *Enviado el:* martes, 15 de abril de 2014 6:59 > *Para:* HENAR MUÑOZ FRUTOS; SERGIO GARCIA GOMEZ; RAMPARANY Fano IMT/OLPS; > JOSE IGNACIO CARRETERO GUARDE > *CC:* SRIVASTAVA Utkarsh SCE/IBNF; NAGELLEN Thierry IMT/OLPS; MIGUEL > CARRILLO PACHECO; MISHRA Vijay SCE/IBNF; MATHUR Antriksh SCE/IBNF > *Asunto:* RE: About how to create recipes > > > > Hello, > > > > Thanks for creating the testbed accounts and we are able to access GE > Cloud portal http://130.206.80.61/. > > > > While setting up the development environment we are facing following > problems: > > > > *prob1:* We are able to create instance from the image. But instead of > creating single instance of an image, portal is creating multiple instances > automatically. > > For example: I chose *“paas-chef-solo-templ” *image & click on launch > button. Openstack admin panel has created 10 instances of single image > though I selected “1” instance to be created. > > > > *prob2:* We’re getting error in launching instance chefsolo. > > > > *prob3:* The IP address is not being generated of newly created instance. > > > > Below screenshot shows Instance tab and problems: > > > > > > > > > > *prob4:* While creating a test volume, the cloud portal has created 9 > volumes automatically. > > > > *prob5:* We’re getting an error in deleting testvol. > > > > Below screenshot shows Volumes tab and problems: > > > > > > > > Kindly look into these problems. > > > > I’ve one more query regarding the development of flod enabler recipes, Do > we have any package (installer) of flod enabler on FI-Ware repository? > because this will be required for us when we start creating *install.rb*recipe of flod enabler. > > > > > > Thanks & Regards, > > Pallav Gupta > > > > *Pallav Gupta, MCTS* > > *Sr. Software Engineer* > > International Centers - Orange Labs P&S - India > > Tower B, 8th Floor, DLF Infinity Towers, DLF Cyber City Phase - II > Gurgaon - 122002, Haryana, INDIA > > pallav.gupta at orange.com > > ( Tel: +91 124 435 8000 ( Mobile: +91 783 847 5602 > > ( CVS: 7 357 6094 ( CVS Access: +33 1 4445 1037 > > > > *From:* HENAR MUÑOZ FRUTOS [mailto:henar at tid.es] > *Sent:* Monday, April 14, 2014 12:48 > *To:* GUPTA Pallav SCE/IBNF; SERGIO GARCIA GOMEZ; RAMPARANY Fano > IMT/OLPS; JOSE IGNACIO CARRETERO GUARDE > *Cc:* SRIVASTAVA Utkarsh SCE/IBNF; NAGELLEN Thierry IMT/OLPS; MIGUEL > CARRILLO PACHECO > *Subject:* RE: About how to create recipes > > > > Hi > > > > I have created two accounts for the GE Cloud portal http://130.206.80.61/. > I will provide the credentials in a separated mail. > > Regards, > > Henar > > > > *De:* pallav.gupta at orange.com [mailto:pallav.gupta at orange.com<pallav.gupta at orange.com>] > > *Enviado el:* lunes, 14 de abril de 2014 8:55 > *Para:* SERGIO GARCIA GOMEZ; RAMPARANY Fano IMT/OLPS; JOSE IGNACIO > CARRETERO GUARDE > *CC:* SRIVASTAVA Utkarsh SCE/IBNF; NAGELLEN Thierry IMT/OLPS; HENAR MUÑOZ > FRUTOS; MIGUEL CARRILLO PACHECO > *Asunto:* RE: About how to create recipes > > > > Hello, > > > > As per the below mail, we are waiting for the creation of testbed account > for starting development of the cookbook & recipes for *“FLOD enabler”*. > > > > Kindly create following two testbed accounts (the specific one for GE > owners): > > > > pallav.gupta at orange.com > > utkarsh.srivastava at orange.com > > > > In case of any query or concern please let us know. > > > > > > Thanks & Regards, > > Pallav Gupta > > > > *Pallav Gupta, MCTS* > > *Sr. Software Engineer* > > International Centers - Orange Labs P&S - India > > Tower B, 8th Floor, DLF Infinity Towers, DLF Cyber City Phase - II > Gurgaon - 122002, Haryana, INDIA > > pallav.gupta at orange.com > > ( Tel: +91 124 435 8000 ( Mobile: +91 783 847 5602 > > ( CVS: 7 357 6094 ( CVS Access: +33 1 4445 1037 > > > > *From:* SERGIO GARCIA GOMEZ [mailto:sergg at tid.es] > *Sent:* Wednesday, April 09, 2014 11:59 > *To:* GUPTA Pallav SCE/IBNF; RAMPARANY Fano IMT/OLPS; JOSE IGNACIO > CARRETERO GUARDE > *Cc:* SRIVASTAVA Utkarsh SCE/IBNF; NAGELLEN Thierry IMT/OLPS; HENAR MUÑOZ > FRUTOS; MIGUEL CARRILLO PACHECO > *Subject:* RE: About how to create recipes > > > > Hi all, > > Sorry for the mistake. In order work in the recipes you have to use a > different testbed, the specific one for GE owners. I cc my colleague Jose > Ignacio, how can give access to that testbed to the following addresses: > > > > pallav.gupta at orange.com > > utkarsh.srivastava at orange.com > > > > Best Regards, > > > > Sergio. > > > > *From:* pallav.gupta at orange.com [mailto:pallav.gupta at orange.com<pallav.gupta at orange.com>] > > *Sent:* Wednesday, April 09, 2014 06:19 > *To:* RAMPARANY Fano IMT/OLPS > *Cc:* SRIVASTAVA Utkarsh SCE/IBNF; NAGELLEN Thierry IMT/OLPS; SERGIO > GARCIA GOMEZ; HENAR MUÑOZ FRUTOS; MIGUEL CARRILLO PACHECO > *Subject:* RE: About how to create recipes > > > > Hello Fano, > > > > Good Morning! > > > > We created following two testbed accounts on FIWARE cloud platform: > > a) pallav.gupta at orange.com > > b) utkarsh.srivastava at orange.com > > > > We have started setting of the development environment by which we can > start developing the cookbook for *“FLOD enabler”*. > > > > The development of cookbook will be done using *“**chef-solo**” *framework. > We identified following requirements for preparing development > environment: > > > > a) chef-solo image named “pass-chef-solo-templ” > > b) flod-3.0.0 image > > > > These two images I could not found on cloud platform after logging in my > testbed account. > > > > Kindly provide the images on cloud platform so that we can create Dev. VM > and start working on developing cookbook. > > > > Regards, > > Pallav Gupta > > > > *Pallav Gupta* > > International Centers - Orange Labs P&S - India > > Tower B, 8th Floor, DLF Infinity Towers, DLF Cyber City Phase - II > Gurgaon - 122002, Haryana, INDIA > > pallav.gupta at orange.com > > ( Tel: +91 124 435 8000 ( Mobile: +91 783 847 5602 > > ( CVS: 7 357 6094 ( CVS Access: +33 1 4445 1037 > > > > *From:* RAMPARANY Fano IMT/OLPS > *Sent:* Tuesday, April 08, 2014 07:29 > *To:* GUPTA Pallav SCE/IBNF; SRIVASTAVA Utkarsh SCE/IBNF > *Cc:* NAGELLEN Thierry IMT/OLPS; SERGIO GARCIA GOMEZ; HENAR MUÑOZ FRUTOS; > MIGUEL CARRILLO PACHECO > *Subject:* RE: About how to create recipes > > > > Hi Pallav and Utkarsh, > > > > I invite you to sign up for testbed accounts. The testbed is what I called > FIWARE cloud platform (that you access using the OpenStack framework) > during our previous discussion. As I told you, you don’t really need > FusionForge accounts at this point, because these are principally dedicated > to GE (generic enabler) developers and are not needed for developing > recipes. > > > > Regards, > > Fano > > > > *De :* SERGIO GARCIA GOMEZ [mailto:sergg at tid.es <sergg at tid.es>] > *Envoyé :* mardi 8 avril 2014 12:38 > *À :* RAMPARANY Fano IMT/OLPS; MIGUEL CARRILLO PACHECO > *Cc :* HENAR MUÑOZ FRUTOS; NAGELLEN Thierry IMT/OLPS; GUPTA Pallav > SCE/IBNF; SRIVASTAVA Utkarsh SCE/IBNF > *Objet :* RE: About how to create recipes > > > > Dear Fano, > > Please, have a look at these two pages: > > > > > https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/How_to_create_a_FusionForge_account > > > > > https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/How_to_join_a_FI-WARE_project_in_FusionForge > > > > Please refer to FLOD / WP6 when you register and request access to the > General and Data projects. > > > > As for the recipes creation, they’re likely to need testbed accounts. They > can simply sign up at https://account.testbed.fi-ware.org/ > > > > Best Regards, > > > > Sergio. > > > > *From:* fano.ramparany at orange.com [mailto:fano.ramparany at orange.com<fano.ramparany at orange.com>] > > *Sent:* Tuesday, April 08, 2014 12:26 > *To:* SERGIO GARCIA GOMEZ; MIGUEL CARRILLO PACHECO > *Cc:* HENAR MUÑOZ FRUTOS; NAGELLEN Thierry IMT/OLPS; GUPTA Pallav > SCE/IBNF; SRIVASTAVA Utkarsh SCE/IBNF > *Subject:* RE: About how to create recipes > > > > Hi Sergio and Miguel, > > > > We would like to request the creation of two accounts: > > pallav.gupta > > utkarsh.srivastava > > for Orange colleagues who will help us creating the recipes for our FLOD > GE. > > > > Thank you in advance for your help, > > > Fano > > > > *De :* SERGIO GARCIA GOMEZ [mailto:sergg at tid.es <sergg at tid.es>] > *Envoyé :* mercredi 2 avril 2014 11:11 > *À :* Moltchanov Boris; RAMPARANY Fano IMT/OLPS; Rolando Sergio (Guest) > *Cc :* HENAR MUÑOZ FRUTOS > *Objet :* RE: About how to create recipes > > > > Dear Boris, > > > > Let me remind you that not having the recipes for the blueprints will lead > to not being in FI-Lab, and it will somehow affect presence in the > catalogue. > > > > Fano, I have to talk with Henar how to solve this issue. So far I don’t > see a way to deploy your recipes on a CAP VM Image, or to combine both > things in a blueprint. I’ll keep you posted. > > > > Best Regards, > > > > Sergio. > > > > > > *Subject* > > *[Fiware-wpa] VERY IMPORTANT: Criteria for deployment of GEis > on FI-Lab* > > *From* > > fiware-wpa-bounces at lists.fi-ware.eu > > *To* > > fiware at lists.fi-ware.eu > > *Cc* > > fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > > *Sent* > > Monday, November 25, 2013 09:46 > > *Attachments* > > <<ATT00001.txt>> > > > > Dear partners and GEi owners in particular, > > > > This mail is to elaborate on the criteria that is being followed to > decide when a given GEi can be deployed on FI-Lab and made available to > third parties. > > > > FI-WARE GEis can be available to UC projects on the FI-PPP Testbed ( > http://testbed.fi-ware.eu) but not yet on FI-Lab due to the fact they > haven't yet fulfilled the listed criteria: > > · Documentation linked to the GEi has to pass the internal review > (Miguel carrillo in charge). Note that the fact we have submitted this > documents as deliverable to the EC, or they have even been accepted by > reviewers, doesn't mean that you have passed this internal review. Our > review is considering whether the documentation reaches a minimum level as > to be shared with third parties. We are referring here to the following > documentation: > > o Installation and Administration guides > > o User and Programmers guides > > · Completeness of information in the FI-WARE Catalogue. Here, > special attention will be made to info about licenses and External > Availability. Overall, we will also check whether description of the GEi > is complete and well-written. We will also check that all necessary links > to documentation, architecture and API specifications and, when apropriate, > source code are published. > > · Availability of tools for automated creation of instances. It > should be feasible to deploy the GEi using virtual pre-configured images, > recipes and blueprints. All this information should be documented in > the "Creating instances" tab linked to the GEi in the FI-WARE Catalogue. > Besides those that don't need to be deployed on FI-Lab because of their > nature (e.g., GEis linked to IoT gateways, the Cloud proxy GEi, the CDI GEi > or the advanced middleware GEi, to mention some examples), the following > GEis are excluded and don't need to follow this rule (the rule has to be > fulfilled for all the rest): > > o WireCloud GEi in the Apps chapter > > o Business Framework related GEis in the Apps chapter > > o GEis in the Cloud Hosting chapter > > o GEis in the Security chapter > > o GEis in the I2ND chapter > > · Training material. There should be enough and complete > training material for the GEi uploaded in the "Help&Info" webpage of FI-Lab > or the FI-WARE eLearning platform. > > > > The need to fulfill these requirements are no new, but we wanted to > stress that we have decided to prevent that GEis not fulfilling the above > criteria are made available to third parties on FI-Lab. > > > > Any GEi that fails to cover this criteria will not deployed on FI-Lab. > Those GEis already deployed on FI-Lab should work hard to ensure that the > above criteria is fulfilled before end of the year. > > > > Whenever you believe that you have fulfilled all these criteria, please > inform Stefano de Panfilis (stefano.depanfilis at eng.it) and Miguel > Carrillo (mcp at tid.es) so that they can confirm. Please keep me on > copy. Once fulfillment of the requirements is confirmed, Stefano and > Miguel will coordinate the necessary steps to make your GEi available on > FI-Lab. > > > > Don't hesitate to formulate any question you may have. > > > > Cheers, > > > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website: www.tid.es > email: jhierro at tid.es > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Coordinator > and Chief Architect > > FI-PPP Architecture Board chairman > > You can follow FI-WARE at: > website: http://www.fi-ware.eu > facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter: http://twitter.com/FIware > linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 > > > > 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 > > > > > > *From:* Moltchanov Boris [mailto:boris.moltchanov at telecomitalia.it<boris.moltchanov at telecomitalia.it>] > > *Sent:* Wednesday, March 26, 2014 16:54 > *To:* fano.ramparany at orange.com; Rolando Sergio (Guest) > *Cc:* HENAR MUÑOZ FRUTOS; SERGIO GARCIA GOMEZ > *Subject:* RE: About how to create recipes > > > > Hi Fano, > > > > unfortunately we’re not going to create a blueprint for the CAP. We’re > accomplishing the planned developments and will release it as NGSI > OpenSource accordingly to the plans. > > > > Thanks. > > > > Best Regards, > > Boris > > > > *From:* fano.ramparany at orange.com [mailto:fano.ramparany at orange.com<fano.ramparany at orange.com>] > > *Sent:* Wednesday, March 26, 2014 4:44 PM > *To:* Moltchanov Boris; Rolando Sergio (Guest) > *Cc:* HENAR MUÑOZ FRUTOS; SERGIO GARCIA GOMEZ > *Subject:* TR: About how to create recipes > > > > Hi Boris and Sergio, > > > > As you might know, there’s a work stream in WP6 dedicated to the packaging > of CAP and FLOD (the semantic extension GE implementation) in one bundle to > be automatically created and deployed using a CHEF blueprint. The roadmap > of this work stream is that each GE providing partner should provide the > recipes for his GE, in your case recipes for CAP. Once this has been done > (i.e. recipes have been created for CAP and FLOD), TiD will help us create > the blueprint. This is a matter of minutes according to Sergio. > > > > Will you engage in developing recipes for CAP or are you already commited > into this? > > > > Thank you for your cooperation, > > > Fano > > > > > > > > *De :* HENAR MUÑOZ FRUTOS [mailto:henar at tid.es <henar at tid.es>] > *Envoyé :* lundi 10 mars 2014 08:25 > *À :* RAMPARANY Fano IMT/OLPS > *Cc :* MIGUEL CARRILLO PACHECO; SERGIO GARCIA GOMEZ; NAGELLEN Thierry > IMT/OLPS; JOSE IGNACIO CARRETERO GUARDE; Moltchanov Boris > *Objet :* RE: About how to create recipes > > > > Hi Fano > > You can have a look at the recipes other partners have done for their GEs. > There is a cookbook repository in > https://forge.fi-ware.eu/scmrepos/svn/testbed/trunk/cookbooks. The > GESoftware folder can help you. > > Regards, > > Henar > > > > *De:* fano.ramparany at orange.com [mailto:fano.ramparany at orange.com<fano.ramparany at orange.com>] > > *Enviado el:* viernes, 07 de marzo de 2014 17:08 > *Para:* HENAR MUÑOZ FRUTOS > *CC:* MIGUEL CARRILLO PACHECO; SERGIO GARCIA GOMEZ; NAGELLEN Thierry > IMT/OLPS; JOSE IGNACIO CARRETERO GUARDE; Moltchanov Boris > *Asunto:* RE: About how to create recipes > > > > Hi Henar, > > > > Could you help us getting started on this thread. Currently the image of > my GE starts its services when being instantiated. Have you got a CHEF > recipe sample which we could start from? > > > > Thank you in advance, > > Fano > > > > > > *De :* RAMPARANY Fano IMT/OLPS > *Envoyé :* lundi 24 février 2014 15:49 > *À :* 'HENAR MUÑOZ FRUTOS' > *Cc :* 'MIGUEL CARRILLO PACHECO'; 'SERGIO GARCIA GOMEZ'; NAGELLEN Thierry > IMT/OLPS; 'JOSE IGNACIO CARRETERO GUARDE'; 'Moltchanov Boris' > *Objet :* RE: About how to create recipes > > > > Hi Henar, > > > > Right now, I’m a bit stuck. I see 3 options for proceeding further: > > 1- I start from a simple recipe and adapt it for my case > > 2- I learn Ruby and Chef > > 3- I find somebody in Orange who can do to job > > > > I’m afraid options 2 and 3 will take too much time. Option 1 would be the > most efficient solution. It should be easy to find such existing simple > recipe, because our GE has been implemented as a standalone server image > (we don’t need Tomcat nor JBoss nor any base platform) with eventually some > configuration files to be stored in specific directories. I suspect such > simple recipe exists somewhere in the CVS, but it will help a lot if you > can point me to the good one. > > > > Thank you in advance for your help, > > > > Fano > > > > *De :* RAMPARANY Fano IMT/OLPS > *Envoyé :* mardi 18 février 2014 17:44 > *À :* 'HENAR MUÑOZ FRUTOS' > *Cc :* MIGUEL CARRILLO PACHECO; SERGIO GARCIA GOMEZ; NAGELLEN Thierry > IMT/OLPS; JOSE IGNACIO CARRETERO GUARDE; Moltchanov Boris > *Objet :* RE: About how to create recipes > > > > Hi Henar, > > > > If you are referring to the video 2 (entitled: “Chef and FIWARE”) and 3 > (entitled: “Creating Chef recipes”), they introduce new terminology such as > “package”, “template”, “service” which I don’t know what they correspond to > in my case. The tutorial and video cover mainly the testing of the recipes, > but what I miss is support to write the required recipes (stop.rb, > install.rb,…) for my GE. Is this documented somewhere? Eventually outside > FIWARE. At the end of the video 2 you say that writing a recipe is not > easy, but you don’t provide any pointers to start from, if I’m not mistaken. > > > > Thanks in advance for your help, > > > Fano > > > > *De :* HENAR MUÑOZ FRUTOS [mailto:henar at tid.es] > *Envoyé :* mardi 18 février 2014 16:58 > *À :* RAMPARANY Fano IMT/OLPS > *Cc :* MIGUEL CARRILLO PACHECO; SERGIO GARCIA GOMEZ; NAGELLEN Thierry > IMT/OLPS; JOSE IGNACIO CARRETERO GUARDE; Moltchanov Boris > *Objet :* RE: About how to create recipes > > > > Hi > > > > There is a video in edu.fi-ware.eu about how to create recipes. You can > have a look. > > Regards, > > Henar > > > > *De:* fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] > *Enviado el:* martes, 18 de febrero de 2014 16:36 > *Para:* HENAR MUÑOZ FRUTOS > *CC:* MIGUEL CARRILLO PACHECO; SERGIO GARCIA GOMEZ; NAGELLEN Thierry > IMT/OLPS; JOSE IGNACIO CARRETERO GUARDE; Moltchanov Boris > *Asunto:* RE: About how to create recipes > > > > Hi Henar, > > > > Thank you for your help. I had to remove the chef-solo server and relaunch > it. I can now ssh on the server and follow the “How to create recipes for > the GEs” tutorial up to the “Node configuration” section. From there on, I > definitely need some help to create a recipe for instanciating and > deploying the FLOD GE (We’ll later need support to create a blueprint > template for instanciating, deploying and binding CAP and FLOD, if I > understand well, but let’s focus right now on the FLOD recipe). > > Although, this GE is very simple, it is available as an image and has > simply to be launched in a ubuntu VM, it is not clear to me: > > - What I should put in the json file, if this json file is > necessary at all and what it purpose is > > - Where should I create and save the recipe and what I should > put in this file. > > - If I need a template file. > > - How I can test the recipe > > > > May be a recipe sample corresponding to the FLOD case could help > > > > Best regards, > > > Fano > > > > *De :* HENAR MUÑOZ FRUTOS [mailto:henar at tid.es] > *Envoyé :* lundi 17 février 2014 16:26 > *À :* RAMPARANY Fano IMT/OLPS > *Cc :* MIGUEL CARRILLO PACHECO; SERGIO GARCIA GOMEZ; NAGELLEN Thierry > IMT/OLPS; JOSE IGNACIO CARRETERO GUARDE > *Objet :* RE: About how to create recipes > > > > Hi Fano > > > > It seems that previous problem was not just affecting images server, but > also nova. It should work now. If you experience more problems, you can > report to us. > > Regards, > > Henar > > > > *De:* fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] > *Enviado el:* lunes, 17 de febrero de 2014 14:47 > *Para:* RAMPARANY Fano IMT/OLPS; HENAR MUÑOZ FRUTOS > *CC:* MIGUEL CARRILLO PACHECO; SERGIO GARCIA GOMEZ; NAGELLEN Thierry > IMT/OLPS > *Asunto:* RE: About how to create recipes > > > > Hi Henar, > > > > I assume that once I’ve launched an instance of a chef-solo server, I have > to allocate it a floating IP number (the tutorial isn’t very explicit about > this). So I remember that to achieve this I have to go the “Security” page > and find there a tab where I can create a Floating IP that I can allocate > to an existing instance. > > Unfortunately this page doesn’t show any instance (see screendump > novaImgPb2.JPG attached) > > > > I also noticed that the chef-solo-ol1 instance I created is still at a “NO > STATE” status (see screendump novaImgPb3.JPG attached) 30mn after creation. > Let me know if this is a pb or if I only need to be patient. > > > > Thanks in advance for your help, > > > Fano > > > > *De :* RAMPARANY Fano IMT/OLPS > *Envoyé :* lundi 17 février 2014 13:43 > *À :* 'HENAR MUÑOZ FRUTOS' > *Cc :* MIGUEL CARRILLO PACHECO; SERGIO GARCIA GOMEZ; NAGELLEN Thierry > IMT/OLPS > *Objet :* RE: About how to create recipes > > > > I now get many images, including the paas-chef-solo-templ one. Could you > please tell us what was wrong with the previous state? > > Thanks > > > Fano > > > > *De :* HENAR MUÑOZ FRUTOS [mailto:henar at tid.es] > *Envoyé :* lundi 17 février 2014 13:11 > *À :* RAMPARANY Fano IMT/OLPS > *Cc :* MIGUEL CARRILLO PACHECO; SERGIO GARCIA GOMEZ; NAGELLEN Thierry > IMT/OLPS > *Objet :* RE: About how to create recipes > > > > Hi > > > > Can you try it again? > > Thanks, > > Henar > > > > *De:* fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] > *Enviado el:* lunes, 17 de febrero de 2014 12:18 > *Para:* HENAR MUÑOZ FRUTOS > *CC:* MIGUEL CARRILLO PACHECO; SERGIO GARCIA GOMEZ; NAGELLEN Thierry > IMT/OLPS > *Asunto:* RE: About how to create recipes > > > > Hi Henar, > > > > As agreed at last week WP6 phonecall meeting, we will create a recipe for > the deployement of the FLOD the PubSub semantic extension GE. My intent was > to create a recipe involving FLOD first and then synchronize with Telecom > Italia to extend the recipe to integrate FLOD and CAP and bind them. > > I’m currently following the “How to create recipes for the GEs” wiki > tutorial page and once I’m logged in the nova platform, and on the “Images” > page, I don’t see any image available, while I was expecting more than 20 > of them (as I’ve seen in the past), and at least the “paas-chef-solo-templ” > image mentioned in the tutorial (See the screendump attached) > > Do you know why? > > > > Thanks in advance, > > Fano > > > > > > > > *De :* HENAR MUÑOZ FRUTOS [mailto:henar at tid.es] > *Envoyé :* jeudi 9 janvier 2014 11:28 > *À :* RAMPARANY Fano IMT/OLPS; SERGIO GARCIA GOMEZ > *Cc :* MIGUEL CARRILLO PACHECO > *Objet :* About how to create recipes > > > > Hi > > You can have a look at > http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_create_recipes_for_the_GEsand check the video > http://edu.fi-ware.eu/course/view.php?id=24. > > Regards, > > Henar > > > > *De:* fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] > *Enviado el:* miércoles, 08 de enero de 2014 15:43 > *Para:* SERGIO GARCIA GOMEZ > *CC:* HENAR MUÑOZ FRUTOS; MIGUEL CARRILLO PACHECO > *Asunto:* RE: Urgent: Delivery of Release 3 > > > > Hi Sergio, > > > > I’ve got some problem accessing the links in the google doc. > > I’ve attached: > > - The screendump of the current view of the dashboard > > - The screendump of the error message when attempting to access > the instructions link > > - The screendump of the error message when attempting to access > the installation and user guide link > > My guess is that most of the links are placeholders where I’m supposed to > fetch the related content for my GE. Thus I expect to reach an empty page > where I’ve simply to copy and paste my content, not an error message? > > This should be indeed explained in the instructions link but as shown in > the 2nd screendump, I can’t access this document. > > > > Any help appreciated, > > > Fano > > > > PS: Henar, could you provide me a good pointer (quick start document) to > “how to create recipes/cookbook”. Thanks in advance > > > > > > *De :* SERGIO GARCIA GOMEZ [mailto:sergg at tid.es] > *Envoyé :* vendredi 20 décembre 2013 11:15 > *À :* RAMPARANY Fano IMT/OLPS > *Cc :* fiware-data at lists.fi-ware.eu > *Objet :* RE: Urgent: Delivery of Release 3 > > > > Hi Fano, > > Great, thanks! If it’s already available and you have followed the > instructions, it should be just a matter of copying the content to the > proper placeholders. > > Please, find the links for your GE in the sheet and let me know. > > > > > https://docs.google.com/spreadsheet/ccc?key=0AgKkYKvfz1EsdDhFZFh5dWw5cWQ0a3JPQlpRS1VlNWc#gid=17 > > > > Since it’s the first time you submit, please make sure that you have > followed the instructions to avoid rejections and delays. The links are > also in the spread sheet. If you have any doubt, let me know. > > > > Best Regards, > > > > Sergio > > > > > > *From:* fano.ramparany at orange.com [mailto:fano.ramparany at orange.com] > *Sent:* Friday, December 20, 2013 10:08 AM > *To:* SERGIO GARCIA GOMEZ > *Cc:* fiware-data at lists.fi-ware.eu > *Subject:* RE: Urgent: Delivery of Release 3 > > > > Hi Sergio, > > > > The PubSub semantic extension documentation is here : > > > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/SPARQL_for_ContextML_RESTful_API_Specification_%28PRELIMINARY%29#Other_Documents > > The user doc, instance creation and testing have http links in the “other > link” section. > > > > Best regards, > > > Fano > > > > *De :* fiware-data-bounces at lists.fi-ware.eu [ > mailto:fiware-data-bounces at lists.fi-ware.eu<fiware-data-bounces at lists.fi-ware.eu>] > *De la part de* SERGIO GARCIA GOMEZ > *Envoyé :* mardi 17 décembre 2013 11:29 > *À :* fiware-data at lists.fi-ware.eu > *Objet :* [Fiware-data] Urgent: Delivery of Release 3 > > > > Hi all, > > I have updated the cockpit with releae 3 delivery and I have realized that > there are several missing contributions: > > * Documents from *FT* (Semantic pubsub), *ATOS* (UDA and SAS) and > *Siemens* (MdPP) are missing > > * Software releases from *TID* (Cosmos), *ATOS* (UDA and SAS), *Siemens*(MdPP), > *Thales* (LOCS), and *URJC* (Kurento) > > > > For the mentioned people, first of all, *please answer this email ASAP*confirming that you are aware and sharing with me the status: > > · Is it available somewhere else and I couldn’t find it or I > overlooked it? If so, please, release it in the proper place or let me > know. > > · Are you working on it yet? When are you delivering? Take into > account that I might have to release without your GE. > > · Aren’t you delivering in R3? If so, let me know. > > > > Best Regards, > > > > Sergio > > > > > > [image: cid:image001.png at 01CEFC94.3834B220] > > > > > > *From:* SERGIO GARCIA GOMEZ > *Sent:* Friday, November 08, 2013 2:14 PM > *To:* fiware-data at lists.fi-ware.eu > *Subject:* FW: [Fiware] VERY IMPORTANT: Organization of FI-WARE Release 3 > > > > Dear all, > > > > As you have seen, we have deliver R3. According to the DoW, this is indeed > delivery of R3.2. All of you have already features in the roadmap for R3.3. > There will an update of documents and sw, and corresponding delivery in the > testbed and the FI-LAB after that. Of course, this is all subject to the > decision about the project extension. As soon as we have news, we’ll let > you know. > > > > I have prepared the wikis so that we can kick off this activity. You can > find in the chapter integrated dashboard a new sheet for release 3: > > > https://docs.google.com/spreadsheet/ccc?key=0AgKkYKvfz1EsdDhFZFh5dWw5cWQ0a3JPQlpRS1VlNWc#gid=17 > > > > I have linked in that page the cockpits and instructions for the > deliverables of every GEi. Specially for the new GEs, please read them > carefully and follow the guidelines, structures of the document, etc. If > you have any doubt, just ask me. Except for the specific comments below: > > · I have copied the public wiki pages to the private one. > > · I have protected the public wiki pages to avoid undesired > editions, merges, etc. From now on, just edit in the private wiki. > > > > Some special comments: > > · PubSub Semantic Extension. @Fano, please copy your > documentation in the pages I have created, and double check content and > structure. > > · Semantic Annotation. @Boris, I haven’t created structure for > this one. As in Release 2, I assume that there’s no deliver in R3. > > · Kurento. @Luis, I have copied the Unit Testing Plans from your > draft in the data wiki. > > · Unstructure DA. @Mauricio, this is the first time this GE is > delivered. Please follow the guidelines. > > · Semantic App Support. @Mauricio, will you deliver this one? > > > > The deadline is December, 15th, and I have to make an internal review and > ask for changes before that. So please, finish your edition one week > before, December, 8th. > > So far, I’m referring only to Unit Testing Plan, User & Prog. Manual and > Install & Admin guides. I guess we will start with Open Specs and > Architecture pretty soon. > > > > Best Regards, > > > > Sergio > > > > *From:* fiware-bounces at lists.fi-ware.eu [ > mailto:fiware-bounces at lists.fi-ware.eu <fiware-bounces at lists.fi-ware.eu>] *On > Behalf Of *Juanjo Hierro > *Sent:* Saturday, November 02, 2013 12:26 PM > *To:* fiware at lists.fi-ware.eu > *Cc:* MIGUEL CARRILLO PACHECO > *Subject:* [Fiware] VERY IMPORTANT: Organization of FI-WARE Release 3 > > > > Dear all, particularly FI-WARE GEi owners, > > > Probably you have already been informed by your WPLs/WPAs, but we are > sending this mail to make sure that all of you have the information about > how edition and publication of deliverables linked to release 3 will be > organized. > > We have the links to edit the deliverables ready on FI-WARE private wiki > now, with the usual rules. > > - > https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FiwareDeliverablesR3 > > Be aware that: > > - We have made an effort to keep the same old rules from R2 for the > sake of simplicity > - This message refers to the Unit Testing Plan, User & Prog. Manual > and Install & Admin guides > - This message refers to WP3, WP4, WP5, WP6, WP7, WP8 and WP13 > - As stated in the wiki pages with the placeholders, the WPL have to > fill in the list of GEs/GEis per deliverable. Once they add the links, you > can start your work. Coordinate internally in each WP. > - Editing the deliverables on the public wiki is not allowed - we will > strictly enforce it this time. The editing of the manuals should happen on > the private wiki > - Yes, we know that there are deliverables from R2 not yet accepted. > They will undergo reviews later but we cannot delay R3 anymore. > - There is a single compulsory delivery at the end of R3. However, if > part of the GE owners wishes to deliver at the end of a minor release, they > can. This would imply delivering internally on the *private *wiki > first, making sure that it is a full and consistently synchronised delivery > (software + manual fully updated for the minor release). Then they would > undergo reviews and get the approval for final publication. > > As for the timing, there is an ongoing discussion whether we will extend > the project as you know. Until this gets solved, we will have to stick to > dates set in the current DoW. This means that the final delivery is M33 > (end of Jan/2014) which means that we should start the reviews before the > end of the year. The deadline is 15/December, each WPL will organize the > internal schedule within each WP. > > Don't hesitate to contact your WPL and Miguel Carrillo for further > clarifications. > > Best regards, > > Miguel and Juanjo > > > > > > > ------------------------------ > > > 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 > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > ------------------------------ > > > 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 > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > ------------------------------ > > > 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 > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > ------------------------------ > > > 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 > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > ------------------------------ > > > 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 > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > ------------------------------ > > > 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 > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > ------------------------------ > > > 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 > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > Questo messaggio e i suoi allegati sono indirizzati esclusivamente > alle persone indicate. La diffusione, copia o qualsiasi altra azione > derivante dalla conoscenza di queste informazioni sono rigorosamente > vietate. Qualora abbiate ricevuto questo documento per errore siete > cortesemente pregati di darne immediata comunicazione al mittente e di > provvedere alla sua distruzione, Grazie. > > *This e-mail and any attachments is confidential and may contain > privileged information intended for the addressee(s) only. Dissemination, > copying, printing or use by anybody else is unauthorised. If you are not > the intended recipient, please delete this message and any attachments and > advise the sender by return e-mail, Thanks.* > > *[image: rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail > se non è necessario.* > > > > > ------------------------------ > > > 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 > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > ------------------------------ > > > 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 > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > ------------------------------ > > > 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 > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > ------------------------------ > > > 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 > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > ------------------------------ > > 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 > > _______________________________________________ > Fiware-portals mailing list > Fiware-portals at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-portals > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-portals/attachments/20140415/16922498/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 32805 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-portals/attachments/20140415/16922498/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 1254 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-portals/attachments/20140415/16922498/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 41675 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-portals/attachments/20140415/16922498/attachment-0001.jpg>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy