As a desktop support analyst, you can set up mirrors of a Debian repository to help ensure easy access and faster download of the packages at the target computers. The following diagram illustrates the steps that you perform to set up Debian mirror repositories:
Perform the following tasks to set up Debian mirror repositories:
Verify the following prerequisites to help ensure that the mirror and synchronization work properly:
Note: Only Linux variants are supported for mirrors. For example, you can host the mirror repository on a Linux scalability server.
Install the add-on package on computers that host the mirror repository. The add-on enables the computer for mirror synchronization.
Important! Mirror synchronization fails if you do not install the add-on package.
Follow these steps:
A software job is created for each computer that you selected.
When the job is completed, the job status changes to SW Installed.
Define the details of the parent repository for the mirror. A parent repository can be a master repository or a mirror repository because you can create a mirror from a master repository or from another mirror repository. You can define multiple mirrors of a parent repository depending on the network traffic, load, and sites you want to support. For example, if you decide to have two mirrors at each site and you have five different office sites, you need ten mirrors of the parent repository.
Note: The steps are the same as defining the external repository, except that you need to define whether the parent is a master or mirror.
Follow these steps:
Note: The changed configuration policy must be applied to all the target computers. Hence, select the Default Configuration Policy.
The policy becomes editable.
Specifies a unique repository name. You can specify any name but verify that the name is unique across the Repositories table.
Specifies whether the repository is a master, mirror, or mirror template.
Specifies that the repository is a master. A master repository is used while creating wrapper packages. CA ITCM cannot deploy native Debian packages directly. Create wrapper packages that include references to the native Debian packages and then deploy the wrapper packages.
Following guidelines apply for master repositories:
Specifies that the repository is a mirror that is created from a master or another mirror.
Specifies that the mirror is only a template and not a physical repository. The mirror template is only a placeholder for multiple mirror repositories that have the same configuration. When you have numerous mirrors, you can create one mirror template per parent instead of creating a row each for all the mirrors. Mirror templates are used for software deployment and repository extraction but not for mirror synchronization. The host name of the computers hosting the mirrors is dynamically replaced at run time.
Specifies the repository type.
Specifies the transfer protocol that is used for transferring the packages from the repository to the target computers. Select HTTP, FTP depending on what you have configured. For more information about this configuration, see Setting Up FTP and HTTP Share for Software Packages and OS Images.
Note: If the repository is a master and you want to browse the repository and create wrapper packages from it, configure the repository as an FTP share.
Specifies the host name of the computer that hosts the repository. For mirror template repositories, do not specify the host name because the host name is dynamically provided at run time. Even if you specify, the host name is ignored for mirror templates.
Specifies the root node of the repository.
The parent repositories information is updated on all target computers.
The synchronization job requires that you define the mirror synchronization details for each mirror repository. The job uses these details to synchronize the mirrors.
Follow these steps:
You need a new policy for mirror synchronization so that you can apply the synchronization details only to the computers that host the mirrors.
Specifies the parent repository you want to mirror.
Note: Verify that the parent repository name you specify in this field exactly matches the name specified in the Default Configuration Policy, DSM, Software Delivery, Shared, External Repositories, Debian, Repositories configuration table. If the names do not match, the synchronization job fails at run time.
Specifies the list of the distributions from the selected repository that must be mirrored. You can specify more than one value by separating each value with a space.
Specifies the list of the components from the selected repository that must be mirrored. You can specify more than one value by separating each value with a space.
Specifies the list of the architectures from the selected repository that must be mirrored. You can specify more than one value by separating each value with a space.
Specifies the location where you want to create the mirror repository.
Note: Verify that this location is exposed as both HTTP and FTP shares. For more information about setting up HTTP and FTP shares, see Setting Up HTTP and FTP Share for Software Packages and OS Images.
Specifies the additional arguments that are used while launching the debmirror utility.
Specifies whether you want to synchronize the mirror or not. If you are not using a mirror repository actively, you can disable the synchronization without deleting the mirror.
The mirror synchronization details are defined and the configuration is applied on the mirror computers.
Schedule the mirror synchronization to automatically synchronize the mirror with its parent repository at the scheduled time. The mirror repository is created when the synchronization job runs successfully for the first time after you have defined the mirror synchronization details.
Follow these steps:
The mirror synchronization is scheduled. At the scheduled time, the CAF Scheduler synchronizes the mirror with the parent repository.
After the mirror synchronization job is executed, follow these steps to verify whether mirror synchronization was successful and CA ITCM is able to connect to the mirrors.
You can view the status of the last synchronization to verify whether the mirror synchronization was successful.
Follow these steps:
The External Repositories page appears.
Specifies the result of last mirror synchronization. A successful synchronization returns 0 and a failure returns a non-zero value.
If the synchronization failed, follow these steps:
The mirror synchronization log is displayed.
Extracting package metadata from the repository lets you view the Debian package details on DSM Web Console.
Note: The following steps apply for extracting the package metadata from both master and mirror repositories.
Follow these steps:
The engine log is displayed.
The New Task Wizard opens.
Note: Ensure that you disable the system firewall to execute the task successfully.
Note: As the repository server is on Linux, values provided in the following Distribution and Components Name fields must be case-sensitive; they must match the case in the repository server. For example, if the repository server location for ftp://172.16.0.12/ubuntu/dists/lucid/main/binary-i386/, the distribution name must be specified as lucid and not as Lucid or LUCID.
Specifies the repository name from which you want to extract the package metadata. The list displays the repositories you had defined in the Repositories configuration table.
Note: You cannot create two engine tasks with the same repository and distribution combination.
Specifies the host name of the repository. This field is enabled only for repositories of type Mirror-Template. For the master and mirror repositories, the host name is automatically taken from the Repositories configuration table.
Specifies the distribution from which you want to extract the package details.
Note: An engine task can extract data only from a single distribution. If you want to extract data from multiple distributions, create additional engine tasks.
Specifies the components that you want to extract. Click Add to add more components.
The System Engine creates the task and executes it at the schedule time. You can monitor the task by clicking the SystemEngine and review the status in the Task List section on the right pane.
Note: You can also browse the repository from Web Console while the engine task is still in progress. The Web Console displays the distributions and packages as and when they are extracted from the repository.
You can browse the contents of a Debian repository in Web Console to know what packages are present in the repository.
Follow these steps:
A list of distributions in the selected repository is displayed. The Synchronization Status column shows the status of the repository extraction task. You can also click View under the Synchronization Log column to view the progress of metadata extraction and errors that are encountered, if any.
Note: If you open the repository before the extraction task completes, it is possible that you do not see all the distributions in the list.
A list of Debian packages in the distribution is displayed.
For Kubuntu deployments, you are required to set up FTP or HTTP share to store software packages and OS images.
See Setting Up FTP or HTTP Share for Software Packages and OS Images section in OSIM Administration Guide for more information.
|
Copyright © 2013 CA.
All rights reserved.
|
|
