rmatte: That is the appropriate call for a component, but no a device unfortunately. I was told that I could use d.getStatus("/") to get device status, but it always seems to show up as "0", even when a device is actually down cluther: I see. So a device is contained within a DeviceClass, but it is not contained within a Location. A non-containing relation is a way to relate to other objects without making them live underneath you. A containing relation means that the objects contained within live HERE, and if they're deleted from this relation they are gone for good. Every object in Zope must have a single primary path where it lives. so I am still a bit foggy on the difference between a containing rel and non-containing rel. You want to avoid those if you can since they're harder to maintain. cluther: that is the other way I was thinking This would keep you from having to create a lot of non-containing relations. What if you started with VG had two relations on it: PV and LV. then what? LV then filesystem techically hdisk -> physical_volume(software_created) -> volume_group -> logical_volume -> filesystem even more technical lun-> lun_id -> vio -> vio_mapping -> hdisk. eg the physical volume What was the third type of object involved? You have VG and PV. cluther: oh wait cluther: say I have many pvs that go into one volume_group doing it this way will keep from creating multiple volume group objects of the same name right? eg hdisk2, hdisk3, hdisk4 all go to a datavg You are putting a vg relation right on the DeviceHW sub-class, right? yes there will be a relation for that on the physical volume sub-class a many to one relationship I am assuming container for the bottom level. but its nice to have confirmation There are a lot of ways to do it, but you seem to have hit upon the best one. and I would need to create those I am assuming but I can use the filesystem one as a template. but I would call the manage_add function from my subcomponent correct? Right. cluther: Hey Buddy cluther: quick question for ya cluther: I created modeler code to create nested dicts for this 2 level relationship stuff I am working on cluther: my question is for my custom function do I just need to create a manage_addfilesystem type method to create the new objects? and if thats the case where would I get the context information? rocket: The context is "here.relname" The context is the relation you're adding the object to. is chet around I have a quick 5 minute question to ask him regarding relationships I pinged him, I'll let you know Thanks thanks cluther What did I do? showed up? you not see my Skype? Oh. conf its just /etc/sudoers there's an Enterprise ZenPack for monitoring Xen oh yeah? hm i'll check it out mrayzenoss: ping. for the most part this is pretty basic stuff I'm aware that this is basic stuff I just haven't had much experience with sudo other than simply granting full access to whoever Title: AFP548 - Essential Sudoers (at found via a google search "sudoers group file access" depending on your platform, there may be a man page for just the conf file rocket : thanks, exactly what I need that said, I can't reach my Debian box to check eg man sudoers yup man nf No manual entry for nf ah that works does zen do anything special for XEN? i'll probably just add dom0 and the domU's as separate devices there is no. using the command visudo to edit the sudoers file rmatte: basically you put all the users in a group rmatte: assign the group the privledges you need by group I mean system group so I could specify the users group for instance? yes system groups (prefixed with '%') does that allow me to specify access to a specific command? or would everyone effectively have zenoss level access? rmatte: you then specify the command rmatte: that is just the user specification you are defining that has access to that command read the man page there are also examples in sudoers I'm reading the man page, it's a long manpage look at sudoers. Morning _ian_ hi all morning good morning good morning can anyone think of a way to allow regular users to execute 1 command only as Zenoss user? and it has to apply to all users, not just specific ones through a shell on the server? correct sudo? I have sudo installed, no idea how I'd go about doing this though you need to configure access in /etc/sudoers look at the man page rmatte: it is pretty simple if you read the man page for sudo.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |