Participants: Etienne, Mark, Emannouil, Johannes, Luigi, Morris, Massimo Sgaravatto, Michaela Lechner, Steve Crouch, Aleksandr, Oxana Agenda: (a) Clarify "unclear" requirements among us and make a quick "yes/no" assessment whether we agree or not. (b) Next telcon (c) Shift of telcon of Thursday (d) AOB continue with unclear requirements 121: Etienne: payload related to anything an activity requires from computing resource Morris: maybe ignoring the payload term Etienne: describing what is wrong inside the computing resource Morris: activity as a container reformulating Steve: understand what he is trying to say Etienne: it is not the application output, it's the app status Steve: define what payload menas here Morris, Etienne: application script or pilot job timeout Morris: somebody voting for "no"? nobody - so "yes" ### 122: Morris: rephrasing somebody "no"? nobody - so "yes" ### 123, 124: rephrasing, including example Emannouil: 123, 124 redundant?! Morris: optional still unclear after 10 min ### 125: changed to "yes" ### 126: changed to "no" ### 128: changed to "yes" ### 133: Oxana: is it really should? rephrasing Michaela: state model should enable the data staging more than a recommendation Morris: reformulated it changed to "no" ### 137: Etienne: problem is about hold points Morris: holdpoints are not directly affected by the application Etienne: not using the word "application" but "activity" Morris: rephrasing clear for everybody? somebody saying "no"? changed to "yes" ### 138: changed to "no" ### 139: Etienne: if "no" for 138, this one should be "no" too changed to "no" ### 140: changed to "no" ### 141: Mark: cannot vote "yes" without further explanation Morris: rephrasing Etienne: exclude ssh from requirements changed to "no" ### 142: Mark: implementation detail so "no" changed to "no" ### 146: Etienne: maybe discuss the next ones before and then mark this as duplicate Oxana: would vote "yes" if there is "ensure" Etienne: remove "e.g. logs" changed to "yes" ### 152: Mark: need to take into account the evolutionary aspects Morris: clear for me Oxana: change "must" to "should" Morris: clear for everybody? somebody saying "no"? changed to "yes" ### 153: Morris: seems to be clear now?! still unclear after 10 min ### 155: Morris, Oxana, Mark, Etienne: rephrasing changed to "no" ### 156: changed to "yes" ### closed next meeting: next week Thrusday usual time -- _ _ _ _ _ _ Johannes Watzl |\/| |\ | |\/| Institut für Informatik / Dept. of CS | | | \| | | Ludwig-Maximilians-Universität München ======= TEAM ======= Oettingenstr. 67, 80538 Munich, Germany Room E 005, Phone +49-89-2180-9162 Munich Network Management Team Email: watzl@nm.ifi.lmu.de Münchner Netz-Management Team http://www.nm.ifi.lmu.de/~watzl