Re: [vpp-dev] jvpp compatiblity

2020-06-17 Thread Jerome Tollet via lists.fd.io
Hi Chang, There’s no active development on jvpp as well as honeycomb but any contribution to update them is of course more than welcome. If you need to program vpp, I’d recommend considering go, c or python. Jerome De : au nom de Hyunseok Date : jeudi 18 juin 2020 à 03:21 À : "vpp-dev@lists.fd.

Re: [EXTERNAL] Re: [vpp-dev] VPP sequential policy command execution giving error

2020-06-17 Thread Chinmaya Aggarwal
Can anyone please suggest something for this? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16748): https://lists.fd.io/g/vpp-dev/message/16748 Mute This Topic: https://lists.fd.io/mt/74477804/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscrib

Re: [vpp-dev] Fetching SR Policy data using VPP C API

2020-06-17 Thread Chinmaya Aggarwal
Can anyone please suggest something for this? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16747): https://lists.fd.io/g/vpp-dev/message/16747 Mute This Topic: https://lists.fd.io/mt/74894689/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscrib

[vpp-dev] jvpp compatiblity

2020-06-17 Thread Hyunseok
Hi, It seems the current jvpp is not compatible with the latest vpp 20.05. Building jvpp against the latest vpp fails. Looks like jvpp development has stopped since vpp 19.04. Is there any plan to update jvpp to make it compatible with the latest vpp?  In fact I do not understand why jvpp was dro

Re: [vpp-dev] ikev2 API & new API change process

2020-06-17 Thread Benoit Ganne (bganne) via lists.fd.io
> Yeah, i would rather not mark all api in progress since that would make > the transition much longer. Agreed. > So I suggest a 1 month period during a developer that wants to downgrade > an API, prepares a change with *just that action*, clearly marked “API > downgrade”, type: fix, adds me as a

Re: [vpp-dev] ikev2 API & new API change process

2020-06-17 Thread Ole Troan
> Personally, I think it would be a good idea to mark ALL APIs as In-Progress, > as it matches the (lack of) guarantees in previous releases, > and let maintainers mark some messages as Production on their own pace. I'm not sure how you could reconcile that with e.g. the CRC job verifier nor all

Re: [vpp-dev] ikev2 API & new API change process

2020-06-17 Thread Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via lists.fd.io
I think there are two issues. One issue is with APIs that were not intended to be Production yet. For ikev2 that basically means the version has been set [5] above 0.x.y only by mistake. As downgrading versions is always risky, marking messages as "In-Progress" instead is better. The other issue