[Pkg-puppet-devel] Multiple version of same module?

[Stig Sandbeck Mathisen]

Thomas Bechtold <thomasbechtold at jpberlin.de> writes:

> Hi,
>
> are there any opinions howto support/handle multiple versions of the
> same module?
> Currently there's a new release of puppetlabs-mysql[1] with the version
> 2.0.0. Many modules still depend on puppetlabs-mysql < 1.0.0 (ie
> puppetlabs-glance). I already filled bug reports to upgrade ie
> puppetlabs-glance to use the new api.
> Howto handle this for packages? Do we want to support multiple versions
> of the the same module?

Good questions. 

It is certainly possible. It may involve hard work and some swearing. It
may also be a good solution to not do it, and point at other tools. :)

The puppet master handles multiple versions of packages, just not in the
same environment.

The alternatives system we use now handles one of the directories on the
module path of the default environment.

There's nothing yet to prevent people from using the alternatives system
to install incompatible modules together.

Modules in the puppet forge are encouraged to use semantic versioning.
(http://docs.puppetlabs.com/puppet/3/reference/modules_publishing.html#a-note-on-semantic-versioning)
…which should make it possible to use ${modulename}${majorversion}
packages.

People who need to control multiple environments with different module
versions already have tools for this:

 * "librarian-puppet", one instance per environment.

 * "r10k" for many environments. (I use "r10k" myself)

However, I do not think either of these can use locally installed
modules as a source, which the packaged modules provide.

-- 
Stig Sandbeck Mathisen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20131020/8726c457/attachment.sig>