Page tree
Skip to end of metadata
Go to start of metadata

Weekly Meetings

  • Weekly on Monday at 16:00 UTC

  • GTM Link https://global.gotomeeting.com/join/819733085
  • Minutes at Infra Working Group Meeting
  • IRC #opnfv-meeting - freenode.net

  • Chaired by Luke Hinds for Jan/Feb (meetings chaired by Infra PTLs on a 2-month basis)

  • You can also dial in using your phone with Access Code: 819-733-085  

    • United States +1 (312) 757-3126 

    • Australia +61 2 8355 1040 

    • Austria +43 7 2088 0034 

    • Belgium +32 (0) 28 93 7018 

    • Canada +1 (647) 497-9350 

    • Denmark +45 69 91 88 64 

    • Finland +358 (0) 923 17 0568 

    • France +33 (0) 170 950 592 

    • Germany +49 (0) 692 5736 7211 

    • Ireland +353 (0) 15 360 728 

    • Italy +39 0 247 92 13 01 

    • Netherlands +31 (0) 208 080 219 

    • New Zealand +64 9 280 6302 

    • Norway +47 75 80 32 07 

    • Spain +34 911 82 9906 

    • Sweden +46 (0) 853 527 836 

    • Switzerland +41 (0) 435 0167 13 

    • United Kingdom +44 (0) 330 221 0086 

Scope and Goals

Working Group scope is all  infrastructure cross project initiatives activities with cross-project impact ... this includes

  • Dashboards for use of lab and CI resources
  • Prioritization / allocation of lab resources .. see Hardware Infrastructure
  • Inconsistencies in use of CI resources

Agenda


January 15th

Agenda:

  1. Octopus project clean up - JIRA, Confluence, git repository julien zhang
  2. Discuss automatically adding INFO.yaml to all repos. https://gerrit.opnfv.org/gerrit/#/c/50381/ Aric Gardner
  3. Moving forward with Ansible playbook for build servers. (Waiting on vpn access to an arm server) https://gerrit.opnfv.org/gerrit/#/c/49747/ Aric Gardner
  4. Vote on documenting Pharos in INFRA section http://docs.opnfv.org/en/latest/infrastructure/overview.html Aric Gardner

Action Items:

  • Check with/remind Luke Hinds regarding chairing the meeting during Jan/Feb, Fatih Degirmenci

  • Remind the next chair regarding going back to original start time, 15:00UTC, Fatih Degirmenci

  • Create repo for release automation and start working on it, Trevor Bramwell

  • Pass the names of the slaves connected from Intel lab for removal, Jack Morgan

  • Remove the slaves offline for 4 months or more, Aric Gardner

  • Look at the schema used by OpenStack release automation/handling and come up with a simplified proposal for OPNFV, David McBride

  • Talk to zxiiro about redirecting OPNFV Releng channels to #lf-releng, Trevor Bramwell

  • Talk to BII for moving lab/pod config to pharos, julien zhang

  • Start conversation around defining the test requirements for gating scenarios for the release, David McBride

  • Investigate configuring the default path for Jenkins consistently/globally Trevor Bramwell

  • Propose new committers for Pharos for review Aric Gardner

  • Talk to Intel, ZTE, BII and ARM lab owners before sending change to move lab info from securedlab to pharos repo Aric Gardner

  • Think about how to automate build server/vPOD configuration Trevor Bramwell Aric Gardner Fatih Degirmenci

  • Follow up the topic regarding defining the test requirements for gating scenarios for the release during Plugfest. David McBride
  • Decide how to handle Pharos/HW Infra documentation - will it be part of Infra space on docs.opnfv.org or something else. julien zhang
  • Move SDF from Octopus repo to Pharos repo. julien zhang
  • Update documents on CI POD requirements Trevor Bramwell

  • Clean up non-active Pharos committers Jack Morgan

Ongoing Items:

  • No labels

5 Comments

  1. Frank Brockners I think it is better the ideas/items go to backlogs directly on JIRA and prioritized there. Keeping them in different places (like confluence, JIRA, etherpad, etc.) will make things harder to track.

    Apart from this, some of the items are already in the backlog so asking people to check JIRA and create items there could reduce the duplication.

     

    1. Fatih Degirmenci - We're on the same page - and JIRA is the right place. I just don't want to lose information when moving to the "clean" way. 
      BTW/ - could you update the filter to show tickets in all projects that carry the INFRA label? That way we also cover Genesis etc. Thanks, Frank

      1. Frank Brockners Updated the filter now and all the JIRA items with INFRA label should be shown in the list. You can click refresh and order by key if GENESIS or other project items do no show up.

        I also sent mail to julien zhang and asked him to put these items to JIRA by passing the link to the version of this page with the ideas he put.

        1. Hi Fatih Degirmenci,

          I have create the JIRA tasks with INFRA label in Releng as you suggested. The content in url(Proposed Improvements) can be deleted. Almost all the tasks and sub-tasks can be done only by admins of Gerrit and JIRA and I just give my suggestions. I also find that Aric Gardner has started to work on some of them.

  2. Hello

    for me, im not sure what has occurred, but it would be good for someone to outline the following:

     

    • why was it necessary to go through and change all the tickets that belong to another lab owner
    • How come the processes that have been established by lab owners were completely disregarded.
    • What is the expectation of time here vs. effort - the point of JIRA is a tool - not the "b all to end all" for INFRA WG.

     

    Seems we are regressing a bit to unilateral actions - we had a large discussion about making work for others withoout having adequate discussion and I fail to see why this all had to be done on Friday?