Re: [atomic-devel] Major image push for glibc?
On 19/02/16 17:14, Josh Berkus wrote: > Folks, > > Given the glibc exploit, it seems like we're going to need to push new > images across all Atomic projects which distribute images, no? > > What all does this consist of? ADB, the various Atomic Hosts (which > presumably will be taken care of by their respective RelEng teams), > anything else? > the ADB Box already includes the updated glibc, the build ran a few minutes after the update got released. yum install centos-release-scl yum install sclo-vagrant1 ; scl enable sclo-vagrant1 /bin/bash vagrant init projectatomic/adb vagrant up vagrant ssh -c "rpm -q glibc --changelog | grep -i cve-2015-7547" CVE-2015-7547 fix (#1296030). - Fix CVE-2015-7547: getaddrinfo() stack-based buffer overflow (#1296030). Connection to 192.168.121.69 closed. for the CentOS Atomic Host, we are going to look at rolling in the next update set from upstream ( including etcd/ flannel / kubernetes etc ) and get an image out in the coming days. This will likely become our Feb 2016 build ( we aim to get one every month ). regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc
Re: [atomic-devel] Thoughts on a website redesign
On 02/19/2016 12:11 PM, Josh Berkus wrote: > Also, WTF is the RSS feed for the blog? Isn't there one? https://github.com/projectatomic/atomic-site/issues/213 I'm CC'ing Tigert on this, because it keeps coming up. There IS a feed, it's just not very discoverable. Let's consider this very *ing urgent and get it fixed, please. As for the other - let's map out content-wise what we want, and then we can discuss designers, etc. Best, jzb -- Joe Brockmeier | Community Team, OSAS j...@redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ signature.asc Description: OpenPGP digital signature
Re: [atomic-devel] Major image push for glibc?
On 02/19/2016 11:14 AM, Josh Berkus wrote: Folks, Given the glibc exploit, it seems like we're going to need to push new images across all Atomic projects which distribute images, no? What all does this consist of? ADB, the various Atomic Hosts (which presumably will be taken care of by their respective RelEng teams), anything else? I just rebuilt all the images on hub.docker.com https://hub.docker.com/u/fedora/ They are now on Fedora 23 with latest glibc.
[atomic-devel] Major image push for glibc?
Folks, Given the glibc exploit, it seems like we're going to need to push new images across all Atomic projects which distribute images, no? What all does this consist of? ADB, the various Atomic Hosts (which presumably will be taken care of by their respective RelEng teams), anything else? -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Thoughts on a website redesign
On 02/19/2016 08:40 AM, Brent Baude wrote: On Fri, 2016-02-19 at 09:20 -0500, Colin Walters wrote: I've been thinking about the website and some improvements/changes we could make. I don't quite have the web skills to do this myself, but hoping to start some discussion and get someone involved who does =) Odd, me too! If people think this is an OK topic for atomic-devel, we'll keep it here. * First, rather than having Atomic Host itself at the toplevel and in the Get Started, I think we should have two flows: - You want to develop containers on your laptop This should primarily point to the ADB docs - You want to run containers on servers This should point to both https://github.com/openshift/openshift- ansible and https://github.com/kubernetes/contrib/tree/master/ansible as example references for cluster standup. This in turn should have Atomic Host as well as non-Atomic Hosts as an option. Link to the existing docs on install distributions via PXE on bare metal, cloud images, etc. * Talk about Kubernetes more, as it's foundational (Really we could use some sort of architecture diagram) * Link very prominently to our sister project OpenShift Origin So there's really *two* sets of flows we want, which is part of why I want to talk to a talented designer because I'm not sure how to make this work. 1. User Flow * You want to develop container apps * ADB, getting started guides * atomic.app * You want to deploy/manage container infra * Atomic Host * OpenShift Origin * Cockpit * You want to hack on Atomic projects * All the projects 2. Project Flow (link to docs *and* project) * Atomic Host * Fedora * CentOS * RHEL * RPM-OStree * ADB * Nulecule + Atomic.app * Cockpit * Kubernetes * OCI-hooks * etc. The reason for the two flows is that people have two main reasons to come to projectatomic.io; (a) looking for general information on how they can use containers in their development/infra, (b) looking for specific information on a specific Atomic project they heard about. This corresponds to two groups of people (a) folks who do Linux and/or Red Hat but aren't container-saavy, and (b) Docker users who want to know what we have to offer. * Move http://www.projectatomic.io/docs/ out into something like mkdocs, asciidoc, or whatever that's better suited to it? Or maybe each "subproject" like ADB, /usr/bin/atomic, should have its own docs section? Collin, We currently are talking with Josh and gang about this as well so you have my support on this suggestion. Specifically, we are talking about the container-best-practices material that IS written in asciidoc and lives under the projectatomic.io "shield" (so to speak). As Josh can attest, there are some technical limitations to this right now given the current setup. But perhaps, as you suggest, if we break out /docs as a whole, this allows us to explore some new ideas. Yeah. Right now this is gated on my ability to learn to hack Ruby Middleman, so it's going to be kind of slow if that's the route we have to take. Our proposal to Josh is that ideally we get to a point where a jenkens job would take our asciidoc source and create HTML from it upon merge to master. Thanks for bringing this up! * Have a steady stream of "tips and tricks"...maybe in the blog section? Yes. Also, WTF is the RSS feed for the blog? Isn't there one? -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Thoughts on a website redesign
On Fri, 2016-02-19 at 09:20 -0500, Colin Walters wrote: > I've been thinking about the website and some improvements/changes we > could make. I don't quite have the web skills to do this myself, but > hoping to start some discussion and get someone involved who does =) > > * First, rather than having Atomic Host itself at the toplevel and in > the Get Started, I think we should have two flows: > > - You want to develop containers on your laptop > This should primarily point to the ADB docs > > - You want to run containers on servers > This should point to both https://github.com/openshift/openshift- > ansible and > https://github.com/kubernetes/contrib/tree/master/ansible as > example references > for cluster standup. > This in turn should have Atomic Host as well as non-Atomic Hosts > as an option. > Link to the existing docs on install distributions via PXE on > bare metal, cloud images, etc. > > * Talk about Kubernetes more, as it's foundational (Really we could > use some sort of architecture diagram) > > * Link very prominently to our sister project OpenShift Origin > > * Move http://www.projectatomic.io/docs/ out into something like > mkdocs, asciidoc, or whatever that's better suited to it? Or maybe > each "subproject" like ADB, /usr/bin/atomic, should have its own docs > section? > Collin, We currently are talking with Josh and gang about this as well so you have my support on this suggestion. Specifically, we are talking about the container-best-practices material that IS written in asciidoc and lives under the projectatomic.io "shield" (so to speak). As Josh can attest, there are some technical limitations to this right now given the current setup. But perhaps, as you suggest, if we break out /docs as a whole, this allows us to explore some new ideas. Our proposal to Josh is that ideally we get to a point where a jenkens job would take our asciidoc source and create HTML from it upon merge to master. Thanks for bringing this up! > * Have a steady stream of "tips and tricks"...maybe in the blog > section? >
Re: [atomic-devel] Thoughts on a website redesign
On Fri, Feb 19, 2016 at 9:20 AM, Colin Walters wrote: > I've been thinking about the website and some improvements/changes we > could make. I don't quite have the web skills to do this myself, but > hoping to start some discussion and get someone involved who does =) > > * First, rather than having Atomic Host itself at the toplevel and in the > Get Started, I think we should have two flows: > > - You want to develop containers on your laptop > This should primarily point to the ADB docs > > +1. > - You want to run containers on servers > This should point to both > https://github.com/openshift/openshift-ansible and > https://github.com/kubernetes/contrib/tree/master/ansible as example > references > for cluster standup. > This in turn should have Atomic Host as well as non-Atomic Hosts as an > option. > Link to the existing docs on install distributions via PXE on bare > metal, cloud images, etc. > > +1. I think we need a landing page that summarizes options, answers why and how > * Talk about Kubernetes more, as it's foundational (Really we could use > some sort of architecture diagram) > > * Link very prominently to our sister project OpenShift Origin > > +1 > * Move http://www.projectatomic.io/docs/ out into something like mkdocs, > asciidoc, or whatever that's better suited to it? Or maybe each > "subproject" like ADB, /usr/bin/atomic, should have its own docs section? > > How about a subdomain docs.projectatomic.io /developers (adb content) /best-practices (under active development) /atomic-registry (under active development) /atomic-platform > * Have a steady stream of "tips and tricks"...maybe in the blog section? > >
[atomic-devel] Thoughts on a website redesign
I've been thinking about the website and some improvements/changes we could make. I don't quite have the web skills to do this myself, but hoping to start some discussion and get someone involved who does =) * First, rather than having Atomic Host itself at the toplevel and in the Get Started, I think we should have two flows: - You want to develop containers on your laptop This should primarily point to the ADB docs - You want to run containers on servers This should point to both https://github.com/openshift/openshift-ansible and https://github.com/kubernetes/contrib/tree/master/ansible as example references for cluster standup. This in turn should have Atomic Host as well as non-Atomic Hosts as an option. Link to the existing docs on install distributions via PXE on bare metal, cloud images, etc. * Talk about Kubernetes more, as it's foundational (Really we could use some sort of architecture diagram) * Link very prominently to our sister project OpenShift Origin * Move http://www.projectatomic.io/docs/ out into something like mkdocs, asciidoc, or whatever that's better suited to it? Or maybe each "subproject" like ADB, /usr/bin/atomic, should have its own docs section? * Have a steady stream of "tips and tricks"...maybe in the blog section?
