VMware VCLOUD REQUEST MANAGER 1.0.0 Uživatelský manuál stáhnout pdf (Strana 7)

Release Notes for Zenoss Ser-

vice Dynamics Version 4.1.1

mysqldump -u root -p [ROOT_PASSWORD] events | gzip -c > zenoss_events.sql.gz

• If you are running with a load-balanced configuration with multiple Zope instances, or have a highly cus-

tomized distributed collector environment, your configuration may be slightly modified during upgrade to

this release of Resource Manager. Specifically, if your main Zenoss 3.2.x master has a DAEMONS_TXT_ONLY

and daemons.txt file to restrict the daemons run on your master server, you will be affected. The upgrade

process will save these two files to your $ZENHOME/etc directory with the extension "rpmsave," and your post-

upgraded system will return to the default daemon starting behavior.

After upgrade, you can safely modify these files and restrict the daemons started on your master server

again. If you do so, please take notice of the daemons needed for Resource Manager Version 4.1.1, as

these have changed from earlier releases.

• Zenoss does not test or evaluate community, customer-developed, or other custom ZenPacks for upgrades.

If you are using one or more ZenPacks that are not installed through the standard Resource Manager

installation process, you should contact the ZenPack author about its compatibility with this release. Do not

upgrade until you ensure compatibility of all custom ZenPacks. Zenoss further recommends you test the

ZenPack for upgrade compatibility in a test environment.

1.4.1.2. Updating Custom ZenPacks

• Custom ZenPacks must be compatible with Python 2.7. You must upgrade custom ZenPacks with Python

2.7-compiled extensions.

• If you have a custom ZenPack running on Zenoss Enterprise 3.2.x that includes alerting rules with custom

actions, then you must modify the ZenPack before you can use it with Resource Manager. Otherwise, the

system will produce warning messages similar to this:

WARNING:zen.migrate: <rule>: Successfully migrated rule to Trigger, \

but was unable to create a Notification - rule has invalid or unknown action type: <action>

You must add the following code to your custom ZenPack, in configure.zcml:

<utility factory=".actions.MyAction"

provides="Products.ZenModel.interfaces.IAction"

name="my_action"/>

</configure>

Read the IAction class declaration in $ZENHOME/Products/ZenModel/interfaces.py for documentation of the

attributes and methods your action needs to implement. Add the following code to actions.py in your custom

ZenPack:

class MyAction(IActionBase):

implements(IAction)

id = 'my_action'

name = 'My Action'

actionContentInfo = ICommandActionContentInfo

def execute(self, notification, signal):

...

def updateContent(self, content=None, data=None):

...

Note that the name attribute in the configure.zcml file matches up to the id attribute in the actions.py

file. Examples of implementing actions are in $ZENHOME/Products/ZenModel/actions.py, which declares four

core actions: email, page, command, and trap.

1.4.1.3. Event Console Filtering

Event console filtering behavior in Resource Manager is different than that of Zenoss 3.2.x, as follows:

• Regular expressions are not supported when filtering by device or component.

1 2 3 4 5 6 7 8 9 10 11 12 ... 20 21

Komentáře k této Příručce

Žádné komentáře

VMware VCLOUD REQUEST MANAGER 1.0.0 Uživatelský manuál Strana 7

Komentáře k této Příručce

Související produkty a manuály pro Software VMware VCLOUD REQUEST MANAGER 1.0.0