[orchagent]: Remove updating APP_DB port oper_status logic from orchagent

[stcheng]

Signed-off-by: Shuotian Cheng [email protected]

[stcheng]

This is to address the issue sonic-net/sonic-buildimage#456.

The logic is already integrated in portsyncd which will update the oper_stauts of a port once the port changes its oper_status.

[stcheng]

it is better to use orchagent to update the oper_status instead of using portsyncd
however, orchagent only gets oper_status of front panel ports notification from ASIC
vlan and port channel oper_status should still be updated from portsyncd

[stcheng]

root@str-s6000-acs-11:/home/admin# ifdown Ethernet8
root@str-s6000-acs-11:/home/admin# redis-cli
127.0.0.1:6379> hgetall PORT_TABLE:Ethernet8
 1) "lanes"
 2) "37,38,39,40"
 3) "alias"
 4) "fortyGigE0/8"
 5) "admin_status"
 6) "down"
 7) "mtu"
 8) "1500"
 9) "oper_status"
10) "down"
root@str-s6000-acs-11:/home/admin# ifup Ethernet8
device Ethernet8 is already a member of a bridge; can't enslave it to bridge Vlan1000.
root@str-s6000-acs-11:/home/admin# redis-cli
127.0.0.1:6379> hgetall PORT_TABLE:Ethernet8
 1) "lanes"
 2) "37,38,39,40"
 3) "alias"
 4) "fortyGigE0/8"
 5) "admin_status"
 6) "up"
 7) "mtu"
 8) "1500"
 9) "oper_status"
10) "up"

[lguohan]

can you update the commit message?

[stcheng]

commit message:

- Front panel ports' oper_status should be notified from the SAI instead of getting
  it from kernel via portsyncd. Thus in this commit, oper_status is removed from the
  portsyncd.

- VLAN and LAG oper_status on the contrary need to be updated from the protocol daemon,
  the kernel and the teamd.