IAM
======
Name:           Update Center 2 Toolkit - IPS Enhancements
Submitter:      Tom Mueller
Owner:          John Fischer
Interest:       dev@updatecenter.dev.java.net
Status:         inception scheduled 09/23/2008
Exposure:       open

SUMMARY
=======

This is a sub-project of the Update Center 2 Toolkit project which
focuses on the IPS Enhancements, Java-based Bootstrap Initialization
Interface, IPS Java API and Python Dependency.

For details of the overall project see:

http://sac.eng/LSARC/2008/411/20080627_christopher.kampmeier

This case is focused on enhancements to IPS to be used by Update Center 2.0.
Update center is intended to provide new packaging technology with update capability for SW infrastructure products and eventually unbundled product.

Anticipating this packaging solution will be used by NetBeans, Glassfish, JCAPS and other Sun products as well. 

Umbrella case is composed of 2 parts:
-Update tool GUI
-IPS Enhancement Case, the case we are looking at today.
Software is intended to be useful beyond just OpenSolaris.

This includes:
-Changes that need to be put back into IPS gate, changes to the IPS software.
-Changes to the Update Center project.

What's part of Update Center:
-Making it portable to OpenSolaris and other platforms.
-Introduced a portable package to the IPS code (portable across multi-platforms)
-Created a build system.
-include wrapping the SW with scripts (for Windows).
-minimized Python distribution
-Packaged IPS and minimize Python into minimized packages so we can update
 our own packages with our own technology.



ISSUES
======

John Fischer questions:

What are you targeting for the OpenSolaris 2008.11 release?
-Haven't seen a change set go in yet. 
Features planned: search capability, RSF feeds, mirroring
 
In the 20q - the PSARC IPS case 2008/190 is refered to.
-That case is still in preinception mode and can't be used as a base case 
for this case. This case is dependent on that case. This must be noted 
in the doc.

In the Functional spec, the imported interfaces mentioned are in 
underlying OS. Will you be using them?
-JavaSE will be used as it is not included with the software.
If additional projects do adopt Phython, sharing copies of Phython may be 
an issue in the future, but it is not an issue now.

21:00
Discussion: John to note OpenSSL and export control related issue in the notes.

Under section 3.1.2 - everything is installed in user chosen location.
Will it use the IPS system dir or will it go through the process again?
-The user image is a container for software. The top of the user image is used
to run the sw under that directory.

Will the security questionaire be part of this case or the umbrella case?
-There hasn't been any changes or enhancements to security in IPS with this case.

Tom Childers questions:

  Is this going to be delivered on all platforms simultaneously?
  Yes. Testing on all platforms on all builds in occurring.

  Python was chosen as an implmentation vehicle b/c IPS used Python, is that  true?
  Yes. There was no viable way to deliver Python with Java Swing (Jython).
  Python was selected b/c there was not much Jython support at the time.

  Is there a plan to elimante Python implementation in the future?
  No. (Perhaps only the runtime enviornment.) Trying to maintain an 
equivalent   Java   implementation would require many resources. 
Jython route will allow portability and programmable access without
 having to rewrite the Java code.


THE NEXT STEP
=============

Tom Childers and Jyri Vriki to review the materials.
 
Approve: John Fischer, Aniruddh Dikhit, Chris Kasso, Lloyd Chambers, 
Deny:
Abstain: Tom Childers
NP:  Jyri Vriki