DovOps
commented
4 years ago As mentioned during our call ( #52 ) - I think it would be more interesting in terms of tooling to discuss the 'glue' and self-service workflow automation that teams at FIs are producing to ensure the proper controls are laid down, and some sort of integration with an internal registry of projects or namespaces that have some known lifecycle and association with systems/CIDB, etc. The individual tools that are selected, automated, and orchestrated will constantly change, but the integrations between these tools and internal systems could be an interesting problem to collaborate on - at the very least, share approaches and learnings, etc. What do others think?
mcleo-d
natishalom
Description
This issue has been created to discuss the 'Glue' and 'Self-Service Workflow Automation' that banking teams have produced to ensure proper controls are created and laid down to deliver software whilst adhering to internal banking policy.
The discussion should also include the existence of internal registry integrations where projects and namespaces have a known lifecycle and association with systems, CIDB, etc.
Individual tools that are selected, automated, and orchestrated will constantly change, but the integrations between these tools and internal systems could be an interesting problem to collaborate on, or at the very least, share approaches and learnings, etc.
DevOps Mutualization Meeting Notes
Date and Time : Thursday 30th July @ 1pm ET / 6pm BST - https://github.com/finos/community/issues/52#issuecomment-669343645
Orchestration tools have been created but gluing them together is the interesting part. Tools out of the box also don't give metrics, so they need to be glued together to obtain.
It was added that self service is important so things can be setup in a secure and right way by the team. Self service in cloud is important, especially considering banking is wedded to approval mechanisms and raising multiple tickets for orders.
It was suggested an orchestration engine should be open sourced so external parties can integrate their tools. This way we reach a financial services unified voice. Open sourcing and comparing notes is a valuable conversation.
Also, self services gives the change frequency, regulatory compliance and security needed whilst being super important
The group was asked, is there value having a whirlwind tour of people who represent their current pipeline orchestration over a call? The group agree there is value with many volunteers.
The group was also asked to add vulnerability scanning tools to the discussion topic list as group representatives don't want to roll their own solutions.
The group fed back that we might find many members are following the same principles of DevOps orchestration with some differences. If one bank leads, we can say whether we're the same or different.
The group would like to answer the question of where we've been forced to build bespoke DevOps orchestration solutions and therefore duplicating effort.