-
Notifications
You must be signed in to change notification settings - Fork 23
2015 09 24
Andre Merzky edited this page Oct 1, 2015
·
9 revisions
-
Agenda:
-
open TODOs:
- WIP IP: anaconda support on client side?
- IP: start a new branch
- MS: possibly start with a static ve?
- DONE VB: check if anaconda support is needed by Justin: NO
- TODO MT: add allocation info to resource doc
-
- HOLD AM/MS: prepare action/support plan for activities on BW
- objectives, challenges, timelines, phase 1
- HOLD AM: check if we can switch to HeartbeatMonitor for pilot health checks
- HOLD AM: suggest alternatives for PTY layer resource consumption
- HOLD MS: Anaconda/SuperMUC (October)
- HOLD MS: add NAMD examples eventually? (Tom Bishop)
- HOLD AM: set up example on how to use synapse as RP workload
- HOLD AM: check documentation of state diagram in released docs
- HOLD MT: move semantic elements of tools into RP.utils
- HOLD AM: proposal to json export to persistent storage
- HOLD MS: proposal for persistent experimental data storage
- WIP IP: anaconda support on client side?
-
Development Progress:
- release plan:
- 0.36: mid September
- 1 week merging of branches (agent split, profiling)
- 1 week of testing
- -> delayed: 2 week
- WIP: start tutorial preps in parallel
- 0.37: this week
- documentation, examples, tutorials
- TODO AM: merge, reorg
- -> as planned
- 0.38: end October
- module refactor
- final state model
- -> as planned
- 0.36: mid September
- testing:
- TODO AT:
- move to RADICAL-Jenkins (with one fixture)
- TODO AT: get stable (red or blue)
- TODO AM: look into mail notifications
- TODO AT:
- Yarn:
- TODO IP: toward dynamic multi node (lower priority)
- TODO AM: daemon startup over LMs?
- DONE IP: chameleon work
- TODO IP: pull request for launcher...
- Spark
- HOLD GC: compare to Yarn integration
- BW:
- "one more fix"
- MPI regression on OpenMPI layer is fixed
- regression on clean agent termination is fixed
- also fixes some module termination issues
- TODO AM: prepare RC right now
- Matteo has access now.
- State of application kernels?
- CECAM
- Agenda
- Documentation Tickets
- which is the target env for installation?
- workflow.iu.edu -> 50 tutorial account
- TODO SJ: clarify account usage and XSEDE allocation
- same accounts for Extasy
- TODO AM: pre/post exec: not after application error
- TODO AM: how is RTD to be synced to devel
- conceptual section is missing
- what problem do we address?
- what is a pilot?
- what is a CU?
- what is this MongoDB thing?
- how do I know what goes on in the pilot? With my CUs?
- what is a scheduler? Why are there multiple schedulers?
- how about data?
- TODO AM: create that structure
- ordering
- there is no single 'good order'
- examples and best practices are different, as is the tutorial
- should the tutorial separated out in the first place?
- rename this document to 'user guide'
- SJ: user guide is pre-requisite for tutorial
- no need to have release nodes in this doc
- Intro: SJ
- install: VB
- branch, some changes,
- TODO VB/AM: add ssh-config
- resources: MT
- TODO SJ: review after
- TODO: link auth links from (II) into that section
- data: AT
- links should be clickable
- move callbacks elsewhere? Most basic examples start with those...
- data examples are on localhost only. Uhm.
- AM: split into concepts and examples? Lets see after concepts are in place
- examples: MS
- getting started needs to go much earlier
- merge 5.2 (error handling) with 5.7 (app flow)
- axe 5.3 (reconnect)
- 5.4 should be merged into resource section
- 5.5: is more an FAQ - move it there?
- add pre/post exec discussion
- 5.6 (MPI) sooner and implicit?
- tutorial: AM
- TODO VB: next Thu: switch from RP testing to ENMD testing protocol
- TODO AT: next Thu: draft user guide, two weeks: testing protocol
- TODO SJ: review of docs by Software institute? (Neil)
- TODO AGENDA: RTD procedures
- TODO AGENDA: where go user credentials? context vs. user pilot description.
- release plan:
- Data Roadmap:
-
Experiments:
- HOLD: micro vs. macro benchmarks
- HOLD: profile status
- Publications:
-
AOB:
- CECAM Tutorial
- online documentation vs. online tutorial
- begin to work on interactive examples (which involve user activity)
- how to submit n tasks of size A and m tasks of size B, toward hosts X and Y
- TODO AT: simple repex example
- TODO AT: check with SJ about suitable example / exercise mode
- TODO VB: simple MD example
- TODO AM: simple RP example
- execution env, software stack, applications/libraries
- WIP AM: assign
documentation
tickets
- SC15 Tutorial
- CECAM Tutorial
-
open TODOs:
- Notes: *