I'm right now in the process of setup a high availability enviroment with 2 distributed OpenERP servers and there are some points that you need to consider that are not exposed in the link before and I couldn't find any reference.
When you do a load balance for any service you need to take care of sessions handling in the number of servers that you may have, in the case of OpenERP the session management is done by werkzeug at the low level and OpenERP use the werkzeug.contrib.sessions.FilesystemSessionStore wich write sessions to disk. If all of your OpenERP servers are on the same server machine and they are started with the same user you should not have any trouble but if the OpenERP servers are distributed perhaps you will end having different sessions for the same user in all the OpenERP servers, for example you ask to the loadbalancer for http://yours.server.com/ and that generate request for load js, css, and many more stuffs like dblist, etc. if you have 2 servers you may be creating session in both of them, so when you login in the UI, you are login in one of the servers and in that server the session store the information related to who you are, but again others request will be send to the rest of the servers and in those your session are not authenticated so you will be seen errors like "your session has expired" because you are trying to access a resource that need to have been authenticated agains a db and in that server your session doesn't. to resolve this I create a session store that use Redis as a backend and is configured to be used in all my OpenERP servers to query Redis for session information, that way all the request agains all the servers can access to the same session information.