Implemented Member ID support unique to server or driver.

[rdiyewar]

While implementing yardstick support for my product, i wanted to distiguish between servers and wanted to implement one out of many server in a specific way, however i could not find any way to do this.

Thus i added MemberID for each member in yardstick which is unique to Servers (Or Drivers). They can now be distinguish between themselves using this MemberID.

Added print statement in Server Configuring server id= and DriverConfiguring driver id= inside EchoBenchmark example and found following output

$ grep "Configuring server" * -r
logs_servers/0_localhost.log:<16:42:11><yardstick> Configuring server id=0
logs_servers/1_localhost.log:<16:42:21><yardstick> Configuring server id=1

$ grep "Configuring driver" * -r
logs_drivers/164224_0_localhost.log:<16:42:34><yardstick> Configuring driver id=0
logs_drivers/164241_1_localhost.log:<16:42:51><yardstick> Configuring driver id=1

[ashutakGG]

Hi,

Thank you for your contribution! Looks like it can be useful.

Do you run your servers/drivers on the same or different hosts? If on different then you can use hostname as an id.

We will do more detailed review in a couple days.

[rdiyewar]

I had ran them on localhost, but my plan are to run actual benchmark on different hosts. Anyways I don't want to use hostname inside code and make it host specific.