git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1231 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1230 71dcc9de-d417-0410-9af5-da40c76e7ee4

changes because if the node have to be dropped (set in DOWN state), the
partition table update will contains it's UUID after it was removed from the
storages partition table and they will fails to find the related node.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1229 71dcc9de-d417-0410-9af5-da40c76e7ee4

not related to partitions currently assigned to a storage node. This is required
because an old node can come back, get a new UUID, start replication and a
conflict on (oid, serial) with the cluster it is joining. As there is now check
on the object integrity, the object will not be replicated and a bad object will
be kept. So during storage initialization, after getting the full partition
table, a storage look if there is partitions unassigned to it and drop data for
those partitions.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1228 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1227 71dcc9de-d417-0410-9af5-da40c76e7ee4

Simplify the neo setup behing testZODB to accelerate it. Complex partition tables should be tested in testStorage.py.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1226 71dcc9de-d417-0410-9af5-da40c76e7ee4

Add a test for partition replication.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1225 71dcc9de-d417-0410-9af5-da40c76e7ee4

the master node, thus when it forward this answer to neoctl, the expected packet
type is always noError.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1224 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1223 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1222 71dcc9de-d417-0410-9af5-da40c76e7ee4

Even if a handler raises, the connection might still contain pending packets. So it should not prevent appending the connection to the list.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1221 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1220 71dcc9de-d417-0410-9af5-da40c76e7ee4

terms. Use them in testImportExport and switch some methods to private
visibility.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1219 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1218 71dcc9de-d417-0410-9af5-da40c76e7ee4

Do not conditionaly define locking classes, so that they can be available independently from VERBOSE_LOCKING value for finer-grained lock tracing.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1217 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1216 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1215 71dcc9de-d417-0410-9af5-da40c76e7ee4

- Add expectCluster<State>() on NeoCluster
- expectNoOutdatedCells renamed as expectOutdatedCells to expect a given number
a cell in OUT_OF_DATE state.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1214 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1213 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1212 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1211 71dcc9de-d417-0410-9af5-da40c76e7ee4

to the method, raise NotReadyError in each method because the master connection
is not always required.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1210 71dcc9de-d417-0410-9af5-da40c76e7ee4

attribute.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1209 71dcc9de-d417-0410-9af5-da40c76e7ee4

NotReady exception to let the handler dispatch method send the answer.
NotReady can now receive a custom message.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1208 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1207 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1206 71dcc9de-d417-0410-9af5-da40c76e7ee4

neoctl command on disconnected nodes.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1205 71dcc9de-d417-0410-9af5-da40c76e7ee4

getConnection().


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1204 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1203 71dcc9de-d417-0410-9af5-da40c76e7ee4

Merge and simplify admin handler classes to hanle just 2 cases: expected answer, and the rest. This fixes cluster state notification handling (which used to only log a line because the hadler method was defined twice...).


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1202 71dcc9de-d417-0410-9af5-da40c76e7ee4

in NeoCluster class.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1201 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1200 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1199 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1198 71dcc9de-d417-0410-9af5-da40c76e7ee4

The existing code was exiting election loop too early, as there might not have been an identified connection to primary master (ask/answerPrimaryMaster is quicker than ask/answerPrimaryMaster + request/acceptNodeIdentification).
The correct way is to stop waiting for connections to nodes other than primary master, and this can be done in answerPrimaryMaster.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1197 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1196 71dcc9de-d417-0410-9af5-da40c76e7ee4

git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1195 71dcc9de-d417-0410-9af5-da40c76e7ee4

No need to cleanum NodeManager content when connection to primary master is closed, since we will anyway flush it when trying to reconnect to a primary master.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1194 71dcc9de-d417-0410-9af5-da40c76e7ee4

Change primary master state to RUNNING, as we are indeed connected to it (and it won't notify of its own state).


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1193 71dcc9de-d417-0410-9af5-da40c76e7ee4

Add a new Node state: UNKNOWN_STATE. In this state, nodes are supposed to be RUNNING, but there was no successful attemp to connect to them yet, nor any notification that they were running. This is especially useful in tests to avoid a stopped node to appear as RUNNING until receiving a notification that it is in fact DOWN.


git-svn-id: https://svn.erp5.org/repos/neo/branches/prototype3@1192 71dcc9de-d417-0410-9af5-da40c76e7ee4