NOTE: This article has moved to the new VMware {code} blog. Please visit https://blogs.vmware.com/code/2017/11/18/vmware-cloud-certification-services-journey-saas-transformation/ to read the article.
NOTE: This article has moved to the new VMware {code} blog. Please visit https://blogs.vmware.com/code/2017/11/18/vmware-cloud-certification-services-journey-saas-transformation/ to read the article.
This blog post is a part of the blog series published by the Content Library team. Please find all the blog posts by the team at this link.
In Uploading an OVF Template to a Content Library tutorial, we went through the UpdateSession
API to upload files to a library item with an example for uploading an OVF template. In this tutorial, we explain the concept of DownloadSession
API and show how to use it to download files from a library item.
At the end of this tutorial you should be able to:
This blog post is a part of the blog series published by the Content Library team. Please find all the blog posts by the team at this link.
Previously, the Basic Life Cycle of a Content Library tutorial explained how to use Content Library APIs to create, update and delete libraries and library items. In this tutorial, we will further explore the APIs to upload content to a library item.
At the end of this tutorial you should be able to:
This blog post is a part of the blog series published by the Content Library team. Please find all the blog posts by the team at this link.
We discussed the requirements and how to prepare the environment to use the Content Library APIs in the Getting Started with the Content Library APIs tutorial. Now we should have an environment ready to make API calls against the Content Library Service in a vCenter Server instance. In this tutorial, we will go through the basic life cycle of a library and library items. The basic operations we will cover are:
This blog post is a part of the blog series published by the Content Library team. Please find all the blog posts by the team at this link.
This tutorial will go through the steps required to setup a development environment that uses the Content Library APIs. At the end of this post you should be able to:
VMware vSphere® Content Library empowers vSphere Admins to effectively manage VM templates, vApps, ISO images and scripts with ease. It is a new addition in the vSphere 6.0 release.
This blog series authored by the Content Library Team is aimed at explaining concepts and APIs exposed by the Content Library feature.
One of the challenges every customer faces when deploying VMware vCloud Automation Center (vCAC) is trying to figure out what services you want to offer, and to whom you want them offered. VMware and other third-party vendors have been creating different plug-ins and workflows to help customers along their journey to ITaaS, and these workflows can be found on the VMware Solution Exchange website. One of the latest plug-ins available is the Horizon 6.0 plug-in for vCenter Orchestrator (vCO) that allows administrators to run automated workflows with the VMware vSphere Web Client and VMware vCAC 6.0.1/6.1.
This is the second in series of articles introducing the VMware Management stack. In the first article, I explained how to:
In this article, we will build on the previous example. We will look at the VMware object system in the form of Managed Objects and Data Objects, learn more about invoking methods on Managed Objects, and use the Property Collector to start exploring the vCenter inventory.
If you are a software developer new to the VMware management stack, you may have noticed that the learning curve is a little steep. This is due in part to the breadth of our offerings, and the number of different ways you may need to use VMware products. This can lead to an overload of information.
This is the first in a series of articles that will walk through the process of getting set up and using the vSphere Management SDK. It is targeted at developers of software products that will manage, monitor, analyze, automate or otherwise interact with virtual resource controlled by VMware infrastructure. I’m not addressing device drivers or low level development, nor am I addressing scripts to automate specific IT operations.