Distributing Release Bundles to the PDN Nodes
This procedure describes how to distribute existing Release Bundles to the PDN Nodes and groups.
To distribute a Release Bundle to PDN, the PDN Nodes must be under a PDN Group.
- From Application | Distribution | Release Bundles select the Release Bundle you want to distribute, and click
The Distribute Release Bundle window appears with the PDN hierarchal view. .
Select the relevant Edges and groups you want to distribute to.
If you select the Edge, the Release Bundle will be distributed to all the groups and nodes under that Edge. If you want to distribute to specific groups, you must select those groups individually. If you select a group, the Edge will also receive the Release Bundle.
- Optional: If you wish to automatically create missing repositories when distributing the Release Bundles, select the checkbox Automatically Create Missing Repositories.
- Click Distribute.
- You can view the status of the distribution from the Distributable tab.
- Click View to see the detailed status/availability of each Release Bundle.
Download Artifact Cache Size
When downloading artifacts, the size of the downloads may exceed the maximum cache size in your system (this is the parameter
maximumMbToKeep). The size will only be exceeded temporarily while downloading, and may appear as such in the JFrog Platform UI. The excess cache will be automatically and immediately deleted once the artifacts have been downloaded successfully.
Distributing a Dynamic Release Bundle
You can distribute a dynamic Release Bundle, which is a Release Bundle you can create, sign, and distribute on the fly, using the Dynamic Release Bundle REST API. The Release Bundle version is created instantly and distributed to the selected PDN Nodes.
Support Bundle Collection
Support Bundles collection for PDN works by Artifactory calling on each PDN Server to collect the Support Bundle data. All the data is then propagated to the main PDN Server's directory (in a High Availability environment, Support Bundles are allocated under each PDN Server). For more information, see Support Zone.
Using PDN Nodes with AWS
By default AWS uses a "tee" process (that runs by default on any EC2 instance) to pipe everything that is written to the
stdout to the
cloud-init.log. When a PDN Node is running in debug mode, it generates a lot of log messages, and when these logs are flushed to the file, this impacts the PDN node functionality. To overcome this issue, the PDN Node output must be redirected from the
stdout/stderr to the output file using the following command on the PDN node: