From raszabo at cisco.com Thu Dec 1 08:15:53 2016 From: raszabo at cisco.com (Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco)) Date: Thu, 1 Dec 2016 08:15:53 +0000 Subject: [sysrepo-devel] bad version of ietf-netconf-acm In-Reply-To: References: Message-ID: <51d12ea182434b60a82a2fb66e1c3cfc@XCH-RCD-002.cisco.com> Hi, What exactly is bad in the "bad" ietf-netconf-acm.yang ? Could you please provide the diff? Thanks, Rastislav From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of Joan Landry Sent: Wednesday, November 30, 2016 5:24 PM To: sysrepo-devel at sysrepo.org Subject: [sysrepo-devel] bad version of ietf-netconf-acm I have found that there is a good version of ietf-netconf-acm.yang and a bad version of the same file. Both have the same rev dates. revision "2012-02-22" For some reason when I download the models from the device I always get the bad version of this file on my mib browser which causes schema issues. I have ensured that I installed the correct version in sysrepo via sysrepoctl install I also ensured that the bad file does not exist in /etc/sysrepo/yang Yet when I get the model from the device I get the bad file. Any ideas if this is a bug in sysrepo - or how I can fix it? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From rkrejci at cesnet.cz Thu Dec 1 09:02:16 2016 From: rkrejci at cesnet.cz (=?UTF-8?B?UmFkZWsgS3JlasSNw60=?=) Date: Thu, 1 Dec 2016 10:02:16 +0100 Subject: [sysrepo-devel] bad version of ietf-netconf-acm In-Reply-To: <51d12ea182434b60a82a2fb66e1c3cfc@XCH-RCD-002.cisco.com> References: <51d12ea182434b60a82a2fb66e1c3cfc@XCH-RCD-002.cisco.com> Message-ID: <23f25042-9124-fc6c-c1a2-d55dbf20a54c@cesnet.cz> Hi, some more info is in [1]. I believe that the only difference is in missing YANG extensions, which is a kind of "known bug" and we are working on extensions support in libyang (currently it is in a separate "extensions" branch and not yet ready for regular use). All other things should be equivalent, if not, it is a bug. [1] - https://github.com/CESNET/Netopeer2/issues/71 Regards, Radek Dne 1.12.2016 v 09:15 Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) napsal(a): > > Hi, > > > > What exactly is bad in the ?bad? ietf-netconf-acm.yang ? Could you please provide the diff? > > > > Thanks, > > Rastislav > > > > *From:* sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] *On Behalf Of *Joan Landry > *Sent:* Wednesday, November 30, 2016 5:24 PM > *To:* sysrepo-devel at sysrepo.org > *Subject:* [sysrepo-devel] bad version of ietf-netconf-acm > > > > I have found that there is a good version of ietf-netconf-acm.yang and a bad version of the same file. > > > > Both have the same rev dates. revision "2012-02-22" > > > > For some reason when I download the models from the device I always get the bad version of this file on my mib browser which causes schema issues. > > > > I have ensured that I installed the correct version in sysrepo via sysrepoctl install > > > > I also ensured that the bad file does not exist in /etc/sysrepo/yang > > > > Yet when I get the model from the device I get the bad file. > > > > Any ideas if this is a bug in sysrepo ? or how I can fix it? > > > > Thanks > > > > _______________________________________________ > sysrepo-devel mailing list > sysrepo-devel at sysrepo.org > http://lists.sysrepo.org/listinfo/sysrepo-devel -- Radek Krejci mobile : +420 732 212 714 office : +420 234 680 256 e-mail : rkrejci at cesnet.cz LinkedIn: http://www.linkedin.com/in/radekkrejci CESNET, Association of Legal Entities Zikova 4 160 00 Praha 6 Czech Republic From lmacko at cisco.com Thu Dec 1 09:28:31 2016 From: lmacko at cisco.com (Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco)) Date: Thu, 1 Dec 2016 09:28:31 +0000 Subject: [sysrepo-devel] Devel branch: state data handling adjustment Message-ID: Hi all, I just wanted to inform you about minor change in devel branch that has an impact on state data handling. The change influences data providers that provide state data located in a configuration list. Sysrepo now sends requests to data provider with the key values filled in xpath. Example: having module like this module demo { /*..*/ list abc { key cfg; leaf cfg { type string; } leaf name { type string; } leaf value { type string; config false; } } /* config data */ } sysrepo will generate requests corresponding to actual configured list instances i.e.: /demo:abc[cfg='0']/value, /demo:abc[cfg='1']/value and so on... (until now sysrepo sent only one request /demo:abc/value and the data provider was supposed to return the data for all instances of config lists) Regards, Lukas -------------- next part -------------- An HTML attachment was scrubbed... URL: From JoLandry at advaoptical.com Thu Dec 1 11:45:10 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Thu, 1 Dec 2016 11:45:10 +0000 Subject: [sysrepo-devel] bad version of ietf-netconf-acm In-Reply-To: <51d12ea182434b60a82a2fb66e1c3cfc@XCH-RCD-002.cisco.com> References: <51d12ea182434b60a82a2fb66e1c3cfc@XCH-RCD-002.cisco.com> Message-ID: <3ab71d7fc3cf4eada1c1c3cb1114f6a3@advaoptical.com> I installed the file ietf-netconf-acm at 2012-02-22.yang And when I do a get schema I get back a different modified version of it that is missing required yang file (file attached was renamed to ietf-bad-netconf-acm at 2012-02-22.yang) Doing pyang on the bad file I get back results in this error: pyang -f yang ietf-netconf-acm\@2012-02-22.yang > tmp.yang ietf-netconf-acm at 2012-02-22.yang:141: error: extension "default-deny-all" is not defined in module ietf-netconf-acm so we are not able to load the ietf-system yang module which depends on including the acm module. From: Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) [mailto:raszabo at cisco.com] Sent: Thursday, December 01, 2016 3:16 AM To: Joan Landry ; sysrepo-devel at sysrepo.org Subject: RE: bad version of ietf-netconf-acm Hi, What exactly is bad in the "bad" ietf-netconf-acm.yang ? Could you please provide the diff? Thanks, Rastislav From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of Joan Landry Sent: Wednesday, November 30, 2016 5:24 PM To: sysrepo-devel at sysrepo.org Subject: [sysrepo-devel] bad version of ietf-netconf-acm I have found that there is a good version of ietf-netconf-acm.yang and a bad version of the same file. Both have the same rev dates. revision "2012-02-22" For some reason when I download the models from the device I always get the bad version of this file on my mib browser which causes schema issues. I have ensured that I installed the correct version in sysrepo via sysrepoctl install I also ensured that the bad file does not exist in /etc/sysrepo/yang Yet when I get the model from the device I get the bad file. Any ideas if this is a bug in sysrepo - or how I can fix it? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ietf-bad-netconf-acm at 2012-02-22.yang Type: application/octet-stream Size: 11754 bytes Desc: ietf-bad-netconf-acm at 2012-02-22.yang URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ietf-netconf-acm at 2012-02-22.yang Type: application/octet-stream Size: 12711 bytes Desc: ietf-netconf-acm at 2012-02-22.yang URL: From JoLandry at advaoptical.com Thu Dec 1 12:16:08 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Thu, 1 Dec 2016 12:16:08 +0000 Subject: [sysrepo-devel] bad version of ietf-netconf-acm In-Reply-To: <23f25042-9124-fc6c-c1a2-d55dbf20a54c@cesnet.cz> References: <51d12ea182434b60a82a2fb66e1c3cfc@XCH-RCD-002.cisco.com> <23f25042-9124-fc6c-c1a2-d55dbf20a54c@cesnet.cz> Message-ID: I attached the original and the one I get back (bad one) via get-schema The problem is that in removing the extensions it renders the model broken and also the ietf-system model becomes not usable as it also depends on acm pyang -f yang ietf-netconf-acm\@2012-02-22.yang > tmp.yang ietf-netconf-acm at 2012-02-22.yang:141: error: extension "default-deny-all" is not defined in module ietf-netconf-acm do you know if there is a time frame for fixing this - if not we may need to remove the use of the ietf-system model from our system. Thanks for any info on this. -----Original Message----- From: Radek Krej?? [mailto:rkrejci at cesnet.cz] Sent: Thursday, December 01, 2016 4:02 AM To: Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) ; Joan Landry ; sysrepo-devel at sysrepo.org Subject: Re: [sysrepo-devel] bad version of ietf-netconf-acm Hi, some more info is in [1]. I believe that the only difference is in missing YANG extensions, which is a kind of "known bug" and we are working on extensions support in libyang (currently it is in a separate "extensions" branch and not yet ready for regular use). All other things should be equivalent, if not, it is a bug. [1] - https://github.com/CESNET/Netopeer2/issues/71 Regards, Radek Dne 1.12.2016 v 09:15 Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) napsal(a): > > Hi, > > > > What exactly is bad in the "bad" ietf-netconf-acm.yang ? Could you please provide the diff? > > > > Thanks, > > Rastislav > > > > *From:* sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] *On Behalf Of *Joan Landry > *Sent:* Wednesday, November 30, 2016 5:24 PM > *To:* sysrepo-devel at sysrepo.org > *Subject:* [sysrepo-devel] bad version of ietf-netconf-acm > > > > I have found that there is a good version of ietf-netconf-acm.yang and a bad version of the same file. > > > > Both have the same rev dates. revision "2012-02-22" > > > > For some reason when I download the models from the device I always get the bad version of this file on my mib browser which causes schema issues. > > > > I have ensured that I installed the correct version in sysrepo via sysrepoctl install > > > > I also ensured that the bad file does not exist in /etc/sysrepo/yang > > > > Yet when I get the model from the device I get the bad file. > > > > Any ideas if this is a bug in sysrepo - or how I can fix it? > > > > Thanks > > > > _______________________________________________ > sysrepo-devel mailing list > sysrepo-devel at sysrepo.org > http://lists.sysrepo.org/listinfo/sysrepo-devel -- Radek Krejci mobile : +420 732 212 714 office : +420 234 680 256 e-mail : rkrejci at cesnet.cz LinkedIn: http://www.linkedin.com/in/radekkrejci CESNET, Association of Legal Entities Zikova 4 160 00 Praha 6 Czech Republic -------------- next part -------------- A non-text attachment was scrubbed... Name: ietf-bad-netconf-acm at 2012-02-22.yang Type: application/octet-stream Size: 11754 bytes Desc: ietf-bad-netconf-acm at 2012-02-22.yang URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ietf-netconf-acm at 2012-02-22.yang Type: application/octet-stream Size: 12711 bytes Desc: ietf-netconf-acm at 2012-02-22.yang URL: From rkrejci at cesnet.cz Thu Dec 1 12:29:19 2016 From: rkrejci at cesnet.cz (=?UTF-8?B?UmFkZWsgS3JlasSNw60=?=) Date: Thu, 1 Dec 2016 13:29:19 +0100 Subject: [sysrepo-devel] bad version of ietf-netconf-acm In-Reply-To: References: <51d12ea182434b60a82a2fb66e1c3cfc@XCH-RCD-002.cisco.com> <23f25042-9124-fc6c-c1a2-d55dbf20a54c@cesnet.cz> Message-ID: Hi, regarding the time - working solution for YANG extensions will probably take few weeks. But I'm not clear why do you mix the schema received from NETCONF server with the one you have locally on client side. Is there a reason for this? Why don't you just get (using get-schema) also the ietf-system module from the NETCONF server. They should work together since the extension instances in ietf-system will be removed. sysrepo and Netopeer2 do not implement NACM (work in progress), so the NACM extension does not have any effect in this moment and ignoring them in ietf-system does not change meaning of anything defined in it. Regards, Radek Dne 1.12.2016 v 13:16 Joan Landry napsal(a): > I attached the original and the one I get back (bad one) via get-schema > > The problem is that in removing the extensions it renders the model broken and also the ietf-system model becomes not usable as it also depends on acm > > pyang -f yang ietf-netconf-acm\@2012-02-22.yang > tmp.yang > > ietf-netconf-acm at 2012-02-22.yang:141: error: extension "default-deny-all" is not defined in module ietf-netconf-acm > > do you know if there is a time frame for fixing this - if not we may need to remove the use of the ietf-system model from our system. > > Thanks for any info on this. > > > -----Original Message----- > From: Radek Krej?? [mailto:rkrejci at cesnet.cz] > Sent: Thursday, December 01, 2016 4:02 AM > To: Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) ; Joan Landry ; sysrepo-devel at sysrepo.org > Subject: Re: [sysrepo-devel] bad version of ietf-netconf-acm > > Hi, some more info is in [1]. I believe that the only difference is in missing YANG extensions, which is a kind of "known bug" and we are working on extensions support in libyang (currently it is in a separate "extensions" branch and not yet ready for regular use). All other things should be equivalent, if not, it is a bug. > > [1] - https://github.com/CESNET/Netopeer2/issues/71 > > Regards, > Radek > > > Dne 1.12.2016 v 09:15 Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) napsal(a): >> Hi, >> >> >> >> What exactly is bad in the "bad" ietf-netconf-acm.yang ? Could you please provide the diff? >> >> >> >> Thanks, >> >> Rastislav >> >> >> >> *From:* sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] *On Behalf Of *Joan Landry >> *Sent:* Wednesday, November 30, 2016 5:24 PM >> *To:* sysrepo-devel at sysrepo.org >> *Subject:* [sysrepo-devel] bad version of ietf-netconf-acm >> >> >> >> I have found that there is a good version of ietf-netconf-acm.yang and a bad version of the same file. >> >> >> >> Both have the same rev dates. revision "2012-02-22" >> >> >> >> For some reason when I download the models from the device I always get the bad version of this file on my mib browser which causes schema issues. >> >> >> >> I have ensured that I installed the correct version in sysrepo via sysrepoctl install >> >> >> >> I also ensured that the bad file does not exist in /etc/sysrepo/yang >> >> >> >> Yet when I get the model from the device I get the bad file. >> >> >> >> Any ideas if this is a bug in sysrepo - or how I can fix it? >> >> >> >> Thanks >> >> >> >> _______________________________________________ >> sysrepo-devel mailing list >> sysrepo-devel at sysrepo.org >> http://lists.sysrepo.org/listinfo/sysrepo-devel -- Radek Krejci mobile : +420 732 212 714 office : +420 234 680 256 e-mail : rkrejci at cesnet.cz LinkedIn: http://www.linkedin.com/in/radekkrejci CESNET, Association of Legal Entities Zikova 4 160 00 Praha 6 Czech Republic From rkrejci at cesnet.cz Thu Dec 1 12:32:59 2016 From: rkrejci at cesnet.cz (=?UTF-8?B?UmFkZWsgS3JlasSNw60=?=) Date: Thu, 1 Dec 2016 13:32:59 +0100 Subject: [sysrepo-devel] bad version of ietf-netconf-acm In-Reply-To: References: <51d12ea182434b60a82a2fb66e1c3cfc@XCH-RCD-002.cisco.com> <23f25042-9124-fc6c-c1a2-d55dbf20a54c@cesnet.cz> Message-ID: ahh, sorry, my fault - NACM extensions are kind of special and their instances are currently printed so they will appear in ietf-system. I'm going to do something with this. Radek Dne 1.12.2016 v 13:29 Radek Krej?? napsal(a): > Hi, > regarding the time - working solution for YANG extensions will probably take few weeks. > > But I'm not clear why do you mix the schema received from NETCONF server with the one you have locally on client side. Is there a reason for this? Why don't you just get (using get-schema) also the ietf-system module from the NETCONF server. They should work together since the extension instances in ietf-system will be removed. sysrepo and Netopeer2 do not implement NACM (work in progress), so the NACM extension does not have any effect in this moment and ignoring them in ietf-system does not change meaning of anything defined in it. > > Regards, > Radek > > > Dne 1.12.2016 v 13:16 Joan Landry napsal(a): >> I attached the original and the one I get back (bad one) via get-schema >> >> The problem is that in removing the extensions it renders the model broken and also the ietf-system model becomes not usable as it also depends on acm >> >> pyang -f yang ietf-netconf-acm\@2012-02-22.yang > tmp.yang >> >> ietf-netconf-acm at 2012-02-22.yang:141: error: extension "default-deny-all" is not defined in module ietf-netconf-acm >> >> do you know if there is a time frame for fixing this - if not we may need to remove the use of the ietf-system model from our system. >> >> Thanks for any info on this. >> >> >> -----Original Message----- >> From: Radek Krej?? [mailto:rkrejci at cesnet.cz] >> Sent: Thursday, December 01, 2016 4:02 AM >> To: Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) ; Joan Landry ; sysrepo-devel at sysrepo.org >> Subject: Re: [sysrepo-devel] bad version of ietf-netconf-acm >> >> Hi, some more info is in [1]. I believe that the only difference is in missing YANG extensions, which is a kind of "known bug" and we are working on extensions support in libyang (currently it is in a separate "extensions" branch and not yet ready for regular use). All other things should be equivalent, if not, it is a bug. >> >> [1] - https://github.com/CESNET/Netopeer2/issues/71 >> >> Regards, >> Radek >> >> >> Dne 1.12.2016 v 09:15 Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) napsal(a): >>> Hi, >>> >>> >>> >>> What exactly is bad in the "bad" ietf-netconf-acm.yang ? Could you please provide the diff? >>> >>> >>> >>> Thanks, >>> >>> Rastislav >>> >>> >>> >>> *From:* sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] *On Behalf Of *Joan Landry >>> *Sent:* Wednesday, November 30, 2016 5:24 PM >>> *To:* sysrepo-devel at sysrepo.org >>> *Subject:* [sysrepo-devel] bad version of ietf-netconf-acm >>> >>> >>> >>> I have found that there is a good version of ietf-netconf-acm.yang and a bad version of the same file. >>> >>> >>> >>> Both have the same rev dates. revision "2012-02-22" >>> >>> >>> >>> For some reason when I download the models from the device I always get the bad version of this file on my mib browser which causes schema issues. >>> >>> >>> >>> I have ensured that I installed the correct version in sysrepo via sysrepoctl install >>> >>> >>> >>> I also ensured that the bad file does not exist in /etc/sysrepo/yang >>> >>> >>> >>> Yet when I get the model from the device I get the bad file. >>> >>> >>> >>> Any ideas if this is a bug in sysrepo - or how I can fix it? >>> >>> >>> >>> Thanks >>> >>> >>> >>> _______________________________________________ >>> sysrepo-devel mailing list >>> sysrepo-devel at sysrepo.org >>> http://lists.sysrepo.org/listinfo/sysrepo-devel -- Radek Krejci mobile : +420 732 212 714 office : +420 234 680 256 e-mail : rkrejci at cesnet.cz LinkedIn: http://www.linkedin.com/in/radekkrejci CESNET, Association of Legal Entities Zikova 4 160 00 Praha 6 Czech Republic From rkrejci at cesnet.cz Thu Dec 1 13:06:43 2016 From: rkrejci at cesnet.cz (=?UTF-8?B?UmFkZWsgS3JlasSNw60=?=) Date: Thu, 1 Dec 2016 14:06:43 +0100 Subject: [sysrepo-devel] bad version of ietf-netconf-acm In-Reply-To: References: <51d12ea182434b60a82a2fb66e1c3cfc@XCH-RCD-002.cisco.com> <23f25042-9124-fc6c-c1a2-d55dbf20a54c@cesnet.cz> Message-ID: <75e69fd3-9ad6-d789-4dc4-5f5ac5a0b0bd@cesnet.cz> ok, so now (libyang 0.11.81) it behaves as I've described - NACM extensions definitions nor instances are printed from libyang, so ietf-netconf-acm and ietf-system received from Netopeer2 server via get-schema should work together even in pyang (it may complain about not used import, but it is only a warning). This is just a temporary hack before finishing YANG extensions support. Regards, Radek Dne 1.12.2016 v 13:32 Radek Krej?? napsal(a): > ahh, sorry, my fault - NACM extensions are kind of special and their instances are currently printed so they will appear in ietf-system. I'm going to do something with this. > > Radek > > > Dne 1.12.2016 v 13:29 Radek Krej?? napsal(a): >> Hi, >> regarding the time - working solution for YANG extensions will probably take few weeks. >> >> But I'm not clear why do you mix the schema received from NETCONF server with the one you have locally on client side. Is there a reason for this? Why don't you just get (using get-schema) also the ietf-system module from the NETCONF server. They should work together since the extension instances in ietf-system will be removed. sysrepo and Netopeer2 do not implement NACM (work in progress), so the NACM extension does not have any effect in this moment and ignoring them in ietf-system does not change meaning of anything defined in it. >> >> Regards, >> Radek >> >> >> Dne 1.12.2016 v 13:16 Joan Landry napsal(a): >>> I attached the original and the one I get back (bad one) via get-schema >>> >>> The problem is that in removing the extensions it renders the model broken and also the ietf-system model becomes not usable as it also depends on acm >>> >>> pyang -f yang ietf-netconf-acm\@2012-02-22.yang > tmp.yang >>> >>> ietf-netconf-acm at 2012-02-22.yang:141: error: extension "default-deny-all" is not defined in module ietf-netconf-acm >>> >>> do you know if there is a time frame for fixing this - if not we may need to remove the use of the ietf-system model from our system. >>> >>> Thanks for any info on this. >>> >>> >>> -----Original Message----- >>> From: Radek Krej?? [mailto:rkrejci at cesnet.cz] >>> Sent: Thursday, December 01, 2016 4:02 AM >>> To: Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) ; Joan Landry ; sysrepo-devel at sysrepo.org >>> Subject: Re: [sysrepo-devel] bad version of ietf-netconf-acm >>> >>> Hi, some more info is in [1]. I believe that the only difference is in missing YANG extensions, which is a kind of "known bug" and we are working on extensions support in libyang (currently it is in a separate "extensions" branch and not yet ready for regular use). All other things should be equivalent, if not, it is a bug. >>> >>> [1] - https://github.com/CESNET/Netopeer2/issues/71 >>> >>> Regards, >>> Radek >>> >>> >>> Dne 1.12.2016 v 09:15 Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) napsal(a): >>>> Hi, >>>> >>>> >>>> >>>> What exactly is bad in the "bad" ietf-netconf-acm.yang ? Could you please provide the diff? >>>> >>>> >>>> >>>> Thanks, >>>> >>>> Rastislav >>>> >>>> >>>> >>>> *From:* sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] *On Behalf Of *Joan Landry >>>> *Sent:* Wednesday, November 30, 2016 5:24 PM >>>> *To:* sysrepo-devel at sysrepo.org >>>> *Subject:* [sysrepo-devel] bad version of ietf-netconf-acm >>>> >>>> >>>> >>>> I have found that there is a good version of ietf-netconf-acm.yang and a bad version of the same file. >>>> >>>> >>>> >>>> Both have the same rev dates. revision "2012-02-22" >>>> >>>> >>>> >>>> For some reason when I download the models from the device I always get the bad version of this file on my mib browser which causes schema issues. >>>> >>>> >>>> >>>> I have ensured that I installed the correct version in sysrepo via sysrepoctl install >>>> >>>> >>>> >>>> I also ensured that the bad file does not exist in /etc/sysrepo/yang >>>> >>>> >>>> >>>> Yet when I get the model from the device I get the bad file. >>>> >>>> >>>> >>>> Any ideas if this is a bug in sysrepo - or how I can fix it? >>>> >>>> >>>> >>>> Thanks >>>> >>>> >>>> >>>> _______________________________________________ >>>> sysrepo-devel mailing list >>>> sysrepo-devel at sysrepo.org >>>> http://lists.sysrepo.org/listinfo/sysrepo-devel -- Radek Krejci mobile : +420 732 212 714 office : +420 234 680 256 e-mail : rkrejci at cesnet.cz LinkedIn: http://www.linkedin.com/in/radekkrejci CESNET, Association of Legal Entities Zikova 4 160 00 Praha 6 Czech Republic From JoLandry at advaoptical.com Thu Dec 1 14:09:41 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Thu, 1 Dec 2016 14:09:41 +0000 Subject: [sysrepo-devel] bad version of ietf-netconf-acm In-Reply-To: <75e69fd3-9ad6-d789-4dc4-5f5ac5a0b0bd@cesnet.cz> References: <51d12ea182434b60a82a2fb66e1c3cfc@XCH-RCD-002.cisco.com> <23f25042-9124-fc6c-c1a2-d55dbf20a54c@cesnet.cz> <75e69fd3-9ad6-d789-4dc4-5f5ac5a0b0bd@cesnet.cz> Message-ID: <216d99e440b64bd380ea677b8553bbfe@advaoptical.com> Ok - thanks so much will try this! -----Original Message----- From: Radek Krej?? [mailto:rkrejci at cesnet.cz] Sent: Thursday, December 01, 2016 8:07 AM To: Joan Landry ; Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) ; sysrepo-devel at sysrepo.org Subject: Re: [sysrepo-devel] bad version of ietf-netconf-acm ok, so now (libyang 0.11.81) it behaves as I've described - NACM extensions definitions nor instances are printed from libyang, so ietf-netconf-acm and ietf-system received from Netopeer2 server via get-schema should work together even in pyang (it may complain about not used import, but it is only a warning). This is just a temporary hack before finishing YANG extensions support. Regards, Radek Dne 1.12.2016 v 13:32 Radek Krej?? napsal(a): > ahh, sorry, my fault - NACM extensions are kind of special and their instances are currently printed so they will appear in ietf-system. I'm going to do something with this. > > Radek > > > Dne 1.12.2016 v 13:29 Radek Krej?? napsal(a): >> Hi, >> regarding the time - working solution for YANG extensions will probably take few weeks. >> >> But I'm not clear why do you mix the schema received from NETCONF server with the one you have locally on client side. Is there a reason for this? Why don't you just get (using get-schema) also the ietf-system module from the NETCONF server. They should work together since the extension instances in ietf-system will be removed. sysrepo and Netopeer2 do not implement NACM (work in progress), so the NACM extension does not have any effect in this moment and ignoring them in ietf-system does not change meaning of anything defined in it. >> >> Regards, >> Radek >> >> >> Dne 1.12.2016 v 13:16 Joan Landry napsal(a): >>> I attached the original and the one I get back (bad one) via get-schema >>> >>> The problem is that in removing the extensions it renders the model broken and also the ietf-system model becomes not usable as it also depends on acm >>> >>> pyang -f yang ietf-netconf-acm\@2012-02-22.yang > tmp.yang >>> >>> ietf-netconf-acm at 2012-02-22.yang:141: error: extension "default-deny-all" is not defined in module ietf-netconf-acm >>> >>> do you know if there is a time frame for fixing this - if not we may need to remove the use of the ietf-system model from our system. >>> >>> Thanks for any info on this. >>> >>> >>> -----Original Message----- >>> From: Radek Krej?? [mailto:rkrejci at cesnet.cz] >>> Sent: Thursday, December 01, 2016 4:02 AM >>> To: Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) ; Joan Landry ; sysrepo-devel at sysrepo.org >>> Subject: Re: [sysrepo-devel] bad version of ietf-netconf-acm >>> >>> Hi, some more info is in [1]. I believe that the only difference is in missing YANG extensions, which is a kind of "known bug" and we are working on extensions support in libyang (currently it is in a separate "extensions" branch and not yet ready for regular use). All other things should be equivalent, if not, it is a bug. >>> >>> [1] - https://github.com/CESNET/Netopeer2/issues/71 >>> >>> Regards, >>> Radek >>> >>> >>> Dne 1.12.2016 v 09:15 Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) napsal(a): >>>> Hi, >>>> >>>> >>>> >>>> What exactly is bad in the "bad" ietf-netconf-acm.yang ? Could you please provide the diff? >>>> >>>> >>>> >>>> Thanks, >>>> >>>> Rastislav >>>> >>>> >>>> >>>> *From:* sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] *On Behalf Of *Joan Landry >>>> *Sent:* Wednesday, November 30, 2016 5:24 PM >>>> *To:* sysrepo-devel at sysrepo.org >>>> *Subject:* [sysrepo-devel] bad version of ietf-netconf-acm >>>> >>>> >>>> >>>> I have found that there is a good version of ietf-netconf-acm.yang and a bad version of the same file. >>>> >>>> >>>> >>>> Both have the same rev dates. revision "2012-02-22" >>>> >>>> >>>> >>>> For some reason when I download the models from the device I always get the bad version of this file on my mib browser which causes schema issues. >>>> >>>> >>>> >>>> I have ensured that I installed the correct version in sysrepo via sysrepoctl install >>>> >>>> >>>> >>>> I also ensured that the bad file does not exist in /etc/sysrepo/yang >>>> >>>> >>>> >>>> Yet when I get the model from the device I get the bad file. >>>> >>>> >>>> >>>> Any ideas if this is a bug in sysrepo - or how I can fix it? >>>> >>>> >>>> >>>> Thanks >>>> >>>> >>>> >>>> _______________________________________________ >>>> sysrepo-devel mailing list >>>> sysrepo-devel at sysrepo.org >>>> http://lists.sysrepo.org/listinfo/sysrepo-devel -- Radek Krejci mobile : +420 732 212 714 office : +420 234 680 256 e-mail : rkrejci at cesnet.cz LinkedIn: http://www.linkedin.com/in/radekkrejci CESNET, Association of Legal Entities Zikova 4 160 00 Praha 6 Czech Republic From mislav.novakovic at sartura.hr Thu Dec 1 14:47:28 2016 From: mislav.novakovic at sartura.hr (Mislav Novakovic) Date: Thu, 1 Dec 2016 15:47:28 +0100 Subject: [sysrepo-devel] issue with make install In-Reply-To: <37fe4170919845f39477338df1548734@advaoptical.com> References: <1aab19c2c71743399ffef4fff327e26f@advaoptical.com> <4a8f57a33b1b4462b9a8845bb0c8c2f0@XCH-RCD-002.cisco.com> <37fe4170919845f39477338df1548734@advaoptical.com> Message-ID: Hi Joan, it should be fixed now in the devel branch, please can you test it. Regards, Mislav On Wed, Nov 30, 2016 at 1:30 PM, Joan Landry wrote: > I just updated to the latest master branch ? started from a fresh install > > > > -- Installing: /usr/include/sysrepo-cpp/Connection.h > > CMake Error at swig/lua51/cmake_install.cmake:36 (FILE): > > file INSTALL cannot find > "/mnt/images/netopeer2/sysrepo/build/swig/lua51/libsysrepoLua51.so". > > > > when I look in that directory there is no file libsysrepoLua51.so ? but > there are these files ? which have a different name. > > > > [root at Fl build]# cd /mnt/images/netopeer2/sysrepo/build/swig/lua51/ > > [root at Fl lua51]# ls > > CMakeFiles examples > libSysrepo_Lua.so > > cmake_install.cmake liblibsysrepoLua51.so Makefile > > CTestTestfile.cmake libsysrepoLua51LUA_wrap.cxx > > > > > > Is building libsysrepoLua51.so a separate task ? or build process? I do not > see reference to it in the INSTALL.md file? > > > > > > From: Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) > [mailto:raszabo at cisco.com] > Sent: Wednesday, November 30, 2016 2:41 AM > To: Joan Landry ; sysrepo-devel at sysrepo.org > Cc: mislav.novakovic at sartura.hr > Subject: RE: issue with make install > > > > Mislav, can you please check this? I guess that Joan is getting the error > because they don?t have Lua installed. > > > > Thanks > > > > From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of > Joan Landry > Sent: Tuesday, November 29, 2016 6:07 PM > To: sysrepo-devel at sysrepo.org > Subject: [sysrepo-devel] issue with make install > > > > I just did a git pull on sysrepo master and I am seeing a make install error > > > > Any ideas? > > > > - Installing: /usr/local/include/sysrepo-cpp/Connection.h > > CMake Error at swig/lua51/cmake_install.cmake:36 (FILE): > > file INSTALL cannot find > > "/mnt/images/netopeer2/sysrepo/build/swig/lua51/libsysrepoLua51.so". > > Call Stack (most recent call first): > > swig/cmake_install.cmake:84 (INCLUDE) > > cmake_install.cmake:148 (INCLUDE) > > > > > > make: *** [install] Error 1 > > [root at Florida build]# From vishalwc at yahoo.com Fri Dec 2 07:28:50 2016 From: vishalwc at yahoo.com (Vishal) Date: Fri, 2 Dec 2016 07:28:50 +0000 (UTC) Subject: [sysrepo-devel] issue with make install In-Reply-To: <1aab19c2c71743399ffef4fff327e26f@advaoptical.com> References: <1aab19c2c71743399ffef4fff327e26f@advaoptical.com> Message-ID: <1280295977.5048196.1480663730939@mail.yahoo.com> this issue is on? master branch and we need acm fix from master branch , can we have this fix on master branch . meanwhile tried and build happen set_target_properties(${SWIG_MODULE_${LUA_SWIG_BINDING}_REAL_NAME} PROPERTIES PREFIX "") but sudo make install failed -- Up-to-date: /usr/local/include/sysrepo-cpp/Xpath.h CMake Error at swig/lua51/cmake_install.cmake:36 (FILE): ? file INSTALL cannot find ? "/home/vishalc/Netconf_v1/sysrepo/build/swig/lua51/libsysrepoLua51.so". Call Stack (most recent call first): ? swig/cmake_install.cmake:46 (INCLUDE) ? cmake_install.cmake:148 (INCLUDE) On Tuesday, 29 November 2016 10:36 PM, Joan Landry wrote: I just did a git pull on sysrepo master and I am seeing a make install error ? Any ideas? ? - Installing: /usr/local/include/sysrepo-cpp/Connection.h CMake Error at swig/lua51/cmake_install.cmake:36 (FILE): ? file INSTALL cannot find ? "/mnt/images/netopeer2/sysrepo/build/swig/lua51/libsysrepoLua51.so". Call Stack (most recent call first): ? swig/cmake_install.cmake:84 (INCLUDE) ? cmake_install.cmake:148 (INCLUDE) ? ? make: *** [install] Error 1 [root at Florida build]# _______________________________________________ sysrepo-devel mailing list sysrepo-devel at sysrepo.org http://lists.sysrepo.org/listinfo/sysrepo-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From vishalwc at yahoo.com Fri Dec 2 07:46:41 2016 From: vishalwc at yahoo.com (Vishal) Date: Fri, 2 Dec 2016 07:46:41 +0000 (UTC) Subject: [sysrepo-devel] issue with make install In-Reply-To: <1280295977.5048196.1480663730939@mail.yahoo.com> References: <1aab19c2c71743399ffef4fff327e26f@advaoptical.com> <1280295977.5048196.1480663730939@mail.yahoo.com> Message-ID: <795633387.5081006.1480664801067@mail.yahoo.com> modified the cmake_install.cmake as below FILE(INSTALL DESTINATION "${CMAKE_INSTALL_PREFIX}/lib64/lua/5.1" TYPE FILE FILES "/home/vishalc/Netconf_v1/sysrepo/build/swig/lua51/liblibsysrepoLua51.so") install also worked but I think the modification should come from CMakelist.txt On Friday, 2 December 2016 12:58 PM, Vishal wrote: this issue is on? master branch and we need acm fix from master branch , can we have this fix on master branch . meanwhile tried and build happen set_target_properties(${SWIG_MODULE_${LUA_SWIG_BINDING}_REAL_NAME} PROPERTIES PREFIX "") but sudo make install failed -- Up-to-date: /usr/local/include/sysrepo-cpp/Xpath.h CMake Error at swig/lua51/cmake_install.cmake:36 (FILE): ? file INSTALL cannot find ? "/home/vishalc/Netconf_v1/sysrepo/build/swig/lua51/libsysrepoLua51.so". Call Stack (most recent call first): ? swig/cmake_install.cmake:46 (INCLUDE) ? cmake_install.cmake:148 (INCLUDE) On Tuesday, 29 November 2016 10:36 PM, Joan Landry wrote: #yiv6568210534 #yiv6568210534 -- filtered {panose-1:2 4 5 3 5 4 6 3 2 4;}#yiv6568210534 filtered {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv6568210534 p.yiv6568210534MsoNormal, #yiv6568210534 li.yiv6568210534MsoNormal, #yiv6568210534 div.yiv6568210534MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;}#yiv6568210534 a:link, #yiv6568210534 span.yiv6568210534MsoHyperlink {color:#0563C1;text-decoration:underline;}#yiv6568210534 a:visited, #yiv6568210534 span.yiv6568210534MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv6568210534 span.yiv6568210534EmailStyle17 {color:windowtext;}#yiv6568210534 .yiv6568210534MsoChpDefault {}#yiv6568210534 filtered {margin:1.0in 1.0in 1.0in 1.0in;}#yiv6568210534 div.yiv6568210534WordSection1 {}#yiv6568210534 I just did a git pull on sysrepo master and I am seeing a make install error ? Any ideas? ? - Installing: /usr/local/include/sysrepo-cpp/Connection.h CMake Error at swig/lua51/cmake_install.cmake:36 (FILE): ? file INSTALL cannot find ? "/mnt/images/netopeer2/sysrepo/build/swig/lua51/libsysrepoLua51.so". Call Stack (most recent call first): ? swig/cmake_install.cmake:84 (INCLUDE) ? cmake_install.cmake:148 (INCLUDE) ? ? make: *** [install] Error 1 [root at Florida build]# _______________________________________________ sysrepo-devel mailing list sysrepo-devel at sysrepo.org http://lists.sysrepo.org/listinfo/sysrepo-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: From JoLandry at advaoptical.com Fri Dec 2 16:41:57 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Fri, 2 Dec 2016 16:41:57 +0000 Subject: [sysrepo-devel] Msgsoft issue with rpc interface type Message-ID: <4d519f36820c45a6ae451a4ab9f57590@advaoptical.com> Has anyone encountered the issue with MgSoft editor where the rpc reply for an interface is considered an error for the type field This is the rpc-reply for an interface from sysrepo eth0 true Ethernet 0 ethernetCsmacd According to MgSoft it should be ianaift: ethernetCsmacd Any ideas if this is a bug in sysrepo or a bug in MgSoft? -------------- next part -------------- An HTML attachment was scrubbed... URL: From JoLandry at advaoptical.com Sun Dec 4 02:14:52 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Sun, 4 Dec 2016 02:14:52 +0000 Subject: [sysrepo-devel] get-schema issue with latest master branch Message-ID: <53e927b728c64e4499571c50cfe4fa2a@advaoptical.com> The latest master branch I am seeing an issue with get-schema - any ideas? The sysrepo eror below looks like it has something to do with registering for '/ietf-netconf-monitoring:get-schema'). Any info on how to fix this would be greatly appreciated. [ERR] (rp_rpc_req_process:1877) No subscription found for RPC delivery (xpath = '/ietf-netconf-monitoring:get-schema'). yangcli root at 10.64.204.119> get-schema Enter string value for leaf yangcli root at 10.64.204.119:get-schema> ietf-system RPC Error Reply 37 for session 1: protocol operation-not-supported error Request could not be completed because the requested operation is not supported by this implementation. Netopeer2 [2016/12/03 21:08:25.144349, 3] ssh_packet_socket_callback: packet: read type 94 [len=284,padding=15,comp=268,payload=268] [2016/12/03 21:08:25.144403, 3] ssh_packet_process: Dispatching handler for packet type 94 [2016/12/03 21:08:25.144431, 3] channel_rcv_data: Channel receiving 259 bytes data in 0 (local win=1265419 remote win=39563241) [2016/12/03 21:08:25.144455, 3] channel_default_bufferize: placing 259 bytes into channel buffer (stderr=0) [2016/12/03 21:08:25.144479, 3] channel_rcv_data: Channel windows are now (local win=1265160 remote win=39563241) [2016/12/03 21:08:25.144510, 3] ssh_channel_read_timeout: Read (1) buffered : 259 bytes. Window: 1265160 [2016/12/03 21:08:25.144536, 3] ssh_channel_read_timeout: Read (1) buffered : 258 bytes. Window: 1265160 [2016/12/03 21:08:25.144561, 3] ssh_channel_read_timeout: Read (1) buffered : 257 bytes. Window: 1265160 [2016/12/03 21:08:25.144585, 3] ssh_channel_read_timeout: Read (1) buffered : 256 bytes. Window: 1265160 [2016/12/03 21:08:25.144609, 3] ssh_channel_read_timeout: Read (1) buffered : 255 bytes. Window: 1265160 [2016/12/03 21:08:25.144633, 3] ssh_channel_read_timeout: Read (1) buffered : 254 bytes. Window: 1265160 [2016/12/03 21:08:25.144659, 3] ssh_channel_read_timeout: Read (249) buffered : 253 bytes. Window: 1265160 [2016/12/03 21:08:25.144700, 3] ssh_channel_read_timeout: Read (1) buffered : 4 bytes. Window: 1265160 [2016/12/03 21:08:25.144725, 3] ssh_channel_read_timeout: Read (1) buffered : 3 bytes. Window: 1265160 [2016/12/03 21:08:25.144750, 3] ssh_channel_read_timeout: Read (1) buffered : 2 bytes. Window: 1265160 [2016/12/03 21:08:25.144774, 3] ssh_channel_read_timeout: Read (1) buffered : 1 bytes. Window: 1265160 netopeer2-server[1582]: Session 1: received message: ietf-system netopeer2-server[1582]: DICT: inserting "rpc" with collision netopeer2-server[1582]: DICT: inserting "message-id" with collision netopeer2-server[1582]: DICT: inserting "37" with collision netopeer2-server[1582]: DICT: inserting (refcount) "urn:ietf:params:xml:ns:netconf:base:1.0" netopeer2-server[1582]: DICT: inserting (refcount) "get-schema" netopeer2-server[1582]: DICT: inserting (refcount) "urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring" netopeer2-server[1582]: DICT: inserting (refcount) "identifier" netopeer2-server[1582]: DICT: inserting (refcount) "ietf-system" netopeer2-server[1582]: DICT: inserting (refcount) "" netopeer2-server[1582]: DICT: inserting (refcount) "" netopeer2-server[1582]: Resolving unresolved data nodes and their constraints... netopeer2-server[1582]: All data nodes and constraints resolved. netopeer2-server[1582]: XPATH: expression "//*": netopeer2-server[1582]: XPATH: Token Operator(Path), in expression "//" netopeer2-server[1582]: XPATH: Token NameTest, in expression "*" netopeer2-server[1582]: XPATH: eval_absolute_location_path parsed Operator(Path)[0] netopeer2-server[1582]: DICT: inserting (refcount) "*" netopeer2-server[1582]: XPATH: eval_node_test parsed NameTest[2] netopeer2-server[1582]: (cl_request_process:420) Sending rpc request. netopeer2-server[1582]: (cl_request_process:442) rpc request sent, waiting for response. netopeer2-server[1582]: (cl_request_process:464) rpc response received, processing. netopeer2-server[1582]: (cl_rpc_send:2942) Error by processing of the request. netopeer2-server[1582]: DICT: inserting "Request could not be completed because the requested operation is not supported by this implementation." with collision netopeer2-server[1582]: DICT: inserting "en" with collision netopeer2-server[1582]: Session 1: sending message: #375 [2016/12/03 21:08:25.149104, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket [2016/12/03 21:08:25.149158, 3] packet_send2: packet: wrote [len=28,padding=12,comp=15,payload=15] [2016/12/03 21:08:25.149183, 3] channel_write_common: channel_write wrote 6 bytes netopeer2-server[1582]: Session 1: sending message: protocoloperation-not-supportederrorRequest could not be completed because the requested operation is not supported by this implementation. [2016/12/03 21:08:25.149284, 3] packet_send2: packet: wrote [len=396,padding=11,comp=384,payload=384] [2016/12/03 21:08:25.149310, 3] channel_write_common: channel_write wrote 375 bytes [2016/12/03 21:08:25.149342, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket netopeer2-server[1582]: Session 1: sending message: ## [2016/12/03 21:08:25.149409, 3] packet_send2: packet: wrote [len=28,padding=14,comp=13,payload=13] [2016/12/03 21:08:25.149434, 3] channel_write_common: channel_write wrote 4 bytes [2016/12/03 21:08:25.149463, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket Sysrepo [DBG] (cm_conn_read_cb:1060) fd 6 readable [DBG] (cm_conn_read_cb:1073) 130 bytes of data received on fd 6 [DBG] (cm_conn_read_cb:1083) fd 6 would block [DBG] (cm_conn_in_buff_process:1013) New message of size 126 bytes received. [DBG] (sr_cbuff_enqueue:461) Circular buffer enqueue to position=0, current count=1. [DBG] (rp_msg_process:3146) Threads: active=0/4, 1 requests in queue [DBG] (rp_worker_thread_execute:2874) Thread id=140737316480768 signaled. [DBG] (sr_cbuff_dequeue:477) Circular buffer dequeue, new buffer head=1, count=0. [DBG] (rp_rpc_req_process:1759) Processing RPC request. [DBG] (dm_get_data_info:1744) Module ietf-netconf-monitoring already loaded [DBG] (sr_locking_set_lock_fd:734) File /etc/sysrepo/data/ietf-netconf-monitoring.persist has been locked [DBG] (pm_load_data_tree:174) Persist data successfully loaded from file '/etc/sysrepo/data/ietf-netconf-monitoring.persist'. [DBG] (sr_locking_set_unlock_close_fd:803) File /etc/sysrepo/data/ietf-netconf-monitoring.persist (fd = 12) has been unlocked [DBG] (pm_get_subscriptions:817) Returning 0 subscriptions found in 'ietf-netconf-monitoring' persist file. [ERR] (rp_rpc_req_process:1877) No subscription found for RPC delivery (xpath = '/ietf-netconf-monitoring:get-schema'). [DBG] (sr_cbuff_enqueue:461) Circular buffer enqueue to position=0, current count=1. [DBG] (rp_worker_thread_execute:2862) Thread id=140737316480768 will wait. [DBG] (cm_msg_enqueue_cb:1668) New message enqueued into CM message queue. [DBG] (sr_cbuff_dequeue:477) Circular buffer dequeue, new buffer head=1, count=0. [DBG] (cm_conn_out_buff_flush:505) Sending 67 bytes of data. [DBG] (cm_conn_out_buff_flush:511) 67 bytes of data sent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From JoLandry at advaoptical.com Sun Dec 4 04:44:07 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Sun, 4 Dec 2016 04:44:07 +0000 Subject: [sysrepo-devel] get-schema issue with latest master branch In-Reply-To: <53e927b728c64e4499571c50cfe4fa2a@advaoptical.com> References: <53e927b728c64e4499571c50cfe4fa2a@advaoptical.com> Message-ID: <0d0f155fe4d744e9a65dd8d7d487d390@advaoptical.com> Also when I add code to register rc = sr_rpc_subscribe(session, "/ietf-netconf-monitoring:get-schema", test_rpc_cb, &sync, SR_SUBSCR_DEFAULT, &subscription); if (SR_ERR_OK != rc) { goto cleanup; } I get Warning: 'rpc-reply' has no child node 'get-schema'. Using anyxml RPC Data Reply 42 for session 1: Before moving to the latest update on the master branch the get-schema use to work t some extent. Is this a change that occurred, a possible bug?? Any info on this would be great. Thanks From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of Joan Landry Sent: Saturday, December 03, 2016 9:15 PM To: sysrepo-devel at sysrepo.org Subject: [sysrepo-devel] get-schema issue with latest master branch The latest master branch I am seeing an issue with get-schema - any ideas? The sysrepo eror below looks like it has something to do with registering for '/ietf-netconf-monitoring:get-schema'). Any info on how to fix this would be greatly appreciated. [ERR] (rp_rpc_req_process:1877) No subscription found for RPC delivery (xpath = '/ietf-netconf-monitoring:get-schema'). yangcli root at 10.64.204.119> get-schema Enter string value for leaf yangcli root at 10.64.204.119:get-schema> ietf-system RPC Error Reply 37 for session 1: protocol operation-not-supported error Request could not be completed because the requested operation is not supported by this implementation. Netopeer2 [2016/12/03 21:08:25.144349, 3] ssh_packet_socket_callback: packet: read type 94 [len=284,padding=15,comp=268,payload=268] [2016/12/03 21:08:25.144403, 3] ssh_packet_process: Dispatching handler for packet type 94 [2016/12/03 21:08:25.144431, 3] channel_rcv_data: Channel receiving 259 bytes data in 0 (local win=1265419 remote win=39563241) [2016/12/03 21:08:25.144455, 3] channel_default_bufferize: placing 259 bytes into channel buffer (stderr=0) [2016/12/03 21:08:25.144479, 3] channel_rcv_data: Channel windows are now (local win=1265160 remote win=39563241) [2016/12/03 21:08:25.144510, 3] ssh_channel_read_timeout: Read (1) buffered : 259 bytes. Window: 1265160 [2016/12/03 21:08:25.144536, 3] ssh_channel_read_timeout: Read (1) buffered : 258 bytes. Window: 1265160 [2016/12/03 21:08:25.144561, 3] ssh_channel_read_timeout: Read (1) buffered : 257 bytes. Window: 1265160 [2016/12/03 21:08:25.144585, 3] ssh_channel_read_timeout: Read (1) buffered : 256 bytes. Window: 1265160 [2016/12/03 21:08:25.144609, 3] ssh_channel_read_timeout: Read (1) buffered : 255 bytes. Window: 1265160 [2016/12/03 21:08:25.144633, 3] ssh_channel_read_timeout: Read (1) buffered : 254 bytes. Window: 1265160 [2016/12/03 21:08:25.144659, 3] ssh_channel_read_timeout: Read (249) buffered : 253 bytes. Window: 1265160 [2016/12/03 21:08:25.144700, 3] ssh_channel_read_timeout: Read (1) buffered : 4 bytes. Window: 1265160 [2016/12/03 21:08:25.144725, 3] ssh_channel_read_timeout: Read (1) buffered : 3 bytes. Window: 1265160 [2016/12/03 21:08:25.144750, 3] ssh_channel_read_timeout: Read (1) buffered : 2 bytes. Window: 1265160 [2016/12/03 21:08:25.144774, 3] ssh_channel_read_timeout: Read (1) buffered : 1 bytes. Window: 1265160 netopeer2-server[1582]: Session 1: received message: ietf-system netopeer2-server[1582]: DICT: inserting "rpc" with collision netopeer2-server[1582]: DICT: inserting "message-id" with collision netopeer2-server[1582]: DICT: inserting "37" with collision netopeer2-server[1582]: DICT: inserting (refcount) "urn:ietf:params:xml:ns:netconf:base:1.0" netopeer2-server[1582]: DICT: inserting (refcount) "get-schema" netopeer2-server[1582]: DICT: inserting (refcount) "urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring" netopeer2-server[1582]: DICT: inserting (refcount) "identifier" netopeer2-server[1582]: DICT: inserting (refcount) "ietf-system" netopeer2-server[1582]: DICT: inserting (refcount) "" netopeer2-server[1582]: DICT: inserting (refcount) "" netopeer2-server[1582]: Resolving unresolved data nodes and their constraints... netopeer2-server[1582]: All data nodes and constraints resolved. netopeer2-server[1582]: XPATH: expression "//*": netopeer2-server[1582]: XPATH: Token Operator(Path), in expression "//" netopeer2-server[1582]: XPATH: Token NameTest, in expression "*" netopeer2-server[1582]: XPATH: eval_absolute_location_path parsed Operator(Path)[0] netopeer2-server[1582]: DICT: inserting (refcount) "*" netopeer2-server[1582]: XPATH: eval_node_test parsed NameTest[2] netopeer2-server[1582]: (cl_request_process:420) Sending rpc request. netopeer2-server[1582]: (cl_request_process:442) rpc request sent, waiting for response. netopeer2-server[1582]: (cl_request_process:464) rpc response received, processing. netopeer2-server[1582]: (cl_rpc_send:2942) Error by processing of the request. netopeer2-server[1582]: DICT: inserting "Request could not be completed because the requested operation is not supported by this implementation." with collision netopeer2-server[1582]: DICT: inserting "en" with collision netopeer2-server[1582]: Session 1: sending message: #375 [2016/12/03 21:08:25.149104, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket [2016/12/03 21:08:25.149158, 3] packet_send2: packet: wrote [len=28,padding=12,comp=15,payload=15] [2016/12/03 21:08:25.149183, 3] channel_write_common: channel_write wrote 6 bytes netopeer2-server[1582]: Session 1: sending message: protocoloperation-not-supportederrorRequest could not be completed because the requested operation is not supported by this implementation. [2016/12/03 21:08:25.149284, 3] packet_send2: packet: wrote [len=396,padding=11,comp=384,payload=384] [2016/12/03 21:08:25.149310, 3] channel_write_common: channel_write wrote 375 bytes [2016/12/03 21:08:25.149342, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket netopeer2-server[1582]: Session 1: sending message: ## [2016/12/03 21:08:25.149409, 3] packet_send2: packet: wrote [len=28,padding=14,comp=13,payload=13] [2016/12/03 21:08:25.149434, 3] channel_write_common: channel_write wrote 4 bytes [2016/12/03 21:08:25.149463, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket Sysrepo [DBG] (cm_conn_read_cb:1060) fd 6 readable [DBG] (cm_conn_read_cb:1073) 130 bytes of data received on fd 6 [DBG] (cm_conn_read_cb:1083) fd 6 would block [DBG] (cm_conn_in_buff_process:1013) New message of size 126 bytes received. [DBG] (sr_cbuff_enqueue:461) Circular buffer enqueue to position=0, current count=1. [DBG] (rp_msg_process:3146) Threads: active=0/4, 1 requests in queue [DBG] (rp_worker_thread_execute:2874) Thread id=140737316480768 signaled. [DBG] (sr_cbuff_dequeue:477) Circular buffer dequeue, new buffer head=1, count=0. [DBG] (rp_rpc_req_process:1759) Processing RPC request. [DBG] (dm_get_data_info:1744) Module ietf-netconf-monitoring already loaded [DBG] (sr_locking_set_lock_fd:734) File /etc/sysrepo/data/ietf-netconf-monitoring.persist has been locked [DBG] (pm_load_data_tree:174) Persist data successfully loaded from file '/etc/sysrepo/data/ietf-netconf-monitoring.persist'. [DBG] (sr_locking_set_unlock_close_fd:803) File /etc/sysrepo/data/ietf-netconf-monitoring.persist (fd = 12) has been unlocked [DBG] (pm_get_subscriptions:817) Returning 0 subscriptions found in 'ietf-netconf-monitoring' persist file. [ERR] (rp_rpc_req_process:1877) No subscription found for RPC delivery (xpath = '/ietf-netconf-monitoring:get-schema'). [DBG] (sr_cbuff_enqueue:461) Circular buffer enqueue to position=0, current count=1. [DBG] (rp_worker_thread_execute:2862) Thread id=140737316480768 will wait. [DBG] (cm_msg_enqueue_cb:1668) New message enqueued into CM message queue. [DBG] (sr_cbuff_dequeue:477) Circular buffer dequeue, new buffer head=1, count=0. [DBG] (cm_conn_out_buff_flush:505) Sending 67 bytes of data. [DBG] (cm_conn_out_buff_flush:511) 67 bytes of data sent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From raszabo at cisco.com Mon Dec 5 08:13:09 2016 From: raszabo at cisco.com (Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco)) Date: Mon, 5 Dec 2016 08:13:09 +0000 Subject: [sysrepo-devel] get-schema issue with latest master branch In-Reply-To: <0d0f155fe4d744e9a65dd8d7d487d390@advaoptical.com> References: <53e927b728c64e4499571c50cfe4fa2a@advaoptical.com> <0d0f155fe4d744e9a65dd8d7d487d390@advaoptical.com> Message-ID: Hi, It seems to be an issue in Netopeer2, similar to this one I have already reported: https://github.com/CESNET/Netopeer2/issues/73 Get-schema RPC should be handled by Netopeer2 and not forwarded to Sysrepo. Thanks, Rastislav From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of Joan Landry Sent: Sunday, December 4, 2016 5:44 AM To: Joan Landry ; sysrepo-devel at sysrepo.org Subject: Re: [sysrepo-devel] get-schema issue with latest master branch Also when I add code to register rc = sr_rpc_subscribe(session, "/ietf-netconf-monitoring:get-schema", test_rpc_cb, &sync, SR_SUBSCR_DEFAULT, &subscription); if (SR_ERR_OK != rc) { goto cleanup; } I get Warning: 'rpc-reply' has no child node 'get-schema'. Using anyxml RPC Data Reply 42 for session 1: Before moving to the latest update on the master branch the get-schema use to work t some extent. Is this a change that occurred, a possible bug?? Any info on this would be great. Thanks From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of Joan Landry Sent: Saturday, December 03, 2016 9:15 PM To: sysrepo-devel at sysrepo.org Subject: [sysrepo-devel] get-schema issue with latest master branch The latest master branch I am seeing an issue with get-schema - any ideas? The sysrepo eror below looks like it has something to do with registering for '/ietf-netconf-monitoring:get-schema'). Any info on how to fix this would be greatly appreciated. [ERR] (rp_rpc_req_process:1877) No subscription found for RPC delivery (xpath = '/ietf-netconf-monitoring:get-schema'). yangcli root at 10.64.204.119> get-schema Enter string value for leaf yangcli root at 10.64.204.119:get-schema> ietf-system RPC Error Reply 37 for session 1: protocol operation-not-supported error Request could not be completed because the requested operation is not supported by this implementation. Netopeer2 [2016/12/03 21:08:25.144349, 3] ssh_packet_socket_callback: packet: read type 94 [len=284,padding=15,comp=268,payload=268] [2016/12/03 21:08:25.144403, 3] ssh_packet_process: Dispatching handler for packet type 94 [2016/12/03 21:08:25.144431, 3] channel_rcv_data: Channel receiving 259 bytes data in 0 (local win=1265419 remote win=39563241) [2016/12/03 21:08:25.144455, 3] channel_default_bufferize: placing 259 bytes into channel buffer (stderr=0) [2016/12/03 21:08:25.144479, 3] channel_rcv_data: Channel windows are now (local win=1265160 remote win=39563241) [2016/12/03 21:08:25.144510, 3] ssh_channel_read_timeout: Read (1) buffered : 259 bytes. Window: 1265160 [2016/12/03 21:08:25.144536, 3] ssh_channel_read_timeout: Read (1) buffered : 258 bytes. Window: 1265160 [2016/12/03 21:08:25.144561, 3] ssh_channel_read_timeout: Read (1) buffered : 257 bytes. Window: 1265160 [2016/12/03 21:08:25.144585, 3] ssh_channel_read_timeout: Read (1) buffered : 256 bytes. Window: 1265160 [2016/12/03 21:08:25.144609, 3] ssh_channel_read_timeout: Read (1) buffered : 255 bytes. Window: 1265160 [2016/12/03 21:08:25.144633, 3] ssh_channel_read_timeout: Read (1) buffered : 254 bytes. Window: 1265160 [2016/12/03 21:08:25.144659, 3] ssh_channel_read_timeout: Read (249) buffered : 253 bytes. Window: 1265160 [2016/12/03 21:08:25.144700, 3] ssh_channel_read_timeout: Read (1) buffered : 4 bytes. Window: 1265160 [2016/12/03 21:08:25.144725, 3] ssh_channel_read_timeout: Read (1) buffered : 3 bytes. Window: 1265160 [2016/12/03 21:08:25.144750, 3] ssh_channel_read_timeout: Read (1) buffered : 2 bytes. Window: 1265160 [2016/12/03 21:08:25.144774, 3] ssh_channel_read_timeout: Read (1) buffered : 1 bytes. Window: 1265160 netopeer2-server[1582]: Session 1: received message: ietf-system netopeer2-server[1582]: DICT: inserting "rpc" with collision netopeer2-server[1582]: DICT: inserting "message-id" with collision netopeer2-server[1582]: DICT: inserting "37" with collision netopeer2-server[1582]: DICT: inserting (refcount) "urn:ietf:params:xml:ns:netconf:base:1.0" netopeer2-server[1582]: DICT: inserting (refcount) "get-schema" netopeer2-server[1582]: DICT: inserting (refcount) "urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring" netopeer2-server[1582]: DICT: inserting (refcount) "identifier" netopeer2-server[1582]: DICT: inserting (refcount) "ietf-system" netopeer2-server[1582]: DICT: inserting (refcount) "" netopeer2-server[1582]: DICT: inserting (refcount) "" netopeer2-server[1582]: Resolving unresolved data nodes and their constraints... netopeer2-server[1582]: All data nodes and constraints resolved. netopeer2-server[1582]: XPATH: expression "//*": netopeer2-server[1582]: XPATH: Token Operator(Path), in expression "//" netopeer2-server[1582]: XPATH: Token NameTest, in expression "*" netopeer2-server[1582]: XPATH: eval_absolute_location_path parsed Operator(Path)[0] netopeer2-server[1582]: DICT: inserting (refcount) "*" netopeer2-server[1582]: XPATH: eval_node_test parsed NameTest[2] netopeer2-server[1582]: (cl_request_process:420) Sending rpc request. netopeer2-server[1582]: (cl_request_process:442) rpc request sent, waiting for response. netopeer2-server[1582]: (cl_request_process:464) rpc response received, processing. netopeer2-server[1582]: (cl_rpc_send:2942) Error by processing of the request. netopeer2-server[1582]: DICT: inserting "Request could not be completed because the requested operation is not supported by this implementation." with collision netopeer2-server[1582]: DICT: inserting "en" with collision netopeer2-server[1582]: Session 1: sending message: #375 [2016/12/03 21:08:25.149104, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket [2016/12/03 21:08:25.149158, 3] packet_send2: packet: wrote [len=28,padding=12,comp=15,payload=15] [2016/12/03 21:08:25.149183, 3] channel_write_common: channel_write wrote 6 bytes netopeer2-server[1582]: Session 1: sending message: protocoloperation-not-supportederrorRequest could not be completed because the requested operation is not supported by this implementation. [2016/12/03 21:08:25.149284, 3] packet_send2: packet: wrote [len=396,padding=11,comp=384,payload=384] [2016/12/03 21:08:25.149310, 3] channel_write_common: channel_write wrote 375 bytes [2016/12/03 21:08:25.149342, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket netopeer2-server[1582]: Session 1: sending message: ## [2016/12/03 21:08:25.149409, 3] packet_send2: packet: wrote [len=28,padding=14,comp=13,payload=13] [2016/12/03 21:08:25.149434, 3] channel_write_common: channel_write wrote 4 bytes [2016/12/03 21:08:25.149463, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket Sysrepo [DBG] (cm_conn_read_cb:1060) fd 6 readable [DBG] (cm_conn_read_cb:1073) 130 bytes of data received on fd 6 [DBG] (cm_conn_read_cb:1083) fd 6 would block [DBG] (cm_conn_in_buff_process:1013) New message of size 126 bytes received. [DBG] (sr_cbuff_enqueue:461) Circular buffer enqueue to position=0, current count=1. [DBG] (rp_msg_process:3146) Threads: active=0/4, 1 requests in queue [DBG] (rp_worker_thread_execute:2874) Thread id=140737316480768 signaled. [DBG] (sr_cbuff_dequeue:477) Circular buffer dequeue, new buffer head=1, count=0. [DBG] (rp_rpc_req_process:1759) Processing RPC request. [DBG] (dm_get_data_info:1744) Module ietf-netconf-monitoring already loaded [DBG] (sr_locking_set_lock_fd:734) File /etc/sysrepo/data/ietf-netconf-monitoring.persist has been locked [DBG] (pm_load_data_tree:174) Persist data successfully loaded from file '/etc/sysrepo/data/ietf-netconf-monitoring.persist'. [DBG] (sr_locking_set_unlock_close_fd:803) File /etc/sysrepo/data/ietf-netconf-monitoring.persist (fd = 12) has been unlocked [DBG] (pm_get_subscriptions:817) Returning 0 subscriptions found in 'ietf-netconf-monitoring' persist file. [ERR] (rp_rpc_req_process:1877) No subscription found for RPC delivery (xpath = '/ietf-netconf-monitoring:get-schema'). [DBG] (sr_cbuff_enqueue:461) Circular buffer enqueue to position=0, current count=1. [DBG] (rp_worker_thread_execute:2862) Thread id=140737316480768 will wait. [DBG] (cm_msg_enqueue_cb:1668) New message enqueued into CM message queue. [DBG] (sr_cbuff_dequeue:477) Circular buffer dequeue, new buffer head=1, count=0. [DBG] (cm_conn_out_buff_flush:505) Sending 67 bytes of data. [DBG] (cm_conn_out_buff_flush:511) 67 bytes of data sent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From JoLandry at advaoptical.com Tue Dec 6 16:21:13 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Tue, 6 Dec 2016 16:21:13 +0000 Subject: [sysrepo-devel] notifications In-Reply-To: References: <9efbb697c0034dc6940e7e71758daa09@advaoptical.com> <075a44418c2d46c58c039fe886d4d019@XCH-ALN-015.cisco.com> Message-ID: <168cfb6891c84f54b8f7c89c33b879cc@advaoptical.com> Do you know if there is a plan to support rfc 6470 as part of the notification feature? Specifically will the libraries send out notifications when a change occurs to a data store? Or is that something that needs to be done outside of the libraries. Thanks, -----Original Message----- From: Radek Krej?? [mailto:rkrejci at cesnet.cz] Sent: Tuesday, November 29, 2016 3:52 AM To: Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco) ; Joan Landry ; sysrepo-devel at sysrepo.org Subject: Re: [sysrepo-devel] notifications just a note - they are supported in sysrepo, in Netopeer2 they are not yet fully supported. It shouldn't need much work (I already have some working base code), but because of the busy end of the year, I'm not sure when I'll be able to finish it. Regards, Radek Dne 29.11.2016 v 08:51 Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco) napsal(a): > > Hi, > > notifications are already supported API can be found here https://github.com/sysrepo/sysrepo/blob/master/inc/sysrepo.h#L1441-L1542 > > an example of sending a notification is here > > https://github.com/sysrepo/sysrepo/blob/master/examples/rpc_example.c#L104-L109 > > > > Regards, > > Lukas > > > > > > *From:*sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] *On Behalf Of *Joan Landry > *Sent:* Monday, November 28, 2016 7:28 PM > *To:* sysrepo-devel at sysrepo.org > *Subject:* [sysrepo-devel] notifications > > > > Does anyone know the status of notification support availability? > > > > Also, is there any example code for sending a notification? > > > > > > _______________________________________________ > sysrepo-devel mailing list > sysrepo-devel at sysrepo.org > http://lists.sysrepo.org/listinfo/sysrepo-devel -- Radek Krejci mobile : +420 732 212 714 office : +420 234 680 256 e-mail : rkrejci at cesnet.cz LinkedIn: http://www.linkedin.com/in/radekkrejci CESNET, Association of Legal Entities Zikova 4 160 00 Praha 6 Czech Republic From raszabo at cisco.com Tue Dec 6 17:22:26 2016 From: raszabo at cisco.com (Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco)) Date: Tue, 6 Dec 2016 17:22:26 +0000 Subject: [sysrepo-devel] notifications In-Reply-To: <168cfb6891c84f54b8f7c89c33b879cc@advaoptical.com> References: <9efbb697c0034dc6940e7e71758daa09@advaoptical.com> <075a44418c2d46c58c039fe886d4d019@XCH-ALN-015.cisco.com> <168cfb6891c84f54b8f7c89c33b879cc@advaoptical.com> Message-ID: <8730a2693d4b4b42bab5bb941a4d47e6@XCH-RCD-002.cisco.com> Hi, The support for RFC 6470 is planned, netconf-config-change & netconf-capability-change notifications will be generated automatically by Sysrepo, the rest ones by Netopeer2. Thanks, Rastislav -----Original Message----- From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of Joan Landry Sent: Tuesday, December 6, 2016 5:21 PM To: Radek Krej?? ; Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco) ; sysrepo-devel at sysrepo.org Subject: Re: [sysrepo-devel] notifications Do you know if there is a plan to support rfc 6470 as part of the notification feature? Specifically will the libraries send out notifications when a change occurs to a data store? Or is that something that needs to be done outside of the libraries. Thanks, -----Original Message----- From: Radek Krej?? [mailto:rkrejci at cesnet.cz] Sent: Tuesday, November 29, 2016 3:52 AM To: Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco) ; Joan Landry ; sysrepo-devel at sysrepo.org Subject: Re: [sysrepo-devel] notifications just a note - they are supported in sysrepo, in Netopeer2 they are not yet fully supported. It shouldn't need much work (I already have some working base code), but because of the busy end of the year, I'm not sure when I'll be able to finish it. Regards, Radek Dne 29.11.2016 v 08:51 Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco) napsal(a): > > Hi, > > notifications are already supported API can be found here https://github.com/sysrepo/sysrepo/blob/master/inc/sysrepo.h#L1441-L1542 > > an example of sending a notification is here > > https://github.com/sysrepo/sysrepo/blob/master/examples/rpc_example.c#L104-L109 > > > > Regards, > > Lukas > > > > > > *From:*sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] *On Behalf Of *Joan Landry > *Sent:* Monday, November 28, 2016 7:28 PM > *To:* sysrepo-devel at sysrepo.org > *Subject:* [sysrepo-devel] notifications > > > > Does anyone know the status of notification support availability? > > > > Also, is there any example code for sending a notification? > > > > > > _______________________________________________ > sysrepo-devel mailing list > sysrepo-devel at sysrepo.org > http://lists.sysrepo.org/listinfo/sysrepo-devel -- Radek Krejci mobile : +420 732 212 714 office : +420 234 680 256 e-mail : rkrejci at cesnet.cz LinkedIn: http://www.linkedin.com/in/radekkrejci CESNET, Association of Legal Entities Zikova 4 160 00 Praha 6 Czech Republic _______________________________________________ sysrepo-devel mailing list sysrepo-devel at sysrepo.org http://lists.sysrepo.org/listinfo/sysrepo-devel From raszabo at cisco.com Wed Dec 7 07:30:47 2016 From: raszabo at cisco.com (Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco)) Date: Wed, 7 Dec 2016 07:30:47 +0000 Subject: [sysrepo-devel] New Sysrepo doc: Security Guidelines Message-ID: <4c0d403e646c419fb173fff591dc3371@XCH-RCD-002.cisco.com> Hi, In reaction to the recent remote code execution attack against DSL modems with TR-69 [1] we have added a new piece of documentation to Sysrepo: Security Guidelines [2] [1] https://isc.sans.edu/forums/diary/Port+7547+SOAP+Remote+Code+Execution+Attack+Against+DSL+Modems/21759 [2] http://www.sysrepo.org/static/doc/html/security.html Have a look at it at let me know if there is something you would like to add there. Thanks, Rastislav -------------- next part -------------- An HTML attachment was scrubbed... URL: From rkrejci at cesnet.cz Mon Dec 12 13:19:50 2016 From: rkrejci at cesnet.cz (=?UTF-8?B?UmFkZWsgS3JlasSNw60=?=) Date: Mon, 12 Dec 2016 14:19:50 +0100 Subject: [sysrepo-devel] YANG extensions in libyang Message-ID: <12ac9608-956a-004b-b844-cba08416b066@cesnet.cz> Hi, some of the users already showed their willing to have YANG extensions support in libyang. Current code in master as well as in devel does not support extensions at all and they are removed from the module which makes input and output modules different. I already have code supporting extensions in a separate branch. But the problem with YANG extension is that they can contain anything and can appear anywhere. The current code limit this which helps quite a lot, but now I seen some modules used by confd (formely tail-f, now cisco) and they use extension in statements we didn't expect - e.g. path or argument, simply in usually text nodes which are currently represented in libyang as 'const char*'. So the question is if keep some limitations about the place where the extension can be instantiated or if we should have more generic implementation. The issue with the generic approach is a) more space for schema tree, but because the data tree space is more critical, this shouldn't be a big issue b) we would have to change a lot in lys_* structures, e.g. description or module prefix, now being represented as 'const char *' would have to change to a structure which would contain the value and pointer to the possible extension instances. So the question is if to do a big change in libyang API/ABI, or limit extensions support. I've created an issue about this at libyang issue tracker, and actually because there can be users not subscribed into the sysrepo-devel mailing list, I would prefer to keep this discussion in the issue tracker, thanks - https://github.com/CESNET/libyang/issues/220 Regards, Radek From rkrejci at cesnet.cz Tue Dec 13 15:33:57 2016 From: rkrejci at cesnet.cz (=?UTF-8?B?UmFkZWsgS3JlasSNw60=?=) Date: Tue, 13 Dec 2016 16:33:57 +0100 Subject: [sysrepo-devel] notifications In-Reply-To: <8e0087e9-6b51-4ee9-4a8e-5e8651fe1873@cesnet.cz> References: <9efbb697c0034dc6940e7e71758daa09@advaoptical.com> <075a44418c2d46c58c039fe886d4d019@XCH-ALN-015.cisco.com> <6fc504588452498e9e176793975cb7cf@advaoptical.com> <8e0087e9-6b51-4ee9-4a8e-5e8651fe1873@cesnet.cz> Message-ID: <76757561-ff81-46ef-8720-751290ee4e46@cesnet.cz> Hi, for testing purposes, you can now use Netopeer2's notifications branch, it should work with the devel branches from other projects. I wasn't testing notifications from sysrepo, but I'm receiving netconf-session-start and netconf-session-end notifications generated by the server (and then sent through sysrepo, due to future use of the notifications storage). Notifications replay is not implemented as well as the subtree and xpath filters specified in subscription. Streams match the names of the schemas defining some notification, the default NETCONF stream includes all the notifications. Regards, Radek Dne 30.11.2016 v 10:13 Radek Krej?? napsal(a): > Hi, it is not yet possible. > > Radek > > Dne 30.11.2016 v 03:28 Joan Landry napsal(a): >> Is there a way to turn on this capability, for testing purposes. I am trying to test sending a notification but I think MgSoft browser does not allow you to register for a notification unless the capability is announced. >> >> Else is there another way to test this? >> >> Thanks >> >> -----Original Message----- >> From: Radek Krej?? [mailto:rkrejci at cesnet.cz] >> Sent: Tuesday, November 29, 2016 3:52 AM >> To: Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco) ; Joan Landry ; sysrepo-devel at sysrepo.org >> Subject: Re: [sysrepo-devel] notifications >> >> just a note - they are supported in sysrepo, in Netopeer2 they are not yet fully supported. It shouldn't need much work (I already have some working base code), but because of the busy end of the year, I'm not sure when I'll be able to finish it. >> >> Regards, >> Radek >> >> >> Dne 29.11.2016 v 08:51 Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco) napsal(a): >>> Hi, >>> >>> notifications are already supported API can be found here https://github.com/sysrepo/sysrepo/blob/master/inc/sysrepo.h#L1441-L1542 >>> >>> an example of sending a notification is here >>> >>> https://github.com/sysrepo/sysrepo/blob/master/examples/rpc_example.c#L104-L109 >>> >>> >>> >>> Regards, >>> >>> Lukas >>> >>> >>> >>> >>> >>> *From:*sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] *On Behalf Of *Joan Landry >>> *Sent:* Monday, November 28, 2016 7:28 PM >>> *To:* sysrepo-devel at sysrepo.org >>> *Subject:* [sysrepo-devel] notifications >>> >>> >>> >>> Does anyone know the status of notification support availability? >>> >>> >>> >>> Also, is there any example code for sending a notification? >>> >>> >>> >>> >>> >>> _______________________________________________ >>> sysrepo-devel mailing list >>> sysrepo-devel at sysrepo.org >>> http://lists.sysrepo.org/listinfo/sysrepo-devel -- Radek Krejci mobile : +420 732 212 714 office : +420 234 680 256 e-mail : rkrejci at cesnet.cz LinkedIn: http://www.linkedin.com/in/radekkrejci CESNET, Association of Legal Entities Zikova 4 160 00 Praha 6 Czech Republic From JoLandry at advaoptical.com Wed Dec 14 12:26:47 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Wed, 14 Dec 2016 12:26:47 +0000 Subject: [sysrepo-devel] changing a leaf to boolean Message-ID: In latest master branch I am seeing an issue where when I modify a leaf value to false (when It was previously true) sysrepo sends the new value as true instead of false. If I set the value to false internally via code - I am able to modify it via an rpc call to true,. So for Boolean objects it looks like the only thing you can set it to is true - via an rpc call. Is this a bug? In my callback I get modified op code but the new and old value are the same. MODIFIED: old value/ensemble-config:ensemble-config/ensemble-rate-profile:rate-profiles/rate-profile[name='rate-profile-6']/color-enabled= true new value/ensemble-config:ensemble-config/ensemble-rate-profile:rate-profiles/rate-profile[name='rate-profile-6']/color-enabled= true the rpc in netopeer looks correct: netopeer2-server[697]: Session 1: received message: rate-profile-6 false I get rpc ok -------------- next part -------------- An HTML attachment was scrubbed... URL: From raszabo at cisco.com Wed Dec 14 13:00:58 2016 From: raszabo at cisco.com (Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco)) Date: Wed, 14 Dec 2016 13:00:58 +0000 Subject: [sysrepo-devel] changing a leaf to boolean In-Reply-To: References: Message-ID: <85370603f60647d59affd8cbb4e74e28@XCH-RCD-002.cisco.com> Hi, So the issue is that in the notification callback you get the new value set to TRUE if it was actually changed to FALSE in the datastore? If yes, then this is a bug, please report it on Github (and add Sysrepo traces + steps to reproduce please). Thanks, Rastislav From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of Joan Landry Sent: Wednesday, December 14, 2016 1:27 PM To: sysrepo-devel at sysrepo.org Subject: [sysrepo-devel] changing a leaf to boolean In latest master branch I am seeing an issue where when I modify a leaf value to false (when It was previously true) sysrepo sends the new value as true instead of false. If I set the value to false internally via code - I am able to modify it via an rpc call to true,. So for Boolean objects it looks like the only thing you can set it to is true - via an rpc call. Is this a bug? In my callback I get modified op code but the new and old value are the same. MODIFIED: old value/ensemble-config:ensemble-config/ensemble-rate-profile:rate-profiles/rate-profile[name='rate-profile-6']/color-enabled= true new value/ensemble-config:ensemble-config/ensemble-rate-profile:rate-profiles/rate-profile[name='rate-profile-6']/color-enabled= true the rpc in netopeer looks correct: netopeer2-server[697]: Session 1: received message: rate-profile-6 false I get rpc ok -------------- next part -------------- An HTML attachment was scrubbed... URL: From JoLandry at advaoptical.com Wed Dec 14 19:20:01 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Wed, 14 Dec 2016 19:20:01 +0000 Subject: [sysrepo-devel] is an apostrophe not an allowed character in a key? Message-ID: <7652ad5c9c0944cf955d3af095e0ff31@advaoptical.com> I am seeing that if the key name of something includes and apostrophe libyang sees it as an error. Is the apostrophe not allowed as a character of a key leaf? To set the name my code does the following: snprintf(xpath_buf, 256, "/ensemble-config:ensemble-config/abc-ensemble-domains:domains/domain[name='%s']/owner-tag", name); where if name has normal characters there is no issue - but if name contains an apostrophe I get an error: example: abcd'efg INF] (rp_dt_set_item_wrapper:559) Set item request running datastore, xpath: /ensemble-config:ensemble-config/ensemble-domains:domains/domain[name='abcd'efg']/persistence [DBG] (dm_ly_log_cb:853) libyang error: Unexpected character(s) 'e' (efg']/persisten). [DBG] (dm_ly_log_cb:853) libyang error: Resolving XPath expression "/ensemble-config:ensemble-config/ensemble-domains:domains/domain[name='abcd'efg']/persistence" failed. [ERR] (rp_dt_set_item:323) Requested node is not valid /adva-ensemble-config:ensemble-config/adva-ensemble-domains:domains/domain[name='abcd'efg']/persistence [ERR] (rp_dt_set_item_wrapper:574) Set item failed [ERR] (rp_set_item_req_process:939) Set item failed for '/ensemble-config:ensemble-config/ensemble-domains:domains/domain[name='abcd'efg']/persistence', session id=602346779. In case above name is defined as a string. list domain { key "name"; leaf name { type string; } -------------- next part -------------- An HTML attachment was scrubbed... URL: From mvasko at cesnet.cz Thu Dec 15 08:14:09 2016 From: mvasko at cesnet.cz (=?utf-8?q?Michal_Va=C5=A1ko?=) Date: Thu, 15 Dec 2016 09:14:09 +0100 Subject: [sysrepo-devel] =?utf-8?b?Pz09P3V0Zi04P3E/ICBpcyBhbiBhcG9zdHJv?= =?utf-8?q?phe_not_an_allowed_character_in_a_key=3F?= In-Reply-To: <7652ad5c9c0944cf955d3af095e0ff31@advaoptical.com> Message-ID: <351e-58525100-27-7074f500@172230032> Hi, XPath defines [1] that a literal (which is a string value, such as your key value) enclosed in single-quotes cannot contain a single-quote and in double-quotes cannot contain a double-quote. Hence use double-quotes. Regards, Michal [1] https://www.w3.org/TR/xpath/#NT-Literal On Wednesday, December 14, 2016 20:20 CET, Joan Landry wrote: > I am seeing that if the key name of something includes and apostrophe libyang sees it as an error. > > Is the apostrophe not allowed as a character of a key leaf? > > To set the name my code does the following: > snprintf(xpath_buf, 256, "/ensemble-config:ensemble-config/abc-ensemble-domains:domains/domain[name='%s']/owner-tag", name); > > where if name has normal characters there is no issue - but if name contains an apostrophe I get an error: > example: abcd'efg > > INF] (rp_dt_set_item_wrapper:559) Set item request running datastore, xpath: /ensemble-config:ensemble-config/ensemble-domains:domains/domain[name='abcd'efg']/persistence > [DBG] (dm_ly_log_cb:853) libyang error: Unexpected character(s) 'e' (efg']/persisten). > [DBG] (dm_ly_log_cb:853) libyang error: Resolving XPath expression "/ensemble-config:ensemble-config/ensemble-domains:domains/domain[name='abcd'efg']/persistence" failed. > [ERR] (rp_dt_set_item:323) Requested node is not valid /adva-ensemble-config:ensemble-config/adva-ensemble-domains:domains/domain[name='abcd'efg']/persistence > [ERR] (rp_dt_set_item_wrapper:574) Set item failed > [ERR] (rp_set_item_req_process:939) Set item failed for '/ensemble-config:ensemble-config/ensemble-domains:domains/domain[name='abcd'efg']/persistence', session id=602346779. > > In case above name is defined as a string. > > list domain { > key "name"; > leaf name { > type string; > } From bclaise at cisco.com Fri Dec 16 16:12:26 2016 From: bclaise at cisco.com (Benoit Claise) Date: Fri, 16 Dec 2016 17:12:26 +0100 Subject: [sysrepo-devel] YANG module compilation Message-ID: Hi, See http://www.claise.be/SysrepoApplicationYANGPageCompilation.html *** Generated by yangdump-pro 16.10-2 *** Copyright (c) 2008-2012, Andy Bierman, All Rights Reserved. *** Copyright (c) 2012-2016, YumaWorks, Inc., All Rights Reserved. Error: Got 'sysrepo-lwaftr-loadtest', Expected: name string sysrepo-lwaftr-loadtest at 2016-06-09.yang:1.8: error(245): wrong token type Error: Expected: closing token sysrepo-lwaftr-loadtest at 2016-06-09.yang:65.2: error(244): EOF reached Regards, Benoit -------------- next part -------------- An HTML attachment was scrubbed... URL: From JoLandry at advaoptical.com Fri Dec 16 21:38:03 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Fri, 16 Dec 2016 21:38:03 +0000 Subject: [sysrepo-devel] is an apostrophe not an allowed character in a key? In-Reply-To: <351e-58525100-27-7074f500@172230032> References: <7652ad5c9c0944cf955d3af095e0ff31@advaoptical.com> <351e-58525100-27-7074f500@172230032> Message-ID: I am sorry I am not sure I fully understand your suggestion on how to correct this issue. In the sr_set_item_example.c example code rc = sr_set_item(sess, "/ietf-interfaces:interfaces/interface[name='gigaeth0']/type", &value, SR_EDIT_DEFAULT); what should be entered if the name of the interface is gig'123 I have tried the following combinations and none of them work. rc = sr_set_item(sess, "/ietf-interfaces:interfaces/interface[name='gig'123']/type", &value, SR_EDIT_DEFAULT); rc = sr_set_item(sess, "/ietf-interfaces:interfaces/interface[name='gig\'123']/type", &value, SR_EDIT_DEFAULT); rc = sr_set_item(sess, "/ietf-interfaces:interfaces/interface[name='gig\"'\"123']/type", &value, SR_EDIT_DEFAULT); any info on this would be greatly appreciated. thanks -----Original Message----- From: Michal Va?ko [mailto:mvasko at cesnet.cz] Sent: Thursday, December 15, 2016 3:14 AM To: Joan Landry Cc: sysrepo-devel at sysrepo.org Subject: Re: [sysrepo-devel] is an apostrophe not an allowed character in a key? Hi, XPath defines [1] that a literal (which is a string value, such as your key value) enclosed in single-quotes cannot contain a single-quote and in double-quotes cannot contain a double-quote. Hence use double-quotes. Regards, Michal [1] https://www.w3.org/TR/xpath/#NT-Literal On Wednesday, December 14, 2016 20:20 CET, Joan Landry wrote: > I am seeing that if the key name of something includes and apostrophe libyang sees it as an error. > > Is the apostrophe not allowed as a character of a key leaf? > > To set the name my code does the following: > snprintf(xpath_buf, 256, > "/ensemble-config:ensemble-config/abc-ensemble-domains:domains/domain[ > name='%s']/owner-tag", name); > > where if name has normal characters there is no issue - but if name contains an apostrophe I get an error: > example: abcd'efg > > INF] (rp_dt_set_item_wrapper:559) Set item request running datastore, > xpath: > /ensemble-config:ensemble-config/ensemble-domains:domains/domain[name= > 'abcd'efg']/persistence [DBG] (dm_ly_log_cb:853) libyang error: > Unexpected character(s) 'e' (efg']/persisten). > [DBG] (dm_ly_log_cb:853) libyang error: Resolving XPath expression "/ensemble-config:ensemble-config/ensemble-domains:domains/domain[name='abcd'efg']/persistence" failed. > [ERR] (rp_dt_set_item:323) Requested node is not valid > /adva-ensemble-config:ensemble-config/adva-ensemble-domains:domains/do > main[name='abcd'efg']/persistence [ERR] (rp_dt_set_item_wrapper:574) > Set item failed [ERR] (rp_set_item_req_process:939) Set item failed > for '/ensemble-config:ensemble-config/ensemble-domains:domains/domain[name='abcd'efg']/persistence', session id=602346779. > > In case above name is defined as a string. > > list domain { > key "name"; > leaf name { > type string; > } From JoLandry at advaoptical.com Sun Dec 18 05:56:46 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Sun, 18 Dec 2016 05:56:46 +0000 Subject: [sysrepo-devel] session info Message-ID: <99cd346e3c754b8a8e1c3a2e6596a794@advaoptical.com> Can you tell me what the callbacks are to know the ip address, username of connected sessions? Is this party of NACM - if so is there any info on when this will be available? -------------- next part -------------- An HTML attachment was scrubbed... URL: From lmacko at cisco.com Mon Dec 19 07:10:18 2016 From: lmacko at cisco.com (Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco)) Date: Mon, 19 Dec 2016 07:10:18 +0000 Subject: [sysrepo-devel] is an apostrophe not an allowed character in a key? In-Reply-To: References: <7652ad5c9c0944cf955d3af095e0ff31@advaoptical.com> <351e-58525100-27-7074f500@172230032> Message-ID: <20f38d55c2574667b8ba24f101927729@XCH-ALN-015.cisco.com> Hi, rc = sr_set_item(sess, "/ietf-interfaces:interfaces/interface[name=\"giga'eth0\"]/type", &value, SR_EDIT_DEFAULT); in the example there is more issue: The identity value should be prefixed by module name value.data.string_val = "iana-if-type:ethernetCsmacd"; Regards, Lukas > -----Original Message----- > From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of > Joan Landry > Sent: Friday, December 16, 2016 10:38 PM > To: Michal Va?ko > Cc: sysrepo-devel at sysrepo.org > Subject: Re: [sysrepo-devel] is an apostrophe not an allowed character in a key? > > I am sorry I am not sure I fully understand your suggestion on how to correct > this issue. > > In the sr_set_item_example.c example code > > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gigaeth0']/type", &value, > SR_EDIT_DEFAULT); > > what should be entered if the name of the interface is gig'123 > > I have tried the following combinations and none of them work. > > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gig'123']/type", &value, > SR_EDIT_DEFAULT); > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gig\'123']/type", &value, > SR_EDIT_DEFAULT); > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gig\"'\"123']/type", &value, > SR_EDIT_DEFAULT); > > any info on this would be greatly appreciated. > thanks > > -----Original Message----- > From: Michal Va?ko [mailto:mvasko at cesnet.cz] > Sent: Thursday, December 15, 2016 3:14 AM > To: Joan Landry > Cc: sysrepo-devel at sysrepo.org > Subject: Re: [sysrepo-devel] is an apostrophe not an allowed character in a key? > > Hi, > XPath defines [1] that a literal (which is a string value, such as your key value) > enclosed in single-quotes cannot contain a single-quote and in double-quotes > cannot contain a double-quote. Hence use double-quotes. > > Regards, > Michal > > [1] https://www.w3.org/TR/xpath/#NT-Literal > > On Wednesday, December 14, 2016 20:20 CET, Joan Landry > wrote: > > > I am seeing that if the key name of something includes and apostrophe libyang > sees it as an error. > > > > Is the apostrophe not allowed as a character of a key leaf? > > > > To set the name my code does the following: > > snprintf(xpath_buf, 256, > > "/ensemble-config:ensemble-config/abc-ensemble-domains:domains/domain[ > > name='%s']/owner-tag", name); > > > > where if name has normal characters there is no issue - but if name contains > an apostrophe I get an error: > > example: abcd'efg > > > > INF] (rp_dt_set_item_wrapper:559) Set item request running datastore, > > xpath: > > /ensemble-config:ensemble-config/ensemble- > domains:domains/domain[name= > > 'abcd'efg']/persistence [DBG] (dm_ly_log_cb:853) libyang error: > > Unexpected character(s) 'e' (efg']/persisten). > > [DBG] (dm_ly_log_cb:853) libyang error: Resolving XPath expression > "/ensemble-config:ensemble-config/ensemble- > domains:domains/domain[name='abcd'efg']/persistence" failed. > > [ERR] (rp_dt_set_item:323) Requested node is not valid > > /adva-ensemble-config:ensemble-config/adva-ensemble- > domains:domains/do > > main[name='abcd'efg']/persistence [ERR] (rp_dt_set_item_wrapper:574) > > Set item failed [ERR] (rp_set_item_req_process:939) Set item failed > > for '/ensemble-config:ensemble-config/ensemble- > domains:domains/domain[name='abcd'efg']/persistence', session > id=602346779. > > > > In case above name is defined as a string. > > > > list domain { > > key "name"; > > leaf name { > > type string; > > } > > > > _______________________________________________ > sysrepo-devel mailing list > sysrepo-devel at sysrepo.org > http://lists.sysrepo.org/listinfo/sysrepo-devel From raszabo at cisco.com Mon Dec 19 09:28:01 2016 From: raszabo at cisco.com (Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco)) Date: Mon, 19 Dec 2016 09:28:01 +0000 Subject: [sysrepo-devel] session info In-Reply-To: <99cd346e3c754b8a8e1c3a2e6596a794@advaoptical.com> References: <99cd346e3c754b8a8e1c3a2e6596a794@advaoptical.com> Message-ID: <8de06933032d40aca47a54a829123ac6@XCH-RCD-002.cisco.com> Hi, There are no callbacks for that. Netopeer2 implements ietf-netconf-monitoring YANG (currently in devel-sever branch), which exposes this information: https://github.com/CESNET/Netopeer2/blob/devel-server/modules/ietf-netconf-monitoring.yang Hope this helps, Rastislav From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of Joan Landry Sent: Sunday, December 18, 2016 6:57 AM To: sysrepo-devel at sysrepo.org Subject: [sysrepo-devel] session info Can you tell me what the callbacks are to know the ip address, username of connected sessions? Is this party of NACM - if so is there any info on when this will be available? -------------- next part -------------- An HTML attachment was scrubbed... URL: From JoLandry at advaoptical.com Mon Dec 19 17:11:14 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Mon, 19 Dec 2016 17:11:14 +0000 Subject: [sysrepo-devel] is an apostrophe not an allowed character in a key? In-Reply-To: <20f38d55c2574667b8ba24f101927729@XCH-ALN-015.cisco.com> References: <7652ad5c9c0944cf955d3af095e0ff31@advaoptical.com> <351e-58525100-27-7074f500@172230032> <20f38d55c2574667b8ba24f101927729@XCH-ALN-015.cisco.com> Message-ID: <3da3a5ea00914bee8e5fe5eb2daf5cdd@advaoptical.com> Thanks so much!! -----Original Message----- From: Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco) [mailto:lmacko at cisco.com] Sent: Monday, December 19, 2016 2:10 AM To: Joan Landry ; Michal Va?ko Cc: sysrepo-devel at sysrepo.org Subject: RE: [sysrepo-devel] is an apostrophe not an allowed character in a key? Hi, rc = sr_set_item(sess, "/ietf-interfaces:interfaces/interface[name=\"giga'eth0\"]/type", &value, SR_EDIT_DEFAULT); in the example there is more issue: The identity value should be prefixed by module name value.data.string_val = "iana-if-type:ethernetCsmacd"; Regards, Lukas > -----Original Message----- > From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On > Behalf Of Joan Landry > Sent: Friday, December 16, 2016 10:38 PM > To: Michal Va?ko > Cc: sysrepo-devel at sysrepo.org > Subject: Re: [sysrepo-devel] is an apostrophe not an allowed character in a key? > > I am sorry I am not sure I fully understand your suggestion on how to > correct this issue. > > In the sr_set_item_example.c example code > > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gigaeth0']/type", &value, > SR_EDIT_DEFAULT); > > what should be entered if the name of the interface is gig'123 > > I have tried the following combinations and none of them work. > > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gig'123']/type", &value, > SR_EDIT_DEFAULT); > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gig\'123']/type", &value, > SR_EDIT_DEFAULT); > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gig\"'\"123']/type", &value, > SR_EDIT_DEFAULT); > > any info on this would be greatly appreciated. > thanks > > -----Original Message----- > From: Michal Va?ko [mailto:mvasko at cesnet.cz] > Sent: Thursday, December 15, 2016 3:14 AM > To: Joan Landry > Cc: sysrepo-devel at sysrepo.org > Subject: Re: [sysrepo-devel] is an apostrophe not an allowed character in a key? > > Hi, > XPath defines [1] that a literal (which is a string value, such as > your key value) enclosed in single-quotes cannot contain a > single-quote and in double-quotes cannot contain a double-quote. Hence use double-quotes. > > Regards, > Michal > > [1] https://www.w3.org/TR/xpath/#NT-Literal > > On Wednesday, December 14, 2016 20:20 CET, Joan Landry > wrote: > > > I am seeing that if the key name of something includes and > > apostrophe libyang > sees it as an error. > > > > Is the apostrophe not allowed as a character of a key leaf? > > > > To set the name my code does the following: > > snprintf(xpath_buf, 256, > > "/ensemble-config:ensemble-config/abc-ensemble-domains:domains/domai > > n[ > > name='%s']/owner-tag", name); > > > > where if name has normal characters there is no issue - but if name > > contains > an apostrophe I get an error: > > example: abcd'efg > > > > INF] (rp_dt_set_item_wrapper:559) Set item request running > > datastore, > > xpath: > > /ensemble-config:ensemble-config/ensemble- > domains:domains/domain[name= > > 'abcd'efg']/persistence [DBG] (dm_ly_log_cb:853) libyang error: > > Unexpected character(s) 'e' (efg']/persisten). > > [DBG] (dm_ly_log_cb:853) libyang error: Resolving XPath expression > "/ensemble-config:ensemble-config/ensemble- > domains:domains/domain[name='abcd'efg']/persistence" failed. > > [ERR] (rp_dt_set_item:323) Requested node is not valid > > /adva-ensemble-config:ensemble-config/adva-ensemble- > domains:domains/do > > main[name='abcd'efg']/persistence [ERR] (rp_dt_set_item_wrapper:574) > > Set item failed [ERR] (rp_set_item_req_process:939) Set item failed > > for '/ensemble-config:ensemble-config/ensemble- > domains:domains/domain[name='abcd'efg']/persistence', session > id=602346779. > > > > In case above name is defined as a string. > > > > list domain { > > key "name"; > > leaf name { > > type string; > > } > > > > _______________________________________________ > sysrepo-devel mailing list > sysrepo-devel at sysrepo.org > http://lists.sysrepo.org/listinfo/sysrepo-devel From JoLandry at advaoptical.com Mon Dec 19 19:01:14 2016 From: JoLandry at advaoptical.com (Joan Landry) Date: Mon, 19 Dec 2016 19:01:14 +0000 Subject: [sysrepo-devel] is an apostrophe not an allowed character in a key? In-Reply-To: <20f38d55c2574667b8ba24f101927729@XCH-ALN-015.cisco.com> References: <7652ad5c9c0944cf955d3af095e0ff31@advaoptical.com> <351e-58525100-27-7074f500@172230032> <20f38d55c2574667b8ba24f101927729@XCH-ALN-015.cisco.com> Message-ID: <53f3e1a482d34150ad9d22eff3eaaedb@advaoptical.com> Hi, I was able to successfully set with an apostrophe in the name of the key using your suggestion snprintf(xpath_buf, 256, "/ensemble-config:ensemble-config/ensemble-domains:domains/domain[name=\"%s\"]/owner-tag", name); Where name = abcd'def However a get rpc error is returned when I tried to read it back s - is there something in netopeer2 preventing a get on a name with an apostrophe in it? RPC Error Reply 42 for session 1: application operation-failed error Unexpected character(s) 'd' (def']). Netopeer2 [2016/12/19 13:48:15.346591, 3] ssh_packet_socket_callback: packet: read type 94 [len=508,padding=8,comp=499,payload=499] [2016/12/19 13:48:15.346647, 3] ssh_packet_process: Dispatching handler for packet type 94 [2016/12/19 13:48:15.346774, 3] channel_rcv_data: Channel receiving 490 bytes data in 0 (local win=1263304 remote win=39563725) [2016/12/19 13:48:15.346799, 3] channel_default_bufferize: placing 490 bytes into channel buffer (stderr=0) [2016/12/19 13:48:15.346823, 3] channel_rcv_data: Channel windows are now (local win=1262814 remote win=39563725) [2016/12/19 13:48:15.346852, 3] ssh_channel_read_timeout: Read (1) buffered : 490 bytes. Window: 1262814 [2016/12/19 13:48:15.346930, 3] ssh_channel_read_timeout: Read (1) buffered : 489 bytes. Window: 1262814 [2016/12/19 13:48:15.346957, 3] ssh_channel_read_timeout: Read (1) buffered : 488 bytes. Window: 1262814 [2016/12/19 13:48:15.346981, 3] ssh_channel_read_timeout: Read (1) buffered : 487 bytes. Window: 1262814 [2016/12/19 13:48:15.347005, 3] ssh_channel_read_timeout: Read (1) buffered : 486 bytes. Window: 1262814 [2016/12/19 13:48:15.347028, 3] ssh_channel_read_timeout: Read (1) buffered : 485 bytes. Window: 1262814 [2016/12/19 13:48:15.347055, 3] ssh_channel_read_timeout: Read (480) buffered : 484 bytes. Window: 1262814 [2016/12/19 13:48:15.347081, 3] ssh_channel_read_timeout: Read (1) buffered : 4 bytes. Window: 1262814 [2016/12/19 13:48:15.347105, 3] ssh_channel_read_timeout: Read (1) buffered : 3 bytes. Window: 1262814 [2016/12/19 13:48:15.347129, 3] ssh_channel_read_timeout: Read (1) buffered : 2 bytes. Window: 1262814 [2016/12/19 13:48:15.347152, 3] ssh_channel_read_timeout: Read (1) buffered : 1 bytes. Window: 1262814 netopeer2-server[29098]: Session 1: received message: netopeer2-server[29098]: DICT: inserting "rpc" with collision netopeer2-server[29098]: DICT: inserting "message-id" with collision netopeer2-server[29098]: DICT: inserting "42" with collision netopeer2-server[29098]: DICT: inserting (refcount) "urn:ietf:params:xml:ns:netconf:base:1.0" netopeer2-server[29098]: DICT: inserting (refcount) "get-config" netopeer2-server[29098]: DICT: inserting (refcount) "urn:ietf:params:xml:ns:netconf:base:1.0" netopeer2-server[29098]: DICT: inserting (refcount) "source" netopeer2-server[29098]: DICT: inserting (refcount) "running" netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "filter" netopeer2-server[29098]: DICT: inserting (refcount) "ensemble-config" netopeer2-server[29098]: DICT: inserting (refcount) "http://www.abc.com/ns/ensemble-config" netopeer2-server[29098]: DICT: inserting (refcount) "domains" netopeer2-server[29098]: DICT: inserting (refcount) "http://www.abcl.com/ns/ensemble-domains" netopeer2-server[29098]: DICT: inserting " " with collision netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: Resolving unresolved data nodes and their constraints... netopeer2-server[29098]: All data nodes and constraints resolved. netopeer2-server[29098]: XPATH: expression "/ietf-netconf:get-config/source/*": netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "ietf-netconf:get-config" netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "source" netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "*" netopeer2-server[29098]: XPATH: eval_absolute_location_path parsed Operator(Path)[0] netopeer2-server[29098]: DICT: inserting (refcount) "get-config" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[1] netopeer2-server[29098]: XPATH: eval_relative_location_path parsed Operator(Path)[24] netopeer2-server[29098]: DICT: inserting (refcount) "source" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[25] netopeer2-server[29098]: XPATH: eval_relative_location_path parsed Operator(Path)[31] netopeer2-server[29098]: DICT: inserting (refcount) "*" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[32] netopeer2-server[29098]: (cl_request_process:420) Sending session-switch-ds request. netopeer2-server[29098]: (cl_request_process:442) session-switch-ds request sent, waiting for response. netopeer2-server[29098]: (cl_request_process:464) session-switch-ds response received, processing. netopeer2-server[29098]: XPATH: expression "/ietf-netconf:*/filter": netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "ietf-netconf:*" netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "filter" netopeer2-server[29098]: XPATH: eval_absolute_location_path parsed Operator(Path)[0] netopeer2-server[29098]: DICT: inserting (refcount) "*" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[1] netopeer2-server[29098]: XPATH: eval_relative_location_path parsed Operator(Path)[15] netopeer2-server[29098]: DICT: inserting (refcount) "filter" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[16] netopeer2-server[29098]: XPATH: expression "/ietf-netconf:*/ietf-netconf-with-defaults:with-defaults": netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "ietf-netconf:*" netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "ietf-netconf-with-defaults:with-defaults" netopeer2-server[29098]: XPATH: eval_absolute_location_path parsed Operator(Path)[0] netopeer2-server[29098]: DICT: inserting (refcount) "*" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[1] netopeer2-server[29098]: XPATH: eval_relative_location_path parsed Operator(Path)[15] netopeer2-server[29098]: DICT: inserting (refcount) "with-defaults" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[16] netopeer2-server[29098]: (cl_request_process:420) Sending session-refresh request. netopeer2-server[29098]: (cl_request_process:442) session-refresh request sent, waiting for response. netopeer2-server[29098]: (cl_request_process:464) session-refresh response received, processing. netopeer2-server[29098]: (cl_request_process:420) Sending get-items request. netopeer2-server[29098]: (cl_request_process:442) get-items request sent, waiting for response. netopeer2-server[29098]: (cl_request_process:464) get-items response received, processing. netopeer2-server[29098]: (cl_request_process:420) Sending get-items request. netopeer2-server[29098]: (cl_request_process:442) get-items request sent, waiting for response. netopeer2-server[29098]: (cl_request_process:464) get-items response received, processing. netopeer2-server[29098]: DICT: inserting "default" with collision netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "true" netopeer2-server[29098]: DICT: inserting "abcd" with collision netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "true" netopeer2-server[29098]: Unexpected character(s) 'd' (def']). netopeer2-server[29098]: DICT: inserting "Request could not be completed because the requested operation failed for a non-specific reason." with collision netopeer2-server[29098]: DICT: inserting "en" with collision netopeer2-server[29098]: DICT: inserting "Unexpected character(s) 'd' (def'])." with collision netopeer2-server[29098]: DICT: inserting "en" with collision netopeer2-server[29098]: Session 1: sending message: #304 [2016/12/19 13:48:15.369739, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket [2016/12/19 13:48:15.369781, 3] packet_send2: packet: wrote [len=28,padding=12,comp=15,payload=15] [2016/12/19 13:48:15.369805, 3] channel_write_common: channel_write wrote 6 bytes netopeer2-server[29098]: Session 1: sending message: applicationoperation-failederrorUnexpected character(s) 'd' (def']). [2016/12/19 13:48:15.369887, 3] packet_send2: packet: wrote [len=332,padding=18,comp=313,payload=313] [2016/12/19 13:48:15.369912, 3] channel_write_common: channel_write wrote 304 bytes [2016/12/19 13:48:15.369944, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket netopeer2-server[29098]: Session 1: sending message: ## [2016/12/19 13:48:15.370011, 3] packet_send2: packet: wrote [len=28,padding=14,comp=13,payload=13] [2016/12/19 13:48:15.370704, 3] channel_write_common: channel_write wrote 4 bytes [2016/12/19 13:48:15.370741, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket -----Original Message----- From: Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco) [mailto:lmacko at cisco.com] Sent: Monday, December 19, 2016 2:10 AM To: Joan Landry ; Michal Va?ko Cc: sysrepo-devel at sysrepo.org Subject: RE: [sysrepo-devel] is an apostrophe not an allowed character in a key? Hi, rc = sr_set_item(sess, "/ietf-interfaces:interfaces/interface[name=\"giga'eth0\"]/type", &value, SR_EDIT_DEFAULT); in the example there is more issue: The identity value should be prefixed by module name value.data.string_val = "iana-if-type:ethernetCsmacd"; Regards, Lukas > -----Original Message----- > From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On > Behalf Of Joan Landry > Sent: Friday, December 16, 2016 10:38 PM > To: Michal Va?ko > Cc: sysrepo-devel at sysrepo.org > Subject: Re: [sysrepo-devel] is an apostrophe not an allowed character in a key? > > I am sorry I am not sure I fully understand your suggestion on how to > correct this issue. > > In the sr_set_item_example.c example code > > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gigaeth0']/type", &value, > SR_EDIT_DEFAULT); > > what should be entered if the name of the interface is gig'123 > > I have tried the following combinations and none of them work. > > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gig'123']/type", &value, > SR_EDIT_DEFAULT); > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gig\'123']/type", &value, > SR_EDIT_DEFAULT); > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gig\"'\"123']/type", &value, > SR_EDIT_DEFAULT); > > any info on this would be greatly appreciated. > thanks > > -----Original Message----- > From: Michal Va?ko [mailto:mvasko at cesnet.cz] > Sent: Thursday, December 15, 2016 3:14 AM > To: Joan Landry > Cc: sysrepo-devel at sysrepo.org > Subject: Re: [sysrepo-devel] is an apostrophe not an allowed character in a key? > > Hi, > XPath defines [1] that a literal (which is a string value, such as > your key value) enclosed in single-quotes cannot contain a > single-quote and in double-quotes cannot contain a double-quote. Hence use double-quotes. > > Regards, > Michal > > [1] https://www.w3.org/TR/xpath/#NT-Literal > > On Wednesday, December 14, 2016 20:20 CET, Joan Landry > wrote: > > > I am seeing that if the key name of something includes and > > apostrophe libyang > sees it as an error. > > > > Is the apostrophe not allowed as a character of a key leaf? > > > > To set the name my code does the following: > > snprintf(xpath_buf, 256, > > "/ensemble-config:ensemble-config/abc-ensemble-domains:domains/domai > > n[ > > name='%s']/owner-tag", name); > > > > where if name has normal characters there is no issue - but if name > > contains > an apostrophe I get an error: > > example: abcd'efg > > > > INF] (rp_dt_set_item_wrapper:559) Set item request running > > datastore, > > xpath: > > /ensemble-config:ensemble-config/ensemble- > domains:domains/domain[name= > > 'abcd'efg']/persistence [DBG] (dm_ly_log_cb:853) libyang error: > > Unexpected character(s) 'e' (efg']/persisten). > > [DBG] (dm_ly_log_cb:853) libyang error: Resolving XPath expression > "/ensemble-config:ensemble-config/ensemble- > domains:domains/domain[name='abcd'efg']/persistence" failed. > > [ERR] (rp_dt_set_item:323) Requested node is not valid > > /adva-ensemble-config:ensemble-config/adva-ensemble- > domains:domains/do > > main[name='abcd'efg']/persistence [ERR] (rp_dt_set_item_wrapper:574) > > Set item failed [ERR] (rp_set_item_req_process:939) Set item failed > > for '/ensemble-config:ensemble-config/ensemble- > domains:domains/domain[name='abcd'efg']/persistence', session > id=602346779. > > > > In case above name is defined as a string. > > > > list domain { > > key "name"; > > leaf name { > > type string; > > } > > > > _______________________________________________ > sysrepo-devel mailing list > sysrepo-devel at sysrepo.org > http://lists.sysrepo.org/listinfo/sysrepo-devel From raszabo at cisco.com Tue Dec 20 07:14:10 2016 From: raszabo at cisco.com (Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco)) Date: Tue, 20 Dec 2016 07:14:10 +0000 Subject: [sysrepo-devel] is an apostrophe not an allowed character in a key? In-Reply-To: <53f3e1a482d34150ad9d22eff3eaaedb@advaoptical.com> References: <7652ad5c9c0944cf955d3af095e0ff31@advaoptical.com> <351e-58525100-27-7074f500@172230032> <20f38d55c2574667b8ba24f101927729@XCH-ALN-015.cisco.com> <53f3e1a482d34150ad9d22eff3eaaedb@advaoptical.com> Message-ID: <10e59772e99e4b1b8f1131886746b9b1@XCH-RCD-002.cisco.com> Hi, > is there something in netopeer2 preventing a get on a name with an apostrophe in it It seems. Since guys from CESNET are already on leave, they probably won?t reply so soon, so I would suggest you to open an issue on Netopeer's github page for this. Rastislav -----Original Message----- From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of Joan Landry Sent: Monday, December 19, 2016 8:01 PM To: Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco) ; Michal Va?ko Cc: sysrepo-devel at sysrepo.org Subject: Re: [sysrepo-devel] is an apostrophe not an allowed character in a key? Hi, I was able to successfully set with an apostrophe in the name of the key using your suggestion snprintf(xpath_buf, 256, "/ensemble-config:ensemble-config/ensemble-domains:domains/domain[name=\"%s\"]/owner-tag", name); Where name = abcd'def However a get rpc error is returned when I tried to read it back s - is there something in netopeer2 preventing a get on a name with an apostrophe in it? RPC Error Reply 42 for session 1: application operation-failed error Unexpected character(s) 'd' (def']). Netopeer2 [2016/12/19 13:48:15.346591, 3] ssh_packet_socket_callback: packet: read type 94 [len=508,padding=8,comp=499,payload=499] [2016/12/19 13:48:15.346647, 3] ssh_packet_process: Dispatching handler for packet type 94 [2016/12/19 13:48:15.346774, 3] channel_rcv_data: Channel receiving 490 bytes data in 0 (local win=1263304 remote win=39563725) [2016/12/19 13:48:15.346799, 3] channel_default_bufferize: placing 490 bytes into channel buffer (stderr=0) [2016/12/19 13:48:15.346823, 3] channel_rcv_data: Channel windows are now (local win=1262814 remote win=39563725) [2016/12/19 13:48:15.346852, 3] ssh_channel_read_timeout: Read (1) buffered : 490 bytes. Window: 1262814 [2016/12/19 13:48:15.346930, 3] ssh_channel_read_timeout: Read (1) buffered : 489 bytes. Window: 1262814 [2016/12/19 13:48:15.346957, 3] ssh_channel_read_timeout: Read (1) buffered : 488 bytes. Window: 1262814 [2016/12/19 13:48:15.346981, 3] ssh_channel_read_timeout: Read (1) buffered : 487 bytes. Window: 1262814 [2016/12/19 13:48:15.347005, 3] ssh_channel_read_timeout: Read (1) buffered : 486 bytes. Window: 1262814 [2016/12/19 13:48:15.347028, 3] ssh_channel_read_timeout: Read (1) buffered : 485 bytes. Window: 1262814 [2016/12/19 13:48:15.347055, 3] ssh_channel_read_timeout: Read (480) buffered : 484 bytes. Window: 1262814 [2016/12/19 13:48:15.347081, 3] ssh_channel_read_timeout: Read (1) buffered : 4 bytes. Window: 1262814 [2016/12/19 13:48:15.347105, 3] ssh_channel_read_timeout: Read (1) buffered : 3 bytes. Window: 1262814 [2016/12/19 13:48:15.347129, 3] ssh_channel_read_timeout: Read (1) buffered : 2 bytes. Window: 1262814 [2016/12/19 13:48:15.347152, 3] ssh_channel_read_timeout: Read (1) buffered : 1 bytes. Window: 1262814 netopeer2-server[29098]: Session 1: received message: netopeer2-server[29098]: DICT: inserting "rpc" with collision netopeer2-server[29098]: DICT: inserting "message-id" with collision netopeer2-server[29098]: DICT: inserting "42" with collision netopeer2-server[29098]: DICT: inserting (refcount) "urn:ietf:params:xml:ns:netconf:base:1.0" netopeer2-server[29098]: DICT: inserting (refcount) "get-config" netopeer2-server[29098]: DICT: inserting (refcount) "urn:ietf:params:xml:ns:netconf:base:1.0" netopeer2-server[29098]: DICT: inserting (refcount) "source" netopeer2-server[29098]: DICT: inserting (refcount) "running" netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "filter" netopeer2-server[29098]: DICT: inserting (refcount) "ensemble-config" netopeer2-server[29098]: DICT: inserting (refcount) "http://www.abc.com/ns/ensemble-config" netopeer2-server[29098]: DICT: inserting (refcount) "domains" netopeer2-server[29098]: DICT: inserting (refcount) "http://www.abcl.com/ns/ensemble-domains" netopeer2-server[29098]: DICT: inserting " " with collision netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: Resolving unresolved data nodes and their constraints... netopeer2-server[29098]: All data nodes and constraints resolved. netopeer2-server[29098]: XPATH: expression "/ietf-netconf:get-config/source/*": netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "ietf-netconf:get-config" netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "source" netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "*" netopeer2-server[29098]: XPATH: eval_absolute_location_path parsed Operator(Path)[0] netopeer2-server[29098]: DICT: inserting (refcount) "get-config" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[1] netopeer2-server[29098]: XPATH: eval_relative_location_path parsed Operator(Path)[24] netopeer2-server[29098]: DICT: inserting (refcount) "source" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[25] netopeer2-server[29098]: XPATH: eval_relative_location_path parsed Operator(Path)[31] netopeer2-server[29098]: DICT: inserting (refcount) "*" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[32] netopeer2-server[29098]: (cl_request_process:420) Sending session-switch-ds request. netopeer2-server[29098]: (cl_request_process:442) session-switch-ds request sent, waiting for response. netopeer2-server[29098]: (cl_request_process:464) session-switch-ds response received, processing. netopeer2-server[29098]: XPATH: expression "/ietf-netconf:*/filter": netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "ietf-netconf:*" netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "filter" netopeer2-server[29098]: XPATH: eval_absolute_location_path parsed Operator(Path)[0] netopeer2-server[29098]: DICT: inserting (refcount) "*" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[1] netopeer2-server[29098]: XPATH: eval_relative_location_path parsed Operator(Path)[15] netopeer2-server[29098]: DICT: inserting (refcount) "filter" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[16] netopeer2-server[29098]: XPATH: expression "/ietf-netconf:*/ietf-netconf-with-defaults:with-defaults": netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "ietf-netconf:*" netopeer2-server[29098]: XPATH: Token Operator(Path), in expression "/" netopeer2-server[29098]: XPATH: Token NameTest, in expression "ietf-netconf-with-defaults:with-defaults" netopeer2-server[29098]: XPATH: eval_absolute_location_path parsed Operator(Path)[0] netopeer2-server[29098]: DICT: inserting (refcount) "*" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[1] netopeer2-server[29098]: XPATH: eval_relative_location_path parsed Operator(Path)[15] netopeer2-server[29098]: DICT: inserting (refcount) "with-defaults" netopeer2-server[29098]: XPATH: eval_node_test parsed NameTest[16] netopeer2-server[29098]: (cl_request_process:420) Sending session-refresh request. netopeer2-server[29098]: (cl_request_process:442) session-refresh request sent, waiting for response. netopeer2-server[29098]: (cl_request_process:464) session-refresh response received, processing. netopeer2-server[29098]: (cl_request_process:420) Sending get-items request. netopeer2-server[29098]: (cl_request_process:442) get-items request sent, waiting for response. netopeer2-server[29098]: (cl_request_process:464) get-items response received, processing. netopeer2-server[29098]: (cl_request_process:420) Sending get-items request. netopeer2-server[29098]: (cl_request_process:442) get-items request sent, waiting for response. netopeer2-server[29098]: (cl_request_process:464) get-items response received, processing. netopeer2-server[29098]: DICT: inserting "default" with collision netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "true" netopeer2-server[29098]: DICT: inserting "abcd" with collision netopeer2-server[29098]: DICT: inserting (refcount) "" netopeer2-server[29098]: DICT: inserting (refcount) "true" netopeer2-server[29098]: Unexpected character(s) 'd' (def']). netopeer2-server[29098]: DICT: inserting "Request could not be completed because the requested operation failed for a non-specific reason." with collision netopeer2-server[29098]: DICT: inserting "en" with collision netopeer2-server[29098]: DICT: inserting "Unexpected character(s) 'd' (def'])." with collision netopeer2-server[29098]: DICT: inserting "en" with collision netopeer2-server[29098]: Session 1: sending message: #304 [2016/12/19 13:48:15.369739, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket [2016/12/19 13:48:15.369781, 3] packet_send2: packet: wrote [len=28,padding=12,comp=15,payload=15] [2016/12/19 13:48:15.369805, 3] channel_write_common: channel_write wrote 6 bytes netopeer2-server[29098]: Session 1: sending message: applicationoperation-failederrorUnexpected character(s) 'd' (def']). [2016/12/19 13:48:15.369887, 3] packet_send2: packet: wrote [len=332,padding=18,comp=313,payload=313] [2016/12/19 13:48:15.369912, 3] channel_write_common: channel_write wrote 304 bytes [2016/12/19 13:48:15.369944, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket netopeer2-server[29098]: Session 1: sending message: ## [2016/12/19 13:48:15.370011, 3] packet_send2: packet: wrote [len=28,padding=14,comp=13,payload=13] [2016/12/19 13:48:15.370704, 3] channel_write_common: channel_write wrote 4 bytes [2016/12/19 13:48:15.370741, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket -----Original Message----- From: Lukas Macko -X (lmacko - PANTHEON TECHNOLOGIES at Cisco) [mailto:lmacko at cisco.com] Sent: Monday, December 19, 2016 2:10 AM To: Joan Landry ; Michal Va?ko Cc: sysrepo-devel at sysrepo.org Subject: RE: [sysrepo-devel] is an apostrophe not an allowed character in a key? Hi, rc = sr_set_item(sess, "/ietf-interfaces:interfaces/interface[name=\"giga'eth0\"]/type", &value, SR_EDIT_DEFAULT); in the example there is more issue: The identity value should be prefixed by module name value.data.string_val = "iana-if-type:ethernetCsmacd"; Regards, Lukas > -----Original Message----- > From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On > Behalf Of Joan Landry > Sent: Friday, December 16, 2016 10:38 PM > To: Michal Va?ko > Cc: sysrepo-devel at sysrepo.org > Subject: Re: [sysrepo-devel] is an apostrophe not an allowed character in a key? > > I am sorry I am not sure I fully understand your suggestion on how to > correct this issue. > > In the sr_set_item_example.c example code > > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gigaeth0']/type", &value, > SR_EDIT_DEFAULT); > > what should be entered if the name of the interface is gig'123 > > I have tried the following combinations and none of them work. > > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gig'123']/type", &value, > SR_EDIT_DEFAULT); > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gig\'123']/type", &value, > SR_EDIT_DEFAULT); > rc = sr_set_item(sess, "/ietf- > interfaces:interfaces/interface[name='gig\"'\"123']/type", &value, > SR_EDIT_DEFAULT); > > any info on this would be greatly appreciated. > thanks > > -----Original Message----- > From: Michal Va?ko [mailto:mvasko at cesnet.cz] > Sent: Thursday, December 15, 2016 3:14 AM > To: Joan Landry > Cc: sysrepo-devel at sysrepo.org > Subject: Re: [sysrepo-devel] is an apostrophe not an allowed character in a key? > > Hi, > XPath defines [1] that a literal (which is a string value, such as > your key value) enclosed in single-quotes cannot contain a > single-quote and in double-quotes cannot contain a double-quote. Hence use double-quotes. > > Regards, > Michal > > [1] https://www.w3.org/TR/xpath/#NT-Literal > > On Wednesday, December 14, 2016 20:20 CET, Joan Landry > wrote: > > > I am seeing that if the key name of something includes and > > apostrophe libyang > sees it as an error. > > > > Is the apostrophe not allowed as a character of a key leaf? > > > > To set the name my code does the following: > > snprintf(xpath_buf, 256, > > "/ensemble-config:ensemble-config/abc-ensemble-domains:domains/domai > > n[ > > name='%s']/owner-tag", name); > > > > where if name has normal characters there is no issue - but if name > > contains > an apostrophe I get an error: > > example: abcd'efg > > > > INF] (rp_dt_set_item_wrapper:559) Set item request running > > datastore, > > xpath: > > /ensemble-config:ensemble-config/ensemble- > domains:domains/domain[name= > > 'abcd'efg']/persistence [DBG] (dm_ly_log_cb:853) libyang error: > > Unexpected character(s) 'e' (efg']/persisten). > > [DBG] (dm_ly_log_cb:853) libyang error: Resolving XPath expression > "/ensemble-config:ensemble-config/ensemble- > domains:domains/domain[name='abcd'efg']/persistence" failed. > > [ERR] (rp_dt_set_item:323) Requested node is not valid > > /adva-ensemble-config:ensemble-config/adva-ensemble- > domains:domains/do > > main[name='abcd'efg']/persistence [ERR] (rp_dt_set_item_wrapper:574) > > Set item failed [ERR] (rp_set_item_req_process:939) Set item failed > > for '/ensemble-config:ensemble-config/ensemble- > domains:domains/domain[name='abcd'efg']/persistence', session > id=602346779. > > > > In case above name is defined as a string. > > > > list domain { > > key "name"; > > leaf name { > > type string; > > } > > > > _______________________________________________ > sysrepo-devel mailing list > sysrepo-devel at sysrepo.org > http://lists.sysrepo.org/listinfo/sysrepo-devel _______________________________________________ sysrepo-devel mailing list sysrepo-devel at sysrepo.org http://lists.sysrepo.org/listinfo/sysrepo-devel From bhatkj at gmail.com Tue Dec 20 08:41:14 2016 From: bhatkj at gmail.com (krishnaprasad bhat) Date: Tue, 20 Dec 2016 14:11:14 +0530 Subject: [sysrepo-devel] How to increase timeout against operation data callback In-Reply-To: References: <1479482069761.64128@pantheon.tech> Message-ID: Hi, We did change RP_OPER_DATA_REQ_TIMEOUT MACRO value. But it seems looks like it doesn't taking effect. However when i am running sysrepo in debug mode i do see the log which say reflects new value. Also given that their are other parameters to consider so just wondering what is the MAX value recommend for RP_OPER_DATA_REQ_TIMEOUT ? Thanks, Krishna On Fri, Nov 18, 2016 at 9:10 PM, krishnaprasad bhat wrote: > Hi Milan, > Thank you. > > Personally i feel it would be worth. So i have created the issue > https://github.com/sysrepo/sysrepo/issues/550 > > > -Krishna > > > On Fri, Nov 18, 2016 at 8:44 PM, Milan Len?o > wrote: > >> Hi, >> >> >> currently the timeout for operational data retrieval is not >> CMake-configurable. It is only defined by macro RP_OPER_DATA_REQ_TIMEOUT in >> src/request_processor.c >> >> If you feel this is worth of propagating to CMake configuration, then >> please file an enhancement request on github: >> https://github.com/sysrepo/sysrepo/issues >> >> >> Thanks, >> >> Milan >> ------------------------------ >> *Od:* krishnaprasad bhat >> *Odoslan?:* 18. novembra 2016 16:06 >> *Komu:* sysrepo-devel at sysrepo.org >> *Predmet:* [sysrepo-devel] How to increase timeout against operation >> data callback >> >> Hi, all: >> Is their any easy way to increase the timeout value so that GET request >> doesn't timeout, to accommodate the scenario where in the operational data >> provider callback (i.e. registered via sr_dp_get_items_subscribe api ) >> takes longer to process. >> >> Thanks, >> Krishna >> >> MilanLen?o >> >> Software Developer >> >> >> S?dlo / Mlynsk? Nivy 56 / 821 05 Bratislava / Slovakia >> R&D centrum / Janka Kr??a 9 / 974 01 Bansk? Bystrica / Slovakia >> / Milan.Lenco at pantheon.tech >> reception: +421 2 206 65 114 / www.pantheon.sk >> >> [image: logo] >> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From raszabo at cisco.com Wed Dec 21 07:38:48 2016 From: raszabo at cisco.com (Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco)) Date: Wed, 21 Dec 2016 07:38:48 +0000 Subject: [sysrepo-devel] How to increase timeout against operation data callback In-Reply-To: References: <1479482069761.64128@pantheon.tech> Message-ID: <267b6f7a5e2d4a64bbf7e705dd82f8cc@XCH-RCD-002.cisco.com> Hi, There is another timeout that you may need to tweak, CL_REQUEST_TIMEOUT in the client library (3 seconds by default). Rastislav From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of krishnaprasad bhat Sent: Tuesday, December 20, 2016 9:41 AM To: Milan Len?o Cc: Sysrepo-public Subject: Re: [sysrepo-devel] How to increase timeout against operation data callback Hi, We did change RP_OPER_DATA_REQ_TIMEOUT MACRO value. But it seems looks like it doesn't taking effect. However when i am running sysrepo in debug mode i do see the log which say reflects new value. Also given that their are other parameters to consider so just wondering what is the MAX value recommend for RP_OPER_DATA_REQ_TIMEOUT ? Thanks, Krishna On Fri, Nov 18, 2016 at 9:10 PM, krishnaprasad bhat > wrote: Hi Milan, Thank you. Personally i feel it would be worth. So i have created the issue https://github.com/sysrepo/sysrepo/issues/550 -Krishna On Fri, Nov 18, 2016 at 8:44 PM, Milan Len?o > wrote: Hi, currently the timeout for operational data retrieval is not CMake-configurable. It is only defined by macro RP_OPER_DATA_REQ_TIMEOUT in src/request_processor.c If you feel this is worth of propagating to CMake configuration, then please file an enhancement request on github: https://github.com/sysrepo/sysrepo/issues Thanks, Milan ________________________________ Od: krishnaprasad bhat > Odoslan?: 18. novembra 2016 16:06 Komu: sysrepo-devel at sysrepo.org Predmet: [sysrepo-devel] How to increase timeout against operation data callback Hi, all: Is their any easy way to increase the timeout value so that GET request doesn't timeout, to accommodate the scenario where in the operational data provider callback (i.e. registered via sr_dp_get_items_subscribe api ) takes longer to process. Thanks, Krishna MilanLen?o Software Developer S?dlo / Mlynsk? Nivy 56 / 821 05 Bratislava / Slovakia R&D centrum / Janka Kr??a 9 / 974 01 Bansk? Bystrica / Slovakia / Milan.Lenco at pantheon.tech reception: +421 2 206 65 114 / www.pantheon.sk [logo] -------------- next part -------------- An HTML attachment was scrubbed... URL: From fan.changhu at zte.com.cn Wed Dec 21 09:01:58 2016 From: fan.changhu at zte.com.cn (fan.changhu at zte.com.cn) Date: Wed, 21 Dec 2016 17:01:58 +0800 (CST) Subject: [sysrepo-devel] =?utf-8?q?about=C2=A0Updating_a_Module_in_sysrepo?= Message-ID: <201612211701582513437@zte.com.cn> SGksDQoNCg0KRG9lcyBzeXNyZXBvIGhhcyBhbnkgcGxhbiBhYm91dCBVcGRhdGluZyBhIE1vZHVs ZSBhcyBkZXNjcmliZWQgaW4gaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzc5NTAjc2Vj dGlvbi0xMSA/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From raszabo at cisco.com Wed Dec 21 09:15:44 2016 From: raszabo at cisco.com (Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco)) Date: Wed, 21 Dec 2016 09:15:44 +0000 Subject: [sysrepo-devel] =?utf-8?q?about=C2=A0Updating_a_Module_in_sysrep?= =?utf-8?q?o?= In-Reply-To: <201612211701582513437@zte.com.cn> References: <201612211701582513437@zte.com.cn> Message-ID: <0f9ed971b9d544699fcda94f29270ae9@XCH-RCD-002.cisco.com> Hi, We are tracking it as an enhancement: https://github.com/sysrepo/sysrepo/issues/287 So far we don?t have any estimates for this, we currently have other priorities. Contributions via pull requests are always welcome ? Thanks, Rastislav From: sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] On Behalf Of fan.changhu at zte.com.cn Sent: Wednesday, December 21, 2016 10:02 AM To: sysrepo-devel at sysrepo.org Subject: [sysrepo-devel] about Updating a Module in sysrepo Hi, Does sysrepo has any plan about Updating a Module as described in https://tools.ietf.org/html/rfc7950#section-11 ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From bhatkj at gmail.com Wed Dec 21 11:08:56 2016 From: bhatkj at gmail.com (krishnaprasad bhat) Date: Wed, 21 Dec 2016 16:38:56 +0530 Subject: [sysrepo-devel] How to increase timeout against operation data callback In-Reply-To: <267b6f7a5e2d4a64bbf7e705dd82f8cc@XCH-RCD-002.cisco.com> References: <1479482069761.64128@pantheon.tech> <267b6f7a5e2d4a64bbf7e705dd82f8cc@XCH-RCD-002.cisco.com> Message-ID: Hi Rastislav, Thank you. It is working now. -Krishna On Wed, Dec 21, 2016 at 1:08 PM, Rastislav Szabo -X (raszabo - PANTHEON TECHNOLOGIES at Cisco) wrote: > Hi, > > > > There is another timeout that you may need to tweak, CL_REQUEST_TIMEOUT in > the client library (3 seconds by default). > > > > Rastislav > > > > *From:* sysrepo-devel [mailto:sysrepo-devel-bounces at sysrepo.org] *On > Behalf Of *krishnaprasad bhat > *Sent:* Tuesday, December 20, 2016 9:41 AM > *To:* Milan Len?o > *Cc:* Sysrepo-public > *Subject:* Re: [sysrepo-devel] How to increase timeout against operation > data callback > > > > Hi, > > > > We did change RP_OPER_DATA_REQ_TIMEOUT MACRO value. But it seems looks > like it doesn't taking effect. > > However when i am running sysrepo in debug mode i do see the log which say > reflects new value. > > > > Also given that their are other parameters to consider so just wondering > what is the MAX value recommend for RP_OPER_DATA_REQ_TIMEOUT ? > > > > Thanks, > > Krishna > > > > > > > > > > > > > > On Fri, Nov 18, 2016 at 9:10 PM, krishnaprasad bhat > wrote: > > Hi Milan, > > Thank you. > > > > Personally i feel it would be worth. So i have created the issue > https://github.com/sysrepo/sysrepo/issues/550 > > > > > > -Krishna > > > > > > On Fri, Nov 18, 2016 at 8:44 PM, Milan Len?o > wrote: > > Hi, > > > > currently the timeout for operational data retrieval is not > CMake-configurable. It is only defined by macro RP_OPER_DATA_REQ_TIMEOUT in > src/request_processor.c > > If you feel this is worth of propagating to CMake configuration, then > please file an enhancement request on github: https://github.com/sysrepo/ > sysrepo/issues > > > > Thanks, > > Milan > ------------------------------ > > *Od:* krishnaprasad bhat > *Odoslan?:* 18. novembra 2016 16:06 > *Komu:* sysrepo-devel at sysrepo.org > *Predmet:* [sysrepo-devel] How to increase timeout against operation data > callback > > > > Hi, all: > > Is their any easy way to increase the timeout value so that GET request > doesn't timeout, to accommodate the scenario where in the operational data > provider callback (i.e. registered via sr_dp_get_items_subscribe api ) > takes longer to process. > > > > Thanks, > > Krishna > > Milan*Len?o* > > Software Developer > > > S?dlo / Mlynsk? Nivy 56 / 821 05 Bratislava / Slovakia > R&D centrum / Janka Kr??a 9 / 974 01 Bansk? Bystrica / Slovakia > / Milan.Lenco at pantheon.tech > reception: +421 2 206 65 114 / www.pantheon.sk > > [image: logo] > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: