Noel J. Bergman wrote:
Guys,
Now that a plan seems to be falling into place, I'd like to see a migration roadmap for those of us using the Avalon technology.
There have been some updated releases, and it seems that there are going to be some refreshes to coincide with the Merlin release. What I'd like to know is the plan for the remaining parts, including Cornerstone and Phoenix. Are we going to have one? What should those of us deploying on Phoenix expect to do in terms of upgrading our Avalon technologies, and when?
There is already a James deployment descriptor bundled in the Merlin distribution. Also, based on the recent work on the meta-data model, it is now feasible to consider automating the generation of deployment directives based on Phoenix assembly and configuration files.
Bottom line is that an operational James solution is already validated. The question comes down to the quality of the jump - there is content in Phoenix that is not provided in Merlin and content in Merlin that is not provided in Phoenix. So from here on its all about jump quality - what do you give up and what do you gain - and how does that equation change over time. Based on my knowlege of James - there is a retrograde step in terms of logging substems control - but that is the only area of concern I can think of. On the other side of the coin there are a bunch of rewards auch as increased opportunities for james and mailet service reuse, simplified configurations, etc.
Stephen.
--- Noel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
