We have a fairly advanced git / CI setup for building NEDs, compiling our own NSO service code and packaging it all up in container images. Some of those bits can get a bit tedious over time and I recently wrote a bit about it and I thought I'd share here, https://plajjan.github.io/automating-git
I have not tried this with Jenkins. While I have used Jenkins in the past I have fairly limited experience with it. I think as a system, it was born in a different day and age than GitLab CI. Based on what I want to do and my expectations of what the CI system should do for me, GitLab CI is a better fit.
For example, per default GitLab CI will create a clean environment (a container) in which it checks out your code and executes the test. After it's done, that environment is removed. There is never a problem of tainting one test through the actions run by a different test. Jenkins however, does not do this for you, per default. You can configure it, but it just requires more time and care to do what GitLab CI will do out of the box. That's why we use GitLab CI.
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