Releases: Boavizta/boaviztapi
v0.3.0-alpha2
Testing the release action see #184
v0.3.0-alpha
An alpha release of the future API v0.3.0.
⚠ Although stable, this alpha release should be used for testing purposes.
It contains Work In Progress, and introduces breaking changes in the format of the data returned compared to the v0.2.x API.
See https://dev.doc.api.boavizta.org/release_notes/
What's Changed
- Cpu die size per core complete update by @da-ekchajzer in #148
- Implementation of the concepts of warning and margin of error by @da-ekchajzer in #149
- adding get all names utils router + correcting cloud utils routers by @da-ekchajzer in #158
- Perimeter improvment : New imapcts criteria and new equipements by @da-ekchajzer in #159
- V0.3 by @da-ekchajzer in #160
- fixing format in user terminal archetype by @da-ekchajzer in #161
- Create cpu_specs_raw_techpowerup.csv by @csauge in #162
- Create cpu_specs_final_techpowerup.csv by @csauge in #163
- Update cpu_specs_final_techpowerup.csv by @csauge in #165
- Fix dev server launch on Windows by @dorev in #166
- Update cpu_specs_final_techpowerup.csv by @csauge in #167
- Update cpu_specs_final_techpowerup.csv by @csauge in #168
- add first version of thefuzz by @csauge in #170
- Fix issues in fuzzymatch by @csauge in #172
- V0.3 by @da-ekchajzer in #173
- Dev by @da-ekchajzer in #174
- Dev by @da-ekchajzer in #175
- Dev by @da-ekchajzer in #176
- adding all_categories router to user terminal by @da-ekchajzer in #177
- Test/cloud instance issue 178 by @da-ekchajzer in #179
- Dev by @da-ekchajzer in #180
New Contributors
Full Changelog: v0.2.2...v0.3.0-alpha
Contributors
Assets 2
v0.2.2
What's Changed
- Change CPU manufacturing impact formula by @samuelrince in #142
- reduce docker image size using distroless by @AirLoren in #141
- Modify cloud route to allow multiple cloud providers by @AirLoren in #139
New Contributors
Full Changelog: v0.2.1...v0.2.2
Contributors
Assets 2
v0.2.0
Goal
v0.2 contains significant changes to the code to facilitate the addition of new features. The main additional functionality is the ability to model the power consumption of certain components, servers and cloud instances from their configuration.
Improvements
- Implementing linear allocation for manufacturing impacts
- Implementing fuzzy matching for string fields
- Model electrical consumption from technical characteristics and usage context for CPU, RAM, Server and Cloud instance
- Complete CPU info from CPU name
- Adding source, units and status for each attributes in verbose mode
- Adding utils routers (list available data for string fields)
- Storing all data in CSV format
- Ease the deployment of API as a serverless application
- Documentation improvements
- Improving CORS settings
- Adding new AWS EC2 instances
Issues
Bug fix
Known future requirements
- Mobile and fix network impacts
- Screen impacts
- Workplace impacts
- IoT impacts
- Generalize AWS process to other cloud providers
- GPU impacts
- Add multiple impact factors for semiconductors
- Add multiple impacts factors for impacts related to electricity
Documentation
v0.2.0-alpha
adapting setup.py for v0.2a
V0.1.2
Bug
missing W to kW conversion
hour_electical_consumption should be given in Watt.
When hours_electrical_consumption was directly given (in watt) the value was used in Wh. The electrical impacts factor requires kWh.
Correction
Adding conversion from W to kW ( / 1000) when hour_electical_consumption is used with an electrical impact factor.
PR
V0.1.1
Goal
The V0.1.1 adds new CPU data and electrical impact factors.
Improvement
- Adding new CPUs
- Implement PE and ADP impact for use phase
- Improvement of gwp impacts factor quality
Issues
Known future requirements
- Mobile and fix network impacts
- Screen impacts
- Workplace impacts
- IoT impacts
- Generalize AWS process to other cloud providers
Dev server
API : http://api.boavizta.org:5000
DOC : http://api.boavizta.org
V0.1.0
Goal
The V0.1.0 introduces the notions of archetypes, verbose and units. An implementation of AWS instances impacts have been implemented. Impact of usage have also been developed.
Functionalities
- Retrieve the impacts of AWS instances
- Retrieve the impacts of server archtypes
- Retrieve usage imapcts (GWP only) of usage
- Verbose option
- Bug fix
- Work on documentation
Issues
Known future requirements
- Mobile and fix network impacts
- Screen impacts
- Workplace impacts
- IoT impacts
- Generalize AWS process to other cloud providers
Dev server
API : http://api.boavizta.org:5000
DOC : http://api.boavizta.org
V0
Goal
The V0 is the MVP of Boavizta tools api.
It aims at giving access to the server bottom-up methodology measuring the scope 3 of servers explain in this article :
Project setup
- Setup python project (fastAPI)
- Setup project test (pytest)
- Setup project documentation (mkdocs)
- Setup CI/CD (gitworkflow - git repository)
- Creation of the theoretical architecture
Functionalities
- Retrieve the manufacture impact of components from its characteristics
- Retrieve the manufacture impact of servers from its characteristics with the bottom-up methodology
- Complete the server or component characteristic if incomplete data are sent by the user
Issues
Known future requirements
- Bug fix
- Returns a verbose object (hypothesis, modify datas, calculation steps)
- Integrate Boavizta database
- Implement new devices
- Support use case implementations
- Implement scope 1 & 2
Dev server
API : http://149.202.185.115:5000
DOC : http://149.202.185.115