The networking_cisco.plugins.cisco.device_manager.rpc.devmgr_rpc_cfgagent_api
Module¶
-
class
networking_cisco.plugins.cisco.device_manager.rpc.devmgr_rpc_cfgagent_api.
DeviceMgrCfgAgentNotifyAPI
(devmgr_plugin, topic=’cisco_cfg_agent’)¶ Bases:
object
API for Device manager service plugin to notify Cisco cfg agent.
-
agent_updated
(context, admin_state_up, host)¶ Updates cfg agent on <host> to enable or disable it.
-
get_hosting_device_configuration
(context, id)¶ Fetch configuration of hosting device with id.
The configuration agent should respond with the running config of the hosting device.
-
hosting_devices_assigned_to_cfg_agent
(context, ids, host)¶ Notify cfg agent to now handle some hosting devices.
This notification relieves the cfg agent in <host> of responsibility to monitor and configure hosting devices with id specified in <ids>.
-
hosting_devices_removed
(context, hosting_data, deconfigure, host)¶ Notify cfg agent that some hosting devices have been removed.
This notification informs the cfg agent in <host> that the hosting devices in the <hosting_data> dictionary have been removed from the hosting device pool. The <hosting_data> dictionary also contains the ids of the affected logical resources for each hosting devices:
{'hd_id1': {'routers': [id1, id2, ...], 'fw': [id1, ...], ...}, 'hd_id2': {'routers': [id3, id4, ...]}, 'fw': [id1, ...], ...}, ...}
The <deconfigure> argument is True if any configurations for the logical resources should be removed from the hosting devices
-
hosting_devices_unassigned_from_cfg_agent
(context, ids, host)¶ Notify cfg agent to no longer handle some hosting devices.
This notification relieves the cfg agent in <host> of responsibility to monitor and configure hosting devices with id specified in <ids>.
-