SUSE Conversations


ZLM 7.2 IR1 >= HP3, Mirroring Security, Optional, Recommended, and Kernel Only

cseader

By: cseader

May 5, 2008 2:36 pm

Reads:235

Comments:0

Rating:0

Looking for a way to filter out the Security, Optional, Recommended or just want to filter the Kernel only? This is a must read.

You must be at ZLM 7.2 IR1 with Hot Patch 3 or greater in order to get this to work. If you have not applied any Hot Patches you will want to send an email to zen.feedback@novell.com with the subject line “ZLM7.2 IR1 Hot Patch” so that you can get the information you need to update your ZLM Server and Clients to the latest Hot Patch.

Below are some example zlmmirror configuration files that you can use to accomplish the filtering spoken of. Please feel free to read my ZLM Lab Guide located here for more information on the setup and troubleshooting of your environment.

Mirroring Security Patches

This is accomplished in a pretty easy fashion with the following zlmmirror configuration. You can adapt this configuration with additional targets if needed. Note the LocalName tag which is for the local name of the Catalog that will be created. Also note the ExcludeBundle tag which includes the kernel to be excluded in this filter. If you would like to include the kernel in the security patches you would just remove that tag.

<ZLMMirrorConf>
   <Session>
      <RemoteServer>
         <Base>https://nu.novell.com/repo</Base>
         <Type>nu</Type>
	 <User>xxxx</User>
	 <Password>xxxx</Password>
      </RemoteServer>
      <LocalServer>
         <Type>zlm</Type>
         <User>administrator</User>
         <Password>novell</Password>
      </LocalServer>
      <Catalog>
         <Name>SLES10-SP1-Updates</Name>
	 <LocalName>SLES10-SP1-Security</LocalName>
         <Folder>sles-10-i586/SP1/patches</Folder>
         <Target>sles-10-i586</Target>
	 <ExcludeBundle>patch-slesp1-kernel.*</ExcludeBundle>
      </Catalog>
   </Session>
</ZLMMirrorConf>

In order to accomplish mirroring the Security patches you will need to run this command:

zlmmirror m --category=security -c /location/of/zlmmirror/configuration

Mirroring Optional Patches

This just like the Security patches can be accomplished with the following zlmmirror configuration. You can adapt this configuration with additional targets if needed. Note the LocalName tag which is for the local name of the Catalog that will be created. Also note the ExcludeBundle tag which includes the kernel to be excluded in this filter. If you would like to include the kernel in the optional patches you would just remove that tag, that is if there is ever any kernel that’s labeled optional :).

<ZLMMirrorConf>
   <Session>
      <RemoteServer>
         <Base>https://nu.novell.com/repo</Base>
         <Type>nu</Type>
	 <User>xxxx</User>
	 <Password>xxxx</Password>
      </RemoteServer>
      <LocalServer>
         <Type>zlm</Type>
         <User>administrator</User>
         <Password>novell</Password>
      </LocalServer>
      <Catalog>
         <Name>SLES10-SP1-Updates</Name>
	 <LocalName>SLES10-SP1-Optional</LocalName>
         <Folder>sles-10-i586/SP1/patches</Folder>
         <Target>sles-10-i586</Target>
	 <ExcludeBundle>patch-slesp1-kernel.*</ExcludeBundle>
      </Catalog>
   </Session>
</ZLMMirrorConf>

In order to accomplish mirroring the Optional patches you will need to run this command:

zlmmirror m --category=optional -c /location/of/zlmmirror/configuration

Mirroring Recommended Patches

Use the following configuration for filtering for recommended patches. You can adapt this configuration with additional targets if needed. Note the LocalName tag which is for the local name of the Catalog that will be created. Also note the ExcludeBundle tag which includes the kernel to be excluded in this filter. If you would like to include the kernel in the optional patches you would just remove that tag, that is if there is ever any kernel that’s labeled Recommended :).

<ZLMMirrorConf>
   <Session>
      <RemoteServer>
         <Base>https://nu.novell.com/repo</Base>
         <Type>nu</Type>
	 <User>xxxx</User>
	 <Password>xxxx</Password>
      </RemoteServer>
      <LocalServer>
         <Type>zlm</Type>
         <User>administrator</User>
         <Password>novell</Password>
      </LocalServer>
      <Catalog>
         <Name>SLES10-SP1-Updates</Name>
	 <LocalName>SLES10-SP1-Recommended</LocalName>
         <Folder>sles-10-i586/SP1/patches</Folder>
         <Target>sles-10-i586</Target>
	 <ExcludeBundle>patch-slesp1-kernel.*</ExcludeBundle>
      </Catalog>
   </Session>
</ZLMMirrorConf>

In order to accomplish mirroring the Recommended patches you will need to run this command:

zlmmirror m --category=recommended -c /location/of/zlmmirror/configuration

Mirroring the Kernel Only

Use the following configuration for filtering for Kernel patches only. You can adapt this configuration with additional targets if needed. Note the LocalName tag which is for the local name of the Catalog that will be created. Also note the Bundle tag which includes the kernel to be included in this filter so that it just mirrors the kernel.

<ZLMMirrorConf>
   <Session>
      <RemoteServer>
         <Base>https://nu.novell.com/repo</Base>
         <Type>nu</Type>
	 <User>xxxx</User>
	 <Password>xxxx</Password>
      </RemoteServer>
      <LocalServer>
         <Type>zlm</Type>
         <User>administrator</User>
         <Password>novell</Password>
      </LocalServer>
      <Catalog>
         <Name>SLES10-SP1-Updates</Name>
	 <LocalName>SLES10-SP1-Kernels</LocalName>
         <Folder>sles-10-i586/SP1/patches</Folder>
         <Target>sles-10-i586</Target>
	 <Bundle>patch-slesp1-kernel.*</Bundle>
      </Catalog>
   </Session>
</ZLMMirrorConf>

In order to accomplish mirroring the Kernels you will need to run this command:

zlmmirror m -c /location/of/zlmmirror/configuration

Enjoy!

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags: ,
Categories: SUSE Linux Enterprise Server, Technical Solutions

Disclaimer: As with everything else at SUSE Conversations, this content is definitely not supported by SUSE (so don't even think of calling Support if you try something and it blows up).  It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.

Comment

RSS