Cleanup

[jbadeau]

Hello,

We are currently in the process of using Hygieia at our organization but we have found the state of the repositories insufficient for our use. In general what we like is:

• simple approach to collect data
• many collectors

What we don't like:

• unclear of roadmap (e.g. spring-boot 2 version seem inactive)
• hard to find a combination of components that work together
• Some bad quality in the code base (not everywhere)
• Poor modularization in the new UI
• no Cloud support
• Poor documentation in some areas

Therefore we have started refactoring the entire codebase to:

Done

• moved to monorepo
• 1 parent pom based on spring 1.5.22.RELEASE
• helm charts
• helmfile for complete deployment
• migrated angular codebase to nx
• moved from jasmine to jest
• moved from protractor to cypress
• extracted out npm modules from app

In progress

• upgrade to spring boot 2.4.1
• add readiness and liveness probes
• adapt spring properties to be easier to manage with kubernetes
• upgrade to angular 11
• remove ts any
• move to API first (design apis in swagger first then generate server/client stubs)
• move all issues to monorepo
• provide independent versioning of modules in monorepo
• maintain a CHANGELOG
• deprecate all unused repos
• have an public hygieia instance running in a cloud that monitors hygieia itself (good for demos and own improvements)
• create a document project for all modules

Future

• Deployment Frequency widget- How often an organization successfully releases to production
• Lead Time for Changes widget - The amount of time it takes a commit to get into production
• Change Failure Rate widget - The percentage of deployments causing a failure in production
• Time to Restore Service widget- How long it takes an organization to recover from a failure in production
• Deployment view widget - Similar to https://codefresh.io/devops/launching-future-devops-gitops-2-0

We originally were going to fork hygieia but though that it prob makes more sense to merge it back. If your interested, I would like to setup a video call so we can show what we have and if it makes sense to merge back?

I believe that hygieia has allot of potential but the currents state of the project is severely limiting its adoption and growth.

[rvema]

I would love to catchup with you and speak about the mentioned points. Let me ping you in gitter

[jbadeau]

I just downloaded gitter and registered with github. Fl free to ping me and lets try to setup a fave to face if possible.

[rvema]

Can you ping me @rvema on gitter?

[jbadeau]

Ill ping you tomorrow (monday)

[rvema]

@jbadeau we moved away from Mono repo for maintenance purposes. Several teams maintain the repositories hence each component resides in their own repo. The upgrade to Springboot 2.4 will resume shortly in Q1 2021 . We can definitely have a call mid January 2021 to discuss about the changes. We definitely like the helm chart idea and would love to get it contributed back.

[jbadeau]

Hi,

Sure, currently we are moving to a ployglot monorepo using NRWL NX with independent versioning as we find it much easier to maintain even with multiple teams.

[jbadeau]

Just let me know when you would like to see what we have.

[VivekBuzruk]

Will also be keen to understand more about NRWL NX based polyglot monorepo approach. Once you achieve a major milestone, appreciate if you can share a video on your approach & benefits.

Btw. I find that you are addressing lot of Technical Debt as part of multirepo => polyglot monorepo restructuring. So, in parallel, Is it possible to create forks in current multi-repo structure and accept relevant / applicable changes? This will accelerate Hygieia's plan to address multiple Technical Debt issues.

[jbadeau]

Hi,

What about an MS teams meeting this week to go over what we have done (internal repo)? Just send me a time that's good and i'll set it up.

• cloud support
• monorepo
• spring version unification
• cicd pipeline

Near Future:

• new deploy widget (based on kubernetes deplyoments)
• reference project (have a public instance of hygieia which monitors the hygieia project itself)
• documentation project using gatsby

Future:

• model resources after OSLC domains to take advantage of standardized resources and their links.
• Move to an event based architecture

[VivekBuzruk]

OSLC & RDF is a good idea. As per my earlier understanding / experience of OSLC (as part of Rational Team Concert / Jazz), may require few fundamental changes to Hygieia (Schema .... Architecture). Need to understand use cases and benefits.

Rest can be better answered by @rvema.

[jbadeau]

@rvema I pinged you in gitter so that we can setup a meeting.

[kennethlong]

Hi all, did anything ever come of this? I am interested in all of the things Jose's team has been working on. Jose, I sent you a message directly on gitter.