Hello and welcome to this lesson on Introduction to Oracle Cloud Infrastructure Registry, also known as OCIR. My name is Mahendra Mehra, and I'm a Senior Training Lead and Evangelist with Oracle University. Let me introduce you to Oracle Cloud Infrastructure Registry. Let's first understand what is it? Oracle Cloud Infrastructure Registry, also known as Container Registry, is an Oracle managed Registry that enables you to simplify your development to production workflow. Container Registry makes it easy for you as a developer to store, share, and manage container images, and the highly available and scalable architecture of Oracle Cloud infrastructure ensures you can reliably deploy your applications, so you don't have to worry about operational issues or scaling the underlying infrastructure. You can use Container Registry as a private Docker Registry for internal use, pushing and pulling Docker images to end from the Container Registry, using the Docker v2 API, and the standard Docker command line interface. You can also use Container Registry as a public Docker registry, enabling any user with Internet access and knowledge of appropriate URL, to pull images from the public repository in Container Registry. Let's take a look at what problem does it solves? Without a registry, it is hard for the development teams to maintain a consistent set of Docker images for their containerized applications. Developers, testers, NCI systems need to use Registry to store images created during the application development process. OCIR makes it possible to iterate on code faster, and push it to the production more frequently. Without a managed registry, it is hard to enforce access rights and security policies for images. OCIR is integrated with Identity Access Management, which provides easy authentication with native Oracle Cloud infrastructure identity. It is hard to find right images and have them available in the region of deployment. Container Registry is an open container initiative compliant registry. As a result, you can store any artifacts that conform to open container initiative specifications, such as Docker images, Manifest list, and Helm charts. If you are familiar with the function service of OCI, the function service also makes use of OCIR. The function code in OCI is packaged as a Docker image, and pushed to the OCIR. The event triggers can be configured in the events service to make sure when the function is invoked. Let's take a look at some key benefits of OCIR. Integration. OCIR provides full integration with Container Engine for Kubernetes. When it comes to security, Registries can be made private, or can be made public by an admin. Regional availability. You can easily pull Container images quickly from the same region as your deployments. High availability. It leverages OCI for high-performance, high availability, and low-latency image push and pull to or from the OCIR. Anywhere access. You can use Docker CLI to push and pull images from anywhere. Maybe Cloud, on-premises, or through your personal laptops. In each region that is enabled for your tenancy, you can create up to 500 repositories in Oracle Cloud Infrastructure Registry, consuming a maximum of 400 GB in total, and each repository can hold up to 100,000 images at a time. Before we move further, let's take a look at Container Registry concepts. What are Docker images? Docker image is basically a read-only template with instructions for creating a Docker container. It holds the application that you want Docker to run as a container along with any dependencies that are required. Repository. It's a meaningfully named collection of related images which are grouped together for convenience in a Container Registry. There are different versions of the same source image which are grouped into the same repository. For example, as you can see, we have a repository called mahindra_project/acme-web-app. Now, you can have multiple images stored under this repository. The only thing that you need to keep changing is the image version. Every image version is given a tag, and the tag uniquely identifies the image. Depending upon your need, a repository can be made private or public. One important thing to note is that user needs to have an OCI username and authentication token before being able to push, pull an image from the OCIR. When working with repositories in Container Registry, you will find it helpful to have a clear understanding of following terms, and how they relate to each other. The region key. The region key identifies the Container Registry region that you are using. For example, as you can see over here, the IAD specifies the US East Ashburn region, whereas the us-phoenix-1, specifies the US West Phoenix region. Repository name is the name of repository in Container Registry to and from which you can push and pull images. Repository names can include one or more slash characters, and are unique across all the compartment in the entire tenancy. You should note that although our repository name can include slash characters, the slash does not represent a hierarchical directory structure. It is simply one character in the string of characters. As a convenience, you might choose to start the name of several different repositories with the same string, perhaps ending in a slash, such as project 01/. Such as string is sometimes called a repository name prefix. But a repository named project01acme-web-app, may not have a relationship with project team, project01/mytest-app. A tenancy namespace is an auto-generated, random, and immutable string of alphanumeric characters. For example, the namespace of acme-dev tenancy might be this random string. How to locate your tenancy namespace will be shown during the demo. A Registry identifier is the combination of your Container Registry region key, and the tenancy namespace. It has the following structure. As you can see, it starts with the region key, and followed by the tenancy namespace. Also make a note that tenancy namespace can be a random string, or it can be a regular name. A tag or image tag is a string used to refer to a particular image in an own repository. Image name. The term image name is sometimes used as a shorthand way to refer to a particular image in a particular repository. In this context, an image name has the structured repository name along with tag, separated by colon. An image path is a fully qualified path to a particular image in a registry. It extends the repository path by adding tags associated with the image. It has the following structure. It starts with the region key, followed by the tenancy namespace, the repo namespace, followed by tag, separated by colon. You can always refer Oracle's documentation to identify the region key for the region you're working in. To wrap up, in this lesson, I introduced you to OCIR service, which is an Oracle Managed Container Registry, and discussed key concepts and terminologies that will help us dive deep in the upcoming lessons. I hope you found this lesson useful. Thanks for watching.