What is the difference between a comment and a label?
As part of the commit option, there is a 'comment' and there is a 'label' that I can add to the commit. I am curious what the difference is between these two. I see that both show up in the rollback information, but does one do something the other does not?
Example: admin@ncs% set ebgpPeer name LAX password laxpass peer csr1 asn 100 ip 22.214.171.124 admin@ncs% set ebgpPeer name LAX peer csr2 asn 200 ip 126.96.36.199 admin@ncs% commit comment ? Possible completions: Add a commit comment admin@ncs% commit comment "this is for fun" label "but it should be really fun" Commit complete. [ok][2018-10-30 17:25:11]
 [root@studentnso GSXbgp]#
and from ./logs
[root@studentnso logs]# cat rollback10061 # Created by: admin # Date: 2018-10-30 17:25:02 # Via: cli # Type: delta # Label: but it should be really fun # Comment: this is for fun # No: 10061
Regarding your question, i've observed the yang model and came up with a conclusion.
in the confd_lib_maapi(3):
int maapi_set_label(int sock, int thandle, const char *label);
Set the "Label" that is stored in the rollback file when a transaction
towards running is committed. Setting the "Label" for transactions via
candidate can be done when the candidate is committed to running, by
using the maapi_candidate_commit_info() function. For a confirmed
commit, the "Label" must also be given via the
Errors: CONFD_ERR_MALLOC, CONFD_ERR_OS, CONFD_ERR_NOSESSION,
int maapi_set_comment(int sock, int thandle, const char *comment);
Set the "Comment" that is stored in the rollback file when a
transaction towards running is committed. Setting the "Comment" for
transactions via candidate can be done when the candidate is committed
to running, by using the maapi_candidate_commit_info() function. For a
confirmed commit, the "Comment" must also be given via the
This is the most detail i can find regarding your question, but i would assume/suspect that the comment can be used per say a 'descriptive' purpose of the commit while the label would be to very vaguely describe the purpose of the commit or associated some sort of ID that relates to the project associated to the commit transaction.
Unfortunately, there is not much information regarding the differences within the yang or NCS CLI.
Step 1 : configure debug server in Pycharm
Go to Run => Edit Configurations, click on "+" => Python Remote Debug
In "Local Host name " enter ip or host name of your local machine. Enter a available port in "Port :"
Give a name, here it's "NSO debug...
Abstract: RFM services can be hard to implement. Especially the lifecycle management of the delete case of the service can be a challenge. Nano Services uses an executable plan and kickers to supports the full lifecycle of a RFM service.
Previous instalments of this blog post series have covered requirements (parts I and II) and baselining, profiling/optimising and monitoring (part III). In this final part we will discuss some architectures you may want to consider as your system grows in...
In part I and part II of this blog, we have been discussing scale and performance requirements. In this third instalment we are going to look at baselining, profiling, optimising and monitoring scale and performance.
Baselining Scale and Perfo...
In part I of our Unlocking Performance in your NSO System blog we started discussing scale and performance requirements, including
Size of device configuration
Number of service instances
Frequency of operation