5. ❖ Traditional Infrastructure
➢ Risks on many manual configurations to the infrastructure
➢ With many Vendors, different approaches
❖ Cloud Infrastructure
➢ More than 50 volume attachment zoning processes when evacuating if one compute is down
Problems on mixing storage resources
6. Mapping LUN to a baremetal
❖ Zoning on SAN Switches
● Get WWPN, WWNN of a host
● Add zone
● Add zoneset
➢ Twice on fabric
7. ❖ Export LUN
● Create LUN
● Create Host, Initiator
● Export LUN to baremetal
Mapping LUN to a baremetal
9. Components
★ OpenStack cluster with 2 of 6 core services: Cinder and Keystone
★ Some tools to store WWN information for thoudsands nodes
★ A dashboard to manage all volumes and storage resources
❖ Made of 3
10. Source of trust for thousands nodes
❖ Viettel DCIM
● Store all server inventory, including HBA
card information
● APIs to get WWN information
11. Manage volumes and storage resources
❖ VStorage Administration & Automation - VSA2
● Volume CRUD
● Allow attach/detach Cinder volumes to
baremetals with WWN information
collected from DCIM
12. Applying the solution
❖ For physical infrastructure
● Simplest provisioning block storage for Baremetals
● Minimum risks by removing any manual configurations on Switches and Storages
❖ To OpenStack Cloud infrastructure
● Pre-persistent zoning for Computes and Storages by attaching a tiny volume
● Remove zoning at Cinder configurations
13. Tunning OpenStack
❖ With the removal of zoning on cinder volume configuration
● Nearly also remove block device mapping time
● Save time when action on Compute Instances like creating, deleting, migrating and
specially evacuating
➔ Successfully evacuated 40 VMs using SAN backend in one Compute at the same time
14. Vision for the solution
❖ Make VSA2 become greater
★ “docker-compose up -d” initiate the whole stack
★ Can do more actions to SAN Switches
★ Be an unified management solution for operating any SANs
★ Cinder volume auto implementation when adding more Storage resources
★ ….