[atomic-wg] Issue #228 `clarify policy on atomic host support for older Fedora "number" releases`

jberkus added a new comment to an issue you are following: `` In which case: if we're not supporting N-1, then what's the reason to not do a rolling release? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/228

[atomic-wg] Issue #229 `decide on version scheme and image naming scheme for f26`

jberkus added a new comment to an issue you are following: `` I'd prefer year/month/day, simply because it's fairly difficult for users to figure out what serial number they want, but the date is easy. `` To reply, visit the link below or just reply to this email

Re: [atomic] passing ENV though atomic

missing, or any examples of unit files with atomic? Can you share your unit file? -- -- Josh Berkus Project Atomic Red Hat OSAS

[atomic-wg] Issue #228 `clarify policy on atomic host support for older Fedora "number" releases`

jberkus added a new comment to an issue you are following: `` -1 on dropping Life Support for N-1 unless we're ready to shift to rolling releases. That's pretty much the worst of all possible worlds. Proposed policy: Life Support+ From the date N is released: * We continue offering OSTree

Re: [HACKERS] Official adoption of PGXN

tarray. You have to admit that it seems really strange in the eyes of a new user that ISN is packaged with PostgreSQL, whereas better-written and more popular extensions (like plv8, pg_partman or pgq) are not. -- Josh Berkus Containers & Databases Oh My! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[atomic-wg] Issue #170 `Finish new Fedora Atomic PRD`

jberkus added a new comment to an issue you are following: `` Roshi: more work is needed, particularly on the Use Case text, which is fairly outdated. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/170

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 a

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 a

Re: [atomic-devel] 2wk atomic release candidate: 20170213: Possible failure on bare metal

his 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. -- -- Josh Berkus Project Atomic Re

Re: Self Introduction: Yu Qi Zhang (yzhang)

On 02/13/2017 01:48 PM, Jerry Zhang wrote: > I am looking for sponsor/reviewers if anyone is interested. I also hope > to be more active in the fedora community in the future. Thank you! Wow, thank you for building these! -- -- Josh Berkus Project Atomic Red Ha

Re: Self Introduction: Yu Qi Zhang (yzhang)

On 02/13/2017 01:48 PM, Jerry Zhang wrote: > I am looking for sponsor/reviewers if anyone is interested. I also hope > to be more active in the fedora community in the future. Thank you! Wow, thank you for building these! -- -- Josh Berkus Project Atomic Red Ha

Re: Ownership of the Cloud Base Image

omic >> but I'm not sure if that is necessary. I think as long as we have a >> separation of ownership (mainly different issue trackers) then that >> should take care of some of the issues. > > +1 Yah, given that we also have atomic-de...@projectatomic.io, we do NOT need more

Re: [HACKERS] Removal of deprecated views pg_user, pg_group, pg_shadow

ince the final pgAdmin 3 release. How long would you suggest is appropriate? Postgres 11? 12? Let's set a target date; that way we can communicate it more than once. -- Josh Berkus Containers & Databases Oh My! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make

Re: Revising the SPI bylaws: third draft

On 02/12/2017 03:57 PM, Jimmy Kaplowitz wrote: > If the membership thinks this draft is reasonable and is willing to > support it, I'd love to send it off to our lawyers for any wording > tweaks from them and then vote on the output of that. +1, let's do this.

Re: [HACKERS] removing tsearch2

xtensions (also CUBE, earthdistance, etc.). However, one of the steps in that would be getting the mainstream platforms to package them so that users have a reasonable upgrade path, so I would not propose doing it for 10. -- Josh Berkus Containers & Databases Oh My! -- Sent via pgsql-hacker

Re: [HACKERS] removing tsearch2

e, >> anyone who wants it can maintain a copy elsewhere). Starting a new >> thread to make sure we collect all the relevant votes, but I really, >> really think it's past time for this to go away. The last actual >> change to tsearch2 which wasn't part of a wider cleanup was >> 3ca7eddbb7c48

Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal

pg_shadow/pg_user. I think Postgres 10 is the right time to break that code (I mean, we have to do it someday, and we're already telling people about breakage in 10), but be aware that there will be shouting and carrying on. -1 on a warning. Very little code today which references the deprecated co

Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal

On 02/09/2017 12:53 PM, Stephen Frost wrote: > * Josh Berkus (j...@berkus.org) wrote: >> On 02/09/2017 12:42 PM, Stephen Frost wrote: >>> * Josh Berkus (j...@berkus.org) wrote: >>>> On 02/09/2017 11:08 AM, Tom Lane wrote: >>>>> Agreed, let's just g

Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal

On 02/09/2017 12:42 PM, Stephen Frost wrote: > * Josh Berkus (j...@berkus.org) wrote: >> On 02/09/2017 11:08 AM, Tom Lane wrote: >>> Agreed, let's just get it done. >>> >>> Although this doesn't really settle whether we ought to do 3a (with >>> bac

Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal

user-chosen names. -- Josh Berkus Containers & Databases Oh My! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: owncloud container in fedora container registry

On 02/08/2017 02:12 PM, Adam Williamson wrote: > On Wed, 2017-02-08 at 14:10 -0800, Josh Berkus wrote: >> Really, our best hope is that NextCloud cleans up the Owncloud >> architecture to make it supportable. > > This seems entirely likely, but it seems very unlikely t

Re: owncloud container in fedora container registry

7 as well. > > Given both the complexity of the environment (requiring unsupported PHP > versions) and the unrest caused by the owncloud/nextcloud fork, is this > really something that should be pushed through at this time? See my comment on the ti

Re: Prelim attendance and setup for Bitcamp 2017 (Apr 7-9,2017)

On 01/29/2017 05:31 PM, Corey W Sheldon wrote: > I am asking to see who is willing and / or able to partake in Bitcamp > 2017 [0] April 7-9, 2017. So, ... where is Bitcamp? City? Country? I ask because the event website doesn't tell me either. -- -- Josh Berkus Project Atomic Red Ha

[atomic] FYI: rpm-ostree upgrade in place works to fix Kube/OpenShift DNS breakage

Folks: Just in case you upgraded to one of the Fedora Atomic trees with the bad kernel, I wanted to let folks know that upgrade in place to the latest ostree will fix DNS on a running Kube cluster, based on my testing. So you don't need to rollback or re-deploy. -- Josh Berkus Project Atomic

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

jberkus added a new comment to an issue you are following: `` @dwalsh Maybe we should name the executable something other than "docker_storage_setup" then, no? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/197

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

jberkus added a new comment to an issue you are following: `` BTW, if you know you won't want to migrate back, I recommend having a single partition with overlayFS (that is, DOCKER_ROOT_VOLUME=no). That way you don't have to guess at allocations at all. `` To reply, visit the link below or

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

jberkus added a new comment to an issue you are following: `` The unallocated space is because we can't predict if the user will need more space for containers, or more for other things (a Gluster storage partition, for example). This means that, in the default case, the user can easily expand

[atomic-devel] Kubecon pass offer for Atomic contributors

. 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

Re: attempt at lightweight fedora container image

t; > You can give this image a shot by pulling "dustymabe/fedora-min". > You need to run 'microdnf install' instead of 'dnf install'. I thought someone else had already built a ~~ 70MB image? -- -- Josh Berkus Project Atomic Red Hat OSAS _

Re: Custom built tree with new kernel

On 01/20/2017 08:22 PM, Josh Berkus wrote: > On 01/20/2017 08:19 PM, Dusty Mabe wrote: > >> This sounds like dns on your node is broken, which is different than >> the issue we were seeing before (which was a connection issue between >> containers running on the same n

Re: Custom built tree with new kernel

it has good information in it? Yah, it's the same as the resolv.conf for the ansible node, where DNS is working. -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email

Delay in Fedora Atomic 2-week release

current plan is to release next week, and then again the following week to get back on schedule. -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le

[atomic-wg] Issue #185 `November 21 ISO is not bootable on UEFI`

jberkus added a new comment to an issue you are following: `` @dustymabe I tested this on one of the minnowboards, and it installed and booted fine. Note that, instead of allocating specific bytes for /boot, you can use this KS command: reqpart --add-boot `` To reply, visit the link below or

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

jberkus added a new comment to an issue you are following: `` Presumably we can do this by changing the default cloud-init? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/197 ___ cloud mailing list --

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

jberkus added a new comment to an issue you are following: `` That's a very good question! And AWS images is one of the biggest places we need to have good default behavior ... `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/197

[atomic-wg] Issue #197 `Change size of Root, Docker partitions in F26 Atomic Host storage setup`

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` The way it is now: Currently, the rootFS is sized at 3GB, fixed, and the Docker partition is 40% of the remaining space. This causes new users to run out of disk space if they do layering, ostree unlock,

[atomic-devel] Can anyone go to OpenStack PTG?

, but then Atlanta isn't *that* far from NC ... -- -- Josh Berkus Project Atomic Red Hat OSAS

[openstack-dev] [containers][magnum] Magnum team at Summit?

Magnum Devs: Is there going to be a magnum team meeting around OpenStack Summit in Boston? I'm the community manager for Atomic Host, so if you're going to have Magnum meetings, I'd like to send you some Atomic engineers to field any questions/issues at the Summit. -- -- Josh Berkus Project

[pgadmin-hackers] Building server without Apache

Pgadmin gurus: I'm trying to create a canonical container image for pgAdmin4 Server. However, using Apache is kind of heavyweight for a container. Has anyone run pgAdmin4 against something lighter weight? -- Josh Berkus Containers & Databases Oh My! -- Sent via pgadmin-hackers mailing

[HACKERS] Retiring from the Core Team

ever hand all of them off). It's been a long, fun ride, and I'm proud of the PostgreSQL we have today: both the database, and the community. Thank you for sharing it with me. -- -- Josh Berkus Red Hat OSAS (any opinions are my own) -- Sent via pgsql-hackers mailing list (pgsql-hackers

[atomic-wg] Issue #191 `Remove-Kube: create end-to-end test for Kubernetes cluster on Atomic`

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Once we have containerized kubernetes working, we need an automated or manual test which creates a 3+ node cluster, installs kubernetes, and launches one or more applications on it. `` To reply, visit the

Re: [HACKERS] RustgreSQL

core Postgres, being able to write extensions in languages other than C (like, full-featured extensions) would be its own benefit. Why not start there? That is, assuming that Joel has gobs of time to work on this? For that matter, I know that Jeff Davis is quite fond of Rust. -- -- Josh Berk

Re: Proposal: require DESCRIPTION, USAGE label for images

On 01/10/2017 10:52 AM, Matthew Miller wrote: > On Tue, Jan 10, 2017 at 10:44:03AM -0800, Josh Berkus wrote: >>> On Tue, Jan 10, 2017 at 10:33:05AM -0800, Josh Berkus wrote: >>>>> USAGE: single command line giving usage example >>>>>

Re: Proposal: require DESCRIPTION, USAGE label for images

*Bump* Sans feedback, I'm going to assume that everyone approves of this pretty soon ... On 12/13/2016 01:24 PM, Josh Berkus wrote: > Folks, > > Looking at the new FDLIBS, I'm noticing that there's not a narrative > description of the image required or provided anywhere tha

Prerequisites to removing Kube from base image

getting this done by F26 just because of the outstanding issues with a containerized install. But we'll see. -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le

[atomic-wg] Issue #190 `Remove-Kube: Determine and document migration process`

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` We will need to figure out, and then fully document, a migration process for users of the old built-in Kubernetes binaries to upgrade to F26 with containerized binaries. `` To reply, visit the link below

[atomic-wg] Issue #189 `Remove-Kube: document new Kubernetes install process`

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Once we have working, containerized Kubernetes install process, we'll need to write documentation for it. `` To reply, visit the link below or just reply to this email

[atomic-wg] Issue #188 `Remove-Kube: produce official containers with Kubernetes components`

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` In order to remove Kubernetes from the AH base image and have a full containerized Kube install, we need to have "official" kubernetes containers produced by the Fedora project. They need to be

[atomic-wg] Issue #187 `Remove-Kube: Make fully containerized install work`

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` This is one of several issues which need to be overcome in order to remove Kubernetes from the base Atomic Host image. This issue is a tracking issue for the various technical problems and bugs which

[atomic-wg] Issue #186 `switch to overlay2`

jberkus added a new comment to an issue you are following: `` Dusty: Right, and that question comes down to "how much do we care about revertability VS. user experience". It's not an easy question to answer. In the long run, DOCKER_ROOT_VOLUME=no as default is the obvious answer. But for

[atomic-wg] Issue #186 `switch to overlay2`

jberkus added a new comment to an issue you are following: `` @dwalsh aha. The current docks emphasize export/import, so I thought it was required. Lemme test that, but if it works that's a powerful argument for maintaining dual partitions for backwards compatibility. If we're doing that,

[atomic-wg] Issue #186 `switch to overlay2`

jberkus added a new comment to an issue you are following: `` Also, using partitioning to limit Docker's space consumption only makes sense if we can somehow automagically "right-size" the two partitions. In our current code, it doesn't matter how much space docker eats up, because we've only

[atomic-wg] Issue #186 `switch to overlay2`

jberkus added a new comment to an issue you are following: `` @dwalsh see comments above about why those tools won't actually work in practice. If we can work around those, then that changes things. But right now what I'm hearing is "you can switch back, but only if you have unallocated

[atomic-wg] Issue #186 `switch to overlay2`

jberkus added a new comment to an issue you are following: `` So, to summarize: 1. The main reason given for keeping "two partitions" by default with docker-storage-setup is so that users can easily switch back to devicemapper if there are critical issues with OverlayFS. 2. However, there is

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

[atomic-wg] Issue #186 `switch to overlay2`

jberkus added a new comment to an issue you are following: `` OK, so regarding (2), a follow-up question: Is there any mechanism by which I can take a running system configured for overlay (with two partitons) and convert it to devicemapper without: a) needing to re-partition? b) needing to

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

[atomic-wg] Issue #186 `switch to overlay2`

jberkus added a new comment to an issue you are following: `` So, there's two questions here: Aha, thanks. Seems like DOCKER_ROOT_VOLUME should default to "on" then if we're going to do partitioning. That leaves us with two questions: 1) What do we feel is the best default settup for an

[atomic-wg] Issue #186 `switch to overlay2`

jberkus added a new comment to an issue you are following: `` So I just did a test of using OverlayFS on Fedora Atomic 25 as a cloud-init option. This resulted in having the whole disk as one volume, shared with the overlay, instead of multiple partitions. That's the desireable default setup,

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. > >

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) >

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

Re: [atomic-devel] Fedora 26 change: using overlayfs as default

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

Re: [flexbackup-help] Project status?

On 01/04/2017 02:22 PM, isdtor wrote: > What is the status of this project? I see 23 open bugs that look like they > were never updated, going back as far as 2004. It's long-dead. I'm surprised the mailing list still works. -- -- Josh

Re: Script to create a cockpit devel VM

eveloper for about 12½. I've > touched a lot of things over the years, but most recently I've mostly been > involved in plumbing (systemd, networking, udisks and the like) and Ubuntu's > CI. Hey, Martin! Glad to see that even though both of us have changed projects, I'll still see yo

Re: Fedora server cloud images dead?

c/ . On this page i can't find > information about other images than Atomic. > > Are Fedora Server cloud images dead and only Atomic will exist? This is an issue with some dropped links between getfedora.org and alt.fedoraproject.org. You can track the issue here: https://pagure.io/

Re: [HACKERS] Proposal for changes to recovery.conf API

ry_target_type and recovery_target_value > into a single parameter could make sense, never mind the other three. > But I don't really want to argue about it any more. > Either solution works for me. -- -- Josh Berkus Red Hat OSAS (any opinions are my own) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[atomic] Update on Kubernetes and Fedora Atomic 25

with testing and feedback, please comment on this mailing list. Users of Fedora Atomic Host who do not use Kubernetes or Flannel will be largely unaffected by these changes. -- -- Josh Berkus Project Atomic Red Hat OSAS

Out tommorrow

I won't be able to make the meeting tommorrow due to travel. -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [HACKERS] Migration Docs WAS: Proposal for changes to recovery.conf API

he docs will be hard enough; if I (or anyone else) has to argue about whether or not they're too long, I'm just going to drop the patch and walk away. -- -- Josh Berkus Red Hat OSAS (any opinions are my own) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes

[atomic-wg] Issue #170 `Finish new Fedora Cloud PRD`

jberkus added a new comment to an issue you are following: `` @mattdm I was trying to use kolinar for this, but it won't let me log in; the OpenID login gets a 404 error. Is there some way I can get access to this tool? `` To reply, visit the link below or just reply to this email

Fwd: Invitation: Hack Day @ Tue Dec 20, 2016 (jber...@redhat.com)

Given that we're working with Openshift-Ansible, as many of us as possible should participate in this. Forwarded Message Subject: Invitation: Hack Day @ Tue Dec 20, 2016 (jber...@redhat.com) Date: Fri, 16 Dec 2016 23:38:18 + From: Daniel McPherson

Re: [HACKERS] Proposal for changes to recovery.conf API

". > I don't see any problem with that, particularly if someone other than > Bruce or me is volunteering to write it ;-) I'm up for writing it (with help from feature owners), provided that I don't have to spend time arguing that it's not too long, or that I should put it somewhere differ

Re: [Spi-private] Very long wait for funds transfer

On 12/15/2016 11:58 AM, Hilmar Lapp wrote: > Seconded. I think we’re all in the same boat here, and I’ll go out on a limb > here and say that we all collectively know that what Joshua reported is by no > means an isolated incident but a pattern that has been festering. Plus, we > are probably

Re: [atomic-devel] Fedora 26 change: using overlayfs as default

ue 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

ue to them is not something we should do lightly. -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [HACKERS] Proposal for changes to recovery.conf API

docs, and not mention the wiki. My 2c. > > Yes, that is the usual approach. > So where in the docs should these go, then? We don't (currently) have a place for this kind of doc. Appendices? -- -- Josh Berkus Red Hat OSAS (any opinions are my own) -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

meeting minutes

) * jbrooks (14) * misc (11) * trishnag (6) * bowlofeggs (2) * tflink (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org

Proposal: require DESCRIPTION, USAGE label for images

d by USAGE, such as how to supply configuration files * Depedencies on other images (e.g. "requires a database") * Links to documentation for the Software, if any -- -- Josh Berkus Project Atomic Red Hat OSAS __

Re: [atomic-devel] Fedora 26 change: using overlayfs as default

e 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: Fedora 26 change: using overlayfs as default

e 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 Projec

Re: [atomic-devel] Fedora 26 change: using overlayfs as default

of migrating an existing system and how that looks. -- -- Josh Berkus Project Atomic Red Hat OSAS

Re: Fedora 26 change: using overlayfs as default

of migrating an existing system and how that looks. -- -- Josh Berkus Project Atomic Red Hat OSAS ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to cloud-le...@lists.fedoraproject.org

Re: [HACKERS] Proposal for changes to recovery.conf API

On 12/08/2016 04:16 PM, Tom Lane wrote: > Josh Berkus <j...@agliodbs.com> writes: >> On 12/01/2016 05:58 PM, Magnus Hagander wrote: >>> And in fairness, having such a "guide to changes" chapter in each >>> release probably *would* be a good id

Re: [HACKERS] Proposal for changes to recovery.conf API

resources to > make that. The release notes are good, but having a more hand-holding > version explaining incompatible changes in "regular sentences" would > probably be quite useful to users. We will have enough major changes in 10.0 to warrant writing one of these. Maybe not

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

[atomic-wg] Issue #185 `November 21 ISO is not bootable`

jberkus added a new comment to an issue you are following: `` Report from the field: ``` 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

Re: [HACKERS] Proposal for changes to recovery.conf API

am sure > that a new version will be sent for the next CF. > Please let's make sure this gets done for 10. We're planning on breaking a lot of config things in 10, so it would be MUCH easier on users if we do the recovery.conf changes in that version as well. -- -- Josh Berkus Red Hat OSA

Re: [atomic-devel] UEFI Fedora atomic partition layout and bootloader install error

xt4 > 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-wg] Issue #185 `November 21 ISO is not bootable`

jberkus added a new comment to an issue you are following: `` Per atomic-devel list, ISOs are in fact broken for UEFI. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/185 ___ cloud mailing list --

[atomic-wg] Issue #184 `ISO file is missing`

jberkus added a new comment to an issue you are following: `` Oh? Because the Princeton mirror didn't have the 11/21 ISO either. Maybe that's a bad mirror? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/184

[atomic-wg] Issue #185 `November 21 ISO is not bootable`

jberkus added a new comment to an issue you are following: `` Hmmm. Didn't have issues with 24. Let me retest now that 12/7 is available. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/185 ___ cloud

[atomic-wg] Issue #184 `ISO file is missing`

jberkus added a new comment to an issue you are following: `` Well, we shouldn't remove the prior ISO until the new one is populated. We had at least 24 hours with no ISO. Also, updating getfedora.org should hinge on the mirrors being populated, somehow. Do the other WGs have this issue? ``

[atomic-wg] Issue #185 `November 21 ISO is not bootable`

jberkus added a new comment to an issue you are following: `` Aside from the problem with installing, this raises the question of whether anyone other than me is testing ISOs on bare metal at all. Queued for meeting because of this. `` To reply, visit the link below or just reply to this

[atomic-wg] Issue #185 `November 21 ISO is not bootable`

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` I'm currently testing the November 21 ISOs by installing on my minnowboard cluster. It seems to be the case that these ISOs are not bootable; after getting through most of the install, they give the

[atomic-wg] Issue #184 `ISO file is missing`

The issue: `ISO file is missing` of project: `atomic-wg` has been assigned to `dustymabe` by jberkus. https://pagure.io/atomic-wg/issue/184 ___ cloud mailing list -- cloud@lists.fedoraproject.org To unsubscribe send an email to

[atomic-wg] Issue #184 `ISO file is missing`

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Try to download the ISO at this location, as supplied by GetFedora.org:

[atomic-wg] Issue #183 `ISO file is missing`

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Try to download the ISO at this location, as supplied by GetFedora.org:

Re: Privacy policy for Tux Paint; ideas?

On 12/07/2016 10:27 AM, Josh berkus wrote: > On 12/07/2016 09:23 AM, Bill Kendrick wrote: >> As Tux Paint is a completely offline program, with no network >> capabilities at this time -- at least in the Desktop version >> (other Tux Paint devs, remind me: what do the Android a

Re: Privacy policy for Tux Paint; ideas?

On 12/07/2016 09:23 AM, Bill Kendrick wrote: > As Tux Paint is a completely offline program, with no network > capabilities at this time -- at least in the Desktop version > (other Tux Paint devs, remind me: what do the Android and iOS > versions do, if anything, online?) -- and as the

<    1   2   3   4   5   6   7   8   9   10   >