[this might be a bit off-topic, so I apologize in advance - we can have a separate conversation on this] >> In addition and in regards of the open Source Community for FIWARE, why to add a GE manage by another Open Source Community? This is an excellent question. In fact, we may need to clarify the corresponding statement in the proposed governance model, currently stating: Technical work within the FIWARE Chapters is intended to advance ICT technologies. Such advancement can be in the form of implementing brand new technologies, but also evolving/adapting existing technologies eventually starting from good available technologies even if produced from the outside of the FIWARE Community. In this respects good and mutual beneficial relationships with other relevant communities (e.g. OpenStack, Apache) are in scope of the FIWARE Mission. In cases when evolving existing technologies (originally developed by existing communities) is the best way to promote the FIWARE Mission, we need to be clear on the expected approach. In some cases the prefered approach might be to contribute to the original community, focusing on promoting things important for FIWARE, rather than maintaining our own "fork" of the code under FIWARE namespace in github. Then the role of the GE team within FIWARE might involve facilitatation between the two communities, contributions either upstream or downstream (on a case by case basis), support (also 'by proxy' in some cases), etc. An alternative approach might be to say that FIWARE comprises (and governs) only things invented within the consortium (and hence there are no relevant existing communities to engage with). Frankly, I am not sure how sustainable such approach would be, given the enormous pace of innovation happening in the industry outside of FIWARE. At the end, this boils down to the question 'what FIWARE is' and 'what FIWARE Reference Architecture' is. But maybe I am taking this to a too phyilosophic direction, and there are more pragmatic ways to address the related questions that may arise. Regards, Alex From: <thierry.nagellen at orange.com> To: Alex Glikson/Haifa/IBM at IBMIL Cc: "fiware-chapter-architects at lists.fiware.org" <fiware-chapter-architects at lists.fiware.org>, "fiware-chapter-leaders at lists.fiware.org" <fiware-chapter-leaders at lists.fiware.org> Date: 21/07/2015 12:46 PM Subject: RE: [Fiware-chapter-leaders] [Fiware-chapter-architects] EC Review - Folder for presentations Hi Alex, I try to play the role of EC expecting to cut some budget for other activities? For me Docker GE is anything more than just Docker and should provide and added value that you cannot find if you are just using the results from Docker Open Source community. There are also initiatives in Open Stack to include docker for Open Stack so introducing Docker GE should have an impact on the architecture (and this impact is not really clear at least for me but I?m not an expert in Docker) and not just using docker as a tool to propose a better user experience for deployment. Again, FIContent and Accelerators have used Docker without any Docker GE. In addition and in regards of the open Source Community for FIWARE, why to add a GE manage by another Open Source Community? For the second point on cloud GEs, my point is that if you explain that you can stop existing GE, for external people (and we have 3 new reviewers) the sustainability itself of FIWARE Lab could be in danger: · who will provide support for the existing GEs, · how future integration will be managed by FIWARE Community? I think we have to explain how features from DCRM GE are already available in open Stack releases and in which components of Open Stack.Does cloud become more, for this part, a facility than an enabler? We have already SMEs funded by accelerators which have installed some GEs in AWS or Google Cloud so they have somewhere demonstrated that current commercial offers could integrate some FIWARE GEs. I fully understand the point on Object Storage but here also my question would be why has FIWARE to work on this issue? What is the status from Open Stack community point of view because if we expect to be aligned with them in 1 year, does FIWARE spend time on this part? BR Thierry De : Alex Glikson [mailto:GLIKSON at il.ibm.com] Envoyé : mardi 21 juillet 2015 11:15 À : NAGELLEN Thierry IMT/OLPS Cc : fiware-chapter-architects at lists.fiware.org; fiware-chapter-leaders at lists.fiware.org Objet : RE: [Fiware-chapter-leaders] [Fiware-chapter-architects] EC Review - Folder for presentations Thanks for your comments. Not sure I understand the distinction between introducing Docker GE and "use Docker directly". GE is a "building block of the FIWARE Reference Architecture, supporting reusable and commonly shared functions serving a multiplicity of use cases across various application domains". Docker runtime is certainly going to be a FIWARE building block supporting reusable and commonly shared functions serving a multiplicity of use cases across various application domains. Can you, please, clarify what is your concern in this regard? Alignment with OpenStack is something we did ~4 years ago, so there is not much news here to report on.. What has changed is that 'vanilla' OpenStack is now good enough to serve most of FIWARE IaaS needs. Does this mean that OpenStack does not need to be reflected in FIWARE Reference Architecture? No, we actually gradually increase the OpenStack adoption, but our development efforts are prioritized a bit differently. Notice that this is a FIWARE Cloud chapter perspective. How exactly the technology is being consumed by FIWARE Lab teams is an important but separate discussion. In general, the slide assumed that the audience is familiar with the situation and developments in FIWARE Cloud in the last 4 years, and the emphasis is on the delta (also given the time constraints). I can add an additional slide or two for reference, to make it more self-contained, potentially skipping them during the review. Thanks, Alex From: <thierry.nagellen at orange.com> To: Alex Glikson/Haifa/IBM at IBMIL, " fiware-chapter-leaders at lists.fiware.org" < fiware-chapter-leaders at lists.fiware.org> Cc: "fiware-chapter-architects at lists.fiware.org" < fiware-chapter-architects at lists.fiware.org> Date: 21/07/2015 11:12 AM Subject: RE: [Fiware-chapter-leaders] [Fiware-chapter-architects] EC Review - Folder for presentations Hi Alex, As explained on the phone yesterday morning, you should reinforce the added value of integrating Docker like a GE. I think it is better to include a dedicated slide for that, the one you have in your presentation yesterday. If you use just ?Docker GE? the question will be why not to use docker directly? Maybe you could also add a general comment on the alignement with current versions of Open Stack to justify to stop DCRM and that FIWARE might be sustainable. BR Thierry De : fiware-chapter-leaders-bounces at lists.fi-ware.org [ mailto:fiware-chapter-leaders-bounces at lists.fi-ware.org] De la part de Alex Glikson Envoyé : lundi 20 juillet 2015 21:44 À : fiware-chapter-leaders at lists.fiware.org Cc : fiware-chapter-architects at lists.fiware.org Objet : Re: [Fiware-chapter-leaders] [Fiware-chapter-architects] EC Review - Folder for presentations I've uploaded a 1-slide presentation outlining the Cloud chapter refocus plan. Comments are welcome. Regards, Alex ==================================================================================== Alex Glikson Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab; FIWARE Cloud Leader & Architect Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: <thierry.nagellen at orange.com> To: MANUEL ESCRICHE VICENTE <manuel.escrichevicente at telefonica.com >, "fiware-chapter-leaders at lists.fiware.org" < fiware-chapter-leaders at lists.fiware.org>, " fiware-chapter-architects at lists.fiware.org" < fiware-chapter-architects at lists.fiware.org> Cc: Angeles Tejado <angeles.tejado at ogilvy.com> Date: 20/07/2015 11:29 AM Subject: Re: [Fiware-chapter-architects] EC Review - Folder for presentations Sent by: fiware-chapter-architects-bounces at lists.fi-ware.org Hi All I have just uploaded a new version of the sustainability presentation. I have add the new recommendations for developers, an external view of Open Source licenses (current landscape) and some open points about communication for the future FI-OSC. BR Thierry De : fiware-chapter-leaders-bounces at lists.fi-ware.org [ mailto:fiware-chapter-leaders-bounces at lists.fi-ware.org] De la part de MANUEL ESCRICHE VICENTE Envoyé : lundi 20 juillet 2015 08:49 À : fiware-chapter-leaders at lists.fiware.org; fiware-chapter-architects at lists.fiware.org Cc : Angeles Tejado; Francisco de la Vega Objet : [Fiware-chapter-leaders] EC Review - Folder for presentations Dear Partners, As you know we have to send the presentations to the EC beforehand. Please, find below the link to a google drive folder where to upload and share them. https://drive.google.com/folderview?id=0B3xxmzdEZ1WtfktCUU5QZjZfTGhIVXhmUWVwUjdCN1N1R0JkU1ZySVY1YjlFZTZmcTV4c1E&usp=sharing If you had any objection, or trouble to access it, please let me know. Kind regards, Manuel ---------------------------- Manuel Escriche Vicente Agile Project Manager/Leader FI-WARE Initiative Telefónica Digital Parque Tecnológico C/ Abraham Zacuto, 10 47151 - Boecillo Valladolid - Spain Tfno: +34.91.312.99.72 Fax: +34.983.36.75.64 http://www.tid.es Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição _________________________________________________________________________________________________________________________ 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. _______________________________________________ Fiware-chapter-architects mailing list Fiware-chapter-architects at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-chapter-architects _________________________________________________________________________________________________________________________ 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. _________________________________________________________________________________________________________________________ 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-chapter-leaders/attachments/20150721/5f315b33/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy