AccessControl.Role.RoleManager:
An object that has configurable permissions
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathManager:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
DocumentTemplate.DT_String.String:
Document templates defined from strings.
DocumentTemplate.DT_HTML.HTML:
HTML Document Templates
HTML Document templates use HTML server-side-include syntax,
rather than Python format-string syntax.
DocumentTemplate.DT_HTML.HTMLFile:
HTML Document templates read from files.
App.special_dtml.ClassicHTMLFile:
Persistent HTML Document Templates read from files
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
Products.ZenRelations.ZItem.ZItem:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathManager:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
Products.ZenRelations.ZenPropertyManager.ZenPropertyManager:
ZenPropertyManager adds keyedselection type to
PropertyManager.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
Products.ZCatalog.CatalogAwareness.CatalogAware:
This is a Mix-In class to make objects automaticly catalog and
uncatalog themselves in Zope, and to provide some other basic
attributes that are useful to catalog.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.PerformanceView.PerformanceView:
Mixin to provide hooks to performance management functions which
allow targetmap management and graphing configuration generation is
in PerformanceDevice and PerformanceServer
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
logging.Filter:
Filter instances are used to perform arbitrary filtering of
LogRecords.
logging.Filterer:
A base class for loggers and handlers which allows them to share
common code.
logging.Handler:
Handler instances dispatch logging events to specific
destinations.
logging.StreamHandler:
A handler class which writes logging records, appropriately
formatted, to a stream.
logging.FileHandler:
A handler class which writes formatted logging records to disk
files.
logging.Logger:
Instances of the Logger class represent a single logging
channel.
logging.RootLogger:
A root logger is not that different to any other logger, except
that it must have a logging level and there is only one instance of
it in the hierarchy.
logging.Formatter:
Formatter instances are used to convert a LogRecord to text.
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.ZenStatus.YearlyDownTime:
this would take less space as a dict with but it would take
longer to query not sure which is better going with faster and
bigger :)
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
_random.Random:
Random() -> create a random number generator with its own
internal state.
random.Random:
Random number generator base class used by bound module
functions.
random.SystemRandom:
Alternate random number generator using sources provided
by the operating system (such as /dev/urandom on Unix or
CryptGenRandom on Windows).
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
Products.ZenRelations.ZItem.ZItem:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathManager:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
Products.ZenRelations.ZItem.ZItem:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathManager:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
Products.ZenRelations.ZenPropertyManager.ZenPropertyManager:
ZenPropertyManager adds keyedselection type to
PropertyManager.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
App.Undo.UndoSupport:
Standard ExtensionClass base type
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
OFS.CopySupport.CopyContainer:
Interface for containerish objects which allow
cut/copy/paste
Products.ZenRelations.RelCopySupport.RelCopyContainer:
Interface for containerish objects which allow
cut/copy/paste
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
OFS.CopySupport.CopySource:
Interface for objects which allow themselves to be copied.
Products.ZenRelations.ZItem.ZItem:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathManager:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
ZenEvents.EventDetail.Implicit:
Base class for objects that implicitly acquire attributes from
containers
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathManager:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
AccessControl.Owned.Owned:
Standard ExtensionClass base type
Products.ZenRelations.ZItem.ZItem:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathManager:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
ZenModel.ZenStatus.YearlyDownTime:
this would take less space as a dict with but it would take
longer to query not sure which is better going with faster and
bigger :)
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
AccessControl.Role.RoleManager:
An object that has configurable permissions
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathManager:
A common base class for simple, non-container objects.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenUtils.ZenDocTest.ZenDocTestRunner:
Extracts doctests from the docstrings of a Zenoss module
and runs them in an environment similar to that of zendmd.
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
twisted.internet.protocol.AbstractDatagramProtocol:
Abstract protocol for datagram-oriented transports, e.g.
twisted.internet.protocol.DatagramProtocol:
Protocol for datagram-oriented transport, e.g.
twistedsnmp.snmpprotocol.SNMPProtocol:
Base class for SNMP datagram protocol
attributes:
requests -- dictionary holding request-key: df,timer
where request-keys are calculated by our getRequestKey
method, df is the defer for callbacks to the request,
and timer is the timeout timer for the request.
Products.ZenRelations.PrimaryPathObjectManager.PrimaryPathObjectManager:
PrimaryPathObjectManager with basic Zope persistent classes.
ZenModel.ZenModelRM.RelationshipManager:
RelationshipManger is an ObjectManager like class that can contain
relationships (in fact relationships can only be added to a
RelationshipManager).
ZenModel.Device.Device:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.TerminalServer.TerminalServer:
Device is a base class that represents the idea of a single
computer system that is made up of software running on
hardware.
ZenModel.System.System:
System class is a device organizer that represents a business
system.
ZenModel.DeviceClass.DeviceClass:
DeviceClass is a device organizer that manages the primary
classification of device objects within the zenoss system.
ZenWidgets.Portlet.Portlet:
A wrapper for a portlet javascript source file that can include
metadata such as a name, a title, a description and
permissions.