On Fri, Mar 27, 2015, at 03:45 AM, Stef Walter wrote:
> On 13.03.2015 13:16, Colin Walters wrote:
> > On Sun, Mar 8, 2015, at 01:59 PM, Stef Walter wrote:
> >>
> >> Tried it out, and after the rebase/reboot I could no longer SSH into the
> >> atomic host.
On Tue, Mar 31, 2015, at 04:35 AM, Pavel Odvody wrote:
> It's supposed to work in the following way:
> - docker daemon is started with the --trusted flag, this labels the
> process as SELinux type 'docker_daemon_t', daemon also labels the
> created Unix socket as 'docker_socket_t'. Define a policy
On Wed, Apr 1, 2015, at 08:43 AM, Radek Vykydal wrote:
>
> One reason for adding iscsid to the host seems to be ongoing work on
> adding iSCSI as persistent storage for Kubernetes and Docker:
> http://rootfs.github.io/iSCSI-Kubernetes/
Looks like this is https://github.com/GoogleCloudPlatform/ku
Currently, the docker, kubernetes (and other Atomic-relevant components) use
separate Bodhi updates for Fedora 22:
https://admin.fedoraproject.org/updates/FEDORA-2015-4770/kubernetes-0.13.2-0.5.git8d94c43.fc22
https://admin.fedoraproject.org/updates/FEDORA-2015-5143/flannel-0.2.0-7.fc22
https://ad
[ Resurrecting, adding atomic-devel CC ]
On Mon, Mar 9, 2015, at 11:34 AM, Michael P. McGrath wrote:
> Hey all, I wanted to start a thread about doing more frequent Atomic releases
> in Fedora.
> In particular I'd like to start building a new atomic release every two weeks
> that
> includes the
On Wed, Apr 8, 2015, at 03:37 AM, Stef Walter wrote:
> It seems the Fedora 22 Atomic build is broken again. This time due to
> the switch to DNF:
Working on it.
https://github.com/projectatomic/rpm-ostree/issues/121
On Wed, Apr 8, 2015, at 02:51 PM, Joe Brockmeier wrote:
> Copr doesn't count. Talked to Tom Callaway about this briefly just now
> and basically - it must be built in Koji to be part of a Spin, unless we
> get an exception.
A side tag as mattdm mentioned somewhere solves that, no need to
rename.
This came up in a discussion elsewhere, just tossing it up on the list if
anyone's interested:
> Doesn't this suggest that [Docker sharing] should be independent of the way
> images are constructed? This could probably be implemented even today
> with overlayfs, by keeping a hash file farm and h
Hi,
For a while I've had a private git repository for vagrant + kubernetes-ansible
that was perpetually in a state of kind-of working. I'd been holding off on
working on it more until the Vagrant stuff got sorted out for Fedora. Now that
that's happening[1], I pushed:
https://github.com/cgwa
On Fri, Apr 10, 2015, at 02:48 AM, Lalatendu Mohanty wrote:
>
> WorkingDirectory=/var/lib/etcd/`$hostname`.etcd
That's not going to work, systemd doesn't do shell script by default.
Not sure who wrote that or uploaded it, but at least I don't see this in the
current package:
http://cbs.centos.org
Hi,
I've seen several people using Docker on loopback; this is the default if you
use a mainline system + yum install Docker, as opposed to an Atomic host which
uses https://github.com/projectatomic/fedora-productimg-atomic and
https://github.com/projectatomic/docker-storage-setup
I submitted
On Fri, Apr 17, 2015, at 02:45 AM, Joe Brockmeier wrote:
> Hey all,
>
> Did I miss something, or when did we decide to add "screen"? IIRC that
> was discussed and rejected, as we already provide tmux.
You totally outed me...
https://git.fedorahosted.org/cgit/fedora-atomic.git/commit/?id=268fabe30
On Mon, Apr 20, 2015, at 01:10 PM, Stephen Major wrote:
>
> The please add feature x will never stop and it is a slippery slope
> that has already been asked many times
This is true, however...progress has been made on using more privileged
containers for some of the things that would traditionall
On Sat, Apr 18, 2015, at 02:22 AM, James wrote:
> I just noticed:
> https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2015-April/msg00027.html
>
> I've just posted a message to this list about the oh-my-vagrant
> patches that I just wrote. For whatever reason, the archives don't
>
I posted before about uids/gids:
https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2015-January/msg8.html
OSTree (like Docker) ships numeric uid/gids - the way I think of this, the
binaries
have "fixated" on a particular name -> uid mapping.
rpm-ostree grew infrastructure
ticket for this w/in Fedora. Thoughts?
Yep, let's discuss in both.
For reference, I've attached the patch. I tested it with a local tree compose
and a rebase from RHELAH 7.1.1-1, it worked.
From 8727110b5244f8329c30491f4f25800244c760f8 Mon Sep 17 00:00:00 2001
From: Colin Walters
Date: W
On Wed, May 6, 2015, at 03:22 PM, Stephen Gallagher wrote:
>
> Strictly speaking, Fedora is not currently in a Freeze. Final Freeze starts
> on Tuesday, May 12. However, we ARE past Beta release and making a change
> like this so late in the release process is extremely risky, particularly
> si
On Wed, May 6, 2015, at 04:22 PM, Stephen Gallagher wrote:
>
> No, I think you're absolutely right that we need to fix this before it goes
> too far, but my concern is that it's already too late to do it for this
> cycle. I think what you need to do is make that change in Rawhide immediately
>
On Fri, May 1, 2015, at 02:01 PM, Aaron Weitekamp wrote:
> ...to verify a host is properly setup for kubernetes. Could we put this into
> atomic CLI?
>
> $ atomic host status --service kubernetes
I know I am becoming the consistent voice of conservatism for `atomic` without
having
written
On Wed, May 6, 2015, at 05:12 PM, Joe Brockmeier wrote:
>
> Honestly, that isn't my biggest concern. I agree here. The concern is
> we're close to freeze and if we make any changes that affect the
> compose, we may wind up not shipping an F22 Atomic.
I am quite confident that this patch will not
On Wed, May 6, 2015, at 05:38 PM, Colin Walters wrote:
> Nevertheless I will do an installer and cloud image generation test runs
> with it tonight.
Works for me:
http://cdn.verbum.org/fedora-atomic-22-installer-20150506.1.walters/images/boot.iso
ere's the fixup patch, based on the current trac ticket
voting in https://fedorahosted.org/cloud/ticket/102 I plan to push tomorrow.
>From 430cd88ba6de7ee26c67f6ecf6ccdc465954de8d Mon Sep 17 00:00:00 2001
From: Colin Walters
Date: Fri, 8 May 2015 16:44:26 -0400
Subject: [PATCH] fixup! passwd/
Hi,
On Mon, May 11, 2015, at 02:02 PM, Jeremy Eder wrote:
> - specialized selinux booleans (for use by NFS clients).
> - specialized handling of LVM auto-extend (for use by docker-storage-setup).
>
> Instead, I think we should come up with a delivery vehicle for centralized
> overrides. This w
On Tue, May 12, 2015, at 01:28 PM, James wrote:
> Ping?
For Fedora, see:
http://koji.fedoraproject.org/koji/tasks?state=all&owner=masher&view=flat&method=createImage&order=-id
Which links to:
F22 Atomic Vagrant: http://koji.fedoraproject.org/koji/taskinfo?taskID=9702767
rawhide Base Vagrant: ht
Hi,
On Tue, May 12, 2015, at 02:15 PM, James wrote:
>
> 1) root password is not set to 'vagrant' (major issue)
It looks like this is in base's vagrant but not atomic's vagrant:
https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-cloud-base-vagrant.ks#n14
versus
https://git.fedoraho
On Wed, May 13, 2015, at 06:16 PM, James wrote:
> Awesome, thank you, although F22 needs this too :)
> It's a pretty important issue so that users can get in as root and be
> hacking right away :)
What specifically breaks? Everything I've used Vagrant for calls sudo
to gain root.
On Fri, May 15, 2015, at 02:39 AM, Stef Walter wrote:
>
> The last time I highlighted this problem, the answer was that I was
> doing an unsupported upgrade ... and that things had changed incompatibily.
>
> Given that OSTree's whole raison d'etre is coherent atomic
> updates/rollback ... it seems
On Fri, May 15, 2015, at 01:11 PM, Matthew Miller wrote:
> In seriousness, this has crept up quite a lot since the initial
> versions we'd worked on a while ago, and has some huge room for
> improvement. I see it includes dracut and grub2,
I think this an Anaconda regression. Using `bootloader
On Fri, May 15, 2015, at 04:41 PM, Colin Walters wrote:
> I'll file a bug with Anaconda.
https://bugzilla.redhat.com/show_bug.cgi?id=1222132
However, I think I found a workaround:
diff --git a/fedora-docker-base.ks b/fedora-docker-base.ks
index c9da8f2..07d3049 100644
--- a/fedor
On Mon, May 18, 2015, at 11:22 AM, Tim St Clair wrote:
> Could folks cc the bugs to the list so we can track.
The Fedora 22 base image should be fixed; however today's Fedora compose failed
to make an installer due to:
hi, looks like all of the images failed, e.g.
http://koji.fedoraproject.or
On Tue, May 19, 2015, at 11:29 AM, Jeremy Eder wrote:
> # cat Dockerfile
> FROM rhel7/rhel-tools
> MAINTAINER red...@redhat.com
> COPY ./MegaCli-8.07.08-1.noarch.rpm /root/
> COPY ./megaraid-profile.sh /etc/profile.d/
> RUN yum localinstall -y /root/MegaCli-8.07.08-1.noarch.rpm
As a general patt
On Thu, May 21, 2015, at 04:22 PM, Tim St Clair wrote:
> Every reboot it's ignored.
>
> Only on an explicit deamon-reload did it take the unit file into account.
One side effect of how `atomic host upgrade` works via OSTree is that
the configuration merge of `/etc` will only take effect when y
There's a new release of docker-storage-setup available via
this GPG signed git tag:
https://github.com/projectatomic/docker-storage-setup/releases/tag/v0.5
The changes are listed here:
https://github.com/projectatomic/docker-storage-setup/blob/e075395113b85d88c152e80c76d5560d89973882/NEWS.md
I
in treefile
Add docs for container=true
Merge pull request #148 from alexlarsson/container
Colin Walters (33):
Add a public shared library, with "rpm -qa" for commit functionality
doc: Add gtk-doc for new library
build: Use -fvisibility=hidden and explicit exports
On Thu, Jun 18, 2015, at 05:53 AM, Lalatendu Mohanty wrote:
> Hi All,
> [1] https://github.com/LalatenduMohanty/centos7-container-app-vagrant-box
I don't object exactly, but at some point we're really going to have to invest
in
de-duplicating Vagrant work.
See:
https://lists.projectatomic.io/pr
On Thu, Jun 18, 2015, at 02:20 PM, Matthew Miller wrote:
> On Tue, Jun 16, 2015 at 07:47:17PM -0400, Matthew Miller wrote:
> > https://fedoraproject.org/wiki/Changes/Two_Week_Atomic
>
> Now updated based on some feedback and with a schematic of how I
> envision the build→test→release→present proce
On Fri, Jun 19, 2015, at 09:50 AM, Matthew Miller wrote:
>
> So, maybe it's better to actually trigger image build on tree compose
> (iff there's an actual change)?
Everything should trigger on its inputs IMO and not time.
For example, images are triggered by tree compose *and* the spin-kickstarts
On Fri, Jun 19, 2015, at 10:44 AM, Matthew Miller wrote:
> But, also, what do you think of the general workflow for pulling in
> updates I suggested, and for correspondence of releases to commits?
I'll be honest, I don't know yet. I'll take just about any incremental
improvement over the status
On Fri, Jul 3, 2015, at 08:28 AM, Bohuslav Kabrda wrote:
> To describe the whole system more: Builds are submitted through osbs-client
> by users/other tools. osbs-client communicates with OpenShift. OpenShift has
> an image with atomic-reactor installed inside, which is used to build
> request
://bugzilla.redhat.com/show_bug.cgi?id=1235843
Signed-off-by: Colin Walters
---
fedora-atomic-docker-host.json | 1 +
1 file changed, 1 insertion(+)
diff --git a/fedora-atomic-docker-host.json b/fedora-atomic-docker-host.json
index d344c4b..60e7f75 100644
--- a/fedora-atomic-docker-host.json
+++ b/fedora-atomic
On Mon, Jul 6, 2015, at 01:34 PM, Eric Paris wrote:
> On Mon, 2015-07-06 at 12:53 -0400, Colin Walters wrote:
> > Currently, firewalld is the default for Fedora. However, both Docker
> > and Kubernetes do not yet know how to talk to it. Work is underway
> > on
> >
See https://lists.fedoraproject.org/pipermail/devel/2015-June/211326.html
---
fedora-atomic-docker-host.json | 1 +
1 file changed, 1 insertion(+)
diff --git a/fedora-atomic-docker-host.json b/fedora-atomic-docker-host.json
index 60e7f75..4bed86a 100644
--- a/fedora-atomic-docker-host.json
+++ b/
On Tue, Jul 7, 2015, at 09:04 AM, Lalatendu Mohanty wrote:
>
> I still think we are overloading the atomic name. The idea of atomic
> host
FWIW I nearly always now correct people to "Atomic Host" when they
mean that exactly because there are a number of things under the brand now.
> is to cre
No objections noted, so I pushed this.
On Tue, Jul 7, 2015, at 08:43 PM, Colin Walters wrote:
> See https://lists.fedoraproject.org/pipermail/devel/2015-June/211326.html
> ---
> fedora-atomic-docker-host.json | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fe
On Wed, Jul 8, 2015, at 04:30 AM, Tobias Florek wrote:
> Hi,
>
> tldr: add early-docker daemon (a la coreos) to support running
I think a two-level approach would indeed allow implementing a
number of nontrivial deployment types. Probably not *all* of them
though (at least at the current time).
Pushed, thanks!
(minor: I deleted the trailing period to match the commit style)
On Fri, Jul 24, 2015, at 01:45 PM, Tomas Radej wrote:
> Hi all,
>
> Please include this patch that switches the Atomic Host manifest from
> Python 2-based packages to Python 3. This change is necessary due to the
> "Python 3 as Default" Fedora Change
> (https://fedoraproject.org/wiki/Changes/
Hi,
A while ago I posted about duplicate Ansible and Vagrant work going on:
https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2015-April/msg00027.html
Now, OpenShift is another large project building on top of the same
technologies as Project Atomic, such as Kubernetes.
I recent
Hi,
On Mon, Aug 3, 2015, at 03:52 AM, Lalatendu Mohanty wrote:
> I was going through the getting started documentation [1] and realized
> that we should have some automation to setup atomic hosts (may be
> ansible playbook)
This is the topic of this post from last week:
https://lists.projecta
On Thu, Aug 13, 2015, at 04:39 PM, Lokesh Mandvekar wrote:
> Dan Walsh maintains a few branches for docker which include upstream docker
> sources
> + RH patches that are used by rpms for fedora, centos, rhel and their atomic
> variants. The repo is: https://github.com/rhatdan/docker . Some curre
Dan, you're already an administrator in the organization, so you should have
the rights to transfer it into the org.
I'd wait through the weekend at least to see if there are any
objections/thoughts from anyone else, then pull the trigger Monday or so?
On Fri, Aug 21, 2015, at 09:07 AM, Tobias Florek wrote:
> Hi,
>
> is there a way to specify dependencies for (spc) containers that provide
> some service?
This is an interesting topic; both raw docker and kubernetes lack
dependency mechanisms. I think down the line, kubernetes is going
to have
On Fri, Aug 21, 2015, at 09:03 AM, Tobias Florek wrote:
> to allow mounting additional filesystems, one needs mount.
> helpers. mount looks for them (not documented, but for at least all
> versions I tried) in /sbin/fs.d. Of course that directory is not
> writeable on atomic hosts.
There is activ
On Mon, Aug 24, 2015, at 09:50 AM, Tobias Florek wrote:
> AFAICT, that does not solve the problem, that e.g. kubernetes gluster
> (or ceph) plugin will call the host's mount(8), which will need to find
> a mount.glusterfs helper script (on the host) that will call
> mount.glusterfs in the containe
Dennis Gilmore noted 'atomic' is only available on x86_64, but docker.spec
disagrees now.
Lokesh?
diff --git a/atomic.spec b/atomic.spec
index 482f3b2..f284cae 100644
--- a/atomic.spec
+++ b/atomic.spec
@@ -1,3 +1,8 @@
+# Define arches for PA and SA
+%global golang_arches %{ix86} x86_64 %{arm}
On Fri, Sep 4, 2015, at 12:50 PM, Vivek Goyal wrote:
> Virtual size of qcow2 f22 atomic size is 6G.
This comes from
https://pagure.io/releng/blob/master/f/scripts/build-cloud-images#_93
Now, one important thing about the cloud image is that via cloud-init it
supports dynamic extension of the
Hi,
While I know it's not officially part of this effort, I'd like to crosspost the
announcement of a new release of my project "linux-user-chroot" here:
https://git.gnome.org/browse/linux-user-chroot/tag/?id=v2015.1
It's focused around *non-root* containers. In contrast to:
http://www.project
On Sun, Sep 6, 2015, at 12:54 PM, James wrote:
> Interesting... Does any of this/can any of this overlap with the xdg-app
> work alexl is doing?
Somewhat, yes; xdg-app is also intended for unprivileged use. Some of
the initial setuid core of xdg-app was based on linux-user-chroot. Since
then I'
Hey, I noticed this PR:
https://github.com/fedora-cloud/Fedora-Dockerfiles/pull/112
What do you guys think about switching to Kubernetes-in-a-container
by default? We should likely keep the Kubernetes in the Atomic Host
available for some time, but how long?
I know this would affect some of the
On Mon, Sep 14, 2015, at 10:52 AM, Tobias Florek wrote:
>
> which is different from the other atomic hosts, which have
> system_u:object_r:sshd_exec_t:s0 as expected.
>
> > Should be running as sshd_t not kernel_t? Are you doing this into the
> > systemd-nspawn container, or
> > is the sshd_t nat
On Wed, Sep 16, 2015, at 10:26 AM, Tim St Clair wrote:
> I have a single oddball machine which appears to have failed an upgrade b/c
> it ran out of space.
The "overwriting error" is a definite bug, but I think the system functioned as
designed and left you with a working system even though th
> What do you guys think about switching to Kubernetes-in-a-container
> by default? We should likely keep the Kubernetes in the Atomic Host
> available for some time, but how long?
>
> I know this would affect some of the Ansible and documentation work
> out there.
Looking around a bit more, one
On Wed, Sep 16, 2015, at 07:23 PM, Clayton Coleman wrote:
> We don't want to encourage local host paths in the future. For now it's fine
Are you planning to use Docker volumes then? Or how else to enable persistence
in the single-host scenario?
(reads farther down)
> The bulk will move into e
Hi,
I saw this land:
https://github.com/projectatomic/ContainerApplicationGenericLabels/blob/master/vendor/redhat/labels.md
Does anyone know more about this? Is this declared stable now?
On Fri, Sep 25, 2015, at 05:19 AM, Sujit Fulse wrote:
> Hi Matthew,
>
thank you for your valuable reply. The links that you forwarded are
useful to me.
> I am interested in stuff where " grub2-mkconfig " is executed while
> generating qcow2 image.
See
https://github.com/rhinstaller/anaconda
On Tue, Sep 29, 2015, at 03:44 PM, Jonathan Lebon wrote:
> Hi all,
>
> I'm currently working on adding automatic PR testing to some
> GitHub repositories in the projectatomic organization[1].
This sounds great!
> Unfortunately, I don't have the sufficient permissions to
> set this up myself (it
Hi,
On Tue, Sep 29, 2015, at 05:53 AM, Natale Vinto wrote:
>
> This let containers hosts being updated silently by pushing the update
> remotely (solicitate an upgrade) and perform a reboot based some
> strategies, where the most useful is the one that let the cluster of
> hosts decide itself wha
I discovered a group for this may already exist as:
https://github.com/orgs/projectatomic/teams/build-service-admins-committers
I just added you; does that work?
On Wed, Sep 30, 2015, at 04:53 AM, Natale Vinto wrote:
> Hi,
> thanks for feedbacks. So, as far I understand, the logic (a module?)
> between daemonized rpm-ostree and any kubernetes node evacuation
> feature that move pods elsewhere, is responsible of upgrade and reboot
> machines, like having a l
Hi, just a quick note:
I created:
https://github.com/projectatomic/atomic/releases/tag/v1.5
as there were no tags, and my build system:
https://github.com/cgwalters/rpmdistro-gitoverlay
really wants one.
Let's agree to make tags and announce releases here
in the future?
Hi,
On Fri, Aug 14, 2015, at 05:45 PM, Daniel J Walsh wrote:
> Yes although I don't want to transfer, since I still want my
> rhatdan/docker. But we could create a docker fork on atomic.
I noticed https://github.com/projectatomic/docker
exists now, cool.
Are there any policies or procedures fo
Hi,
I noticed:
http://pkgs.fedoraproject.org/cgit/kubernetes.git/log/
now contains OpenShift Origin.
This seems like it has a lot of potential consequences. Should
we now start adjusting the website and documentation to
share more with Origin as well?
It looks like right now that change is only
On Wed, Oct 7, 2015, at 12:24 PM, Dusty Mabe wrote:
> The idea is more or less to support an application developer being
> able to define his/her own verbs to allow the user to call from atomic
> CLI.
I haven't looked at this closely, but it sounds like it overlaps with the
Dockerfile `ENTRYPOI
Hi,
I was chatting with someone running Atomic Host whose / partition had filled up
due to a container logging going out of control.
Since 1.7 docker has supported:
https://docs.docker.com/reference/logging/journald/
And journald supports log file rotation based on disk space. Any objections
On Thu, Oct 8, 2015, at 04:40 PM, Clayton Coleman wrote:
> Doesn't this break docker logs calls? At least on 1.7?
Yeah, it does, we need:
https://github.com/projectatomic/docker/commit/e611a189cb3147cd79ccabfe8ba61ae3e3e28459
Which is only in 1.9 I think.
(Random aside, I applaud the quality o
On Tue, Oct 20, 2015, at 06:18 AM, Nick Coghlan wrote:
> Arbitrary Ansible commands don't necessarily make sense on a stateless
> system like Atomic Host,
Atomic Host is not required to be stateless, persistent changes in /etc and
/var are fully supported.
the stack
we go.
> in fedora 23, so ansible cannot do even the most basic things.
Please see the below patch, which restores "basic things" like the
template/copy module.
Any objections?
>From 567053cf7d249687a91284f95eabb761ee89c832 Mon Sep 17 00:00:00 2001
From: Colin Walters
On Wed, Oct 21, 2015, at 04:05 PM, Colin Walters wrote:
> Python 2 is explicitly installed, but the question is how far up the stack
> we go.
Specifically a topical question is `python-docker-py` which is used
by the Ansible Docker module.
Personally, I vote against adding this - anyo
On Wed, Oct 21, 2015, at 04:09 PM, Eric Paris wrote:
> On Wed, 2015-10-21 at 16:06 -0400, Colin Walters wrote:
>
> The upstream kubernetes ansible needs the following on the node
>
> python # everyone need python2
> python-dnf # some versions of ansible (2.0) use dnf dir
On Mon, Oct 26, 2015, at 07:01 AM, Sujit Fulse wrote:
> hello all, I am building fedora 22 atomic host on my
> ppc64le machine . I am referring*
> https://github.com/jasonbrooks/byo-atomic*. My "rpm-ostree-toolbox create-vm-
> disk " command returning with *"error: lsetxattr: Operation n
On Tue, Oct 27, 2015, at 05:13 AM, Sujit Fulse wrote:
>
> while, i am using "imagefactory" command, to generate VM image.
>
> "rpm-ostree-toolbox imagefactory " is failing with "No disk activity
> in 300 seconds, failing". I increased time-out upto 2000 seconds
> still now working.
Unfortunately
On Wed, Oct 28, 2015, at 01:26 PM, Adam Miller wrote:
> I'd vote in favor of including the python-docker-py package for users
> of Atomic Host and the Ansbile docker module.
OK, looks like consensus agrees. Want to do a patch?
On Thu, Oct 29, 2015, at 03:05 PM, Adam Miller wrote:
> I don't think I have perms on the repo, but the patch is below.
Added:
python-chardet-2.2.1-3.fc23.noarch
python-docker-py-1.3.1-1.fc23.noarch
python-requests-2.7.0-7.fc23.noarch
python-six-1.9.0-3.fc23.noarch
python-urllib3-1.10.4-6.fc2
On Wed, Oct 28, 2015, at 10:49 AM, Joe Smithian wrote:
> Hello,
>
> I am interested in using CentOS atomic for its virtualization,
> softwsre upgrade and roll back support and few other nice features. I
> am wondering if we can use ostree-rm in offline/local mode to upgrade
> OS with NO online acc
On Sun, Nov 8, 2015, at 08:33 AM, Jan Pazdziora wrote:
> On Tue, Oct 27, 2015 at 11:51:23AM +0100, Jan Pazdziora wrote:
> >
> > Specifically I believe the attached patch against
> > https://git.fedorahosted.org/cgit/fedora-atomic.git master branch
> > might be a good start.
>
> I have now rebased
On Mon, Nov 9, 2015, at 02:13 PM, Charlie Drage wrote:
> I'm working on docker-machine integration for atomic host's. The
> problem I'm facing is the fact that "atomic" isn't defined under
> /etc/os-release, it's simply "fedora" or "centos" as the id.
https://bugzilla.redhat.com/show_bug.cgi?id=12
On Fri, Nov 13, 2015, at 05:07 AM, Jan Pazdziora wrote:
> On Thu, Nov 12, 2015 at 09:00:31PM -0500, Colin Walters wrote:
> >
> > Can you improve the commit message? It currently is mostly "what"
> > but not much "why" (and the subject line should be impe
If you have thoughts on this or use cases, please follow up here:
https://bugzilla.redhat.com/show_bug.cgi?id=1283701
On Wed, Nov 18, 2015, at 08:37 AM, Jan Pazdziora wrote:
> What is the next step? When / how is the rawhide ISO regenerated?
Atomic Host doesn't currently work in rawhide because we haven't
yet forward-ported a systemd patch that's in the F23 branch.
But:
> Also, any chance of bringing this chan
is that it will also automatically
fetch history from the server side. This was theoretically possible
before but far from ergonomic. Now it is much easier to find an
earlier OS version and look for a regression, or upgrade to something
that's not the latest.
Thanks to all contributors!
On Tue, Dec 8, 2015, at 02:53 AM, Nick Coghlan wrote:
> There's one trick we discussed that I think is actually fairly safe:
> using hard links to share the same set of compiled files for normal
> execution and -O, rather than having two copies.
OSTree's default content-addressed storage means t
ber Rosa (4):
atomic: simplify exception handling
Imports: general reorganization
Disable urllib3 warning: move code to a util module function
Disable urllib3 warnings: handle imports more gracefully
Colin Walters (5):
diff: Quiet pylint warning
Dan Walsh (30):
Bumb
On Mon, Jan 11, 2016, at 04:10 PM, Daniel J Walsh wrote:
> With the latest patches going into docker we can run containers with the
> mount clients inside of
> the container. I don't think we need to move these into the atomic
> host. Lets work to get
> a cephs, gluster, nfs mount client that us
On Fri, Jan 15, 2016, at 06:50 AM, Pavel Odvody wrote:
> Hello,
>
> there's a new release of HICA, system & API for wiring container
> applications back to host based on runtime label introspection.
This is a cool project, the concepts obviously parallel work done on modern
application sandboxing
Suggest replies to anaconda-devel-list@.
- Original message -
From: "Brian C. Lane"
To: anaconda-devel-l...@redhat.com
Subject: Anaconda Docker addon review needed
Date: Wed, 20 Jan 2016 12:10:39 -0800
Here's a pile of code that needs to be reviewed. I totaly failed to
figure out how to
On Mon, Jan 25, 2016, at 07:21 AM, Lukas Slebodnik wrote:
> ehlo,
>
> We changed packaging in sssd-1.13.3-3.fc23 and sssd plugin for sudo
> is in separate package and not in sssd-common. It's a minimal package
> which depends only on glibc and communicate with sssd (daemon/container)
> via unix
On Fri, Jan 22, 2016, at 07:46 AM, Karanbir Singh wrote:
> I realise there have been a few efforts that startedup, but none that
> really finished implementation so maybe the first thing would be to
> recap who's actually doing any testing at this point, where are they
> running it and whats the
On Thu, Jan 21, 2016, at 10:41 AM, Chris Evich wrote:
>
> All,
>
> Looking for some advice re: a tooling bug. The problem (bug) has to do
> with sosreport incorrectly determining whether or not it's not running
> w/in a SPC container. The context is always going to be from within an
> SPC,
Hi,
On Thu, Jan 21, 2016, at 07:31 AM, Charles Paul wrote:
> Hello all,
>
> Making a request to enable LUKS in Atomic Host's dracut as per this
> bug report https://bugzilla.redhat.com/show_bug.cgi?id=1270335 .
Originally, not including cryptsetup is mostly attributed to it not
being in the criti
On Fri, Jan 29, 2016, at 11:08 AM, Jonathan Lebon wrote:
> Make atomic-devmode part of the tree compose.
Not sure if you saw, there was some FESCo discussion of this:
https://meetbot.fedoraproject.org/teams/fesco/fesco.2016-01-29-17.00.log.html
I guess no one from there followed up here?
1 - 100 of 290 matches
Mail list logo
