OpenDaylight video of YANG on Liangzi, spicy chicken, it will depend on the amount of players and the number of points like this, not superstition official
Link Operational and config differences
Operational differences and config
Config & operational (data store two forms)
the Data Store in data storage are two forms: config and operational, config data held by written application, but reflect the actual operational state of the device, reading data from the device, if no error which can actually see the current information about the device.
config data store query generally does not include the flow table entry to the routing table for the stream object (which is why the operational mode can query the table-miss flow entry, i.e. out-port: controller, but can not find config mode), but OpenDaylight developers said this aspect of the future may change, but the reason for this is because these streams flow through an external service (without dataStore and config) sent to the device, which then flows through the device in the form of operational data in the form of newspaper back again.
config with respect to the life cycle of the controller (or even restart can still survive). The flow entry is added by an application and here, when a suitable device will be sent to it.
In principle openflowplugin and controller should not use config. This is reserved for the application, such as listening to FRM wrote on config change to send to flow inside the device. This can be used for pre-configuration - the application can write some "useful" not yet exist for a number of flow devices, once the existence of related equipment will be issued to the stream which, without application of any action.
Hair configuration (post, put), may be generally used to obtain the Config information (GET)
Operational usually obtain the actual device information (GET), the contents and config data store operational data store may be different, but the different modules both designs may not be the same as illustrated:
For openflow protocol: operational information reflecting the actual device, if the configuration issued, the process is config-> device-> operational
For bgp agreement: to deliver the configuration process is: config-> operational-> device
Respondents @ earth cloud network
no less installed plug-ins, nodes should be operational data, not the data config
API/url
payload
Collection Postman
Link
blog about YANG speak clearer
Link OpenDayLight controller: YANG Schema Model and
the biggest inspiration to write this blog is also very good, their own efforts to translate, then hang a link. Report this week will be able to quickly find the original English text
link to this blogger YANG speak good