The docker runs a copy of confd, in whose configuration file we have set the webui tag enabled at port 8008.
When we finally run confd on the docker, I get an error “Module “tailf-webui” in access rule “any-group/tailf-webui-user” does not exist - ignoring rule”.
Also, when I try to access the webui from the CENTOS browser using docker-ip:8008 I don’t get a thing.
Do you have the module tailf-webui in the load path of ConfD?
You can verify this by running the command: confd --status
An example output is: (I highlighted what you need to look for)
confd --status
vsn: 6.0
SMP support: no
Using epoll: no
available modules: backplane,netconf,cdb,cli,snmp, webui
running modules: backplane,netconf,cdb,cli
status: started
namespaces: urn:ietf:params:xml:ns:yang:iana-crypt-hash prefix:ianach exported to: all
urn:ietf:params:xml:ns:yang:ietf-inet-types prefix:inet exported to: all
urn:ietf:params:xml:ns:yang:ietf-netconf-acm prefix:nacm exported to: all
urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring prefix:ncm exported to: all
urn:ietf:params:xml:ns:yang:ietf-netconf-notifications prefix:ncn exported to: all
urn:ietf:params:xml:ns:yang:ietf-yang-types prefix:yang exported to: all http://tail-f.com/ns/example/routes/1.0 prefix:r exported to: all http://tail-f.com/ns/aaa/1.1 prefix:aaa exported to: all http://tail-f.com/yang/acm prefix:tacm exported to: all http://tail-f.com/yang/common-monitoring prefix:tfcg exported to: all http://tail-f.com/yang/confd-monitoring prefix:tfcm exported to: all http://tail-f.com/yang/netconf-monitoring prefix:tncm exported to: all
http://tail-f.com/ns/webui prefix:webui exported to: all
YANG data models:
module: iana-crypt-hash revision: 2014-04-04
namespace: urn:ietf:params:xml:ns:yang:iana-crypt-hash
prefix: ianach
exported to: all
module: ietf-inet-types revision: 2013-07-15
namespace: urn:ietf:params:xml:ns:yang:ietf-inet-types
prefix: inet
exported to: all
module: ietf-netconf-acm revision: 2012-02-22
namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-acm
prefix: nacm
exported to: all
module: ietf-netconf-monitoring revision: 2010-10-04
namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring
prefix: ncm
exported to: all
module: ietf-netconf-notifications revision: 2012-02-06
namespace: urn:ietf:params:xml:ns:yang:ietf-netconf-notifications
prefix: ncn
exported to: all
module: ietf-yang-types revision: 2013-07-15
namespace: urn:ietf:params:xml:ns:yang:ietf-yang-types
prefix: yang
exported to: all
module: routes
namespace: http://tail-f.com/ns/example/routes/1.0
prefix: r
exported to: all
module: tailf-aaa revision: 2015-06-16
namespace: http://tail-f.com/ns/aaa/1.1
prefix: aaa
exported to: all
module: tailf-acm revision: 2013-03-07
namespace: http://tail-f.com/yang/acm
prefix: tacm
exported to: all
module: tailf-common-monitoring revision: 2013-06-14
namespace: http://tail-f.com/yang/common-monitoring
prefix: tfcg
exported to: all
module: tailf-confd-monitoring revision: 2013-06-14
namespace: http://tail-f.com/yang/confd-monitoring
prefix: tfcm
exported to: all
module: tailf-netconf-monitoring revision: 2014-11-13
namespace: http://tail-f.com/yang/netconf-monitoring
prefix: tncm
exported to: all
module: tailf-webui revision: 2013-03-07
namespace: http://tail-f.com/ns/webui
prefix: webui
exported to: all
I don’t think this is a version problem, if this version hadn’t supported the webui feature, then it would never have that tag in the configuration file itself.
The configuration in the ConfD configuration file, confd.conf, in some examples do have the WebUI tag as the same example is shipped with ConfD Premium too.
But the JSON-RPC API and the auto-rendered WebUI examples are removed from the ConfD Basic version. So are SNMP, REST, CLI customization, a couple of CLI styles, CLI multi-session, and Java and Python language bindings.
In ConfD Basic, NETCONF is the focus. A limited CLI, and MAAPI are enabled too, for debugging purposes and to enable real applications to be built with NETCONF support. You have C and Erlang language bindings to choose from to interact with ConfD for your application through for example the CDB, MAAPI, and DP application interfaces.