thanks stefano, the concern we had with fernando it is that if we are gonna change the vision and related “implementation" of fiware lab, we would need as well to refocus the tool support part to match the vision and its needs. in these sense, it would be better to have such a vision before we work on things that may be made obsolete and hence waste resources we could refocus in shaping the lab to match the new vision. federico Dr. Federico Michele Facca Head of Martel Lab Martel Innovate Dorfstrasse 73 - 3073 Gümligen (Switzerland) 0041 78 807 58 38 0041 31 994 25 25 martel-innovate.com <http://martel-innovate.com/> > On 19 Dec 2016, at 17:32, Stefano De Panfilis <Stefano.DePanfilis at fiware.org> wrote: > > dear federico, > > thank you very much for your contribution to the discussion. > > in january, shortly alfonso/laura, will issue a doodle to properly start the discussion with all the concerned partners properly involved including, of course, the fiware foundation and the current commercial nodes. > > the plan is to release the fiware lab sustainability policy in a public way by no later then 30 june, which, i agree with you, is really soon so that to have it operative by 1st january 2018. > > of course before publicly releasing such policy we will also involve the community at large, for instance by realising a draft version around mid march/beginning apriland openning a period of community consultation. > > ciao, > stefano > > On 15 December 2016 at 11:01, Federico Michele Facca <federico.facca at martel-innovate.com <mailto:federico.facca at martel-innovate.com>> wrote: > Dear All, > In the past days we discussed about the sustainability of the nodes. it is clear that the federation, with centralised management of users and so on, it’s not sustainable > if not by covering through the public funding or the foundation when the fi-next project is over. but this of course, it’s not going to be sustainable for the foundation. > more the “cost” of managing the federation, it is quite relevant itself. we also know that users would prefer solutions with better slas (and potentially additional services). > > Thus, after discussing with different people here at the summit (mainly Fernando and Alex), I think we should go for a much simpler set-up. I am trying to summarise my proposal below: > > 1 - having one only real “fiware node” that is hosting the global instances, and providing some hosting capacity using containers / container clusters. access to vm > should be only granted in this reduced “lab” to fiware global service developer / operators. > 2 - providing a front-end that allows the community users to deploy (and monitor) in a simple way containerised generic enablers and apps on the lab node and on the standalone nodes > provided by other providers (ideally the fiware commercial providers). > 3 - having a mechanism that allow users to insert their credentials from the commercial providers in the tool of bullet 2 so that the deployment after this step is very simple. > 4 - (eventually) transforming fiware lab in an identity provider that can be leveraged by users to subscribe and access commercial providers services with a single account. > > Different Open Source options are available to build 2 rapidly > The included providers may ask for money, or provide a free tier, anyhow this is a different matter. For sure for the time their operation will be covered by FI-NEXT, > there should be a free tier. > This will avoid the need for duplicating nodes in part of FIWARE Lab and commercial ones. It will also mostly avoid any problem in relation to NREN policies (assuming > the central node will be hosted in RED.ES <http://red.es/> like today), because the NREN services will not be used for hosting commercial applications. > > We should also probably the discuss about revising the policy for community accounts if want to make them more inclusive and simple for users. On one side, > we could give up restrictions on getting details on what people want to do with FIWARE to attract more people to the Lab, > on the other we can introduce automatic identity verification mechanisms (e.g. based on credit card validation transactions) to make community account available instantly. > > Said so, as said already in the nodes mailinglist, the point that it is crucial to understand is also the vision of the foundation in this respect. We need to take decisions > asap, because then accordingly we can discuss how to re-focus efforts on the operational tools part to support the vision realisation quickly. > > My 2 cents, > Federico > Dr. Federico Michele Facca > Head of Martel Lab > > Martel Innovate > Dorfstrasse 73 - 3073 Gümligen (Switzerland) > 0041 78 807 58 38 > 0041 31 994 25 25 > martel-innovate.com <http://martel-innovate.com/> > > > __________________________________________________________________________________________ > > 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/FIWARE_Privacy_Policy> > - http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE <http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Cookies_Policy_FIWARE> > > FI-NEXT mailing list > FI-NEXT at lists.fiware.org <mailto:FI-NEXT at lists.fiware.org> > https://lists.fiware.org/listinfo/fi-next <https://lists.fiware.org/listinfo/fi-next> > > > > > > -- > Stefano De Panfilis > Chief Operations Officer > FIWARE Foundation > > mob: +393357542567 > skype: depa01 > twitter: depa01 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fi-next/attachments/20161220/48625987/attachment-0001.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy