Category Archives: OpenStack Consumption

VMware Integrated OpenStack(VIO) announced the official support for Barbican, OpenStack secrets manager, in version 5.1. With Barbican, cloud Operators can offer Key Management as a service by leveraging Barbican API and command line(CLI) to manage X.509 certificates, keys, and passwords. Basic Barbican workflow is relatively simple – invoke the secrets-store plugin to encrypt a secret on the store and decrypt a secret on retrieval. In addition to generic secrets management, some OpenStack projects integrate with Barbican natively to provide enhanced security on top of its base offering. This blog will introduce Barbican consumption and operation maintenance through the use of Neutron Load Balancer as a Service (LBaaS).

Understanding Policies

Barbican scopes the ownership of a secret at the OpenStack project level. For each API call, OpenStack will check to ensure the project ID of the token matches the project ID stored as the secret owner. Further, Barbican uses roles and policies to determine access to secrets. Following roles are defined in Barbican::

Admin – Project administrator. This user has full access to all resources owned by the project for which the admin role is scoped.

Creator – Users with this role are allowed to create and delete resources. Users with this role cannot delete other user’s resources managed within same project. They are also allowed full access to existing secrets owned by the project in scope.

Observer – Users with this role are allowed access to existing resources but are not allowed to upload new secrets or delete existing secrets.

Audit – Users with this role are only allowed access to the resource metadata. So users with this role are unable to decrypt secrets

VIO 5.1 ships with “admin” and “creator” role out of the box. A project member must be assigned with the creator role to consume barbican. Based on the above roles, Barbican defines a set of rules or policies for access control. Only operations specified by the matching rule will be permitted.

While the policy framework works well, but secrets management is never one size fits all, and there are limitations with the policy framework if fine-grain control is required. Scenarios such as grant specific user access to a particular secret or upload a secret for which only the uploader has access needs OpenStack ACLs. Please refer to ACL API User Guide for full details.

Supported Plugin

The Barbican key manager service leverages secret-store plugins to allow authorized users to store secrets. VIO 5.1 supports two type of plugins, simple crypto and KMIP enabled. Only a single plugin can be active for a VIO deployment. Secret stores can be software-based, such as a software token, or hardware devices such as a hardware security module (HSM).

Simple crypto plugin

The simple crypto plugin uses a single symmetric key, stored locally on the VIO controller in the /etc/barbican/barbican.conf file to encrypt and decrypt secrets. This plugin also leverages local Barbican database and stores user secrets as encrypted blobs in the local database. The reliance on local text file and database for storage is considered insecure, and therefore upstream community considers simple crypto plugin to be suitable for development and testing workloads only.

Secret store KMIP plugins

The KMIP plugin stores secrets securely in an external KMIP-enabled device. The Barbican database, instead of storing encrypted secrets, maintain location references of secrets for later retrieval. Client certificate-based authentication is the recommended approach to integrate the plugin with the KMIP enabled device.

Example Barbican Consumption:

One of the most commonly requested use case specific to VIO is Barbican integration with Neutron LBaaS to offer HTTPS offload. This is a five step process, we will review each step in detail.

Install KMIP server (Greenfield only)

Integrate KMIP using VIOCLI

ACL update

Workflow to create secret

Workflow to create LBaaSv2

Please note, you must leverage OpenStack API or CLI for step #4. Horizon support for Barbican is not available.

Install KMIP server

Production Barbican deployment requires a KMIP server. In a greenfield deployment, Dell EMC CloudLink is a popular solution VMware vSAN customers leverage to enable vSAN storage encryption. CloudLink includes both a key management server (KMS) as well as the ability to control, monitor and encrypt secrets across a hybrid cloud environment. Additional details on CloudLink is available from VMware solution exchange.

Integrate KMIP using VIOCLI

To integrate with CloudLink KMS or any other KMIP based secret store, simply login into the VIO OMS server and issue the following VIOCLI command;

Configure Barbican to use the KMIP plugin.

viocli barbican –secret-store-plugin KMIP

–user viouser \

–password VMware**** \

–host <KMIP host IP> \

–ca-certs /home/viouser/viouser_key_cert/ca.pem \

–certfile /home/viouser/viouser_key_cert/cert.pem \

–keyfile /home/viouser/viouser_key_cert/key.pem –port 5696

Successful completion of VIOCLI command performs following set of actions:

ACL updates based on consumption

Neutron LBaaS relies on a Barbican service account to read and push certificates and keys stored in the Barbican containers to a load balancer. The Barbican service user is an admin member of the service project, part of the OpenStack Local domain. Default Barbican security policy does not allow admin or member of one project to access secrets stored in a different project. In order for Barbican service user to access and push certificate and keys, tenant users must grant access to the service account. There are two ways to allow access:

Option 1:

1). Tenant creator gives Barbican service user access using the OpenStack ACL command. Cloud administrator needs to supply the UUID of the Barbican service account.

Repeat this command with each certificate, key, and container you want to provide Neutron access to.

Option 2:

2.) If cloud administrators are comfortable providing Neutron with access to secrets without users granting access to individual objects, cloud administrators may elect to modify the Barbican policy file. Implementing this policy change means that tenants won’t need to add the Neutron barbican service_user to every object, which makes the process of creating TERMINATED_HTTPS listeners easier. Administrators should understand and be comfortable with the security implications of this action before implementing this approach. To perform the policy change, use a custom-playbook to change the following line in the Barbican policy.json file:

From: “secret:get”: “rule:secret_non_private_read or rule:secret_project_creator or rule:secret_project_admin or rule:secret_acl_read”,

To: “secret:get”: “rule:secret_non_private_read or rule:secret_project_creator or rule:secret_project_admin or rule:secret_acl_read or role:admin”,

Workflow to Create Secret:

This step assumes you have pre-created certificates and keys. If you have not created keys and certificates before, please refer to this blog for details. To follow steps outlined below, make sure to name your output files accordingly (server.crt and server.key). To upload a certificate:

openstack secret store –name=’certificate’ \

–payload=”$(cat server.crt)” \

–secret-type=passphrase

Most of options are fairly self-explanatory, passphrase indicates a plain text. Repeat the same command for keys:

openstack secret store –name=’private_key’ \

–payload=”$(cat server.key)” \

–secret-type=passphrase

you can confirm by listing out all secrets:

Final, create a TLS container pointing to both private key and certificate secrets:

Workflow to create LBaaSv2

With Barbican service up and running, ACL configured to allow retrieval of secret keys, let’s start to create a Load balancer and upload a certificate and key from the KMS server. Load balancer creation workflow does not change with Barbican. When creating a listener, be sure to specify TERMINATED_HTTPS as the protocol, and URL of the TLS container stored in Barbican.

Please note:

If you are testing Barbican against NSX-T, NSX-MGR must be running at least version 2.2 or higher.

Written by Xiao Gao, with valuable feedbacks from Damon Li.

DNS is essential to nearly every cloud application, and it is almost unimaginable to launch any cloud service without a robust DNS implementation. Booting a VM in OpenStack takes seconds. However, for most OpenStack operators, once a VM is booted, the first step towards production is to manually create a ticket to register the IP address with the corporate DNS. This registration process can often take few days. Why give users the power to boot VM only to have them submit an IT support ticket for DNS entry? Delegating the responsibility for maintaining DNS records to the application owners, entirely based on self-service(DNSaaS), reduces the load on IT teams and gives users the power to do what they want. DNS is so fundamental to any application lifecycle, and it should just happen.

One of the most requested features from the VIO user community has been self-service for DNS records, and we are proud to deliver OpenStack Designate as part of VIO 5.0. OpenStack Designate is the OpenStack equivalent of AWS route 53. There are three ways to consume Designate in VIO 5.0:

Designate Architecture

API service – It is the consumption layer of Designate. API service is also responsible for validation of API input.

Sink – Sink is a notification event listener. It also generates simple DNS forward lookup A record based on Nova and Neutron notification events.

Central Process – Business logic handler. Central Process is responsible for the user and permission validation. It also manages access to the Designate database and request dispatch.

Pool Manager – Manages the states of the DNS servers. The Pool manager divides DNS servers into ‘Pools’ (PowerDNS, BIND9, etc.) so that zones within Designate can split across different sets of backend servers. The Pool Manager is also responsible for making sure that backend DNS servers are in sync with the Designate database.

Designate-zone-manager – A zone shard is a collection of zones allocated based on the first three characters of zone UUID. The Zone Manager handles all tasks relating to the zone shard.

Component Mapping in VIO

Designate Consumption

VIO 5.0 supports Bind9, PowerDNS (version 4+) and Infoblox back-ends. Since DNS is so foundational, there’s no such thing as greenfield for Designate. Once Designate is enabled, there are few strategies to insert Designate into your private cloud. Graham Hayes (OpenStack PTL) and a few others gave an excellent talk on this topic. You can find their talk here:

3). Consume – VIO currently does not support provider network based DNS registration, only floating IP. A recordset is created during floating association of a VM and deleted after a disassociation. Customer running BGPaaS / no-nat can leverage static records to insert entries into DNS:

openstack recordset create –records <IP> –type A <domain>

I have created a video recording to demonstrate basic consumption of Designate.

There is not a one size fits all solution to Phase II and III. Each organization may adopt different implementation strategies based on operational processes and application availability unique to their organization. Some organizations may never implement beyond phase I. You are not alone. We recommend you to consult with VMware PSO team to work out the most optimal implementation based on your unique requirements. Also, we welcome your input. Feel free to share your experience on our VIO community page, or leave a note at the end of this blog with your thoughts.

VMware today announced VMware Integrated OpenStack (VIO) 5.0. We are truly excited about our latest OpenStack distribution as VMware is one of the first companies to support and provide enhanced stability on top of the newest OpenStack Queens Release. Available in both Carrier and Data Center Editions, VIO 5.0 enables customers to take advantage of advancements in Queens to support mission-critical workloads, and adds support for the latest versions of VMware products including vSphere, vSAN, and NSX.

For our Telco/NFV customers, VIO 5.0 is about delivering scale and availability for hybrid applications across VM and container-based workloads using a single VIM (Virtual Infrastructure Manager). Also for NFV operators, VIO 5.0 will help fast track a path towards Edge computing with VIO-in-a-box, secure multi-tenant isolation and accelerated network performance using the enhanced NSX-T VDS (N-VDS). For VIO Datacenter customers, advanced security, simplified user experience, and advanced networking with DNSaaS have been on top of the wish list for many VIO customers. We are super excited to bring those features in VIO 5.0.

Heterogeneous Cluster using Node Group: Now you can have different types of worker nodes in the same cluster. Extending the cluster node profiles feature introduced in VIO 4.1, a cluster can now have multiple node groups, each mapping to a single node profile. Instead of building isolated special purpose Kubernetes clusters, a cloud admin can introduce a new node group(s) to accommodate heterogeneous applications such as machine learning, artificial intelligence, and video encoding. If resource usage exceeds the node group limit, VIO 5.0 supports cluster scaling at a node group level. With node groups, cloud admins can address cluster capacity based on application requirements, allowing the most efficient use of available resources.

Enhanced Cluster Manageability: vkube heal and ssh allow you to directly ssh into any of the nodes of a given cluster and to recover a failed cluster nodes based on ETCD state or cluster backup in the case of complete failure.

Advanced Networking:

N-VDS: Also Known as NSX-T VDS in Enhanced Data-path mode. Enhanced, because N-VDS runs in DPDK mode and allows containers and VMs to achieve significant improvements in response time, reduced network latencies and breakthrough network performance. With performance(s) similar to SR-IOV, while maintaining the operational simplicity of virtualized NICs, NFV customers can have their cake and eat it too

NSX-V Search domain: A new configuration setting in the NSX-V will enable the admin to configure a global search domain. Tenants will use this search domain if there is no other search domain set on the subnet.

NSX-T availability zone (AZ): An availability zone is used to make network resources highly available by group network nodes that run services like DHCP, L3, NAT, and others. Users can associate applications with an availability zone for high availability. In previous releases neutron AZ was supported against NSX-V, we are extending this support to the T as well.

Security and Metering:

Keystone Federation: Federated Identity provides a way to securely use existing credentials to access cloud resources such as servers, volumes, and databases, across multiple endpoints across multiple authorized clouds using a single set of credentials. VIO5 supports Keystone to Keystone (K2K) federation by designating a central Keystone instance as an Identity Provider (IdP), interfacing with LDAP or an upstream SAML2 IdP. Remote Keystone endpoints are configured as Service Providers (SP), propagating authentication requests to the central Keystone. As part of Keystone Federation enhancement, we will also support 3rd party IdP in addition to the existing support for vIDM.

Gnocchi: Gnocchi is the project name of a TDBaaS (Time Series Database as a Service) project that was initially created under the Ceilometer umbrella. Rather than storing raw data points, it aggregates them before storing them. Because Gnocchi computes all the aggregations at ingestion, data retrieval is exceptionally speedy. Gnocchi resolves performance bottlenecks in Ceilometer’s legacy architecture by providing an extremely robust foundation for the metric storage required for billing and monitoring. The legacy Ceilometer API service has been deprecated by upstream and is no longer available in Queens. Instead, the Ceilometer API and functionality has been broken out into the Aodh, Panko, and Gnocchi services, all of which are fully supported in VIO 5.0.

Default Drop Policy: Enable this feature to ensure that traffic to a port that has no security groups and has port security enabled will always discard.

End to End Encryption: The cloud admin now has the option to enable API encryption for internal API calls in addition to the existing encryption on public OpenStack endpoints. When enabled, all internal OpenStack API calls will be sent over HTTPS using strong TLS 1.2 encryption. Encryption on internal endpoints helps avoid man-in-the-middle attacks if the management network is compromised.

Performance and Manageability:

VIO-in-a-box: Also known as the “Tiny” deployment. Instead of separate physical clusters for management and compute, VMware Integrated OpenStack control and data plane can now consolidate on a single physical server. This drastically reduces the footprint of a deployment and is ideal for Edge Computing scenarios where power and space is a concern. VIO-in-a-box can be preconfigured manually or fully automated with OMS API.

Hardware Acceleration: GPUs are synonymous with artificial intelligence and machine learning. vGPU support gives OpenStack operators the same benefits for graphics-intensive workloads as traditional enterprise applications: specifically resource consolidation, increased utilization, and simplified automation. The video RAM on the GPU is carved up into portions. Multiple VM instances can be scheduled to access available vGPUs. Cloud admins determine the amount of vGPU each VM can access based on VM flavors. There are various ways to carve vGPU resources. Refer to the NVIDIA GRID vGPU user guide for additional detail on this topic.

OpenStack at Scale: VMware Integrated OpenStack 5.0 features improved scale, having been tested and validated to run 500 hosts and 15,000 VMs in a region. This release will also introduce support for multiple regions at once as well as monitoring and metrics at scale.

Elastic TvDC: A Tenant Virtual Datacenter (TvDC) can extend across multiple clusters in VIO 5.0. Extending on support of single cluster TvDC’s introduced in VIO 4.0, VIO 5.0 allows a TvDC to span across multiple clusters. Cloud admins can create several resource pools across multiple clusters assigning the same name, project-id, and unique provider-id. When tenants launch a new instance, the OpenStack scheduler and placement engine will schedule VM request to any of the resource pools mapped to the TvDC.

VMware at OpenStack Summit 2018:

VMware is a Premier Sponsor of OpenStack Summit 2018 which runs May 21-24 at the Vancouver Convention Centre in Vancouver, BC, Canada. If you are attending the Summit in person, we invite you to stopped by VMware’s booth (located at A16) for feature demonstrations of VMware Integrated OpenStack 5 as well as VMware NSX and VMware vCloud NFV. Hands on training is also available (RSVP required). Complete schedule of VMware breakout sessions, lightening talks and training presentations can be found here.

Written by Xiao Gao, with valuable feedbacks and inputs from Mark Voelker.

While working with customers that are switching over to VMware Integrated OpenStack (VIO) from a different OpenStack distribution, customers expressed the need to update policies. Reasons were:

Backward compatibility with their legacy OpenStack deployment.

Internal company process and procedure alignment.

While updating policy is not any more complicated on VIO when compared to other distributions, it is an operation that we traditionally advised our customers to avoid. Following are some of the reasons:

1). Upgrade. While many non-default changes can seem trivial and straightforward, VMware can’t guarantee upstream implementation will always be backward compatible when moving between releases. Therefore, responsibility of maintaining day-2 changes lies within the customer

2). Snowflake avoidance. Upstream gate tests focus almost exclusively on default policies. The risk of exposing unexpected side effect increases when the security posture of an operation is relaxed or tightened. Security is also a concern when relaxing policies. Similarly, most popular OpenStack orchestration/monitoring tools such as Terraform, Gophercloud, or Nagios are implemented assuming default policies. When policies are made more restrictive, it can cause your favorite OpenStack tools to fail.

Snowflakes not only are difficult to support and maintain, often cause of unexpected outages.

3). Leverage external CMP for enhanced governance and control. External CMP such as the vRA is designed to integrate business processes into IAAS consumption. Instead of maintaining low-level policies changes, leverage out of box capabilities of vRA to control what users will have access to.

Implementation Options:

We understand there are scenarios where policy changes are required. Our recommendation for those scenarios is to leverage VIO custom playbook to make those changes. The basic idea behind custom playbook:

Customer will code up what has to change using Ansible.

VIO will decide when to make required changes, to survive upgrades and other maintenance tasks.

While VIO doesn’t sanction contents of the custom playbook, it’s essential to write the playbook in a manner that is modular and agnostic to the OpenStack version. Ideal playbook should be stateless, grouped based on operational action, and not restrictive towards alignment with the upstream (see example section for details). Loggings is on by default.

Working Example:

Let’s look at an example. Say we want regular users to be able to create shared networks. To do that we need to modify /etc/neutron/policy.json and change:

“create_network:shared”: “rule:admin_only”

to:

“create_network:shared”: “”

There is number of ways to accomplish above task. You can go down the path of j2 templates and introduce variables for each policy modification. But this approach requires discipline from the operator to update his/her entire set of j2 policy template(s) before any significant upgrade to avoid drift or conflicts with upstream. On the other hand, if you leverage direct file manipulation method, you will change only parameters that are required in your local environment, and leave everything else in constant alignment with upstream.

example uses back references (e.g., the parenthesis in the “regex” line and the \\1 and \\2 in the “line” line) to preserve the indentation/leading spaces on the beginning of each line and the comma at the end of the line (if it’s present). Back reference makes the regex a tad more complicated-looking, and it keeps the formatting in place.

Log Outputs:

Below are sample logs:

Conclusion

This post outlined thought processes involved when updating OpenStack Policies. I would love to hear back from you.

Also, VIO 4.1 is now GA. You can Download a 60-day VIO evaluation now and get started.

VMware announced general availability (GA) of VMware Integrated OpenStack (VIO) 4.1 on Jan 18th, 2018. We are truly excited about our latest OpenStack distribution that gives our customers enhanced stability on top of the Ocata release and support for the latest versions of VMware products, across vSphere, vSAN, and NSX V|T (including NSX-T LBaaSv2). For OpenStack Cloud Admins, the 4.1 release is also about enhanced control. Control over API throughput, virtual machine bandwidth (QoS), deployment form factor, and user management across multiple LDAP domains. For Kubernetes Admins, 4.1 is about enhanced tooling. Tooling that enables Control plane backup and recovery, integration with Helm and Heapster allowing for simplified application deployment and monitoring, and centralized log forwarding. Finally, VIO deployment automation has never been more straightforward using newly documented OMS API.

Public OMS API – Management server APIs that can be used to automate deployment and lifecycle management of VMware Integrated OpenStack is available for general consumption. Users can perform tasks such as provision OpenStack cluster, start/stop the cluster, gather support bundles, etc using the OMS public API. Users can also leverage Swagger UI to check and validate API availability and specs,

Neutron QoS – Before VIO 4.1, Nova image or flavor extra-spec controlled network QoS against the vCenter VDS. With VIO 4.1, Cloud administrator can leverage Neutron QoS to create the QoS profile and map to a port(s) or logical switch. Any virtual machine associated with the port or logical switch will inherit the predefined bandwidth policy.

Native NSX-T Load Balancer as a Service (LBaaS) – Before VIO 4.1, NSX-T customers had to implement BYO Nginx or third party LB for application load balancing. With VIO 4.1, NSX-T LBaaSv2 can be provisioned using both Horizon or Neutron LBaaS API. Each load balancer must map to an NSX-T Tier 1 logical router (LR). Missing LR or LR without a valid uplink is not a supported topology.

Multiple domain LDAP backend – VMware Integrated OpenStack 4.1 supports SQL plus one or more domains as an identity source. Up to a maximum of 10 domains, each domain can belong to a different authentication backend. Cloud administrators can create/update/delete domains and grant / revoke Domain administrator users. Domain administrator is a local administrator, delegated to manage resources such as user, quotas, and projects for a specific domain. VIO 4.1 Support both AD and OpenDirectory as authentication backends.

4.1 NFV and Kubernetes Features:

VIO-in-a-box – AKA Tiny deployment. Instead of separate physical clusters for management and compute, VIO deployment can now consolidate on a single physical server. VIO-in-a-box drastically reduces the footprint and is suitable for environments which do not have high availability requirements nor large workloads. VIO-in-a-box can be preconfigured manually or fully automated with OMS API. Shipped as a single RU appliance to any manned or unmanned Data Center where space, capacity, availability of onsite support are biggest concerns.

VM Import – Further expanding on VM import capabilities, you can now import vSphere VM with multiple disks and NICs. Any VMDK not classified as VM root disk imports as cinder-volume(s). Existing networks import as provider network with access restricted only to the given tenant. Ability to import vSphere VM workloads into OpenStack and run critical Day 2 operations against them via OpenStack APIs is the foundation we are setting for future sophisticated use cases around availability. Refer to here for VM import instructions.

Networking passthrough – Traditionally Nova flavor or image extra-specs defined the workflow for hardware passthrough, without direct involvement of Neutron. VIO 4.1 introduces Neutron-based network passthrough device configuration. The Neutron based approach allows a Cloud administrators to control and manage network settings such as MAC, IP, and QoS of a passthrough network device. Although both options will continue to be available, going forward commendation is to leverage the neutron workflow for network and nova extra-specs for all other hardware passthrough devices. Refer to Upstream and VMware documentation for details.

Enhanced Kubernetes support – VIO 4.1 ships with Kubernetes version 1.8.1. In addition to the latest upstream release, integration with widely adopted application deployment and monitoring tools are standard out of the box, Helm and Heapster. VIO 4.1 with NSX-T2.1.will allow you to consume Kubernetes network security policy as well.

VIO Kubernetes support bundle – Opening support tickets couldn’t be simpler with VIOK support bundle. Using a single line command, specify the start and end date, VIO Kubernetes will capture logs from all components required to diagnosis tenant impacting issues within the specified time range.

VIO Kubernetes Log Insight integration – Cloud administrator can specify FQDN of the log Insight as the logging server. Current release supports a single logging server.

Virtual machines and containers are two of my favorite technologies. In today’s DevOps driven environment, deliver applications as microservices allows an organization to provide features faster. Splitting a monolithic application into multiple portable fragments based on containers are often top of most organization’s digital transformation strategies. Virtual Machines, delivered as IaaS, has been around since the late 90s, it is a way to abstract hardware to offer enhanced capabilities in fault tolerance, programmability, and workload scalability. While enterprise IT large and small are scrambling to refactor application into microservices, the reality is IaaS are proven and often used to complement container based workloads:

1). We’ve always viewed the IaaS layer as an abstraction from the infrastructure to provide a standard way of managing and consolidate disparate physical resources. Resource abstraction is one of the many reasons most of the container today runs inside of Virtual machines.

2). Today’s distributed application consists of both Cattles and Pets. Without overly generalizing, Pet workload tends to be “hand fed” and often have significant dependencies to the legacy OS that isn’t container compatible. As a result, for most organizations, Pet workloads will continue to run as VMs.

3). While there are considerable benefits to containerize NFV workloads, current container implementation is not sufficient enough to meet 100% NFV workload needs. See IETF report for additional details.

4). Ability to “Right Size” the container host for dev/test workloads where multiple environments are required to perform different testings.

Instead of mutually exclusive, over time it’s been proven that two technologies complement each other. As long as there are legacy workloads and better ways to manage and consolidate sets of diverse physical resources, Virtual Machines (IaaS) will co-exist to complement containers.

OpenStack IaaS and Kubernetes Container Orchestration:

It’s a multi-cloud world, and OpenStack is an important part of the mix. From the datacenter to NFV, due to the richness of its vendor-neutral API, OpenStack clouds are being deployed to meet needs of organizations needs in delivering public cloud like IaaS consumption in a private cloud data center. OpenStack is also a perfect complement to K8S by providing underline services that are outside the scope of K8S. Kubernetes deployments in most cases can leverage the same OpenStack components to simplify the deployment or developer experiences:

1). Multi-tenancy: Create K8S cluster separation leveraging OpenStack Projects. Development teams have complete control over cluster resources in their project and zero visibility to other development teams or projects.

2). Infrastructure usage based on HW separation: IT department often are the central broker for development teams across the entire organization. If Development team A funded X number of servers and Y for team B, OpenStack Scheduler can ensure K8S cluster resources always mapped to Hardware allocated to respective development teams.

3). Infrastructure allocation based on quota: Since deciding how much of your infrastructure to assign to different use cases can be tricky. Organizations can also leverage OpenStack quota system to control Infrastructure usage.

5). Container storage persistence: Since K8S pods are not durable, storage persistence is a requirement for most stateful workloads. When leverage OpenStack Cinder backend, storage volume will be re-attached automatically after a pod restart (same or different node).

6). Security: Since VM and containers will continue to co-exist for the majority of enterprise and NFV applications. Providing uniform security enforcement is therefore critical. Leverage Neutron integration with industry-leading SDN controllers such as the VMware NSX-T can simplify container security insertion and implementation.

7). Container control plane flexibility: K8S HA requirements require load balanced Multi-master and scaleable worker nodes. When Integrated with OpenStack, it is as simple as leverage LBaaSv2 for master node load balancing. Worker nodes can scale up and down using tools native to OpenStack. WIth VMware Integrated OpenStack, K8S worker nodes can scale vertically as well using the VM live-resize feature.

Next Steps:

I will leverage VMware Integrated OpenStack (VIO) implementation to provide examples of this perfect match made in heaven. This blog is part 1 of a 4 part blog series:

Historically, organizations had “racked and stacked” hardware, and then installed and configured software and applications for their IT needs. With advent of cloud computing, IT organizations could start taking advantage of virtualization to enable the on-demand provisioning of compute, network, and storage resources. By using the CLI or GUI, users have been able to manually provision these resources. However, with manual provisioning, you carry the following risks:

Inconsistency due to human error, leading to deviations from the defined configuration.

Lack of agility by limiting the speed at which your organization can release new versions of services in response to customer needs.

Difficulty in attaining and maintaining compliance to corporate standards due to the absence of a repeatable process

Infrastructure as Code (IAC) solutions address these issues by allowing you to automate the entire configuration and provisioning process. In its essence, this concept allows IT teams to treat infrastructure the same way application developers treat their applications – with code. The definition of the infrastructure is in human readable software code. The code allows to script, in a declarative way, the final state that you want for your environment and when executed, your target environment is automatically provisioned. A recent blog on this topic by my colleague David Jasso referred to IAC paradigm as IT As Developer. For additional information on IAC, read the two Forrester reports: How A Sysadmin Becomes A Developer (Chris Gardner and Robert Stroud; Forrester Research; March 2017); Lead The I&O Software Revolution With Infrastructure-As-Code (Chris Gardner and Richard Fichera; Forrester Research; September 2017)

In this blog post I will show you how by using Terraform and VMware Integrated OpenStack (VIO), you describe and execute your target infrastructure configuration using code. Terraform allows developers to define their application infrastructure via editable text files ending in .tf extension. You can write Terraform configurations in either Terraform format (using the .tf extension) or in JSON format (using the .tf.json extension). When executed, Terraform consumes the OpenStack API services from the VIO (OpenStack distribution from VMware) to provision the infrastructure as you have defined. As a result, you can use these provisioning tools, in conjunction with VIO, to implement Infrastructure as code.

For those not familiar with VIO, VIO differentiates from upstream distribution in by making install, upgrade and maintenance operations simple, and leveraging VMware enterprise-grade infrastructure to provide the most stable release of OpenStack in the market. In addition to OpenStack distribution, VIO is also helping bridge gaps in traditional OpenStack management monitoring and logging by making VMware enterprise-grade tools such as vRealize Operations Manager and Log Insight OpenStack aware with no customization.

Standard DefCore Compliant OpenStack Distribution delivered as an OVA

End to end support by VMware, OpenStack and SDDC infrastructure.

The best foundational Infrastructure for IaaS is available with vSphere Compute (Nova), NSX Networking (Neutron), vSphere Storage (Cinder / Glance)

OpenStack endpoint management and logging is simple and easy to perform with VMware vRealize Operations Manager for management, vRealize Log Insight for logging, and vRealize Business for chargeback analysis

Best way to leverage existing VMware investment in People, Skills, and Infrastructure

Let’s look at the structure of code that makes IAC possible. The first step in defining the configuration is defining all the variables a user needs to provide within the Terraform configuration – see example below. The variables can have default values. Putting as much site specific information as possible into variables (rather than hardcoding the configuration parameters) makes the code more reusable. Please note that the code below is for illustration only. Complete example can be downloaded from here.

The next step in defining the configuration is identifying the provider. Terraform leverages multiple providers to talk to services such as AWS, Azure or VIO (OpenStack distribution from VMware). In the example below we specify that the provider is OpenStack, using the variables that you defined earlier.

Next you define the resource configuration. Resources are the basic building blocks of a Terraform configuration. In the example code below (please use it as an illustration), you use Terraform code, which in turn leverages VIO, to create the compute and network resource instances and then assigns network ID to the compute instance to stand a networked compute instance. As you will see in the example, the properties of a resource created may be passed as arguments to the instance creation step of the next resource, such as using Network ID from the ‘network’ resource created, when creating the resource ‘subnet’ in the code below.

Infrastructure as a code allows you to treat all aspects of operations as software and manage almost everything in code, including servers, storage, networks, log files, automated tests, deployment processes, and so on. The concept extends to making configuration changes as well. When you want to make any infrastructure configuration changes, you can check out the configuration code files from your code repository management system such as git, edit it to make the changes you want, check-in that new version. So you can use git to make and track changes to your configuration code – just as developers do.

Summary:

In this blog post, we have shown how you can implement IAC paradigm by using Terraform, running on VIO. Download 60-day VIO evaluation now and get started, or try out VIO 4.0 based VMware Integrated OpenStack Hands-on Lab, no installation required.

Last week at VMworld, VMware’s biggest event of the year, I attended a few sessions with various topics related to open source, and was impressed with the number of people who showed interest those sessions. Our customers are looking to leverage open source products on top of VMware technologies, and VMware is more active in the open source community than one might think.

We, at VMware, use open source in our products, make thousands of contributions every year to many upstream projects, and create new open source projects that are being used by many. Some of the open source projects created by VMware include:

And the list goes on. You can learn about additional projects here. VMware’s investment in open source makes a lot of sense when you think about it. First, we would like to influence and engage with our customers, who might be looking at open source projects to improve the way they do stuff (see Clarity for example). Second, we would like to improve our products and tools based on feedback and support from the community. And lastly, a lot of growth is happening at the edge of the technology and we want to leverage the opportunity.

One of the most important open source projects VMware is involved in is OpenStack. At VMworld last week, we announced our new release of VMware Integrated OpenStack, the OpenStack distribution from VMware. In the last few years we have been working hard to deliver an OpenStack distribution that would seamlessly work on VMware SDDC, without you having to spend hours on customization or professional services.

History of Working with the OpenStack Community

VMware has a history of open source contributions to the OpenStack community starting in 2010. Initially it was via the Nicira team’s work on Open vSwitch (OVS) (Niciria was acquired by VMware). Later, it was via other projects including Nova, Neutron, Cinder, Glance and Ceilometer. We are the #1 contributor to the Neutron project, and the #6 contributor to the Nova project. In addition, we share all the Compute, Network, and Storage drivers with the community.

Source: http://stackalytics.com/

Compliance with Interop Working Group guidelines

VMware Integrated OpenStack complies with the interoperability guidelines defined by the OpenStack Interop Working Group. This group drafts the guidelines that include a list of capabilities that a “true OpenStack” cloud must expose to end users, a list of tests they must pass in order to prove it, and a list of designated sections of the upstream codebase they must use to provide those capabilities. For example, automation tools that leverage the OpenStack APIs should work on VMware Integrated OpenStack as they would on any other OpenStack distribution. Interoperability prevents vendor lock-in because it allows you to easily switch from your current OpenStack deployment to a different vendor’s distribution.

One area where developers may have been concerned in the past is image formats, since the VMware platform currently utilizes OVA, VMDK, and ISO disk formats with Glance. However, tools exist to convert from other formats to the formats we have adopted (for example: qemu-img to convert qcow2 to VMDK). In addition, significant community work in the area of image building with projects like Diskimage Builder and Packer enables users to auto-generate a VMware-compatible image relatively quickly.

VMWare is committed to keeping VMware Integrated OpenStack open by ensuring all its drivers are open source, ensuring vendor interoperability based on InterOp Working Group guidelines as well as being a very active participant in the OpenStack community.

A production cloud isn’t very efficacious unless users have the ability to run virtual machine images required by their application. A cloud image is a single file that contains a virtual disk that has an operating system. For many organizations, the simplest way to obtain a virtual machine image is to download a prebuilt base cloud image with a pre-packaged version of cloud-init to support user-data injection. Once downloaded, an organization would leverage tools such as Packer to further customize and harden on top of the base image before rolling to production. Most operating system projects and vendors maintain official images for direct download. Openstack.org maintains a list of most commonly used images here.

Recently we received some queries about the proper way to import prebuilt QCOW2 native cloud images into VMware Integrated OpenStack. Images import correctly, but would not successfully boot. Common symptoms are “no Operating System found” messages generated by the virtual machine’s BIOS, the guest OS hanging during the boot cycle, or DHCP failure when trying to acquire an IP address. After further analysis, problems were either caused by older upstream tooling or simple adjustments required in the cloud image to match the vSphere environment. Specifically:

Some storage vendors need StreamOptimized image format.

Guest Images are attempting to write boot log to ttyS0, but the serial interface is not available on the VM.

Defects in earlier versions of the qemu-img tool while creating streamOptimized images.

DHCP binding failure caused by Predictive Network Interface Naming.

To overcome these issues, we came up with the following set of best practices to help you simplify the image import process. I thought it would be a good idea to share our recommendations so others can avoid running into similar issues.

1). VIO 3.x and earlier, serial console output is not enabled. When booting an image that requires serial console support, use libguestfs to edit the grub.cfg and remove all references to “console=ttyS0”. Libguestfs provides a suite of tools for accessing and editing VM disk images. Once installed the “guest mount” command-line tool can be used to mount qcow2 based images. By default, the disk image mounts in read-write mode. More info on Libguestfs here.

# guestmount -a xxx-cloudimg-amd64.img -m /dev/sda1 /mnt

# vi /mnt/boot/grub/grub.cfg

# umount mnt

See below screen Capture:

2). VMware vSAN requires all images to be in streamOptimized format. When converting to VMDK format, use the –o flag to specify the subformat as streamOptimized:

“lsilogic” is the recommended adapter type. Although it is possible to set the adapter type during image upload into glance, we recommend as a good practice to always set the adapter type as part of the image conversion process.

Older versions of the qemu-img tool contain a bug that causes problems with the streamOptimized subformat. The following command can be run after converting an image to correct the problem: printf ‘\x03’ | dd conv=notrunc of=xxx-server-cloudimg-amd64.vmdk bs=1 seek=$((0x4)). It is harmless to execute the printf even if you’re using a version of qemu-tools that has the fix: all the command does is set the VMDK version to “3” which correct version of qemu-img will already have done. If you are not sure what version of qemu-tools you have, apply the printf command.

3). In the case of CentOS, Udev rule ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules as part of the image bundle is ignored during CentOS image boot up and Predictable Network Interface Naming is enabled as a result. Our recommendation is to disable predictive naming using grub. You can find more information on my previous blog.

4). Finally, with Cirros QOCW image, preserve the adapter type as ‘ide’ during the QCOW2 to VMDK conversion process. There’s currently an upstream bug open.

Once converted, you can look into the image metadata and validate information such as disk and image type before uploading into Glance image repository. Image metadata can be viewed by display the first 20 lines of the VMDK

# cat xxx-server-cloudimg-amd64.vmdk | head -20

You can add the newly converted image into glance using OpenStack CLI or Horizon. Set the public flag when ready for end user consumption.

OpenStack CLI:

Horizon:

Your cloud is as useful as the application and virtual machine images you can support. By following above simple best practice guidelines, you will deliver a better user experience to your end users by offering more Virtual machine varieties with significantly reduced lead time.

Visit us at VMworld in Las Vegas; we have a large number of Demo and speaking sessions planned:

While testing out the latest CentOS 7 QCOW2 cloud image, we ran into an issue where the guest operating system wasn’t able to obtain a DHCP IP address after successful boot. After some troubleshooting, we quickly realized the NIC name was assigned based on predictive consistent network device name (CNDN). You can read more about CNDN from here. Network script required to bring up the network interface was missing from /etc/sysconfig/network-scripts, only default ifcfg-eth0 script was present. The network interface remained in DOWN status since interface script wasn’t available. Therefore, the Linux dhclient therefore couldn’t bind to the interface, hence the DHCP failure.

Fixing the symptom we simply edited and renamed the interface script to reflect the predictive name, then restart networking. But since this problem will show up again when booting a new VM, we need a permanent fix in the image template.

It turns out predictive naming was intended to be disabled in the CentOS 7 Cloud Image based on the udev role below:

The system ignored this setting during bootup and predictive naming was enabled as a result.

There are multiple ways to workaround this:

Solution 1 – Update Default GRUB to Disable CNDN:

1). To restore the old naming convention, you can edit the /etc/default/grub file and add net.ifnames=0 and biosdevname=0 at the end of the GRUB_CMDLINE_LINUX variable:

Solution 3: Create Customer Udev Rule

We will create an udev rule to override the unintended predictive name.

1) Create a new 80-net-name-slot.rules in /etc/udev/rules.d/

# touch /etc/udev/rules.d/80-net-name-slot.rules

2). Add below line to the new 80-net-name-slot.rules:

NAME==””, ENV{ID_NET_NAME_SLOT}!=””, NAME=”eth0″

Final Implementation

All three solutions solved the problem. Approach #1 involves updating GRUB config, so handle with care. Solution #2 is a very hands-off approach allowing Network Manager to control interface states. Most sysadmins have a love/hate relationship with NetworkManager however. NetworkManager simplifies management of WiFI interfaces but can lead to unpredictable behavior in interface states. Most common concerns are interfaces brought up by NetworkManager when it should be down as sysadmin are not ready to turn up those NIC yet. OpenStack community had reported cloud-init timing related issues as well, although we didn’t have any problems enabling it on the Cloud Centos 7 image. Solution #3 needs to align with overall deployment requirements in a Multi-NIC environment.

In reality, CNDN was designed to solve NIC naming issues in a physical server environment. It stopped being useful with virtual workloads. Most of the cloud workloads deploy with a single NIC. The NIC is always eth0. Consequently, disabling CNDN makes sense, solution #1 is what we recommend.

Once CentOS VM image is in the desirable state, create a snapshot, then refer to the OpenStack documentation to upload into glance. A shortcut to validate the new image, instead of creating a snapshot, download and upload back into glance, it is perfectly fine to boot VM directly from a snapshot. Please refer to VIO documentation for recommended steps.