It is not clear from the document that we have basically decided on option 2. This is already since you can include in a cover letter when you send it to Juanjo. There is no mention of the fact that you are using a fork of Keystone and intend examine how in the future you can use vanilla Keystone. I think the next step is to send this document with a cover letter to Juanjo. I also think we should present our conclusions to TSC. I think the conclusions should be presented to the TSC as a set of slides that will cover the conclusions. If possible I will like to do this in next week's TSC meeting (if Juanjo is present). Best Regards, Kenneth Nagin Ph: +972-4-8296227 Cell: 054-6976227 Fx: +972-4- 8296114 http://researcher.ibm.com/view.php?person=il-NAGIN From: Álvaro Alonso <aalonsog at dit.upm.es> To: Alex Glikson/Haifa/IBM at IBMIL Cc: fiware-cloud at lists.fi-ware.org, "Federico M. Facca" <federico.facca at martel-innovate.com>, Federico Fernández <fefernandez at dit.upm.es> Date: 14/12/2016 05:01 PM Subject: Re: [Fiware-cloud] New Cloud Portal evolution Document Sent by: fiware-cloud-bounces at lists.fiware.org Hi Alex, many thanks for your comments. We have just updated the document accordingly. Regarding your last comment about cloud organizations, we have also added a note with the alternative you propose. However, to have an estimation of the needed effort its needed to perform a detailed analysis that also takes time :) BR -- Álvaro [attachment "20161214 FIWARE Cloud Portal Evolution v4.pdf" deleted by Kenneth Nagin/Haifa/IBM] El 14 dic 2016, a las 13:12, Alex Glikson <GLIKSON at il.ibm.com> escribió: Thanks, Alvaro. Couple of comments: "In order to support multiple regions in the same way that Cloud Portal does currently, an extensive part of Horizon core should be rewritten" - this seems inaccurate, given the discussion yesterday "This is especially significant when thinking about access permissions to regions and projects. By default, Horizon allows every user to create Cloud resources in any of its Keystone projects." - can we turn this into a 1st level item, replacing "other modifications" with specific items? "Terms and conditions app would be lost" - I think a more accurate statement would be that it will be merged with general FIWARE Lab terms and conditions. "Sanity checks app [...] (nodes status visualization)" - I would recommend making the wording more accurate by referring specifically to region/node health indicator in region/node drop-down. "Recipes management" - isn't this something that is available as part of Murano? I see that you added "Important note after Cloud Project meeting at Malaga FIWARE Summit (December 13th, 2016)" on page 7-8. I think it is a good summary of the prefered option we came up with. It seems that there is one high-risk item -- per-organization access control, disabling access to cloud capabilities in certain organizations. It seems to me that creating a special role in Keystone for access to cloud capabilities, and configuring the 'core' services to require this role, may solve the problem. Of course, the Account portal would need to set this role properly, and maybe also requiring some other changes (e.g., avoid org admin from assigning this role to their users later on). It might be good if you could take a closer look at this, and come up with some conclusions (and potentially sizing to implement this). Kenneth - how would you like to take this forward? Regards, Alex =========================================================================== Alex Glikson Senior Researcher, Cloud Platforms, IBM Research - Haifa; IBM Lead for FIWARE Email: glikson at il.ibm.com | Skype: alex.glikson | Phone: +972-4-8281085 | Mobile: +972-54-6466667 From: Álvaro Alonso <aalonsog at dit.upm.es> To: fiware-cloud at lists.fi-ware.org Cc: Federico Fernández <fefernandez at dit.upm.es> Date: 14/12/2016 11:31 AM Subject: [Fiware-cloud] New Cloud Portal evolution Document Sent by: fiware-cloud-bounces at lists.fiware.org Hi all, attached the new version of the document based on the analysis we perform during our meeting yesterday BR -- Álvaro[attachment "20161214 FIWARE Cloud Portal Evolution.pdf" deleted by Alex Glikson/Haifa/IBM] __________________________________________________________________________________________ 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-cloud mailing list Fiware-cloud at lists.fiware.org https://lists.fiware.org/listinfo/fiware-cloud __________________________________________________________________________________________ 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-cloud mailing list Fiware-cloud at lists.fiware.org https://lists.fiware.org/listinfo/fiware-cloud -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-cloud/attachments/20161215/faaf7f55/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy