#opnfv-ovsnfv: Weekly Open vSwitch for NFV meeting (27th October 2015)

Meeting started by mdgray at 14:01:00 UTC (full logs).

Meeting summary

  1. Roll Call (mdgray, 14:01:29)
    1. mdgray (mdgray, 14:01:32)
    2. Billy O'Mahony (billyoma, 14:02:14)
    3. Gabor Halasz (gabor_halasz_, 14:02:21)
    4. TFHerbert (tfherbert, 14:02:29)

  2. Agenda Bashing (mdgray, 14:03:24)
    1. Upstream code discussion. How do we deal with out of tree patches? (mdgray, 14:03:45)
    2. RDO (mdgray, 14:03:52)
    3. Fuel Update (mdgray, 14:03:56)
    4. CI Update (mdgray, 14:04:02)

  3. Upstream code discussion (mdgray, 14:05:20)
    1. As a project, we stated that we wouldn't fork OVS but there is discussion as to how we deal with out-of-tree patches. e.g. NSH patches (mdgray, 14:07:26)
    2. question is how to deal with nsh, multi-queue before they are merged upstream (tfherbert, 14:07:32)
    3. http://lists.opnfv.org/pipermail/opnfv-tech-discuss/2015-October/006031.html (mdgray, 14:09:38)
    4. Daniel outlined how Fuel upstream model works in Opnfv (mdgray, 14:10:04)
    5. Tom states that some things might not be available upstream by B-release (mdgray, 14:11:37)
    6. Daniel Smith suggests to discuss with Debra what are artifacts would be (mdgray, 14:12:00)
    7. How long do we maintain out-of-tree patches? (mdgray, 14:15:05)
    8. If things sit for a long time who maintains the patches. (mdgray, 14:15:43)
    9. Two current example features are multiqueue and nsh (mdgray, 14:16:51)
    10. Suggestion is that the feature developer maintains the feature (mdgray, 14:18:11)
    11. Do we use a temporary repo? (mdgray, 14:19:29)
    12. until things get upstreamed (mdgray, 14:19:42)
    13. OPNFV takes upstream only code (mdgray, 14:20:19)
    14. ACTION: Tom to bring this up at the Release meeting (mdgray, 14:27:50)

  4. RDO (mdgray, 14:29:53)
    1. Fuel is more suited to deploying ubuntu (mdgray, 14:30:54)
    2. Arno the fuel work was more targeted to Ubuntu as Foreman was targeted to Centos. There was no point in duplicating effort. (mdgray, 14:31:48)
    3. Fuel is targeting Mirantis 8 for B-release (mdgray, 14:32:14)
    4. Still not sure about what the plans are for CentOS support in Fuel for B-release (mdgray, 14:32:50)
    5. Hard to align all component versions. We could be developing against Arno but for B-release, all opnfv component versions could change. (mdgray, 14:34:52)
    6. General agreement that we should be enabling RDO (mdgray, 14:36:05)
    7. There were some feature gaps in RDO that made this difficult. Installing an alternate rpm was one key feature. (mdgray, 14:37:00)
    8. For RDO, we need to be able to substitute Open vSwitch rpm. (mdgray, 14:40:43)
    9. and any other related infrstructure (mdgray, 14:40:58)
    10. ACTION: mdgray Discuss next week. (mdgray, 14:41:21)

  5. Fuel update (mdgray, 14:42:00)
    1. VM install appears to be working on Daniel's montreal pod (mdgray, 14:43:23)
    2. We have an agreed methodology that is it repeatable (mdgray, 14:44:45)
    3. Gabor will email out final instructions (mdgray, 14:45:09)
    4. Gabor needs to know what format is expected and a link where to upload it (gabor_halasz_, 14:46:55)
    5. Good progress! Good starting point that we can begin to modify. (mdgray, 14:47:10)
    6. Gabor ideally the wiki, i think? (mdgray, 14:47:28)
    7. https://wiki.opnfv.org/ovsnfv?&#key_project_facts (mdgray, 14:48:13)
    8. Building an ISO behind a proxy. Very close. Great support from the OPNFV fuel team. (mdgray, 14:50:55)
    9. Billy is trying to create a fuel plugin (mdgray, 14:53:07)
    10. Billy added Jira stories to flesh out what needs to be done here (mdgray, 14:53:16)
    11. Plugin will install userspace ovs and dependencies (mdgray, 14:53:38)
    12. Ubuntu will be easier for initial deployment due to Fuel. (mdgray, 14:55:07)
    13. When we have something working, it will be easier to look at centos. (mdgray, 14:55:39)
    14. Good help from fuel team (mdgray, 14:56:29)

  6. CI (mdgray, 14:58:08)
    1. Never getting time for this! (mdgray, 14:58:14)
    2. Need to put time in the agenda for this next week (mdgray, 14:58:25)
    3. ACTION: mdgray Mark to put this at the head of agenda next week (mdgray, 14:58:42)
    4. We should start with basic CI (not even include tests initially) (mdgray, 15:00:19)
    5. Tom and Sriram have been looking at this (mdgray, 15:01:01)


Meeting ended at 15:01:34 UTC (full logs).

Action items

  1. Tom to bring this up at the Release meeting
  2. mdgray Discuss next week.
  3. mdgray Mark to put this at the head of agenda next week


Action items, by person

  1. mdgray
    1. mdgray Discuss next week.
    2. mdgray Mark to put this at the head of agenda next week


People present (lines said)

  1. mdgray (56)
  2. collabot (4)
  3. tfherbert (2)
  4. gabor_halasz_ (2)
  5. billyoma (1)


Generated by MeetBot 0.1.4.