United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6979976 Solaris IPS packages needed for Solaris 11 RR
JDK-6979976 : Solaris IPS packages needed for Solaris 11 RR

Details
Type:
Enhancement
Submit Date:
2010-08-25
Status:
Closed
Updated Date:
2011-03-30
Project Name:
JDK
Resolved Date:
2011-03-30
Component:
install
OS:
solaris,generic
Sub-Component:
install
CPU:
generic
Priority:
P2
Resolution:
Fixed
Affected Versions:
6u23,7
Fixed Versions:

Related Reports
Duplicate:
Relates:
Relates:
Relates:
Relates:
Relates:

Sub Tasks

Description
jdk6 updates need to generate/delever IPS style packages along with SVR4 packages, by RR of Solaris 11.

                                    

Comments
EVALUATION

Initial Analysis

IPS offers many advantages over the current solaris packaging service. Significant thought about the process of providing a network based  repository have not been shared with us. It is assumed that this task is about performing a basic install and not the numerous possibilities IPS provides for the Solaris java environment. IPS is the core infrastructure component to build such an environment. It is the role of the Feature request owners to define the scope of IPS  support the Oracle Java Distribution team is to implement. IPS can support 100's of Java add on applications versioned to work with this release as well as support for licensing terms and possible monetization offerings.



The Distribution team is currently supporting SVR4 packages for Solaris. 
A feature in Solaris packages allows one to load packages over the network using 

	pkgadd -d http:/..

Our arcane external download system (not the JRE Distribution system) implementation doesn't allow us to use these powerful modern installer features. This is mentioned  because IPS is inherently a service that supports operations over  the network. An initial install may not use a repostiory but it is assumed that users will want to download  over the network from repostiores that are hosted by Oracle. There are several duplications of efforts with installs of Java using IPS due to the inability of all projects to work with the latest version. We have consulted with the GF team, Dalibor Topic and several system admins. We have  failed to engage in any dialogs with the original IPS team and David Comay. We have also considered use cases on how users use Blast wave and Sun Freeware. Some of these efforts are due to lack of input on what the packaging system should provide.

The current items require definition from  various groups in Oracle, if Distribution Engineering is to implement them.  New Code Complete dates may result from additional features.

1) IPS  puts the "payload" in the close to final destination. Subsequent applications are to customize the install. There are no pre and post process  hooks for special processing.  There is no plan to provide lan a solaris installer. A small script may be needed to run after the installation is complete . We do not have a solution to installing and running an application without  user intervention at this time. Automated installers will be able to complete the process. We can provide examples on how to automate the installation so that Java is installed and runnable. 

2) Solaris systems are often used in graphical environments and many users may expect that the browser support Java and Web Start as well as browser plugins.  If  this is needed this should be requested as a separate CR so that other groups can  participate in its ongoing support and changes that may occur from release to release independent of the core install.

3) Will Oracle be providing an external server for users to install from? Who will own and manage this server if it is in scope. The process involved in getting that server online and into the distribution system is more work than the implementation of simple IPS support from a local repository.

4) What coordination is needed with the team producing the default install of a Solaris System so that there are no path conflicts and what Policy do we want with multiple versions. Solaris users cannot be updated by removing previous versions since this may break many missing critical apps which may not have registered with IPS.

5) IPS has implications for full releases versus patches. It is assumed that we will be doing a full release  unless we are going to create patches. In IPS a patch is just a new revision to get the base package too.


Some examples on defining what Oracle Java Distribution(OJD) implementation of IPS could mean

The Solaris team will distribute and stage all of the IPS components, the OJD needs to provide the  basic files,  to release notes and post install test and verification scripts.
IPS packages need to be available on external servers that are available all over the world
Customers can take the IPS package and create their own repositories
IPS installs should attempt to interface to the default browser on the system
IPS installs need to preserver previous packages
......
                                     
2010-10-08
SUGGESTED FIX

Implement packages to comply with the following document and process. Do not invest in the more complete update of the remote repositories at thtis time and java as it's own repository.

The IPS transition wiki actually just says "by RR", but there will be follow-up discussions with each C-team on when they can transition.  I think you will be contacted as the process gets worked.

-- Alan

On 10/29/10 03:19 PM, David Katleman wrote:
On 10/29/2010 3:11 PM, Alan Steinberg wrote:
Anything that is staying in Solaris 11 must be delivered via IPS by dev complete. So the alternative would be to yank it out before then.

Is "dev complete" the same as "Feature Freeze" listed on the S11 Schedule (Build 166,  05/16/2011)?

        Thanks
                    Dave



On 10/29/10 03:04 PM, David Katleman wrote:


On 10/29/2010 2:57 PM, Lou Ann Smith wrote:
Hi

Okay, I have relaxed them.  You should see WARNINGs now.

Thanks, that is indeed what I see now.

As to IPS, we don't expect to ever have them for the 5.0 based release.   I'm nudging the folks on my side to get 5.0 removed from S11, as planned.

But until that happens, I want to keep the copy of 5.0 that is there updated with the latest security fixes.

    Thanks
                Dave


On 10/29/10 02:41 PM, David Katleman (Oracle) wrote:
Hi guys!

Need to have the audits for SUNWj5* relaxed, we're integrating freshbitted packages, so the Pkginfo_VERSION will never be incremented.

Here are the relevant messages, let me know if you need full logs:

REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5rtx(i386): new_version=1.5.0,REV=2005.03.04.02.15:old_version=1.5.0,REV=2005.03.04.02.15
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5dvx(i386): new_version=1.5.0,REV=2005.03.04.02.15:old_version=1.5.0,REV=2005.03.04.02.15
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5dmx(i386): new_version=1.5.0,REV=2005.03.04.02.15:old_version=1.5.0,REV=2005.03.04.02.15
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5rt(i386): new_version=1.5.0,REV=2004.12.06.22.53:old_version=1.5.0,REV=2004.12.06.22.53
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5dev(i386): new_version=1.5.0,REV=2004.12.06.22.53:old_version=1.5.0,REV=2004.12.06.22.53
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5dmo(i386): new_version=1.5.0,REV=2004.12.06.22.53:old_version=1.5.0,REV=2004.12.06.22.53
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5man(i386): new_version=1.5.0,REV=2004.12.06.22.53:old_version=1.5.0,REV=2004.12.06.22.53
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5jmp(i386): new_version=1.5.0,REV=2004.12.06.22.53:old_version=1.5.0,REV=2004.12.06.22.53
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5cfg(i386): new_version=1.5.0,REV=2004.12.06.22.53:old_version=1.5.0,REV=2004.12.06.22.53
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5rt(sparc): new_version=1.5.0,REV=2004.12.07.00.07:old_version=1.5.0,REV=2004.12.07.00.07
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5dev(sparc): new_version=1.5.0,REV=2004.12.07.00.07:old_version=1.5.0,REV=2004.12.07.00.07
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5dmo(sparc): new_version=1.5.0,REV=2004.12.07.00.07:old_version=1.5.0,REV=2004.12.07.00.07
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5man(sparc): new_version=1.5.0,REV=2004.12.07.00.07:old_version=1.5.0,REV=2004.12.07.00.07
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5jmp(sparc): new_version=1.5.0,REV=2004.12.07.00.07:old_version=1.5.0,REV=2004.12.07.00.07
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5cfg(sparc): new_version=1.5.0,REV=2004.12.07.00.07:old_version=1.5.0,REV=2004.12.07.00.07
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5rtx(sparc): new_version=1.5.0,REV=2004.12.06.22.09:old_version=1.5.0,REV=2004.12.06.22.09
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5dvx(sparc): new_version=1.5.0,REV=2004.12.06.22.09:old_version=1.5.0,REV=2004.12.06.22.09
REJECT:Pkginfo_VERSION_MustBeIncremented:nv/SUNWj5dmx(sparc): new_version=1.5.0,REV=2004.12.06.22.09:old_version=1.5.0,REV=2004.12.06.22.09

       Thanks
                Dave

On 10/29/2010 2:12 PM, Lou Ann Smith wrote:
The integrate dock is now open for Solaris 11 build 152.

The deadline for build 152 delivery is:

       ** 10:00AM (Pacific Time) on Tuesday, November 2, 2010 **

Please review the Guide to Solaris 11 Package Integration for Release
Engineering:

http://wikihome.sfbay.sun.com/spe-re/Wiki.jsp?page=SolarisNextPkgIntegration

There is a single integrate dock for both sparc and x86 packages.  Here
is an example on how to integrate into Solaris 11:

/net/paradise/export/tools/bin/integrate -l <cteam name> -r nv_solnext <pkg>

C-team IPS repo packages are also delivered to the same dock:

/net/paradise/export/tools/bin/integrate -l <cteam name> -r nv_solnext
-i <cteam>.zip


You can review the following document on how to use the integrate command.

https://stbeehive.oracle.com/teamcollab/wiki/Solaris+Release+Engineering:Integrate+Command

Please integrate your packages early so that you can resolve any
package-related problems.

For assistance, please email ###@###.###.

-- Lou Ann
                                     
2010-10-29
WORK AROUND

IPS does not provide script actions to perform before and after install. The Java Bundles are installed using a naming convention relying on sumbolic  links. The FCS version of Solaris will include an application to manage the symbolic links. In the shortsort term some scripts will be provided with a readme telling users why and how it will work in the future. However this version may not make it to real users unless we decide to have somee type of beta/trial/internal test process for the IPS packages. It is not clear at this time how users will be informed and trained to go run the "Link Manager" to manage the Java versions, use this version of Java.

The Soalris 11 express edition is shipping with a  packaging schem that may or may not work with the FCS IPS packaging approach. It is expected  that those users will upgrade or be able to run package "remove/replace"  comamnds and create a working baseline. This is still being investigated.
                                     
2010-11-17
SUGGESTED FIX

After further discussions with David Comay and Bert Smalders the following implmentation is being performed.

1) Create a repository that contains the required packages for sparc, sparcv9, 586 and x64

2) Comply with IPS transition plan

3) Use IPS as it is intended and create symbolic links to enable use my other applications

4) Solaris 11 FCS will include an application to manage the links allowing users to use different versions.
                                     
2010-11-17
WORK AROUND

Recently there has been communicaiton from the IPS team that the delegated link manager may not be available for FCS.

When you install jdk7-1  and that is the latest a second onstall of jdk7-2 should become the latest and  so on jdk7-3... jdk7-n. Removal of jdk7-3 should make jdk7-2 the latest unless there was a jdk7-4.  There is no mechanism to make other versions the latest without additions of scripts or the facility proposed here:

   http://mail.opensolaris.org/pipermail/pkg-discuss/2010-October/024604.html

This is on the nice to have list but not critical. Why?

Java updates by providing a full release and leaving the previous version on the system image Most otther IPS packages update the current image so there is only one directory. having multiple versions of java is an assumed unwritten requirement based on what we have been doing.
                                     
2011-01-19
WORK AROUND

Java and IPS versions don't map due to alpha character use. A webapp has been developed to validate and or convert and validate a version. This tool can be found here: 

http://bursrotst07.east.sun.com:8082/cv.html

It is not decided if this tool will become permanent and need to go through an SQE test cycle. Initial load is slow due to validation of the 1.5 version numbers as an example of the mapping



1.5.0_01-b08 	1.5.0.1,5.11-8 	Success
1.5.0_02-b09 	1.5.0.2,5.11-9 	Success
1.5.0_03-b07 	1.5.0.3,5.11-7 	Success
1.5.0_04-b05 	1.5.0.4,5.11-5 	Success
1.5.0_05-b05 	1.5.0.5,5.11-5 	Success
1.5.0_06-b05 	1.5.0.6,5.11-5 	Success
1.5.0_07-b03 	1.5.0.7,5.11-3 	Success
1.5.0_08-b03 	1.5.0.8,5.11-3 	Success
1.5.0_09-b03 	1.5.0.9,5.11-3 	Success
1.5.0_10-b03 	1.5.0.10,5.11-3 	Success
1.5.0_11-b03 	1.5.0.11,5.11-3 	Success
1.5.0_12-b04 	1.5.0.12,5.11-4 	Success
1.5.0_13-b05 	1.5.0.13,5.11-5 	Success
1.5.0_13-ea-b01 	1.5.0.13,5.11- 	Failure
1.5.0_14-b03 	1.5.0.14,5.11-3 	Success
1.5.0_15-ea-b01 	1.5.0.15,5.11- 	Failure
1.5.0_15-b04 	1.5.0.15,5.11-4 	Success
1.5.0_15-b07 	1.5.0.15,5.11-7 	Success
1.5.0_15-b04 	1.5.0.15,5.11-4 	Success
1.5.0_15-b07 	1.5.0.15,5.11-7 	Success
1.5.0_15-b04 	1.5.0.15,5.11-4 	Success
1.5.0_16-ea-b01 	1.5.0.16,5.11- 	Failure
1.5.0_16-b02 	1.5.0.16,5.11-2 	Success
1.5.0_16-revHIT04-b02 	1.5.0.16,5.11- 	Failure
1.5.0_17-b04 	1.5.0.17,5.11-4 	Success
1.5.0_17-revHIT05-b04 	1.5.0.17,5.11- 	Failure
1.5.0_18-b02 	1.5.0.18,5.11-2 	Success
1.5.0_18-b02 	1.5.0.18,5.11-2 	Success
1.5.0_18-b02 	1.5.0.18,5.11-2 	Success
1.5.0_19-b02 	1.5.0.19,5.11-2 	Success
1.5.0_19-b02 	1.5.0.19,5.11-2 	Success
1.5.0_19-b02 	1.5.0.19,5.11-2 	Success
1.5.0_20-b02 	1.5.0.20,5.11-2 	Success
1.5.0_20-b02 	1.5.0.20,5.11-2 	Success
1.5.0_20-b02 	1.5.0.20,5.11-2 	Success
1.5.0_21-b01 	1.5.0.21,5.11-1 	Success
1.5.0_21-b01 	1.5.0.21,5.11-1 	Success
1.5.0_21-b01 	1.5.0.21,5.11-1 	Success
1.5.0_22-b03 	1.5.0.22,5.11-3 	Success
1.5.0_22-b03 	1.5.0.22,5.11-3 	Success
1.5.0_22-b03 	1.5.0.22,5.11-3 	Success
1.5.0_23-b01 	1.5.0.23,5.11-1 	Success
1.5.0_23-b01 	1.5.0.23,5.11-1 	Success
1.5.0_23-b01 	1.5.0.23,5.11-1 	Success
1.5.0_24-b02 	1.5.0.24,5.11-2 	Success
1.5.0_24-b02 	1.5.0.24,5.11-2 	Success
1.5.0_24-b02 	1.5.0.24,5.11-2 	Success
1.5.0_25-b03 	1.5.0.25,5.11-3 	Success
1.5.0_25-b03 	1.5.0.25,5.11-3 	Success
1.5.0_26-b03 	1.5.0.26,5.11-3 	Success
1.5.0_26-b03 	1.5.0.26,5.11-3 	Success
1.5.0_27-b02 	1.5.0.27,5.11-2 	Success
1.5.0_27-b02 	1.5.0.27,5.11-2 	Success
1.5.0_28-b03 	1.5.0.28,5.11-3 	Success
1.5.0_28-b03 	1.5.0.28,5.11-3 	Success
1.5.0_16-rev-b03 	1.5.0.16,5.11- 	Failure
1.5.0-beta3-b62 	1.5.0,5.11- 	Failure
1.5.0-b64 	1.5.0,5.11-64 		Success
1.5.0-rc-b63 	1.5.0,5.11- 		Failure
1.5.0-beta3-b62 	1.5.0,5.11- 	Failure
1.5.0-b64 	1.5.0,5.11-64 		Success
1.5.0-rc-b63 	1.5.0,5.11- 		Failure
                                     
2011-01-19



Hardware and Software, Engineered to Work Together