Hello all The integration test got resolved but @Anil Belur is still looking for the root cause. In any case, Here is the new CSIT spreadsheet for Aluminium AR

hi ahmed, some more inputs. not sure if survey-takers will be willing/allowed to answer with specifics for proprietary controllers, so there should be a choice for 'proprietary', without mentioning

hi all, few comments from me - typo - Ericsson product is called CSC (Cloud SDN Controller) what type of sdn do you use for k8s - should be broken up into the foll - 'what type of networking solution

Zoom session: https://zoom.us/j/91654497219 Meeting page:

OK then ill pick up AR#220.. Aluminium integrations tests are stuck though... https://jenkins.opendaylight.org/releng/view/autorelease/job/integration-distribution-test-aluminium/ I just opened a

oops, I meant 278 not 277. but it's done and has passed. I forgot that we gave super committer rights by default during code freeze. Thanks for reminding me :) JamO On

Thanks Jamo and Karthik, Indeed, I'll pick tonight's Aluminium AR ... but this netvirt job/277 was completed yesterday, you meant 279? Also i think that Supercommitters' powers allow you to merge even

Ok Karthikeyan, I merged it with super committer powers I guess. I did not expect those to be active. The Aluminium branch should have been locked. @Anil, do you know why we

Hi Daniel/Jamo, Can you please merge the fix[1] into a stable/aluminium branch as i do not have privilege to merge. [1] https://git.opendaylight.org/gerrit/c/netvirt/+/92279

Sure - makes sense.

I also feel TWS would be better for this discussion.

I have no objection to waiting for this fix to come in, but it will require a new autorelease to pass and distribution-test to run so we can vet the results of CSIT. Thanks,

Sounds good.

Hi Daniel, Marked the below JIRA with highest priority. https://jira.opendaylight.org/browse/NETVIRT-1709 Thanks, Srinivas +91-9243478719

Hello Karthik. Ok we can wait until [1] gets fixed, if TSC doesn't have any objections to delay Aluminium a bit more. Please mark the jira ticket as highest priority so it shows up as a blocker if

Hi Abhijit, Maybe TWS calls are a better choice than TSC, given the nature of the subject. We have a free flowing discussion without the agenda hanging over us. Just a thought. BR Manoj

The TSC meetings are always open to all - so Abhijit C and Niral Networks are welcome and can talk about their use case. It will be definitely good if they are planning to contribute to the two

Jim, It is currently a weekend - so I think we should give the TSC at least 3-4 days to review? Maybe Thursday or Friday? If we keep it Friday - we can also discuss it in the TSC meeting on

Hi Ahmed, I see some of the questions also apply to non DC use cases so maybe we can structure the questions as follows: Do you use SDN? If No, what is the reason for not adopting SDN? (add

Hi Daniel, As per the srinivas input(Based on the CSIT Job results) NAT use cases are not working due to the exception[0]. It would be good if we include the fix[1] also into the Aluminium release