fix rsyslog server to listen both tcp and udp

[Bogdan Dobrelya]

To provide more reliable messaging for syslog, TCP mode was assumed to be used for rsyslog clients.
1) Currently we have it hardcded, fix it to use selected value from UI (Settings: Syslog Transport Protocol)
2) Make rsyslog server to listen both tcp and udp to provide backwards compatible logging mode for provision stage (send2syslog.py script and some ks/preseed templates are using udp)
3) Make rsyslog clients to use TCP for deployment stage only (which is the most critical for reliable logs because of possible interfaces shutdown actions)

[Bogdan Dobrelya (bogdando)]

https://review.openstack.org/70942

[Bogdan Dobrelya (bogdando)]

We should accept this to make sure the patch for #1271176 will work as expected
Default UI option for syslog transport should be changed to TCP as well (https://review.openstack.org/#/c/70941/)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/70942
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=e6797f98aad8bcce66a078dafe922a2f17451978
Submitter: Jenkins
Branch: master

commit e6797f98aad8bcce66a078dafe922a2f17451978
Author: Bogdan Dobrelya <email address hidden>
Date: Tue Feb 4 11:56:55 2014 +0200

    Fix TCP/UDP usage for rsyslog logging

    - Introduce 'both' value for rsyslog server proto
    - Make rsyslog server to listen both tcp and udp
    - Fix wrong proto param usage for clients (clients
      should use $rservers hash instead)
    - Change base rsyslog server proto to TCP

    CI retest
    Additional to: #1271176
    Closes bug: #1276065

    Change-Id: I3b13781a85a88dcb7d36edb54f5ad60c2f16c74b
    Signed-off-by: Bogdan Dobrelya <email address hidden>