Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 367830

Summary:	[nano] support cloning/clustering by reworking the configuration directory
Product:	[RT] Virgo	Reporter:	Glyn Normington <glyn.normington>
Component:	runtime	Assignee:	Borislav Kapukaranov <b.kapukaranov>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	b.kapukaranov
Version:	3.1.0.M01
Target Milestone:	3.5.0.M02
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Glyn Normington

2012-01-04 06:12:47 EST

Currently the configuration directory contains files config.ini and bundles.info which are logically part of the binary installation and which should be shared by cloned/clustered Virgo instances. However, the current configuration directory is mutated at runtime (to contain Virgo instance-specific data) and so it cannot be shared across instances.

A proposal Borislav and I have been discussing is to have p2 create the files config.ini and bundles.info in a lib/configuration directory and then copy these files into work/configuration in the startup scripts (after deleting work in the clean start case).

(We might also copy these files in a new Virgo shell command which would then perform the equivalent of the p2 confapply command in order to make dynamic updates, but that need not be implemented in this bug.)

Comment 1 Borislav Kapukaranov

2012-01-05 11:35:02 EST

Fixed with commits:
nano - 1c2ba11
kernel - cbb9c1b
web-server - 529d02e
jetty-server - 996548c

As a result the /config directory, merged with the new /configuration and the Equinox's configuration.area directory is now in /work, not it /work/osgi/configuration.
Also the new /configuration directory contains Equinox's config.ini, the bundles.info and Virgo's specific configurations.