You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 17
Next »
An attempt at capturing the remaining work to (approximately) complete the transition of Fermi software as we approach the end of the original 10-yr mission goal.
Code Development
Item | Description | Who | Deadline | Status | JIRA |
---|
Python 3 | Enable flags for swig | Alex | | IN PROGRESS |
STGEN-181
-
Getting issue details...
STATUS
|
Unit Test Overhaul | Separate flyweight and integration tests. Improve reporting. | | | NOT STARTED | |
| | | | | |
Build Products Production
Item | Description | Who | Deadline | Status | JIRA |
---|
Expose binary artifacts (externals, ST, GR, containers) via https | We need to have an general endpoint for binary artifacts in NFS/GPFS. Some part of that endpoint should be structured so that artifacts can be downloaded according to parameters such as artifact name, artifact version, and architecture. Compilation flags may be another parameter. | Brian | | | |
Organize on-disk representation of artifacts (externals,GR,containers, ST?) | Related to exposing the binary artifacts, we want to organize on-disk artifacts in a similar way, but unpacked in NFS/GPFS. This structure will be replicated to AFS and CVMFS for mounting in via containers, which is optimal for use in the batch system and login nodes. | | | | |
GlastRelease Containers | For GlastRelease, the previous on-disk representation of artifacts (available via cvmfs and afs), coupled with a lightly-modified centos6 container, should be adequate for L1 and simulations to use in production. It may be desired to have a "fat" container built with docker for use. We should get the build process for the lightly-modified centos6 container in Jenkins (a job separate from GR/ST builds) | | | | |
ScienceTools Containers | It's not apparent that we need ScienceTools Singularity container in the same way we want a GR container, though it may be desirable. We probably do want a "fat" docker container which is built via Conda. | | | | |
conda (ScienceTools) - mac builds | fermitools now builds on MacOS Sierra. I'm generating a new tarball for upload to the channel now and will ping everyone once it is ready. Please see the resolved JIRA issue for specifics.~Joe | Alex & Joe | | IN PROGRESS |
STGEN-178
-
Getting issue details...
STATUS
|
conda (ScienceTools) - user test bugs | | Alex & FSSC | | IN PROGRESS |
STGEN-180
-
Getting issue details...
STATUS
|
Mac OS Support
Item | Description | Who | Deadline | Status | JIRA |
---|
set up lease of servers | | | | NOT STARTED | |
| | | | | |
| | | | | |
Using Containers in L1 and Simulations
Item | Description | Who | Deadline | Status | JIRA |
---|
| | | | | |
| | | | | |
| | | | | |
Operating L1 etc
Item | Description | Who | Deadline | Status | JIRA |
---|
cleanup documentation | | TomS, Warren | | IN PROGRESS |
LONE-206
-
Getting issue details...
STATUS
|
L1 GR branch builds | | Heather | | IN PROGRESS | |
Get Jenkins to clean up workspace for new builds | An L1 build may follow a master build and it's not clear what is being rebuilt - some build products are re-used across builds. | Brian | | |
GRINF-87
-
Getting issue details...
STATUS
|
Fill ISOC SVN repository documentation | A lot of the ISOC software is held in a SVN repository. We need documentation on the packages contained there including a description, where it gets install, who maintains it, and whether or not the repository and code in production are synced. | Steve T., Tom S., others? | | |
PIPE-49
-
Getting issue details...
STATUS
|
Documentation