I quite confuse about VMware Product Name between vCloud and vRelized. VMware renamed the product on VMWorld 2014. Here's the summary of VMware Product.

ช่วง 5 ปีให้หลังจะได้ยินคำว่า DR Site (Disaster Recovery Site) บ่อยมาก และเริ่มมีบริษัทสนใจที่จะ implement DR Site หลังจากช่วงกีฬาสีและช่วงน้ำท่วม แต่ยังไม่รู้ว่า DR Site ควรจะต้องทำยังไง และต้องทำอะไรบ้าง ใน Entry นี้จึงอธิบายวิธีการกันก่อน

จะมี 3 คำที่ต้องคุ้นเคยก่อน

• Disaster Recovery
• Business Continuity 
• Disaster Recovery / Business Continuity Plan

Disaster Recovery

• เป้าหมาย เพื่อฟื้นฟู Business Process ที่วิกฤติ ที่ทำให้การดำเนินการธุรกิจหยุดชะงัก เช่น ERP 
• Disaster Recovery เป็นส่วนหนึ่งของ Business Continuity
• โฟกัสไปที่ Data Recovery
• ช่วงเวลาการฟื้นฟู ไม่เกิน 30 วัน
• Solution : Hot Site Recovery

Business Continuity 

• เป้าหมาย เพื่อฟื้นฟูธุรกิจให้กลับเป็นสถานะเดิม เช่น การทำงาน, process (คือเคยทำงานแบบใด ก็ทำงานแบบปกติ)
• โฟกัสไปที่ การทำให้เป็นปกติ
• ช่วงเวลาการฟื้นฟู 30 วันเป็นต้นไป
• Solution : New Building, New Device

Disaster Recovery / Business Continuity Plan

• เป็น วิธีการ, Process, กระบวนการ ที่ทำให้เกิดความสูญเสียให้น้อยที่สุด 
• เป็น Guideline หรือกิจกรรมที่ต้องทำในการฟื้นฟู
• เขียน Test Plan ที่ทำให้การฟื้นฟูเป็นไปตามเวลาที่กำหนดไว้ 

I have heard docker for long time. Today I listen presentation, then try to setup docker in OS X environment. Here's the step of installation.

1. Download Boot2Docker, then install pkg
2. Open Boot2Docker in Application
   

   bash
   unset DYLD_LIBRARY_PATH ; unset LD_LIBRARY_PATH
   mkdir -p ~/.boot2docker
   if [ ! -f ~/.boot2docker/boot2docker.iso ]; then cp /usr/local/share/boot2docker/boot2docker.iso ~/.boot2docker/ ; fi
   /usr/local/bin/boot2docker init 
   /usr/local/bin/boot2docker up 
   $(/usr/local/bin/boot2docker shellinit)
   docker version
   Last login: Thu Mar  5 19:08:10 on console
   MacBook-Pro:~ joezine$ bash
   bash-3.2$ unset DYLD_LIBRARY_PATH ; unset LD_LIBRARY_PATH
   bash-3.2$ mkdir -p ~/.boot2docker
   bash-3.2$ if [ ! -f ~/.boot2docker/boot2docker.iso ]; then cp /usr/local/share/boot2docker/boot2docker.iso ~/.boot2docker/ ; fi
   bash-3.2$ /usr/local/bin/boot2docker init 
   Generating public/private rsa key pair.
   Your identification has been saved in /Users/joezine/.ssh/id_boot2docker.
   Your public key has been saved in /Users/joezine/.ssh/id_boot2docker.pub.
   The key fingerprint is:
   55:2d:82:f3:01:e6:25:71:5b:1f:91:75:95:36:57:bb joezine@MacBook-Pro
   The key's randomart image is:
   +--[ RSA 2048]----+
   |        =+o o.o+O|
   |       oo+o+..o=+|
   |        .ooo .o.o|
   |         ..     .|
   |        S      E |
   |                 |
   |                 |
   |                 |
   |                 |
   +-----------------+
   /usr/local/bin/boot2docker up 
   $(/usr/local/bin/boot2docker shellinit)
   docker version
   
   
   
   bash-3.2$ /usr/local/bin/boot2docker up 
   Waiting for VM and Docker daemon to start...
   ........................ooooooooooooooooooooooo
   Started.
   Writing /Users/joezine/.boot2docker/certs/boot2docker-vm/ca.pem
   Writing /Users/joezine/.boot2docker/certs/boot2docker-vm/cert.pem
   Writing /Users/joezine/.boot2docker/certs/boot2docker-vm/key.pem
   
   To connect the Docker client to the Docker daemon, please set:
       export DOCKER_HOST=tcp://192.168.59.103:2376
       export DOCKER_CERT_PATH=/Users/joezine/.boot2docker/certs/boot2docker-vm
       export DOCKER_TLS_VERIFY=1
   
   bash-3.2$ $(/usr/local/bin/boot2docker shellinit)
   Writing /Users/joezine/.boot2docker/certs/boot2docker-vm/ca.pem
   Writing /Users/joezine/.boot2docker/certs/boot2docker-vm/cert.pem
   Writing /Users/joezine/.boot2docker/certs/boot2docker-vm/key.pem
   bash-3.2$ docker version
   Client version: 1.5.0
   Client API version: 1.17
   Go version (client): go1.4.1
   Git commit (client): a8a31ef
   OS/Arch (client): darwin/amd64
   Server version: 1.5.0
   Server API version: 1.17
   Go version (server): go1.4.1
   Git commit (server): a8a31ef

3. You may download image from Docker's repository by using this command
   

    docker pull centos:7

4. Try to run "docker run hello-world"
   

   bash-3.2$ docker run hello-world
   Hello from Docker.
   This message shows that your installation appears to be working correctly.
   
   To generate this message, Docker took the following steps:
    1. The Docker client contacted the Docker daemon.
    2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
       (Assuming it was not already locally available.)
    3. The Docker daemon created a new container from that image which runs the
       executable that produces the output you are currently reading.
    4. The Docker daemon streamed that output to the Docker client, which sent it
       to your terminal.
   
   To try something more ambitious, you can run an Ubuntu container with:
    $ docker run -it ubuntu bash
   
   For more examples and ideas, visit:
    http://docs.docker.com/userguide/

I just know that Docker built in GO

I have not much time. vSphere 6 was released last month. I would like to summarize the new highlight features of ESXi 6.0. Actually, you may read them from other sites but I would like to recap on my blog.

ESXi 6.0

New Features

• VDPA is part of vSphere Essentials Plus or higher vSphere editions, vSOM editions, and all vCloud Suite editions (Source)
• Instant Clone (It clones a running VM in second)
• VMware integrate with OpenStack (VIO)
• Virtual SAN (VSAN) 6.0 (More info)
• Virtual Volumes (available on vSphere Standard Edition and above and above as well as vSphere ROBO editions (ROBO)
  Note : vSphere ROBO Editions will replace vSphere Essential Editions soon
• vSphere APIs for IO Filtering
• NFS 4.1 support
• VM Component Protection (VMCP)
• Virtual DataCenter
• NVIDIA Grid vGPU support
• ESXi 6.0 can out of the box installed on all Mac Platform

Enhanced features

• Fault Tolerance support for 4 vCPU
• vMotion Enhancements 
  • vMotion across vCenter 
  • vMotion across Virtual Switches : Virtual Standard Switch (VSS), Virtual Distributed Switches (VDSs)
  • vMotion using routed vmotion networks
  • Long-distance vMotion for use cases such as:
    • Permanent migration (often for Datacenter expansions, acquisitions, consolidations)
    • Disaster avoidance
    • SRM and disaster avoidance testing
    • Multi-site capacity utilization
    • Follow-the-sun scenarios
    • Onboarding onto vSphere-based public cloud (including VMware vCloud Air)
• Better Microsoft clustering support
• Hot-add RAM now vNUMA aware
• WDDM 1.1 GDI acceleration features

Networking

• You can set a guaranteed bandwidth 
• VMware stopped selling and supporting Cisco Nexus 1000v viritual switch but Cisco will continue to support

vSphere Replication

• VR Traffic can be isolated from other vSphere host traffic
• Compression can be enabled. It is disabled by default
• Uses FastLZ compression llibraries

VMware vCenter 6.0

• Microsoft clustering support, not just the database
• Fault Tolerance is not supported for vCenter Server on Windows and the vCenter appliance
• vMotion across vCenter. Requires vSphere 6.0 on both ends
• Long distance vMotion increased latency supports up to 100ms RTTs
• Windows install supports Postgres and External SQL and Oracle DBs
• vCSA supports embedded Postgres and external Oracle DBs

VMware VM Component Protection (VMCP)

Imagin fiber channel controller failure, VMware HA is now able to detect the loss of storage connection and restart virtual machine on other hosts

Others:

• Edition Comparison
• vCenter Server
• Certification Roadmap

Flickr is the best tool for backing up photos. The one of Flickr's problems is, it's very difficult to view overall photos. When I would like to find them without searching, I have to click each page. It takes time so much. I just see that Flickr releases Camera Roll. I love this feature so much because I can view overall photos with small thumbnail. So I can find photos quickly.

I have not seen new feature for long time. I hope flickr will release many features later.