Netflix, HuluPlus, Amazon on Roku device

mmmh I need some BitCoins to pay for all this, please donate some to me :-) .... - 16tb2Rgn4uDptrEuR94BkhQAZNgfoMj3ug

If you live in a country that has censorship laws, corrupt politicians, a crime rate higher than the stars and people taking other people's land and you are desperate to get some decent TV, then this is for you.

I recently had fiber to the home installed, but there was no way to set the DNS in the ONT - Optical Network Terminal, IE the little thingy that's mounted on the wall where the fiber plugs in, this caused some problems for me, as I stream through a Roku device and the Roku device of course does not allow you to set the DNS...

I do have Unotelly, but the problem is that although I can activate the UnoTelly DNS on my computer and stream Netflix by using the computer, that does not solve my Roku streaming problem as the Roku device does not pick up the computer settings, so below is what I did

Install Pacemaker and Corosync on SLES 11 SP3 - Postgres streaming - Part3

Darn, between part1, part2 and part3, no Bitcoins, Is there someone out there?.... - 16tb2Rgn4uDptrEuR94BkhQAZNgfoMj3ug

Hopefully you read through Part 2?

Install Pacemaker and Corosync on SLES 11 SP3 - Postgres streaming - Part2

Darn, no Bitcoins, PLEASE?.... - 16tb2Rgn4uDptrEuR94BkhQAZNgfoMj3ug

Hopefully you read through Part 1?

Install Pacemaker and Corosync on SLES 11 SP3 - Postgres streaming - Part1

When starting Corosync, the Corosync scripts should start Pacemaker as well, you can check this with the following in all the nodes

cl1_lb1:/ # ps -ef | grep corosync
root      4064     1  0 07:14 ?        00:00:07 /etc/init.d/rc3.d/S11corosync start
root      7594 12522  0 10:08 pts/0    00:00:00 grep corosync
cl1_lb1:/ # ps -ef | grep pacemaker
90        4084  4064  0 07:14 ?        00:00:29 /usr/lib64/pacemaker/cib
root      4085  4064  0 07:14 ?        00:00:01 /usr/lib64/pacemaker/stonithd
root      4086  4064  0 07:14 ?        00:00:02 /usr/lib64/pacemaker/lrmd
90        4087  4064  0 07:14 ?        00:00:00 /usr/lib64/pacemaker/attrd
90        4088  4064  0 07:14 ?        00:00:00 /usr/lib64/pacemaker/pengine
90        4089  4064  0 07:14 ?        00:00:00 /usr/lib64/pacemaker/crmd
root      7770 12522  0 10:08 pts/0    00:00:00 grep pacemaker
cl1_lb1:/ #

Install Pacemaker and Corosync on SLES 11 SP3 - Postgres streaming - Part1

Guess what, no Bitcoins from ANYONE, Please buy some and donate them to me.... - 16tb2Rgn4uDptrEuR94BkhQAZNgfoMj3ug

I recently had the 'pleasure' of installing Pacemaker and Corosync on a 4 node cluster, originally the configuration called for 2 clusters, hence the naming, Cluster1 and Cluster2, cl1 and cl2.

As it normally goes in the IT world, things change and I implemented the following configuration.

Cluster (Only one now)
4 nodes, all running SLES 11 SP3, cl1_lb1, cl1_lb2, cl2_lb1, cl2_lb2
2 nodes, one master Postgres and one slave with Postgres streaming, cl1_lb1 and cl2_lb2

2 applications, the one called CBC, the other CGW

CBC runs on one of the Postgres machines (either cl1_lb1 or cl2_lb1), depending on which one is the Master, uses a VIP address for the outside world to communicate with it

CGW runs on all the nodes, uses a VIP in a round robin fashion, to serve Apache2 pages