| *** jamesmcarthur has quit IRC | 00:24 | |
| *** jamesmcarthur has joined #openinfralabs | 00:42 | |
| *** jamesmcarthur has quit IRC | 00:49 | |
| *** jamesmcarthur has joined #openinfralabs | 00:50 | |
| *** jamesmcarthur has quit IRC | 00:55 | |
| *** jamesmcarthur has joined #openinfralabs | 01:16 | |
| *** jamesmcarthur has joined #openinfralabs | 01:16 | |
| *** tzumainn has quit IRC | 01:17 | |
| *** jamesmcarthur has quit IRC | 01:21 | |
| *** jamesmcarthur has joined #openinfralabs | 01:24 | |
| *** jamesmcarthur has quit IRC | 01:36 | |
| *** jamesmcarthur has joined #openinfralabs | 01:36 | |
| *** jamesmcarthur has quit IRC | 01:38 | |
| *** jamesmcarthur has joined #openinfralabs | 01:39 | |
| *** jamesmcarthur has quit IRC | 03:09 | |
| *** jamesmcarthur has joined #openinfralabs | 03:10 | |
| *** jamesmcarthur has quit IRC | 03:15 | |
| *** jamesmcarthur has joined #openinfralabs | 03:20 | |
| *** jamesmcarthur has quit IRC | 03:23 | |
| *** sudhir has joined #openinfralabs | 06:18 | |
| *** sudhir has quit IRC | 13:23 | |
| *** tzumainn has joined #openinfralabs | 13:44 | |
| *** etienne has joined #openinfralabs | 14:23 | |
| *** cwawak has joined #openinfralabs | 14:50 | |
| *** cwawak has quit IRC | 15:30 | |
| *** cwawak has joined #openinfralabs | 15:55 | |
| *** cwawak has quit IRC | 15:56 | |
| *** cwawak has joined #openinfralabs | 15:57 | |
| msdisme | fungi: are there limits on how many people may work in an opendev etherpad at the same time? | 16:00 |
|---|---|---|
| fungi | msdisme: if there are, we haven't hit it | 16:01 |
| msdisme | :-) | 16:01 |
| fungi | i mean, there are logical limits where it becomes a too-many-cooks sort of problem | 16:01 |
| fungi | but we've had 100+ people on a single pad in the past, granted most aren't making edits at the same times and are usually editing different areas of the text | 16:02 |
| msdisme | but if 20 people are in the doc and 3 are working on 1 section, a diff. 3 on another, 5 on a third section etc? | 16:02 |
| msdisme | ((I hope we have this problem some day :-)) | 16:02 |
| fungi | yeah, that should work just peachy | 16:02 |
| msdisme | (soon) | 16:02 |
| msdisme | cool! | 16:03 |
| fungi | keep in mind you'll want to export/backup content... it's a little too easy for people to blow stuff away in there and occasionally the timeslider can get confused. we've also seen some browser extensions (especially auto-translation sorts of extensions) go haywire in pads | 16:04 |
| fungi | if you do get a pad into a weird state (not common, but it does happen... it's software and all software has bugs) then just let us know and we have an administrative api and access to its database, as well as daily backups of the data for the server | 16:05 |
| msdisme | Bill and I were thinking to use combination of IRC and an etherpad to "flesh out" stories before taking them to git - do you mean we should do backups every few minutes? | 16:05 |
| fungi | nah, but maybe when you get to certain checkpoints/milestones in your work, you might want to export the page to a local file or just copy/paste stuff from it | 16:06 |
| msdisme | got it | 16:06 |
| fungi | in most cases, if someone does blow content away, you can use the timeslider to look back at a time before that and copy the text from there and paste it back in | 16:06 |
| fungi | but it's not like a revision control system where you can easily revert specific edits | 16:07 |
| msdisme | got it | 16:07 |
| fungi | most people don't, it's rarely an issue, i just tend to be overly cautious (that's probably how i ended up as a sysadmin) | 16:14 |
| * msdisme leifmadsen added some topic areas to https://gitlab.com/open-infrastructure-labs/nerc-architecture/-/issues/4. For an IRC next week focused on Establish an Architecture for the Monitoring Platform: https://gitlab.com/open-infrastructure-labs/nerc-architecture/-/issues/4 Bill and I wanted to get folks feedback on how to make the meeting most effective - our straw person for feedback: | 20:43 | |
| * msdisme | 20:43 | |
| * msdisme In IRC: | 20:43 | |
| * msdisme 1. Have a few high level story subject lines we share - ( I will put the ones Leif added below) | 20:43 | |
| * msdisme 2. Spend 15 minutes of brainstorming for other 1 line subjects | 20:43 | |
| * msdisme 3. Copy those into a shared etherpad and have a few "coordinators" help organize all the thoughts in the etherpad stories and then move them to gitlab stories. | 20:43 | |
| msdisme | Leif's additions: what are the things desired from a monitoring platform? | 20:46 |
| msdisme | *what kind of information is expected (is just metrics enough? what other data types do you require?) | 20:46 |
| msdisme | *what kind of presentation layer is expected? do you just need a dashboard that shows graphs, or do you need more *detailed analysis, and what might that look like if you do? | 20:46 |
| msdisme | *how can the operational knowledge be conveyed? are there a default set of rules that can be provided out of the box as *it were? what defines a "healthy cloud"? what defines a cloud that is degraded? what is the remediation path, such as *alerting a human, or are there systems that can fix the cloud automatically? | 20:46 |
| msdisme | *are closed-loop systems different from monitoring? are they different planes? are they similar but have different scopes? | 20:46 |
| msdisme | *what is the expected resolution of metrics? sub-second? 5 seconds? 30 seconds? minutes? | 20:46 |
| msdisme | I think these may break into a diff epic /stories vs. the "architecture" of what are we running on/where is data collected - like to hear others thoughts. | 20:47 |
| *** tzumainn has quit IRC | 23:03 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!