Puppet

Davor Ocelic wrote:

It’s not that current fake OIDs are terribly wrong, but we have the chance to use proper ones.

The OIDs contained in the patch are from a block assigned to my company Spinlock Solutions (http://www.spinlocksolutions.com/), they’re valid, and I reasonably guarantee that they can be uniquely used for this purpose, and won’t be reused for other elements.

Not that I’m against your patch, but maybe Reductive Labs could ask to the IANA for an enterprise number as they qualify. It’s free and reasonably fast to get one (at least it was back in 2002 when I get ours). So you won’t have to “lend” your own space for a product not belonging to your own company :–)

Note to RL staff, see there for the application form: http://pen.iana.org/pen/PenApplication.page

That’s alright as well, but I wondered why they didn’t do it already :)

When you get the PEN, just replace all occurrences of “30977” in the patch file with the respective new PEN. Other numbers stay as they are.

Getting the PEN is still relatively fast, I think I got mine in 4 or 5 days, 2 years ago.

Cya, -doc

Luke – I forwarded you the pull request for this a little while ago. We’ve discussed this before so up to you.

I’ve submitted for a number, and if it’s that easy, I’ll just wait until that number shows up.

It took about two months to get ours, with pinging IANA two times about it. Just don’t give up if it takes a while :–)

Attached is also another patch which properly capitalizes puppetclass, parentnode and puppetvar. Currently they’re all lowercase, while they should be puppetClass, parentNode and puppetVar.

This isn’t very important per-se since ldap is case-insensitive (as far as attribute names go), but it does always return the attribute names in their original form and capitalization.

So when those attributes are used as variables in ERB templates, their capitalization is important, because puppetclass != puppetClass. All other attributes coming from LDAP do use proper capitalization, so it’s best to adjust this for uniformity.

The second patch is a good idea; thanks.

We’ve got an OID: 34380.

Don’t see why this can’t go straight into .2 – it’s not really a new feature.

Pushed in commit:“bf7c108825ffdb5ea89cf3e500d55d27ab64b8d2” in branch 0.25.x