------------------------------------------------------------ revno: 6395 committer: Miika Komu <miika@xxxxxx> branch nick: hipl timestamp: Sun 2012-10-28 17:02:50 +0200 message: Documented how to use reverse HTTP proxy with HIPL in the manual We experimented with HAproxy in the following publication, and now this is documented in the manual. M. Komu, M. Sethi, R. Mallavarapu, H. Oirola, R. Khan, and S. Tarkoma. Secure Networking for Virtual Machines in the Cloud, In International Workshop on Power and QoS Aware Computing (PQoSCom2012). IEEE, sep 2012. modified: doc/HOWTO.xml.in -- lp:hipl https://code.launchpad.net/~hipl-core/hipl/trunk Your team HIPL core team is subscribed to branch lp:hipl. To unsubscribe from this branch go to https://code.launchpad.net/~hipl-core/hipl/trunk/+edit-subscription
=== modified file 'doc/HOWTO.xml.in' --- doc/HOWTO.xml.in 2012-10-28 15:01:44 +0000 +++ doc/HOWTO.xml.in 2012-10-28 15:02:50 +0000 @@ -842,7 +842,7 @@ <section id="ch_tips_for_hip"> <title>Tips for Using HIP with Some Applications</title> <section id="sec_using_hip_proxy"> - <title> Using HIP Enabled Web Proxy</title> + <title> Using HIP with Forward Web Proxy</title> <para> In the deployment phase, it is interesting to set-up a proxy server that translates the TCP/IP traffic into HIP. For instance, this is convenient @@ -887,6 +887,24 @@ hipconf daemon run normal|opp firefox </para> </section> + + <section id="sec_rev_proxy"> + <title>Using HIP with Reverse HIP Proxy</title> + + <para> + HAProxy (version 1.3.22) has been successfully used with HIPL for web-based + load balancing in in a cloud-based deployment. In the experimentation, the + HAProxy translated non-HIP communications originating from clients + into HIP-based connections to the servers. The HAProxy did not require + any changes, and it was merely configured to use LSIs or HITs instead of + IPv4 or IPv6 addresses. In the experiment, the hosts files were modified to + contain both the identifiers and locators as described by method 3a in + <xref linkend="sec_easy_methods" />. In addition, HIP daemon and firewall + were installed at the host that was running HAProxy. + </para> + + </section> + <section id="sec_sendmail"> <title>Sendmail and SpamAssassin</title> <para>