| | 41 | === Configuration format === |
| | 42 | Ariba 0.9.x uses a new configuration format, based in boost::property_tree. Hence you can use the JSON format to store ariba configs. Other formats (e.g. XML) are supported, too. Please refor to the documentation: [http://www.boost.org/doc/libs/1_46_1/doc/html/property_tree.html Boost.PropertyTree] |
| | 43 | |
| | 44 | '''Example configuration file''' |
| | 45 | {{{ |
| | 46 | //JSON |
| | 47 | { |
| | 48 | "ariba": { |
| | 49 | "node_name": "Node1", |
| | 50 | "spovnet_name": "pingpong", |
| | 51 | |
| | 52 | "listen_on": [ |
| | 53 | {"category": "TCPIP", "addr": "::", "port": 5000 } |
| | 54 | ], |
| | 55 | |
| | 56 | "bootstrap": { |
| | 57 | "direct": [ |
| | 58 | {"category": "TCPIP", "addr": "127.0.0.1", "port": 41322 } |
| | 59 | ], |
| | 60 | } |
| | 61 | } |
| | 62 | } |
| | 63 | }}} |
| | 64 | |
| | 65 | - As in earlier ariba versions the ''node_name'' and the ''spovnet_name'' can be specified. Please keep in mind that node names must be unique and all nodes must use the same spovnet name in order to communicate. |
| | 66 | - ''listen_on'' describes an array of local addresses, on which ariba will listen. |
| | 67 | - Since bluetooth is currently disabled, `category` must be `TCPIP` |
| | 68 | - `addr` can either be an ipv4 or ipv6 address ("::" is the ipv6 any-address) |
| | 69 | - a port can be specified, if port 0 is given, ariba will try to find a usable port (starting with port 41322) |
| | 70 | - ''bootstrap'' defines the bootstrap hints, the nodes ariba tries to connect in order to join the spovnet |
| | 71 | - Since the bootstrap modules are currently disabled, only direct bootstrapping is available |
| | 72 | - ''direct'' describes an array of remote endpoints ariba tries to connect to (same syntax as the `listen_on` field) |
| | 73 | |
| | 74 | Note that all ariba related config is stored in a field named `ariba`. The same JSON file can be used to store application specific config data as well. |
| | 75 | |
