Hello all,
As some people watching GitHub closely might have noticed, the majority
of proposed changes (for primary/secondary in the end) were merged around
weekend. This impacts text documentation and keyword support for upsmon
configuration, testing welcome :)
Some work remains for image files in documentation, and the protocol/ABI
were not touched so far.
Following the recent eminent emergence of Religiously Correct Speech
zealots, while at this, we like other projects should also contemplate
supporting as aliases or even primary key words a dichotomy of a
"shepherd"
and (some) "sheep" in this context, that might make intuitive sense.
Happy holidays and thanks for voting,
Jim Klimov
On Sun, Mar 21, 2021, 19:29 Dan Langille <dan at langille.org> wrote:
> Thank you. I think you've handled this well.
>
> On Sun, Mar 21, 2021, at 2:01 PM, Jim Klimov via Nut-upsuser wrote:
>
> Some more replies trickled in, a few seemingly trolling in the
"Other"
> field (no, "servant" is not a good replacement for
"slave" today), and
> others cementing the victory of the modest and reasonable
> "primary/secondary" pair.
>
> I will amend the wordings in prepared PRs that tentatively used
> "manager/subordinate" as the replacement (which did come in
second in the
> poll) but otherwise intend to keep the changes proposed earlier and merge
> when I'm done. Last call for comments, "bar is closing in 15
minutes" ;)
>
> https://github.com/networkupstools/nut/pull/989
> https://github.com/networkupstools/nut/pull/990
> https://github.com/networkupstools/nut/pull/991
> https://github.com/networkupstools/nut/pull/992
>
> Thanks to all,
> Jim Klimov
>
>
> On Thu, Mar 18, 2021 at 3:25 PM Jim Klimov <jimklimov at gmail.com>
wrote:
>
> So, for the past couple of days the SurveyMonkey results are not changing,
> with 13 replies overall. Should we wait for more or everyone passionate
> enough has already spoken? In practice I'd likely follow up on a
weekend
> anyway, but... the weekend is coming! :)
>
> Currently we have a clear leader pair that collected almost half the votes
> (6), two votes were to keep old words in place - alas, nowadays doing
> nothing (and breaking nothing) does not seem to be a viable option.
>
> Also reminding that there are PRs open for the docs/comments changes, some
> closely related to this subject (#992 along with code) and some bystanders
> that "fell under a hot hand" (#989, 990, 991) - feel free to
review the
> proposals if they make sense or should be improved ;)
>
> Thanks to all,
> Jim
>
> On Sat, Mar 13, 2021, 13:41 Jim Klimov <jimklimov+nut at gmail.com>
wrote:
>
> Thank you for the suggestions, keep them coming :)
>
> To me, I think I considered pub-sub but it did not quite fit - gotta
> refresh my memory by code re-reading (or expert comments) - I found I'm
> vague now on who hits the big red button to shout that a particular power
> source device got critical - the upsmon in "master" role, or
"upsd" that
> talks to all subscribed (indeed!) upsmon's and just some choose to stop
> asap (if they won't have enough PSUs powered) and others wait for them
to
> pull the plug on UPS afterwards :)
>
> So if in a way upsd is a message broker between many clients actively
> emitting commands, pub-sub is an option. If upsd emits messages differently
> based on roles of registered clients - not so much.
>
> Note also that there technically can be multiple machines with connections
> and ability to bring the UPS down (or several UPSes) and perhaps configured
> so for redundancy, so in general case it is neither a 1:1 nor 1:many
> relationship.
>
> Jim
>
> On Sat, Mar 13, 2021, 05:05 Douglas Parsons <doug at
parsonsemail.com> wrote:
>
> There is,
>
> https://en.m.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern
>
> I said I stayed away from it because of the Cisco link. Others as well as
> you are free to persue it. I was just making suggestions.
>
>
>
>
> On Fri, Mar 12, 2021, 10:43 PM Baker, Lawrence M <baker at usgs.gov>
wrote:
>
> That is terminology from Computer Science. (Decades ago?) It is
> familiar. Not invented by Cisco. As in, producer-consumer, from the same
> time. Those were all different paradigms for client-server relationships.
> There must be Wikipedia citations that can be consulted. As I recall,
> there were distinctions, such as, producer-consumer were tightly bound,
> where the producer had no purpose without a consumer. In
> publisher-subscriber, subscribers registered their interest in what the
> publisher had to say, but were neither required to exist at all, or might
> ignore what was being published.
>
>
> Larry Baker
> US Geological Survey
> 650-329-5608
> baker at usgs.gov
>
>
> On Mar 12 2021, at 7:22:35 PM, Douglas Parsons <doug at
parsonsemail.com>
> wrote:
>
> I didn't go there due to its use by Cisco.
>
> On Fri, Mar 12, 2021, 10:03 PM Baker, Lawrence M via Nut-upsuser <
> nut-upsuser at alioth-lists.debian.net> wrote:
>
> Jim,
>
> The terminology I recall for that one-to-many relationship is
> publisher-subscriber.
>
> Larry Baker
> US Geological Survey
> 650-329-5608
> baker at usgs.gov
>
>
> On Mar 12 2021, at 6:24:38 PM, Phil Stracchino via Nut-upsuser <
> nut-upsuser at alioth-lists.debian.net> wrote:
>
>
>
> This email has been received from outside of DOI - Use caution before
> clicking on links, opening attachments, or responding.
>
>
>
> On 3/12/21 9:14 PM, Rusty Bower wrote:
>
> Manager/subscriber seems most accurate
>
> Sent from my iPhone
>
>
> On Mar 12, 2021, at 20:13, Douglas Parsons <doug at parsonsemail.com>
wrote:
>
> ?
> In place of secondary how about subscriber? It would be accurate to
> the role.
>
>
>
> I'd been going to suggest controller and ... something. Controller and
> subscriber?
>
>
> --
> Phil Stracchino
> Babylon Communications
> phils at caerllewys.net
> phil at co.ordinate.org
> Landline: +1.603.293.8485
> Mobile: +1.603.998.6958
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
>
>
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Falioth-lists.debian.net%2Fcgi-bin%2Fmailman%2Flistinfo%2Fnut-upsuser&data=04%7C01%7Cbaker%40usgs.gov%7C02f93786357b4c8628c808d8e5c99173%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637512001184607208%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aR0FjsOcr6yUjWZzRIKVSLlhF%2BDXVn%2F84CZ4%2Br3Dvqo%3D&reserved=0
>
<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Falioth-lists.debian.net%2Fcgi-bin%2Fmailman%2Flistinfo%2Fnut-upsuser&data=04%7C01%7Cbaker%40usgs.gov%7Cb01ce3a796ae4eac503b08d8e5cf4b28%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637512025774162066%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=BUrriooegO%2BufxvgamwuSSYbbACoc4R5Bn4W2N7qaFs%3D&reserved=0>
>
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Falioth-lists.debian.net%2Fcgi-bin%2Fmailman%2Flistinfo%2Fnut-upsuser&data=04%7C01%7Cbaker%40usgs.gov%7Cb01ce3a796ae4eac503b08d8e5cf4b28%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637512025774162066%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=BUrriooegO%2BufxvgamwuSSYbbACoc4R5Bn4W2N7qaFs%3D&reserved=0>
>
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
>
> --
> Dan Langille
> dan at langille.org
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20210401/699bdfc4/attachment.htm>
