Home > Blogs > VMware {code} > Monthly Archives: November 2017

Monthly Archives: November 2017

An Overview of VMware Cloud on AWS APIs

As part of vSphere 6.5 we revolutionized the programmatic interaction of the product by enabling new REST based APIs and Open Sourced SDKs to provide a developer and automation experience which delighted users. Continuing this work and moving into the cloud we are looking to provide an equal if not better experience with VMware Cloud on AWS.

The new vSphere 6.5 REST APIs which are used to manage both new features of the 6.5 release and some existing features were modernized to provide a superior experience, continuing with this experience, the VMware Cloud on AWS APIs are RESTful, making use of CRUD (Create, Retrieve, Update, Delete) based actions and utilizing JSON formatted inputs and outputs for the data structure. The documentation for these APIs will also be available in numerous ways both online and inline.

There are three main APIs, among several others, which users should be aware of that allow you to programmatically access the VMware Cloud on AWS features and surrounding areas to work with the environment and automate or develop to succeed in your use cases:
VMware Cloud Service API Tree

We will be taking a bit deeper look at the first three in the following sections.

Cloud Services Platform API

The Cloud Services Platform (CSP) APIs are available for all cloud services which are offered by VMware. They contain the core features that customers will use when working with multiple cloud services from VMware.

In the context of VMware Cloud on AWS, the main use of the CSP APIs will be to serve as the authentication point. Once authenticated, the authorization token will be valid against this API as well as the VMware Cloud on AWS API. The CSP API also serves as the main point for Organization (Org) and VMware Cloud on AWS console user management. Some of the methods include displaying all the users within an Org, adding users to an Org, and removing users from an Org.

VMware Cloud on AWS API

The VMware Cloud on AWS (VMC) API will be the endpoint for most actions available within the VMware Cloud on AWS console. This API, which is currently in Technical Preview, allows for SDDC management actions like creating or removing SDDCs with a single API call, adding or removing the elastic hardware provided by the VMC service and adding the ESXi hosts to our SDDC, and handling network operations for the SDDC. We can also gather task based information on items which take place in the VMC environment.

Access to the VMC API is also be available in multiple ways. First off, since this API is RESTful, it can be consumed with your preferred programming language or client which can talk REST. The open-sourced vSphere Automation SDKs can be used as well and are available in programming languages like Python, Java, Ruby, and more. This API can then be explored through a built in API Explorer. The features of VMC can also be accessed through the command line with PowerCLI 6.5.4 and a technical preview of the new version of Datacenter CLI (DCLI). DCLI, which is available as a separate download, can be installed on Windows, MacOS, and Linux. More posts are planned to explain these areas in depth in the future so stay tuned!

Deployed SDDC APIs – vSphere API

The last of the APIs are the vSphere APIs. These are the same APIs you already know and love! You will be able to consume these APIs in the exact same way you already do with our on-premises offerings of vSphere. With VMware Cloud on AWS being a managed environment you will of course have limited permissions and certain key differences on areas which you should deploy to but we will dig into these in a future blog post.

Summary

We just reviewed the three API endpoints you will want to become familiar with when accessing VMware Cloud on AWS. The CSP API, which serves as the main authentication point and management point for Orgs and console users. There is the VMC API that is the SDDC management point. Lastly, there are the deployed SDDC APIs themselves which will be the vSphere APIs which hopefully you are already familiar with.

In the next blog, we will cover how to get started using each of these APIs!

VMware {code} OpenStack MeetUp | November 29th | Maximize Developer Velocity with Containers

EVENT DETAILS:

Wednesday, November 29th, 2017
6:30 – 8:30 pm
Prom C Cafeteria, VMware HQ (see MeetUp event for a map)
Watch the livestream on the VMTN Facebook page

 

DESCRIPTION:

Please join us at VMware headquarters on Wednesday November 29th for an SF Bay Area OpenStack MeetUp hosted by VMware {code}. The speakers at this MeetUp, Dustin Kirkland and Sabari Murugesan, will examine the modern set of container best practices filling the sails of the smartest and most efficient developers in the world. After their presentations, they will stick around after for a bit of Q & A. Please see the details below on the event schedule and speaker bios. Light dinner and drinks will be provided, we hope to see you there!

 

SCHEDULE:

6:30 – 7:00 Introductions, Snacks, and Brief Presentation on VMware {code}
7:00 – 7:05 – K8s on OpenStack Lightning Talk, Sabari Murugesan
7:05 – 8:00 Discussion and Q&A, Dustin Kirkland
8:00 – 8:30 Networking

 

SPEAKERS

 

Dustin Kirkland

Dustin is a VP of Product Development at Ubuntu/Canonical. Dustin leads a team of expert product managers, directing and managing the product lifecycle and road maps across the suite of Ubuntu server, cloud, desktop, and IoT device products. Dustin drives functional requirements across internal and external teams, delivering marketing and product requirements. Find Dustin on Twitter: @DustinKirkland

 

 

 

Sabari Murugesan

Sabari is a Staff Engineer at VMware and has been working with OpenStack since the Havana release. In the past, he was a core contributor to the Glance project and has also been associated with the Nova and Oslo projects. At VMware, he primarily works as a developer in the VMware Integrated OpenStack & Kubernetes product team, a.k.a “Team OpenStack @ VMware.” Find Sabari on Twitter: @neosab87

 

 

Interested? RSVP on MeetUp. If you can’t attend in person, the event will be live-streamed on the VMTN Facebook page.

VMware {code} is a free developer program that provides access to a growing community of developers and experts. If you are an existing Developer Center user or partner program member, you can join the new VMware {code} program using your MyVMware account. If you do not have one, register below to access SDKs and participate in developer forums.

Join VMware {code}

VMware Cloud Certification Services: A Journey to SaaS Transformation

VMware delivers a pre-configured cloud based certification test bed in the cloud for a fixed duration of time to it’s partners to certify their products. Partners with access to the program can log-in using a URL provided by VMware and access the test bed without any VPN.

Continue reading

Introducing the New Workspace ONE Swift SDK

The VMware Workspace ONE product teams have been hard at work this year with the goal to make developing with VMware and Workspace ONE easier and better than ever. First we launched the brand new Workspace ONE Dev Center and then the completely revamped Workspace ONE Swift Software Development Kit (SDK).

You may already be familiar with the AirWatch Software Development Kit (SDK), a set of tools that let you easily add advanced security and management capabilities to enterprise mobile apps. The new Workspace ONE Swift SDK is the completely revamped version of the AirWatch SDK for the iOS platform. The Swift SDK takes the old SDK, written in Objective-C, and is updated with the Swift 3.1 (Swift 3.2 and 4.0 support is right around the corner) programming language from Apple (https://developer.apple.com/swift/) along with many other modern technologies.

By leveraging the latest and greatest Apple technology, the Swift SDK offers all of the benefits of the AirWatch SDK with a few more bells and whistles when it comes to user experience and performance.

You’ll love the Swift SDK, here is why:

  • Greatly reduced app-to-app flipping: The Swift SDK leverages a new protocol for app data sharing, significantly reducing the amount of app-to-app flipping required
  • Reduced integration time:  With the Swift SDK, you no longer need to include as many dependent frameworks
  • Refactored code: Much of the AirWatch SDK code has been refactored, resulting in less operations on the main thread, a smoother feel when interacting with UI elements and more
  • Support for Workspace ONE devices:  The Swift SDK apps will now also be compatible on devices enrolled through Workspace ONE

Architecture for the Future

In addition to the tangible user experience and performance improvements, there are several major underlying architecture changes made in the new Swift SDK which set the groundwork for future improvements. Future improvements will include things such as bitcode support and adoption of modern package management technologies like Cocoa Pods.

So, want to try it out?

The Workspace ONE Swift SDK is available today. Contact your account representative or AirWatch customer support for more information.

Using the Objective-C SDK? Here are some things you should know.

What behavior has changed between Objective-C and. Swift?

The Swift SDK will introduce a new mechanism using the shared keychain for SDK apps to communicate with other SDK apps on the device. This approach provides benefits from both a security and a user experience perspective.

SDK applications built by the same developer account and are also in the same keychain group or “cluster” will now be able to share an app passcode & SSO session with each other without requiring a flip to the Agent or Container application every time authentication is required. However, applications on the same device built by different keychain groups will not be able to take advantage of this passcode sharing capability. There will still be some scenarios where a flip to the Agent, Container, or Workspace ONE app is required for obtaining the server URL and other setup information but this particular flip should only occur once per cluster of apps.

The diagram below illustrates this new “clustering” behavior. The dotted cluster represents a unique developer account and keychain group. Applications with the same color code represents SDK apps which will share information with each other.

How will Swift SDK and Objective-C SDK applications interact and behave when both are present on a device?

Upon upgrading one app to use the Swift SDK (see State 2 in diagram below), the Objective-C SDK applications will automatically switch to the clustering behavior for passcode and other app data sharing mentioned in the behavior changes section above. Thus, the Objective-C applications will no longer flip to the Agent for passcode authentication nor will it share a passcode with apps which are outside of its own keychain cluster.

Note: Anchor app refers to either Agent, Container, or Workspace ONE.

What is the plan for the Objective-C SDK?

The Objective-C version of the iOS SDK will be in maintenance mode and new features/capabilities will be exclusive to the new Swift SDK.

Get in on the conversation!

Join VMware {code}

Become a part of one of the fastest-growing developer communities devoted to cloud infrastructure and enterprise mobility.

 

Learn More

Check out the VMware EUC blog post on developing enterprise applications with the Workspace ONE SDK here.