===================================
#opnfv-meeting: Octopus weekly call
===================================
Meeting started by ulik at 14:00:14 UTC. The full logs are available at
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-03-30-14.00.log.html
.
Meeting summary
---------------
* agenda bashing (ulik, 14:02:57)
* adding documentation system to the agenda (ulik, 14:03:28)
* release candidate 1 should also be on the agenda (ulik, 14:04:40)
* additional committers (ulik, 14:05:00)
* Bryan Sullivan (bryan_att, 14:05:42)
* Uli asks whether everybody would agree to add Fatih, Iben and Jerry
to the committers (ulik, 14:06:01)
* AGREED: Octopus team agrees that Fatih, Iben and Jerry should be
committers (ulik, 14:07:30)
* gotomeeting link? (rprakash, 14:07:57)
* LINK: https://global.gotomeeting.com/join/150627173 (bryan_att,
14:08:24)
* release candidate 1 (ulik, 14:08:57)
* Fatih clarifies that this Thursday, we only need to do build.
(ulik, 14:10:17)
* This is working fine, so octopus should be fine (ulik, 14:10:44)
* we will verify also with BGS after this meeting. (ulik, 14:11:05)
* can you add me to commiter for octuopus I missed that earlier
(rprakash, 14:11:14)
* Fuel was already running, other installers still missing (ulik,
14:11:41)
* Foreman, OpenSteak and others, the build scripts are still missing.
(ulik, 14:12:20)
* Build resources are needed for different installers (fdegir,
14:13:35)
* Information to connect lab resources to OPNFV LF Jenkins (fdegir,
14:14:28)
* LINK: https://etherpad.opnfv.org/p/octopus (fdegir, 14:14:31)
* look for How to Connect Servers from Labs to OPNFV Jenkin (fdegir,
14:14:40)
* and contact aricg (fdegir, 14:15:10)
* Triggering tests in different labs (ulik, 14:16:25)
* Fatih: update on triggering tests from labs (bryan_att, 14:17:14)
* ... some problems with internet reources being debugged for Intel
lab (bryan_att, 14:17:36)
* ... also issues from other labs (bryan_att, 14:17:58)
* Proposed solution might not work for all the labs as it happened
with Intel lab (fdegir, 14:18:58)
* uli: the more labs we try the better - all Pharos page labs should
try to connect (bryan_att, 14:19:21)
* if this is the case for more labs, we need to get firewall openings
so OPNFV Jenkins master can reach the resources in different labs
(fdegir, 14:19:34)
* Fatih: when we get LF resources we won't have this problem
(bryan_att, 14:20:14)
* ... it will help for R1 at least one running environment
(bryan_att, 14:20:40)
* (?): who is working on the LF hardware? (bryan_att, 14:20:54)
* fatih: Constantin from LF is working on it (bryan_att, 14:21:13)
* aric: they are waiting on a switch; still need some topo info. but
check with constantin (bryan_att, 14:21:40)
* uli: who will provide the info? (bryan_att, 14:21:58)
* peter: the suggestion was to standardize the lab setup topo
(bryan_att, 14:23:03)
* LINK: https://wiki.opnfv.org/pharos/pharos_specification (rprakash,
14:23:22)
* ... last week - currently at the Pharos page the ref platform is
described - public nets are missing; there are three interfaces
(bryan_att, 14:23:45)
* ... plus lights-out net makes four (bryan_att, 14:23:59)
* ... another BGS meeting after this one will continue the discussion
(bryan_att, 14:24:22)
* fatih: we need BGS and LF to address the setup so we have something
for next week (bryan_att, 14:24:42)
* peter: we expect it to be completed soon - tests require a ref
platform agreement (bryan_att, 14:25:29)
* hardware usage (ulik, 14:26:00)
* uli: need more input from BGS (bryan_att, 14:26:18)
* fatih: for fuel we can use docker images but need input for the
others e.g. bare metal or ISOs (bryan_att, 14:26:41)
* ?: foreman team has been working on bare metal (bryan_att,
14:27:38)
* ?: it would be more agile to focus on virtual environments
(bryan_att, 14:28:03)
* uli: we need to revisit this requirement on bare metal vs virtual
(bryan_att, 14:28:36)
* fatih: for R1 bare metal is required at least to verify its working
(bryan_att, 14:29:02)
* some of the stack inputs from BGS to Octopus (CI) like RDO, Juju and
other tracks may bnot be ISO but some artifacts like tar files
(rprakash, 14:29:18)
* ... for the long term we can't run full CI loops for each commit and
test on bare metal, but later we can do so using a virtual
environment (bryan_att, 14:30:02)
* ... for bare metal will have to schedule based upon the installers
being verified (bryan_att, 14:30:49)
* uli: we will revisit for R2 (bryan_att, 14:31:26)
* document repository (ulik, 14:31:57)
* aric: the desired end result is PDFs - IMO not the right way, e.g.
space reqs. I recommend using a markup lang and generate PDFs as an
artifact (bryan_att, 14:33:06)
* Bryan: +1 (bryan_att, 14:33:10)
* fatih: some people said they don't know git etc (bryan_att,
14:33:58)
* bryan: we need to set an expectation that people will use the tools
typical for open soruce (bryan_att, 14:34:46)
* uli: this must be addressed in the documentation group (bryan_att,
14:35:00)
* fatih: how do we handle this, e.g. go to TSC? (bryan_att, 14:35:17)
* uli: until the project is created, we can do it there; in the
meantime in the TSC (bryan_att, 14:35:37)
* bryan: can Octopus make a recommendation as an agreement
(bryan_att, 14:36:26)
* ... the documentation project should assess and support the
consensus of projects rather than dictate (bryan_att, 14:37:16)
* ?: don't want to see word documents - rather latex (bryan_att,
14:37:46)
* bryan: everyone who has an opinion should voice it on the TSC and
list (bryan_att, 14:39:17)
* fatih: can we vote on this now, here? (bryan_att, 14:39:39)
* For Octopus documentation: R1 use markdown, R2 latex (or something
else) (fdegir, 14:40:04)
* ul: it would be good for Octopus to provide an input to the TSC
(bryan_att, 14:41:32)
* to have a project voice to text tool format ? (rprakash, 14:41:39)
* ... anyone speaking against? (bryan_att, 14:41:42)
* david: agree storing a binary artifact is not good - text is better
(bryan_att, 14:42:10)
* AGREED: to give message to tsc for a text based document format
(ulik, 14:42:26)
* uli: we can thus use git for this (bryan_att, 14:42:54)
* frank: will we use markdown for R1? (bryan_att, 14:43:28)
* frank: all should be able to use markdown (bryan_att, 14:43:56)
* For Octopus, we will use markdown for R1 (fdegir, 14:44:24)
* artifact repository (ulik, 14:45:06)
* bala: we can talk to TSC about whether markdown or latex should be
used (bryan_att, 14:45:07)
* LINK: http://artifacts.opnfv.org/ (aricg, 14:45:32)
* fatih: aric helped setup google cloud storage for artifacts
(bryan_att, 14:45:37)
* ... we still have some fine tuning to do (bryan_att, 14:46:03)
* LINK: http://artifacts.opnfv.org/ (ulik, 14:46:17)
* bryan: can we access control this as needed? (bryan_att, 14:46:29)
* aric: we can mark artifacts as private etc (bryan_att, 14:47:16)
* ... we will create a different bucked with specific access controls
(bryan_att, 14:47:38)
* fatih: metadata handling is not good enough with google storage; we
need to address this (bryan_att, 14:48:57)
* uli: if we have a R2 patch ISO needing to be deployed; this will be
in google storage; can jenkins auto-store these? (bryan_att,
14:49:31)
* fatiih: upload/download works fine, but the problem is with metadata
(bryan_att, 14:49:55)
* uli: the deploy script needs to find the right artifact (bryan_att,
14:50:09)
* fatih: we might upload our own metadata file and link it to the
artifact, then extract from the storage when we want to use the
artifact (bryan_att, 14:51:08)
* ... we can put text in both places (bryan_att, 14:51:42)
* ... anyone can join the discussion on #opnfv-octopus (bryan_att,
14:52:17)
Meeting ended at 14:53:26 UTC.
People present (lines said)
---------------------------
* bryan_att (60)
* ulik (22)
* fdegir (10)
* aricg (7)
* collabot (6)
* rprakash (5)
* frankbrockners (4)
* MrSnvn (1)
* fdegit (0)
Generated by `MeetBot`_ 0.1.4