[Fiware-cloud] FIWARE (Cloud) Portal roadmap

[Joaquín Salvachúa]

Dear Alex 


Html and JavaScript is a very fast moving technology on actual web. Since a lot of applications and services depends on them there are several technology changes really fast adopted.

The main pattern is the MVC (Model – View – Controller ) is used to build and create the code.  

 Right now actual OpenStack Horizon uses django. This is a very sound MVC implementation on server side build over python language. This was the right decision some years ago.

This means all the application is run on the server side and transfer HTML & Javascript files to a browser.

 M-V-C   == > Client

Since this imply a lot of transfer and most of the actual devices have a lot of CPU and Memory some solutions move part of the MVC and HTML generation to the client side.  This implies less computation at the server and, in some cases, a lower cost over a cloud computer server infrastructure. 

 There is not a winning solution on this side.

This technology was used to build the Fiware Cloud portal.  At the time we choose backbone.js as the right library to build upon. 



Rest services  == >  MVC in client

This technology evolved and several new libraries appears.

 The problem is that a library change may imply to rewrite all the code for the portal.

 Inside the OpenStack community some experiences where develop   using the solution proviced by google angular.js (https://etherpad.openstack.org/p/horizon-kilo-virtual-sprint <https://etherpad.openstack.org/p/horizon-kilo-virtual-sprint> ). This is an hybrid temporal solution to show how it can be done. We are experience with this technology.

 There is another proposal to use a pure client approach (like our Fiware portal) but based on angular.js  (https://github.com/r1chardj0n3s/angboard <https://github.com/r1chardj0n3s/angboard> )

 To make things more complex right now angular.js is facing a full non backwards compatible rewriting  (angular.js 2.0 ) not yet available but probably ready by octuber  and a new library  react.js proposed and used by facebook, twitter or yahoo. We think that react.js could be the properly library to rewrite horizon with.

 This means that we don’t forseen a sound solution for the cloud portal. Keep in mind that most solutions require a full rewriting of all the portal code, without any warranty that it wont need to be rewritten  in the very close future.

Best Regards

Joaquín 

 

 

 

 
> El 6/5/2015, a las 14:49, Alex Glikson <GLIKSON at il.ibm.com> escribió:
> 
> Dear Alvaro, Joaquin, all, 
> 
> I've recently seen a blog post [1] suggesting that OpenStack Horizon is making progress towards adoption of client-side UI (based on AngularJS). Apparently, it seems that the "old" Horizon is transforming, gradually incorporating the "new" client-side code. 
> 
> I wonder what is currently the roadmap of our portal developments with regards to alignment with (and contribution to) this transformation. 
> 
> And a related question, given the transition from the 'legacy' PaaS manager to Murano in FIWARE, what is our UI plan here - do we plan to change the existing Cloud Portal to work with Murano APIs, or do we plan to migrate to 'native' Murano UI? Or some other approach? 
> 
> Maybe we can add this to the agenda of today's weekly call in few minutes. 
> 
> Thanks, 
> Alex 
> 
> 
> [1] https://developer.ibm.com/opentech/2015/05/05/horizon-kilo-cycle-recap-2/ <https://developer.ibm.com/opentech/2015/05/05/horizon-kilo-cycle-recap-2/> 
> 
> ====================================================================================
> Alex Glikson
> Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab
> Email: 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
> https://lists.fi-ware.org/listinfo/fiware-cloud

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-cloud/attachments/20150520/647c5143/attachment.html>