Open Energy Infrastructure Support¶
Interacting with the OE3 authorization and authentication services as either a consumer or provider of information has some degree of complexity - this library exists to handle these concerns, leaving you to write the business logic without having to manage the details of token management etc.
- Accessing OE Shared Data
- Providing OE Shared Data
- Metadata File Handling
- Deploying a Data Provider to EC2
- Installing Python 3.9
- Installing Nginx
- Installing and configuring Certbot
- Generating key material using the directory
- Installing gunicorn and your Data Provider
- Logging and monitoring
- Running a Data Provider with gunicorn
- Local Data Provider Development Mode
- Python API : ib1.openenergy.support
Open Energy Phase 3¶
For definitive information about the Open Energy project, please visit us at https://energydata.org.uk/ - the information presented here is specific to the functions of this library and will not explain the wider OE3 ecosystem.
Fig. 9 above shows the entire Open Energy ecosystem. This library is limited in scope to two elements of the overall architecture:
The Shared Data API Client held within the Service Provider (SP)
The Shared Data API held within the Data Provider (DP)
Depending on your role in the system, you may need to implement either or both of these in your code.
If you are building an internal or customer facing tool to access, present, or analyse, shared energy data, you would need to access secure data APIs through the first of these. See Accessing OE Shared Data
If you have shared energy data and need to share it with other participants in a secure manner within the ecosystem, you will need to implement an appropriately secured shared data API. See Providing OE Shared Data