BEER YANG at the DOCKS
It's probably not a usual combination to want to use YANG to brew beer - however a bit of tinkering has started to scratch the itch of providing a data model for homebrew.
At work I'm used to Command Line Interfaces (CLI), I don't really do Graphic User Interfaces (GUI)'s and hate mice and trackpads with a passion.
So when the raspberry pi controlling the physical push buttons and switches failed a chasm formed.
Physical buttons (push, press, rotary) OK, Physical representations of rodents NOT OK
So this has me massively excited...
module test {
namespace "http://test.com";
prefix test;
container test {
leaf hello {
type string;
default world;
}
leaf thinking {
type string;
config false;
}
leaf service {
type string;
}
}
}
admin@ncs> request packages reload
>>> System upgrade is starting.
>>> Sessions in configure mode must exit to operational mode.
>>> No configuration changes can be performed until upgrade has completed.
>>> System upgrade has completed successfully.
reload-result {
package galaxy
result true
}
reload-result {
package pioneer
result true
}
admin@ncs> request devices device galaxy sync-from
result true
[ok][2018-09-13 00:28:39]
admin@ncs> show configuration devices device galaxy config
test:test {
hello "BOO!!!RADLEY";
service abc;
}
<<<<in 13-Sep-2018::00:25:29.653 device=galaxy session-id=4
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"><data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><test xmlns="http://test.com"><hello>BOO!!!RADLEY</hello><service>abc</service></test></data></rpc-reply>
Many folk won't see why this is interesting - but for me this is a place to learn new skills whilst brewing some beer!
At work I'm used to Command Line Interfaces (CLI), I don't really do Graphic User Interfaces (GUI)'s and hate mice and trackpads with a passion.
So when the raspberry pi controlling the physical push buttons and switches failed a chasm formed.
Physical buttons (push, press, rotary) OK, Physical representations of rodents NOT OK
So this has me massively excited...
module test {
namespace "http://test.com";
prefix test;
container test {
leaf hello {
type string;
default world;
}
leaf thinking {
type string;
config false;
}
leaf service {
type string;
}
}
}
admin@ncs> request packages reload
>>> System upgrade is starting.
>>> Sessions in configure mode must exit to operational mode.
>>> No configuration changes can be performed until upgrade has completed.
>>> System upgrade has completed successfully.
reload-result {
package galaxy
result true
}
reload-result {
package pioneer
result true
}
admin@ncs> request devices device galaxy sync-from
result true
[ok][2018-09-13 00:28:39]
admin@ncs> show configuration devices device galaxy config
test:test {
hello "BOO!!!RADLEY";
service abc;
}
<<<<in 13-Sep-2018::00:25:29.653 device=galaxy session-id=4
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"><data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><test xmlns="http://test.com"><hello>BOO!!!RADLEY</hello><service>abc</service></test></data></rpc-reply>
Many folk won't see why this is interesting - but for me this is a place to learn new skills whilst brewing some beer!
Comments
Post a Comment