Get an overview of the Content Library and how it is implemented.
- [Instructor] Now one of the more useful features that have been implemented since 6.0 is content libraries. Content libraries allow us to store inventory objects from our virtual environment. This could be something as simple as templates. Anything that we have as an inventory object can be contained in these content libraries, and these content libraries can be shared not just within our data center, but to multiple data centers throughout our environment. Think about how useful that is for consistency, or ease of rollout.
You have a content library in your main office. You're rolling out some virtual machines in your branch office. As long as the vCenter Server has access to the content library at that main office, we can pull directly from our content library to get the virtual machines that we would deploy at our main office level. So very, very convenient feature. There are two types of libraries. There is a local library. This would be limited to your data center, and this can obviously be published, because our subscribed libraries are nothing more than local libraries that have been published for other sites to use.
Whoever has been given access, and the information to get to those sites will have access to its inventory. Now a published library has synchronization obviously. Subscribed libraries have a synchronization that takes place. You can download the entire contents of a library immediately, or you can just take the metadata or the listing of everything that's there, and then synchronize with those items you need to as needed. This saves a lot of storage space for data if you're running into a storage shortage.
Now obviously as the libraries change, there's going to be an update, and we can have that update take place at intervals, regular intervals, or we can manually force it to do an update whenever we need to. Now we talked a little bit about synchronization already, but let's go through it again. When we select download all, this will be the metadata, or the table of contents kind of, what's there in the library, and the contents themselves. So a lot of data may be contained on there, depending on which templates, or which profiles are being used at the time.
When we choose Only as needed, that's only going to grab the metadata, or what I like to refer to as the table of contents. A listing of what's there. Then we can synchronize the downloads as we need each item. So this is really useful if, like I said earlier, we're running out of storage in our environment, or our storage options are limited. Why would you download an entire content from the main office when you're just a branch office? Just download what you need. Now here are some things that would be helpful to know about content libraries.
They're pretty simple. They're basically just a storage place, but we can require authentication, and I do recommend that authentication take place here, because you want to make sure people are subscribing to your library that need to. You don't want everyone gaining access to the virtual machines you're running into production, because lo and behold, someone could grab a hold of that, figure out some of your security flaws. So make sure you have authentication in place if you're in production. Also, whenever we use a template in our environment, and then we post it up to the library, it's going to be changed into an .ovf format.
Not a big deal here, but I just want you to be aware, .ovf format once it gets in the library. Next, we have required privileges for any type of update and delete functions for our library. So, we're going to have roles and privileges, and certain privileges are required for certain things you want to do. You want to update your library, you want to delete some of the things that are located in the library. You need to make sure that you have the privileges to do so. Last but not least, these libraries are very flexible, and the software development kit comes with a plethora of options for you.
Python, Java, whatever your language of choice, you can make changes as needed to your library content.
Instructor Russell Long demonstrates how to configure advanced settings, create and manage a multisite content library, set up and maintain vCloud Air, and deploy vApps. Russell shows how to publish and subscribe to a content catalog, determine which permissions are required to manage content catalogs, and configure a content library to work across sites. He compares automatic sync with on-demand sync. He also takes you through the steps of authentication configuration, VM migration to vCloud Air, and VPN connection verification.
This course is also an exam preparation resource, as it covers the topics in the Administer and Manage vSphere Virtual Machine domain of the VCP-DCV 6 exam.
- Deploying and configuring VMs
- Managing shared USB devices
- Configuring hosts and VMs for passthrough
- Monitoring VM resource consumption
- Taking a snapshot of a VM
- Managing content libraries
- Using content library roles
- Creating a VPN connection between vCloud Air and an on-premises site
- Migrating a VM to vCloud Air
- Deploying and configuring vApps