#opendaylight-devforum5: Inter-Project Infrastructure Services

Meeting started by tykeal at 18:25:19 UTC (full logs).

Meeting summary

  1. How to do cross project testing (tykeal, 18:26:06)
    1. tools we have: jenkins, sonar, nexus (tykeal, 18:26:46)
    2. docs & integration projects -- integrating the ecosystem (tykeal, 18:27:41)
    3. Talking about tools we have, tools we need (dfarrell07, 18:29:27)
    4. Tools we have: Jenkins, Sonar, Nexus, docs, integration projects (dfarrell07, 18:29:53)
    5. Tools we need: Branding strategy (I think that's what the board says) (dfarrell07, 18:30:23)
    6. "We need to scale tykeal" (dfarrell07, 18:30:57)
    7. Getting Started for Projects wiki is helpful for scaling andy (dfarrell07, 18:31:26)
    8. General discussion about how projects get started, where they look at docs and such (dfarrell07, 18:33:11)
    9. regXboi points out that there's some reasons to privilage important things like project starting/building wikis, group decides this is out of scope (dfarrell07, 18:34:50)
    10. Can't rely on individual projects talking to tykeal, doesn't scale, via rovarga (dfarrell07, 18:35:33)
    11. Possible solution is infra project, rovarga (dfarrell07, 18:35:48)
    12. Sounds great, but who will write it - colindixon (dfarrell07, 18:36:10)
    13. regXboi points out that adding tooling on the fly without process is a problem (dfarrell07, 18:37:29)
    14. colindixon notes that to outsource infrastructure from the projects you need a well defined interface. That iterface today is POM files (phrobb, 18:38:26)
    15. "Infra project" would be responsible for defining structure, API - rovarga (dfarrell07, 18:39:18)
    16. May need to hire someone to look a things like POM files, say they have issues. In general, if outsorcing project gen/tools, need more people first, then automate (dfarrell07, 18:41:11)
    17. continued discussion about automation vs person to help projects with infra/tools/building (dfarrell07, 18:42:29)
    18. rovarga wants it to be very easy for committers to start a new project with minimal knowledge of underlying infrastructure (phrobb, 18:42:39)
    19. Issues/limitations with mvn being discussed (dfarrell07, 18:45:10)
    20. this infrastructure project would evaluate and document how changing infrastructure components would impact all projects. example is moving from maven to gradle (phrobb, 18:46:19)
    21. Pushback on changing tooling, don't want to make this a per-release tool change. Need to become stable at some point. (dfarrell07, 18:48:10)
    22. Docs on how to use and audit build tools are a good first step, cool things in the future would be good of course, but making sure folks know what to do is 90% (dfarrell07, 18:50:07)
    23. starting to formalize problems, find people to fix them (dfarrell07, 18:53:17)
    24. Problem: Many general POM issues (dfarrell07, 18:54:03)
    25. Problem: Projects don't know how to set up Jenkinds, POMs, Sonar, etc (dfarrell07, 18:54:30)
    26. cleaning up the POM hierarchy is a problem for DevinAvery (phrobb, 18:54:36)
    27. Problem: People should use odlparent and be able to tel lif they are dangerously overriding things (dfarrell07, 18:55:05)
    28. effective POM doesn't explain the hierarchy and references across different POM files from different projects (phrobb, 18:56:10)
    29. Problem: POM file structure is really *unknown word*, eg, don't mirror dir structure (dfarrell07, 18:56:31)
    30. Problem: HOWTOs and wiki pages can help once, but don't help with maintaining (dfarrell07, 19:00:11)
    31. Problem: How do we manage inter-project versions? (dfarrell07, 19:00:36)
    32. Problem: Howe do we "go back in time" (dfarrell07, 19:00:47)
    33. Problem: How do we bump versions? (dfarrell07, 19:02:51)
    34. continued discussion about bumping versions (dfarrell07, 19:04:50)
    35. "What problem do we hate the most"? Let's pick one and focus on it. (dfarrell07, 19:05:31)
    36. Main problem proposal0: Versions (dfarrell07, 19:06:04)
    37. Problems that become inter-project actually only screw over a few people who do inter-project work, projects can/do ignore it (dfarrell07, 19:07:01)
    38. Hack fest to work on one or more of these projects, maybe tomorrow attack one of these (dfarrell07, 19:08:19)
    39. Major problem proposal1: ODL parent does dep and plugin managment, not list of version strings, if you don't specifiy you get the right one, throw warning if you choose a different one, hard to override but not impossible (dfarrell07, 19:10:11)
    40. Major proposal2: Make sure OpenFlow Java inherits from common parent (dfarrell07, 19:12:02)
    41. Major proposal3: Tool to check for this family of issues (dfarrell07, 19:12:24)
    42. properly commenting file and having code review may be better than tool to check for all possible mistakes in this domain (dfarrell07, 19:13:05)
    43. Tests are better, says many people (dfarrell07, 19:13:35)
    44. Major project proposal4: Make really solid POM file to use as example (dfarrell07, 19:14:46)
    45. Recap of major projects people seem to care about the most: Fix ODL parent, make ODL Java use it, docuemnt what POMs do and how they do it (dfarrell07, 19:15:56)
    46. Who sould own ODL parent? How do we handle artifcats that you don't maintain in your code. Maybe scope creep here (dfarrell07, 19:17:05)
    47. TODO0: Fix ODL parent; with plugin managment; with dependency managment for 3rd party artifacts (dfarrell07, 19:18:13)
    48. TODO1: Convert OpenFlow Java to use TODO0 in best current practice (dfarrell07, 19:18:39)
    49. TODO2: Document what TODO1 solves, how and why (dfarrell07, 19:18:54)
    50. this needs to be an unconf or just grab a room and do it (dfarrell07, 19:19:13)
    51. send email to -discuss when this happens so others can find it (dfarrell07, 19:19:33)
    52. Edit to TODO0: It should not break other projects (dfarrell07, 19:20:26)
    53. Edit to TODO0: Get it into Gerrit, start thinking looking, don't merge soon (dfarrell07, 19:21:19)


Meeting ended at 19:22:10 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. dfarrell07 (53)
  2. regXboi (9)
  3. tykeal (8)
  4. phrobb (5)
  5. odl_meetbot (5)
  6. dbainbri (2)
  7. zxiiro (1)


Generated by MeetBot 0.1.4.