Collaborate to define the initial common cloud services, first common service taxonomy and top level taxonomy

[mcleo-d]

Description

The following questions and next steps were raised during the Define Cloud Services Taxonomy group call - #7

• What are the common CSPs and CSP service types that should be initially targeted by CCC?
• Propose a taxonomy for the first common service.
  • @mark-rushing proposed an S3 compatible Object Store
• Proposal for the top level of the taxonomies
  • Compute
  • Network
  • Storage
  • etc

@mark-rushing (Citi), @njwilliams (Morgan Stanley), @simonzhangbmo (BMO), Gary Butler (Fidelity) and David Stone (Google) initially agreed to collaborate on this issue.

Please also see GitHub Discussion by @vicenteherrera - #29

cc @eddie-knight (SonaType)

[vicenteherrera]

Please consider me also a collaborator, let me know about next steps for this. My spare time is limited, but I'll try to be able to contribute.

[mcleo-d]

Hey @vicenteherrera 👋🏻

Allow me to introduce you to @mark-rushing who is running the working group from Citi. The group is self organising now, so thank you for putting your hand up.

I will introduce you to the group over email too.

James.

[simonzhangbmo]

Here are my thoughts on the questions:

1. What are the common CSPs and CSP service types that should be initially targeted by CCC?
   CSPs include AWS, Azure, GCP

2. Proposal for the top level of the taxonomies

• Compute
• Network
• Storage
• Containers
• Databases
• Integration
• Analytics
• Machine Learning
• Developer Tools
• Security
• Monitoring
• Management and Governance
• Migration
• Cost and Billing
• ... ...

3. Propose a taxonomy for the first common service.
   @mark-rushing proposed an S3 compatible Object Store ==> agreed
   maybe add one from Compute and one from Network, e.g., Virtual Machine and Network Load Balancer

[smendis-scottlogic]

Please consider me - Sonali Mendis from Scott Logic as a contributor for this.

[eziogas-scottlogic]

Hi all, I too would like to help - Euthyme Ziogas, Scott Logic.

[vicenteherrera]

Hi friends. Regarding the categories Simon Zhang has proposed, I have compiled a spreadsheet with the official categories from AWS, GCP and Azure, and shown how they may match with those. https://docs.google.com/spreadsheets/d/10TP21qAnjnn5TkW1y758oPpjzc4CcyF4UKNCmsnlzps/ It's just an exercise in what people would have to think about when they have to map their cloud provider categories to ours. For example note that officially there is no "Compute" in AWS, but it's an obvious one to have, so don't take this as very important. I may seek a different categorization within AWS for this comparison. In some cases there are more than one category on a cloud provider. In other cases I still haven't looked into what is in fact inside a category to understand if the match is right. Should serverless / functions as a service and pipelines belong to "compute"? (I think so). Maybe when we agree on the categories we should have a phrase that defines and clarifies what each category means. So take it as a WIP and with a grain of salt. You can add or change things if you think they fit (i have another copy) –Vicente Herrera ***@***.*** www.vicenteherrrera.com <https://vicenteherrrera.com> | LinkedIn <http://es.linkedin.com/in/vicenteherrera> | Mastodon @***@***.*** ***@***.***>

…

On Tue, Sep 5, 2023 at 5:25 PM Euthyme Ziogas ***@***.***> wrote: Hi all, I too would like to help - Euthyme Ziogas, Scott Logic. — Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUNFQE25AL3RPM5CZN3GTLXY475DANCNFSM6AAAAAA4GHRAEI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[simonzhangbmo]

@vicenteherrera thank you. Can you please move the Excel sheet to Github? My company's firewall blocks Google Docs :-(

[vicenteherrera]

Sure, here it is:
Finos CCC categories.xlsx

[simonzhangbmo]

@vicenteherrera The sheet works now.
I like the detailed work. Thank you for the big effort. There are some questions for us to discuss in next meeting.

[mark-rushing]

This is really great progress, thanks Vincente!

[dduet66]

Hi I would like to help and be invited to this workstream ( Don Duet / ConcourseLabs / don@concourselabs.com )

[eddie-knight]

What is the first service that we should be working on for validation testing?

[smendis-scottlogic]

Hi I'm Sonali from Scott Logic. This is the summary of the yesterday's meeting wrt Define Cloud Services Taxonomy as I understood.

1. We should look at services on category level not on product level. Eg: Think about databases not specifically RDS (from AWS)
2. Identify similar services. Eg: AWS S3, Blob Storage (Azure), Object Store (GCP)
3. Identify the common controls in those similar services. Eg: controls wrt to life cycle management, versioning, cross AZ replication, etc.
4. Check the objectives of these common controls and how relevant are those when it comes to Fintech
5. How to present the common cloud controls as taxonomy - yet to finalize.

Very much appreciate if someone can jump in to amend, correct or refine the list to capture the full summary of yesterday's meeting :)

[mcleo-d]

What is the first service that we should be working on for validation testing?

Hi @eddie-knight - I have added your question to the CCC GitHub Discussions for the Taxonomy group and wider CCC project to discuss ...

• What is the first service that we should be working on for validation testing? #21

Thanks for raising 👍🏻

James.

[mcleo-d]

@mark-rushing and Team 👋🏻

I have created the agenda for the September 28th working group session if you'd like to add your discussion topics for bringing this work together for review.

• September 28th 2023 Common Cloud Controls - Define Cloud Services Taxonomy #25

Please also note, I have created the following GitHub Discussion to help resolve @eddie-knight's question ...

• Collaborate to define the initial common cloud services, first common service taxonomy and top level taxonomy #15 (comment)

All the best.

James.

[eziogas-scottlogic]

Hi guys, just to follow up what @smendis-scottlogic said - any ideas how to divide this kind of work? For example, N1 people look at category C1 and of these some look at this provider, some at that one, some at yet another?
It seems to me that we risk replicating effort across the board, if we let things just regulate themselves.

@mcleo-d, should this question be posted elsewhere instead?

Cheers,
Euthyme Ziogas, Scott Logic

[mcleo-d]

Hi guys, just to follow up what @smendis-scottlogic said - any ideas how to divide this kind of work? For example, N1 people look at category C1 and of these some look at this provider, some at that one, some at yet another? It seems to me that we risk replicating effort across the board, if we let things just regulate themselves.

@mcleo-d, should this question be posted elsewhere instead?

Cheers, Euthyme Ziogas, Scott Logic

Hey @eziogas-scottlogic

Do you mind adding your question to the GitHub Discussions - https://github.com/finos/common-cloud-controls/discussions

This then allows us to separate the contexts of what needs to be discussed verses what needs to be actioned. We can then break the actions out into GitHub issues.

Feel free to tag me in your Discussion and drop a link here. I'll then add it to the project kanban 👽

How does that sound?

James.

[mcleo-d]

Hi @vicenteherrera

I have raised the following PR that converts your Google Sheet to Markdown so all participants can view and collaborate through Github ... https://docs.google.com/spreadsheets/d/10TP21qAnjnn5TkW1y758oPpjzc4CcyF4UKNCmsnlzps/

• Add Taxonomy as Markdown #39

I suggest we review the taxonomy with @smendis-scottlogic's additions on the next Taxonomy working group call #25

James.

[github-actions]

This issue will be closed as stale in 7 days. Please update this issue if it is still needed.

[github-actions]

Closed as stale. An update may reopen this issue.