- 23 Oct, 2024 6 commits
-
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
requestStart seems to be called on every instance every day. There is no need to call the alarm if nothing changed on the instance
-
Romain Courteaud authored
slapos_cloud: allow recreating a Compute Node even if there is an invalidated node with the same title
-
Romain Courteaud authored
-
Paul Graydon authored
-
- 22 Oct, 2024 1 commit
-
-
Paul Graydon authored
-
- 17 Oct, 2024 23 commits
-
-
Rafael Monnerat authored
Insert suffix on RSS Entry title, to better indicate what is the notification is about. MONITORING was widely used already, so it drops the need for custom entries.
-
Rafael Monnerat authored
-
Rafael Monnerat authored
not monitoring.
-
Rafael Monnerat authored
It is broken, unused, and it is saves no time in general. It is better rely directly on sync to get all information on monitoring, or improve Support Request UI itself.
-
Rafael Monnerat authored
This import Raw/Custom OPML feature is not support anymore on Monitoring app. The sync occur directly from jIO API, so no reason to keep it. The code is also broken and untested in general.
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
-
Rafael Monnerat authored
Overtime, the compute node can fail differently before the administrator take action, create multiple tickets for the same compute node don't help. Whenever you have a ticket for a computer or instance, it is irrelevant to create a second since the unsolved first one is most likely the source of the second one. Fewer tickets increase efficiency, and encourage no ticket pending policy and to resolve the problems.
-
Rafael Monnerat authored
Keep testSlapOSCRMAlarm for regularisation request related alarms Create testSlapOSCRMMonitoringAlarm for tests related to Monitoring ticket creations and so on.
-
Rafael Monnerat authored
Merge into Project_checkMonitoring for launch per-project basis.
-
Rafael Monnerat authored
Refactor the implementation of the alarms: - Search from Project rather them query compute nodes, directly respecting if the project can create tickets - Split ticket creation from messaging introducing *_getReportedErrorDict to calculate the error messages (so we can re-use them) - Merge 2 alarms (for check compute node and check compute software installations) info a single one, so we launch at least half the amount of activities for compute nodes. - Drop the specific alarm and to issue a ticket if the user has an instance on a 'close/forever' compute node - Reimplement SupportRequest_recheckMonitoring Merge SoftwareInstallation_getReportedErrorDict into ComputeNode_getReportedErrorDict: We only check for problems from Compute Node perspective, so we should report only one ticket per time. SupportRequest_recheckMonitoring can guarantee that the compute node don't have other problems while closing the ticket. So, this reduces the scope of checks, for example, if the computer isn't connecting, there is no point in check all software installations inside. Another example is, if multiple software releases are failing we dont need to report each one, since the administrator is informed and create multiple tickets for the same compute node will only spam the administrator.
-
Rafael Monnerat authored
This feature was replaced by "Recheck" Monitoring later on and never used. Since it is broken since the refactoring, it is best to improve "Recheck" and drop this action for good.
-
Rafael Monnerat authored
Drop the action and forms that were not used anymore (and it was not exactly working).
-
Rafael Monnerat authored
Moved jump from slapos_crm Drop tab since this information is duplicated with the jump anyway.
-
Rafael Monnerat authored
It is duplicated with Panel View and InstanceTree_view so it provide no benefit in keeping it
-
Rafael Monnerat authored
-
Rafael Monnerat authored
Moving logic to SoftwareInstallation_hasReportedError allow us reuse the logic on SupportRequest_recheckMonitoring script.
-
Rafael Monnerat authored
Old script not used anywhere
-
Rafael Monnerat authored
Dont use cache to check ticket creation is closed. Use countResults to not require len() over the list.
-
Rafael Monnerat authored
This reverts commit ae35b7bc. Site messages arent used anymore for this purpose, so custom the view is not needed, since Site Messages arent used by any UI and we dont have plans to use anymore.
-
- 11 Oct, 2024 2 commits
-
-
Thomas Gambier authored
2^16 is too big and in many machines, you will have "Argument list too long" error. Actually 2^16-1 is the limit and with the "echo " characters in the beginning, we could do max "2^16 - 6". Using 2^15 is already enough.
-
Jérome Perrin authored
-
- 10 Oct, 2024 6 commits
-
-
Romain Courteaud authored
getMovementHistoryList may return the same event twice.
-
Romain Courteaud authored
erp5_forge is not needed to run the upgrader
-
Romain Courteaud authored
connection_value can also be a list.
-
Romain Courteaud authored
Interact with the support request if possible.
-
Romain Courteaud authored
-
Romain Courteaud authored
-
- 09 Oct, 2024 1 commit
-
-
Carlos Ramos Carreño authored
- Type hints for testcase module are completed. - Type comments (to be compatible with Python 2) have been added to other parts of slapos.core only when necessary to achieve full type checking in the testcase module, with Pyright in strict mode. - Docstrings added/completed for the testcase module. - Source is formatted with ruff. See merge request !693
-
- 04 Oct, 2024 1 commit
-
-
Romain Courteaud authored
erp5_interaction_drop/slapos_crm/slapos_cloud: increate priority of alarms checking all documents without changing them
-