Hello,
I added an Openstack device on Zencore 4.2.5, inputted the my credentials to the cloud network.
The Zencore platform did recognise my cloud device but it couldn't retrieve the flavors, servers and images I have on the cloud. this is what the log says:

INFO zen.Job: Job ee4a1e61-2e94-43e8-890e-b8770c3d44a9 (Products.ZenModel.ZDeviceLoader.DeviceCreationJob) received

INFO zen.Job: Beginning job Add Device Products.ZenModel.ZDeviceLoader.DeviceCreationJob

INFO zen.Job: Running Job Add Device Products.ZenModel.ZDeviceLoader.DeviceCreationJob

INFO zen.Job: Spawning subprocess: /usr/local/zenoss/bin/zendisc run --now -d 192.168.7.58 --monitor localhost --deviceclass /Devices/OpenStack --prod_state 1000 --job ee4a1e61-2e94-43e8-890e-b8770c3d44a9

INFO zen.ZenDisc: Connecting to localhost:8789

INFO zen.ZenDisc: Connected to ZenHub

2014-08-04 23:32:11,245 INFO zen.ZenDisc: Looking for 194.18.7.18

2014-08-04 23:32:49,629 INFO zen.ZenDisc: Result: Discovered device 194.18.7.18

2014-08-04 23:32:51,416 INFO zen.ZenDisc: No WMI plugins found for 194.18.7.18

2014-08-04 23:32:51,437 INFO zen.ZenDisc: Python collection device 194.18.7.18

2014-08-04 23:32:51,438 INFO zen.ZenDisc: plugins: zenoss.OpenStack

2014-08-04 23:32:51,439 INFO zen.OpenStack: Requesting flavors

2014-08-04 23:32:51,439 ERROR zen.ZenDisc: Unable to fill collection slots: [Failure instance: Traceback (failure with no frames): <type 'exceptions.AttributeError'>: 'Client' object has no attribute 'flavors'

]

2014-08-04 23:35:50,585 WARNING zen.ZenDisc: Client 194.18.7.18 timeout

2014-08-04 23:35:50,585 INFO zen.ZenDisc: Scan time: 180.96 seconds

2014-08-04 23:35:50,680 INFO zen.ZenDisc: Daemon ZenDisc shutting down

Am I doing something wrong?

Thanks

I was hoping to monitor the servers I created on the cloud platform but unfortunately, whenever I select on any of the servers/images or flavors created, the display graph section keeps loading only to end-up displaying no graph. Please what can I possibly do to sort out this issue? Thanks

I was testing out if Zenoss could pick up live migration events and update the instances just like instance state change events, but this was not working.

I found the issue to be in events.py :

# Note: I do not currently have good test data for what a real
# live migration looks like.  I am assuming that the new host will be
# carried in the last event, and only processing that one.
'openstack|compute.instance.live_migration.pre.start': (instance_id, None),
'openstack|compute.instance.live_migration.pre.end': (instance_id, None),
'openstack|compute.instance.live_migration.post.dest.start': (instance_id, None),
'openstack|compute.instance.live_migration.post.dest.end':  (instance_id, None),
'openstack|compute.instance.live_migration._post.start':  (instance_id, None),
'openstack|compute.instance.live_migration._post.end': (instance_id, instance_update),

openstack|compute.instance.live_migration.post.dest.end should be used instead, while also removing instance_update from openstack|compute.instance.live_migration._post.end:

'openstack|compute.instance.live_migration.pre.start': (instance_id, None),
'openstack|compute.instance.live_migration.pre.end': (instance_id, None),
'openstack|compute.instance.live_migration.post.dest.start': (instance_id, None),
'openstack|compute.instance.live_migration.post.dest.end':  (instance_id, instance_update),
'openstack|compute.instance.live_migration._post.start':  (instance_id, None),
'openstack|compute.instance.live_migration._post.end': (instance_id, None),

After this change, the instance's hostname will effectively change after approximately 30 seconds when the live migration has finished.

Having a similar set of attributes as those in euca-describe-instances command's output is quite useful.

e.g.

euca-describe-instances

RESERVATION r-4sq6z15s myproj default
INSTANCE i-00000018 ami-00000002 192.168.0.12 192.168.0.12 running $KEYNAME ($PROJECT_NAME, $HOST) 0

or like nova-manage output:

nova-manage vm list

instance node type state launched image kernel ramdisk project user zone index
server-12 $HOST m1.small active 2011-10-12 08:54:08 2 1 $PROJECT_NAME novaadmin $ZONE 0

Good morning,

Would it be possible to add functionality to show a list of all hypervisors and monitor services on those hypervisors (for instance, 'nova-compute')?

The nova command line has these capabilities through nova hypervisor-list and nova service-list.

I don't know if you designed this as an OpenStack admin or an end user. Coming from the administration viewpoint, details like this make it a lot easier.

Thank you!

Hi,

When attempting to model my environment I get the following error

2013-12-18 04:31:56,301 ERROR zen.ZenModeler: Traceback (most recent call last):
File "/opt/zenoss/Products/DataCollector/zenmodeler.py", line 647, in processClient
datamaps = plugin.process(device, results, self.log)
File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.OpenStack-1.2.0dev-py2.7.egg/ZenPacks/zenoss/OpenStack/modeler/plugins/zenoss/OpenStack.py", line 77, in process
flavorId=int(flavor.id), # 1
ValueError: invalid literal for int() with base 10: '41214c13-e0a8-4044-ab06-786855e2ec1a'

This is because the code assumes flavor.id will always be an int. While the default flavors added by openstack are integers, and extra ones added through openstack tools get created with a uuid instead. The plugin needs to be updated to handle this.

Thanks in advance,

Graeme

Hi, I'm trying to install this plug-in into my Zenoss. However, I have some problem that every time I try to install it, there will return an error:

Traceback (most recent call last):
File "/usr/local/zenoss/zenoss/Products/ZenUtils/zenpack.py", line 21, in
import Globals
File "/usr/local/zenoss/python/lib/python2.6/site-packages/Zope2-2.12.1-py2.6-linux-x86_64.egg/Globals/init.py", line 74, in
from App.ProductContext import ProductContext
File "/usr/local/zenoss/python/lib/python2.6/site-packages/Zope2-2.12.1-py2.6-linux-x86_64.egg/App/ProductContext.py", line 23, in
from AccessControl.Permission import registerPermissions
File "/usr/local/zenoss/python/lib/python2.6/site-packages/Zope2-2.12.1-py2.6-linux-x86_64.egg/AccessControl/init.py", line 16, in
from AccessControl.Implementation import setImplementation
File "/usr/local/zenoss/python/lib/python2.6/site-packages/Zope2-2.12.1-py2.6-linux-x86_64.egg/AccessControl/Implementation.py", line 101, in
setImplementation("C")
File "/usr/local/zenoss/python/lib/python2.6/site-packages/Zope2-2.12.1-py2.6-linux-x86_64.egg/AccessControl/Implementation.py", line 56, in setImplementation
from AccessControl import ImplPython as impl
File "/usr/local/zenoss/python/lib/python2.6/site-packages/Zope2-2.12.1-py2.6-linux-x86_64.egg/AccessControl/ImplPython.py", line 37, in
from AccessControl.unauthorized import Unauthorized
File "/usr/local/zenoss/python/lib/python2.6/site-packages/Zope2-2.12.1-py2.6-linux-x86_64.egg/AccessControl/unauthorized.py", line 16, in
import zExceptions
File "/usr/local/zenoss/python/lib/python2.6/site-packages/Zope2-2.12.1-py2.6-linux-x86_64.egg/zExceptions/init.py", line 26, in
from zope.publisher.interfaces import INotFound
File "/usr/local/zenoss/lib/python/zope/publisher/interfaces/init.py", line 26, in
from zope.security.interfaces import IParticipation
File "/usr/local/zenoss/lib/python/zope/security/init.py", line 17, in
from zope.security.management import checkPermission
File "/usr/local/zenoss/lib/python/zope/security/management.py", line 20, in
from zope.security import interfaces
File "/usr/local/zenoss/lib/python/zope/security/interfaces.py", line 19, in
from zope.schema import Text, TextLine
File "/usr/local/zenoss/lib/python/zope/schema/init.py", line 16, in
from zope.schema._field import Field, Container, Iterable, Orderable
File "/usr/local/zenoss/lib/python/zope/schema/_field.py", line 53, in
from zope.schema.vocabulary import getVocabularyRegistry
File "/usr/local/zenoss/lib/python/zope/schema/vocabulary.py", line 19, in
from ordereddict import OrderedDict
ImportError: No module named ordereddict

I assume that this is because some kind of Python version problem maybe? Could you give some advices on how to solve it please?

Thank you!

Hi all,

I met a problem when Adding Openstack endpoint (Infrastructure)

The ZenPacks I installed is ZenPacs.zenoss.OpenStackInfrastructure-2.4.2, Zenoss.core is 6.2.1, Zenoss Control Center is 1.6.2

The error message show "KeystoneERROR unauthorizedERROR: 401 Unauthorized (check username and password)"

I'm sure that username and password are correct,
because I write a python script, try to get keystone token, and the python script run success.

Receiving the following output when attempting to model a Diablo cloud.

2011-11-01 11:49:12,410 INFO zen.ZenDisc: Python collection device cloud.example.com
2011-11-01 11:49:12,410 INFO zen.ZenDisc: plugins: zenoss.OpenStack
2011-11-01 11:49:12,411 INFO zen.OpenStack: Requesting flavors
2011-11-01 11:49:12,562 INFO zen.OpenStack: Requesting images
2011-11-01 11:49:12,676 INFO zen.OpenStack: Requesting servers
2011-11-01 11:49:12,805 INFO zen.PythonClient: Python client finished collection for cloud.example.com
2011-11-01 11:49:12,841 ERROR zen.ZenDisc: Problem while executing plugin zenoss.OpenStack
2011-11-01 11:49:12,842 ERROR zen.ZenDisc: Traceback (most recent call last):
  File "/usr/local/zenoss/zenoss/Products/DataCollector/zenmodeler.py", line 623, in processClient
    datamaps = plugin.process(device, results, self.log)
  File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.OpenStack-1.0.2-py2.6.egg/ZenPacks/zenoss/OpenStack/modeler/plugins/zenoss/OpenStack.py", line 94, in process
    serverBackupEnabled=server.backup_schedule.enabled, # False
  File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.OpenStack-1.0.2-py2.6.egg/ZenPacks/zenoss/OpenStack/lib/python_novaclient-2.4.2-py2.6.egg/novaclient/servers.py", line 157, in backup_schedule
    return self.manager.api.backup_schedules.get(self)
  File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.OpenStack-1.0.2-py2.6.egg/ZenPacks/zenoss/OpenStack/lib/python_novaclient-2.4.2-py2.6.egg/novaclient/backup_schedules.py", line 73, in get
    'backupSchedule')
  File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.OpenStack-1.0.2-py2.6.egg/ZenPacks/zenoss/OpenStack/lib/python_novaclient-2.4.2-py2.6.egg/novaclient/base.py", line 51, in _get
    resp, body = self.api.client.get(url)
  File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.OpenStack-1.0.2-py2.6.egg/ZenPacks/zenoss/OpenStack/lib/python_novaclient-2.4.2-py2.6.egg/novaclient/client.py", line 89, in get
    return self._cs_request(url, 'GET', **kwargs)
  File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.OpenStack-1.0.2-py2.6.egg/ZenPacks/zenoss/OpenStack/lib/python_novaclient-2.4.2-py2.6.egg/novaclient/client.py", line 76, in _cs_request
    **kwargs)
  File "/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.OpenStack-1.0.2-py2.6.egg/ZenPacks/zenoss/OpenStack/lib/python_novaclient-2.4.2-py2.6.egg/novaclient/client.py", line 62, in request
    raise exceptions.from_response(resp, body)
NotFound: n/a (HTTP 404)

2012-10-09 00:23:12,792 INFO zen.OpenStack: Linking poll_openstack.py plugin into $ZENHOME/libexec/
ln: creating symbolic link /usr/local/zenoss/zenoss/libexec/poll_openstack.py': No such file or directory chmod: cannot access/usr/local/zenoss/zenoss/libexec/poll_openstack.py': No such file or directory

(I have no /usr/local/zenoss/zenoss/libexec directory at all)

Zenoss Zenoss 3.2.1
OS Linux (x86_64) 3.0.0 (Linux monvm04 3.0.0-16-virtual #28-Ubuntu SMP Fri Jan 27 18:22:35 UTC 2012 x86_64)
Zope Zope 2.12.1
Python Python 2.6.2
Database MySQL 5.0.45 (Ver 5.0.45)
RRD RRDtool 1.3.9
Twisted Twisted 8.1.0
NetSnmp NetSnmp 5.4.1
PyNetSnmp PyNetSnmp 0.29.13
WMI Wmi 1.3.13

locate poll_openstack.py
/home/zenoss/ZenPacks.zenoss.OpenStack/build/lib/ZenPacks/zenoss/OpenStack/poll_openstack.py
/home/zenoss/ZenPacks.zenoss.OpenStack/ZenPacks/zenoss/OpenStack/poll_openstack.py
/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.OpenStack-1.1.4-py2.6.egg/ZenPacks/zenoss/OpenStack/poll_openstack.py
/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.zenoss.OpenStack-1.1.4-py2.6.egg/ZenPacks/zenoss/OpenStack/poll_openstack.pyc

creating the /usr/local/zenoss/zenoss/libexec directory seems to fix the issue, but the zenpack should handle this situation gracefully

Hello

I was wondering if you are working on adding Cinder monitoring support to this ZenPack? I was browsing around and found this commit, which seems it's adding some Cinder capabilities but I am not sure.

Getting "Invalid client version ''" when trying to add an Icehouse env (2014.1.1) on the latest stable ZenPack (1.2.2) on Zenoss 4.2.4

[zenoss@zenoss bin]$ zencommand run -v10 --showfullcommand --showrawresults --device=23.108.36.162
2014-09-04 14:50:39,345 DEBUG zen.zencommand: Starting PBDaemon initialization
2014-09-04 14:50:39,345 INFO zen.zencommand: Connecting to localhost:8789
2014-09-04 14:50:39,347 DEBUG zen.pbclientfactory: Starting connection...
2014-09-04 14:50:39,347 DEBUG zen.zencommand: Logging in as admin
2014-09-04 14:50:39,348 DEBUG zen.pbclientfactory: Connected
2014-09-04 14:50:39,348 DEBUG zen.pbclientfactory: Cancelling connect timeout
2014-09-04 14:50:39,348 DEBUG zen.pbclientfactory: Sending credentials
2014-09-04 14:50:39,351 DEBUG zen.pbclientfactory: Cancelling connect timeout
2014-09-04 14:50:39,351 INFO zen.zencommand: Connected to ZenHub
2014-09-04 14:50:39,352 DEBUG zen.zencommand: Setting up initial services: EventService, Products.ZenHub.services.CommandPerformanceConfig
2014-09-04 14:50:39,352 DEBUG zen.zencommand: Chaining getInitialServices with d2
2014-09-04 14:50:39,352 DEBUG zen.pbclientfactory: pinging perspective
2014-09-04 14:50:39,355 DEBUG zen.zencommand: Loaded service EventService from zenhub
2014-09-04 14:50:39,355 DEBUG zen.zencommand: Loaded service Products.ZenHub.services.CommandPerformanceConfig from zenhub
2014-09-04 14:50:39,356 DEBUG zen.zencommand: Queued event (total of 1) {'rcvtime': 1409867439.355932, 'severity': 0, 'component': 'zencommand', 'agent': 'zencommand', 'summary': 'started', 'manager': 'zenoss.ubiquityservers.com', 'device': 'localhost', 'eventClass': '/App/Start', 'monitor': 'localhost'}
2014-09-04 14:50:39,356 DEBUG zen.zencommand: Sending 1 events, 0 perf events, 0 heartbeats
2014-09-04 14:50:39,357 DEBUG zen.zencommand: Calling connected.
2014-09-04 14:50:39,357 DEBUG zen.collector.config: Heartbeat timeout set to 900s
2014-09-04 14:50:39,357 DEBUG zen.collector.scheduler: add task configLoader, <Products.ZenCollector.config.ConfigurationLoaderTask object at 0x5a982d0> using 1200 second interval
2014-09-04 14:50:39,358 DEBUG zen.zencommand: Performing periodic maintenance
2014-09-04 14:50:39,358 DEBUG zen.pbclientfactory: perspective ponged
2014-09-04 14:50:39,358 DEBUG zen.pbclientfactory: Cancelling ping timeout
2014-09-04 14:50:39,359 DEBUG zen.collector.scheduler: Task configLoader starting on 1200 second intervals
2014-09-04 14:50:39,359 DEBUG zen.collector.scheduler: Task configLoader changing state from IDLE to QUEUED
2014-09-04 14:50:39,361 DEBUG zen.collector.scheduler: Task configLoader changing state from QUEUED to RUNNING
2014-09-04 14:50:39,361 DEBUG zen.collector.config: configLoader gathering configuration
2014-09-04 14:50:39,361 DEBUG zen.collector.config: Fetching daemon configuration properties
2014-09-04 14:50:39,382 DEBUG zen.collector.scheduler: Task configLoader changing state from RUNNING to FETCHING_MISC_CONFIG
2014-09-04 14:50:39,382 DEBUG zen.zencommand: Updated configCycleInterval preference to 360
2014-09-04 14:50:39,382 DEBUG zen.zencommand: Changing config task interval from 20 to 360 minutes
2014-09-04 14:50:39,382 DEBUG zen.collector.scheduler: Stopping task configLoader, <Products.ZenCollector.config.ConfigurationLoaderTask object at 0x5a982d0>
2014-09-04 14:50:39,382 DEBUG zen.collector.scheduler: call finished LoopingCall<1200>(CallableTask: configLoader, (), *{}) : LoopingCall<1200>(CallableTask: configLoader, (), *{})
2014-09-04 14:50:39,383 INFO zen.collector.scheduler: Detailed Task Statistics:
configLoader Current State: FETCHING_MISC_CONFIG Successful_Runs: 1 Failed_Runs: 0 Missed_Runs: 0

Detailed Task States:
configLoader State: RUNNING Total: 1 Total Elapsed: 0.0206 Min: 0.0206 Max: 0.0206 Mean: 0.0206 StdDev: 0.0000
configLoader State: QUEUED Total: 1 Total Elapsed: 0.0024 Min: 0.0024 Max: 0.0024 Mean: 0.0024 StdDev: 0.0000

2014-09-04 14:50:39,383 DEBUG zen.collector.config: Heartbeat timeout set to 900s
2014-09-04 14:50:39,383 DEBUG zen.collector.scheduler: add task configLoader, <Products.ZenCollector.config.ConfigurationLoaderTask object at 0x5a98050> using 21600 second interval
2014-09-04 14:50:39,384 DEBUG zen.zencommand: Updated defaultRRDCreateCommand preference to ('RRA:AVERAGE:0.5:1:600', 'RRA:AVERAGE:0.5:6:600', 'RRA:AVERAGE:0.5:24:600', 'RRA:AVERAGE:0.5:288:600', 'RRA:MAX:0.5:6:600', 'RRA:MAX:0.5:24:600', 'RRA:MAX:0.5:288:600')
2014-09-04 14:50:39,384 DEBUG zen.collector.config: Fetching threshold classes
2014-09-04 14:50:39,390 DEBUG zen.zencommand: Loading classes ['Products.ZenModel.MinMaxThreshold', 'Products.ZenModel.ValueChangeThreshold']
2014-09-04 14:50:39,391 DEBUG zen.collector.config: Fetching collector thresholds
2014-09-04 14:50:39,629 DEBUG zen.thresholds: Updating threshold ('high event queue', ('localhost collector', ''))
2014-09-04 14:50:39,629 DEBUG zen.thresholds: Updating threshold ('zenmodeler cycle time', ('localhost collector', ''))
2014-09-04 14:50:39,629 DEBUG zen.collector.config: Fetching configurations
2014-09-04 14:50:39,692 DEBUG zen.zencommand: updateDeviceConfigs: updatedConfigs=['23.108.36.162']
2014-09-04 14:50:39,693 DEBUG zen.zencommand: Processing configuration for 23.108.36.162
2014-09-04 14:50:39,693 DEBUG zen.daemon: DummyListener: configuration 23.108.36.162 added
2014-09-04 14:50:39,693 DEBUG zen.collector.tasks: Splitting config 23.108.36.162
2014-09-04 14:50:39,694 DEBUG zen.zencommand: Tasks for config 23.108.36.162: {'23.108.36.162 300 Local': <main.SshPerformanceCollectionTask object at 0x60236d0>}
2014-09-04 14:50:39,694 DEBUG zen.collector.scheduler: add task 23.108.36.162 300 Local, COMMAND schedule Name: 23.108.36.162 300 Local configId: 23.108.36.162 Datasources: 1 using 300 second interval
2014-09-04 14:50:39,694 DEBUG zen.collector.scheduler: Task 23.108.36.162 300 Local starting on 300 second intervals
2014-09-04 14:50:39,695 DEBUG zen.collector.scheduler: Task 23.108.36.162 300 Local changing state from IDLE to QUEUED
2014-09-04 14:50:39,695 DEBUG zen.zencommand: purgeOmittedDevices: deletedConfigs=
2014-09-04 14:50:39,695 DEBUG zen.collector.scheduler: Task configLoader finished, result: 'Configuration loaded'
2014-09-04 14:50:39,696 DEBUG zen.collector.scheduler: Task 23.108.36.162 300 Local changing state from QUEUED to RUNNING
2014-09-04 14:50:39,696 DEBUG zen.zencommand: Running command(s) locally
2014-09-04 14:50:39,696 DEBUG zen.collector.scheduler: Task 23.108.36.162 300 Local changing state from RUNNING to FETCH_DATA
2014-09-04 14:50:39,696 INFO zen.zencommand: Datasource OpenStackEndpoint/openstack command: $ZENHOME/libexec/poll_openstack.py 'admin' '$KEY' 'd889d9097f38460da6340cc4e69c5110' 'http://23.108.36.162:5000/v2.0' '' 'RegionOne'
2014-09-04 14:50:39,696 DEBUG zen.zencommand: Running $ZENHOME/libexec/poll_openstack.py
2014-09-04 14:50:40,235 DEBUG zen.zencommand: Datasource: openstack Received exit code: 0 Output:
'{"events": [{"eventClassKey": "openStackFailure", "summary": "OpenStack failure: Invalid client version ''. must be one of: 3, 2, 1.1", "severity": 5, "eventKey": "openStackFailure"}]}\n'
2014-09-04 14:50:40,235 DEBUG zen.zencommand: Process OpenStackEndpoint/openstack stopped (0), 0.53 seconds elapsed
2014-09-04 14:50:40,235 DEBUG zen.collector.scheduler: Task 23.108.36.162 300 Local changing state from FETCH_DATA to PARSING_DATA
2014-09-04 14:50:40,236 DEBUG zen.collector.scheduler: Task 23.108.36.162 300 Local changing state from PARSING_DATA to STORE_PERF_DATA
2014-09-04 14:50:40,237 DEBUG zen.zencommand: Queued event (total of 1) {'rcvtime': 1409867440.237171, 'severity': 5, 'eventClassKey': u'openStackFailure', 'agent': 'zencommand', 'summary': u"OpenStack failure: Invalid client version ''. must be one of: 3, 2, 1.1", 'manager': 'zenoss.ubiquityservers.com', 'eventKey': u'openStackFailure', 'device': '23.108.36.162', 'device_guid': '0bc6b751-1e14-4ffd-9bd0-ecfa71905727', 'monitor': 'localhost'}
2014-09-04 14:50:40,237 DEBUG zen.zencommand: Queued event (total of 2) {'rcvtime': 1409867440.23758, 'device_guid': '0bc6b751-1e14-4ffd-9bd0-ecfa71905727', 'component': '', 'agent': 'zencommand', 'manager': 'zenoss.ubiquityservers.com', 'device': '23.108.36.162', 'eventClass': '/Cmd/Fail', 'severity': 0, 'monitor': 'localhost', 'summary': 'Datasource OpenStackEndpoint/openstack command completed successfully', 'eventKey': 'openstack'}
2014-09-04 14:50:40,237 DEBUG zen.collector.scheduler: Task 23.108.36.162 300 Local finished, result: [(<Products.ZenRRD.zencommand.Cmd instance at 0x5a99320>, ParsedResults
events: [{'eventClassKey': u'openStackFailure',
'eventKey': u'openStackFailure',
'severity': 5,
'summary': u"OpenStack failure: Invalid client version ''. must be one of: 3, 2, 1.1"},
{'component': '',
'device': '23.108.36.162',
'eventClass': '/Cmd/Fail',
'eventKey': 'openstack',
'severity': 0,
'summary': 'Datasource OpenStackEndpoint/openstack command completed successfully'}]
values: []})]
2014-09-04 14:50:40,239 DEBUG zen.collector.scheduler: Task 23.108.36.162 300 Local changing state from STORE_PERF_DATA to IDLE
2014-09-04 14:50:40,239 INFO zen.zencommand: 1 devices processed (0 datapoints)
2014-09-04 14:50:40,239 INFO zen.collector.scheduler: Tasks: 2 Successful_Runs: 1 Failed_Runs: 0 Missed_Runs: 0 Queued_Tasks: 0 Running_Tasks: 1
2014-09-04 14:50:40,239 DEBUG zen.collector.scheduler: In shutdown stage before
2014-09-04 14:50:40,239 DEBUG zen.collector.scheduler: Stopping running task 23.108.36.162 300 Local
2014-09-04 14:50:40,240 DEBUG zen.collector.scheduler: call finished LoopingCall<300>(CallableTask: 23.108.36.162 300 Local, (), *{}) : LoopingCall<300>(CallableTask: 23.108.36.162 300 Local, (), *{})
2014-09-04 14:50:40,240 DEBUG zen.collector.scheduler: Removing task 23.108.36.162 300 Local
2014-09-04 14:50:40,240 DEBUG zen.collector.scheduler: Removing task configLoader
2014-09-04 14:50:40,240 DEBUG zen.collector.scheduler: tasks to clean set([<Products.ZenCollector.config.ConfigurationLoaderTask object at 0x5a98050>, <Products.ZenCollector.config.ConfigurationLoaderTask object at 0x5a982d0>, <main.SshPerformanceCollectionTask object at 0x60236d0>])
2014-09-04 14:50:40,240 DEBUG zen.collector.scheduler: Cleanup on task configLoader <Products.ZenCollector.config.ConfigurationLoaderTask object at 0x5a98050>
2014-09-04 14:50:40,240 DEBUG zen.collector.scheduler: Scheduler._cleanupTaskComplete: result=None task.name=configLoader
2014-09-04 14:50:40,240 DEBUG zen.collector.scheduler: Cleanup on task configLoader <Products.ZenCollector.config.ConfigurationLoaderTask object at 0x5a982d0>
2014-09-04 14:50:40,241 DEBUG zen.collector.scheduler: Scheduler._cleanupTaskComplete: result=None task.name=configLoader
2014-09-04 14:50:40,241 DEBUG zen.collector.scheduler: Cleanup on task 23.108.36.162 300 Local COMMAND schedule Name: 23.108.36.162 300 Local configId: 23.108.36.162 Datasources: 1
2014-09-04 14:50:40,241 DEBUG zen.collector.scheduler: Scheduler._cleanupTaskComplete: result=None task.name=23.108.36.162 300 Local
2014-09-04 14:50:40,241 DEBUG zen.zencommand: Tried to stop reactor that was stopped
2014-09-04 14:50:40,241 INFO zen.zencommand: Daemon CollectorDaemon shutting down
2014-09-04 14:50:40,242 DEBUG zen.zencommand: Sending 2 events, 0 perf events, 0 heartbeats
2014-09-04 14:50:40,263 DEBUG zen.zencommand: Removing service EventService
2014-09-04 14:50:40,263 DEBUG zen.zencommand: Removing service Products.ZenHub.services.CommandPerformanceConfig
2014-09-04 14:50:40,264 DEBUG zen.pbclientfactory: Lost connection to 127.0.0.1:8789 - [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion: Connection lost.
]
2014-09-04 14:50:40,264 DEBUG zen.collector.scheduler: In shutdown stage during
2014-09-04 14:50:40,265 DEBUG zen.collector.scheduler: In shutdown stage after

Hello,
I added ZenPacks.zenoss.Openstack version 1.2.2 on Zenoss Core 4.2.5.
When I add my Openstack credentials and API URL job is started, but zen.ZenDisc never starts zenoss.OpenStack plugin and flavours, images and servers aren't requested.
Here is job log (I changed IP to 1.1.1.1 on purpose) :

2014-06-11 15:01:46,794 INFO zen.Job: Job e0ff5837-6749-4e79-bd81-40154b58df54 (Products.ZenModel.ZDeviceLoader.DeviceCreationJob) received
2014-06-11 15:01:46,817 INFO zen.Job: Beginning job Add Device Products.ZenModel.ZDeviceLoader.DeviceCreationJob
2014-06-11 15:01:47,158 INFO zen.Job: Running Job Add Device Products.ZenModel.ZDeviceLoader.DeviceCreationJob
2014-06-11 15:01:47,158 INFO zen.Job: Spawning subprocess: /opt/zenoss/bin/zendisc run --now -d 1.1.1.1 --monitor localhost --deviceclass /Devices/OpenStack --prod_state 1000 --job e0ff5837-6749-4e79-bd81-40154b58df54
2014-06-11 15:01:51,410 INFO zen.ZenDisc: Connecting to localhost:8789
2014-06-11 15:01:51,415 INFO zen.ZenDisc: Connected to ZenHub
2014-06-11 15:01:51,524 INFO zen.ZenDisc: Looking for 1.1.1.1
2014-06-11 15:01:58,836 INFO zen.ZenDisc: Result: Discovered device 1.1.1.1.
2014-06-11 15:01:58,891 INFO zen.ZenDisc: skipping WMI-based collection, PySamba zenpack not installed
2014-06-11 15:01:58,934 INFO zen.ZenDisc: No Python plugins found for 1.1.1.1
2014-06-11 15:01:58,936 INFO zen.ZenDisc: No command plugins found for 1.1.1.1
2014-06-11 15:01:58,939 INFO zen.ZenDisc: SNMP collection device 1.1.1.1
2014-06-11 15:01:58,939 INFO zen.ZenDisc: plugins: zenoss.snmp.NewDeviceMap, zenoss.snmp.DeviceMap, zenoss.snmp.InterfaceMap, zenoss.snmp.RouteMap
2014-06-11 15:01:58,943 INFO zen.ZenDisc: No portscan plugins found for 1.1.1.1
2014-06-11 15:02:04,946 INFO zen.SnmpClient: Device timed out: SNMP info for 1.1.1.1 at 1.1.1.1:161 timeout: 1 tries: 6 version: v2c community: public
2014-06-11 15:02:04,946 INFO zen.SnmpClient: snmp client finished collection for 1.1.1.1
2014-06-11 15:02:04,947 WARNING zen.SnmpClient: Device 1.1.1.1 timed out: are your SNMP settings correct?
2014-06-11 15:02:04,947 INFO zen.ZenDisc: No change in configuration detected
2014-06-11 15:02:04,947 INFO zen.ZenDisc: Scan time: 6.11 seconds
2014-06-11 15:02:04,948 INFO zen.ZenDisc: Daemon ZenDisc shutting down
2014-06-11 15:02:06,327 INFO zen.Job: Job e0ff5837-6749-4e79-bd81-40154b58df54 Finished with result 0
2014-06-11 15:02:06,329 INFO zen.Job: Job e0ff5837-6749-4e79-bd81-40154b58df54 finished with result 0

After job is finished, when I go to device added and click "Modeller Plugins", only zenoss.snmp.NewDeviceMap, zenoss.snmp.DeviceMap, zenoss.snmp.InterfaceMap, zenoss.snmp.RouteMap are selected. There is no zenoss.OpenStack. If I add it manually and push changes nothing happens...

Am I doing something wrong or I encountered some bug?

Thanks

I found a relationship mismatch between Endpoint.servers <-> Server.endpoint.

Endpoint defines:
('servers', ToManyCont(ToOne, 'ZenPacks.zenoss.OpenStack.Server.Server', 'endpoint',),

Server defines:
('endpoint', ToOne(ToManyCont, 'ZenPacks.zenoss.OpenStack.Endpoint.Endpoint', 'images',),

The remote name of the relationship in Server.py should be servers not images.

A crucial requirement for an administrator/analyzer is to study each VM instance statistics and status. Right now there is no direct way from Servers list in an OpenStack device to libvirtGuests in libvirtHost device. Having these functionality in the same place is a great advantage.

Good morning,

I am trying to setup Zenoss monitoring on a v2 OpenStack environment. The error I am getting is:

2014-02-23 08:15:05,625 INFO zen.ZenDisc: plugins: zenoss.OpenStack
2014-02-23 08:15:05,666 INFO zen.OpenStack: Requesting flavors
2014-02-23 08:15:05,798 ERROR zen.ZenDisc: Unable to fill collection slots: [Failure instance: Traceback (failure with no frames): <class 'requests.exceptions.SSLError'>: [Errno 1] _ssl.c:503: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

The SSL cert is valid but Chrome reports is as "not having valid public audits". I'm not sure how important that is to python, though.

Good evening,

While trying to scan my openstack environment, I get the following error:

2014-02-27 21:53:57,319 ERROR zen.zencommand: domain 300 Local OpenStackEndpoint/openstack Error running parser <Products.DataCollector.Plugins.PluginLoader instance at 0x5740f38>
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenRRD/zencommand.py", line 816, in _processDatasourceResults
parser.processResults(datasource, results)
File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.OpenStack-1.2.1.egg/ZenPacks/zenoss/OpenStack/parsers/endpoint.py", line 20, in processResults
data = json.loads(cmd.result.output)
File "/opt/zenoss/lib/python2.7/json/init.py", line 326, in loads
return _default_decoder.decode(s)
File "/opt/zenoss/lib/python2.7/json/decoder.py", line 366, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/opt/zenoss/lib/python2.7/json/decoder.py", line 384, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded

Is there anything else I can provide to help track this down?

There is an issue when using the new version 2.2.0 of the ZenPack where an errors occur in the EventsAMQP datasource when an event is sent from Ceilometer that is below Liberty, and using the Zenoss Ceilometer Dispatcher v1.0.1

After comparing the datasource code to previous versions of this ZenPack. I discovered that the issue occurs in Line #170, in this current version:

traits[trait[0]] = trait[2]

The following replacement (from previous versions) did the trick:

traits[trait['name']] = trait['value']

I believe it would be good to add some back compatibility in this part of the datasource against versions prior to 2.0.2 of the Zenoss Ceilometer dispatcher plugin.

I am getting this critical event (see title) when trying to add an Openstack Infrastructure endpoint. I am not sure what the cause of the problem is. I am running a Zenoss Core 4, and the Openstack is Kilo version.

Here is more detailed information of the event:

agent zencommand
component null
dedupid openstack||/Status|openStackFailure|5
eventClass /Status
eventClassKey openStackFailure
eventClassMapping openStackFailure
eventGroup
eventKey openStackFailure
eventState New
evid 000c2951-5c27-ab6b-11e5-67e5ab8c2c45
facility
message OpenStack failure: Connection was closed cleanly.
ntevid
priority
severity 5
summary OpenStack failure: Connection was closed cleanly.

Since Mitaka OpenStack-Ansible Deployment uses a combination of Ansible and Linux Containers (LXC) to install and manage OpenStack. Ansible provides an automation platform to simplify system and application deployment.

OpenStack-Ansible is now the official OpenStack Foundation deployment tool.

While Docker OpenStack nodes may model correctly under OpenStack-Ansible they are all treated as separate entities and show up as separate servers generally without an IP address to connect to which produces a lot of alerts.

This is predominate on the Controllers but likely to occur on the other node types as well.

There's code and a zproperty to check for the presence of docker containers so can code be added to check of LXC containers?

Hi,
I have zenoss 4.2.5 installed with OpenstackInfrastructure Zenpack installed . When i run openstack_amqp_config script to enable ceilomemeter get following error. Please guide.
##########################################################
Traceback (most recent call last):
File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.OpenStackInfrastructure-2.4.1.egg/ZenPacks/zenoss/OpenStackInfrastructure/openstack_amqp_init.py", line 23, in
import transaction
ImportError: No module named transaction
##########################################################