feuerlabs / exodm Goto Github PK

It may be appropriate to state what the build tools and environment are for exodm in the wiki? For instance, I started off with OTP 17.4 on Lubuntu 14.04. I nearly just tried it natively on my Mac, but was highly suspicious of that.

It seems that the "regular" build system would be OTP R15B02 on some version of CentOS? At least for 1.3?

ERL: OTP 17.4
Exodm: master

On line 800 of the deps/yang/yang_validate.erl file there is what looks like an extra comma. Look after "none":

rule('type') ->
    {'type',identifier_ref,
     ?ALL(0,none‚,[
           ?Y(0,1,'fraction-digits'), %% decimal64
           ?Y(0,1,'range'),   %% numerical
           ?Y(0,1,'length'),
           ?Y(0,n,'pattern'),  %% string
           ?Y(0,n,'enum'),   %% enum
           ?Y(0,1,'path'),   %% leafref FIXED: RFC6020 - Errata ID 2949
           ?Y(0,1,'base'),   %% identityref
           ?Y(0,1,'require-instance'),  %% instance-identifier
           ?Y(0,n,'bit'),               %% bits
           ?Y(0,n,'type')               %% union
          ])};

When trying to set up the Exosense server and add the ckp.yang file, I found that the create-yang-module.sh file would not work. I'm not sure entirely the reason, but changing the "==" equalities to "=" in the bash if statements did the trick. i.e.

if [ $# = 1 ]
then
    REPO=user
    YANG_FILE=$1
elif [ $# = 2 ]
then
    REPO=$1
    YANG_FILE=$2
else
    echo "Usage: $0 [user|system] yang-file"
    exit 255
fi

ERL: OTP 17.4
eoxdm: master

This is artifact of using 17.4, ignore if you want.

When compiling yaws, the dependency on crypto:sha/1 causes the build to fail. It is deprecated. Changed the rebar.config, removed "warnings_as_errors" and added "nowarn_deprecated_type".

{erl_opts, [%% OTP R11 - R15B -> yaws_sendfile_drv or compat_send
            {platform_define,
             "R1([1-4]|5[AB]-).*(linux|freebsd|darwin)", 'HAVE_YAWS_SENDFILE'},
            {platform_define, "R1([1-4]|5[AB]-)", 'NO_FILE_SENDFILE'},
            no_debug_info,
            {src_dirs, ["src", "examples/src"]},
           nowarn_deprecated_type]}.

I struggled to use this file a bit, I believe the $VAL argument is supposed to be optional? And yet it seemed to be required. I also wasn't sure how to use it... Am I supposed to be able to change the yang spec for the config-set with this?

ERL: OTP 17.4
Exodm: master

Feel free to ignore this, it was discovered when I was trying to build something with the latest code and OTP version.

There are several files with non utf-8 encodings. In some cases, this just generates an error. In other modules where the "warnings_as_errors" flag is set, it fails the build.

In lhttpc:

ERROR: Failed to extract name from /home/git/feuerlabs/exodm/deps/lhttpc/src/lhttpc.app.src: {27, file_io_server, invalid_unicode}

Just deleting the comment at the top of the file or forcing UTF-8 encoding fixes this.

In yaws:

==> yaws (compile)
--- Will not overwrite /home/rob/git/feuerlabs/exodm/deps/yaws/etc/yaws/yaws.conf
--- Installing local config file at /home/rob/git/feuerlabs/exodm/deps/yaws/etc/yaws/yaws.conf.template
/home/rob/git/feuerlabs/exodm/deps/yaws/src/yaws_xmlrpc.erl:1: Non-UTF-8 character(s) detected, but no encoding declared. Encode the file in UTF-8 or add "%% coding: latin-1" at the beginning of the file. Retrying with latin-1 encoding.
ERROR: compile failed while processing /home/rob/git/feuerlabs/exodm/deps/yaws: rebar_abort
make: *** [compile] Error 1

Also the following files in yaws have different encodings:

/exodm/deps/yaws/src/yaws_jsonrpc.erl
/eoxdm/deps/yaws/src/yaws_rpc.erl

ERL: OTP 17.4
Exodm: Master

Feel free to ignore, this is an artifact of OTP 17.4.

Meck did not compile because there was a warning about a deprecated library and the "warnings_as_errors" flag was set inside that package:

==> meck (compile)
/home/rob/git/feuerlabs/exodm/deps/meck/src/meck.erl:71: type dict/0 is deprecated and will be removed in OTP 18.0; use use dict:dict/0 or preferably dict:dict/2
ERROR: compile failed while processing /home/rob/git/feuerlabs/exodm/deps/meck: rebar_abort
make: *** [compile] Error 1

Can be fixed by changing the erl_opts argument and adding the "nowarn_deprecated_type"?

In exodm/deps/meck/rebar.config

{erl_opts, [warnings_as_errors, debug_info, nowarn_deprecated_type]}.

ERL: R15B02
Exodm: 1.3.rc5

The rebar.config file in exodm references master in Exometer. I believe the following needs to be changed if one want to build the 1.3 release?

, {exometer, ".*", {git, "[email protected]:Feuerlabs/exometer.git",
              {branch, "master"}}}

to

, {exometer, ".*", {git, "[email protected]:Feuerlabs/exometer.git",
              {tag,"1.1"}}}

As per a discussion with Ulf, it appears that when upgrading from one version of exodm to another it may be necessary to go through a database migration process. This is not defined anywhere....