[Project Update] Impact Framework

[Sealjay]

Impact Framework

@jmcook1186 GSF PM
@srini1978 of Microsoft - https://github.com/Green-Software-Foundation/carbon-ql
@navveenb of Accenture - https://github.com/Green-Software-Foundation/carbon-ql

[Sealjay]

In #75 WG - @srini1978 mentioned meetings have kicked off for WG, w/Amadeus and others, with all those who expressed interest.
Readme has been reviewed; and identified how we might identify SCI for various types of project, on-prem, managed services, cloud etc.
User stories created, good candidates for minimum lovable product.

[Sealjay]

@Oleg-Zhymolokhov / @srini1978 gave an update in OSS WG:

looking for direction for the project to add value to existing projects. Originally planned for an API for those unfamiliar with SCI calculation to generate SCI score in user-friendly way.
Feedback that a lot of companies are using Cloud Carbon Footprint and other APIs. @jawache gave suggestions for analysing this. 1) use sci-ontology project to drive the scope of the architecture of the application. aka: users build app architecture in SCI-Ontology. @navveenb making examples to provide ability to enter data, and sci-ontology would generate a score from that data. 2) CarbonQL to be an SDK that provides set of modules and applications to use these modules; describe the architecture in code, e.g. VMs in Azure or other cloud.
Looking ahead, and figuring out where CarbonQL will have a sweet spot, looking at integration possibilities. SCI-Ontology has GUI for describing software boundary. Chatting with Amadeus at the moment.

Suggest discussing in GitHub to get input. #79

Filippo from Shell mentioned going through same process; trying to do more than Cloud Carbon Footprint.

[dtoakley-tw]

Update from @srini1978:

Had a demo from SCI Ontology project. High level alignment: build an extendible SDK that can help anyone plug and play model, telemetry of cloud or on prem. First cut: focused on cloud providers. Intent will be to build from bottom up a few model (different data providers: Cloud Carbon Footprint, Etsy, GCP, etc). Goal is for people to provide input parameters and utilize the SKD interfaces, and extend them. This discussion summarizes where the group aligned on: Green-Software-Foundation/if#26

Next Steps: build this design spec, based on the discussion above ^

[dtoakley-tw]

@Oleg-Zhymolokhov update: missed the call this week, but Srini is working on some code snippets. Also investigating two models: Cloud Carbon Footprint and Etsy's approach. Some notes have been prepared.

@srini1978 / @navveenb : if you could share any notes when you have a chance, it would be great. No rush though.

[Sealjay]

Reviewed the CQL design doc with @Oleg-Zhymolokhov ( https://docs.google.com/document/d/1vJKIEMFId5rl81GaWUXBWtyUhALyqJjeMq_ViTtKX1Q/edit#heading=h.dt3dajceouk6 ) - which compared CCF and the Etsy implementation of carbon measurement.

@Oleg-Zhymolokhov Planning to get requirements from @navveenb, working with the SCI Ontology project Python developer/resource.

Query from @Willmish regarding the scope of CarbonQL vs Carbon Aware SDK:
Green-Software-Foundation/if#32

[Sealjay]

Update from @srini1978, WG discussed having identified the two parts we want to build.

1. The interface/application model - to define & build the boundary of the application (to be able to call out the infra components that someone may want to define as part of the software being built (serverless, laptops, etc));
2. The backend piece - the carbon model - no longer an API, but a framework to integrate with any backend model to calculate operational emissions.
   • Standardise the way we call these models - either building, or integrating with existing models
   • So that any customer who wants to understand how to calculate emissions has a standardised interface specification to the backend models

Specification still under review, WG/project team met over the last few weeks to discuss.

@Oleg-Zhymolokhov, @jawache and @Willmish tried to connect; decided to discuss in this forum.

@Sealjay mentioned this might cross over with the real time emissions data spec; tightly coupled projects.

@jawache covered this project, and highlighted the positive nature of the project in how we're treating the project in incubation and identifying the solution.

• Carbon Aware SDK: Clear overlap - original proposal for Carbon Aware SDK was to create an API, which then became an interface/facade pattern to WattTime & ElectricityMap and other data providers.
• CarbonQL: No API, a software interface to other objects, could be files, or other things - a common way to share carbon intensity data. Not yet defined how this will manifest.
  • Hope: A common series of software interfaces for carbon data (as above, the data providers) - and then if that exists, potentially a layer below or consumed from Carbon Aware SDK.

@Willmish confirmed that a standard interface to extract data from various services already built into Carbon Aware SDK - how would this differ from our approach to support a new datasource?

@Willmish shared current process for CA SDK: https://github.com/Green-Software-Foundation/carbon-aware-sdk/blob/dev/docs/architecture/data-sources.md#creating-a-new-data-source

Next steps:

• @Willmish to work through Carbon Aware SDK components on next CarbonQL call to get the learnings from SDK - and whiteboard the components SDK already has.
• Action to add project calls to the Open Source Calendar