spray.can.server.parsing.max-content-length=70m
Customizing bpocore configuration settings for clusters
CAUTION! Use this procedure only if you have discussed it with Ciena Customer Service. Changing bpocore configuration settings are at your own risk and might result in incompatibilities with other containers or releases.
This procedure describes how to change bpocore configuration settings in a single file on one host and share them across all nodes in a cluster.
The following list describes the configuration sources bpocore reads:
-
deploy.conf—Override values specified for the deployment; includes multiple .conf files that are dynamically written based on the deployment environment and information from application Blue Planet Orchestration hooks
-
bpocore.conf—Specific settings may be set in /etc/bp2/bpocore/bpocore.conf
-
override.conf—Introduced in bpocore:1.5.1; specific settings may be set in /etc/bp2/bpocore/override.conf
On a Blue Planet host, perform these steps to create an override.conf file. See the previous Caution! statement before you complete this procedure.
-
For a single host, create and edit a file named /etc/bp2/bpocore/override.conf to contain a configuration setting that you wish to override. Find configuration details at https://github.com/typesafehub/config.
For example, to increase the maximum size of the payload in a REST API request, include the following line:
-
On a multi-host site, create this file on a single host then:
-
copy it to other hosts:
bp2-site sync-site-config -
check that all the hosts are in sync:
bp2-site diff-site-config
-
-
Restart the bpocore app.
$ solman "solution_app_restart <solution> bpocore"
where <solution> is the name of the Orchestrate solution; for example, bpdr.io.blueplanet.orchestrate:ha-17.06.1-123.