Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

volumeGroups relationships are missing #556

Open
Hemie143 opened this issue Sep 16, 2019 · 1 comment
Open

volumeGroups relationships are missing #556

Hemie143 opened this issue Sep 16, 2019 · 1 comment

Comments

@Hemie143
Copy link

The volumeGroups relationships are missing from a zenpacklib.device.

@ethirolle
Copy link

As explained in https://zenoss.zendesk.com/agent/#/tickets/156400:

I think what you are describing is not a defect in zenpacklib, but rather its expected behavior:

If your ActiveMQ devices are always Linux devices, and you always want to include all the relations and datasources of a normal Linux (SSH) device... then I think you can accomplish that by how you define the base class. I..e., by defining a new device class (e.g., "ActiveMQDevice"?), and setting its base to the Linux device class, I think you inherit all the Linux device relations/datasources/etc... and then you can use the YAML to add any additional relations, etc.

So for example, if you wish to create a new ActiveMQ device class (named "ActiveMQDevice") that "inherits" all the relations of a Linux device, I think you could do something like:

classes:
  ActiveMQDevice:
    base: [zenpacklib.Device, ZenPacks.zenoss.LinuxMonitor.LinuxDevice.LinuxDevice]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants