::: Virtual Aleph ::: Virtualization Techniques: #VMworld Barcelona Day 0 (part 4): #HOL-SDC-1420 - #OpenStack with #VMware

VMworld 2017 Banner

VMworld 2017 Banner
VMworld 2017 Las Vegas

13 October, 2014

#VMworld Barcelona Day 0 (part 4): #HOL-SDC-1420 - #OpenStack with #VMware

Hi all,
my relationship with the HOLs continue.
I'm doing right now HOL-SDC-1420 - OpenStack with VMware, but the massive concurrency of Labs going in parallel give me the opportunity to write this post, in the meanwhile the two instances of VM launched with OpenStack are respawning.

OpenStack is an open source software that delivers a framework of services for API based infrastructure consumption. OpenStack framework requires hardware or software based infrastructure components and management tools to build a functional OpenStack cloud. The "plug-in" architecture of OpenStack services enables various vendors (such as VMware) to integrate their infrastructure solutions (such as vSphere and NSX) to deliver an OpenStack cloud.

The VMware NSX Appliance is an important networking feature to understand in this topology. The appliance is a separate installation and not visible in the vSphere Web Client.
The NSX appliance provides Networking Services such as L2 networks, L3 routing, Floating IPs, Security Groups and more. OpenStack delivers these services through the Neutron service and API’s.

VOVA is an OVF-based virtual appliance that provides "OpenStack in a box”. VOVA runs all OpenStack services such as Nova, Glance, Cinder, Neutron, Keystone and Horizon in an Ubuntu Linux appliance. VOVA is not a commercial product, it is a learning tool released by VMware engineers to allow VMware customers to try out OpenStack integration with vSphere

If you would like to download and run VOVA in your own environment, please copy down the following link: http://bit.ly/16Ue7qn

In a real deployment scenario, the Cloud Administrator would be responsible for installing and maintaining OpenStack. 

In OpenStack, users are grouped in containers called projects. These projects are effectively tenants in the OpenStack cloud environment. Each project has an assigned quota of compute, network and storage resources that are shared by all users in that project. Projects are isolated from each other, that is, users in one project can't see the users and resources of other projects.

This lab is quite long and impossible to complete in the given time, nevertheless, the co-operation between Openstack and VMware real good stated that things like DRS, HA, FT, etc. will continue to work, making this solution very attractive for enterprise administrators wanting to benefit from open orchestration (OpenStack) without sacrificing VMware's unmatched enterprise-level functions.

cheers
\mf