Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Massive Update - Remove old storage check, add new storage and resource check to all scripts - Remove downscaling with pct set #333

Merged
merged 12 commits into from
Nov 18, 2024

Conversation

MickLesk
Copy link
Member

Description

Massive Update (Remove StorageCheck (old) + Add Ressource & StorageCheck, Remove Whiptail, Remove PCT Ressource Set

Type of change

Please check the relevant option(s):

  • Bug fix (non-breaking change that resolves an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (a fix or feature that would cause existing functionality to change unexpectedly)
  • New script (a fully functional and thoroughly tested script or set of scripts.)

Prerequisites

The following efforts must be made for the PR to be considered. Please check when completed:

  • Self-review performed (I have reviewed my code, ensuring it follows established patterns and conventions)
  • Testing performed (I have tested my changes, ensuring everything works as expected)
  • Documentation updated (I have updated any relevant documentation)

Related Pull Requests / Discussions

If there are other pull requests or discussions related to this change, please link them here:

…eck, Remove Whiptail, Remove PCT Ressource Set
@MickLesk MickLesk requested a review from a team as a code owner November 18, 2024 13:11
@github-actions github-actions bot added the update script A change that updates a script label Nov 18, 2024
@MickLesk MickLesk added enhancement New feature or request breaking change A change that is not backward compatible labels Nov 18, 2024
@remz1337
Copy link
Contributor

Awesome work. I'm supportive of the usage of the new centralized functions (check_ressources). However, can we discuss the PCT set resources? Personnaly, I hate having my LXC overprovisioned. I would prefer to keep that part.

@MickLesk
Copy link
Member Author

Yes we can discuss, but the right thing to do in my opinion would be to make a small fix PR, with proper resources. In the end, Proxmox and the LXC only use what it actually needs :-) if it doesn't need it, it doesn't use it. (Unlike with Homeassistant VM 😂)

havardthom
havardthom previously approved these changes Nov 18, 2024
Copy link
Contributor

@havardthom havardthom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, only comments on moving the functions before app installation and whiptail in some scripts. I tested moving header_info before whiptail in cockpit script locally and it worked fine.
Also have you tested that check_container_storage and check_container_resources works on all supported distributions?

debian 11
debian 12
ubuntu 20.04
ubuntu 22.04
ubuntu 24.04

@MickLesk
Copy link
Member Author

Jep, local it works for Fedora and co too. Thats a later PR. For now only all Debian & Ubuntu Systems

@MickLesk
Copy link
Member Author

@havardthom all done.

havardthom
havardthom previously approved these changes Nov 18, 2024
Co-authored-by: Håvard Gjøby Thom <[email protected]>
@newzealandpaul
Copy link
Contributor

Awesome work. I'm supportive of the usage of the new centralized functions (check_ressources). However, can we discuss the PCT set resources? Personnaly, I hate having my LXC overprovisioned. I would prefer to keep that part.

...

Yes we can discuss, but the right thing to do in my opinion would be to make a small fix PR, with proper resources. In the end, Proxmox and the LXC only use what it actually needs :-) if it doesn't need it, it doesn't use it. (Unlike with Homeassistant VM 😂)

For setups with limited resources, it does make sense to not over-provision. If for example I try a script that ends up consuming a lot more storage when in use (this happened to me a few days ago) I would rather that new LXC crashed, than my long running LXCs.

@newzealandpaul
Copy link
Contributor

Code looks fine and will approve, but I don't think our policy should be over provisioning LXC.

@MickLesk MickLesk merged commit ad18c05 into main Nov 18, 2024
3 checks passed
@havardthom havardthom changed the title Massive Update (Remove StorageCheck (old) + Add Ressource & StorageCheck, Remove Whiptail, Remove PCT Ressource Set Massive Update - Remove old storage check, add new storage and resource check to all scripts - remove resource scaling Nov 18, 2024
@havardthom havardthom changed the title Massive Update - Remove old storage check, add new storage and resource check to all scripts - remove resource scaling Massive Update - Remove old storage check, add new storage and resource check to all scripts - Remove resource scaling Nov 18, 2024
@havardthom havardthom changed the title Massive Update - Remove old storage check, add new storage and resource check to all scripts - Remove resource scaling Massive Update - Remove old storage check, add new storage and resource check to all scripts - Remove downscaling with pct set Nov 18, 2024
@MickLesk MickLesk deleted the feature/storage_ressource_check branch November 18, 2024 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change A change that is not backward compatible enhancement New feature or request update script A change that updates a script
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants