Because our vCenter doesn't currently have a content library that the
controller is able to use in this video
We're going to create a content library in vCenter. So to do that, we're gonna
go back here to the vSphere client
We'll click on the hamburger menu in the top left and from the drop down
We'll click right here on content libraries and sure enough we have no content
libraries by default
So we'll click right here on create to go ahead and create a new content
library
Let's name it something super clever like our content library
Fantastic it's give me associate with this vCenter vcsa - red.ogit.Lab WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Fantastic it's give me associate with this vCenter vcsa - red.ogit.Lab
We'll click on next and it'll be a local content library
We'll click on next and we won't use a security policy
We'll click on next and then we'll choose a home for the files
Let's go ahead and click on the red three data store and click on next and then
we'll click on finish and boom
We now have a content library and if we click on that content library right
here currently it's showing us that we have
Absolutely nothing in it. So that's really like having a
Library for books and things with no books WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Library for books and things with no books
But the good news is now that we have the content library later when we deploy
our NSX cloud
The controller for the advanced load balancer can actually put files in this
content library that it can then use to deploy
Service engines so as far as our game plan goes boom we now have a content
library in vCenter
[BLANK_AUDIO]