Artem Glazychev

I'm not sure if this is the problem. You are right that sometimes we see errors. But the integration-tests are designed in such a way that if we get an...

@ljkiraly Could you please take a look if you have a chance?

hi @316953425 We've discussed this issue a bit - we haven't actually run these examples for a while. Perhaps we will consider this issue in the next release.

@edwarnicke I looked at the VCL feature and tried to run it for NSM. There are a few questions: **_1. How do we plan to share the socket with the...

@edwarnicke Not really I agree that in case of VCL we don't need traffic selection on _the NSC side_. But what will we do on _the forwarder side_ to which...

@edwarnicke Yes. And as far as I understand, we can't. We must assign an IP address and route to this VPP interface (one end of a 'cross connect', vxlan for...

Hello @barby1138, Thanks for the report! In fact, we have the opportunity to use any host interface for the forwarder: for this we need to specify the NSM_TUNNEL_IP env. For...

Hello @316953425 , Yes we agree there is some lack of documentation especially to bootstrap and start working on NSM in very beginning for new members and we are working...

Thanks for the detailed information. We have created issues for the site and deployments-k8s repositories improvement: - https://github.com/networkservicemesh/site/issues/261 - https://github.com/networkservicemesh/site/issues/262 - https://github.com/networkservicemesh/deployments-k8s/issues/10487 ETA ~ 2w Also, we'll respond soon to...

Hi @316953425 , These issues are still in progress: https://github.com/networkservicemesh/site/issues/262 https://github.com/networkservicemesh/deployments-k8s/issues/10487 You can take a look at: https://github.com/networkservicemesh/site/pull/265 https://github.com/networkservicemesh/site/pull/264 https://github.com/networkservicemesh/deployments-k8s/issues/10487#issuecomment-1833380783