You need to use a patch analysis job, and select the ‘install mode’ on the 2nd tab. Add a filter for just the rpm name you want and run the job – that will create a deploy job w/ the deps.
For all the things you can do with yum, some people might have used satellite to install /upgrade rpms on redhat,
Everything , all those actions can be done using BladeLogic.
As suggested by Bill, create a patch catalog point it to your repository containing all rpms required. It can also be one huge repository containing many rpms or complete redhat channel.
Do a patch catalog update and then use a patch analysis job in install mode with include list as one of the main rpms you intend to install.
It will automatically fetch all dependencies and give you a deploy job, it uses yum install behind the scenes , BladeLogic's very own yum called Blyum shipped with every agent.
Thanks for the information guys.
It seems to make this patch functionality work I need to create my own RPM repo outside of Bladelogic since it wants to point to a patch catalog. I don't want it to be pulling down the latest version from a public repo everytime it runs. This seems very cumbersome looking at it from a new perspective. That means that we'll need to create yet another server to host the RPM repo -- or am I missing something? I already imported the RPMs into Bladelogic, but it doesn't appear to let me be able to use them.
The advantage of using patch functionality is that you don't have to worry about the dependencies, the job will do that for you.
Otherwise, you can add all rpms , you should know the complete list of dependencies yourself, add them to depot
Create a rpm group in a blpackage, add all these rpms to the rpm group inside a blpackage.
1 of 1 people found this helpful
For blade patching you need a redhat helper. It does not need to have httpd running. so you can build a repo of your custom rpms on that server. there’s a section in the user guide about how to import custom reports using the offline downloader (you don’t actually download anything, the downloader runs createrepo among other things).
The only way to get rpms to install and have them automatically resolve dependencies is to have them in a repo and use yum, or have the whole set of rpms available when you run the rpm –Uvh command. if you already know all the deps you need to install you can create a blpackage that contains all the rpms w/ all the deps. If you don’t know all the deps, then the rpms you are installing need to be in a repo.
It sounds like you may have all of the rpms that you need, then in that case I think a rpm group should work. how did you create it?
Thanks everyone. I just wanted to let you know I used the Group concept since I knew all the dependencies and the package deployed succesfully!
Onwards and upwards!