Shulou(Shulou.com)06/01 Report--

Today, I would like to share with you how to install docker compose redis cluster related knowledge, detailed content, clear logic, I believe that most people still know too much about this knowledge, so share this article for your reference, I hope you can learn something after reading this article, let's take a look at it.

1. Redis configuration information template

File name: redis-cluster.tmpl

# redis port port ${PORT} # redis access password requirepass 123456#redis access Master node password masterauth 12345 off protected mode protected-mode no# open cluster cluster-enabled yes# cluster node configuration cluster-config-file nodes.conf# timeout cluster-node-timeout 500 cluster node IP host mode is host IP# cluster-announce-ip 192.168.1.1 cluster node port 7001-7006cluster-announce-port $ {PORT} cluster-announce-bus-port 1 ${PORT} # turn on appendonly backup mode appendonly yes# backup per second when appendfsync everysec# compresses aof files Whether to perform synchronous operation no-appendfsync-on-rewrite no# when the current aof file size exceeds 100% of the aof file size at the time of the last rewrite, the minimum size of the AOF file before the auto-aof-rewrite-percentage 10 rewrite default 64mbauto-aof-rewrite-min-size 64mb# log configuration # debug: will print and generate a lot of information, suitable for the development / test phase # verbose: contains a lot of less useful information But not as messy as the debug level # notice: moderately verbose, suitable for production environments # warning: only record very important and critical warning messages loglevel notice# log file path logfile "/ data/redis.log" 2, write bulk generation configuration file scripts

File name: redis-cluster-config.sh

For port in `seq 7001 7006`; do\ mkdir-p. / ${port} / conf\ & & PORT=$ {port} envsubst

. / ${port} / conf/redis.conf\ & & mkdir-p. / ${port} / data;\ done III. Batch generate configuration files

Execute redis-cluster-config.sh to generate configuration file

Fourth, write docker-compose files

File name: docker-compose.yml

Version: '3'services: redis-7001: image: redis:6 container_name: redis-7001 command: ["redis-server" "/ usr/local/etc/redis/redis.conf"] volumes: -. / 7001/conf/redis.conf:/usr/local/etc/redis/redis.conf -. / 7001/data:/data ports:-"70017001/conf/redis.conf:/usr/local/etc/redis/redis.conf 7001"-"170017001/conf/redis.conf:/usr/local/etc/redis/redis.conf 17001" environment: # set the time zone to Shanghai Otherwise, there will be a problem with the time-TZ=Asia/Shanghai logging: options: max-size: '100m' max-file: '10' redis-7002: container_name: redis-7002 -. / 7002/conf/redis.conf:/usr/local/etc/redis/redis.conf -. / 7002/data:/data-"7002max-size 7002"-"17002VV 17002" "redis-7003: container_name: redis-7003 -. / 7003/conf/redis.conf:/usr/local/etc/redis/redis.conf -. / 7003/data:/data -" 7003VR 7003 "-" 17003VOR 17003 "redis-7004: container_name: redis-7004 -. / 7004/conf/redis.conf:/usr/local/etc/redis/redis.conf- . / 7004/data:/data-"7004redis-7005 7004"-"17004VOR 17004" redis-7005: container_name: redis-7005 -. / 7005/conf/redis.conf:/usr/local/etc/redis/redis.conf -. / 7005/data:/data-"7005Vl7005"-"17005Vl17005" redis-7006: container_name: redis-7006 -. / 7006/conf/redis.conf:/usr/local/etc/redis/redis.conf -. / 7006/data:/data-"7006 7006"-"17006 VR 17006" 5. Do clusters and assign slots

Note: 192.168.44.65 is the host ip

Ipport192.168.44.657001192.168.44.657002192.168.44.657003192.168.44.657004192.168.44.657005192.168.44.657006

Execute the command:

Note: cluster-replicas indicates that a master node has several slave nodes.

C:\ Users\ billow > docker exec-it redis-7001 redis-cli-p 7001-a 123456-- cluster create 192.168.44.65 docker exec 7001 192.168.44.65 it redis-7001 redis-cli 7002 192.168.44.65 10922Master 7003 192.168.44.65 7004 192.168.44.65 10922Master 7005 192.168.44.6515 7006-cluster-replicas 1 > > Performing hash slots allocation on 6 nodes...Master [0]-> Slots 0-5460Master [1]-> Slots 5461-10922Master [2] -> Slots 10923-16383Adding replica 192.168.44.65 slots 7006 to 192.168.44.65:7002Adding replica 192.168.44.65 to 192.168.44.65 to 192.168.44.65 to 7003 > Trying to optimize slaves allocation for anti-affinity [WARNING] Some slaves are in the same host as their masterM: 741c7bb537888ff97866896abb22da27c22f8eaf 192.168.44.65 slots 7001 slots: [0-5460] (5461 slots) masterM: e5f687462a0c47f51c3abf4b8d77d646a3d63fa9 192.168.44 .65 slots 7002 slots: [5461-10922] (5462 slots) masterM: 9936d3690d971eccfc8b8ed43c5defc66f318454 192.168.44.65 9936d3690d971eccfc8b8ed43c5defc66f318454 7003 slots: [10923-16383] (5461 slots) masterS: b7b6fa6a4766c32c5d42d759548d6fcdf2b9159b 192.168.44.65 f69a5d0ae974816396a9d9e613c13f6ceea25de2 7004 replicates e5f687462a0c47f51c3abf4b8d77d646a3d63fa9S: 2275c996f25a8815342e2435af073eb29565778b 192.168.44.65 f69a5d0ae974816396a9d9e613c13f6ceea25de2 7005 replicates 741c7bb537888ff97866896abb22da27c22f8eafCan I set the above configuration? (type 'yes' to accept): yes > > Nodes configuration updated > > Assign a different config epoch to each node > > Sending CLUSTER MEET messages to join the clusterWaiting for the cluster to join. > > Performing Cluster Check (using node 192.168.44.65 master 7001) M: 741c7bb537888ff97866896abb22da27c22f8eaf 192.168.44.65 master 7001 slots: [0-5460] (5461 slots) master 1 additional replica (s) S: f69a5d0ae974816396a9d9e613c13f6ceea25de2 172.25.0.11 slots 7006 slots: (0 slots) slave replicates 741c7bb537888ff97866896abb22da27c22f8eafM: 9936d3690d971eccfc8b8ed43c5defc66f318454 172.25.0.7 Slots: [10923-16383] (5461 slots) master 1 additional replica (s) M: e5f687462a0c47f51c3abf4b8d77d646a3d63fa9 172.25.0.8 slots 7002 slots: [5461-10922] (5462 slots) master 1 additional replica (s) S: 2275c996f25a8815342e2435af073eb29565778b 172.25.0.10 slots 7005 slots: (0 slots) slave replicates 9936d3690d971eccfc8b8ed43c5defc66f318454S: b7b6fa6a4766c32c5d42d759548d6fcdf2b9159b 172.25.0.9 slots 7004 slots: (0 slots) slave replicates e5f687462a0c47f51c3abf4b8d77d646a3d63fa9 [OK] All nodes agree about slots configuration. > > Check for open slots... > Check slots coverage... [OK] All 16384 slots covered. VI. Testing:

Command:

-clusters, Assign slot docker exec-it redis-7001 redis-cli-p 7001-a 123456-cluster create 192.168.44.65 cluster create 7002 192.168.44.65 cluster create 7003 192.168.44.65 cluster create 7004 192.168.44.65 7004 192.168.44.65 7005 192.168.44.65 cluster create 7006-- cluster-replicas 1-Test docker exec-it redis-7001 redis-cli-h 192.168.44.65-p 7003-a 123456-Cary-check View cluster status cluster nodes-- view shard information cluster slots-- view cluster information cluster info

Execution result:

C:\ Users\ billow > docker exec-it redis-7001 redis-cli-h 192.168.44.65-p 7003-a 123456-c

Warning: Using a password with'- a'or'- u 'option on the command line interface may not be safe.

192.168.44.65 purl 7003 >

192.168.44.65 purl 7003 >

192.168.44.65 purl 7003 >

192.168.44.65 purl 7003 >

192.168.44.65 7003 > set name admin

-> Redirected to slot [5798] located at 172.25.0.8 purl 7002

OK

172.25.0.8 7002 > get name

"admin"

172.25.0.8 7002 > cluster nodes

2275c996f25a8815342e2435af073eb29565778b 172.25.0.10 connected 7005 slave 9936d3690d971eccfc8b8ed43c5defc66f318454 0 1648086940436 3

F69a5d0ae974816396a9d9e613c13f6ceea25de2 172.25.0.11 connected 7006 17006 slave 741c7bb537888ff97866896abb22da27c22f8eaf 0 1648086939000 1

B7b6fa6a4766c32c5d42d759548d6fcdf2b9159b 172.25.0.9 connected 7004 slave e5f687462a0c47f51c3abf4b8d77d646a3d63fa9 0 1648086939710 2

741c7bb537888ff97866896abb22da27c22f8eaf 172.25.0.6 connected 7001mm 17001 master-0 16480869393992 1

E5f687462a0c47f51c3abf4b8d77d646a3d63fa9 172.25.0.8 connected 7002mm 17002 myself,master-0 1648086939000 2 connected 5461-10922

9936d3690d971eccfc8b8ed43c5defc66f318454 172.25.0.7 connected 7003 connected 17003 master-0 1648086938868 3

172.25.0.8 purl 7002 >

172.25.0.8 purl 7002 >

172.25.0.8 purl 7002 >

172.25.0.8 purl 7002 >

172.25.0.8 purl 7002 >

172.25.0.8 7002 > cluster slots

1) 1) (integer) 0

2) (integer) 5460

3) 1) "172.25.0.6"

2) (integer) 7001

3) "741c7bb537888ff97866896abb22da27c22f8eaf"

4) 1) "172.25.0.11"

2) (integer) 7006

3) "f69a5d0ae974816396a9d9e613c13f6ceea25de2"

2) 1) (integer) 5461

2) (integer) 10922

3) 1) "172.25.0.8"

2) (integer) 7002

3) "e5f687462a0c47f51c3abf4b8d77d646a3d63fa9"

4) 1) "172.25.0.9"

2) (integer) 7004

3) "b7b6fa6a4766c32c5d42d759548d6fcdf2b9159b"

3) 1) (integer) 10923

2) (integer) 16383

3) 1) "172.25.0.7"

2) (integer) 7003

3) "9936d3690d971eccfc8b8ed43c5defc66f318454"

4) 1) "172.25.0.10"

2) (integer) 7005

3) "2275c996f25a8815342e2435af073eb29565778b"

172.25.0.8 7002 > cluster info

Cluster_state:ok

Cluster_slots_assigned:16384

Cluster_slots_ok:16384

Cluster_slots_pfail:0

Cluster_slots_fail:0

Cluster_known_nodes:6

Cluster_size:3

Cluster_current_epoch:6

Cluster_my_epoch:2

Cluster_stats_messages_ping_sent:906

Cluster_stats_messages_pong_sent:911

Cluster_stats_messages_meet_sent:1

Cluster_stats_messages_sent:1818

Cluster_stats_messages_ping_received:911

Cluster_stats_messages_pong_received:906

Cluster_stats_messages_received:1817

VII. Manual expansion

Add two new nodes for manual expansion

File name: add-redis-docker.yml

Version: '3'services: redis-7007: image: redis:6 container_name: redis-7007 command: ["redis-server" "/ usr/local/etc/redis/redis.conf"] volumes: -. / 7007/conf/redis.conf:/usr/local/etc/redis/redis.conf -. / 7007/data:/data ports:-"7007 7007/conf/redis.conf:/usr/local/etc/redis/redis.conf 7007"-"17007 7007/conf/redis.conf:/usr/local/etc/redis/redis.conf 17007" environment: # set the time zone to Shanghai Otherwise, there will be a problem with the time-TZ=Asia/Shanghai logging: options: max-size: '100m' max-file:' 10' redis-7008: container_name: redis-7008 -. / 7008/conf/redis.conf:/usr/local/etc/redis/redis.conf -. / 7008/data:/data-"7008max-size 7008"-"17008virtual 17008" "networks: default: external: name: learn_shop

Execute the command:

Docker-compose-f add-redis-docker.yml up

8. Add master / slave node 1, add master node-enter any node docker exet-it redis-7001 bash-- add master node (192.168.44.65 docker exet 7001-a 123456 this can be any existing node, mainly used to obtain cluster information) redis-cli-cluster add-node 192.168.44.65 redis-cli 7007 192.168.44.65 redis-cli 7001-a 123456

Results:

Root@aa1e004c00ff:/data# redis-cli-- cluster add-node 192.168.44.65 7007 192.168.44.65 purl 7001-a 123456

Warning: Using a password with'- a'or'- u 'option on the command line interface may not be safe.

> Adding node 192.168.44.65 to cluster 7007 192.168.44.65

> Performing Cluster Check (using node 192.168.44.65)

M: 741c7bb537888ff97866896abb22da27c22f8eaf 192.168.44.65:7001

Slots: [0-5460] (5461 slots) master

1 additional replica (s)

S: 2275c996f25a8815342e2435af073eb29565778b 172.25.0.6:7005

Slots: (0 slots) slave

Replicates 9936d3690d971eccfc8b8ed43c5defc66f318454

M: 9936d3690d971eccfc8b8ed43c5defc66f318454 172.25.0.8:7003

Slots: [10923-16383] (5461 slots) master

1 additional replica (s)

S: f69a5d0ae974816396a9d9e613c13f6ceea25de2 172.25.0.11:7006

Slots: (0 slots) slave

Replicates 741c7bb537888ff97866896abb22da27c22f8eaf

S: b7b6fa6a4766c32c5d42d759548d6fcdf2b9159b 172.25.0.9:7004

Slots: (0 slots) slave

Replicates e5f687462a0c47f51c3abf4b8d77d646a3d63fa9

M: e5f687462a0c47f51c3abf4b8d77d646a3d63fa9 172.25.0.7:7002

Slots: [5461-10922] (5462 slots) master

1 additional replica (s)

[OK] All nodes agree about slots configuration.

> Check for open slots...

> Check slots coverage...

[OK] All 16384 slots covered.

>

[OK] New node added correctly.

View the primary node that you just added:

127.0.0.1 cluster nodes741c7bb537888ff97866896abb22da27c22f8eaf 7001 > 172.25.0.10 cluster nodes741c7bb537888ff97866896abb22da27c22f8eaf 7001mm 17001 myself Master-0 1648104789000 1 connected 0-54602275c996f25a8815342e2435af073eb29565778b 172.25.0.6 slave 9936d3690d971eccfc8b8ed43c5defc66f318454 0 1648104789523 3 connected6f0c7d0ae166717d645e84b48b72b9706c7c758a 172.25.0.13 54602275c996f25a8815342e2435af073eb29565778b 7007 "17007 master-0 1648104790133 0 connected9936d3690d971eccfc8b8ed43c5defc66f318454 172.25.0.88003" 17003 master-016484790546 3 connected 10923-16383f69a5d0ae974816396a9d9e613c13f6ceea25de2 172.0.11 Race 7006 "17006 slave 741c7bb537888ff97866896abb22da27c22f8eaf 0 1648104790000 1 connectedb7b6fa6a4766c32c5d42d759548d6fcdf2b9159b 172.25.0.9 Rod 7004" 17004 slave e5f687462a0c47f51c3abf4b8d77d646a3d63fa9 0 1648104790000 2 connectede5f687462a0c47f51c3abf4b8d77d646a3d63fa9 172.25.0.7 700214002 master-0 1648104791062 connected 5461-109222, Add Slave Node-enter any Node docker exet-it redis-7001 bash-- add Slave Node (192.168.44.65 7001-a 123456 this can be any existing node Mainly used to obtain cluster information) (6f0c7d0ae166717d645e84b48b72b9706c7c758a is the just added master node id) redis-cli-- cluster add-node-- cluster-slave-- cluster-master-id 6f0c7d0ae166717d645e84b48b72b9706c7c758a 192.168.44.65 redis-cli 7008 192.168.44.65 redis-cli 7001-a 123456

Results:

127.0.0.1 7001 > cluster nodes

741c7bb537888ff97866896abb22da27c22f8eaf 172.25.0.10 connected 7001mm 17001 myself,master-0 1648105151000 1 connected 0-5460

2275c996f25a8815342e2435af073eb29565778b 172.25.0.6 connected 7005 slave 9936d3690d971eccfc8b8ed43c5defc66f318454 0 1648105154016 3

6f0c7d0ae166717d645e84b48b72b9706c7c758a 172.25.0.13 connected 7007 master-0 1648105152000 0

9936d3690d971eccfc8b8ed43c5defc66f318454 172.25.0.8 connected 7003 17003 master-0 1648105153000 3 connected 10923-16383

F69a5d0ae974816396a9d9e613c13f6ceea25de2 172.25.0.11 connected 7006 17006 slave 741c7bb537888ff97866896abb22da27c22f8eaf 0 1648105152000 1

6478c692a149130d56538aea69b54d2abc1c98b4 172.25.0.12 connected 7008 slave 6f0c7d0ae166717d645e84b48b72b9706c7c758a 0 1648105152000 0

B7b6fa6a4766c32c5d42d759548d6fcdf2b9159b 172.25.0.9 connected 7004 slave e5f687462a0c47f51c3abf4b8d77d646a3d63fa9 0 1648105153599 2

E5f687462a0c47f51c3abf4b8d77d646a3d63fa9 172.25.0.7 connected 7002mm 17002 master-0 1648105153000 2 connected 5461-10922

IX. Assign slots

The newly added master-slave node cannot be used because no slot has been allocated

Rebalance balances the number of cluster nodes slot

Syntax:

Rebalance host:port--weight-- auto-weights--threshold-- use-empty-masters--timeout-- simulate--pipeline host:port: this is a required parameter, which is used to obtain the entire cluster information from one node, which is equivalent to the entry for obtaining cluster information. -- weight: the weight of the node, in the format of node_id=weight. If you need to assign weights to multiple nodes, you need to add multiple-- weight parameters, that is,-- weight b31e3a2e=5-- weight 60b8e3a1power5 NodeSecretid can be the prefix of the node name, as long as you ensure that the number of prefix bits can uniquely distinguish the node. Nodes that do not pass-weight default to 1. Auto-weights: this parameter is not used in the rebalance process. -- threshold: the rebalance operation will be performed only if the slot threshold of the node to be migrated exceeds the threshold. The specific calculation method can be found in the fourth step of the rebalance command flow below. -- whether use-empty-masters:rebalance considers master without nodes. By default, master without assigned slot nodes does not participate in rebalance. Set-- use-empty-masters allows nodes without assigned slot to participate in rebalance. -- timeout: sets the timeout for the migrate command. -- simulate: set this parameter to simulate the rebalance operation and prompt the user which slots will be migrated without actually performing the migration operation. -- pipeline: like the pipeline parameter of reshar, define the number of key fetched by the cluster getkeysinslot command at a time. If not passed, the default value is 10. -- allocation slot (192.168.44.65 cluster-threshold 7001-a 123456 this can be any existing node and is mainly used to obtain cluster information) redis-cli-- cluster rebalance-- cluster-threshold 1-- cluster-use-empty-masters 192.168.44.65 cluster-threshold 7001-a 123456

If you need to perform a simulation to add:-- cluster-simulate

Results:

Root@aa1e004c00ff:/data# redis-cli-- cluster rebalance-- cluster-threshold 1-- cluster-use-empty-masters 192.168.44.65 cluster-threshold 7001-a 123456

Warning: Using a password with'- a'or'- u 'option on the command line interface may not be safe.

> Performing Cluster Check (using node 192.168.44.65)

[OK] All nodes agree about slots configuration.

> Check for open slots...

> Check slots coverage...

[OK] All 16384 slots covered.

Rebalancing across 4 nodes. Total weight = 4.00

Moving 1366 slots from 172.25.0.7:7002 to 172.25.0.13:7007

#

Moving 1365 slots from 172.25.0.8:7003 to 172.25.0.13:7007

#

Moving 1365 slots from 192.168.44.65:7001 to 172.25.0.13:7007

#

View node information:

127.0.0.1 7001 > cluster nodes

741c7bb537888ff97866896abb22da27c22f8eaf 172.25.0.10 connected 7001 17001 myself,master-0 1648105892000 1 connected 1365-5460

2275c996f25a8815342e2435af073eb29565778b 172.25.0.6 connected 7005 slave 9936d3690d971eccfc8b8ed43c5defc66f318454 0 1648105893536 3

6f0c7d0ae166717d645e84b48b72b9706c7c758a 172.25.0.13 6f0c7d0ae166717d645e84b48b72b9706c7c758a 7007 17007 master-0 1648105894566 8 connected 0-1364 5461-6826 10923-12287

9936d3690d971eccfc8b8ed43c5defc66f318454 172.25.0.8 connected 7003 17003 master-01648105893000 3 connected 12288-16383

F69a5d0ae974816396a9d9e613c13f6ceea25de2 172.25.0.11 connected 7006 17006 slave 741c7bb537888ff97866896abb22da27c22f8eaf 0 1648105893000 1

6478c692a149130d56538aea69b54d2abc1c98b4 172.25.0.12 connected 7008 17008 slave 6f0c7d0ae166717d645e84b48b72b9706c7c758a 0 1648105894576 8

B7b6fa6a4766c32c5d42d759548d6fcdf2b9159b 172.25.0.9 connected 7004 slave e5f687462a0c47f51c3abf4b8d77d646a3d63fa9 0 1648105893000 2

E5f687462a0c47f51c3abf4b8d77d646a3d63fa9 172.25.0.7 connected 7002 "17002 master-0 1648105894566 2

10. Cluster test root@aa1e004c00ff:/data# redis-cli-p 7001-a 123456-cWarning: Using a password with'- a'or'- u 'option on the command line interface may not be safe.127.0.0.1:7001 > set 1 1-> Redirected to slot [9842] located at 172.25.0.7:7002OK172.25.0.7:7002 > set 22-> Redirected to slot [5649] located at 172.25.0.13:7007OK172.25.0.13:7007 > set 3 3- > Redirected to slot [1584] located at 172.25.0.10:7001OK172.25.0.10:7001 > set 4-> Redirected to slot [14039] located at 172.25.0.8:7003OK172.25.0.8:7003 > set 55-> Redirected to slot [9974] located at 172.25.0.7:7002OK172.25.0.7:7002 > set 6 6-> Redirected to slot [5781] located at 172.25.0.13:7007OK172.25.0.13:7007 > set 7 7- > Redirected to slot [1716] located at 172.25.0.10:7001OK172.25.0.10:7001 > 172.25.0.10 get 7001 > 172.25.0.10 get 7001 > 172.25.0.10 get 1-> Redirected to slot [9842] located at 172.25.0.7 get 7002 "1" 172.25.0.7 VR 7002 > get 2-> Redirected to slot [5649] located at 172.25.0.1315 7007 "2" 172.25.0 .13 located at 7007 > get 3-> Redirected to slot [1584] located at 172.25.0.10 located at 7001 "3" 172.25.0.10 located at 7001 > get 4-> Redirected to slot [14039] located at 172.25.0.8 located at 7003 "4" 172.25.0.8 get 7003 > get 5-> Redirected to slot [9974] located at 172.25.0.7 purge 7002 "5" 172.25.0.7 located at 7002 > get 6-> Redirected to slot [5781] located at 172.25.0 .13 located at 7007 "6" 172.25.0.13 located at 7007 > located at 7-> located at 7001 "7" 11, Common command Cluster cluster info: print cluster information cluster nodes: list all nodes currently known to the cluster (node) And information about these nodes. Node cluster meet: add the node specified by ip and port to the cluster and make it part of the cluster. Cluster forget: removes the node specified by node_id from the cluster. Cluster replicate: sets the current node as the slave node of the node specified by node_id. Cluster saveconfig: save the node configuration file to your hard drive. Slot cluster addslots [slot.]: assign (assign) one or more slot to the current node. Cluster delslots [slot.]: removes the assignment of one or more slots to the current node. Cluster flushslots: removes all slots assigned to the current node, making the current node a node with no slots assigned. Cluster setslot node: assign the slot slot to the node specified by node_id. If the slot is already assigned to another node, let the other node delete the slot > before assigning it. Cluster setslot migrating: migrate the slot slot of this node to the node specified by node_id. Cluster setslot importing: import slot slot into this node from the node specified by node_id. Cluster setslot stable: cancel the import (import) or migration (migrate) of slot slot. Key cluster keyslot: calculates which slot the key key should be placed on. Cluster countkeysinslot: returns the number of key-value pairs currently contained in slot slot. Cluster getkeysinslot: return the keys in the count slot slots above is all the content of the article "how to install redis clusters in docker compose". Thank you for reading! I believe you will gain a lot after reading this article. The editor will update different knowledge for you every day. If you want to learn more knowledge, please pay attention to the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.