jberkus added a new comment to an issue you are following:
``
I wasn't thinking that topic would be the primary method of communication.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/169
___
cloud
clear on what users can *do*
with an single atomic node on vagrant.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
Folks,
I'm starting a discussion around the structure of the Atomic Host
documentation on atomic-devel list. It's there because I want to cover
Centos Atomic as well.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
cloud mailing list -- cloud
les/2750891>
Cool!
Seems like we should automatically create the PKI setup on Atomic hosts, no?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
Vivek, Dan,
> - Now when docker users overlay2 graph driver, all the images, containers
> and associated metadata will be stored outside the root filesystem and
> onto /dev/docker-vg/foo logical volume.
This is a change from current storage setup? Right now, containers go in the
docker
jberkus added a new comment to an issue you are following:
``
Walters: are you saying that the CentOS solution should work for Fedora as
well? Testing ...
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/178
On 11/16/2016 10:27 PM, Jimmy Kaplowitz wrote:
> As with Martin Michlmayr's reply, I'm fine with the bylaws specifying that we
> should have a board attendance policy, and that falling below a certain
> threshold can (or should or must) lead to removal for cause. I'd rather leave
> the specifics
On 11/17/2016 11:27 AM, Joshua D. Drake wrote:
> On 11/17/2016 10:59 AM, Josh berkus wrote:
>
>> That's not relevant to why we need an admin. Nor has anyone suggested
>> hiring a fundraiser.
>>
>> SPI is at this point a $500K organization. It is downright
>>
On 11/17/2016 09:49 AM, Neil McGovern wrote:
> On Thu, Nov 17, 2016 at 09:05:33AM -0800, Josh berkus wrote:
>> 2) SPI is a big enough NPO that it really should have at least one paid
>> administrative staff member. I believe that Drake previously proposed
>> something of the
jberkus added a new comment to an issue you are following:
``
Well, the whole point of Atomic is to be immutable: "configure once, deploy
many times". Having a key piece of infrastructure depend on per-server package
layering kinda breaks that. It makes it hard to explain why people should
jberkus added a new comment to an issue you are following:
``
Well, OpenShift is its own thing rather than an alternative to Kubernetes.
Some people want Kube, some want OpenShift.
So I've been doing a bunch with Kubeadm on AH. Jason's version does actually
work, with some caveats:
1) it
jberkus added a new comment to an issue you are following:
``
Sorry, that was suppsoed to be en_US, not en_UTF8. Still errors out.
The problem is that C.UTF8 isn't a real locale. It's just barely good enough
for English speakers, and it's useless for supporting foriegn-language
speakers.
On 11/17/2016 09:18 AM, Hilmar Lapp wrote:
>
>> On Nov 17, 2016, at 12:05 PM, Josh berkus <j...@postgresql.org> wrote:
>>
>> 2) SPI is a big enough NPO that it really should have at least one paid
>> administrative staff member. I believe that Drake previously
a big enough NPO that it really should have at least one paid
administrative staff member. I believe that Drake previously proposed
something of the sort?
--Josh Berkus
___
Spi-general mailing list
Spi-general@lists.spi-inc.org
http://lists.spi-inc.org/listinfo/spi-general
jberkus added a new comment to an issue you are following:
``
C.UTF-8 is not the same locale at en_UTF8.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/178
___
cloud mailing list --
On 11/16/2016 11:10 AM, Martin Michlmayr wrote:
> * Josh berkus <j...@postgresql.org> [2016-11-16 11:03]:
>> One chronic problem we have had with the SPI Board is failure to attend
>> meetings causing board meetings to be recessed due to lack of quorum.
>
> It hasn
jberkus added a new comment to an issue you are following:
``
On a full-blown Ferdora system, I'd fix the above with localectl, but that's
not present in the base image.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/178
jberkus added a new comment to an issue you are following:
``
Sorry, doesn't work.
initdb: invalid locale name "en_utf8"
-bash-4.3$ export LANG=C.UTF8
-bash-4.3$ initdb -D /pgdata/data --locale=en_UTF8
The files belonging to this database system will be owned by user "postgres".
This user must
jberkus added a new comment to an issue you are following:
``
testing ...
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/178
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an
jberkus added a new comment to an issue you are following:
``
Sure, that's fine.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/177
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe
jberkus reported a new issue against the project: `atomic-wg` that you are
following:
``
TL;DR: it is impossible to load a real locale in the base image. This breaks
many applications.
In regular Fedora, locale is now part of systemd. The mini-systemd in the
container base image does not
jberkus added a new comment to an issue you are following:
``
Yes, there's a workaround. However, imagine that you're a developer porting
your Dockerfiles from Ubuntu. You run into bizarre errors with cp, or hangs
during the build. Do troubleshoot them, or give up and go back to Ubuntu?
``
jberkus added a new comment to an issue you are following:
``
Try to copy *over* a file.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/177
___
cloud mailing list -- cloud@lists.fedoraproject.org
To
jberkus reported a new issue against the project: `atomic-wg` that you are
following:
``
Currently, the "cp" command in fedora base image is "cp -i" interactive, as is
it with Fedora Workstation. This can cause "cp" commands in dockerfile scripts
to fail, because of the interactive prompt,
y to
> generate a diff after getting the source document from him if LibreOffice has
> a
> way to do that. I'm not sure about either of those "if"s and suspect the diff
> would be noisy anyway due to the reformatting.
I don't see how the membership can appro
o use it
>
> I am already planning to write the first blog post. Any volunteers for the
> 2nd one.
I was planning to write out "how to install KubeAdm on Atomic"; is that
what you're looking for?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
__
Someone's written a tiny C implementation of gosu:
https://github.com/ncopa/su-exec
This is invaluable for entrypoint scripts, as a way of demoting
permissions without losing TTY. Could we include it?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
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
___
Container-tools mai
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
? Sure it is. Ships in PostgreSQL-core.
I mean, I'm not particularly in favor of using JSON for this (arrays
seem OK), but that seems like an invalid reason not to.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or
On 10/21/2016 10:29 AM, Robert Haas wrote:
> On Fri, Oct 21, 2016 at 1:17 PM, Josh Berkus <j...@agliodbs.com> wrote:
>> Particularly, with 9.6's freeze map, point (2) is even stronger reason
>> to *lower* autovacuum_max_freeze_age. Since there's little duplicate
>> w
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 i
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
ted
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
As an additional test, I set up a 3-node Docker Swarm cluster.
This worked fine (after fixing the docker-storage-setup issues). I was
able to deploy a service to multiple nodes.
Note that the Docker documentation isn't accurate when it comes to what
ports you need to expose.
--
--
Josh Berkus
On 10/23/2016 11:13 PM, Murtuza Zabuawala wrote:
>
>
> --
> Regards,
> Murtuza Zabuawala
> EnterpriseDB: http://www.enterprisedb.com <http://www.enterprisedb.com/>
> The Enterprise PostgreSQL Company
>
> On Mon, Oct 24, 2016 at 10:12 AM, Josh Berk
49
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
On 10/11/2016 01:47 PM, Dave Page wrote:
>
>
> On Tuesday, October 11, 2016, Josh Berkus <j...@agliodbs.com
> <mailto:j...@agliodbs.com>> wrote:
> Ah, so I can drop a path into config_local?
>
>
> Yes, per the example I sent yesterday. config_local.py
n
> no discussion for the last three weeks doesn't mean this effort is
> dead; I would like very much to see it move forward.
Has this gone anywhere? Given that we're in "break all the things" mode
for PostgreSQL 10, it would be the ideal time to consolidate
recovery.conf with pg.conf.
--
--
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
to *lower* autovacuum_max_freeze_age. Since there's little duplicate
work in a freeze scan, a lot of users will find that frequent freezing
benefits them a lot ... especially if they can take advantage of
index-only scans.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
--
Sent
On 10/19/2016 12:12 PM, Hongbin Lu wrote:
> Please find below for the draft of Magnum mascot.
>
Huh. I was expecting a big bottle of bubbly. ;-)
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
__
OpenStack Devel
On 10/20/2016 06:34 AM, Joshua D. Drake wrote:
> On 10/19/2016 07:22 PM, Josh Berkus wrote:
>> On 10/19/2016 06:27 PM, Joshua D. Drake wrote:
>>> Hello,
>>>
>>> After all these years, we are still regularly running into people who
>>> say, "pe
use-case, it makes far more sense to do batch loads interspersed
with ANALYZEs and VACUUMS of loaded/updated tables.
--
--
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
l from the
> standby to the master, while vacuum_defer_cleanup_age behaves like
> old_snapshot_threshold in that it causes cancel for long-running
> queries.
See Andres' response on this thread. He's already covered why the
setting is still useful, but why we might want to remove it anyway.
I have a few.
Please reply off-list.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
Container-tools mailing list
Container-tools@redhat.com
https://www.redhat.com/mailman/listinfo/container-tools
On 10/18/2016 01:37 PM, Andres Freund wrote:
> Hi,
>
> On 2016-10-09 21:51:07 -0700, Josh Berkus wrote:
>> Given that hot_standby_feedback is pretty bulletproof now, and a lot of
>> the work in reducing replay conflicts, I think the utility of
>> vacuum_defer_cleanup_
On 10/18/2016 01:28 PM, Robert Haas wrote:
> On Tue, Oct 18, 2016 at 4:18 PM, Josh Berkus <j...@agliodbs.com> wrote:
>> On 10/12/2016 05:00 PM, Robert Haas wrote:
>>> On Sun, Oct 9, 2016 at 9:51 PM, Josh Berkus <j...@agliodbs.com> wrote:
>>>> Given that
On 10/12/2016 05:00 PM, Robert Haas wrote:
> On Sun, Oct 9, 2016 at 9:51 PM, Josh Berkus <j...@agliodbs.com> wrote:
>> Given that hot_standby_feedback is pretty bulletproof now, and a lot of
>> the work in reducing replay conflicts, I think the utility of
>> vacuum_def
On 10/10/2016 10:50 PM, Dave Page wrote:
>
>
> On Monday, October 10, 2016, Josh Berkus <j...@agliodbs.com
> <mailto:j...@agliodbs.com>> wrote:
> One thing which would improve this is to have setup.py take an optional
> --directory argument.
>
&
this is to have setup.py take an optional
--directory argument.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
On 10/10/2016 08:31 PM, Dave Page wrote:
>
>
> On Sunday, October 9, 2016, Josh Berkus <j...@agliodbs.com
> <mailto:j...@agliodbs.com>> wrote:
>
> On 10/09/2016 05:04 PM, Josh Berkus wrote:
> > sqlite> select * from ConfigDB;
> >
the option in 10?
--
--
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
On 10/10/2016 11:26 AM, Magnus Hagander wrote:
> On Mon, Oct 10, 2016 at 6:57 PM, Josh Berkus <j...@agliodbs.com
> And you'd need the SELinux perms even if it was in /var/lib/, because of
> the nologin status of the Apache user.
>
>
> Yes, but /var/lib is supposed
On 10/10/2016 11:10 AM, Joshua D. Drake wrote:
> On 10/09/2016 06:54 PM, Josh berkus wrote:
>> On 10/09/2016 11:45 AM, Dimitri John Ledkov wrote:
>>> This was meant to go into September meeting (originally proposed). At
>>> that point, a clause suggesting what t
On 10/10/2016 03:36 AM, Magnus Hagander wrote:
>
>
> On Mon, Oct 10, 2016 at 2:26 AM, Josh Berkus <j...@agliodbs.com
> <mailto:j...@agliodbs.com>> wrote:
>
> On 10/09/2016 04:36 PM, Josh Berkus wrote:
> > I'll confirm here that the Web version doesn't
ons to the content of the proposal, but
16 hours is WAY insufficient discussion time for an Associated project
proposal.
We depend on the members to raise issues around legal entanglements,
traps and other "unknown unknowns" with new projects. Giving members
less than a day's notice is in no wa
On 10/09/2016 04:36 PM, Josh Berkus wrote:
> I'll confirm here that the Web version doesn't work either from the
> Fedora packages. In the case of the web version, this appears to be
> because of confusion between Python2 and Python3 dependencies.
Leaving out the SQLite bug (see oth
On 10/09/2016 05:04 PM, Josh Berkus wrote:
> sqlite> select * from ConfigDB;
> Error: no such table: ConfigDB
More relevantly:
sqlite> select * from version;
Error: no such table: version
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
--
Sent via pgadmin-support
ng executed.
pgadmin4 1.0, installed on Fedora24, from yum.postgresql.org packages.
Being used as the sole web application under httpd.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes
described above should be
> necessary anyway: I would've expected that after installing the RPM I'd
> have an application that works out of the box.
>
> best regards,
> Peter Juhasz
>
>
>
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
who have the time to try it out.
What's the ISO link? I'd like to add it in, but I can't figure out what
the stable link is.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an
On 10/05/2016 11:41 AM, Colin Walters wrote:
> Now that Cloud -> Atomic and will be focusing on Project Atomic, can we move
> the
> Docker base image into this group from the "Fedora Base" group?
+1
--
--
Josh Berkus
Proje
push the design
changes back.
--
--
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
d with a redesign which emphasizes
Atomic over the cloud base image if F25-base Atomic isn't ready at
release time. We'll have to hold that back, and that's something the
design team needs to know.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
clou
g.
Kushal?
Based on my attendence at the Cloud WG meetings, I had the understanding
that Atomic was becoming our main deliverable. If that's not true, then
I need to pull a whole bunch of changes and put them on ice until Fedora 26.
--
--
Josh Berkus
Project A
lease, it looks pretty bad;
that's saying we're ok with only being 2/3 ready, or that despite
promoting Atomic to 1st class status we don't really believe it's important.
--
--
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
All,
Where are we with getting F25 Atomic to boot? If it doesn't boot, I
don't see any point in having a test day.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email
On 09/30/2016 08:58 AM, Adam Miller wrote:
> On Thu, Sep 29, 2016 at 1:54 PM, Josh Berkus <jber...@redhat.com> wrote:
>> On 09/29/2016 08:18 AM, Adam Miller wrote:
>>> On behalf of the Fedora Cloud Working Group, I am happy to
>>> announce that we now ha
On 09/30/2016 08:58 AM, Adam Miller wrote:
> On Thu, Sep 29, 2016 at 1:54 PM, Josh Berkus <jber...@redhat.com> wrote:
>> On 09/29/2016 08:18 AM, Adam Miller wrote:
>>> On behalf of the Fedora Cloud Working Group, I am happy to
>>> announce that we now ha
s *at all* with "continuous release"
projects like Cockpit which don't have separate major releases, just
incremental releases every week. I'm not sure how to handle those; how
do we do it for RPMs right now?
--
--
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
development and adoption.
--
--
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
at users always be aware of
> the version (compose id) of the image they downloaded in order to not
> have issues/bugs filed against an image named "latest" that is
> changing out from under users every two weeks.
Yaaay!
>
> The new URLs are below
ISO URL?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
at users always be aware of
> the version (compose id) of the image they downloaded in order to not
> have issues/bugs filed against an image named "latest" that is
> changing out from under users every two weeks.
Yaaay!
>
> The new URLs are below
ISO URL
Forwarded Message
Subject: Re: getfedora.org/atomic notes
Date: Tue, 27 Sep 2016 16:35:44 -0400
From: Máirín Duffy <du...@redhat.com>
To: Josh Berkus <jber...@redhat.com>
CC: Robert Mayr <robyd...@fedoraproject.org>
Hey Josh,
OK here is what I'm thinking a
fflist responses I've
gotten from members of this list, I'd say yes.
I suspect you'd feel differently if you were asking for one of the passes.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
fflist responses I've
gotten from members of this list, I'd say yes.
I suspect you'd feel differently if you were asking for one of the passes.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
Container-tools mailing list
Container-tools@redhat.com
/community/Kubernetes_Dev_Summit.md
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
dev mailing list
dev@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
... do we have a project for this? I don't see one.
Right, now, it seems like the only thing we're missing for the stack.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
Container-tools mailing list
Container-tools@redhat.com
https
Folks,
If anyone needs a pass to attend KubeCon in Seattle, please reply to me
ASAP. We have a limited number of passes and they're vanishing fast.
Note that folks recieving passes will be expected to put in several
hours of booth duty.
Thanks!
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
Two Week
> Release cycle was to be able to deliver new stuff faster and fix
> issues faster but playing it safe isn't inherently a bad approach
> either.
When is F26 out?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
the meeting.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
On 09/08/2016 10:33 AM, Trishna Guha wrote:
> On Thu, Sep 8, 2016 at 8:10 PM, Josh Berkus <jber...@redhat.com
> <mailto:jber...@redhat.com>> wrote:
>>
>> In what way are images created for atomic not runnable on regular
>> Docker? Examples?
>>
>
the ability to use the Dockerfiles.
>
> Since we are focusing on having production ready Dockerfiles for Atomic
> host, Should we create a separate repository that contains Atomic
> specific Dockerfiles?
In what way are images created for atomic not runnable on regular
Docker? Examples?
--
ver, booting the installed system fails. I *think* this
> is because its initramfs is broken. See
> https://bugzilla.redhat.com/show_bug.cgi?id=1374082 for more details.
> Thanks!
>
Thanks for keeping us updated. I have no idea how to troubleshoot that,
though.
--
--
Josh Berkus
Pro
ey wanted quorum. So the sensible default
would be:
"k (n1, n2, n3)" == "any k (n1, n2, n3)"
... however, that will break backwards compatibility. Thoughts?
My $0.02 is that we break backwards compat somehow and document the heck
out of it.
--
--
Josh Berkus
Red Hat OSA
it releases work, but we need an answer
which will be acceptable to packagers.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
cockpit-devel mailing list
cockpit-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/admin/lists/cockpit-devel@lists.fedorahosted.org
of these stages is useful on its own. And if we can get
1 & 2 going, I think that additional community help will show up.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
netes, given.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
pplication
And this would be a poor one:
Fedora24
|
MyGeoDjangoApplication
But AFAIK, there aren't any tools to encourage or check for the first
over the second.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
Container-tools mailing list
Container-tools@
Per today's meeting, please refine the spec for this:
https://fedorahosted.org/cloud/ticket/169
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
cloud mailing list
cloud@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/cloud
, although the quoted party must be willing to
have their quote translated.
I will need any quotes by September 15th.
If you know someone who can give us a quote, or can suggest someone I
can ask, let me know. Thanks!
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
--
Sent via pgsql-general
to start on this via Fedora or CentOS. Thoughts?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
If we fold Cloud Base into Server --
which we should -- we'll need to do a bunch of community outreach
beforehand to make sure that people don't think we're abandoning our users.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
cloud mai
gments). I'm not sure this is
a real problem which users will notice (in today's scales, 144MB ain't
much), but if it turns out to be, it would be nice to have a way to
switch it back *just for them* without recompiling.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
--
Sent via pgsq
On 06/27/2016 08:58 PM, Jason Brooks wrote:
> I can go file an issue in k8s/contrib, but is this a bug, or am I not
> understanding how this is supposed to work?
So ... this is still broken. Is this a bug in /contrib, not Atomic Host?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
nents
> [2], as well as backwards compatible transport protocol. I hope to post
> more documentation about these guarantees soon.
What about making a 1.0 release?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
___
cockpit-devel mailing list
coc
On 08/15/2016 05:18 PM, Tom Lane wrote:
> Josh Berkus <j...@agliodbs.com> writes:
>> On 08/15/2016 02:43 PM, Tom Lane wrote:
>>> Last I heard, there's an exclusion for "system" accounts, so an
>>> installation that's using the Fedora-provided pgsql accou
On 08/15/2016 02:43 PM, Tom Lane wrote:
> Josh Berkus <j...@agliodbs.com> writes:
>> On 07/10/2016 10:56 AM, Joshua D. Drake wrote:
>>> tl;dr; Systemd 212 defaults to remove all IPC (including SYSV memory)
>>> when a user "fully" logs out.
>
>&
a user "fully" logs out.
That looks like it was under discussion in April, though. Do we have
confirmation it was never fixed? I'm not seeing systemd killing
Postgres under Fedora24.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
--
Sent via pgsql-hackers mailing list (pgs
container technology;
2. Descriptions and demos of some cool new technology;
3. Inspirational talks about the container ecosystem or social aspects
of new stacks.
If you have an idea for such a keynote, please email me with a 3-4 line
description.
--
--
Josh Berkus
Project Atomic
Re
401 - 500 of 7835 matches
Mail list logo
