Ubuntu Wiki

• Launchpad Entry: server-karmic-eucalyptus-in-main

• Created: June 2nd, 2009

• Contributors: ThierryCarrez

• Packages affected: lots

Summary

Eucalyptus, as part of the Ubuntu Enterprise Cloud, needs to move to main to be properly supported by Canonical. That means that all runtime and build-time dependencies (and all dependencies of the dependencies) must also move to main. This specification tracks which packages will need to move to main and efforts made to reduce the total number as much as possible.

Release Note

Eucalyptus is now part of the Ubuntu "main" repository, and fully supported by Canonical.

Rationale

Eucalyptus is currently in universe, together with most of its Java library dependencies. Since Eucalyptus is part of the Ubuntu Enterprise Cloud product, it needs to be properly supported by Canonical, which means move to the "main" repository. However, packages in "main" also need to have all their runtime and build-time dependencies in "main" as well. Java software in general heavily makes use of other Java libraries, so this quickly snowballs into a large number of packages to move to main. Furthermore, there isn't so much Java-based software in main already (OpenOffice.org, tomcat6) so even some basic Java libraries need to be moved.

User stories

• Dave has been trying the UEC technology preview in 9.04 and aims to deploy UEC with the 9.10 release. As it will no longer be a technology preview, it needs to be properly supported.

Assumptions

This spec does not take care of any other non-Java MIR that Eucalyptus may need. iscsitarget for example could be a new 1.6 dependency, and it is in universe currently.

Design

We need to try to keep the number of packages as small as possible in order to avoid MIR team overload. Some hacks (like duplicating some greedy source packages to avoid bringing lots of unnecessary build dependencies) are worth the trouble if they save a significant amount of packages. However Debian doesn't care about keeping the number of dependency packages small, so those hacks don't really make sense from a Debian perspective.

Avoid packages difficult to maintain

• Abandoned stuff
  • OpenSAML 1.1/Java
• Large software stacks
  • JBoss (pulled through Hibernate)
  • Glassfish (pulled through glassfish-javaee and glassfish-toplink-essentials, used as build-deps)

Proposed actions for package number reduction

• Use a specific eucalyptus-hibernate package instead of generic libhibernate3-java: saves 34+ packages
• Include libhibernate-entity-manager in eucalyptus-hibernate: saves 10+ packages
• Include libhibernate-[commons-]annotations in eucalyptus-hibernate: saves 2 packages (?)
• Use glassfish-javaee instead of geronimo-* (?)

• Remove dependency from libclassworlds-java -> maven-ant-helper: saves 8+ packages

• xmlbeans is no longer needed (Axis2 build dep) so removed libxmlbeans-java libsaxonb-java from list
• Add arch-based recommend in antlr3 + build as "any": removed antlr3-gcj from list
• Add arch-based recommend in libbcprov-java + build as "any": removed libbcprov-java-gcj from list

Resulting list (without those from RefactorEucalyptusJavadepsSpec)

New dependencies expected from Eucalyptus 1.6

• netty 3.1
• dnsjava
• Excalibur
• geronimo-ejb_3.0_spec-1.0.1
• geronimo-jpa_3.0_spec-1.1.1

Packages expected from RefactorEucalyptusJavadepsSpec

• Axiom
• Drools
• Mule
• MVEL
• WSS4J
• Spring
• JUG
• Jetty 6
• Google Web Toolkit

Packages from Eucalyptus-Hibernate

• eucalyptus-hibernate

Dependencies from Spring

Core dependencies

Extra dependencies coming from Debian packaging

Note: we would patch so that it uses:

• libtomcat6-java instead on libtomcat5.5-java (avoiding libcommons-[el,launcher,modeler]-java)
• tomcat6-examples instead of glassfish-appserv

Can we get rid of :

Glassfish decision

Including glassfish source in main would give us glassfish-javaee and glassfish-toplink-essentials. But it also means we engage in supporting Glassfish v2 in main ?

To do it we require:

• Getting rid of glassfish-toplink-essential dependency in Debian Spring
• Getting rid of stale glassfish-javaee dependencies everywhere else

If we don't do it, we can get rid of 9 geronimo-* equivalents and use 2 glassfish things instead (-7)

Total

• 54 from primary list
• 5 from new Eucalyptus deps

• 9 from RefactorEucalyptusJavadepsSpec

• 1 from Euca-hibernate
• 20 from Refactor/Spring

Total: 89 packages to MIR

Other potential actions to reduce number of packages

• Do a minimal Spring rather than take Debian spring, get rid of (at most) 17 packages

Implementation

Create eucalyptus-hibernate

Create the specific eucalyptus hibernate libraries, containing the subset of hibernate needed for Eucalyptus and not all the JBoss hooks the libhibernate3-java package contains.

Those should be shipped as the new "eucalyptus-javadeps" package (which is kept to include all the non-standard libraries required by Eucalyptus).

Implement other hacks

All the other number-reducing hacks should be implemented:

• Remove dependency from libclassworlds-java -> maven-ant-helper

• ...

Determine final map of MIR, split into sets

The final dependencies should be determined and splitted into sets that can be handled separately.

Process MIR sets

Several options, to be discussed with MIR team:

• One bug per set, one task per package in set
• One bug per package
• One bug for everything
• Process outside Launchpad, with one metabug to track progress

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

None.

BoF agenda and discussion

UDS discussion

Current status

• 99 packages which would need to move to main.

• Java in main is currently driven by OpenOffice. Tomcat6 is there, but has few dependencies.

Future

• Eucalyptus version for Karmic should have fewer dependencies anyway from upstream refactoring.

How can the number of build/runtime dependencies be reduced?

• Get rid of anything not necessary
  • Geronimo spec packages (already provided by glassfish-j2ee)
• Move parts into Eucalyptus code
• Refactor packages (e.g. hibernate pulls in a lot of stuff)
  • Requires multiple source packages or only to promote some resulting binaries to main.
    • (doko recommends duplicating the source package and documenting it)

What could be expected to be refused inclusion to main

• Active upstream criteria
  • Annogen
  • OpenSAML
  • WSS4J?
• Known to be insecure
  • Nothing obvious
• Partial builds (because of non-free dependencies)
  • Mule
  • We don't really care

Size issues (adding to default CD)

• GWT is 6MB of binary
  • 1.6 should be more granular and work with existing java packages more
• JRuby is 3MB
  • Just be a build-time dependency of GWT
• libjgroups-java, 3MB. Not needed ?
• glassfish-toplink-essentials, 2.4MB, comes from hibernate
• Avoiding JDK would save about 50MB of CD space
• Avoiding GCJ would save about 20MB

Can we use the new Spring packaging from Debian?

• Not included yet in Debian, but work is underway
• Might make too hard choices for us ? Testing from Eucalyptus side needed.

Safety net

• Keep a eucalyptus-javadeps package to drop in any problematic parts which can't be fixed (hibernate?).
  • One tiny part of Drools

Action Summary

• Which Eucalyptus version we'll use in Karmic and its dependencies?
• Can we use Spring from Debian?
• What can we do to reduce Hibernate size?
  • Will it be acceptable to move JBoss to main?
• JDK dependency investigation
• Ask Colin about blacklisting for the server seed only to solve GCJ issue
• Once it's known what is required, start preparing/filing MIRs to avoid a last minute panic.

CategorySpec