[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Antw: Cups Schema

Am 20.03.2014 08:30, schrieb Ulrich Windl:

Hi!

When you try to implement CUPS (which is one implemenation of IPP, BTW) in LDAP, you should consider the printer MIB (RFC 3805) for reference. That way your schema will be more univeral, I guess. Maybe you can even map the OIDs of the MIB into your OID-space.

That would be RFC3712 "(LDAP): Schema for Printer Services"
There was an unfinished discussion about this on a CUPS developer List (http://comments.gmane.org/gmane.comp.printing.cups.devel/4326) from July 2010. Conclusion: someone should develop "a patch to use the RFC 3712 schema as an option, or to provide a backend that does regular printer discovery using LDAP". 

I don't know if this has happened yet.

Cheers,

Peter



Regards,
Ulrich


"Borresen, John - 0442 - MITLL" <John.Borresen@ll.mit.edu> schrieb am

19.03.2014 um 22:01 in Nachricht
<201403192101.s2JL1mpv094150@boole.openldap.org>:

Hopefully, someone can point me in the correct direction.  Forgive me if
this falls into the category of "What is the color of George Washington's
white horse?" But, I want to do this in the correct way.

Using this schema:
# Definitions for a schema to store CUPS printer information in LDAP
# OID Base is iso(1) org(3) dod(6) internet(1) private(4) enterprise(1)
me(5323) cupsSchema(22)

# Syntaxes are under 1.3.6.1.4.1.5323.22.0
# Attributes are under 1.3.6.1.4.1.5323.22.1
# Object Classes are under 1.3.6.1.4.1.5323.22.2

attributetype ( 1.3.6.1.4.1.5323.22.1.1
        NAME 'printerDescription'
        DESC 'Description of Printer'
        EQUALITY caseExactMatch
        SINGLE-VALUE
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

attributetype ( 1.3.6.1.4.1.5323.22.1.2
        NAME 'printerURI'
        DESC 'CUPS style URI for printer'
        EQUALITY caseExactIA5Match
        SINGLE-VALUE
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 )

attributetype ( 1.3.6.1.4.1.5323.22.1.3
        NAME 'printerLocation'
        DESC 'Identifier string for Printer Location'
        EQUALITY caseExactMatch
        SINGLE-VALUE
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

attributetype ( 1.3.6.1.4.1.5323.22.1.4
        NAME 'printerMakeAndModel'
        DESC 'String CUPS uses to figure out driver'
        EQUALITY caseExactMatch
        SINGLE-VALUE
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

attributetype ( 1.3.6.1.4.1.5323.22.1.5
        NAME 'printerType'
        DESC 'Integer CUPS uses to figure out type'
        EQUALITY integerMatch
        SINGLE-VALUE
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 )

objectclass ( 1.3.6.1.4.1.5323.22.2.1
     NAME 'cupsPrinter'
   SUP top
        AUXILIARY
        MUST ( printerDescription $ printerURI $ printerLocation $
printerMakeAndModel $ printerType ) )


There is no Structural ObjectClass defined specifically in this schema.
Would I use the same ObjectClass as I used to define Hosts, it is a network
device.

Thanks,

John D. Borresen (Dave)
Linux/Unix Systems Administrator
MIT  Lincoln Laboratory
Surveillance Systems Group
244 Wood St
Lexington, MA  02420
Email: john.borresen@ll.mit.edu







--

Peter Gietz, CEO

DAASI International GmbH
Europaplatz 3
D-72072 Tübingen
Germany

phone: +49 7071 407109-0
fax:   +49 7071 407109-9
email: peter.gietz@daasi.de
web:   www.daasi.de

Sitz der Gesellschaft: Tübingen
Registergericht: Amtsgericht Stuttgart, HRB 382175
Geschäftsleitung: Peter Gietz