Attention is currently required from: laforge, pespin, msuraev.

2 comments:

Patchset:
- Patch Set #5:
  That's pretty big - shouldn't there be some tests/ additions to ensure things won't fall apart?
  I tested with the ttcn3 test suite, first of all whether everything still works with a single cs7, same as jenkins, and then i also tested manually with separate cs7 instances ... So I tested it (TM) and we can merge it now;
  Or, if you reviewers prefer we can first wait for the entire MSC/SGSN pooling feature to be complete -- this is only the first step in a yet larger refactoring.
  I submitted it early because customer wants to use this as a workaround.
  For the CN pooling feature, there will be substantial new tests and infrastructure in HNBGW_Tests.ttcn and I guess we should configure one or two of the MSCs/SGSNs of the CN pool in the ttcn3 tests in separate cs7 instances.
  Short answer is: yes, will come =) not part of this patch
- Patch Set #5:
  What I am missing here is dding a new .cfg file to doc/examples/ showcasing this new possible setup. […]
  (i have no idea why this is marked resolved, unresolving now)

To view, visit change 32323. To unsubscribe, or for help writing mail filters, visit settings.