| Anonymous | Login | 2024-04-24 00:05 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0017821 | ClearOS | app-base - Base System | public | 2017-11-14 11:16 | 2018-02-26 21:22 | ||||
| Reporter | user2 | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | feature | Reproducibility | have not tried | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 7.4.0 | ||||||||
| Target Version | 7.4.0 Updates | Fixed in Version | 7.4.0 Updates | ||||||
| Summary | 0017821: Add memory usage helper | ||||||||
| Description | In low-memory environments, most apps in the ClearOS Marketplace can either automatically scale or provide a path to programmatically scale (e.g. limiting the number of startup processes in Squid). Containers will require a lot more RAM, so new APIs and tools need to be put in place to manage container-based apps. 1) Apps over the memory limit should be marked as "unavailable" in the Marketplace 2) If apps are installed via command line, the app should show a warning message and auto-start should be disabled. Addendum: we might want to also add compute power detection too. The ClamAV issue described in 0018081 is a good example. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2017-11-14 11:16 | user2 | New Issue | |
| 2017-11-14 12:13 | user2 | Assigned To | => user2 |
| 2017-11-14 12:13 | user2 | Status | new => confirmed |
| 2017-12-05 08:34 | user2 | Description Updated | View Revisions |
| 2018-02-26 21:22 | user2 | Status | confirmed => resolved |
| 2018-02-26 21:22 | user2 | Fixed in Version | => 7.4.0 Updates |
| 2018-02-26 21:22 | user2 | Resolution | open => fixed |
| 2018-02-26 21:22 | user2 | Status | resolved => closed |
|
Issue History |