14:00:12 <bh526r> #startmeeting Weekly Technical Discussion 157
14:00:12 <collabot> Meeting started Mon Nov  4 14:00:12 2019 UTC.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:12 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00:12 <collabot> The meeting name has been set to 'weekly_technical_discussion_157'
14:00:38 <bh526r> #topic Roll Call
14:00:46 <bh526r> #info Bin Hu
14:01:03 <bh526r> #info Jim Baker
14:01:10 <bh526r> #info Liang Chen
14:01:37 <bh526r> #info Jack Morgan
14:01:53 <bh526r> #info Parker Berberian
14:02:47 <bh526r> #info Al Morton
14:03:09 <bh526r> #info Daniel Balsiger
14:03:24 <bh526r> #info Mike Fix
14:03:37 <bh526r> #info Jiaqiang Zhang
14:05:00 <bh526r> #info Mark Shostak
14:06:26 <bh526r> #topic Hardware Requirement from CNTT-RI
14:06:41 <bh526r> #link https://github.com/cntt-n/CNTT/blob/master/doc/ref_impl/cntt-ri/chapters/chapter04.md
14:07:22 <bh526r> #info Mark S introduced hardware requirements listed in above link
14:09:00 <bh526r> #info Mark S. indicated that it is still work in progress
14:09:22 <bh526r> #info Trevor Cooper
14:10:03 <trevor_intel> #info Trevor Cooper
14:14:24 <bh526r> #info The scope is primarily "functional"
14:14:53 <bh526r> #info "Scalability" needs scales of servers
14:17:27 <bh526r> #info And lots of forward-looking work
14:25:19 <bh526r> #info Trevor C asked where the number 14 came from
14:25:51 <bh526r> #info Mark S explained it was created based on functional requirement at very high level we need to address
14:26:10 <bh526r> #info 2 nodes per instance type, 3 controllers, quite conservation
14:26:46 <bh526r> #info "conservative" instead of "conservation"
14:27:33 <bh526r> #info Trevor C. said typical Pharos is 6 nodes: 3 controllers for HA, 2 compute and 1 jump server
14:31:27 <bh526r> #info Jack M asked if we need to do it in phases
14:32:32 <bh526r> #info Mark S said that we need discussion, and it is just an input and work in progress
14:33:26 <bh526r> #info Trevor C asked how to organize the community to get the work done
14:36:21 <bh526r> #info Jack M. LaaS v.s. Static is just deployment methodology. We need to understand the hardware requirement. Pharos specs only says 6 servers
14:40:34 <bh526r> #info Cedric Ollivier
14:40:52 <bh526r> #info Sridhar Rao
14:41:01 <bh526r> #info Trevor Bramwell
14:42:22 <bh526r> #info Bin asked if "6" number in Pharos is architecturally and technically limited, or is it just a matter of funding
14:43:16 <bh526r> #info Jack M clarified we picked number "6" because of OpenStack setup, and architecturally and technically it can scale to any number
14:44:27 <bh526r> #info Ollivier also indicated that in FuncTest, it can also divide into 3 server setup etc., so the number of servers should be technically supported, and flexible.
14:51:19 <bh526r> #info Bin summarized that we can do it in parallel:
14:52:03 <bh526r> #info CNTT clarify the rationale of the number of servers, i.e. why 14 is needed and what is really the minimum number
14:53:13 <bh526r> #info Jack specifies the scalability in Pharos next evolution
14:53:51 <bh526r> #info Jack M suggested that CNTT specifies what is needed for Iruya, J and K releases.
14:54:52 <bh526r> #info Pierre Lynch
14:59:42 <bh526r> #topic AOB
14:59:51 <bh526r> #info None. Meeting adjourned
14:59:55 <bh526r> #endmeeting