Next:
- CEIP-4469
- migrate newrelic off KSI to CSI secrets, terraform is here: https://github.com/elsevier-centraltechnology/tio-terraformcontrol-ce/blob/master/535508023165/newrelic/newrelic-logging.tf
- document the above as blog post
- consider consolidating Kong onto
nri-bundle
- Install Camunda 8 (with Argo? or manually?)
- Demo task list to PPE
- refactor 1.26 migration to take advantage of kubent on inspector
- crtxctl generic JSON renderer
2023-12-20
- dev duty
- issue with laptop battery discharging, esp. when on Zoom
- reported that it says it requires service and ordered replacement
- working with Ashish on capability testing (both ways)
- got PR in for NewRelic tests: https://github.com/elsevier-centraltechnology/cortex-operations/pull/348
2023-12-19
- new relic capability testing, completed platform test
- bit short day
2023-12-18
- run 1.26 readiness report
- retro meeting
2023-12-15
- complete 1.26 readiness report inc. test cleanup, passing and coverage
- discuss Cortex BPM idea with Felipe
2023-12-13 and 14: Vacation
2023-12-12: half day
- tips for personal review: https://nonsolus.elsevier.net/Content/Page/Index/8206f9d7-1f7a-4efd-9f94-8619b890cb41
- check if can extend troubleshoot with kubent -> create tickets
2023-12-11
- review README for KA
- watch videos from Richard
- crtxctl release 0.5.0
- REOL
- principles for vendor selection
- simplify before re-implement
- reuse thru sub-processes
- avoid vendor lock in
- standards based: bpmn, introduce dmn
- interoperability: oracle to camunda is a problem
- same users have multiple task lists
- REST
- HA
- dedidated UI workers?
- open source / low cost
- support required for 3-4B USD
- reports
- workflow video
- at each milestone: send supplier order
- escalation if nearing due date may be of interest
- pattern:
- pre-process, notification, ‘fix’ loops are common
- post-notification task is validation (this is PTS code)
- principles for vendor selection
2023-12-08
- capability test convo w AN
- working on summary table for 1.26 readiness
- BPM call
- xp across
- richard chinn : 22 years on Production Tracking System
- get rid of oracle workflow in favour of Camunda (TBC)
- rakesh: started 2007, aw2 sim. to PTS arch (oracle), apollo, now ppe
- ppe: react + spring boot
- working w sravan and richard
- sravan
- eng lead, started support lead via vtw, apollo
- 2 years on ppe, 7 tears w els
- RC:
define principle for selection
noted tech and lic diffs with 8
tempted by SaaS
months long human workflow
some automation but even then has humans in the loop
existing tightly meshed app and workflow
desire to extract vetical by vertical
predj against vendor lock in, but recognise losing features that way.
desire to build own task list
next steps
install 8 on cortex and get existing workflow onto
Rakesh: main reason to move from Alfresco was cost
2023-12-07: office day
- longish chat about 1.26 report and how to get into advisor:
- kubent inside inspector? check can run as custom collector
- refactor remainder as advisor check
- (A) write up tickets accordingly
2023-12-06: vacation
2023-12-05
per tier, per cluster how much work
2023-12-04
callum / camunda
self-eval: get started
Retro:
- capability testing as tool to understnd and document
- too much fire-fighting leaves no time to prevent need for fire-fighting
- 2024
- eye candy graphs and ‘forcing’ drives partners
- integrate advisor / crtxctl / inspector
- write RFP for desired tool
chat with Callum
oracle
- article production
- issue production
- more or less as-is should be good enough
- journal production?
proposed: 6 week evalof uncustomised rest API to show how fast progress bpm can deliver.
- or graphql inserted between rest and react (bit sceptical of this myself: ‘i can write a better api’)
2023-12-01
- post-creation tasks for rdp-prod and rdp-tooling
- ppe logging truncation call
- complete crtxctl publication workflow
- discuss 1.26 deprecations w FG