headers
Luke Kanies | 1 Apr 2008 05:00
Gravatar

[Puppet Users] Re: UPGRADE/DEPRECATED/ROADMAP document


On Mar 31, 2008, at 8:41 AM, Richard wrote:

>
> The UPGRADE document does a great job of listing the history, however
> I would like a bit more information on the future of Puppet.
> Specifically, I want to know about things that have been or are going
> to be deprecated.
>
> As I'm running Debian Etch and it includes Puppet v0.20.1 I am a
> little behind the current version of Puppet.  I can't really upgrade
> to a more current version without breaking my platform but at the same
> time I don't really want to use something that will be disabled in
> future versions if I can help it.  Things like libdir going away are
> buried in the middle of the document and extremely hard to find.  If
> we could have a list of deprecated things and/or a map of the future
> it would be very helpful.

I've built a first version of a Roadmap:

http://reductivelabs.com/trac/puppet/wiki/RoadMap

I don't know where the all-caps thing came from, but, uh, I'm not  
going to continue it.  Maybe it's from the files at the root of the  
repo?  Those should probably be changed, although some of them are  
pointed to by web sites and such.

There are no mentions of deprecations in this document.  In fact, it's  
really just a quick dash of what's in my head.  Hopefully I'll add  
things as I think of them, but, well, who knows?
(Continue reading)

Permalink | Reply | 4 comments |
headers
Blake Barnett | 1 Apr 2008 05:37
Picon

[Puppet Users] Re: UPGRADE/DEPRECATED/ROADMAP document


On Mar 31, 2008, at 8:00 PM, Luke Kanies wrote:

>
> On Mar 31, 2008, at 8:41 AM, Richard wrote:
>
>>
>> The UPGRADE document does a great job of listing the history, however
>> I would like a bit more information on the future of Puppet.
>> Specifically, I want to know about things that have been or are going
>> to be deprecated.
>>
>> As I'm running Debian Etch and it includes Puppet v0.20.1 I am a
>> little behind the current version of Puppet.  I can't really upgrade
>> to a more current version without breaking my platform but at the  
>> same
>> time I don't really want to use something that will be disabled in
>> future versions if I can help it.  Things like libdir going away are
>> buried in the middle of the document and extremely hard to find.  If
>> we could have a list of deprecated things and/or a map of the future
>> it would be very helpful.
>
> I've built a first version of a Roadmap:
>
> http://reductivelabs.com/trac/puppet/wiki/RoadMap
>
> I don't know where the all-caps thing came from, but, uh, I'm not
> going to continue it.  Maybe it's from the files at the root of the
> repo?  Those should probably be changed, although some of them are
> pointed to by web sites and such.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Luke Kanies | 1 Apr 2008 05:41
Gravatar

[Puppet Users] Re: UPGRADE/DEPRECATED/ROADMAP document


On Mar 31, 2008, at 10:37 PM, Blake Barnett wrote:

> Coming from the Rails world, I thought the deprecated plugin[1] was
> really helpful.  I'm sure the idea could be applied to puppet
> manifests and configs in some way...   I think it'd be useful if the
> tool is separate from any puppet release, and that it know about as
> old a version as is possible (maybe 0.20.x?).  Maybe when the tool is
> run it checks the current version, and then they can specify a target
> version (the one they want to upgrade to) and it spits out what will
> break between those releases.

This would be great.

Any volunteers?

--

-- 
Hanlon's razor:
     Never attribute to malice that which can adequately be explained by
     stupidity.
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users <at> googlegroups.com
To unsubscribe from this group, send email to puppet-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
(Continue reading)

Permalink | Reply | 2 comments |
headers
Blake Barnett | 1 Apr 2008 05:46
Picon

[Puppet Users] Re: UPGRADE/DEPRECATED/ROADMAP document


On Mar 31, 2008, at 8:41 PM, Luke Kanies wrote:

>
> On Mar 31, 2008, at 10:37 PM, Blake Barnett wrote:
>
>> Coming from the Rails world, I thought the deprecated plugin[1] was
>> really helpful.  I'm sure the idea could be applied to puppet
>> manifests and configs in some way...   I think it'd be useful if the
>> tool is separate from any puppet release, and that it know about as
>> old a version as is possible (maybe 0.20.x?).  Maybe when the tool is
>> run it checks the current version, and then they can specify a target
>> version (the one they want to upgrade to) and it spits out what will
>> break between those releases.
>
>
> This would be great.
>
> Any volunteers?

I suspect it'll be a whole lot of trial and error, especially with all  
the older versions.  I'm happy to help with writing the code for it if  
we can make it a collaborative effort with people testing different  
version combinations and reporting breakages.  I imagine there's a lot  
of hints in git history logs and tickets too.

-Blake

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Gunnar Wrobel | 1 Apr 2008 07:24

[Puppet Users] Re: Identifying the current version of an installed package


Hi Peter,

thanks for the reply.

On 31 Mrz., 22:07, Peter Meier <peter.me... <at> immerda.ch> wrote:
> Hi
>
> > I'm currently creating a puppet configuration repository for the Kolab
> > groupware server (http://kolab.org). As the server runs on a variety
> > of different platforms there exists a certain variability in the
> > versions of the server components. So I need to provide configurations
> > for different software versions and I'd like to be able to ask puppet
> > for the currently installed version.
>
> > What would be the best approach to do that?
>
> why not simply provide per distro (os) a specific config file, which
> means that you would automatically support only the latest version of
> the specific distro/os. So something like this:

This works rather well with distros like Debian where a single release
number indicates which software versions most of the installed
packages have.

With distros such as Gentoo it gets more complicated. There is no
single release version and users can have any package version
installed from a wide range of available package versions.

Of course you are right and I could just accept the latest available
(Continue reading)

Permalink | Reply | 1 comment |
headers
Gunnar Wrobel | 1 Apr 2008 07:25

[Puppet Users] Re: Identifying the current version of an installed package


Hi Blake,

On 31 Mrz., 22:07, Blake Barnett <sha... <at> gmail.com> wrote:
> On Mar 31, 2008, at 12:54 PM, Gunnar Wrobel wrote:
> <snip>
>
>
>
> > Is there a way to get a simple function for the task?
>
> Yup:http://reductivelabs.com/trac/puppet/wiki/WritingYourOwnFunctions
>
> -Blake

Okay, will try to do it that way :)

Thanks!

Gunnar
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users <at> googlegroups.com
To unsubscribe from this group, send email to puppet-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
Gunnar Wrobel | 1 Apr 2008 07:27

[Puppet Users] Re: Identifying the current version of an installed package


On 31 Mrz., 22:49, Luke Kanies <l... <at> madstop.com> wrote:
> On Mar 31, 2008, at 2:54 PM, Gunnar Wrobel wrote:
>
> >        $eix_out = generate('/usr/bin/eix', '--nocolor', '--format',
> > '"<installedversionsshort>"', '--pure-packages', '--exact', '--
> > category-name', 'net-nds/openldap')
>
> Note that this will only work if the server is also where you're
> running your software.  This command runs on the server, not on the
> client.
>

Right, I didn't really consider that yet. Currently I'm running in
client mode anyhow and I guess it will be client mode for most Kolab
users. Nevertheless I shouldn't loose sight of also allowing client/
master mode.

> The only way to get client information to the server is via facts.

Okay, I guess I'll have to investigate how I would get this done.

Thanks!

Gunnar

>
> --
> Football is a mistake. It combines the two worst elements of American
> life. Violence and committee meetings. -- George F. Will
(Continue reading)

Permalink | Reply | 1 comment |
headers
Blake Barnett | 1 Apr 2008 07:30
Picon

[Puppet Users] Re: Identifying the current version of an installed package


On Mar 31, 2008, at 10:27 PM, Gunnar Wrobel wrote:
> On 31 Mrz., 22:49, Luke Kanies <l... <at> madstop.com> wrote:
>> On Mar 31, 2008, at 2:54 PM, Gunnar Wrobel wrote:
>>
>>>       $eix_out = generate('/usr/bin/eix', '--nocolor', '--format',
>>> '"<installedversionsshort>"', '--pure-packages', '--exact', '--
>>> category-name', 'net-nds/openldap')
>>
>> Note that this will only work if the server is also where you're
>> running your software.  This command runs on the server, not on the
>> client.
>>
>
> Right, I didn't really consider that yet. Currently I'm running in
> client mode anyhow and I guess it will be client mode for most Kolab
> users. Nevertheless I shouldn't loose sight of also allowing client/
> master mode.
>
>> The only way to get client information to the server is via facts.
>
> Okay, I guess I'll have to investigate how I would get this done.

In case you hadn't seen this yet either:
http://reductivelabs.com/trac/puppet/wiki/AddingFacts

-Blake

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Francois Deppierraz | 1 Apr 2008 08:35
Picon

[Puppet Users] Re: AuthorizedKeys...Type?


David Schmitt wrote:

> Which is why I believe that with this syntax, the "comment" field is 
> superfluous. Writing the comment into the namevar will also make the 
> implementation much easier (see ParsedFile and friends).

That's a good point.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users <at> googlegroups.com
To unsubscribe from this group, send email to puppet-users-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
James Turnbull | 1 Apr 2008 11:49
Gravatar

[Puppet Users] Re: UPGRADE/DEPRECATED/ROADMAP document


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Blake Barnett wrote:
| I suspect it'll be a whole lot of trial and error, especially with all
| the older versions.  I'm happy to help with writing the code for it if
| we can make it a collaborative effort with people testing different
| version combinations and reporting breakages.  I imagine there's a lot
| of hints in git history logs and tickets too.

Happy to test if you write the code.

James Turnbull

- --
James Turnbull (james <at> lovedthanlost.net)
- --
Author of:
- - Pulling Strings with Puppet
(http://www.amazon.com/gp/product/1590599780/)
- - Pro Nagios 2.0
(http://www.amazon.com/gp/product/1590596099/)
- - Hardening Linux
(http://www.amazon.com/gp/product/1590594444/)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH8gUj9hTGvAxC30ARAiGiAKCHnHucXAtXK2PX+SdjIDRglW7mGQCeKxlr
(Continue reading)

Permalink | Reply | 0 comments |

Gmane