Hi Silvio,
I am currently in Germany with limited access to my email. I can provide the description of task corresponding to TID.
Regarding IMDEA. I might forward but I cannot follow the actions. I will talk with Miguel about it.
Best regards and Happy New Year.
Fernando.-
========================================================
REPORT M14-M25
(OCTUBRE 2015 - SEPTIEMBRE 2016)
Task 2.1.1 Platform Deployment Tool (FI-Deploy)
Contribution and results:
* None
Deviation and proposed corrective action:
* No planned activities were developed in this task.
Task 2.1.2 Platform Deployment Tool (FI-Dashboard)
Contribution and results:
* None
Deviation and proposed corrective action:
* No planned activities were developed in this task.
Task 2.1.3 Platform Analytics Tools (FI-Health)
* FI-Health / Sanity Checks tool
* Generate the proper content of the deliverable D.12.1.1
* Generate the proper content of the deliverable D.21.1.1
* Updated README files to show ToC and “installation verification” section
* Script to have the mailing lists used by FIHealth Dashboard automatically created and configured.
* Improve log messages adding transactionId to the operations with the PhoneHome server.
* Include additional logs and messages in HTML report of Sanity Checks
* Include errors when deleting resources in HTML report of Sanity Checks
* Include verification of the “admin” role of the user running the Sanity Checks
* Include obfuscation of any sensible information (e.g. auth token) shown in HTML report of Sanity Checks.
* Upgrade Node.js engine to a LTS version (4.5)
* New feature to dynamically configure sanity checks for a region, reading details from the configuration file
* New feature to sort regions by name on Dashboard list.
* New feature to filter out images that are configured in the properties file on the Dashboard list
* New feature to publish Sanity Status directly to Monasca API
* Delete regions no longer federated and active
* Create, publish and deploy new releases
* Support for Sanity Checks
* Bug fixing: 21 resolved (OPS-642, OPS-643, OPS-798, OPS-807, OPS-912, OPS-923, OPS-965, OPS-1018, OPS-1049, OPS-1088, OPS-1116, OPS-1125, OPS-1141, OPS-1147, OPS-1194, OPS-1195, OPS-1202, OPS-1211, OPS-1324, OPS-1329, OPS-1332)
* Help-Desk tickets: 12
* FIWARE Monitoring tool
* Publish a Press Note related to the presentation of the OpenStack Summit in Atlanta related to the new Monitoring Architecture used in FIWARE.
* Install New Monitoring architecture (Monasca, Kafka, etc.) in a master node
* Support to Infrastructure owners in configuring the New Monitoring architecture
* Testing and contribution to the OpenStack community to improve the overall quality of the component.
* Script to check the installation and configuration of the components of New Monitoring architecture.
* Add "region" dimension when creating metrics for multitenancy in New Monitoring architecture
* Include support to NGSI API v2 in NGSI Adapter
* Implement a new loadable parser for NGSI Adapter to transform incoming Monasca data (through UDP requests) into NGSI attributes
* New feature to monitor global instances of GEri’s from Catalog, reusing components NGSI Adapter and NGSI Event Broker.
* Deploy an Orion Context Broker instance to receive the data from the monitoring of GEri global instances and send them, via subscription, to the Monitoring portal developed by UPM team.
* Define, install and configure the integration between Local monitoring system based on OpenStack Ceilomenter and Federated monitoring system based on OpenStack Monasca.
* Update documentation of the component
* Support for FIWARE Monitoring tool
* Bug fixing: 2
* Help Desk tickets: 10
Task 2.1.4 Support tools
* Aiakos
* Architecture definition.
* Implementation of core service of the component to upload public keys associated to the different FIWARE Lab nodes.
* Documentation about management of keys.
* Implement validation for the name of regions.
* Implement authentication against Keystone with admin user.
* Document the API specification in Apiary.
* Ask all node admins for ssh-keys (ssh-key and gpg-key) through Jira tickets.
* Create the docker files corresponding to the component.
* Upload and configure the component to HubDocker.
* Implement error management (HTTP 404, 405, 415, json format).
* Build/Deploy production environment in aiakos.fiware.org.
* Creates new volume and configure backup folder to provide persistent storage for the keys.
* Generate the proper content of the deliverable D.12.1.1.
* Create the documentation of the component
* Define/Implement acceptance tests.
* Improve coverage of the unit tests of the component.
* Support for Aiakos tool
* Bugs fixing: 2 (OPS-903, OPS-904)
* Help Desk tickets: 1
* GlanceSync
* Create some scripts in order to automate the creation of the images of the different GE.
* Travis (Continuous integration) and Coveralls (coverage report) configuration.
* New API GlanceSync specification.
* Implement unifies process tool.
* Improve getNID script requirements.
* Develop the functionality to connect GlanceSync with Keystone using APIv3.
* Parallelization as much as possible in order to reduce the time of execution.
* Implement and connect GlanceSync API code with GlanceSync core activities.
* Implement acceptance and unit tests for API.
* Add authentication to GlanceSyn API.
* Improve error reports to infrastructure owner.
* Implement an automatic process to create new GE image from base image.
* Add logger to API server.
* Reduce the information published in the 'server' header in order to reduce the detailed information for security reasons.
* Add API to get information about the synchronization tasks depending on the status of the task that it is in the DB.
* Provide the way (setup python) to installing GlanceSync as a 'system' command.
* Add docker files.
* Add admin token expiration validation.
* Improve API response message errors.
* Provide mechanism to give authorization access to a token received in the GlanceSync API.
* Build/Deploy API server and core in a global instance.
* Script for base image Debian 8.
* Create and install release 5.3 and 5.4.1
* Update and improve documentation of the component.
* Support for Glancesync component
* Bugs fixing: 18 (OPS-596, OPS-542, OPS-454, OPS-409, OPS-408, OPS-631, OPS-649, OPS-628, OPS-694, OPS-630, OPS-697, OPS-854, OPS-916, OPS-907, OPS-908, OPS-979, OPS-978, OPS-1098)
* Help-Desk tickets: 4
* Skuld
* Impersonate process associated to expired users.
* Generate python package
* Create the docker files corresponding to the component.
* Upload and configure the component to HubDocker.
* Obtain report with community expired users and their regions
* Delete the resources associated to the community users expired
* Create acceptance tests for user deletion with a dummy testbed
* Improve unit tests coverage
* Improve coverage of acceptance tests.
* Improve documentation of the component
* Complete refactorization of the component to improve code quality
* Generate the proper content of the deliverable D.21.1.1
* Support for Skuld tool:
* Bug fixing: 3 (OPS-806, OPS-1143, OPS-1259).
* Help-Desk: 3
* FIWARE Testbed Deploy
* Generation of a Cloud testbed for testing
* Create docker for deploying the testbeds
* Configure hub docker to contain the image of the component.
* Generate the acceptance tests associated to the component
* Generate the corresponding functionality to check that the installation of the component was resolved without any problem
* Create the documentation of the component
* Generate the proper content of the deliverable D.21.1.1
* Not needed support
From: <fiware-ops-dev-bounces at lists.fiware.org> on behalf of Silvio Cretti <silvio.cretti at create-net.org>
Date: Wednesday, 21 December 2016 at 22:02
To: fiware-ops-dev <fiware-ops-dev at lists.fiware.org>
Subject: [Fiware-ops-dev] Fwd: [Fiware] Start of the 2nd year reporting. We need work from ALL
Dear all,
as you understand from the Miguel's email, it's time to report on our activity in OPS.
Of course I will take care of the general part of the WP and of the CNET part. Each partner should take care of its part.
Please do not wait the last days: even though deadline is January 17th for providing the report to Miguel, I need it some days before in order to armonize all the contributions and in case come back to you for a final validation. So please do it asap and in any case not later than January 11th.
Last thing: @Fernando, I am not sure that IMDEA is in this mailing list. Can you please fwd this email to them?
Thanks in advance and best regards,
silvio
---------- Forwarded message ----------
From: MIGUEL CARRILLO PACHECO <miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>>
Date: Wed, Dec 21, 2016 at 6:33 PM
Subject: [Fiware] Start of the 2nd year reporting. We need work from ALL
To: "fiware at lists.fiware.org<mailto:fiware at lists.fiware.org>" <fiware at lists.fiware.org<mailto:fiware at lists.fiware.org>>
Cc: JAVIER DE PEDRO SANCHEZ <javier.depedrosanchez at telefonica.com<mailto:javier.depedrosanchez at telefonica.com>>, JUAN JOSE HIERRO SUREDA <juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>>
Dear all,
As announced in the coordination call today, we have launched the 2nd year report. We have made available the links to edit it for all partners. They are here:
WP11
Global FIWARE Technical Coordination
https://docs.google.com/document/d/1eMgHbvaQBejfeXdxEBm1mwUoqIbIZByLe1pfOWZ-yig/
WP12
Cloud Hosting
https://docs.google.com/document/d/1j-HIjlqEpjPGn1TlEbxGRb8WzzKDQ_3zWOIqeBGhI5M/
WP13
Data/Media and Context Management
https://docs.google.com/document/d/1MbIgnZ--a8vPIYQVXYsUgPw8EmsfNFSdenfP9VKppGs/
WP14
IoT Services Enablement
https://docs.google.com/document/d/1dUrC_rAcy-RDZdDPdUz3XRrxNhA66TeAralQdzIPqPM/
WP15
Advanced Web-based User Interfaces
https://docs.google.com/document/d/1aQm0EeyGVH_oNSxKUfkN-AR007k8HfL7VyFjfHPtE9Q/
WP16
Apps/Service and Data Delivery
https://docs.google.com/document/d/1HZeUZFa1cPZ2eF-kjG_eNI5PtVPJzL2HHf-YHQDQZP0/
WP17
Security
https://docs.google.com/document/d/11DRpLGrJnyhrWECqka_o9uTWCmve16wkE3ycGwozzKw/
WP18
Advanced Middleware and Interfaces to Networks and Robotics
https://docs.google.com/document/d/1LDGy1ReFpLBcV9t0XfcyqM3XzjJlG5_VQz9hjydzlgY/
WP21
FIWARE Ops Tools
https://docs.google.com/document/d/1tz-Nb1xd_7eBOhsslXquFCUjE9c4TN0Gyq2FmqYeU9U/
WP22
FIWARE Lab Setup and Operation
https://docs.google.com/document/d/1QNFRaQWkm5J90J0xqjU6VKZuz_XmCOqPc2hUbC0on1k/
WP31
Sustainability Support Tools
https://docs.google.com/document/d/1Ahl4rDQYyJvMeBQxNZT2Gha8xgEbDZLvoIO4DPfGD_w/
WP32
Sustainability Model Definition and Activities
https://docs.google.com/document/d/1Oc7IKsf0oU6nGJhMdyubQVyfEvUA_gLIbcfd70maqXk/
WP33
Exploitation
https://docs.google.com/document/d/1SRsnaFzYfIzIEUTJUPSLfl6g0ER7GtMCOKS1Gf0gHcI/
WP41
Project Management
https://docs.google.com/document/d/1o9ojsHHuaYcvtxRhWpq3dGqgi-czSvP-f-KyPpqDjtE/
WP42
Communication, Collaboration and Dissemination
https://docs.google.com/document/d/1sCkzT6cpcaHEXbFqdbyqvAukBlkQBLGEHo3pczuV4Fc/
You are requested to report on your activity in the project in Year 2, from M14 (Oct/2015) till M28(Dec/2016). You cannot report activity before M14 or after M28.
These links and the information within are FIWARE confidential
Deadline: 17/January
Important guidelines:
* The WPLs are expected to check that the partners per task are the right ones according to the current DoW (amendment 2)
* The WPLs are expected to do periodic backup of their part (weekly, at least!). This is more serious than you may think, someone may delete all by mistake and then we would have a problem.
* The WPLs are expected to fill in the "general" parts of their WPs/chapters
* The WPLs are expected to ensure that all is consistent, have good quality and that all is delivered on time (Jan, 17). If they throw at me things that are in bad shape, they will have a negative observation in the report from the coordination
* The WPLs are expected to send reminders to the partners who failed to fill in their part.
* All the partners have a clear entry in all the tasks where they contribute.
* If the do not have anything to report, they do not delete their entry. They state "Nothing to report in this reporting period". This is entirely unambiguous (deleting your entry leaves room to think that maybe it is an oversight and that we forgot this partner).
* If a given partner fails to provide their inputs, I will waste no time. If someone is not interested in claiming money from the EC, I respect it. In the cases of partners with no info (or those who disregard the previous bullet point and delete their entries), I will add this in red: "This partner did not contribute contents to this part despite the requests of the coordination"
* We will request financial info in January at a later stage
* We will also start the creation of the Final Report soon (it is a different report from the one we are talking about in this message)
* If it helps, this is the previous report as we delivered to the EC.(you may find change tracking but this is how we delivered it for reasons that are out of the scope of this interaction): https://drive.google.com/file/d/0B6GGeaQGro3fZEpzSkZQd21PWWs/view?usp=sharing
Regards,
Miguel
--
Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>
----------------------------------------------------------------------
_/ _/_/ Miguel Carrillo Pacheco
_/ _/ _/ _/ Telefónica Distrito Telefónica
_/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 6
_/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
_/ _/_/ 28050 Madrid (Spain)
Tel: (+34) 91 312 94 15<tel:+34%20913%2012%2094%2015>
e-mail: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>
Follow FIWARE on the net
Website: http://www.fiware.org
Facebook: https://www.facebook.com/eu.fiware
Twitter: http://twitter.com/Fiware
LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
- http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE_Privacy_Policy
- http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE
Fiware mailing list
Fiware at lists.fiware.org<mailto:Fiware at lists.fiware.org>
https://lists.fiware.org/listinfo/fiware
--
Silvio Cretti,
Distributed Computing and Information Processing (DISCO)
Area Head
CREATE-NET Research Center
Via alla Cascata 56 D
38123 Povo, Trento - Italy
email: silvio.cretti at create-net.org<mailto:silvio.cretti at create-net.org>
Tel: +39-0461-312433
Mobile: +39-338-6738175
http://perfectcloud.it/
www.create-net.org<http://www.create-net.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-ops-dev/attachments/20161222/ea689096/attachment-0001.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy