Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Virgo/Community/F2F/Journal November 2010/Day2"
m |
m (→more later) |
||
| Line 13: | Line 13: | ||
Since the minutes are such a good summary, I'm going to limit these journal entries to extra-topic observations. Hope it isn't too ephemeral. | Since the minutes are such a good summary, I'm going to limit these journal entries to extra-topic observations. Hope it isn't too ephemeral. | ||
| − | ==== | + | ==== 09:30 start agenda - compare Virgo to other OSGi server solutions ==== |
| + | |||
| + | This was really a nice session — we were able to pat ourselves on the back a bit. However, Dmitry did remind us that the others were 'catching up' and that we need to get new compelling function in, or at least make the app developers job significantly smoother to reamin near the front of the pack. | ||
| + | |||
| + | Glyn had some observations around the use of Aries deployment on Virgo. This highlighted for us how hard it is for someone to place other components on our platform. Although most of the problems turn out to be dependency issues not of our making, this is still sobering — others will struggle to get these things working. | ||
| + | |||
| + | Out of this session (it was not a dissing exercise, honest) some requirements arose — these were nearly all simple things (not all) so there is no shortage of work for contributors/committers in the near future. The roadmap discussion later today will be very interesting. One of these was enhancements to administration — the use of Admin Console to dynamically manage logging, for example — and there were requests to make persistence issues much easier to handle. | ||
| + | |||
| + | Although this session wandered a bit, it has to be said that the comparisons were not at all bad for us. Other topics raised here were EJB support (?), JavaEE web profiles, and JPA solutions which cut down management/update burden for that sort of application ("98% of all apps use datasources" - D). | ||
| + | |||
| + | ==== 10:13 break ==== | ||
| + | |||
| + | ==== 10:23 development vs production modes ==== | ||
| + | |||
| + | It is clear that the idea of having special restrictions placed on servers in production would be quite a useful feature for admins. Coupled with a notion of 'captured resolution' for artifacts, this would go some way to allowing a production system to be robust, and potentially faster in deployment. The security of production systems (Krasimir talks about security later) could also be different, though it would be nice to switch this on in development for testing. In general we agreed that the 'mode' of a system should be visible on every (or nearly every) system admin panel displayed. Chris can surely manage this :-) | ||
| + | |||
| + | ==== 10:54 Jetty ==== | ||
| + | |||
| + | Chris gave an outline of the Jetty work — which involves having a Jetty layer instead of the web layer (including Gemini.web and tomcat) on top of the kernel to produce a new server config. Chris has successfully gotten Jetty running as a prototype, and, apart from a few refactorings and tweaks, splash and admin console should be able to run on top of this platform. It has to be said that some features are lost here — and import bundle is one of them — but this is not supposed to be functionally equivalent to the tomcat solution. | ||
| + | |||
| + | ==== 11:07 Snaps ==== | ||
Revision as of 10:00, 1 December 2010
Day 2
Florian arrived! Apparently he has had a woeful time stranded in Frankfurt and having to take a 'bus from Heathrow to Southampton as flights to So'ton were cancelled.
09:00 start
Glyn asked us all to identify ourselves (barring memory loss from last night), and this helped us all to attach names again.
Glyn then read minutes for yesterday for our perusal. (I hope this doesn't get reviewed too severely :-D) The summary was masterly (even recognisable) — well done Glyn.
Since the minutes are such a good summary, I'm going to limit these journal entries to extra-topic observations. Hope it isn't too ephemeral.
09:30 start agenda - compare Virgo to other OSGi server solutions
This was really a nice session — we were able to pat ourselves on the back a bit. However, Dmitry did remind us that the others were 'catching up' and that we need to get new compelling function in, or at least make the app developers job significantly smoother to reamin near the front of the pack.
Glyn had some observations around the use of Aries deployment on Virgo. This highlighted for us how hard it is for someone to place other components on our platform. Although most of the problems turn out to be dependency issues not of our making, this is still sobering — others will struggle to get these things working.
Out of this session (it was not a dissing exercise, honest) some requirements arose — these were nearly all simple things (not all) so there is no shortage of work for contributors/committers in the near future. The roadmap discussion later today will be very interesting. One of these was enhancements to administration — the use of Admin Console to dynamically manage logging, for example — and there were requests to make persistence issues much easier to handle.
Although this session wandered a bit, it has to be said that the comparisons were not at all bad for us. Other topics raised here were EJB support (?), JavaEE web profiles, and JPA solutions which cut down management/update burden for that sort of application ("98% of all apps use datasources" - D).
10:13 break
10:23 development vs production modes
It is clear that the idea of having special restrictions placed on servers in production would be quite a useful feature for admins. Coupled with a notion of 'captured resolution' for artifacts, this would go some way to allowing a production system to be robust, and potentially faster in deployment. The security of production systems (Krasimir talks about security later) could also be different, though it would be nice to switch this on in development for testing. In general we agreed that the 'mode' of a system should be visible on every (or nearly every) system admin panel displayed. Chris can surely manage this :-)
10:54 Jetty
Chris gave an outline of the Jetty work — which involves having a Jetty layer instead of the web layer (including Gemini.web and tomcat) on top of the kernel to produce a new server config. Chris has successfully gotten Jetty running as a prototype, and, apart from a few refactorings and tweaks, splash and admin console should be able to run on top of this platform. It has to be said that some features are lost here — and import bundle is one of them — but this is not supposed to be functionally equivalent to the tomcat solution.