Hi Alex, I provide the content of the Monitoring and Policy Manager architectural description. De: Alex Glikson <GLIKSON at il.ibm.com<mailto:GLIKSON at il.ibm.com>> Fecha: Thursday 26 February 2015 17:17 Para: "fiware-cloud at lists.fi-ware.org<mailto:fiware-cloud at lists.fi-ware.org>" <fiware-cloud at lists.fi-ware.org<mailto:fiware-cloud at lists.fi-ware.org>> Asunto: Re: [Fiware-cloud] URGENT: Architecture deliverable Some comments on the architecture, following a brief review: https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.Compute_R4 * In Copyright, mention that the 'baseline' specification is from OpenStack Foundation (see in Object Storage) * This page have to be self-contained -- to certain extent. Hence, need to outline also the architecture and the capabilities that we 'inherit' from 'vanilla Nova -- which we think are important. Remember that this is a *reference* architecture, not a product architecture. The rest of the comments are derived from this one. * Add a diagram showing Nova architecture (api, queue, DB, conductor, compute, etc) * Interactions: add also basic disk/network/image-related operations * Example: missing details. https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.ObjectStorage_R4 * Make sure CDMI is not mentioned (including examples) * Add details on storlets (including examples) * I suggest replacing the diagram with one which is more aligned with how Swift is architected https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.SelfServiceInterfaces_R4 * I suggest restructuring a bit the description to reflect that the Portal/Toolkit has different portions interacting with different underlying GEs. So, would be good to have a sub-section per underlying GE, elaborating on the main user-visible capabilities which are provided by leveraging the corresponding GE underneath. * Interactions section is missing (in fact, the per-GE details I mentioned above could be provided in this section) https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.Monitoring_R4 * Missing https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.Policy_R4 * Missing https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.ApplicationManagement_R4 * In Copyright, you should mention that the 'baseline' specification is from OpenStack Murano (since this is not an official OpenStack project, not sure whether the copyright belongs to OpenStack Foundation or to someone else.. - but I would guess it is) * Features: please, outline 'baseline' features too (in addition to the additional features we contribute) * Interactions: same as above -- add high-level details on 'baseline' iteractions * Example scenario is missing ==================================================================================== Alex Glikson Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab Email: glikson at il.ibm.com<mailto:glikson at il.ibm.com> | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Alex Glikson/Haifa/IBM at IBMIL To: fiware-cloud at lists.fi-ware.org<mailto:fiware-cloud at lists.fi-ware.org> Date: 24/02/2015 07:02 PM Subject: Re: [Fiware-cloud] URGENT: Architecture deliverable Sent by: fiware-cloud-bounces at lists.fi-ware.org<mailto:fiware-cloud-bounces at lists.fi-ware.org> ________________________________ I've updated the chapter-wide architecture diagram -- please, review & let me know whether you have any comments/suggestions. The components are color-coded -- blue for GEs we actively work on, green for components we reuse from OpenStack 'as is', and yellow for GEs from other chapters. I am still working on the text around the diagram. https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cloud_Hosting_Architecture_R4 Please, make sure you finish working on your individual GE pages by tomorrow's meeting at 15:00 CET. Thanks! Alex ==================================================================================== Alex Glikson Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab Email: glikson at il.ibm.com<mailto:glikson at il.ibm.com> | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: Alex Glikson/Haifa/IBM at IBMIL To: fiware-cloud at lists.fi-ware.org<mailto:fiware-cloud at lists.fi-ware.org> Date: 23/02/2015 07:41 AM Subject: Re: [Fiware-cloud] URGENT: Architecture deliverable Sent by: fiware-cloud-bounces at lists.fi-ware.org<mailto:fiware-cloud-bounces at lists.fi-ware.org> ________________________________ Apparently I forgot about: 9. Orchestration service (*) The old 9..12 would be 10..13. TID would own 9-13 now. Regards, Alex From: Alex Glikson/Haifa/IBM at IBMIL To: fiware-cloud at lists.fi-ware.org<mailto:fiware-cloud at lists.fi-ware.org> Date: 22/02/2015 05:22 PM Subject: [Fiware-cloud] URGENT: Architecture deliverable Sent by: fiware-cloud-bounces at lists.fi-ware.org<mailto:fiware-cloud-bounces at lists.fi-ware.org> ________________________________ Dear partners, Please, read this email carefully (and notice the deadline this Wed). As you know, the Architecture deliverable is due end of this week, and we are behind schedule (my fault). I would like to urge you to give this high priority this week, so that we can deliver on time (or with a small delay). I've started transforming the Wiki, and we should be able to work in parallel along this week. First, I've moved all the old architecture pages adding " R3" suffix (meaning "Release 3"), with redirects from the original to R3 pages [1]. Then I've created the R4 (meaning Release 4) version of the main architecture page: https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cloud_Hosting_Architecture_R4 I plan to copy the relevant content from the R3 main architecture page, and make the necessary updates -- so depending on the time you open this page, you might see a work-in-progress. I envision having the following GEs in the new R4 Architecture (aligned with the naming convention for official OpenStack services): 1. Compute service 2. Image service (*) 3. Volume service (*) 4. Network service (*) 5. Object storage service 6. Identity service 7. Toolkit 8. Dashboard 9. Monitoring service 10. Policy service 11. Application management service 12. Software configuration service The full names would be "FIWARE Cloud xxx service" -- e.g., "FIWARE Cloud Compute Service", "FIWARE Cloud Monitoring Service", etc. I assume the scope of each of the above is clear (notice that "Application management service" is the new name for PaaS & Murano -- we need to have a common approach to naming of GEs, aligned with the official OpenStack naming conventions). Let me know if you have any questions/comments/concerns regarding the approach & the specific components. Ownership of the individual components, as expected, is: IBM: 1-5 UPM: 6-8 TID: 9-12 Please, notice that the last section on this page, as before, comprises links to R4 architecture descriptions of the individual GEs in the NEW architecture. The plan is that the services marked with (*) will be consumed 'as is' from an OpenStack repository (by the operations teams), as we don't plan to make any changes to them. Hence, they will not have separate Architecture Description pages (at least for now) - just links to the corresponding community pages. Currently all the links are broken. You can just click on the link, and start editing the page. The structure should be the same as in R3 pages (you can also copy from there the relevant content, of course). Please, finish editing before our weekly call on Wednesday, so that we can have a quick review, discussion & round of further updates if needed, and be ready to deliver early next week. [1] R3 pages: https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cloud_Hosting_Architecture_R3 https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.DCRM_R3 https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.SM_R3 https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.SelfServiceInterfaces_R3 https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.CloudEdge_R3 https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.ObjectStorage_R3 https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.SDC_R3 https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.PaaS_R3 https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.Monitoring_R3 https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.Edgelets_R3 https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.ArchitectureDescription.Cloud.JobScheduler_R3 ==================================================================================== Alex Glikson Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab Email: glikson at il.ibm.com<mailto:glikson at il.ibm.com> | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 _______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.org<mailto:Fiware-cloud at lists.fi-ware.org> https://lists.fi-ware.org/listinfo/fiware-cloud_______________________________________________ Fiware-cloud mailing list Fiware-cloud at lists.fi-ware.org<mailto:Fiware-cloud at lists.fi-ware.org> https://lists.fi-ware.org/listinfo/fiware-cloud ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-cloud/attachments/20150226/1c3cf5b6/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy