From lars at redhat.com Wed Apr 1 20:58:07 2020 From: lars at redhat.com (Lars Kellogg-Stedman) Date: Wed, 1 Apr 2020 16:58:07 -0400 Subject: [Openinfralabs] openinfralabs.org repo In-Reply-To: <5E7E5BD5.4030200@openstack.org> References: <1e9ed58b-2161-0362-bfbd-4ae0012ed6e9@bu.edu> <5E7E5BD5.4030200@openstack.org> Message-ID: <20200401205807.gb6zpomhtnvmaped@redhat.com> On Fri, Mar 27, 2020 at 03:02:29PM -0500, Jimmy McArthur wrote: > Thanks Michael! Can you give a brief overview of what your longterm > vision for the site is? I know there has been some discussion of a > possible blog, for example. How else would you see the site > growing? I think we should definitely plan on some sort of blog feature, since we'll probably want a place to post updates as various part of the project progress. I would vote for something of the "drop a markdown file into the correct folder" variety. > Wherever you want to repo to live is fine, but I'd like to make sure it > works with Netlify and our development team has access to help you manage > the back end. Additionally, our marketing team does a fair amount of the > updates via the Netlify CMS, so ensuring that's accessible and available for > those folks is important as well. I don't think we have a strong set of requirements at this point. Speaking almost exclusively for myself, because I haven't had the chance to touch base with anyone on this topic, I would prefer that: - The website lives alongside any other repositories we're maintaining. - Changes to the website going through a CI and review process. - The website can be rendered using open source tooling through a CI pipeline associated with the repository. I don't know what sort of workflow you folks have around the site right but, but if it's not terribly complicated it would be great to move the site sources over to https://gitlab.com/open-infrastructure-labs/openinfralabs-website, since this is where we'll be hosting other things. Hopefully Michael at least can chime in on this to confirm that I have not making things up. -- Lars Kellogg-Stedman | larsks @ {irc,twitter,github} http://blog.oddbit.com/ | N1LKS From lars at redhat.com Thu Apr 2 16:06:31 2020 From: lars at redhat.com (Lars Kellogg-Stedman) Date: Thu, 2 Apr 2020 12:06:31 -0400 Subject: [Openinfralabs] Gitlab group available Message-ID: <20200402160631.p3mi7oalekp3z26j@redhat.com> Hey folks, We've established a presence on Gitlab at https://gitlab.com/open-infrastructure-labs. There's nothing there at the moment, although we hope to have some folks from Red Hat contributing something Real Soon Now. There is a copy of the openinfralabs.org website repository there, but at the moment this isn't the official source of the site. We're working on getting things moved around. -- Lars Kellogg-Stedman | larsks @ {irc,twitter,github} http://blog.oddbit.com/ | N1LKS From lars at redhat.com Thu Apr 2 20:50:59 2020 From: lars at redhat.com (Lars Kellogg-Stedman) Date: Thu, 2 Apr 2020 16:50:59 -0400 Subject: [Openinfralabs] Prometheus long-term storage Message-ID: <20200402205059.ixzjgvxewtonmeat@redhat.com> Hey, We're currently evaluating Prometheus at the MOC right now, and one of our open questions is what platform we should be using for providing (a) a global view of multiple Prometheus instances (b) some form of HA (basically, we want to be able to take a prometheus host out of service for maintenance without losing metrics) and (c) long term storage of metrics. I've looked at both Thanos and Victoria Metrics, and from both a design and performance perspective Victoria Metrics seems better...but Thanos seems to have more mindshare among people I've spoken with, and looking online for solid comparisons between the two didn't turn up much except some finger-pointing from developers of both solutions (and I haven't even tried to evaluate other options yet, like Cortex, M3DB, etc). Are there folks on this list now who have opinions about these options? -- Lars Kellogg-Stedman | larsks @ {irc,twitter,github} http://blog.oddbit.com/ | N1LKS From mhild at redhat.com Fri Apr 3 10:49:44 2020 From: mhild at redhat.com (Marcel Hild) Date: Fri, 3 Apr 2020 12:49:44 +0200 Subject: [Openinfralabs] Prometheus long-term storage In-Reply-To: <20200402205059.ixzjgvxewtonmeat@redhat.com> References: <20200402205059.ixzjgvxewtonmeat@redhat.com> Message-ID: Given that thanos shares a lot of the community and code behind prometheus, I think this is the way to go now. Also Red Hat uses thanos for ingesting all telemetry data from connected OpenShift 4 deployments, so it works at scale. I'm happy to contribute working deployment artifacts On Thu, Apr 2, 2020 at 10:51 PM Lars Kellogg-Stedman wrote: > Hey, > > We're currently evaluating Prometheus at the MOC right now, and one of > our open questions is what platform we should be using for providing > (a) a global view of multiple Prometheus instances (b) some form of HA > (basically, we want to be able to take a prometheus host out of > service for maintenance without losing metrics) and (c) long term > storage of metrics. > > I've looked at both Thanos and Victoria Metrics, and from both a > design and performance perspective Victoria Metrics seems better...but > Thanos seems to have more mindshare among people I've spoken with, and > looking online for solid comparisons between the two didn't turn up > much except some finger-pointing from developers of both solutions > (and I haven't even tried to evaluate other options yet, like Cortex, > M3DB, etc). > > Are there folks on this list now who have opinions about these > options? > > -- > Lars Kellogg-Stedman | larsks @ {irc,twitter,github} > http://blog.oddbit.com/ | N1LKS > > > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lars at redhat.com Fri Apr 3 14:50:30 2020 From: lars at redhat.com (Lars Kellogg-Stedman) Date: Fri, 3 Apr 2020 10:50:30 -0400 Subject: [Openinfralabs] Prometheus long-term storage In-Reply-To: References: <20200402205059.ixzjgvxewtonmeat@redhat.com> Message-ID: <20200403145030.qgikh5kclzh3as65@redhat.com> On Fri, Apr 03, 2020 at 12:49:44PM +0200, Marcel Hild wrote: > Also Red Hat uses thanos for ingesting all telemetry data from connected > OpenShift 4 deployments, so it works at scale. > > I'm happy to contribute working deployment artifacts That sounds great, and I would be interested in a high level overview of how you have things set up. And as long as I have your attention: We have a simple sandbox set up, and I've noticed recently that the compactor service is falling over with errors along the lines of: > error executing compaction: compaction failed: compaction failed > for group 0 at 2818969819553058366: pre compaction overlap check: > overlaps found while gathering blocks. Have you seen that before, and do you know how to deal with it effectively? We're only collecting data from a single prometheus instance right now, so it's not like we have an HA pair sending duplicate data or something. -- Lars Kellogg-Stedman | larsks @ {irc,twitter,github} http://blog.oddbit.com/ | N1LKS From mhild at redhat.com Fri Apr 3 15:22:55 2020 From: mhild at redhat.com (Marcel Hild) Date: Fri, 3 Apr 2020 17:22:55 +0200 Subject: [Openinfralabs] Prometheus long-term storage In-Reply-To: <20200403145030.qgikh5kclzh3as65@redhat.com> References: <20200402205059.ixzjgvxewtonmeat@redhat.com> <20200403145030.qgikh5kclzh3as65@redhat.com> Message-ID: You should have 2 additional components running all the time. A `compact` component, that, well, compacts. And then a `verify`, which also can repair blocks. https://github.com/thanos-io/thanos/blob/master/docs/components/bucket.md See if that helps On Fri, Apr 3, 2020 at 4:50 PM Lars Kellogg-Stedman wrote: > On Fri, Apr 03, 2020 at 12:49:44PM +0200, Marcel Hild wrote: > > Also Red Hat uses thanos for ingesting all telemetry data from connected > > OpenShift 4 deployments, so it works at scale. > > > > I'm happy to contribute working deployment artifacts > > That sounds great, and I would be interested in a high level overview > of how you have things set up. > > And as long as I have your attention: > > We have a simple sandbox set up, and I've noticed recently that the > compactor service is falling over with errors along the lines of: > > > error executing compaction: compaction failed: compaction failed > > for group 0 at 2818969819553058366: pre compaction overlap check: > > overlaps found while gathering blocks. > > Have you seen that before, and do you know how to deal with it > effectively? We're only collecting data from a single prometheus > instance right now, so it's not like we have an HA pair sending > duplicate data or something. > > -- > Lars Kellogg-Stedman | larsks @ {irc,twitter,github} > http://blog.oddbit.com/ | N1LKS > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lars at redhat.com Fri Apr 3 15:31:38 2020 From: lars at redhat.com (Lars Kellogg-Stedman) Date: Fri, 3 Apr 2020 11:31:38 -0400 Subject: [Openinfralabs] Prometheus long-term storage In-Reply-To: References: <20200402205059.ixzjgvxewtonmeat@redhat.com> <20200403145030.qgikh5kclzh3as65@redhat.com> Message-ID: <20200403153138.i2636hlekfqnzefi@redhat.com> On Fri, Apr 03, 2020 at 05:22:55PM +0200, Marcel Hild wrote: > You should have 2 additional components running all the time. A `compact` > component, that, well, compacts. And then a `verify`, which also can repair > blocks. Right. It's the "compact" component that is throwing the error, and the "thanos bucket verify --repair" process just throws up its hands: msg="repair is not implemented for this issue" issue=overlapped_blocks -- Lars Kellogg-Stedman | larsks @ {irc,twitter,github} http://blog.oddbit.com/ | N1LKS From mhild at redhat.com Fri Apr 3 15:52:08 2020 From: mhild at redhat.com (Marcel Hild) Date: Fri, 3 Apr 2020 17:52:08 +0200 Subject: [Openinfralabs] Prometheus long-term storage In-Reply-To: <20200403153138.i2636hlekfqnzefi@redhat.com> References: <20200402205059.ixzjgvxewtonmeat@redhat.com> <20200403145030.qgikh5kclzh3as65@redhat.com> <20200403153138.i2636hlekfqnzefi@redhat.com> Message-ID: Sorry, can't help here :( Probably good to open an issue at the upstream project... On Fri, Apr 3, 2020 at 5:31 PM Lars Kellogg-Stedman wrote: > On Fri, Apr 03, 2020 at 05:22:55PM +0200, Marcel Hild wrote: > > You should have 2 additional components running all the time. A `compact` > > component, that, well, compacts. And then a `verify`, which also can > repair > > blocks. > > Right. It's the "compact" component that is throwing the error, and > the "thanos bucket verify --repair" process just throws up its hands: > > msg="repair is not implemented for this issue" issue=overlapped_blocks > > -- > Lars Kellogg-Stedman | larsks @ {irc,twitter,github} > http://blog.oddbit.com/ | N1LKS > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lars at redhat.com Fri Apr 3 16:03:35 2020 From: lars at redhat.com (Lars Kellogg-Stedman) Date: Fri, 3 Apr 2020 12:03:35 -0400 Subject: [Openinfralabs] Prometheus long-term storage In-Reply-To: References: <20200402205059.ixzjgvxewtonmeat@redhat.com> <20200403145030.qgikh5kclzh3as65@redhat.com> <20200403153138.i2636hlekfqnzefi@redhat.com> Message-ID: <20200403160335.psufro7n4nbbgq7o@redhat.com> On Fri, Apr 03, 2020 at 05:52:08PM +0200, Marcel Hild wrote: > Sorry, can't help here :( > Probably good to open an issue at the upstream project... It's been tried before... https://github.com/thanos-io/thanos/issues/469 It's a litany of "I'm also having the same problem" comments with no upstream response. This is why I'm looking for folks who have experience with something other than Thanos :). > On Fri, Apr 3, 2020 at 5:31 PM Lars Kellogg-Stedman wrote: > > > On Fri, Apr 03, 2020 at 05:22:55PM +0200, Marcel Hild wrote: > > > You should have 2 additional components running all the time. A `compact` > > > component, that, well, compacts. And then a `verify`, which also can > > repair > > > blocks. > > > > Right. It's the "compact" component that is throwing the error, and > > the "thanos bucket verify --repair" process just throws up its hands: > > > > msg="repair is not implemented for this issue" issue=overlapped_blocks -- Lars Kellogg-Stedman | larsks @ {irc,twitter,github} http://blog.oddbit.com/ | N1LKS From mhild at redhat.com Fri Apr 3 16:15:41 2020 From: mhild at redhat.com (Marcel Hild) Date: Fri, 3 Apr 2020 18:15:41 +0200 Subject: [Openinfralabs] Prometheus long-term storage In-Reply-To: <20200403160335.psufro7n4nbbgq7o@redhat.com> References: <20200402205059.ixzjgvxewtonmeat@redhat.com> <20200403145030.qgikh5kclzh3as65@redhat.com> <20200403153138.i2636hlekfqnzefi@redhat.com> <20200403160335.psufro7n4nbbgq7o@redhat.com> Message-ID: Ok :( But it's a great example of why an open-cloud would make sense, so that the thanos folks could look at the blocks. On Fri, Apr 3, 2020 at 6:03 PM Lars Kellogg-Stedman wrote: > On Fri, Apr 03, 2020 at 05:52:08PM +0200, Marcel Hild wrote: > > Sorry, can't help here :( > > Probably good to open an issue at the upstream project... > > It's been tried before... > > https://github.com/thanos-io/thanos/issues/469 > > It's a litany of "I'm also having the same problem" comments with no > upstream response. This is why I'm looking for folks who have > experience with something other than Thanos :). > > > On Fri, Apr 3, 2020 at 5:31 PM Lars Kellogg-Stedman > wrote: > > > > > On Fri, Apr 03, 2020 at 05:22:55PM +0200, Marcel Hild wrote: > > > > You should have 2 additional components running all the time. A > `compact` > > > > component, that, well, compacts. And then a `verify`, which also can > > > repair > > > > blocks. > > > > > > Right. It's the "compact" component that is throwing the error, and > > > the "thanos bucket verify --repair" process just throws up its hands: > > > > > > msg="repair is not implemented for this issue" > issue=overlapped_blocks > > -- > Lars Kellogg-Stedman | larsks @ {irc,twitter,github} > http://blog.oddbit.com/ | N1LKS > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From msd at bu.edu Thu Apr 16 01:14:38 2020 From: msd at bu.edu (Michael Daitzman) Date: Wed, 15 Apr 2020 21:14:38 -0400 Subject: [Openinfralabs] What operational data and data streams should be gathered? Message-ID: <89eaeb20-6753-adb5-fab9-fa884f296b5c@bu.edu> TL;DR: As we think about making operational data from the Mass Open Cloud available to the open source community, we need to define what data and data streams will be useful and gathered. This email is meant to begin a discussion and define that. TS;WM: Some context - the Mass Open Cloud (MOC) is a research cloud formed as a public-private partnership between 5 Research Universities, a group of partner companies, and the state of Massachusetts. The MOC has always had a goal of sharing operational data about the MOC to enable research on cloud computing technologies. As teams working on OI Labs projects began discussing operational data, one question was, “can the MOC share that data to the open source community?” To a great extent, this becomes part of a “Research Compliance” question and may be affected by various grants which have funded the MOC (good news - in almost every grant the PI’s have made clear that data sharing is a goal). As we looked into making such information available, I had a brief discussion with the director of BU’s Research Computing group who helped frame how we should approach this question. The first steps are: 1. Defining what data and data streams will be useful and gathered is the first step 2. Based on that we may identify which populations may be affected 3. Decide on the next steps based on the answers to item 1 and 2 above -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhild at redhat.com Thu Apr 16 10:52:28 2020 From: mhild at redhat.com (Marcel Hild) Date: Thu, 16 Apr 2020 12:52:28 +0200 Subject: [Openinfralabs] What operational data and data streams should be gathered? In-Reply-To: <89eaeb20-6753-adb5-fab9-fa884f296b5c@bu.edu> References: <89eaeb20-6753-adb5-fab9-fa884f296b5c@bu.edu> Message-ID: I would start with monitoring data, i.e. all prometheus metrics being collected. But those in itself are not really useful without a picture of the infrastructure and access to the infrastructure. And you might need access to ticket systems, since you want to correlate the metrics with incidents. My point is, we need to open up _all_ aspects of operations to make it actually useful, otherwise it'll be just a pile of data. I was hoping that the newly build out NERC could be the blueprint for this. On Thu, Apr 16, 2020 at 3:15 AM Michael Daitzman wrote: > > TL;DR: > > As we think about making operational data from the Mass Open Cloud > available to the open source community, we need > to define what data and data streams will be useful and gathered. > > This email is meant to begin a discussion and define that. > > TS;WM: > > Some context - the Mass Open Cloud (MOC) is a research cloud formed as a > public-private partnership between 5 Research Universities, a group of > partner companies, and the state of Massachusetts. > > The MOC has always had a goal of sharing operational data about the MOC to > enable research on cloud computing technologies. > > As teams working on OI Labs projects began discussing operational data, > one question was, “can the MOC share that data to the open source > community?” > > To a great extent, this becomes part of a “Research Compliance” question > and may be affected by various grants which have funded the MOC (good news > - in almost every grant the PI’s have made clear that data sharing is a > goal). > > As we looked into making such information available, I had a brief > discussion with the director of BU’s Research Computing group who helped > frame how we should approach this question. The first steps are: > > 1. > > Defining what data and data streams will be useful and gathered is the > first step > 2. > > Based on that we may identify which populations may be affected > 3. > > Decide on the next steps based on the answers to item 1 and 2 above > > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > -------------- next part -------------- An HTML attachment was scrubbed... URL: From msd at bu.edu Fri Apr 17 19:58:20 2020 From: msd at bu.edu (Daitzman, Michael S) Date: Fri, 17 Apr 2020 19:58:20 +0000 Subject: [Openinfralabs] Some High Level Project Planning for NERC Message-ID: <623488F6-D109-4B02-AF1E-966340C86FDB@bu.edu> We have begun putting a few very high-level Epics into gitlab – take look and please let us know what you think: https://gitlab.com/open-infrastructure-labs/nerc-architecture/-/boards --- Michael Daitzman (He/Him) msd at bu.edu cell:978-201-9965 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhild at redhat.com Tue Apr 21 10:04:19 2020 From: mhild at redhat.com (Marcel Hild) Date: Tue, 21 Apr 2020 12:04:19 +0200 Subject: [Openinfralabs] Operate First OKRs and Manfisto Message-ID: If we invite people to contribute to https://gitlab.com/open-infrastructure-labs/nerc-architecture I would love to explain why we do it all in the open. While the website https://openinfralabs.org/ is a good first start, it certainly lacks some content. In the spirit of release early and often, how about putting a community version of the operate first manifesto and the OKRs on that same webpage? Is this domain the right place for it? Or should we grab https://instantdomainsearch.com/#search=operatefirst -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan at openstack.org Tue Apr 21 15:57:40 2020 From: jonathan at openstack.org (Jonathan Bryce) Date: Tue, 21 Apr 2020 10:57:40 -0500 Subject: [Openinfralabs] OpenInfra Labs Branding In-Reply-To: <2840A830-EC0F-4EC2-8E91-71EDDBD8AB16@openstack.org> References: <2840A830-EC0F-4EC2-8E91-71EDDBD8AB16@openstack.org> Message-ID: Digging this one back up and adding some of my free brainstorm thoughts > • Do you have any initial ideas or opinions for this brand? This is a project that focuses on integrating systems together for real-world usage. It’s got an academic/science/research heritage, but I don’t think it will play only in that world. There’s also a strong operations focus—running things reliably and repeatably—and sharing the resources and knowledge around doing that broadly and openly. > • How would you want this brand to be perceived (corporate, futuristic, whimsical, trustworthy, etc.)? I don’t have a strong opinion on this one. Would love to hear if anyone else has thoughts on it. > • Are there any brands or projects similar to this project? Someone in a conversation once compared it to Underwriters Laboratories ( https://www.ul.com/ ). Not sure the brand feel would be the same, but just sharing. OPNFV ( https://www.opnfv.org/ ) is another open source community that has a similar mission in the telecom space. > • Are there any brands or visual systems you do not want to emulate? > • Any other thoughts? Thanks! Jonathan > On Mar 31, 2020, at 5:08 PM, James Cole wrote: > > Greetings OpenInfra Labs team! > > My name is James Cole and I’m a graphic designer with the OpenStack Foundation. We want to help you brand this project and would like to gather your ideas before venturing too far down the logo development process. > > There are a few obvious possibilities for the visual identity (e.g., laboratory equipment, scientific things, symbols related to testing, etc.) but maybe you have some unique ideas that would better represent the project. > > Our brand design process normally follows these steps: > > • Gather internal and community requirements > • Create some rough concepts > • Share the concepts internally with the OSF team > • Share the concepts on the mailing list and gather feedback > • Revise and refine concepts as necessary > • Gather consensus and select the community favorite as the official logo > > Some things that are helpful to know: > > • Do you have any initial ideas or opinions for this brand? > • How would you want this brand to be perceived (corporate, futuristic, whimsical, trustworthy, etc.)? > • Are there any brands or projects similar to this project? > • Are there any brands or visual systems you do not want to emulate? > • Any other thoughts? > > Thank you! > > James Cole > Graphic Designer > OpenStack Foundation > > > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs From james at openstack.org Tue Apr 21 16:25:22 2020 From: james at openstack.org (James Cole) Date: Tue, 21 Apr 2020 11:25:22 -0500 Subject: [Openinfralabs] OpenInfra Labs Branding In-Reply-To: References: <2840A830-EC0F-4EC2-8E91-71EDDBD8AB16@openstack.org> Message-ID: <8A4D6E28-18E7-4682-B059-1AE77A1AE5F4@openstack.org> Thanks Jonathan! This is helpful. I’d love to hear if anybody else has thoughts on these things as well. -James > On Apr 21, 2020, at 10:57 AM, Jonathan Bryce wrote: > > Digging this one back up and adding some of my free brainstorm thoughts > >> • Do you have any initial ideas or opinions for this brand? > This is a project that focuses on integrating systems together for real-world usage. It’s got an academic/science/research heritage, but I don’t think it will play only in that world. > > There’s also a strong operations focus—running things reliably and repeatably—and sharing the resources and knowledge around doing that broadly and openly. > >> • How would you want this brand to be perceived (corporate, futuristic, whimsical, trustworthy, etc.)? > I don’t have a strong opinion on this one. Would love to hear if anyone else has thoughts on it. > >> • Are there any brands or projects similar to this project? > Someone in a conversation once compared it to Underwriters Laboratories ( https://www.ul.com/ ). Not sure the brand feel would be the same, but just sharing. > > OPNFV ( https://www.opnfv.org/ ) is another open source community that has a similar mission in the telecom space. > >> • Are there any brands or visual systems you do not want to emulate? >> • Any other thoughts? > > Thanks! > > Jonathan > > > > >> On Mar 31, 2020, at 5:08 PM, James Cole wrote: >> >> Greetings OpenInfra Labs team! >> >> My name is James Cole and I’m a graphic designer with the OpenStack Foundation. We want to help you brand this project and would like to gather your ideas before venturing too far down the logo development process. >> >> There are a few obvious possibilities for the visual identity (e.g., laboratory equipment, scientific things, symbols related to testing, etc.) but maybe you have some unique ideas that would better represent the project. >> >> Our brand design process normally follows these steps: >> >> • Gather internal and community requirements >> • Create some rough concepts >> • Share the concepts internally with the OSF team >> • Share the concepts on the mailing list and gather feedback >> • Revise and refine concepts as necessary >> • Gather consensus and select the community favorite as the official logo >> >> Some things that are helpful to know: >> >> • Do you have any initial ideas or opinions for this brand? >> • How would you want this brand to be perceived (corporate, futuristic, whimsical, trustworthy, etc.)? >> • Are there any brands or projects similar to this project? >> • Are there any brands or visual systems you do not want to emulate? >> • Any other thoughts? >> >> Thank you! >> >> James Cole >> Graphic Designer >> OpenStack Foundation >> >> >> _______________________________________________ >> Openinfralabs mailing list >> Openinfralabs at lists.opendev.org >> http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > > > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs From jimmy at openstack.org Tue Apr 21 16:32:33 2020 From: jimmy at openstack.org (Jimmy McArthur) Date: Tue, 21 Apr 2020 11:32:33 -0500 Subject: [Openinfralabs] Operate First OKRs and Manfisto In-Reply-To: References: Message-ID: Hi all! Last time we spoke we were in the process of moving OpenInfra Labs over to Gatsby and setting the site up on Netlify.  Unfortunately, that deliverable was pushed a bit and I'm expecting that to occur this week. After that, we'll plan to move the site over to its final home on Gitlab, which is I think the preferred home for all of your development. Please let me know who your repo admins should be and I'll make sure to set that up as well. Re: the content suggestion below - yes!  Love that there is some interest in adding to the site content.  I think this could probably end up being either a blog post or a stand alone section on the site. Either of which will be doable when we get the new structure in place. In the meantime, can I suggest doing a PR against the existing site on github and we can just add this content to the homepage?  Once the new site is up, we can look at moving things into sections or individual posts as your community deems appropriate. Also worth mentioning, the OSF follows what we call the 4 Opens: https://osf.dev/about/four-opens/  I thought it might help with your operate first manifesto or if you think there is some content that could be added from the manifesto to the 4 Opens, please feel free to contribute: https://opendev.org/osf/four-opens/ Cheers, Jimmy Marcel Hild wrote on 4/21/20 5:04 AM: > If we invite people to contribute to > https://gitlab.com/open-infrastructure-labs/nerc-architecture I would > love to explain why we do it all in the open. > While the website https://openinfralabs.org/ is a good first start, it > certainly lacks some content. > > In the spirit of release early and often, how about putting a > community version of the operate first manifesto and the OKRs on that > same webpage? > > Is this domain the right place for it? Or should we grab > https://instantdomainsearch.com/#search=operatefirst > > > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs -------------- next part -------------- An HTML attachment was scrubbed... URL: From bburns at redhat.com Wed Apr 22 18:54:29 2020 From: bburns at redhat.com (Bill Burns) Date: Wed, 22 Apr 2020 14:54:29 -0400 Subject: [Openinfralabs] OpenInfra Labs Branding In-Reply-To: References: <2840A830-EC0F-4EC2-8E91-71EDDBD8AB16@openstack.org> Message-ID: On Tue, Apr 21, 2020 at 12:00 PM Jonathan Bryce wrote: > Digging this one back up and adding some of my free brainstorm thoughts > > > • Do you have any initial ideas or opinions for this brand? > This is a project that focuses on integrating systems together for > real-world usage. It’s got an academic/science/research heritage, but I > don’t think it will play only in that world. > > There’s also a strong operations focus—running things reliably and > repeatably—and sharing the resources and knowledge around doing that > broadly and openly. > > > • How would you want this brand to be perceived (corporate, > futuristic, whimsical, trustworthy, etc.)? > I don’t have a strong opinion on this one. Would love to hear if anyone > else has thoughts on it. > Maybe organizational? Or simplifying? It's about taking cloud computing environments which are difficult and complex to operate and trying to make it more reasonable. > > • Are there any brands or projects similar to this project? > Someone in a conversation once compared it to Underwriters Laboratories ( > https://www.ul.com/ ). Not sure the brand feel would be the same, but > just sharing. > > OPNFV ( https://www.opnfv.org/ ) is another open source community that > has a similar mission in the telecom space. > Yes, that may be the best analogy. OPNFV was about making sure various projects could work together. And this is about making sure various projects that make up a cloud can be reasonably operated. cheers, Bill > > > • Are there any brands or visual systems you do not want to > emulate? > > • Any other thoughts? > > Thanks! > > Jonathan > > > > > > On Mar 31, 2020, at 5:08 PM, James Cole wrote: > > > > Greetings OpenInfra Labs team! > > > > My name is James Cole and I’m a graphic designer with the OpenStack > Foundation. We want to help you brand this project and would like to gather > your ideas before venturing too far down the logo development process. > > > > There are a few obvious possibilities for the visual identity (e.g., > laboratory equipment, scientific things, symbols related to testing, etc.) > but maybe you have some unique ideas that would better represent the > project. > > > > Our brand design process normally follows these steps: > > > > • Gather internal and community requirements > > • Create some rough concepts > > • Share the concepts internally with the OSF team > > • Share the concepts on the mailing list and gather feedback > > • Revise and refine concepts as necessary > > • Gather consensus and select the community favorite as the > official logo > > > > Some things that are helpful to know: > > > > • Do you have any initial ideas or opinions for this brand? > > • How would you want this brand to be perceived (corporate, > futuristic, whimsical, trustworthy, etc.)? > > • Are there any brands or projects similar to this project? > > • Are there any brands or visual systems you do not want to > emulate? > > • Any other thoughts? > > > > Thank you! > > > > James Cole > > Graphic Designer > > OpenStack Foundation > > > > > > _______________________________________________ > > Openinfralabs mailing list > > Openinfralabs at lists.opendev.org > > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > > > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bburns at redhat.com Wed Apr 22 19:20:24 2020 From: bburns at redhat.com (Bill Burns) Date: Wed, 22 Apr 2020 15:20:24 -0400 Subject: [Openinfralabs] Operate First OKRs and Manfisto In-Reply-To: References: Message-ID: On Tue, Apr 21, 2020 at 12:32 PM Jimmy McArthur wrote: > Hi all! > > Last time we spoke we were in the process of moving OpenInfra Labs over to > Gatsby and setting the site up on Netlify. Unfortunately, that deliverable > was pushed a bit and I'm expecting that to occur this week. After that, > we'll plan to move the site over to its final home on Gitlab, which is I > think the preferred home for all of your development. Please let me know > who your repo admins should be and I'll make sure to set that up as well. > > Re: the content suggestion below - yes! Love that there is some interest > in adding to the site content. I think this could probably end up being > either a blog post or a stand alone section on the site. Either of which > will be doable when we get the new structure in place. In the meantime, > can I suggest doing a PR against the existing site on github and we can > just add this content to the homepage? Once the new site is up, we can > look at moving things into sections or individual posts as your community > deems appropriate. > > Also worth mentioning, the OSF follows what we call the 4 Opens: > https://osf.dev/about/four-opens/ I thought it might help with your > operate first manifesto or if you think there is some content that could be > added from the manifesto to the 4 Opens, please feel free to contribute: > https://opendev.org/osf/four-opens/ > > I don't think this would change the four opens. Ideally communities will decide to make operational considerations part of their design and development processes along with the functionality they produce. You see this today with Kubernetes Operators, where an API for operations has developed that many projects are moving toward. I suppose a community like OSF could broadly embrace an idea of "open operations" as well, as some point. cheers, Bill Cheers, > Jimmy > > Marcel Hild wrote on 4/21/20 5:04 AM: > > If we invite people to contribute to > https://gitlab.com/open-infrastructure-labs/nerc-architecture I would > love to explain why we do it all in the open. > While the website https://openinfralabs.org/ is a good first start, it > certainly lacks some content. > > In the spirit of release early and often, how about putting a community > version of the operate first manifesto and the OKRs on that same webpage? > > Is this domain the right place for it? Or should we grab > https://instantdomainsearch.com/#search=operatefirst > > > _______________________________________________ > Openinfralabs mailing listOpeninfralabs at lists.opendev.orghttp://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > > > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at openstack.org Wed Apr 22 21:02:40 2020 From: james at openstack.org (James Cole) Date: Wed, 22 Apr 2020 16:02:40 -0500 Subject: [Openinfralabs] OpenInfra Labs Branding In-Reply-To: References: <2840A830-EC0F-4EC2-8E91-71EDDBD8AB16@openstack.org> Message-ID: <038E7751-B9E9-4F69-BEBE-20E1D56D4BDF@openstack.org> Thanks for the insight, Bill! -James > On Apr 22, 2020, at 1:54 PM, Bill Burns wrote: > > > > On Tue, Apr 21, 2020 at 12:00 PM Jonathan Bryce > wrote: > Digging this one back up and adding some of my free brainstorm thoughts > > > • Do you have any initial ideas or opinions for this brand? > This is a project that focuses on integrating systems together for real-world usage. It’s got an academic/science/research heritage, but I don’t think it will play only in that world. > > There’s also a strong operations focus—running things reliably and repeatably—and sharing the resources and knowledge around doing that broadly and openly. > > > • How would you want this brand to be perceived (corporate, futuristic, whimsical, trustworthy, etc.)? > I don’t have a strong opinion on this one. Would love to hear if anyone else has thoughts on it. > > Maybe organizational? Or simplifying? It's about taking cloud computing environments which > are difficult and complex to operate and trying to make it more reasonable. > > > > > • Are there any brands or projects similar to this project? > Someone in a conversation once compared it to Underwriters Laboratories ( https://www.ul.com/ ). Not sure the brand feel would be the same, but just sharing. > > OPNFV ( https://www.opnfv.org/ ) is another open source community that has a similar mission in the telecom space. > > Yes, that may be the best analogy. OPNFV was about making sure various projects > could work together. And this is about making sure various projects that make up > a cloud can be reasonably operated. > > cheers, > Bill > > > > • Are there any brands or visual systems you do not want to emulate? > > • Any other thoughts? > > Thanks! > > Jonathan > > > > > > On Mar 31, 2020, at 5:08 PM, James Cole > wrote: > > > > Greetings OpenInfra Labs team! > > > > My name is James Cole and I’m a graphic designer with the OpenStack Foundation. We want to help you brand this project and would like to gather your ideas before venturing too far down the logo development process. > > > > There are a few obvious possibilities for the visual identity (e.g., laboratory equipment, scientific things, symbols related to testing, etc.) but maybe you have some unique ideas that would better represent the project. > > > > Our brand design process normally follows these steps: > > > > • Gather internal and community requirements > > • Create some rough concepts > > • Share the concepts internally with the OSF team > > • Share the concepts on the mailing list and gather feedback > > • Revise and refine concepts as necessary > > • Gather consensus and select the community favorite as the official logo > > > > Some things that are helpful to know: > > > > • Do you have any initial ideas or opinions for this brand? > > • How would you want this brand to be perceived (corporate, futuristic, whimsical, trustworthy, etc.)? > > • Are there any brands or projects similar to this project? > > • Are there any brands or visual systems you do not want to emulate? > > • Any other thoughts? > > > > Thank you! > > > > James Cole > > Graphic Designer > > OpenStack Foundation > > > > > > _______________________________________________ > > Openinfralabs mailing list > > Openinfralabs at lists.opendev.org > > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > > > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs -------------- next part -------------- An HTML attachment was scrubbed... URL: From bburns at redhat.com Fri Apr 24 17:28:23 2020 From: bburns at redhat.com (Bill Burns) Date: Fri, 24 Apr 2020 13:28:23 -0400 Subject: [Openinfralabs] Operate First OKRs and Manfisto In-Reply-To: References: Message-ID: I took the Operate First Manifesto that we had created for the Red Hat initiative and made a community version that I have added to the website git repo. I created a merge request to add it. Let me know if there are any issues with my request.... cheers, bill On Tue, Apr 21, 2020 at 12:32 PM Jimmy McArthur wrote: > Hi all! > > Last time we spoke we were in the process of moving OpenInfra Labs over to > Gatsby and setting the site up on Netlify. Unfortunately, that deliverable > was pushed a bit and I'm expecting that to occur this week. After that, > we'll plan to move the site over to its final home on Gitlab, which is I > think the preferred home for all of your development. Please let me know > who your repo admins should be and I'll make sure to set that up as well. > > Re: the content suggestion below - yes! Love that there is some interest > in adding to the site content. I think this could probably end up being > either a blog post or a stand alone section on the site. Either of which > will be doable when we get the new structure in place. In the meantime, > can I suggest doing a PR against the existing site on github and we can > just add this content to the homepage? Once the new site is up, we can > look at moving things into sections or individual posts as your community > deems appropriate. > > Also worth mentioning, the OSF follows what we call the 4 Opens: > https://osf.dev/about/four-opens/ I thought it might help with your > operate first manifesto or if you think there is some content that could be > added from the manifesto to the 4 Opens, please feel free to contribute: > https://opendev.org/osf/four-opens/ > > Cheers, > Jimmy > > Marcel Hild wrote on 4/21/20 5:04 AM: > > If we invite people to contribute to > https://gitlab.com/open-infrastructure-labs/nerc-architecture I would > love to explain why we do it all in the open. > While the website https://openinfralabs.org/ is a good first start, it > certainly lacks some content. > > In the spirit of release early and often, how about putting a community > version of the operate first manifesto and the OKRs on that same webpage? > > Is this domain the right place for it? Or should we grab > https://instantdomainsearch.com/#search=operatefirst > > > _______________________________________________ > Openinfralabs mailing listOpeninfralabs at lists.opendev.orghttp://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > > > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chlong at redhat.com Fri Apr 24 18:15:41 2020 From: chlong at redhat.com (Chris Long) Date: Fri, 24 Apr 2020 14:15:41 -0400 Subject: [Openinfralabs] Operate First OKRs and Manfisto In-Reply-To: References: Message-ID: could you post the MR link please Bill? Chris Long Red Hat Pillar Architect, EXD Infrastructure, Enterprise eXperience and Delivery, Westford Mobile: +603 400 7986 IRC: chlong "Do what you love doing, with people who you like being with, to the overall benefit of society - build individual and collective wealth in the team." On Fri, Apr 24, 2020 at 1:28 PM Bill Burns wrote: > > I took the Operate First Manifesto that we had created for the Red Hat > initiative and made a community version that I have added to the website > git repo. I created a merge request to add it. Let me know if there are > any issues with my request.... > > cheers, > bill > > > > On Tue, Apr 21, 2020 at 12:32 PM Jimmy McArthur > wrote: > >> Hi all! >> >> Last time we spoke we were in the process of moving OpenInfra Labs over >> to Gatsby and setting the site up on Netlify. Unfortunately, that >> deliverable was pushed a bit and I'm expecting that to occur this week. >> After that, we'll plan to move the site over to its final home on Gitlab, >> which is I think the preferred home for all of your development. Please let >> me know who your repo admins should be and I'll make sure to set that up as >> well. >> >> Re: the content suggestion below - yes! Love that there is some interest >> in adding to the site content. I think this could probably end up being >> either a blog post or a stand alone section on the site. Either of which >> will be doable when we get the new structure in place. In the meantime, >> can I suggest doing a PR against the existing site on github and we can >> just add this content to the homepage? Once the new site is up, we can >> look at moving things into sections or individual posts as your community >> deems appropriate. >> >> Also worth mentioning, the OSF follows what we call the 4 Opens: >> https://osf.dev/about/four-opens/ I thought it might help with your >> operate first manifesto or if you think there is some content that could be >> added from the manifesto to the 4 Opens, please feel free to contribute: >> https://opendev.org/osf/four-opens/ >> >> Cheers, >> Jimmy >> >> Marcel Hild wrote on 4/21/20 5:04 AM: >> >> If we invite people to contribute to >> https://gitlab.com/open-infrastructure-labs/nerc-architecture I would >> love to explain why we do it all in the open. >> While the website https://openinfralabs.org/ is a good first start, it >> certainly lacks some content. >> >> In the spirit of release early and often, how about putting a community >> version of the operate first manifesto and the OKRs on that same webpage? >> >> Is this domain the right place for it? Or should we grab >> https://instantdomainsearch.com/#search=operatefirst >> >> >> _______________________________________________ >> Openinfralabs mailing listOpeninfralabs at lists.opendev.orghttp://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >> >> >> _______________________________________________ >> Openinfralabs mailing list >> Openinfralabs at lists.opendev.org >> http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >> > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bburns at redhat.com Fri Apr 24 18:22:36 2020 From: bburns at redhat.com (Bill Burns) Date: Fri, 24 Apr 2020 14:22:36 -0400 Subject: [Openinfralabs] Operate First OKRs and Manfisto In-Reply-To: References: Message-ID: Is this what you need? https://gitlab.com/open-infrastructure-labs/openinfralabs-website/-/merge_requests cheers, Bill On Fri, Apr 24, 2020 at 2:16 PM Chris Long wrote: > could you post the MR link please Bill? > Chris Long > > Red Hat > > > Pillar Architect, EXD Infrastructure, > > > Enterprise eXperience and Delivery, Westford > Mobile: +603 400 7986 > IRC: chlong > > > > "Do what you love doing, with people who you like being with, to the > overall benefit of society - build individual and collective wealth in the > team." > > > On Fri, Apr 24, 2020 at 1:28 PM Bill Burns wrote: > >> >> I took the Operate First Manifesto that we had created for the Red Hat >> initiative and made a community version that I have added to the website >> git repo. I created a merge request to add it. Let me know if there are >> any issues with my request.... >> >> cheers, >> bill >> >> >> >> On Tue, Apr 21, 2020 at 12:32 PM Jimmy McArthur >> wrote: >> >>> Hi all! >>> >>> Last time we spoke we were in the process of moving OpenInfra Labs over >>> to Gatsby and setting the site up on Netlify. Unfortunately, that >>> deliverable was pushed a bit and I'm expecting that to occur this week. >>> After that, we'll plan to move the site over to its final home on Gitlab, >>> which is I think the preferred home for all of your development. Please let >>> me know who your repo admins should be and I'll make sure to set that up as >>> well. >>> >>> Re: the content suggestion below - yes! Love that there is some >>> interest in adding to the site content. I think this could probably end up >>> being either a blog post or a stand alone section on the site. Either of >>> which will be doable when we get the new structure in place. In the >>> meantime, can I suggest doing a PR against the existing site on github and >>> we can just add this content to the homepage? Once the new site is up, we >>> can look at moving things into sections or individual posts as your >>> community deems appropriate. >>> >>> Also worth mentioning, the OSF follows what we call the 4 Opens: >>> https://osf.dev/about/four-opens/ I thought it might help with your >>> operate first manifesto or if you think there is some content that could be >>> added from the manifesto to the 4 Opens, please feel free to contribute: >>> https://opendev.org/osf/four-opens/ >>> >>> Cheers, >>> Jimmy >>> >>> Marcel Hild wrote on 4/21/20 5:04 AM: >>> >>> If we invite people to contribute to >>> https://gitlab.com/open-infrastructure-labs/nerc-architecture I would >>> love to explain why we do it all in the open. >>> While the website https://openinfralabs.org/ is a good first start, it >>> certainly lacks some content. >>> >>> In the spirit of release early and often, how about putting a community >>> version of the operate first manifesto and the OKRs on that same webpage? >>> >>> Is this domain the right place for it? Or should we grab >>> https://instantdomainsearch.com/#search=operatefirst >>> >>> >>> _______________________________________________ >>> Openinfralabs mailing listOpeninfralabs at lists.opendev.orghttp://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >>> >>> >>> _______________________________________________ >>> Openinfralabs mailing list >>> Openinfralabs at lists.opendev.org >>> http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >>> >> _______________________________________________ >> Openinfralabs mailing list >> Openinfralabs at lists.opendev.org >> http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhild at redhat.com Fri Apr 24 19:00:59 2020 From: mhild at redhat.com (Marcel Hild) Date: Fri, 24 Apr 2020 21:00:59 +0200 Subject: [Openinfralabs] Operate First OKRs and Manfisto In-Reply-To: References: Message-ID: Looks like you're missing the commit - the merge request is empty :) https://gitlab.com/open-infrastructure-labs/openinfralabs-website/-/merge_requests/1 On Fri, Apr 24, 2020 at 8:22 PM Bill Burns wrote: > > Is this what you need? > > > https://gitlab.com/open-infrastructure-labs/openinfralabs-website/-/merge_requests > > cheers, > Bill > > > On Fri, Apr 24, 2020 at 2:16 PM Chris Long wrote: > >> could you post the MR link please Bill? >> Chris Long >> >> Red Hat >> >> >> Pillar Architect, EXD Infrastructure, >> >> >> Enterprise eXperience and Delivery, Westford >> Mobile: +603 400 7986 >> IRC: chlong >> >> >> >> "Do what you love doing, with people who you like being with, to the >> overall benefit of society - build individual and collective wealth in the >> team." >> >> >> On Fri, Apr 24, 2020 at 1:28 PM Bill Burns wrote: >> >>> >>> I took the Operate First Manifesto that we had created for the Red Hat >>> initiative and made a community version that I have added to the website >>> git repo. I created a merge request to add it. Let me know if there are >>> any issues with my request.... >>> >>> cheers, >>> bill >>> >>> >>> >>> On Tue, Apr 21, 2020 at 12:32 PM Jimmy McArthur >>> wrote: >>> >>>> Hi all! >>>> >>>> Last time we spoke we were in the process of moving OpenInfra Labs over >>>> to Gatsby and setting the site up on Netlify. Unfortunately, that >>>> deliverable was pushed a bit and I'm expecting that to occur this week. >>>> After that, we'll plan to move the site over to its final home on Gitlab, >>>> which is I think the preferred home for all of your development. Please let >>>> me know who your repo admins should be and I'll make sure to set that up as >>>> well. >>>> >>>> Re: the content suggestion below - yes! Love that there is some >>>> interest in adding to the site content. I think this could probably end up >>>> being either a blog post or a stand alone section on the site. Either of >>>> which will be doable when we get the new structure in place. In the >>>> meantime, can I suggest doing a PR against the existing site on github and >>>> we can just add this content to the homepage? Once the new site is up, we >>>> can look at moving things into sections or individual posts as your >>>> community deems appropriate. >>>> >>>> Also worth mentioning, the OSF follows what we call the 4 Opens: >>>> https://osf.dev/about/four-opens/ I thought it might help with your >>>> operate first manifesto or if you think there is some content that could be >>>> added from the manifesto to the 4 Opens, please feel free to contribute: >>>> https://opendev.org/osf/four-opens/ >>>> >>>> Cheers, >>>> Jimmy >>>> >>>> Marcel Hild wrote on 4/21/20 5:04 AM: >>>> >>>> If we invite people to contribute to >>>> https://gitlab.com/open-infrastructure-labs/nerc-architecture I would >>>> love to explain why we do it all in the open. >>>> While the website https://openinfralabs.org/ is a good first start, >>>> it certainly lacks some content. >>>> >>>> In the spirit of release early and often, how about putting a community >>>> version of the operate first manifesto and the OKRs on that same webpage? >>>> >>>> Is this domain the right place for it? Or should we grab >>>> https://instantdomainsearch.com/#search=operatefirst >>>> >>>> >>>> _______________________________________________ >>>> Openinfralabs mailing listOpeninfralabs at lists.opendev.orghttp://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >>>> >>>> >>>> _______________________________________________ >>>> Openinfralabs mailing list >>>> Openinfralabs at lists.opendev.org >>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >>>> >>> _______________________________________________ >>> Openinfralabs mailing list >>> Openinfralabs at lists.opendev.org >>> http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Fri Apr 24 19:10:58 2020 From: jimmy at openstack.org (Jimmy McArthur) Date: Fri, 24 Apr 2020 14:10:58 -0500 Subject: [Openinfralabs] Operate First OKRs and Manfisto In-Reply-To: References: Message-ID: <24a607c0-b002-6ab0-51b6-7e98d1df0692@openstack.org> As mentioned in a previous email, the website is still being served from github.  We're in final QA of the site updates we've been working on, so whatever is committed to gitlab is going to need to be redone as a pull request on github. Marcel Hild wrote on 4/24/20 2:00 PM: > Looks like you're missing the commit - the merge request is empty :) > https://gitlab.com/open-infrastructure-labs/openinfralabs-website/-/merge_requests/1 > > On Fri, Apr 24, 2020 at 8:22 PM Bill Burns > wrote: > > > Is this what you need? > > https://gitlab.com/open-infrastructure-labs/openinfralabs-website/-/merge_requests > > cheers, >  Bill > > > On Fri, Apr 24, 2020 at 2:16 PM Chris Long > wrote: > > could you post the MR link please Bill? > ChrisLong > > Red Hat > > > > Pillar Architect, EXD Infrastructure, > > Enterprise eXperience and Delivery, Westford > Mobile: +603 400 7986 > IRC: chlong > > > > "Do what you love doing, with people who you like being with, > to the overall benefit of society - build individual and > collective wealth in the team." > > > On Fri, Apr 24, 2020 at 1:28 PM Bill Burns > wrote: > > > I took the Operate First Manifesto that we had created for > the Red Hat > initiative and made a community version that I have added > to the website > git repo. I created a merge request to add it. Let me know > if there are > any issues with my request.... > > cheers, >  bill > > > > On Tue, Apr 21, 2020 at 12:32 PM Jimmy McArthur > > wrote: > > Hi all! > > Last time we spoke we were in the process of moving > OpenInfra Labs over to Gatsby and setting the site up > on Netlify.  Unfortunately, that deliverable was > pushed a bit and I'm expecting that to occur this > week. After that, we'll plan to move the site over to > its final home on Gitlab, which is I think the > preferred home for all of your development. Please let > me know who your repo admins should be and I'll make > sure to set that up as well. > > Re: the content suggestion below - yes!  Love that > there is some interest in adding to the site content.  > I think this could probably end up being either a blog > post or a stand alone section on the site. Either of > which will be doable when we get the new structure in > place. In the meantime, can I suggest doing a PR > against the existing site on github and we can just > add this content to the homepage?  Once the new site > is up, we can look at moving things into sections or > individual posts as your community deems appropriate. > > Also worth mentioning, the OSF follows what we call > the 4 Opens: https://osf.dev/about/four-opens/  I > thought it might help with your operate first > manifesto or if you think there is some content that > could be added from the manifesto to the 4 Opens, > please feel free to contribute: > https://opendev.org/osf/four-opens/ > > Cheers, > Jimmy > > Marcel Hild wrote on 4/21/20 5:04 AM: >> If we invite people to contribute to >> https://gitlab.com/open-infrastructure-labs/nerc-architecture I >> would love to explain why we do it all in the open. >> While the website https://openinfralabs.org/ is a >> good first start, it certainly lacks some content. >> >> In the spirit of release early and often, how about >> putting a community version of the operate first >> manifesto and the OKRs on that same webpage? >> >> Is this domain the right place for it? Or should we >> grab >> https://instantdomainsearch.com/#search=operatefirst >> >> >> _______________________________________________ >> Openinfralabs mailing list >> Openinfralabs at lists.opendev.org >> >> http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bburns at redhat.com Tue Apr 28 15:16:14 2020 From: bburns at redhat.com (Bill Burns) Date: Tue, 28 Apr 2020 11:16:14 -0400 Subject: [Openinfralabs] Operate First OKRs and Manfisto In-Reply-To: References: Message-ID: Hopefully fixed now.... Bill On Fri, Apr 24, 2020 at 3:01 PM Marcel Hild wrote: > Looks like you're missing the commit - the merge request is empty :) > > https://gitlab.com/open-infrastructure-labs/openinfralabs-website/-/merge_requests/1 > > On Fri, Apr 24, 2020 at 8:22 PM Bill Burns wrote: > >> >> Is this what you need? >> >> >> https://gitlab.com/open-infrastructure-labs/openinfralabs-website/-/merge_requests >> >> cheers, >> Bill >> >> >> On Fri, Apr 24, 2020 at 2:16 PM Chris Long wrote: >> >>> could you post the MR link please Bill? >>> Chris Long >>> >>> Red Hat >>> >>> >>> Pillar Architect, EXD Infrastructure, >>> >>> >>> Enterprise eXperience and Delivery, Westford >>> Mobile: +603 400 7986 >>> IRC: chlong >>> >>> >>> >>> "Do what you love doing, with people who you like being with, to the >>> overall benefit of society - build individual and collective wealth in the >>> team." >>> >>> >>> On Fri, Apr 24, 2020 at 1:28 PM Bill Burns wrote: >>> >>>> >>>> I took the Operate First Manifesto that we had created for the Red Hat >>>> initiative and made a community version that I have added to the website >>>> git repo. I created a merge request to add it. Let me know if there are >>>> any issues with my request.... >>>> >>>> cheers, >>>> bill >>>> >>>> >>>> >>>> On Tue, Apr 21, 2020 at 12:32 PM Jimmy McArthur >>>> wrote: >>>> >>>>> Hi all! >>>>> >>>>> Last time we spoke we were in the process of moving OpenInfra Labs >>>>> over to Gatsby and setting the site up on Netlify. Unfortunately, that >>>>> deliverable was pushed a bit and I'm expecting that to occur this week. >>>>> After that, we'll plan to move the site over to its final home on Gitlab, >>>>> which is I think the preferred home for all of your development. Please let >>>>> me know who your repo admins should be and I'll make sure to set that up as >>>>> well. >>>>> >>>>> Re: the content suggestion below - yes! Love that there is some >>>>> interest in adding to the site content. I think this could probably end up >>>>> being either a blog post or a stand alone section on the site. Either of >>>>> which will be doable when we get the new structure in place. In the >>>>> meantime, can I suggest doing a PR against the existing site on github and >>>>> we can just add this content to the homepage? Once the new site is up, we >>>>> can look at moving things into sections or individual posts as your >>>>> community deems appropriate. >>>>> >>>>> Also worth mentioning, the OSF follows what we call the 4 Opens: >>>>> https://osf.dev/about/four-opens/ I thought it might help with your >>>>> operate first manifesto or if you think there is some content that could be >>>>> added from the manifesto to the 4 Opens, please feel free to contribute: >>>>> https://opendev.org/osf/four-opens/ >>>>> >>>>> Cheers, >>>>> Jimmy >>>>> >>>>> Marcel Hild wrote on 4/21/20 5:04 AM: >>>>> >>>>> If we invite people to contribute to >>>>> https://gitlab.com/open-infrastructure-labs/nerc-architecture I would >>>>> love to explain why we do it all in the open. >>>>> While the website https://openinfralabs.org/ is a good first start, >>>>> it certainly lacks some content. >>>>> >>>>> In the spirit of release early and often, how about putting a >>>>> community version of the operate first manifesto and the OKRs on that same >>>>> webpage? >>>>> >>>>> Is this domain the right place for it? Or should we grab >>>>> https://instantdomainsearch.com/#search=operatefirst >>>>> >>>>> >>>>> _______________________________________________ >>>>> Openinfralabs mailing listOpeninfralabs at lists.opendev.orghttp://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >>>>> >>>>> >>>>> _______________________________________________ >>>>> Openinfralabs mailing list >>>>> Openinfralabs at lists.opendev.org >>>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >>>>> >>>> _______________________________________________ >>>> Openinfralabs mailing list >>>> Openinfralabs at lists.opendev.org >>>> http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs >>>> >>> -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Thu Apr 30 16:02:28 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 30 Apr 2020 16:02:28 +0000 Subject: [Openinfralabs] What operational data and data streams should be gathered? In-Reply-To: References: <89eaeb20-6753-adb5-fab9-fa884f296b5c@bu.edu> Message-ID: <20200430160228.b4f2cgdgw7u3ojm5@yuggoth.org> On 2020-04-16 12:52:28 +0200 (+0200), Marcel Hild wrote: > I would start with monitoring data, i.e. all prometheus metrics > being collected. I agree that's a good route to take initially. Using OpenDev as an example, while obviously not the same systems and not necessarily constrained by the same risks, we try to keep all non-sensitive monitoring and trending data public, like: http://cacti.openstack.org/cacti/graph.php?action=view&local_graph_id=25&rra_id=all http://grafana.openstack.org/d/T6vSHcSik/zuul-status?orgId=1 > But those in itself are not really useful without a picture of the > infrastructure and access to the infrastructure. One thing we've done in that vein is to try to keep all our deployment and systems management notes (runbooks or whatever you like to term them) on a public site: https://docs.opendev.org/opendev/system-config/ We also try to publish logs for some services of interest if we can be certain they won't leak things like PII or credentials: https://nb01.openstack.org/ (sorry, self-signed cert on that one) > And you might need access to ticket systems, since you want to > correlate the metrics with incidents. Absolutely, though relying on a public incident/defect tracker does also mean you need to train your users to leverage privacy features for anything which may contain sensitive data, or to avoid putting such information in tickets and instead forwarding it via more confidential channels. It also means getting better about redacting certain classes of data either automatically or on request (and then dealing with fallout for the latter, treating that material as though it has leaked even if you've masked or deleted it after the fact to limit the damage). > My point is, we need to open up _all_ aspects of operations to > make it actually useful, otherwise it'll be just a pile of data. [...] For more general day-to-day operations, as well as scheduled maintenance or similar change activity, we've found it's useful to keep discussion on publicly-archived mailing lists and in publicly logged IRC channels so that they're easy to refer back to later. http://lists.opendev.org/pipermail/service-discuss/2020-April/thread.html http://eavesdrop.openstack.org/irclogs/%23opendev/%23opendev.2020-04-30.log.html http://eavesdrop.openstack.org/meetings/opendev_maint/2020/opendev_maint.2020-04-10-17.00.log.html We're also using an IRC bot which our sysadmins can command to log important status information to a Web page: https://wiki.openstack.org/wiki/Infrastructure_Status That allows us to easily publish notes about what we're doing which might have public impact, and we also tie it into a notification system which can echo messages in subscribed IRC channels or temporarily update their channel topics to reflect important service status information. Another major choice we've made is to perform installation and life-cycle management of a lot of our services through continuous deployment jobs in a public-facing CI/CD system: https://zuul.opendev.org/t/openstack/builds?pipeline=deploy It does require careful thought, however, to make sure you're not exposing anything which could compromise the integrity or security of those systems. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From mhild at redhat.com Thu Apr 30 16:19:22 2020 From: mhild at redhat.com (Marcel Hild) Date: Thu, 30 Apr 2020 18:19:22 +0200 Subject: [Openinfralabs] What operational data and data streams should be gathered? In-Reply-To: <20200430160228.b4f2cgdgw7u3ojm5@yuggoth.org> References: <89eaeb20-6753-adb5-fab9-fa884f296b5c@bu.edu> <20200430160228.b4f2cgdgw7u3ojm5@yuggoth.org> Message-ID: Wow, that's some good open data. Is there a single entry page, from which I could've discovered that myself? And is that all related to a single OpenStack cluster that's being run by the community or is it build related infrastructure? On Thu, Apr 30, 2020 at 6:02 PM Jeremy Stanley wrote: > On 2020-04-16 12:52:28 +0200 (+0200), Marcel Hild wrote: > > I would start with monitoring data, i.e. all prometheus metrics > > being collected. > > I agree that's a good route to take initially. Using OpenDev as an > example, while obviously not the same systems and not necessarily > constrained by the same risks, we try to keep all non-sensitive > monitoring and trending data public, like: > > > http://cacti.openstack.org/cacti/graph.php?action=view&local_graph_id=25&rra_id=all > > http://grafana.openstack.org/d/T6vSHcSik/zuul-status?orgId=1 > > > But those in itself are not really useful without a picture of the > > infrastructure and access to the infrastructure. > > One thing we've done in that vein is to try to keep all our > deployment and systems management notes (runbooks or whatever you > like to term them) on a public site: > > https://docs.opendev.org/opendev/system-config/ > > We also try to publish logs for some services of interest if we can > be certain they won't leak things like PII or credentials: > > https://nb01.openstack.org/ (sorry, self-signed cert on that one) > > > And you might need access to ticket systems, since you want to > > correlate the metrics with incidents. > > Absolutely, though relying on a public incident/defect tracker does > also mean you need to train your users to leverage privacy features > for anything which may contain sensitive data, or to avoid putting > such information in tickets and instead forwarding it via more > confidential channels. It also means getting better about redacting > certain classes of data either automatically or on request (and then > dealing with fallout for the latter, treating that material as > though it has leaked even if you've masked or deleted it after the > fact to limit the damage). > > > My point is, we need to open up _all_ aspects of operations to > > make it actually useful, otherwise it'll be just a pile of data. > [...] > > For more general day-to-day operations, as well as scheduled > maintenance or similar change activity, we've found it's useful to > keep discussion on publicly-archived mailing lists and in publicly > logged IRC channels so that they're easy to refer back to later. > > http://lists.opendev.org/pipermail/service-discuss/2020-April/thread.html > > > http://eavesdrop.openstack.org/irclogs/%23opendev/%23opendev.2020-04-30.log.html > > > http://eavesdrop.openstack.org/meetings/opendev_maint/2020/opendev_maint.2020-04-10-17.00.log.html > > We're also using an IRC bot which our sysadmins can command to log > important status information to a Web page: > > https://wiki.openstack.org/wiki/Infrastructure_Status > > That allows us to easily publish notes about what we're doing which > might have public impact, and we also tie it into a notification > system which can echo messages in subscribed IRC channels or > temporarily update their channel topics to reflect important service > status information. > > Another major choice we've made is to perform installation and > life-cycle management of a lot of our services through continuous > deployment jobs in a public-facing CI/CD system: > > https://zuul.opendev.org/t/openstack/builds?pipeline=deploy > > It does require careful thought, however, to make sure you're not > exposing anything which could compromise the integrity or security > of those systems. > -- > Jeremy Stanley > _______________________________________________ > Openinfralabs mailing list > Openinfralabs at lists.opendev.org > http://lists.opendev.org/cgi-bin/mailman/listinfo/openinfralabs > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Thu Apr 30 17:09:17 2020 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 30 Apr 2020 17:09:17 +0000 Subject: [Openinfralabs] What operational data and data streams should be gathered? In-Reply-To: References: <89eaeb20-6753-adb5-fab9-fa884f296b5c@bu.edu> <20200430160228.b4f2cgdgw7u3ojm5@yuggoth.org> Message-ID: <20200430170917.4gs42trydm4fiwgh@yuggoth.org> On 2020-04-30 18:19:22 +0200 (+0200), Marcel Hild wrote: > Wow, that's some good open data. > > Is there a single entry page, from which I could've discovered > that myself? It's not all aggregated in one place yet, unfortunately, though those sites tend to be mentioned in various places in the sysadmin docs we publish. Eventually we hope to have a lot more of it directly discoverable from the main https://opendev.org/ page. > And is that all related to a single OpenStack cluster that's being > run by the community or is it build related infrastructure? [...] We're running the collaboration services used by OpenStack and many other communities (including a majority of those represented by the OSF), so not actually a deployment of OpenStack software. This is why my earlier E-mail said it wasn't a perfect example, due to being different software and so different associated risks. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: