Differences

This shows you the differences between two versions of the page.

--- devel:blueprints:ipdevpoll [2009/07/13 14:20] – klette
+++ devel:blueprints:ipdevpoll [2012/05/07 11:26] (current) – fix url morten
@@ Line 43: / Line 43: @@
 Data is provided through the use of shadow-classes of django-models. Plugins never write django-objects directly. This is handled by the job the plugin runs in at the end of each job.
-Shadow-classes are created in ''nav.ipdevpoll.storage''
+Shadow-classes are created in ''nav.ipdevpoll.shadows''
 \\
 Example shadowclass specification
@@ Line 76: / Line 76: @@
 Deletion of objects in the database is done if the shadowobject has its
 ''delete''-property set to True.
+Once the job is done the storage routine is called. The storage system then parses all
+the shadow objects contained in ''job_handler.container'' and make s sure all foreignkeys needed for the storing
+an instance are saved before the object it self.
 ==== Plugins ====
@@ Line 189: / Line 193: @@
 === Implemented plugins ===
-Already implemented plugins can be found on [[devel:ipdevpollplugins]]
+Already implemented plugins can be found on [[devel:ipdevpoll:plugins]]
 ===== Database changes =====
@@ Line 207: / Line 211: @@
 The IF-MIB has no concept of an interface/module relationship.  Information about such a relationship will most likely come from proprietary MIBs (or possibly a properly populated ENTITY-MIB), and should be treated as a bonus if found.  Ie. NAV's model should add to the interface table a mandatory foreign key to netbox,  and only an optional foreign key into the module table.
-===== Code =====
+===== Status =====
-The mercurial repositories can be found at http://metanav.uninett.no/hg/features/ipdevpoll/
+The first NAV release to include ipdevpoll was version 3.6.
 ===== References =====