operations center enables the sharing of cloud configuration across the Client Masters in the operations center cluster.
The sharing model used for shared cloud configuration is similar to the shared configuration propagation.
Unlike shared clouds or shared agents, shared cloud configuration replicates the configuration of the cloud provider to the specified Client Masters such that each Client Master has separate control of the cloud rather than leasing agents from the operations center server.
Other clouds may be available in future software upgrades.
|The shared cloud configuration is licensed individually for each cloud type.|
The plugin defining the configuration must be installed on the Client Masters within scope for using
The plugin versions on the Client Master(s) and the operations center server must be compatible in terms of configuration data model.
|Violations of the requirements above may have a serious impact on cloud provisioners on Client Masters. The service administrators should ensure|
Shared configurations should be created as Jenkins items like Client Masters, folders and templates using the
New Item action on the left hand menu in operations center. Items can be created at the root of the instance or within a folder.
If you create in the root of operations center, the cloud will be available to all Client Masters
If you create a shared cloud configuration item in a folder, the cloud will be available only to Client Masters within the folder or within the folders sub-folders.
Click on the "New Item" action in Jenkins root or a folder. In both cases you will be presented with the standard new item screen.
Provide a configuration name
Cloud Configurationtype that you wish to create.
OKbutton. A new configuration window will appear
Options are similar to the standard Jenkins cloud configuration options.
|if a cloud provider requires configuration of native tools or libraries then this location must be the same on all Client Masters that receive this configuration in order to operate correctly|
When the shared cloud configuration is complete save or apply the configuration.
The cloud configuration will be pushed to all online Client Masters that have not opted out. of receiving shared configuration. If a Client Master is offline, the new configuration will be applied when this master connects to operations center.
Below you can find configuration examples for the supported clouds.
As mentioned earlier, prior to configuring a shared-cloud ensure that the plugin defining the launcher
is installed on all the Client Masters within scope for using the shared cloud. === === Docker shared cloud configuration
Please refer to the Docker plugin’s Wiki page to find setup guidelines and info about supported configurations. This section describes the operations center specifics only.
Container caps are being managed individually for each Client Master, there is no global limitations of the containers number
Current Docker Plugin version supports TLS connection options via environment variables only. These environment variables are not being distributed to Client Masters by Docker Shared Cloud Configuration. These environment variables should be set up on Client Masters using other Jenkins features
Please refer to Amazon EC2 plugin’s Wiki page to find setup guidelines and info about supported configurations. This section describes the operations center specifics only.
Instance caps are being managed individually for each Client Master, there is no global limitation for the entire operations center cluster.
If you use
Access Key IDand
Secret Access Keyto define EC2 credentials, these credentials will be shared across all CloudBees Jenkins Enterprise instances. EC2 must allow multiple logins from different places if have multiple Client Masters
If all target CloudBees Jenkins Enterprise instances are running on EC2 instances, you can use
EC2 instance profileto obtain credentials from the instance metadata
Currently there is no opportunity to setup different
Regionsfor CloudBees Jenkins Enterprise instances in AWS EC2 Shared Cloud Configuration. In such case use individual setups of EC2 Cloud on each master
If you click on the
Test Connectionbutton in the configuration, the test will be launched on operations center. Make sure that the AWS EC2 cloud is available to operations center.
If the instance is configured to obtain credentials from
EC2 instance profile, operations center must be running on a properly configured Amazon Machine Image
You can also test the connection from one of Jenkins Client Masters when the configuration gets synchronized. It’s highly recommended if your AWS EC2 Shared Cloud Configuration uses
EC2 instance profileto obtain credentials
This Shared cloud configuration allows sharing of settings for Microsoft Azure cloud.
Please refer to Azure Slave plugin’s Wiki page to find setup guidelines and info about supported configurations.This section describes the operations center specifics only.
Instance caps are being managed individually for each Client Master. There is no global limitation for the entire operations center cluster.
The PublishSettings (Microsoft Azure Subscription Manifest) credentials will be shared across all CloudBees Jenkins Enterprise instances.