Hi Lin, The RFC specifies hooks that can be used to limit the visible bundles and in this way to allow Virgo kernel to create user region. The RFC does not specify how to use the hooks of course, but it should be possible in theory to create more than one region with this technique. This however is not in the Virgo plan currently. Seems like you may use the same region for these projects. You said that they do not share resources, but what about modules? Are there any conflicting and backward incompatible module versions? Even if this is the case the projects can still be using the same user region since the EARs should be isolated in terms of classloading. Regards, Hristo Iliev From: virgo-dev-bounces@xxxxxxxxxxx [mailto:virgo-dev-bounces@xxxxxxxxxxx] On Behalf Of Linfengqi
Sent: Tuesday, December 07, 2010 11:33 AM
To: virgo-dev@xxxxxxxxxxx
Subject: Re: [virgo-dev] Minutes etc. of Virgo F2F Hi Hristo,
But I didn't find any content about multiple regions with framework hook in RFC 138, could you give me some articles or links about this. Thanks a lot!
Our scenario is, we have two projects, there isn't any relationship between these two projects, and they won't share the resources between each other. The load of each project is very low, so we want to deploy these two projects in one server. Each project is a EAR package which contains some core modules, a war file and a lib folder.
Best Regards
Lin Fengqi On Mon, Dec 6, 2010 at 8:48 PM, <virgo-dev-request@xxxxxxxxxxx> wrote: Send virgo-dev mailing list submissions to
virgo-dev@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/virgo-dev
or, via email, send a message with subject or body 'help' to
virgo-dev-request@xxxxxxxxxxx
You can reach the person managing the list at
virgo-dev-owner@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of virgo-dev digest..."
Today's Topics:
1. Re: Minutes etc. of Virgo F2F (Iliev, Hristo)
2. Re: Project meta data is out of date for rt.virgo
(Glyn Normington)
3. Re: Debian package (Glyn Normington)
4. Re: Debian package (Holger Staudacher)
5. Virgo weekly call -> conference room (Kapukaranov, Borislav)
----------------------------------------------------------------------
Message: 1
Date: Mon, 6 Dec 2010 08:58:23 +0100
From: "Iliev, Hristo" <hristo.iliev@xxxxxxx>
To: Virgo Project <virgo-dev@xxxxxxxxxxx>
Subject: Re: [virgo-dev] Minutes etc. of Virgo F2F
Message-ID:
<C84C4067E3732B4193B886F28DA0C67804056F0C6A@xxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"
Hi Lin,
The migration is triggered from the changes in RFC 138 . The aim is to adopt the hooks approach ASAP and to check if we have all the needed functionality. This early adoption would allow us to provide feedback in case there are some problems.
Theoretically it will still be possible to implement multiple regions with framework hooks, but this has to be checked in practice. That?s another reason we want to have the new implementation, so we can explore the possibilities (or limitations) in other directions also.
Currently Virgo supports (and is tested with) only one user region. It would be interesting to see a working prototype with more regions. Is this the case? Using more regions does not provide better isolation since the regions share the same VM and therefore same resources. Can you please share the use cases you have for multiple regions ? perhaps we are missing something?
Regards,
Hristo Iliev
From: virgo-dev-bounces@xxxxxxxxxxx [mailto:virgo-dev-bounces@xxxxxxxxxxx] On Behalf Of Linfengqi
Sent: Sunday, December 05, 2010 7:56 AM
To: virgo-dev@xxxxxxxxxxx
Subject: Re: [virgo-dev] Minutes etc. of Virgo F2F
Hi Glyn,
I saw the mail of F2F meeting, and there is a message about migration of user region. I knew the current user region is implemented by CompositeBundle, why we need migrate to framework hooks. And how to implement multiple user regions by framework hooks.
PS, we need multiple user regions to deploy multiple applications on a server, do you have any plan to implement this feature?
Migration of user region from nested framework to framework hooks
* Migration to Equinox 3.7 complete
* Prototyping necessary to see how well the user region functions with framework hooks
* May need to feed back issues into OSGi spec work, so needs to be high priority
Best Regards,
Lin Fengqi
On Sat, Dec 4, 2010 at 1:00 AM, <virgo-dev-request@xxxxxxxxxxx<mailto:virgo-dev-request@xxxxxxxxxxx>> wrote:
Send virgo-dev mailing list submissions to
virgo-dev@xxxxxxxxxxx<mailto:virgo-dev@xxxxxxxxxxx>
To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/virgo-dev
or, via email, send a message with subject or body 'help' to
virgo-dev-request@xxxxxxxxxxx<mailto:virgo-dev-request@xxxxxxxxxxx>
You can reach the person managing the list at
virgo-dev-owner@xxxxxxxxxxx<mailto:virgo-dev-owner@xxxxxxxxxxx>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of virgo-dev digest..."
Today's Topics:
1. Minutes etc. of Virgo F2F (Glyn Normington)
----------------------------------------------------------------------
Message: 1
Date: Fri, 3 Dec 2010 16:52:05 +0000
From: Glyn Normington <gnormington@xxxxxxxxxx<mailto:gnormington@xxxxxxxxxx>>
To: Virgo Project <virgo-dev@xxxxxxxxxxx<mailto:virgo-dev@xxxxxxxxxxx>>
Subject: [virgo-dev] Minutes etc. of Virgo F2F
Message-ID: <B30285C7-5944-4C54-BDE8-D21E24B57B69@xxxxxxxxxx<mailto:B30285C7-5944-4C54-BDE8-D21E24B57B69@xxxxxxxxxx>>
Content-Type: text/plain; charset="us-ascii"
Please see [1] for the minutes, presentations, etc. from this week's Virgo F2F.
Participants: please feel to correct/improve anything as you see fit.
[1] http://wiki.eclipse.org/Virgo/Community/F2F
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/virgo-dev/attachments/20101203/c7b7be0a/attachment.htm>
------------------------------
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx<mailto:virgo-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/virgo-dev
End of virgo-dev Digest, Vol 10, Issue 4
****************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/virgo-dev/attachments/20101206/48e7660a/attachment.htm>
------------------------------
Message: 2
Date: Mon, 6 Dec 2010 09:46:43 +0000
From: Glyn Normington <gnormington@xxxxxxxxxx>
To: Virgo Project <virgo-dev@xxxxxxxxxxx>
Subject: Re: [virgo-dev] Project meta data is out of date for rt.virgo
Message-ID: <E6429E7D-4416-44E1-88DB-1029A43287F7@xxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
Based on last week's F2F, perhaps we should set the next release of Virgo to be 3.0 in June 2011.
Thoughts?
Regards,
Glyn
On 5 Dec 2010, at 05:00, portal on behalf of emo wrote:
> Glyn,
> Projects are required to keep meta data up to date using the MyFoundation
> Portal (http://portal.eclipse.org/). The following problems were found
> with this project's meta-data:
>
> * There is no next/future release of this project. All Eclipse projects
> must have a "next release" planned and scheduled.
>
> _______________________________________________
> virgo-dev mailing list
> virgo-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/virgo-dev
------------------------------
Message: 3
Date: Mon, 6 Dec 2010 10:03:52 +0000
From: Glyn Normington <gnormington@xxxxxxxxxx>
To: Virgo Project <virgo-dev@xxxxxxxxxxx>
Subject: Re: [virgo-dev] Debian package
Message-ID: <3E211623-18D8-438F-B1B5-232C5E62E43A@xxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
Hi Peter
There is no debian package for Virgo. If you create a package and license it under the Eclipse Public License, I don't think you'll have any licensing issues.
The recently proposed Eclipse RT Packaging project is looking at creating these kinds of packages for RT projects, but I wouldn't let that put you off as it will be quite a while coming.
Regards,
Glyn
On 4 Dec 2010, at 12:37, Peter Lauri wrote:
> Hi,
>
> We are using debian packaging for our softwares in general, and we were thinking to create a debian package for Virgo. Or does it exist?
>
> If we choose to create a debian package for it, are there any licensing issues we would need to consider? Of course we would contribute this to debian/Ubuntu community as well.
>
> With regards,
> Peter Lauri
>
> * Sent on the road from my iPad
> _______________________________________________
> virgo-dev mailing list
> virgo-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/virgo-dev
------------------------------
Message: 4
Date: Mon, 6 Dec 2010 12:42:44 +0100
From: Holger Staudacher <hstaudacher@xxxxxxxxxxxxxxxxx>
To: virgo-dev@xxxxxxxxxxx
Subject: Re: [virgo-dev] Debian package
Message-ID: <3B68E326-8C1D-4BE5-8248-1D8496E5DA7D@xxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii
Hi Glyn and Peter,
the RT Packaging project will be publicly announced within this week I believe.
@Peter: One goal of the project is to deliver RT technologies like virgo in a more user friendly way. If you want to create a Debian we would welcome contributions or experience reports. Please keep us posted.
Regards Holger
Innoopract Informationssysteme GmbH
hstaudacher@xxxxxxxxxxxxxxxxx
Tel: +49 721 - 66 47 33 - 0
Fax: +49 721 - 66 47 33 29
========================= Legal Disclaimer =========================
According to Section 80 of the German Corporation Act Innoopract
Informationssysteme GmbH must indicate the following information:
Address: Stephanienstrasse 20, 76133 Karlsruhe Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
====================================================================
------------------------------
Message: 5
Date: Mon, 6 Dec 2010 13:48:11 +0100
From: "Kapukaranov, Borislav" <borislav.kapukaranov@xxxxxxx>
To: "virgo-dev@xxxxxxxxxxx" <virgo-dev@xxxxxxxxxxx>
Subject: [virgo-dev] Virgo weekly call -> conference room
Message-ID:
<DC7218B52792D340B42F087485716516302F634721@xxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"
Hello,
At the F2F we discussed the possibility of using a conference room with visual interaction instead of the current call.
The conference room is available at https://sap.emea.pgiconnect.com/virgo/
We'll see how the room works during this week's call and evaluate it in practice.
The time slot is the same - 14:00 UTC. To avoid confusion, see here for your time zone:
http://www.timeanddate.com/worldclock/fixedtime.html?year=2010&month=5&day=4&hour=14&min=0&sec=0
It is opened for everyone. Feel free to join as participants.
There is audio conference integrated in the room - when you join you should be prompted to specify your phone number.
Best Regards
Borislav
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/virgo-dev/attachments/20101206/e7f93d23/attachment.htm>
------------------------------
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
End of virgo-dev Digest, Vol 10, Issue 8
**************************************** |
