Two related statements enable you to configure JUNOS SDK services on a system level:
- [edit]
- system {
-
- extensions {
- providers provider-id;
- }
- }
You enable installation of a JUNOS SDK application by configuring its provider ID, a short string supplied by the provider. The provider-id, as it is called in the command-line interface (CLI), is part of the certificate name. The application’s certificate name is used to sign the package during the build process, as explained in the JUNOS SDK installation instructions. When a provider ID is enabled on a router, any SDK application package built using that prefix can be installed and run on the router. Multiple prefixes can be enabled on a router.
- [edit]
- chassis {
-
- fpc slot-number {
-
- pic pic-number {
-
- adaptive-services {
-
- service-package {
-
- extension-provider {
- control-cores control-number;
- data-cores data-number;
- object-cache-size value;
- }
- }
- }
- }
- }
- }
There are eight cores on a PIC. Some cores, called control cores, are dedicated to run control functionality for the application. Cores dedicated to processing data for the application are called data cores. You must set at least one control core using the control-cores option. Setting the data-cores option is optional. The total number of cores, control and data cores, that can be set using the extension-provider statement ranges from 1 through 8. Any cores not configured as control or data cores are treated as user cores.
The object-cache-size statement is used to tune SDK application performance.
In the following example, all but one of the available cores are configured. Three cores are control cores, four are data cores, and one is a user core.
- [edit]
- chassis {
-
- fpc 0 {
-
- pic 1 {
-
- adaptive-services {
-
- service-package {
-
- extension-provider {
- control-cores 3;
- data-cores 4;
- }
- }
- }
- }
- }
- }