API-server deployment updates and memory limits, off-grid, heating loads and ExistingBoiler, emissions/RE, validator fixes, urls fixes#353
Conversation
Added classes for boiler, existingboiler, spaceheating
data model updated to accept inputs for ExistingBoiler, Boiler and SpaceHeating keys
added and updated the input and output models for boiler, existingboiler and spaceheatinginputs. updated the migration files to remain in line with master branch
update the scalar to vec function to handle 12 month fuel costs, which causes issues with cross-clean downstream
Manifest.toml file now points to REopt.jl#newboiler
This reverts commit 187fe93.
Consolidate tests in single test scenario
update PV validation to happen only if PV key is provided.
update manifest to point to newboiler reopt.jl branch
Fix a bug in solar PV validation and update TOML files to point to REopt.jl#develop, where emissions code exists until REopt.jl v0.17.0 is ready.
Existingboiler and spaceheating
add v2/outagesimjob and v2/ghpghx urls
hdunham
changed the title
zolanaj
changed the title
This reverts commit f4e672c.
The staging and production clusters are now on a newer version of k8s, so this requires the same configuration we previously only applied in development. We can now remove this as a configurable flag and conditional and just make it the same everywhere.
|
@Bill-Becker: The staging and production cluster appear to be fixed by ITS now, so I was able to deploy successfully to staging (after a small tweak due to the newer version of k8s they're now running: 2e2901e). So if you wall want to review anything there or test any other staging/production deploys, I think things should finally be back in action. |
|
@GUI Great news! I know Rancher was going to do a reboot of the cluster at 5pm yesterday, and then their platform engineering support was available to help - it would be good to at least understand the high level cause and fix, so we're more informed next time. |
|
@hdunham The deployment stuff seems to be working, so let's work toward merging this. It looks like you made a lot of the updates to the Changelog - let me know if that is all set or we need to add more (the TODO is still in the description). |
|
@hdunham Can you prioritize this since it should just be adding any additional changes to the CHANGELOG.md, and then we can get these server memory improvements on production? |
@Bill-Becker I'd finished making changed and approved the PR, the TODO was just meant to be a reminder for you to change "Develop" to the next version # right before merging. But I went ahead and did that just now, and I also removed both TODOs since you said you deployed successfully as well. |
make all stable/ urls also available from v2/
7 participants
This PR includes: