Sprint 142 Planning: Fabric8 Analytics

[krishnapaparaju]

OSIO Analytics Sprint 142

Sprint Goals

Work towards publishing IDE extensions for OSIO analytics platform (VSCode, DevStudio)

• UX related enhancements for the stack report (Implement the OSIO stack report as per revamped UX #1277)
• Identify performance bottlenecks and publish matrix for OSIO resource requirements based on load testing results (Scale OSIO analytics platform  #1144)
• Deploy 3scale APICast gateway, Update IDE workflow to include 3scale user registration and test IDE workflow end-to-end with 3Scale gateway deployed. (Deploy self hosted 3scale gateway  #1451, VSCode integration with 3scale registration portal #1285)
• List and close all the marketplace related TODOs (icons, READMEs) for publishing IDE extensions ( Items related to publishing VSCode extension to marketplace #1455 )

Analytics recommendations for quick-starter app

• Improve Analytics recommendations for quick starter applications #1471

Testing / Quality related

• Fabric8 Analytics: All the code promotions go thru Dev. cluster #1521
• Run E2E tests against f8a deployments at OSIO #1522
• UI integration tests for F8A platform #1523
• Run E2E tests against fabric8-analytics prod deployment: [3] Run E2E tests against fabric8-analytics prod deployment #1460
  • this is about a subset of our existing E2E tests, UI is not covered by them

Getting started experience

• Continue implementation of the UI code merge work., Add component to ngx-forge #1186
• Integrate the Che files, Consolidate Chefile and Factory redhat-developer/rh-che#402
• Based on feedback Analytics flow to create his/her own application stack #1323, develop 2nd leg for POC for Analytics driven flow

Figure out next steps for operationalising CVE mapping work to individual packages (#1264)

• [3] Design pipeline for mapping new CVEs from NVD to component names #1613

Bugs

• Stack report recommendations show up only for one quick start application #1500
• Incorrect usage outliers show up at stack report #1429
• Stack report: Not displaying recommendations for companion components #1450
• Caused by: java.io.IOException: No space left on device #1298
• Bug: Show the unknown license count for unique unknown licenses in the stack report UI #1147
• PGM scoring fails with OOM error #1490
• fabric8-analytics API server uses half a CPU core even though there is no traffic [prod-preview] #1463

Engineering work

Work on high priority Technical Debt

• Expose workers bookkeeping data: [8] Expose workers bookkeeping data via API #1404
• Able to figure out and sync the delta between OLAP and OLTP stores: Able to figure out and sync the delta between OLAP and OLTP stores #1085

Wrap up service related open items for getting a handle on various operational scenarios, service (#1087)

AWS resources/infra improvements:

• Map AWS resources to staging/dev [5] Mapping of AWS resources to Dev,Stage and production environments #1081

Tests:

• enable/improve E2E tests for ingestion components: [13] Perform integration tests for data ingestion related components of OSIO analytics #1329

Gradle:

• Implement Gradle support in Mercator: [8] Gradle support in mercator #689

[bmicklea]

CVEs continue to be a high priority. Is #1471 actually complete? It looks like all subtasks are done...

In fact it seems several of these are already closed. Perhaps a quick clean-up is needed?

@slemeur is the getting started experience items here part of the work you've been doing with the team? From my perspective the OSIO stack reports, CVEs and a similar experience to start.spring.io (with added analytics) are high priorities. Please discuss the natural language experiment for package building with @slemeur before continuing work there.

[miteshvp]

@bmicklea - We actually increased the scope of #1471 to cover all OSIO quick-starts. Thanks for pointing out, I have added explicitly a line item for the same and we are working towards the same in this sprint (142).

[miteshvp]

Description EDITED - Removed #1427 as it was already covered under previous sprint

[krishnapaparaju]

@bmicklea CVE work is going good, with Maven related CVEs will be in good condition by end of the train. Along with this, will working with SourceClear for improving CVEs for Maven.

[krishnapaparaju]

@bmicklea experiment related to natural language processing is only an experiment. I am working with @slemeur to define the user experience for analytics driven dependencies..

[bmicklea]

Thanks for the responses - is the list in this issue ordered by priority?

[krishnapaparaju]

@bmicklea Except items related to 'Engineering Work', all other work items carry same/high priority. While working towards these high priority items, comfortable to close on these by end of the current train.

[bmicklea]

@sivaavkd going forward perhaps each item referenced in the sprint plan should be proceeded by a checkbox. That way at the end of the sprint when we close the issue the team can "check" each of the items that was completed. This would provide a quick way for PM to understand what was completed and would be a good input into the sprint retrospective.

[sivaavkd]

@bmicklea - ack. I think we have check boxes already in the sprint plan. But I think, we are not checking. Will look into this and talk to team.