Managing Image Repository
The image repository is the bridge between the OSD Manager and the deployment target. Contrary to the OSD Manager it is platform independent and thus can be any device with a CM agent . It does not build any deployment projects, it stores projects it is assigned by the OSD Manager, thus it requires a large amount of hard disk space to store the cached data. The image repository communicates very regularly with the OSD Manager to ensure its cached files are still valid.
In a perfect architecture you would have one image repository per physical site, which would then have one network boot listener per subnet as children. An image repository can be a network boot listener at the same time, but it can only have another image repository or the OSD Manager as a parent. It can have other image repositories and network boot listeners as children.
An image repository has the following tabs and subnodes:
- Members
- Storage
- Configuration
- One node for each defined Image Repository
- One node for each defined Network Boot Listener
Sizing requirements
The image repository needs to store the project data, which tend to be quite large. You need to preview the following storage space on the hard disk of the image repository:
- size of the image file
- each project, activated or not, takes approximately an additional 250MB without drivers
- size of the attached drivers
This section includes:
Comments
Log in or register to comment.