SDP-743
Open
Enhance load_checkpoint.sh to use full checkpoints for new edges.
The '-t <Type>' will indicate a the server type, and this value
is inferred from '-s <ServerID>' if the SDP Server Spec Naming
Standard is followed.
The normal workflow for creating edge servers is to use the SDP
edge_dump.sh to create a special edge seed checkpoint, and then
load that checkpoint.
This special seed checkpoint must be used for existing edge servers
(those with any useful local data) and if the edge server is
filtered.
However, when creating new edge servers, it may be more convenient
to use a full checkpoint taken on the master rather than creating
a special purpose checkpoint using edge_dump.sh, since standard
checkpoints are readily available from routine processing on the
master. When loading checkpoins for an edge server,
load_checkpoint.sh must handle the exclusion of edge-specifc
tables.
The '-t <Type>' will indicate a the server type, and this value
is inferred from '-s <ServerID>' if the SDP Server Spec Naming
Standard is followed.
The normal workflow for creating edge servers is to use the SDP
edge_dump.sh to create a special edge seed checkpoint, and then
load that checkpoint.
This special seed checkpoint must be used for existing edge servers
(those with any useful local data) and if the edge server is
filtered.
However, when creating new edge servers, it may be more convenient
to use a full checkpoint taken on the master rather than creating
a special purpose checkpoint using edge_dump.sh, since standard
checkpoints are readily available from routine processing on the
master. When loading checkpoins for an edge server,
load_checkpoint.sh must handle the exclusion of edge-specifc
tables.
- Status
- Open
- Project
- perforce-software-sdp
- Severity
- C
- Reported By
- C. Thomas Tyler
- Reported Date
- Modified By
- C. Thomas Tyler
- Modified Date
- Owned By
- tom_tyler
- Component
- core-unix
- Type
- Feature