#opnfv-meeting: Weekly Technical Discussion

Meeting started by bh526r at 14:00:02 UTC (full logs).

Meeting summary

  1. Roll Call (bh526r, 14:00:11)
    1. Brandon Wick (bh526r, 14:00:18)
    2. Trevor Cooper (bh526r, 14:00:25)
    3. Trevor Bramwell (bramwelt, 14:00:29)
    4. Cristina Pauna (bh526r, 14:00:54)
    5. Cristina Pauna (CristinaPauna, 14:01:40)
    6. David McBride (dmcbride_, 14:01:50)
    7. Al Morton (bh526r, 14:05:18)

  2. Infrastructure Evolution (bh526r, 14:05:42)
    1. Al Morton (acm, 14:06:01)
    2. Trevor summarized what has been discussed in email thread (bh526r, 14:06:01)
    3. Trevor reviewed the background of looking into packet.net (bh526r, 14:06:32)
    4. David further added that the reason of adding packet.net was because the Cisco server was not supported in LF lab in Portland (bh526r, 14:07:42)
    5. Comments from email indicated that current Pharos lab (community lab) was under-utilized (bh526r, 14:08:23)
    6. Rex Lee (mj_rex, 14:09:21)
    7. If we roll Intel lab into LaaS, we will get all benefits to Intel lab and community (bh526r, 14:09:35)
    8. Suggestion is to add Pharos lab in LaaS (bh526r, 14:10:10)
    9. At beginning, although LaaS was not visioned to support the use case of spanning over multiple Pharos labs (bh526r, 14:11:13)
    10. Trevor C understands that packet.net will replace all LF-hosted services (bh526r, 14:13:00)
    11. Does it include all servers that Intel donated? (bh526r, 14:13:22)
    12. David M and Trevor B clarified that packet.net will replace those 16 (or 13) Cisco UCS servers, because no one in LF lab was trained to support those hardware. We used to have support contract, but not any more because of budget. Thus those 16 (or 13) Cisco UCS server has not support (though Frank arranged some kind of ad-hoc support as a favor from some Cisco engineer). (bh526r, 14:15:15)
    13. What will be remaining in LF lab? (bh526r, 14:16:14)
    14. Answer is Intel servers (3 or 6), used for XCI (bh526r, 14:16:30)
    15. Packet.net is VM based. The only option of baremetal is AWS, but it needs some kind of configuration of networking which may or may not work for OPNFV (bh526r, 14:19:19)
    16. Trevor B and David M further indicated that we may have a good deal with packet.net that intends to support LFN, and replacing hardware could be free of charge. (bh526r, 14:20:17)
    17. David M indicated that we can have a trial of packet.net for a couple of months, like test drive, for free. (bh526r, 14:20:47)
    18. Trevor C thinks that if those 16 Cisco UCS server was replaced, we should compare those 16 UCS server with packet.net. (bh526r, 14:21:54)
    19. David M indicated we had this comparison a couple of months ago (bh526r, 14:22:38)
    20. Trevor C indicated that we should compared the support of UCS v.s. support of packet.net (bh526r, 14:23:17)
    21. Current support of 6 Intel is very low. If we replace those 16 UCS server with 16 vanilla servers, the support will still be low. (bh526r, 14:24:19)
    22. The cost of replacing 16 server is $300k, and support of packet.net is $300k for 18 months. So the break-even point is 18 months. And the cost of $19k per server is very expensive. Usual cost of each server is about $4k-5k (bh526r, 14:26:52)
    23. David M clarified it is based on cost model in UNH-IOL lab (bh526r, 14:27:16)
    24. Trevor C mentioned that many of UNH-IOL lab hardware was donated by Intel (bh526r, 14:27:43)
    25. Trevor B agrees that we should have a clearer picture. (bh526r, 14:31:51)
    26. David M, Trevor B and Trevor C work together to find out more accurate estimate of the cost v.s. support, and the break-even point. (bh526r, 14:35:19)
    27. Once we have that information, it is easier to agree to a way to move forward (bh526r, 14:35:43)
    28. The information should also cover the information such as capacity, networking options, etc., as much as possible, for evaluation purpose. (bh526r, 14:37:10)
    29. David M mentioned that perhaps the best way of evaluation is to design a trial (bh526r, 14:39:46)
    30. Jack Morgan (bh526r, 14:51:10)
    31. Trevor C asked the question is if we use packet.net, is it feasible to do dynamically-allocated pods? (bh526r, 14:52:21)
    32. Trevor B said it actually makes it easier to do dynamic pods (bh526r, 14:53:05)

  3. AOB (bh526r, 15:03:59)
    1. Meeting adjourned (bh526r, 15:04:08)


Meeting ended at 15:04:12 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. bh526r (41)
  2. dmcbride_ (3)
  3. collabot` (3)
  4. acm (1)
  5. bramwelt (1)
  6. CristinaPauna (1)
  7. mj_rex (1)


Generated by MeetBot 0.1.4.