[atomic-devel] Pass available for GopherCon
All, I know it's kind of last-minute, but I have a pass available for GopherCon, if anyone can easily make it there on their own (travel funds not included). PM me. -- -- Josh Berkus Kubernetes Community Red Hat OSAS
[atomic-devel] Atomic is working on the minnowboard again
I haven't had a chance to try installing to the minnowboards in a while (3 months). In the meantime, something got fixed. They now install and boot correctly. Yay! -- -- Josh Berkus Kubernetes Community Red Hat OSAS
Re: [atomic-devel] Kubernetes manual setup
On 02/23/2018 10:43 AM, Matthew Miller wrote: > On Fri, Feb 23, 2018 at 10:16:46AM -0800, Jason Brooks wrote: >>> If we have a preferred non-manual way, we should encourage people to >>> use that, but I don't see what we lose from having good documentation >>> at a lower level too. >> That's totally awesome. Now someone needs to do that work. In the >> absence of that person, it's not dismissive to link them to a popular >> resource for manual installation. > > Of course -- but what I mean is saying "You wanted to know how to do > Kubernetes on Fedora Atomic Host? Go do Kubernetes the hard way!" > doesn't come off as very friendly to someone who doesn't know that > "Learn the hard way!" is a somewhat tongue-in-cheek meme. If > that's the best resource and we recommend it, let's recommend it with a > preface. Oh, I was planning to recommend Kubeadm. Kubeadm is good enough for most users, these days, and it's actually a good way to test new Kubernetes releases. And the Kubeadm team is enthusiastic enough to maybe offer us some help. My primary concern with making sure that Kube is available on FAH/CAH is that I want Kubernetes developers regarding AH as a reasonable target platform for development. We also want to make sure not to abandon our existing AH+Kube users, but presumably installation docs are not the primary thing those users need. I wouldn't *mind* having a "the hard way" doc for FAH/CAH, but I can't commit to putting in the time it would require to write it, since I'm not sure who the target user for it is. Someone who wants something "production" is going to install Origin, no? -- -- Josh Berkus Kubernetes Community Red Hat OSAS
Re: [atomic-devel] Kubernetes manual setup
On 02/21/2018 05:51 PM, Chris Negus wrote: > - Original Message - >> Works for me. > > Me too. If everyone is in agreement, I'll see what I can do with Jason's > suggestions. I don't mind writing and maintaining docs on the Kubernetes.io > site, if you all will review it and make sure I'm on the right track. Once I > put something together, I'll ask Jason and others to take a look at it. I'll help with this. Find me on kube-docs on slack? -- -- Josh Berkus Kubernetes Community Red Hat OSAS
Re: [atomic-devel] Proposing moving https://github.com/stefwalter/oci-kvm-hook into projectatomic
On 02/16/2018 11:23 AM, Colin Walters wrote: > Hi, > > In working on our CI (and just locally in containers in general), I > find https://github.com/stefwalter/oci-kvm-hook to be very, very > useful. Yes, there are other ways one can do it; see the thread in > https://github.com/stefwalter/oci-kvm-hook/issues/5 > > I propose moving it into our organization to raise its visibility and > have it not be "owned" by one person in general. > > Any thoughts/objections? (Or other ways people do qemu-in-containers?) Does Stef *want* it to be moved? It's his repo. -- -- Josh Berkus Kubernetes Community Red Hat OSAS
[atomic-devel] Atomic BOF at RH Summit
Folks, An Atomic BOF session has been confirmed for RH Summit in May. I will be organizing it since Sanja won't be at this year's Summit. Who will be at RH Summit? I'd like 4-6 people to talk about various Atomic projects before we take questions. -- -- Josh Berkus Kubernetes Community Red Hat OSAS
Re: [atomic-devel] [Fedocal] Reminder meeting : General Atomic Community Meeting
On 02/12/2018 08:00 AM, jber...@redhat.com wrote: > Dear all, > > You are kindly invited to the meeting: >General Atomic Community Meeting on 2018-02-19 from 16:00:00 to 17:00:00 > UTC > > > The meeting will be about: > This is the general Atomic community meeting, in order to coordinate across > projects and discuss topics of general interest. > > irc.freenode.net, #atomic > > Topics for the meeting should be decided on the atomic-devel@projectatomic.io > mailing list ahead of the meeting. > > > Source: https://apps.fedoraproject.org/calendar/meeting/6394/ Feh, there's supposed to be a different calendar item for this. I apparently didn't remove the old one correctly. -- -- Josh Berkus Kubernetes Community Red Hat OSAS
Re: [atomic-devel] Docker usage survey results
On 01/04/2018 06:10 AM, Joe Brockmeier wrote: > Did you ask about the number of hosts for this? I did not. Damn! That would have been a really good question. -- -- Josh Berkus Kubernetes Community Red Hat OSAS
[atomic-devel] Docker usage survey results
Atomic Team: I've prepared some graphs and a report from our docker usage survey: https://docs.google.com/document/d/1aC8uthOMrTLiYK3l5muUVKDnOO7Rich2JxJ0sd4LJ6o/edit?usp=sharing We'll discuss this tommorrow at the Fedora Atomic meeting (12:30 EST). -- -- Josh Berkus Kubernetes Community Red Hat OSAS
Re: [atomic-devel] [Fedocal] Reminder meeting : General Atomic Community Meeting
On 12/18/2017 08:00 AM, jber...@redhat.com wrote: > Dear all, > > You are kindly invited to the meeting: >General Atomic Community Meeting on 2017-12-25 from 16:00:00 to 17:00:00 > UTC Please ignore, we are obviously not having a meeting on Christmas. -- -- Josh Berkus Kubernetes Community Red Hat OSAS
[atomic-devel] Delay on blog post publication
Sinny, Dusty, Stephen: There's going to be a delay on posting to the projectatomic.io blog. We've moved to OpenShift Online Pro, but DNS propogation has been delayed, and we're waiting for the switchover before we can push more stuff. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Docker version updates planned?
On 12/13/2017 10:51 AM, Richard Alloway wrote: > Hi! > > I've been taking a look at Atomic OS in my "free" time and have noticed > that it is shipped with Docker 1.12.x and/or 1.13.x. > > Those branches appear to be deprecated. > > Are there any plans to move to the 17.x.x series (Docker CE/EE)? If you have opinions on this, can you fill out this survey? http://www.projectatomic.io/blog/2017/11/docker-usage-survey/ -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] [Fedocal] Reminder meeting : General Atomic Community Meeting
On 11/22/2017 11:55 AM, Josh Berkus wrote: > Agenda: > > * KubeCon Plans: talks, demos, sessions, salons, booth duty. > > * Telling a good developer story: How do our docker-alternative tools > integrate? > > * CAH Update > And minutes from the meeting today: https://www.centos.org/minutes/2017/November/atomic.2017-11-27-16.02.html https://www.centos.org/minutes/2017/November/atomic.2017-11-27-16.02.log.html -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] [Fedocal] Reminder meeting : General Atomic Community Meeting
Agenda: * KubeCon Plans: talks, demos, sessions, salons, booth duty. * Telling a good developer story: How do our docker-alternative tools integrate? * CAH Update Anything else? On 11/20/2017 08:00 AM, jber...@redhat.com wrote: > Dear all, > > You are kindly invited to the meeting: >General Atomic Community Meeting on 2017-11-27 from 16:00:00 to 17:00:00 > UTC > > > The meeting will be about: > This is the general Atomic community meeting, in order to coordinate across > projects and discuss topics of general interest. > > irc.freenode.net, #atomic > > Topics for the meeting should be decided on the atomic-devel@projectatomic.io > mailing list ahead of the meeting. > > > Source: https://apps.fedoraproject.org/calendar/meeting/6394/ > > -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Atomic Host for ARM
On 11/10/2017 12:53 PM, Iván Chavero wrote: > El vie, 10-11-2017 a las 11:34 -0800, Josh Berkus escribió: >> On 11/09/2017 05:37 PM, Iván Chavero wrote: >>> >>> Hello, I want to use Atomic Host on a Cubietruck but i can't find >>> any >>> images for ARM. >>> >>> I've checked and just found ISO and vagrant files and cloud images >>> for >>> x86_64, looked for >>> >>> guides on how to build the image and i couldn't find any. >>> >>> >>> Can somebody give me pointers on where to find the ARM images or >>> guides >>> on how to build them? >> >> So the good news is that we'll have images and official support for >> ARM64 with the release of Fedora 27. >> >> The Cubie is 64-bit ... is it real ARM8? > > The Cubie is Cortex-A7 (ARMv7-A) 32bits. > > I would like to learn how to build the images, can you give me some > pointers? Sorry for nonresponsiveness, we've been working on the Fedora 27 Atomic release. Will have pointers for you soon. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Getting rid of obsolete images from projectatomic dockerhub
All, Per the community meeting today, I will be purging obsolete images from the /projectatomic/ namespace on Dockerhub. By my view, this includes: atomicapp atomic-registry-install atomic-registry-quickstart nulecule-library ... and 14 repositories for specific atomicapps. If anyone has any objections to deleting any of these, please let me know them by the end of the week. Thanks! -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Atomic General Meeting minutes
Minutes: https://www.centos.org/minutes/2017/November/atomic.2017-11-13-16.05.html Log: https://www.centos.org/minutes/2017/November/atomic.2017-11-13-16.05.log.html -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Atomic General Community Meeting Monday 1600UTC
Atomicans, We have an Atomic General community meeting scheduled for tommorrow, 1600 UTC/1100 EST, channel #atomic on irc.freenode.net. We have two short things on the agenda: * CentOS Atomic Host Update * Improving atomic install --system -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Atomic Host for ARM
On 11/09/2017 05:37 PM, Iván Chavero wrote: > > Hello, I want to use Atomic Host on a Cubietruck but i can't find any > images for ARM. > > I've checked and just found ISO and vagrant files and cloud images for > x86_64, looked for > > guides on how to build the image and i couldn't find any. > > > Can somebody give me pointers on where to find the ARM images or guides > on how to build them? So the good news is that we'll have images and official support for ARM64 with the release of Fedora 27. The Cubie is 64-bit ... is it real ARM8? -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Help us decide how you will install Docker
Atomic Host users and friends: We need your help to decide how Docker will be installed & run in Fedora Atomic Host in the future. Survey: https://goo.gl/forms/2C9qFOUEIfJaGkCp2 THE WAY IT IS NOW: one specific Docker version ships with Fedora Atomic Host, and is included in the OSTree and all update. Currently it is 1.13. In CentOS, there is an older Docker version, plus a package called "docker-latest" which includes 1.13. CRI-O and alternate container runtimes do not ship with Fedora Atomic Host, except for runc with systemd for running system containers. THE WAY IT MIGHT BE: We could stop shipping any version of Docker with Fedora Atomic Host, and make it so that all container runtimes aside from the basic runc are installed as system containers. ADVANTAGES of the change: * Smaller base OS image/OStree * Fewer updates to the base OS * Easier for users to run alternate versions of Docker * Easier for users to run alternate container runtimes DISADVANTAGES of the change: * Extra install step when setting up a new Atomic Host * Docker no longer gets updates by "atomic host upgrade" Note that making this change in Fedora Atomic Host does not guarantee that the same change will be made downstream in CentOS Atomic Host or Red Hat Atomic Host. Help us figure out what to do, fill out the survey. https://goo.gl/forms/2C9qFOUEIfJaGkCp2 -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Minutes for Fedora Atomic meeting
here: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-11-08/fedora_atomic_wg.2017-11-08-16.30.html full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-11-08/fedora_atomic_wg.2017-11-08-16.30.log.html -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] a better place for system container images?
On 11/06/2017 08:29 AM, Giuseppe Scrivano wrote: > Dusty Mabe <du...@dustymabe.com> writes: > >>>> - create a projectatomic-devel organization and put them under there >>>> - put them under projectatomic/ but add devel or upstream in the name of >>>> each image. >>> would a tag be enough? >> My personal opinion is no. Not many people inspect tags when using images. > they will still need to specify the tag when pulling or installing the > image. It is something like: > > atomic pull --storage ostree docker.io/projectatomic/etcd:devel > > instead of: > > atomic pull --storage ostree docker.io/projectatomic/etcd-devel > > The problem with this is that there's no update to the tag when a new devel build is pushed. This will make it hard to make sure you're pulling the most recent image for testing. Maybe tag with ##devel? e.g. docker.io/projectatomic/etcd:0.3devel -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Changes, discussion for Fedora Container Guidelines
The following issues are all straightforward changes to the guidelines, which I will be adding to the document unless someone objects: https://pagure.io/atomic-wg/issue/326 https://pagure.io/atomic-wg/issue/283 https://pagure.io/atomic-wg/issue/367 https://pagure.io/atomic-wg/issue/327 There is also a long discussion into clarity and improvements we need to make on the Help File: https://pagure.io/atomic-wg/issue/354 I've added that for the next meeting. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] /sysroot is full - Can we clean, resize it
On 10/27/2017 07:03 AM, Charles Moulliard wrote: > Many thanks. > > - I will try to upload Fed Atomic 26 on our OpenStack platform > - Here is the info required > : https://gist.github.com/cmoulliard/07866a4f89804cfdd6de863487f24a88 > - I will look to your suggestions: move to f26 > > Are you running docker with overlayfs? I don' think so > Then it's much simpler; you just need to grow the / volume using lvextend. So: lvextend -L6G /dev/mapper/atomicos-root xfs_growfs /dev/mapper/atomicos-root This is, BTW, why we're switching to "one big volume" by default in F27. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Atomic General Community Meeting: call for items
Folks: As usual, Atomic General Community meeting will be this Monday, at 12:00 EDT / 1600 UTC. This meeting will be run by Jason Brooks. Please post replies with items that you have for the meeting. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Fedora Atomic WG meeting minues
Minutes here: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-25/atomic_wg.2017-10-25-17.02.html Full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-25/atomic_wg.2017-10-25-17.02.log.html -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] [Fedora Atomic] WG Membership Overhaul (Issue #
Fedora Atomic folks: I've updated our list of members here: https://fedoraproject.org/wiki/Atomic_WG#Working_Group_Members_and_Points_of_Contact Please see this issue for discussion of changes we need to make for the list of members: Particularly, if you are involved with Fedora Atomic and aren't on the list of members, you should probably add yourself. https://pagure.io/atomic-wg/issue/363 -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Looking for projects for new Fedora-Origin hardware
Folks, So we finally have our blades, which were earmarked for the "FOSP" project. Events have moved on a bit, though, so I wanted to check with the Atomic community for projects we could do targeting these servers. This also affects how the infra team sets them up (networking, base OS etc.). The original plan for this cluster was to test deploying and scaling up Fedora-Atomic-Origin, and possibly to supply a test farm for apps developed to run in that environment. That use is still possible provided we can get someone to admin it (hint, hint). Hardware: * 16 blades, each 10 cores with 128GB RAM and 240GB onboard storage Project Requirements: * must somehow involve Fedora Atomic and OpenShift Origin * there is no 24/7 support for the hardware, so production hosting uses are probably not feasible * there is no administrative software for the cluster (yet), so helping implementing/deploying that may become part of your project Given the above requirements, does anyone in the wide Atomic community have projects for which they could use a cluster, or part of a cluster? -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Atomic General meeting minutes
https://meetbot.fedoraproject.org/atomic/2017-10-16/atomic-community.2017-10-16-16.02.html -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Atomic General Meeting today
We have a meeting on October 16, at 1600UTC / 12:00 Eastern. (sorry for late notice on this, the ML seems to have eaten my notice from last week) Agenda so far: * Brainstorming new hardware uses for blades * Upcoming events * DockerCon * KubeCon * OSS-EU * CRI-O 1.0 More topics? Bring them to the meeting. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] what are the plans for devconf?
So ... For everyone else, care to share what talks you plan to submit? -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] what are the plans for devconf?
On 10/06/2017 05:19 AM, Tomas Tomecek wrote: > Yes, I am. That's why I'm asking. If you don't submit one, I'll make > sure our team does it. I would love to help with a workshop led by your team. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] 2wk atomic release candidate: 20171003
On 10/05/2017 05:14 PM, Josh Berkus wrote: > Dusty, all: > > So I did an upgrade-and-rollback test today, and the results are kind of > alarming: I can't rollback. > > Basically, on a minnowboard, with the current release, if you upgrade, > you are forced to pave and re-install the system to restore it to operation. OK, less alarming now. A cold reboot (power off) allows you to roll back to the prior release and log into the system. For some reason, a hot restart does not. Somehow, changes are being cached for the boot sector or grub? Or something? -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] 2wk atomic release candidate: 20171003
Dusty, all: So I did an upgrade-and-rollback test today, and the results are kind of alarming: I can't rollback. Basically, on a minnowboard, with the current release, if you upgrade, you are forced to pave and re-install the system to restore it to operation. I'm not in the office tommorrow ... but in the meantime we might want to warn users in case they have hardware sufficiently similar to minnowboards. Will put that in the blog announcement. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] what are the plans for devconf?
On 10/05/2017 03:58 AM, Tomas Tomecek wrote: > Hey guys, > > since DevConf CfP is now open, what talks are you planning to do? > > For our team (containerization) we are planning to finish proposals this > sprint, which I hope we'll manage to do next week. > > Specifically, I'm interested to hear whether you are planning to do a > workshop on building images. *should* we do one? Are you interested in helping with one? -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] 2wk atomic release candidate: 20171003
On 10/03/2017 04:11 PM, Josh Berkus wrote: > On 10/03/2017 11:34 AM, Dusty Mabe wrote: >> Tomorrow we will attempt to release the 20171003 images. >> These images contain the following ostree version/commit: >> >> 26.141 >> 541abd650d1ffb3929e2ba8114436a0b04ee41da76a691af669dd037589a1421 >> >> The atomic host VM images are here: >> >> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20171003.0/compose/CloudImages/x86_64/images/ >> >> The ISO image is here: >> >> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20171003.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-26-20171003.0.iso > > Hardware test FAIL: https://pagure.io/atomic-wg/issue/345 > BTW, I'm thinking I should pick up a less wonky small server for these HW tests; I never trust that the minnowboard behaves like a normal x86 server. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] 2wk atomic release candidate: 20171003
On 10/03/2017 11:34 AM, Dusty Mabe wrote: > Tomorrow we will attempt to release the 20171003 images. > These images contain the following ostree version/commit: > > 26.141 > 541abd650d1ffb3929e2ba8114436a0b04ee41da76a691af669dd037589a1421 > > The atomic host VM images are here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20171003.0/compose/CloudImages/x86_64/images/ > > The ISO image is here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20171003.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-26-20171003.0.iso Hardware test FAIL: https://pagure.io/atomic-wg/issue/345 -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Minutes for today's meeting
Summary: https://meetbot-raw.fedoraproject.org/atomic/2017-10-02/atomic-community.2017-10-02-16.02.txt Raw: https://meetbot.fedoraproject.org/atomic/2017-10-02/atomic-community.2017-10-02-16.02.log.html -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Atomic Community Meeting October 2: call for agenda items
On 09/29/2017 09:18 AM, Josh Berkus wrote: > All: > > We have a meeting on October 2, at 1600UTC / 12:00 Eastern. > > Please add your agenda items here. As a reminder, this isn't just about > Atomic Host; all Atomic projects are encouraged to join/discuss. > > AGENDA: > > - CRI-O on Atomic Host > - Container for Openshift-Ansible? > - CAH release last week > - YOUR ITEM HERE > Updated: - CRI-O on Atomic Host - Container for Openshift-Ansible? - CAH release last week - Website migrations - Shutting down ASK/activating serverfault Anything else? -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Atomic Community Meeting October 2: call for agenda items
All: We have a meeting on October 2, at 1600UTC / 12:00 Eastern. Please add your agenda items here. As a reminder, this isn't just about Atomic Host; all Atomic projects are encouraged to join/discuss. AGENDA: - CRI-O on Atomic Host - Container for Openshift-Ansible? - CAH release last week - YOUR ITEM HERE -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Who got accepted to Kubecon?
Folks: - who got a talk accepted to KubeCon US? - who didn't get a talk accepted but wants to go anyway? Let me know, I need to figure out passes for the conference. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Outreachy intern?
Folks, Fedora is participating in Outreachy this season, which gives us the opportunity to recruit an intern if we want one. This would mean both coming up with some suitable project proposals, *and* a couple of us volunteering as mentors for the spring. Unlike GSoC, outreachy interns aren't limited to hacking core code. They can also do documentation, infrastructure projects, even marketing/advocacy. Is this something we want to do? -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Atomic Community Meeting: call for Topics, Moderator
On 09/11/2017 03:20 PM, Josh Berkus wrote: > Folks, > > First, please post any topics you have for Monday's Atomic Community > Meeting. Among other things, we should probably talk about CRI-O > support across the various projects. > > > Second, can I have a volunteer to be chair/moderator? I'll be on > vacation the day of the meeting. I'll try to make it anyway, but I'd > like someone else as moderator in case I don't. > Bump. Issues? Lead? -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Atomic Community Meeting: call for Topics, Moderator
Folks, First, please post any topics you have for Monday's Atomic Community Meeting. Among other things, we should probably talk about CRI-O support across the various projects. Second, can I have a volunteer to be chair/moderator? I'll be on vacation the day of the meeting. I'll try to make it anyway, but I'd like someone else as moderator in case I don't. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Can anyone do DevOpsDays Boston?
This is kinda last-minute, but I'm hoping some folks in the Boston area might be interested in proposing an Open Spaces session on Atomic, new container tools, or other of our projects at DevOpsDays Boston. If you're interested in going, I can cover your registration from community funds. However, you need to promise to pitch an Open Spaces session. https://www.devopsdays.org/events/2017-boston/program/ -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] 2wk atomic release candidate: 20170905
On 09/05/2017 03:36 PM, Dusty Mabe wrote: > The ISO image is here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20170905.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-26-20170905.0.iso Installation test on minnowboard passed, including a reboot. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Shirts for Atomic contribs
Folks, If you contribute to Atomic projects, and you've done or are doing booth duty at one or more conferences, you are entitled to a Project Atomic oxford shirt or a fleece. Please fill out this form if you are entitled and want one. Land's End is having a sale, so I'm doing a large order soon. https://goo.gl/forms/118rz8430fE1Xz8f1 Note that I have three undelivered shirts for people whose names I've lost, so y'all speak up. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Atomic community meeting next week, or not?
On 08/29/2017 10:20 AM, Joe Brockmeier wrote: > +1 to skip > On Sun, Aug 27, 2017 at 10:38 PM Dusty Mabe <du...@dustymabe.com OK. see y'all on the 16th. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] RC hardware test -- Fail
here's been more on this; let's track it through this issue: https://pagure.io/atomic-wg/issue/324 TL;DR: current 2-week release is fatal for the minnowboard HW. On 08/22/2017 11:17 AM, Josh Berkus wrote: > On 08/22/2017 06:41 AM, Colin Walters wrote: >> >> >> On Mon, Aug 21, 2017, at 10:23 PM, Josh Berkus wrote: >>> On 08/21/2017 04:17 PM, Josh Berkus wrote: >>>> Dusty, >>>> >>>> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20170821.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-26-20170821.0.iso >>>> >>>> Passed the minnowboard install test.\ >>>> >>>> Some new warnings, about null bytes in the image shell script. Do we care? >>>> >>> >>> Reported too soon. The image installs fine, but won't boot once installed. >> >> Is the symptom similar to >> https://bugzilla.redhat.com/show_bug.cgi?id=1482922 ? >> > > Not exactly; I don't get any grub output at all. It looks to me like > Grub is just completely failing to boot. > -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] RC hardware test -- Fail
On 08/21/2017 04:17 PM, Josh Berkus wrote: > Dusty, > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20170821.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-26-20170821.0.iso > > Passed the minnowboard install test.\ > > Some new warnings, about null bytes in the image shell script. Do we care? > Reported too soon. The image installs fine, but won't boot once installed. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Lunch on Thursday for team meeting during Flock?
Folks, Since pretty much no evenings are available, could folks meet up durning Thursday Lunch to do an Atomic WG meeting/discussion? -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Call for topics: Atomic Community Meeting Aug 21
Folks, We have our regularly scheduled Atomic Community Meeting at 1600 UTC on Monday, August 21. Please reply to this email with any discussion topics you may have. See you on #atomic then. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Who wants to go to Copenhagen?
Atomic folks: We could use some community members to help staff the RedHat/Atomic/Openshift booth at DockerCon EU. Copenhagen, DK, Oct 16-17. Let me know if you're interested; passes available, travel funding possible. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] 2wk atomic release candidate: 20170807
On 08/07/2017 08:18 AM, Dusty Mabe wrote: > Tomorrow we will attempt to release the 20170807 images. > These images contain the following ostree version/commit: > > 26.101 > f6331bcd14577e0ee43db3ba5a44e0f63f74a86e3955604c20542df0b7ad8ad6 > > The atomic host VM images are here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20170807.0/compose/CloudImages/x86_64/images/ > > The ISO image is here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20170807.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-26-20170807.0.iso Bare metal install successful. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Reaching the Fedora Audience
On 08/03/2017 03:07 PM, Justin W. Flory wrote: > On 08/03/2017 04:42 PM, Dusty Mabe wrote: >> It would be nice if more people in the Atomic/Kubernetes/OpenShift Sphere >> could reach the Fedora Audience better. There is a nice way to get your >> blog aggregated into http://fedoraplanet.org/. You can easily add it by >> following >> the directions here: >> >> https://fedoraproject.org/wiki/Planet?rd=Planet_HowTo#How_to_join_the_Planet >> >> Please add yourself if you have good material to share :) >> >> Dusty >> > > On top of this, the Fedora Community Blog would also be a super nice > place to see more Fedora-specific Atomic content. Right now, there is an > Atomic category, but it looks a little empty right now. > > https://communityblog.fedoraproject.org/category/atomic/ Given that we just created the Atomic category *this week* ... -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Python 2 and Atomic Host
On 08/02/2017 10:40 AM, Micah Abbott wrote: > On 08/02/2017 10:20 AM, Colin Walters wrote: >> Hey, just a quick note here that I've been waging a fight to keep >> /usr/bin/python as Python 2 for Fedora Atomic Host, and in >> general to support Ansible. >> >> This was covered on LWN: >> https://lwn.net/Articles/729366/ >> >> For openshift-ansible I think we're generally OK with supporting >> Python 3 and working through that. But if you're a user of >> Atomic Host + Ansible with Python 2, it'd be useful to respond >> here to let me know this fight is worth continuing =) > > Yup, that's me. The tests we maintain in the 'atomic-host-tests' > repo[0] are all Ansible. Counter-argument: Ansible container and/or system container. That's how we're supposed to handle these library issues, no? -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Docs VFAD results
All, First, I'd like to thank everyone who participated in our first Documentation VFAD. Especially our new community participants! In this VFAD, we: 1. finished the outline for the Administrator Guide 2. added links for existing material to the outline A full copy of the notes from the session is here: http://etherpad.osuosl.org/fedora_atomic_docs_vfad The completed outline is here: https://github.com/projectatomic/atomic-host-docs/blob/master/outline.txt Our next steps will be preparing the atomic-host-docs repo for the Flock workshop, including preparing issues for each of the documentation "pages" so that people can begin work on them. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Atomic Host Docs VFAD on Friday information & preparation
Folks: As scheduled, we will be having a Virtual Fedora Activity Day focused on the Atomic Host documentation this Friday, July 28th. The day starts at 13:30 UTC (9:30 EDT, 19:00 IST), with a video conference before we split up for work. The rest of the program may be found on this etherpad: http://etherpad.osuosl.org/fedora_atomic_docs_vfad Before you come to the VFAD, please read that document. If you have a chance beforehand -- or if you cannot make it to the VFAD at all -- please comment on the proposed documentation content in the etherpad. Make sure and put your name in for your color so we know whose comments belong to whom. (note to folks on the cloud@ mailing list: we will soon stop using this mailing list for Atomic stuff. please sign up for atomic-devel) -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] 2wk atomic release candidate: 20170723
On 07/24/2017 07:50 AM, Dusty Mabe wrote: > Tomorrow we will attempt to release the 20170723 images. > These images contain the following ostree version/commit: > > There are a lot of updates in this release, including a new kernel > and brand new major release of kubernetes that should fix earlier > issues that we were having with starting the apiserver. Please help > us test this thoroughly before release. Tested the ISO on bare metal. Successfully installed, and installed kubeadm containerized. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Last-minute agenda items for atomic community meeting
Atomic community meeting in 1 hour (12noon EDT): * Changes to Fedora Atomic Host Mailing lists, IRC * Moving MLs to Fedora hosting * Fedora Kubernetes-SIG * Atomic Registry (if Aaron can make it) Anyone else have something? Meeting on IRC, irc.freenode.net, #atomic -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] No Community Meeting this week
Atomic folks: We don't have an agenda this week, so I'm cancelling the Community Meeting. Have an hour of your Monday back. See you in 2 weeks. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Upcoming Events: call for speakers/staff plus funding & swag
On 06/29/2017 03:32 PM, Derek Carter wrote: > Does the fleece offer count for events not in the list above, or is it > just for the events with atomic/RH presence? > > I'm doing a presentation at OpenWest in July. It counts for OpenWest, but I may draft you for booth duty if there's a booth (if not, you get a pass). -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Breaking up our tools container image
On 06/27/2017 02:01 PM, Ben Breard wrote: > Today we ship a “tools” container that’s *really* large, specifically > it’s about 1.5 GB on disk. The feedback I’ve gotten from users is that > it's too large to be useful and they try to avoid it. This of course > makes me sad and I think we should take another look at it. Primarily > this container contains debugging, performance, support utilities > (sosreport), as well as man pages for packages only shipped on Atomic > Host. I think splitting it up along these lines makes sense and will be > intuitive for users. That said, there’s a fine line between some of the > debugging and performance tools, so after looking at the package list, I > think it makes sense to keep those together in the “2.0” tools container. > Here’s what I’m proposing and would love feedback on: So, given that this is a concern for upstream, I support breaking up the image into logical parts. Additionally, what about basing each image on RHAtomic Image and/or Fedora/CentOS minimal image? That might bring the size down further, altough it's possible that the packages involved would just re-install all of that content anyway. > 1) Drop all packages from rhel-tools that exist only for documentation > purposes. [1] +1 on the idea, I don't understand your paste output though. > 2) Trim down the included packages to this list: [2] > Basically leaves the full capabilities and results in a 476M image which > is a huge step in the right direction. No objections in general. We might want to look at breaking this down further into six contianers: - build-tools (gcc, git, glibc etc) - debug-tools (ltrace, gdb, crash, sos, etc.) - cli-tools (which, bash-completion, tar, etc.) - admin-tools ( parted, passwd, pciutils, xfsprogs, etc.) - net-tools (net-tools, ethtool, tcpdump, etc.) - perf-tools (perf, sysstat, systemtap, etc.) > 3) Create a dedicated image for sosreport utilities. > Includes redhat-support-tool, sos, & strace and depending on which base > image we use it’s either 120M (rhel7-atomic) or 212M (rhel7) > This may only be appealing on the rhel side of the house, but if there’s > value for fedora & centos, it would be trivial to also offer it. sos & strace have appeal, redhat-support-tool less so. For Fedora and CentOS, I would tend to see those as going into the general tools package in (2), but don't have strong objections to it being its own container. > > 4) Optionally create a man pages container. > I really want feedback to see if anyone thinks this is useful. RPM & yum > provide a nodocs capability, but they lack a docs only setting which is > what we need. It works quite well to tar up the man-db for our existing > rhel-tools image and inject it in our minimal base image. This results > in a docs only container that’s ~100M on disk. It would be a slight > hacky process to release something like this, but we could do it. I just I'm in favor of a man pages contianer, but it might violate FLIBS policy. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Upcoming Events: call for speakers/staff plus funding & swag
Folks: The following events are important to us for promoting Atomic Host, Cockpit, and other technologies. I am looking for speakers, booth staff, and other participants. Both travel funding and assistance with proposals and talks is available for all of these events. Additionally, any Project Atomic contributors who work an event are entitled to a spiffy Project Atomic embroidered shirt or a fleece (some advance notice required to order, may take a long time to get them to Asia and Europe) (If I promised you one, and you didn't get it, please ping me offlist). Please note that there's a couple of CfP deadlines in the below, coming up soon. Please share with teammates as appropriate. Open Source Summit Los Angeles (LinuxCon): Dates: September 11-14 Needed: Booth Staff, Additional people for Atomic BOF http://events.linuxfoundation.org/events/open-source-summit-north-america Linux Plumber's Container Microconference Dates: September 13-15 Location: Los Angeles, CA, next to OSSummit Needed: Linux internals participants (will ask for booth duty at OSS-LA) http://www.linuxplumbersconf.org/2017/containers-microconference-accepted-into-linux-plumbers-conference/ ContainerCamp UK Dates: September 9 Location: London Needed: Speakers, Booth Staff CfP Deadline: **July 14, 2017** https://2017.container.camp/uk/ Open Source Summit Prague Dates: October 23-25 Location: Prague Needed: Speakers, BOF organizer, Booth Staff CfP Deadline: **July 8, 2017** http://events.linuxfoundation.org/events/open-source-summit-europe KubeCon North America Dates: December 6-8 Location: Austin, TX Needed: Speakers, Booth Staff CfP Deadline: August 21 http://events.linuxfoundation.org/events/cloudnativecon-and-kubecon-north-america Please respond if you can help with any of the above! Thanks! -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Atomic General Meeting Minutes
Summary: https://meetbot-raw.fedoraproject.org/atomic/2017-06-26/project_atomic_community_meeting.2017-06-26-16.02.html Detail: https://meetbot-raw.fedoraproject.org/atomic/2017-06-26/project_atomic_community_meeting.2017-06-26-16.02.log.html Thanks to all for attending! -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Kubernetes vs. Origin for upstream
Folks: We started this discussion at the last Atomic General meeting, but didn't resolve it. You can find the actual discussion here: http://etherpad.osuosl.org/atomic-community-meeting The Problem Currently we kind of promote Kubernetes as our main orchestrator for upstream Atomic (Fedora Atomic and Centos Atomic). However, we also promote upstream Atomic as a plaform for Origin. There are two problems with our current approach: 1. we don't realistically have the resources to package, document, and promote both upstream Kubernetes and Origin on upstream Atomic. 2. not having a default option with clear & complete documentation confuses users and doesn't present them with a complete system. As a result, we need to decide which platform is the one we promote first, and ensure has a complete and up-to-date toolchain. Kubernetes First Advantages: * more upstream/cutting edge stuff * better able to connect with, promote through, Kubernetes community and developers * kubernetes is much better known than OpenShift * FLIBS, CP containers mostly work on Fedora Disadvantages: * most Red Hat staff work with OpenShift * could not count on help from downstream (RHEL Atomic) * doesn't integrate with some of our other projects (e.g. gluster storage) Origin First Advantages: * nice GUI * better app developer experience * better documentation for administration * able to combine work with downstream folks Disadvantages: * lose most of Kubernetes developer/user community * installation on Fedora is problematic and poorly maintained * Atomic not seen as next-gen platform * would need to refactor FLIBS, CP to have Origin-worthy containers == So, thoughts? And more discussion on Monday. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Reminder, call for Agenda items: Atomic General Community Meeting on Monday
Atomic General Community Meeting Monday, 12:00 EDT / 1600 UTC irc.freenode.net, #atomic Please send me agenda items. Also, we will continue the discussion around Kubernetes vs. Origin. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] CentOS Atomic Host tree numbering is inconsistent
On 06/19/2017 11:20 AM, Jason Brooks wrote: > On Mon, Jun 19, 2017 at 10:53 AM, Josh Berkus <jber...@redhat.com> wrote: >> Jason, KB, etc.: >> >> This is the beginning of last month's announcement: >> >> An updated version of [CentOS Atomic >> Host](https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) >> (tree version 7.20170428), is >> now available ... >> >> And this is this month's: >> >> An updated version of CentOS Atomic Host (tree version 7.1705), is now >> available[1]. CentOS Atomic Host is a lean operating system designed to >> run ... >> >> See the problem here? How is a user supposed to keep track of upgrades? > > We did change the versioning, I should have mentioned it in the message. > > It's not inconsistent, though, in that both are date-based, the last > indicates Apr 2017, this one indicates May 2017. We talked about this > in our last SIG meeting -- the rest of centos revs monthly, with this > same major-version.YYMM scheme, and we've switched to that scheme for > CentOS Atomic. > > Our images have actually carried this 1705, 1704, 1703 number for > quite a while now, and this should make it easier for users to match > up images with the version of the tree they contain. OK. Mind writing a para on this for the blog post? -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] CentOS Atomic Host tree numbering is inconsistent
Jason, KB, etc.: This is the beginning of last month's announcement: An updated version of [CentOS Atomic Host](https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) (tree version 7.20170428), is now available ... And this is this month's: An updated version of CentOS Atomic Host (tree version 7.1705), is now available[1]. CentOS Atomic Host is a lean operating system designed to run ... See the problem here? How is a user supposed to keep track of upgrades? -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Shutting down ask.projectatomic.io, moving to StackExchange, needs your help
On 06/15/2017 02:37 PM, Josh Berkus wrote: > On 06/14/2017 06:59 AM, Joe Brockmeier wrote: >> >> On Tue, Jun 13, 2017 at 1:40 PM Josh Berkus <jber...@redhat.com >> <mailto:jber...@redhat.com>> wrote: >> >> All: >> >> In this week's Atomic Community Meeting, we voted to shut down >> ask.projectatomic.io <http://ask.projectatomic.io>. There's two >> parts to this: >> >> 1. Us being ready to take questions on StackExchange/StackOverflow. >> >> 2. Actually disabling the page and redirecting people. >> >> For the first part, that means I need as many Atomic contributors as >> possible to sign up for both StackOverflow and >> unix.stackexchange.com <http://unix.stackexchange.com>. >> Once there, I need you all to do the following things: >> >> >> Serverfault.com seems more appropriate for Atomic. (I believe they're >> all part of the same network, but you have to log in separately once >> you've set up an account, IIRC.) >> >> Serverfault has a fair number of Atomic questions. > > Joined. > > Do we want to push ServerFault, though? I ask because of the three, > ServerFault seems to have comparatively poor googleability. > > On the other hand, the number of existing questions there around Atomic > Host dwarfs the other two platforms, so maybe we do. I was mistaken. I'm getting a lot of full-text hits for "atomic" and "host" separately; there are, in fact, relatively few questions about atomic host. > > I'm asking because I want to have *one* site that we recommend to users. > We'll troll for questions on all three sites, of course. > -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Shutting down ask.projectatomic.io, moving to StackExchange, needs your help
All: In this week's Atomic Community Meeting, we voted to shut down ask.projectatomic.io. There's two parts to this: 1. Us being ready to take questions on StackExchange/StackOverflow. 2. Actually disabling the page and redirecting people. For the first part, that means I need as many Atomic contributors as possible to sign up for both StackOverflow and unix.stackexchange.com. Once there, I need you all to do the following things: * Look for any existing questions about Atomic and related technologies. * Answer any unanswered questions you can (don't comment, answer). * Upvote both questions and answers about Atomic tech. Some sample searches: https://stackoverflow.com/search?q=atomic+host https://stackoverflow.com/search?q=centos+atomic https://stackoverflow.com/search?q=fedora+atomic Also search on individual projects: https://stackoverflow.com/search?q=cockpit https://stackoverflow.com/search?q=skopeo Also unix.stackexchange.com: https://unix.stackexchange.com/search?q=atomic+host etc ... -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] First Atomic Community Meeting Monday June 12
All, Notes and logs for the meeting are here: http://etherpad.osuosl.org/atomic-community-meeting -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] First Atomic Community Meeting Monday June 12 -- time correction.
On 06/09/2017 05:07 PM, Josh Berkus wrote: > Folks, > > Based on the poll, the Atomic Community Meetings will be: > > 2nd and 4th Mondays > at 12n EDT / 1700 UTC > > The first meeting will be: > > Monday, June 12th, 1700 UTC / 12n EDT > IRC.freenode.net > #atomic channel > > I've sent a bunch of you invitations to that meeting. > > Thanks, see you there. > CORRECTION: 1600 UTC. Apparently Google calendar doesn't have a correct UTC offset. Sigh. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] First Atomic Community Meeting Monday June 12
Folks, Based on the poll, the Atomic Community Meetings will be: 2nd and 4th Mondays at 12n EDT / 1700 UTC The first meeting will be: Monday, June 12th, 1700 UTC / 12n EDT IRC.freenode.net #atomic channel I've sent a bunch of you invitations to that meeting. Thanks, see you there. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Atomic bi-weekly general community meeting: NEW TIMES
All, At the request of one of our Indian contributors, I've added two earlier timeslots (on Wed and Fri). Please take another look at the survey and fill in your availability for those? https://doodle.com/poll/c94n9miwxb7xdq66 On 06/06/2017 12:41 PM, Josh Berkus wrote: > Contributors: > > As requested, I am trying to schedule a general Atomic community meeting > in order to coordinate activitities around the larger Atomic upstream > ecosystem, specifically: > > - Fedora Atomic Host and CentOS Atomic Host > - FLIBS and Container Pipeline > - Atomic CLI tools, including Kompose, Buildah, CRI-O, Atomic > - Cockpit and Commissaire, when applicable > > We have two topics for the first such meeting: > > * What are our plans for upstream kubernetes releases on upstream Atomic > platforms? > > * Deprecating ask.projectatomic.io > > I've created a Doodle so that folks can indicate their availability. > Please set the Doodle for your time zone. While the Doodle is set up > for choosing our first meeting, please pick timeslots to indicate your > general availability for a meeting to occur twice a month on that same > day of week and time. > > https://doodle.com/poll/c94n9miwxb7xdq66 > -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Atomic bi-weekly general community meeting: help pick a time
Contributors: As requested, I am trying to schedule a general Atomic community meeting in order to coordinate activitities around the larger Atomic upstream ecosystem, specifically: - Fedora Atomic Host and CentOS Atomic Host - FLIBS and Container Pipeline - Atomic CLI tools, including Kompose, Buildah, CRI-O, Atomic - Cockpit and Commissaire, when applicable We have two topics for the first such meeting: * What are our plans for upstream kubernetes releases on upstream Atomic platforms? * Deprecating ask.projectatomic.io I've created a Doodle so that folks can indicate their availability. Please set the Doodle for your time zone. While the Doodle is set up for choosing our first meeting, please pick timeslots to indicate your general availability for a meeting to occur twice a month on that same day of week and time. https://doodle.com/poll/c94n9miwxb7xdq66 -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] 2wk atomic release candidate: 20170426
On 04/26/2017 04:30 AM, Dusty Mabe wrote: > > Planning to get back on track this week and also release an > Atomic Host with a fix for CVE-2017-5461. > > We are going to attempt to release the 20170426 images. > These images contain the following ostree version/commit: > > 25.113 > 3492546bc1ef6bca1bc7801ed6bb0414f90cc96668e067996dba3dee0d83e6c3 > > The atomic host VM images are here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170426.0/compose/CloudImages/x86_64/images/ > > The ISO image is here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170426.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170426.0.iso Installs on bare metal, Docker works on OverlayFS. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] 2wk atomic release candidate: 20170327
On 03/27/2017 02:54 PM, Dusty Mabe wrote: > > We are going to attempt to release the 20170327 images. > These images contain the following ostree version/commit: > > 25.89 > 6a71adb06bc296c19839e951c38dc0b71ee5d7a82262fef9612f256f0c2a70da > > The atomic host VM images are here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170327.0/compose/CloudImages/x86_64/images/ > > The ISO image is here: > > https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170327.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170327.0.iso Since I'm at Kubecon, I cannot test the ISO on bare metal this week. Can someone else? -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] creating atomic-host-docs repo
Folks: I'm creating an "Atomic Host Docs" repo so that we can have a home for the ASCIIBinder source which isn't under atomic-site. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Fedora Atomic VFAD 2: Container Guidelines
We will be having a VFAD this Friday (March 10) to update and revise the Container Guidelines based on the reviews of the first containers submitted to FLIBs. The tentative schedule for this VFAD is: EST UTC 10:00-12:00 15:00-17:00 Part I 12:00-13:00 17:00-18:00 Break 13:00-15:00 18:00-20:00 Part II A specific agenda will be published Wednesday and a BlueJeans link on Thursday. If you can only attend part of the FAD because of your time zone, please update the Pagure issue with your availability and specific issues you care about so that we can adjust the agenda: https://pagure.io/atomic-wg/issue/238 This VFAD will consist of discussion of each issue followed by updating of the container guidelines. Some items may require follow-up, but the goal is to get all items settled during the VFAD. Issues covered by this VFAD are here: https://pagure.io/atomic-wg/issues?status=Open=VFAD If you have additional issues, please add them to Pagure, and make sure to tag them VFAD/containers. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] 2wk atomic release candidate: 20170213: Possible failure on bare metal
On 02/14/2017 06:33 AM, Dusty Mabe wrote:
>
>
> On 02/13/2017 10:42 PM, Josh Berkus wrote:
>> On 02/13/2017 07:32 AM, Dusty Mabe wrote:
>>> We are going to try to release our next 2WA release this week.
>>> Feel free to test out today's build and see if there are any issues!
>>>
>>> The atomic images are here:
>>>
>>> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170213.0/compose/CloudImages/x86_64/images/
>>>
>>> The ISO image is here:
>>>
>>> https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170213.0/compose/Atomic/x86_64/iso/Fedora-Atomic-ostree-x86_64-25-20170213.0.iso
>>
>> I get a failure on this in bare metal install. This may be pilot error,
>> see KS file.
>>
>> Installation is on minnowboard from USB key, using the attached
>> kickstart file.
>>
>> Error message is:
>>
>> Failed to pull from repository: g-io-error-quark: No such Metadata
>> object: {long hex key}
>>
>>
>> Interactive install succeeded.
>>
>>
>
> I know what the problem is here. I'll see if we can fix it in Lorax
> when the ISO is created vs making users change their kickstart files.
>
What's the issue? Is this something we should notify the users about so
that they gradually change files (and update our docs?)
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
[atomic-devel] Kubecon pass offer for Atomic contributors
Atomic team: This is a quick check to see if anyone needs a pass to Kubecon. These passes won't be free, but I have a small budget for folks who are willing to work the event. This is just for folks from the Atomic/DevTools teams, not OpenShift, since OpenShift has their own allocations. If you want to go to KubeCon, contribute to an Atomic project (whether you work for Red Hat or not), and are willing to help with the Atomic pod in the Red Hat booth, please let me know ASAP so I can get you one. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Can anyone go to OpenStack PTG?
Folks, We've received a request to send someone who does Fedora Atomic to the OpenStack PTG next month (Feb 20-24) in Atlanta. This is to talk to the Magnum team about some issues they're having with Atomic. Given budget for this, would anyone be able to go? It's really close in time, but then Atlanta isn't *that* far from NC ... -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Fedora 26 change: using overlayfs as default
On 01/06/2017 10:11 AM, Jeremy Eder wrote: > It would be good to confirm ... if you still have the devicemapper > setup, run docker info I do my testing on ephemeral AWS instances, so that one is long gone. I'll do a performance test later when I have time to blog about it. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Fedora 26 change: using overlayfs as default
On 01/06/2017 01:48 PM, Vivek Goyal wrote: > On Fri, Jan 06, 2017 at 01:38:09PM -0800, Josh Berkus wrote: >> On 01/06/2017 11:24 AM, Vivek Goyal wrote: >>> On Thu, Jan 05, 2017 at 04:16:45PM -0800, Josh Berkus wrote: >>>> So, I've done some testing, thanks to Dusty's setup. >>>> >>>> I wasn't able to test on Kubernetes because of some setup issues. >>>> However, I hammered away at Docker using some IO-intensive applications, >>>> including PostgreSQL and Etcd, both of which write data frequently to >>>> some unexpected places. >>>> >>>> So far I haven't seen any unexpected IO errors from containers running >>>> under overlayfs. >>>> >>>> And having all of storage be one big volume is really nice; it >>>> eliminates a longstanding issue we've had with disk allocation; the >>>> whole disk is simply available. >>>> >>>> So +1 on moving to overlayfs for F26. >>> >>> Nice to hear that Josh. BTW, on fedora server and atomic, overlay storage >>> will still come from non-root fs partition. That will allow one to switch >>> back to devicemapper if overlay2 does not work for them. >> >> Why? It didn't when I just ran the test. Why can't we have a shared >> partition? > > We can have depending on what's the default configuration of storage. So > for atomic-host, rootfs was 3G by default and rest of the space was free > which used to be used by devicemapper. > > I think you are talking of some other image where default rootfs > configuration looks different. If rootfs is consuming all space available > on disk by default, then shared partition makes perfect sense. > > So whether to have shared partition by default or setup a separate logical > volume to store images/containers depends on default storage setup of > image. Takign this discussion to the Paguire issue: https://pagure.io/atomic-wg/issue/186 -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Fedora 26 change: using overlayfs as default
On 01/05/2017 05:15 PM, Jeremy Eder wrote: > On Thu, Jan 5, 2017 at 7:22 PM, Josh Berkus <jber...@redhat.com > <mailto:jber...@redhat.com>>wrote: > > Also, performance is MUCH better on PostgreSQL pgbench than devicemapper > is. Like 3X better. > > > Details please? Were you using the loopback dm driver? I was using whatever is the default with Atomic docker-storage-setup. It wasn't actually a rigourous test; I was mostly interested in verifying that Overlay wasn't *slower*. If we have a reason to want a rigorous test, I'll playbook something and get numbers. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Fedora 26 change: using overlayfs as default
On 01/05/2017 05:39 PM, Colin Walters wrote: > On Thu, Jan 5, 2017, at 07:22 PM, Josh Berkus wrote: > >> Also, performance is MUCH better on PostgreSQL pgbench than devicemapper >> is. Like 3X better. > > You really should not store databases (or any persistent data) > in the container's rootfs. Use kubernetes PVs, etc., or for > a real pet database, a host volume pinned to a node > with specifically provisioned storage, etc. The purpose of this test was to test OverlayFS, which I could only do if the data was stored in the container. I pointed out upthread why it's necessary to do this; not interested in repeating myself. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Fedora 26 change: using overlayfs as default
On 01/05/2017 04:16 PM, Josh Berkus wrote: > So, I've done some testing, thanks to Dusty's setup. > > I wasn't able to test on Kubernetes because of some setup issues. > However, I hammered away at Docker using some IO-intensive applications, > including PostgreSQL and Etcd, both of which write data frequently to > some unexpected places. > > So far I haven't seen any unexpected IO errors from containers running > under overlayfs. > > And having all of storage be one big volume is really nice; it > eliminates a longstanding issue we've had with disk allocation; the > whole disk is simply available. > > So +1 on moving to overlayfs for F26. Also, performance is MUCH better on PostgreSQL pgbench than devicemapper is. Like 3X better. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Fedora 26 change: using overlayfs as default
So, I've done some testing, thanks to Dusty's setup. I wasn't able to test on Kubernetes because of some setup issues. However, I hammered away at Docker using some IO-intensive applications, including PostgreSQL and Etcd, both of which write data frequently to some unexpected places. So far I haven't seen any unexpected IO errors from containers running under overlayfs. And having all of storage be one big volume is really nice; it eliminates a longstanding issue we've had with disk allocation; the whole disk is simply available. So +1 on moving to overlayfs for F26. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Fedora 26 change: using overlayfs as default
Dan, Dusty, Vivek: So far nobody has defined (technically) the exact problem with overlayfs and how it affects applications which want to write data inside the container. Note that just saying "don't use Overlay for persistent data" really isn't good enough. Apps in containers frequently write data to places users aren't aware of, such as writing port information to /var/run. While this data may not be important to the user, the app will fail if it errors out. Pushing a change which will cause 30% of a user's containers to start failing for reasons which are opaque to them is not something we should do lightly. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Fedora 26 change: using overlayfs as default
On 12/12/2016 02:24 PM, Dusty Mabe wrote: > I think the rationale is that we'd like to not have a much different > experience whether you are using docker on atomic host or not. My > thoughts are that overlay is where we want to be in the future and > Fedora is the first place we should try that out. > > DM would still be supported via configuration of docker-storage-setup, > just like overlay is supported today in the same way. I'd the impression from the Docker hackers that overlayfs was their future platform. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Fedora 26 change: using overlayfs as default
On 12/12/2016 02:12 PM, Dusty Mabe wrote: > > After I get a bug[1] fixed and out the door I'm going to publish > a blog post/docs on setting up Fedora 25 Atomic host and/or Cloud > base to use overlay2 as the storage driver for docker. > > I'd like for everyone that can to test this out and to start running > their container workloads with overlay2 with selinux enabled and let's > file bugs and get it cleaned up for Fedora 26 release. > > Should we file this as a "change" for Fedora 26? I'd say so, yes. Also, someone needs to test the case of migrating an existing system and how that looks. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] UEFI Fedora atomic partition layout and bootloader install error
Vasiliy, You can follow the UEFI bug here: https://pagure.io/atomic-wg/issue/185 -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] UEFI Fedora atomic partition layout and bootloader install error
On 12/08/2016 03:37 AM, Vasiliy Tolstov wrote: > Im also add biosboot partition, but this not helps. My debug says, that > in ostree grub2 does not have files for x86_64-efi, only 386-pc, so > installation failed when bootloader comes. > What do you think? > > 8 Дек 2016 г. 10:33 пользователь "Vasiliy Tolstov" <v.tols...@selfip.ru > <mailto:v.tols...@selfip.ru>> написал: > > Last night, I'm try to install Fedora 25 atomic host on UEFI notebook. > But all the time installation finished with error fail to install > bootloader. > As I see after this message /mnt/sysimage have no grub files in boot > (grub install not put files) also no grub.cfg > I'm try some partition layouts like: > 1) part1 - fstype EFI, size 500 /boot/efi > part2 - lvmpv > lvmvol - /boot size 500 ext4 > lvmvol - / all size ext4 > 2) part1 - fstype EFI, size 500 /boot > part2 - lvmpv > lvmvol - / all size ext4 > > Whats wrong? Thanks for any help. Thanks for confirming this. I was having the same issues, and hadn't traced the cause. We'll be working on fixing the image. -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Structure of Atomic Host docs for Fedora and CentOS
Folks, Given all of the changes in the platform, it's time to rewrite and re-organize the Atomic Host documentation. Here's what I'm thinking for structure: * Introduction * Installation * Vagrant * Public Cloud * ISO * Others * Quick Start * Links to simplest setups, below * Cluster Setup * Single-Node Vagrant Example (QS) * AH + Kubernetes * Kubeadm (QS) * Kubernetes-Ansible (production) * OpenShift * oc cluster up (QS) * Openshift-Ansible (production) * Other Platforms * Swarm? * Mesos? * Using Ostree * Updates * Rebasing * Hotfixes & Testing * Overlays * Atomic Tools * Atomic CLI (link, maybe) * Docker (and Docker Latest) * System Containers * Other stuff? Open Questions: 1) Should these be combined Fedora/CentOS docs, or should we make a "build" for each OS? 2) Where should these live? projectatomic.io or RTD? 3) Is Vagrant really where we want to direct people as a quickstart option? I'm asking because I'm not that clear on what users can *do* with an single atomic node on vagrant. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] Image Signing Integration Guide
On 11/29/2016 05:16 AM, Aaron Weitekamp wrote: > Check out the integration guide[1] published to help explain the > container image signing capabilities recently introduced to the distros. > > [1] https://access.redhat.com/articles/2750891 > <https://access.redhat.com/articles/2750891> Cool! Seems like we should automatically create the PKI setup on Atomic hosts, no? -- -- Josh Berkus Project Atomic Red Hat OSAS
[atomic-devel] Looking for FOSDEM talks on Atomic/Containers/Etc.
Folks, For anyone going to FOSDEM, there's some containerish rooms, one on microservices (I'm running it) and one on Monitoring & Ops. https://www.cncf.io/event/fosdem-2017 -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] We have a bugzilla requesting that we change the default CMD to systemd for base images in RHEL
On 10/25/2016 12:14 PM, Josh Berkus wrote: > On 10/25/2016 12:02 PM, Jeremy Eder wrote: >> When you "docker pull golang", the image is over 600MB (and it's built >> on alpine). >> Same with docker pull java...also > 600MB. >> >> docker pull alpine is not apples:apples. If you're pulling alpine it's >> because you're about to shove in a ton of other stuff. > > Yah, I'm less concerned about the exact size as I am with the dependency > graph. Currently systemd pulls in a LOT of random stuff, any of which > requires various security updates. There's also the effect on startup > time for calling a container which is running a websocket-activated app, > or a desktop app. You know, though: if we're just changing the default CMD, and NOT what we include in the base image, then it really doesn't break anything. Everyone who builds a container overrides the default CMD. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] We have a bugzilla requesting that we change the default CMD to systemd for base images in RHEL
On 10/25/2016 10:54 AM, Daniel J Walsh wrote: > > > On 10/25/2016 01:43 PM, Josh Berkus wrote: >> On 10/21/2016 01:17 PM, Daniel J Walsh wrote: >>> >>> On 10/21/2016 01:14 PM, Matthew Miller wrote: >>>> On Fri, Oct 21, 2016 at 01:03:58PM -0400, Joe Brockmeier wrote: >>>>> I like Dan's proposal of rhel7-init (or fedora-init, centos-init). >>>> For whatever it's worth, I don't. It makes sense if you're steeped in >>>> the distro world where init systems have been a hot topic for the last >>>> few years, but without that context it sounds like it's something about >>>> inititalizing RHEL/Fedora/CentOS, not that there's a process manager >>>> running. Or even an initial attempt at making a rhel7 container. >>>> >>> Do you prefer >>> rhel7-systemd, fedora-systemd, centos-systemd >>> or >>> rhel7-system, fedora-system, centos-system >>> >>> Or don't like the idea at all? >> Given that we already get flak ... which leads to reduced adoption ... >> of our base images due to their large size, this seems like the wrong >> direction to move into. >> >> Systemd and its dependencies are quite large, sometimes larger than >> everything else in the container combined, both in storage space and in >> memory footprint. If we want to push the idea of having systemd inside >> containers, then we need a new tiny version of systemd designed for >> containers. And by "tiny" I mean "less than 10MB, with few or no >> dependancies which are liable to create extra update churn". >> >> A tiny systemd would be a great selling point. We'd have integrated >> journaling, more sophisticated PID1 scripts, zombie harvesting, etc. >> Those things are benefits to the developer, and we could promote them. >> But nobody's going to buy those at the cost of 100MB+ of bloat. >> > Well splitting it into two container images rhel7 and rhel7-systemd, > would allow you to > get closer to your deal. We attempted to do fakesytemd and > systemd-container, but both > ended causing more trouble then they were worth. We currently ship real > systemd inside > of the RHEL7/Fedora/Centos container images, I believe it has been > shrunk as far as its dependencies > but removing it would be better, although every daemon package that you > install will pull it > in, since they all currently require systemctl. > > Colin's work on this should improve the situation, and I think we have > shrunk the size of Fedora > images with some of the newer versions of rpm/dnf. Well, there's no reason why a systemd designed for just container init couldn't be tiny; it's requirements would be so much less than one running outside a container. But it would be essentially a new piece of software. -- -- Josh Berkus Project Atomic Red Hat OSAS
Re: [atomic-devel] We have a bugzilla requesting that we change the default CMD to systemd for base images in RHEL
On 10/21/2016 01:17 PM, Daniel J Walsh wrote: > > > On 10/21/2016 01:14 PM, Matthew Miller wrote: >> On Fri, Oct 21, 2016 at 01:03:58PM -0400, Joe Brockmeier wrote: >>> I like Dan's proposal of rhel7-init (or fedora-init, centos-init). >> For whatever it's worth, I don't. It makes sense if you're steeped in >> the distro world where init systems have been a hot topic for the last >> few years, but without that context it sounds like it's something about >> inititalizing RHEL/Fedora/CentOS, not that there's a process manager >> running. Or even an initial attempt at making a rhel7 container. >> > Do you prefer > rhel7-systemd, fedora-systemd, centos-systemd > or > rhel7-system, fedora-system, centos-system > > Or don't like the idea at all? Given that we already get flak ... which leads to reduced adoption ... of our base images due to their large size, this seems like the wrong direction to move into. Systemd and its dependencies are quite large, sometimes larger than everything else in the container combined, both in storage space and in memory footprint. If we want to push the idea of having systemd inside containers, then we need a new tiny version of systemd designed for containers. And by "tiny" I mean "less than 10MB, with few or no dependancies which are liable to create extra update churn". A tiny systemd would be a great selling point. We'd have integrated journaling, more sophisticated PID1 scripts, zombie harvesting, etc. Those things are benefits to the developer, and we could promote them. But nobody's going to buy those at the cost of 100MB+ of bloat. -- -- Josh Berkus Project Atomic Red Hat OSAS
