Bugzilla – Full Text Bug Listing
| Summary: | Provision Virgo with p2 | ||
|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | Borislav Kapukaranov <b.kapukaranov> |
| Component: | runtime | Assignee: | Borislav Kapukaranov <b.kapukaranov> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | frank, glyn.normington, gunnar, mlippert, rafal, s.yousouf, slewis |
| Version: | 3.0.0.M04 | ||
| Target Milestone: | 3.5.0.M01 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
| Bug Depends on: | 345277, 363133, 363135, 363137, 363140, 363142, 363146 | ||
| Bug Blocks: | 364571 | ||
|
Description
Borislav Kapukaranov
How do you plan to implementing this? Are there concrete ideas beyond what had been initially discussed on the p2-dev mailing list [1]? [1] http://dev.eclipse.org/mhonarc/lists/virgo-dev/msg00778.html Yes, there's been development on most of the ideas. We plan to start releasing alpha milestones of 3.5 when the 3.0 work is complete. Hopefully that will happen soon. Probably these will be in parallel with the master branch so 3.x(x<5) release is possible. These alpha milestones will include comprehensive documentation for the p2 integration in Virgo's programmer guide. (In reply to comment #1) > How do you plan to implementing this? Are there concrete ideas beyond what had > been initially discussed on the p2-dev mailing list [1]? > > [1] http://dev.eclipse.org/mhonarc/lists/virgo-dev/msg00778.html Tobias: in case you missed it, see Borislav's recent blog: http://bkapukaranov.wordpress.com/2011/07/12/rt-meets-p2/ The Virgo-p2 integration has taken a radical turnaround during the last week. The major difference is that we now use every external component "as-is". This frees us from inter-component dependencies and is a good environment to progress fast. In a nutshell we decided to provide a new distribution that lives below the current “kernel” and “web-server” space. It shares some diagnostics and supportability features available in the current distributions. Being the smallest Virgo offering, it is a single-region environment which is in some ways similar to the kernel region of the other distros. The working name for this new distribution is Nano. Initial provisioning via p2 is coming to all Virgo flavors, but only Nano will be extended via p2. The current distributions will continue to be extended via the Virgo deployer component. Supportability features included in Nano are - logback logging - event logging - deadlock detection with more on the way. This week I’ll break down the remaining tasks into bugzillas. The first milestone of 3.5.0 is released. The released milestones actually carries version 3.1.0 because of a version range restriction placed by the Gemini Web implementation we are using. The next milestone(M02) will carry the proper version. The repository from which you can provision every Virgo distribution is http://download.eclipse.org/virgo/updatesite/3.1.0.M01 Chapters 3) and 8.4) from Virgo's User Guide relate to using the available p2 tooling to both initial provision and extend a Virgo distribution. These will be enhanced more in future but are sufficient for a first step. Bug 364571 is the umbrella enhancement that tracks the remaining Virgo Nano work such as hot-deployment and Virgo tooling enhancements. With the initial provisioning available I'm closing this enhancement. |