Bigtop
  1. Bigtop
  2. BIGTOP-417

webapps shipped by bigtop components should be using a system-provided Tomcat

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.2.0, 0.4.0
    • Fix Version/s: 0.4.0
    • Component/s: general
    • Labels:
      None

      Description

      We now have at least 2 different components that squirrel away private copies of Tomcat (Oozie and HTTPFS). The right approach is to setup different instances of the system Tomcat via CATALINA_BASE (still pointing at a common, system-wide CATALINA_HOME). More on how it works here:
      http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html
      http://willcode4beer.com/ware.jsp?set=tomcat_config

      1. BIGTOP-417.patch.txt
        13 kB
        Roman Shaposhnik
      2. BIGTOP-417-2.patch.txt
        5 kB
        Roman Shaposhnik

        Activity

        Hide
        Roman Shaposhnik added a comment -

        After spending some time reviewing the versions and availability of Tomcat for the platforms we have to support I'm leaning towards a solution of making tomcat be part of the Bigtop distribution itself. That will help us get around a sad state of affairs on platforms like CentOS 5 (where only Tomcat 5 is available, and Oozie/HTTPFS need at least 6) and also give a greater control over the versioning of Tomcat in general (we can keep it uniform across all the distros).

        Of course, we will not be a producing a general-purpose Tomcat packaging solution here. Think of it as an "embedded Tomcat" or as a Bigtop Container Platform (BCP). The proposed package name will be bigtop-tomcat and the location of files will be /usr/lib/bigtop-tomcat. No init.d scripts or /usr/bin scripts will be provided since the entry point will remain via the init.d scripts of individual components (e.g. /etc/init.d/

        {oozie,httpfs}

        ).

        Thoughts?

        Show
        Roman Shaposhnik added a comment - After spending some time reviewing the versions and availability of Tomcat for the platforms we have to support I'm leaning towards a solution of making tomcat be part of the Bigtop distribution itself. That will help us get around a sad state of affairs on platforms like CentOS 5 (where only Tomcat 5 is available, and Oozie/HTTPFS need at least 6) and also give a greater control over the versioning of Tomcat in general (we can keep it uniform across all the distros). Of course, we will not be a producing a general-purpose Tomcat packaging solution here. Think of it as an "embedded Tomcat" or as a Bigtop Container Platform (BCP). The proposed package name will be bigtop-tomcat and the location of files will be /usr/lib/bigtop-tomcat. No init.d scripts or /usr/bin scripts will be provided since the entry point will remain via the init.d scripts of individual components (e.g. /etc/init.d/ {oozie,httpfs} ). Thoughts?
        Hide
        Bruno Mahé added a comment -

        +1
        Seems like a great idea!

        Show
        Bruno Mahé added a comment - +1 Seems like a great idea!
        Hide
        Alejandro Abdelnur added a comment -

        +1

        Show
        Alejandro Abdelnur added a comment - +1
        Hide
        Peter Linnell added a comment -

        +1

        Show
        Peter Linnell added a comment - +1
        Hide
        Roman Shaposhnik added a comment -

        Attaching the first rough cut of the packaging. Once this is approved I'll try to make Oozie and HTTPFS use this package instead of bundling the Tomcat.

        Show
        Roman Shaposhnik added a comment - Attaching the first rough cut of the packaging. Once this is approved I'll try to make Oozie and HTTPFS use this package instead of bundling the Tomcat.
        Hide
        Peter Linnell added a comment -

        + 1 on the patch. Looks like a good start. Is this version of tomcat the preferred one ?

        Show
        Peter Linnell added a comment - + 1 on the patch. Looks like a good start. Is this version of tomcat the preferred one ?
        Hide
        Bruno Mahé added a comment -
        • why build-depends on git-core?
        • some indentation issues
        • +BIGTOP_TOMCAT_BASE_VERSION=6.0.35
          +BIGTOP_TOMCAT_PKG_VERSION=6.0.35

          If they are the same, just use BIGTOP_TOMCAT_BASE_VERSION

        Not blockers, but would be nice to have it fixed or tickets opened.

        Show
        Bruno Mahé added a comment - why build-depends on git-core? some indentation issues +BIGTOP_TOMCAT_BASE_VERSION=6.0.35 +BIGTOP_TOMCAT_PKG_VERSION=6.0.35 If they are the same, just use BIGTOP_TOMCAT_BASE_VERSION Not blockers, but would be nice to have it fixed or tickets opened.
        Hide
        Roman Shaposhnik added a comment -

        Attaching a second patch. This one hooks Oozie and HTTPFS to the bigtop-tomcat

        Show
        Roman Shaposhnik added a comment - Attaching a second patch. This one hooks Oozie and HTTPFS to the bigtop-tomcat
        Hide
        Roman Shaposhnik added a comment -

        @Bruno – thanks for the feedback. Took care of all the points.

        Show
        Roman Shaposhnik added a comment - @Bruno – thanks for the feedback. Took care of all the points.
        Hide
        Roman Shaposhnik added a comment -

        Too risky for 0.3 and fixed in 0.4

        Show
        Roman Shaposhnik added a comment - Too risky for 0.3 and fixed in 0.4

          People

          • Assignee:
            Roman Shaposhnik
            Reporter:
            Roman Shaposhnik
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development