Hi,
In addition to Aarons changes there are still a lot of issues which I
think are problematic with the current implementation. The problems that
I see at the moment are as follows:
1. The amount of data that sent on the network to the agents
2. The way in which the data is parsed on the agent:
i. Networks that are disabled are sent to the agent
ii. Subnets that have DHCP disabled are sent to the agent
iii. The host file is rebuilt with each and every change. This
means looping over all of the ports in the network each time there is an
update.
3. Message reliability. At the moment I am investigating a bug where
deleting 10 networks leaves the host file with details of a port that
has already been deleted. (
I think that a way of addressing the above may be as follows:
1. Enable the plugin to prepare the information for the agents. This can
leverage the database filtering and reduce the amount of data on the
network. In addition to this the plugin can/may have drivers that are
specific to the agents implementation - for example in the case of
dnsmasq, it will be preparing the host file. In the case of the dnsmasq
we can send host file deltas. A further reduction can be compressing the
host file.
2. In order to prevent very heavy operations when either agents/services
are restarted we can have a hash of the above file. This can ensure that
it is synced (this is something that is specific to the driver
implementations).
Thoughts?
Thanks
Gary
--
Mailing list: https://launchpad.net/~quantum-core
Post to : [email protected]
Unsubscribe : https://launchpad.net/~quantum-core
More help : https://help.launchpad.net/ListHelp
