Video Conference Device Comparsion between Polycom Vs Tandberg

by Posted in 2. IT Security (資訊保安), 2.2 IT Security Operation (保安操作) Tagged 2 Comments

Bandwidth Optimization – Polycom can send 720HD at lower speeds but Tandberg can send more than CIF4CIF7201080, which I’ll take that over the lower HD speeds any day.
Central Admin – Tandbery is great for admin (if you have several hundred end-point, you definitely choose Tandbery. Polycom was beta and their provisioning wasn’t ready yet.
End User Usability – This is real close and I give favor to Polycom.
Reliability/Maintenance – I once had some one tell me Polycom is like Mircosoft and Tandberg is like Cisco. Polycom looks good but has bugs while Tandberg might not be as flashy but is rock solid. I’d pick Tandberg.
Cost – if you could compare apples to apples they’d be close but looking at just the bottom line Polycom is the winner.

Conclusion: If you have only a few connection VC points and have a loose network control (e.g. not using Cisco device), I suggest to use Polycom because it is easy to setup. For company with many VC end-points (say > 50), I will prefer to choose Tandberg which is more security and easy to manage.

Diary of IT Guy in Factory – poor Dongguan beggar

by Posted in Diary of IT Man(IT人在工廠日記) Leave a comment

When I go and return from China factory and pass across the china border, I always see some poor beggers on street. Most are disabled, e.g. without arm or leg, I know that this kind of disabled is human-made. Those beggers was controlled and forced by bad guys. They are living in a very very poor life. Please China Government help those beggers.

————–

http://www.youtube.com/watch?v=jKW2pQElPYA

Odoo System Schedule Backup and Restore Database Setup

by Posted in 3. IT Application (應用軟件), 3.1 ERP System (資源管理) Tagged

This module will be work internally as command line interface (for Linux only) through linux crontab to backup and restore database.

  1. Backup database
  2. Restore as database _TEST
  3. Update image (i.e., with test logo) to _TEST

Just install this module, and it should work. Setup schedule time as you need it. Note: Itself, can also be used as scheduler instead of normal scheduler in OpenERP (you will see this backup and restore as one example).

Features

  • Add, Modify, Delete schedule
  • Direct process through command line interface

Setup Procedure

Menu -> Setting/Technical/Scheduler/Crontab Configuration

Fields:

  1. Crontab Name – name of crontab

  2. Description – more information

  3. Scheduling – crontab scheduling

    3.1 Minute: 0-59

    3.2 Hour: 0-23

    3.3 Day: 1-31

    3.4 Month: 1-12

    3.5 Weekday: 0-6, where 0 = Sunday

  4. Execute Directory – OpenERP’s root path to be used for log file, Temp File, DB Backup File and etc (depends on type of program)

  5. Command – command to run the program in command line interface pattern, require full path.

  6. Active – when True, will create crontab scheduler in OS. When False will delete it.

  7. Status

    7.1 Draft

    7.2 Confirmed

    7.3 Cancelled

  8. Attach File – Additional files, to be used in process (optional)

Note: crontab scheduler will be created only when State = Confirmed and Active = True

Technical Detail

Backup Database Script:

Use script, db_backup.py (written in Python)

 db_backup.py -u -d -p

Example:

 ‘/home/buasri/workspace/ecosoft_official_addons/ecosoft-addons/crontab_config/db_backup.py’ -u openerp -d TT -p ‘/home/buasri/workspace/openerp_tt’>>’/home/buasri/workspace/openerp_tt/crontab_oe.log’

Process:

  1. Create backup database as _dbbackup-YYYY-MM-DD hh:mm:ss.dmp
  2. Create file oe_db_last_bkup.txt to be used for restoration

Restore Database Process:

Use script, db_restore.py (written in Python)

 db_restore.py -u -d -p

-i id of crontab in OpenERP, from table crontab_config -c id of Company in OpenERP, from table res_company

Example:

 ‘/home/buasri/workspace/ecosoft_official_addons/ecosoft-addons/crontab_config/db_restore.py’ -u openerp -d TT_TEST -p ‘/home/buasri/workspace/openerp_tt’>>’/home/buasri/workspace/openerp_tt/crontab_oe.log’

Process

  1. Disconnect database to be restored
  2. Delete database
  3. Create new database
  4. Restore it.
  5. Read attached logo file
  6. Resize logo file
  7. Update logo file