My first doubt is that I assumed that I would be able to use the “content view” as “Installation Media” to do the initial OS deployment but I realized I cannot. What I did is to create “installation media” with url “http://my-katello-server.com/pulp/repos/Default_Organization/Library/custom/Centos_7_3/base_x86_64/” . Is this the recommended approach or should I do it differently
You can do it this way, but the recommended method is to use ‘Synced Content’ instead of installation media. When creating a new host or host group, if you select a Content View, Lifecycle Environment, Content Source, Arch and Operating System, it should then allow you to select a kickstart repo to install from without creating installation media. This will also allow you to use kickstart repos that are in your content views.
As a workaround I tried to modify the snippet to do something like “rpm -ivh http://my-katello-server.com/pulp/repos/Default_Organization/Library/custom/Centos_7_3/base_x86_64/Packages/subscription-manager.rpm” but I cannot find the subscription-manager rpm when accessing “http://my-katello-server.com/pulp/repos/Default_Organization/Library/custom/Centos_7_3/base_x86_64/Packages/” with my browser. The weird thing is that If I go to “Products >> Centos_7.3 >> Repositories >> base_x86_64 >> Packages” in the webui I can find the “subscription-manager” rpm and this repo is included in my content view
For Centos, that is the best method. The reason it doesn’t show up when browsing is most likely because this repository is set to “On Demand” (the default value). On demand repositories do not actually download any rpms until they are requested by a client (or browser). After being requested once, they will show up in 5-10 minutes while browsing the repo.
If you don’t want to use the on demand download policy, simply change that repo to ‘immediate’ and re-sync the repo. That will cause all rpms to be download to the server.