Documentation/SupportedImages/BuildingBaselineImage: omf-resctl.yaml

File omf-resctl.yaml, 2.3 KB (added by seskar, 5 years ago)

OMF Resource Controller 5.4 configuration file

Line 
1# This is an example configuration for the Resource Controller at NICTA
2#
3# NOTE: use only 'spaces' to indent !
4# ('tab' indents are not supported by the ruby yaml parser used to read this file)
5#
6---
7:rcontroller:
8  # Communication settings
9  :communicator:
10
11    # Number of seconds between consecutive HEARTBEAT messages
12    :heartbeat_interval: 10
13   
14    # Interface to the control network from which this resource can be
15    # controlled & managed
16    :control_if: 'eth1'
17
18    # set this to true or false if you want to enable or disable signature checks and message signing                                       
19    :authenticate_messages: false
20    # your RSA/DSA SSH private key file
21    :private_key: '/etc/omf-resctl-5.4/id_rsa'
22    # directory holding the public keys of your OMF peers
23    :public_key_dir: '/etc/omf-resctl-5.4/peer_keys'
24   
25    :type: 'xmpp'
26    :xmpp:
27      # Address of the PubSub server to use as gateway for PubSub communication
28      :pubsub_gateway: 'xmpp2.orbit-lab.org'
29
30      # Address of the PubSub server which host the communication for my slice
31      # Leave this commented if the pubsub groups for this slice are hosted on
32      # the same server as the 'pubsub_gateway'
33      #:pubsub_domain: 10.0.0.200
34      # The following 'home_pubsub_user' and 'home_pubsub_pwd' are optional
35      # RC will create a unique user/pwd for itself if this is not provided
36      # In a typical OMF install, you should not uncomment these lines
37      # (do so only if you need to manually set user/password for
38      # your client to connect to your pubsub server)
39      #:pubsub_user: 'my_RC_name'
40      #:pubsub_pwd: 'my_RC_password'
41
42  # Agent settings
43  :agent:
44
45    # Name (i.e. unique HRN ID) of this resource
46    # Or this could also be passed as a command line parameter "--name"
47    # This is either a fully defined string, e.g. "my_resource_name"
48    # Or a string for which some values will be replaced by the running RC,
49    # currently we support the values: %hostname% %macaddr%
50    # For example, if you use "some_prefix.%hostname%.some_suffix"
51    # Then if your hostname is 'node1', then your RC name will be
52    # 'some_prefix.node1.some_suffix'
53    # %macaddr% is replaced with the MAC address of the control interface
54    :name: '%fqdn%'
55
56    # Name (i.e. unique HRN ID) of the slice to which this resource is assigned
57    :slice: default_slice
58