> On 13 Jun 2019, at 17:00, Mark Reynolds <mreynolds@xxxxxxxxxx> wrote: > > > On 6/13/19 4:02 AM, William Brown wrote: >> >>> On 12 Jun 2019, at 17:36, Mark Reynolds <mreynolds@xxxxxxxxxx> wrote: >>> >>> http://www.port389.org/docs/389ds/design/repl-agmt-status-design.html >> >> Looks great! >> >> Instead of "Success" we could use "Healthy" because replication isn't a success/fail, it's a longterm "good/bad" IE healthy/failing state. So perhaps instead of success/warning/error, we have "healthy/delayed/warning/error" instead? Additionally, on warning + error, we log those to error log by default so that an admin can "see" past errors, and when they "resolve" a resolution is also posted to the error log too? > Really there are only three states: working, delayed, and broken. What about: Good, Warning, Error? FYI if this does not get pushed today we will a very important deadline (in fact it will mean all the bugs slated for the next release will be missed!!!!) So I don't want to keep debating "names" for much longer... Look, anything that isn't so ... I dunno. "Single action" focused but conveys that the service is operating as expected. I think good may not be the right term either from an admin point of view. So Healthy/Warning, Operational/Delayed, Green/Amber/Red also works from a monitoring case. >> >> Date is json should be ISO 8601 format instead? >> >> 2019-06-13T07:53:20+00:00 > I will look into this, but we are running our of time as I mentioned above. Maybe I will just drop the date for now... Fair, we can add this later then - after all it's json so we can change it without breaking things. Just as a mild concern, I know that there are RH deadlines to meet, but I don't like that leaking into rushing work upstream :( >> >> I hope this helps! >> >> >>> _______________________________________________ >>> 389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx >>> To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx >>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >>> List Archives: https://lists.fedoraproject.org/archives/list/389-devel@xxxxxxxxxxxxxxxxxxxxxxx >> — >> Sincerely, >> >> William Brown >> >> Senior Software Engineer, 389 Directory Server >> SUSE Labs >> _______________________________________________ >> 389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: https://lists.fedoraproject.org/archives/list/389-devel@xxxxxxxxxxxxxxxxxxxxxxx — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-devel@xxxxxxxxxxxxxxxxxxxxxxx
