OpenPKG 4.0 licenses explained

2010-01-02 by Thomas Lotterer

The new OpenPKG 4.0 framework is a shareware product. Here is an explanation of the licenses available today. Most of them are free of charge, one can be purchased from the OpenPKG GmbH online shop.
See what licenses are installed and which one is activated.
$ openpkg license list
- BOOT
- COMMUNITY
+ EVAL
- EXAMPLE
- PROMO
- RECOVERY

To view the human readable text of the EVAL license, run this command
$ openpkg license view EVAL

The EVAL license allows the framework to be run for 30 days after fresh install or upgrade from a OSS framework. When time is up, the framework will no longer work. To remedy the situation, switch to another license.

$ openpkg license install VALUE myvaluefile
$ openpkg license activate VALUE

Now to the explanations. Currently all license texts are at version 1.0.0 and they only differ in the text under the heading “GRANT OF RIGHTS TO USE THE OPENPKG FRAMEWORK” and some reference additional parameters which are carried in the same document.

Understand that a “LifeTime” assertion checks the real-time clock on the wall against a specified time-frame and a “GrantTime” assertion checks the release date recorded in the Framework against a specified time-frame.

  • VALUE

    The VALUE license is the most convenient one. It allows infinite run-time of the most recent framework release at the date of license issue. In addition, it allows the use of updated framework releases within the next year after the date of license issue. Finally it allows use of all previous framework releases with the same licensing concept. Note that past and future framework releases may not be able to use the license file for technical reasons. To protect the upgrade path, the issuer will re-issue a technically valid license file free of charge, if that is required. It is expected that the use of previous framework releases is exercised to extend, replace, reproduce an existing setup for which a technically valid license file is already available to the licensee. In this case, the new license is “paperwork” only, the issuer will not re-issue a technically valid file for past releases, and the licensee may technically “overbook” his existing old license.

    The VALUE license does not ship with the free download and can be purchased at the OpenPKG online shop (soon, in January 2010). One VALUE license is required “per kernel” running one or more OpenPKG frameworks.

    Before the times of isolation and virtualization, “per kernel” would have been identical to “per server” or “per metal”. The picky “per kernel” just clearly defines the scope within isolated and virtualized environments. Technologies where host and guest share the same kernel instantiation may also share a VALUE license, e.g. chroot, Solaris zones, FreeBSD jails, Parallels Virtuozzo Containers; In contrast, technologies where host and guest run different kernel instantiations require one VALUE license for every kernel, e.g. VMware Server/ Workstation/ Player, Citrix XenServer;

    Issued: 2010-01-01

    Quantity: 1

    This “value” license can be purchased from the OpenPKG GmbH and
    allows restricted use of the OpenPKG Framework. The constraints are
    use on no more kernels than quantified, see “Quantity” at the top of
    this document. As long as technically possible you are granted to
    use the license with any OpenPKG Framework released during a
    specified time frame, see “Assertion-GrantTime” at the bottom of
    this document. If this license is not compatible to an OpenPKG
    Framework released before this license was issued, see “Issued” at
    the top of this document, than you may reuse an existing license as
    a substitute. You must not expect the OpenPKG GmbH to issue an old
    license version. If this license is not compatible to an OpenPKG
    Framework released at or after the license was issued, and still
    within the specified time frame, you can assume the OpenPKG GmbH
    will issue a working license in exchange of this license. This
    effectively means to use the release current at the date of issue
    and some future updates, if available. The license does not impose
    any life-time limitation.

    Assertion-GrantTime: 2008-01-01:2010-12-31

  • BOOT

    This license is purely for internal use. The license processor is deeply integrated into RPM5 and there are some special cases during the bootstrap procedure where the licensing processor ought to work but the operator had no chance to install a valid license. The technical limitation is that no package but “openpkg” is allowed to be installed.

    This “bootstrap” license ships free of charge with every OpenPKG
    Framework and allows restricted use of the OpenPKG Framework. The
    constraint is a run-time limitation of the RPM database to contain
    only the “openpkg” package and GPG keys, a situation typical during
    and immediately after bootstrapping. The license does not impose
    any life-time limitation.

  • COMMUNITY

    The COMMUNITY license is available free of charge. It could have been called the “bleeding edge” or “source force” license. It is time-bombed, bound to a certain framework and includes a list of the most recent Open Source Packages. Only those OSS packages listed or newer can be run. The combination of being time-bombed, bound to a recent framework release and the inclusion of a recent OSS package list enforces the use of up-to-date software. It only allows installation of binary packages which have been built from source on the same host. It reports usage information online.

    This “community” license ships free of charge with every OpenPKG
    Framework and allows restricted use of the OpenPKG Framework. The
    constraints are run-time limitations of the OpenPKG Framework to
    enforce regular updates. The packages must have been built on the
    target host, inhibiting “build on one host, deploy on other host”
    scenarios. Online reporting is enabled. A large amount of
    packgages being installed must be known by name and release,
    preventing use of large amounts of outdated or modified packages.
    This is effectively a “force source” and “bleeding edge” license.

  • EVAL

    The EVAL license is the heart of the shareware approach. It ships with the framework and enables run-time for 30 days after installation. Then it’s time to decide whether some alternative license should be activated or the evaluation being discarded. Anyway, once the time is up, the framework ceases to work.

    This “evaluation” license ships free of charge with every OpenPKG
    Framework and allows restricted use of the OpenPKG Framework. The
    constraint is a run-time limitation after initial installation,
    see “Assertion-InstanceAge” at the bottom of this document. After
    that period the evaluation license is void and either must be
    replaced by another license or use of the OpenPKG Framework must be
    discontinued.

    Assertion-InstanceAge: 90d

  • EXAMPLE

    The EXAMPLE license is designed for preparing documentation, demos and trainings. It is limited to the hardcoded prefix “/example” and user/ group being “example”.

    This “example” license ships free of charge with every OpenPKG
    Framework and allows restricted use of the OpenPKG Framework. The
    constraints are the use in documentation, demonstration and training
    material only and the filesystem prefix, user and group
    parameters being locked to certain paramenters, see
    “Assertion-Prefix”, “Assertion-User” and “Assertion-Group” at the
    bottom of this document. The license does not impose any life-time
    limitation.

    Assertion-Prefix: /example
    Assertion-User: example
    Assertion-Group: example

  • PROMO

    The PROMO license is a gift from the OpenPKG GmbH marketing and may contain any feature, depending on the current department goal. The openpkg-4.0.0-20100101 framework ships with a time-bombed run-time based on real-time till 2010-02-01.

    This “promotion” license can be obtained from the OpenPKG GmbH
    and allows restricted use of the OpenPKG Framework. The constraints
    are the use of the OpenPKG Framework in a specified real-time frame,
    see “Assertion-LifeTime” at the bottom of this document, and use of
    the OpenPKG Framework released in a specified time frame, see
    “Assertion-GrantTime” at the bottom of this document.

    Assertion-LifeTime: 2008-01-01:2010-01-31
    Assertion-GrantTime: 2008-01-01:2010-01-31

  • RECOVERY

    The RECOVERY license is a helper when other licenses do work temporarily, most likely because some time restriction has passed by. While active, each and every internal “openpkg rpm” operation requires online approval. The usage is tracked and excessive consumption may lead to lock out. Also, if online access is not available or the recovery server is offline, this license is of no use.

    This “recovery” license ships free of charge with every OpenPKG
    Framework and allows temporary recovery from licensing issues.
    It requires online access to license clearing services from the
    OpenPKG GmbH which are not guaranteed to be available.

One Response to “OpenPKG 4.0 licenses explained”

  1. jmdesp Says:

    Would you consider updating the http://www.openpkg.org/documentation/faq/ page so that it corresponds to this new framework ?

    It’s not obvious for a newcomer that “openpkg license list” lists the already locally available licences, amongst which you can then switch with “openpkg license activate”.

    There seems to be something broken with the package browser, since, whilst it says it should be correct, “openpkg build gcc45″ fails, as well as “build gcc43″, “build gcc41″, “build gcc4″, “build gcc3″. Fortunately “openpkg build gcc” does build gcc 45 but I have no idea what I should do if I need another version. Maybe I missed something.

Leave a Reply