*_Updates_* Kasparnet:
* merged michelles gpii-app pull (moving of "exit gpii" to dev mode only) Yay! * Made a fix for GPII-2535 - could use review * Cleaning up the buggy payloads related to MM to prep for PCP (partly rolling back the work i sneaked (snuck?) into GPII-2297 Ale: * Working on https://issues.gpii.net/browse/GPII-2537 * Working on Onboarding/Integration planification for all the APCP timeline. * Preparatory work for moving MiMic into GPII. * Back from vacations :( Alfredo: * Mettings about Cloud scope and planification * Some research about how to deploy Prometheus on a Kubernetes cluster * Solved some issues with the ES cluster Antranig: * Working with Kaspar to remedy problems in the PCP API specification and implementation o Have filed: + https://issues.gpii.net/browse/GPII-2556 + https://issues.gpii.net/browse/GPII-2557 o Currently updating Google Docs https://docs.google.com/document/d/1c7QWlh-CFmkdERja7m0VRby50rySAkAP9eLGNiSlZGE/edit# * Working further with Kaspar to resolve race conditions found during pre-pilots (meeting immediately following this one) Cindy * GPII-2435: Addressing review comments and some refactoring for GPII-2538 * GPII-2538: About to start * Worked with Simon about onboarding Brendan * Review Tony's infusion pull request to add code coverage Giovanni: * GPII-2464 - Got ingress controller to run on AWS but still facing some issues with TLS and Let's Encrypt. Continuing to work on this * GPII-2463 - Investigated how to deploy GlusterFS on Kubernetes. Successfully got a PoC running and deployed GPII components to it. JJ: * Working on GPII-2521. * Learning a lot from GPII, how to create own settings handlers and SR processing. * Talking with Ale and Colin about onboarding and MiMiC. * Asking lots of question Steve, Antranig,Javi and Kasper. Thanks you all. Joseph: o Back from vacation o ProcessReporter (GPII-442) + Merged in master branches from universal, linux, and windows to the three pull requests + Thought of a better way to do the context awareness bits, and modified as such. + All tests pass, pushed, and ready for further review. o DeviceReporter (GPIi-1932, GPII-2395, GPII-2404) reporting the available screen resolutions. + As above, meged master branches from universal, linux, and windows. + Working through merge conflicts with respect to windows display settings handlers (dpi work from Steve Gr. and Javi) + Hope to finish in next couple days, and be ready for review. Justin: * Working on bug fixes for UIO+ work. o Currently investigating GPII-2560 ( https://issues.gpii.net/browse/GPII-2560 ) o Making some tweaks to GPII-2541 ( https://issues.gpii.net/browse/GPII-2541 ) o Also continuing work on making the arrow navigation clickable * Waiting on review for GPII-2501 Kavya: * Done testing official build for pre pilots - No new issues identified * Testing UIO+ web personalization - Identified few issues and discussing with Justin * Retesting few bug fixes for GPII chrome extension * Continue testing Web personalization and also official build on other platforms Michelle: * Back from vacation - getting the GPII-2092 branch working again with the changes in hst. Sandra: * Welcoming Brendan O'Connor to the team; joining Cindy for the implementation of Security requirements. * Y3 planning work for Gregg. * Reviewing resumes for Reliability expert candidates. No strong ones so far. * Working on monthly report for Kate and Gregg. * Lots of follow-ups for Gregg. * Happy to report that my old kittie, who suffered a stroke last week, does not need to be euthanized. Yay. - Congratulations!! Simon: * Doing code review on GPII-2435 * Security and PCP with memory meeting * Helping Justin test UIO+ Chrome extension Steve Grundell * Windows Service (GPII-2338) Brendan: * There is a nearly unbelievable amount of stuff going on. :-) * Who's got the best list of "start here to eat all the documentation as quickly as possible?" o For you, starting here is a page that is slightly less terrible and slightly less horribly out of date than many such wiki pages: https://wiki.gpii.net/w/Security_and_Privacy o You might like to dig up notes (in GPII pads) of recent security/Oauth related meetings + e.g. https://pad.gpii.net/p/discussion-on-auth-documents-kl34nur - sorry this is rather incomprehensible but is a discussion that you might well be interested in - see https://github.com/GPII/universal/pull/519 Tyler: * GPII on Kubernetes on AWS Yuriy: Team (PCP Client) summary: * Broke down the implemented tasks so far and created PRs for them * Had a discussion on how the PCP should work, waiting on more information about the API and on sample responses * Currently focusing on visual tasks *Resources*: * https://wiki.fluidproject.org/display/fluid/Get+Involved * https://wiki.fluidproject.org/display/fluid/IRC+Channel <--- #fluid-work is the main channel o https://botbot.me/freenode/fluid-work/ <--- logs of the architecture team's primary channel for hanging out (fluid-tech exists for esoteric overflow discussions) * http://lists.gpii.net/mailman/listinfo <---- the archictecture list is the most important one * http://docs.fluidproject.org/infusion/development/ <--- infusion documentation * _https://wiki.gpii.net/_ * _https://issues.gpii.net/_ *_Agenda:_* * Getting to know the PCP team better, and directing them to community resources o Yuriy - coordinator o Georgi Todorov, Danail both full-stack developers, experienced with JavaScript frameworks * Integration strategies for the PCP - how will it be integrated into the process architecture? o Sounds like it should be an npm module which is loaded by the gpii-app (Githens) o We might have to use electron-ipc if we do it in-process * Talking about PCP API updates and their requirements * why does CI say the gpii-app passes when the tests fail? oh-oh!!! * https://ci.gpii.net/job/gpii-app-test/67/console * The command: vagrant winrm -c "do.ps1 -c 'npm test'" ends with exit status 0, which means OK for the CI. Despite the last command reports: jq: Failure in fixture file - no tests were queued - FAIL * "Failure in fixture file - no tests were queued" ... no tests were queued.. so everything is fine, no tests failed :) No News Is Good News (?) * why do linux CI tests fail: o https://github.com/GPII/linux/pull/94#issuecomment-324088200 o Due to: Linux CI configured to use 'npm run test ...', but the test scripts are not there, e.g., https://ci.gpii.net/job/linux-unit-tests/79/console -- Kasper Galschiot Markus Lead Research Engineer, Raising the Floor - International, www.raisingthefloor.org
_______________________________________________ Architecture mailing list [email protected] http://lists.gpii.net/mailman/listinfo/architecture
