On Wed, 2013-09-11 at 12:01 -0400, Matthew Miller wrote:
So, idea one is to make something like CoreOS (http://coreos.com/): a
lightweight distribution made for running containers on top of. We wouldn't
attempt to be _as_ lightweight as CoreOS (for that, there's CoreOS), but aim
to be small
Hi,
https://github.com/cgwalters/min-metadata-service
is a new project of mine which might be of interest to a potential few
people here in the cloud space that are building smaller operating
systems - small enough to not include Python (or other scripting
languages).
I just released
On Mon, Feb 10, 2014 at 1:37 AM, Matthew Miller
mat...@fedoraproject.org wrote:
So at my Fedora.next talk at DevConf, I mentioned that OSTree might
be an
interesting thing for Fedora Cloud to look at.
I am obviously interested in this =) I have some forthcoming work to
post within a week
On Wed, Mar 5, 2014 at 6:58 AM, Sandro red Mathys
r...@fedoraproject.org wrote:
Heads-up: I've taken ownership for the external need Automatic
Smoketests on Image Build [0]
Testing an image takes time and resources, and with several images, it
takes several times that. Since that simply doesn't
-computing on the
build server what in the traditional package world happens per-client.
Oh, totally. Still, I would rather have a statement from Colin Walters
that states it's in a good enough state for our use case. Leading-edge
is good, broken edges aren't :)
Short answer: Yes, I think so. Longer
On Thu, Mar 6, 2014 at 8:19 AM, Sandro red Mathys
r...@fedoraproject.org wrote:
- Create image using ImageFactory (and initialize ostree in %post)
This is possible, but in the realm of options which range from:
1) Hack up current rpm-ostree direct .qcow2 generation code
2) ImageFactory with
On Thu, Mar 6, 2014 at 11:52 AM, Matthew Miller
mat...@fedoraproject.org wrote:
I think it will eventually be pretty useful for servers, although
without a
good layer on top, we would just be, to extend your analogy, forcing
everyone to buy their groceries from a restaurant, and making them
On Thu, Mar 6, 2014 at 11:58 AM, Joe Brockmeier j...@redhat.com wrote:
How would this go over for people coming from $other_images that have
cloud-init and expect to use it? If I understand correctly, you're
saying their existing stuff isn't going to work well w/Fedora even if
we
have
On Fri, Mar 7, 2014 at 4:42 AM, Sandro red Mathys
r...@fedoraproject.org wrote:
Sorry, missing something here. What would I need that code for? I was
actually thinking about writing something like:
Yep, that code is just the JS implementation of the shell script you
posted.
Hm, does
- How does one activate the deployed product if extlinux is the active
bootloader? The website has only instructions for GRUB (bls_import,
etc).
Ah, you probably hit this:
https://bugzilla.gnome.org/show_bug.cgi?id=726007
This is also related:
https://bugzilla.gnome.org/show_bug.cgi?id=722845
On Tue, Mar 11, 2014 at 9:33 AM, James Slagle jsla...@redhat.com
wrote:
There are 2 image upgrade paths being pursued by TripleO. In both
cases, the
end goal is to have your instances running with a read-only root
partition
and your stateful data you need preserved mounted on a separate
On Tue, Mar 11, 2014 at 5:17 PM, James Slagle jsla...@redhat.com
wrote:
How is it incompatible with packaging? The read only root support that
already exists in Fedora today is what would be used.
In that /etc and /var are read-only. Now you're right, there is
read-only root which makes
On Thu, May 1, 2014 at 2:37 PM, Mike Ruckman ro...@fedoraproject.org
wrote:
* Crucial basic Docket Host Image decisions (jzb, 08:07:23)
* https://fedorahosted.org/cloud/ticket/47 (jzb, 08:07:36)
* AGREED: fedora atomic docker-specific image will not include
yum/dnf
(mattdm,
I'm not sure what you are saying here. This is about yum/dnf/etc.
being
in the minimal install image for the Atomic host.
Do you plan to ship rpm-ostree in that?
I thought that was the plan?
I guess you are saying that you are planning on shipping more than
just
ostree, so people can
Hello cloud dwellers,
So I was looking at rpm-ostree + EC2 stuff, and digging into the
current Fedora cloud image, I hadn't realized just how special it is.
Basically we have extlinux in the VBR, and
/boot/extlinux/extlinux.conf. This is used by qemu-kvm/OpenStack. But
in order to
On Wed, May 7, 2014 at 9:28 AM, Joe Brockmeier j...@redhat.com wrote:
Any chance you can make it to tomorrow's meeting? We might have more
questions that you are uniquely qualified to help us sort out.
I'll be on IRC, but unfortunately I have a time conflict on that slot
(as I imagine many
Hello world,
I finally got some time this weekend to work on min-metadata-service;
it's
now more featureful, and has a better name: min-cloud-agent.
https://bugzilla.redhat.com/show_bug.cgi?id=1096479
Is the new package review request, per policy since it's renamed. A
reviewer would be
On Sun, Jun 22, 2014, at 11:27 AM, Dennis Gilmore wrote:
1) the image is intended to be just ran without tweaks
For reference I meant that Fedora rel-eng performs this operation,
ending up with two distinct cloud images but without significant pain in
generating them.
Anyways though I think
On Fri, Jun 13, 2014, at 08:47 PM, Renich Bon Ciric wrote:
I'm, currently, working on a Fedora image for Google Cloud; just for fun.
A semi-related followup here: For the Atomic Cloud Image our original
thought was to try min-cloud-agent, but I haven't had much time to
invest in it recently,
Hi,
I have a regular meeting time conflict with this one, sorry I wasn't
able to make it. I'll try to ensure I at least am on IRC for the
meeting.
On Thu, Jul 10, 2014, at 08:07 AM, Matthew Miller wrote:
* Atomic Cloud Image (mattdm, 14:41:59)
* this one needs a new owner (mattdm,
should be safe because the Fedora Cloud kickstart in
spin-kickstarts uses services --enabled=cloud-init.
---
cloud-init.spec | 22 ++
1 file changed, 2 insertions(+), 20 deletions(-)
From 71d73e3ae96fd66f401db44e74a6aacecc030ecc Mon Sep 17 00:00:00 2001
From: Colin Walters walt
On Tue, Jul 15, 2014, at 02:52 AM, Garrett Holmstrom wrote:
This would be a great thing to add to the bug report for this issue [1]
as well.
Done, patch attached.
If the kickstart explicitly enables cloud-init then yes, let's drop the
self-enabling bits. We should really be using
On Tue, Jul 22, 2014, at 03:57 PM, Matthew Miller wrote:
+1 -- let's aim to implement the Atomic patterns unless there's a
compelling
reason not to (and, if that happens, see if we can work with the upstream
project to straighten out whatever problem).
A specific reason to include Cockpit by
Hi,
Trying to get ahead of the Change process this time =)
I'd like to move Atomic under the Server WG as I feel it's a more
appropriate home for Fedora 22, with the increased scope to bare metal
installation. (Really it crosses both as Atomic should run in all the
clouds that mainline does,
===
#fedora-meeting Meeting
===
Meeting started by walters at 16:07:39 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2014-08-01/fedora-meeting.2014-08-01-16.07.log.html
.
Meeting summary
---
* LINK:
On Sun, Sep 7, 2014, at 11:22 PM, Dusty Mabe wrote:
In a nutshell, it would be great if we added Container to references we
make to the container image (in conversation and docs).
I tend to say Docker Base Image - that's the terminology upstream
Docker uses:
On Thu, Sep 25, 2014, at 06:43 PM, David Gay wrote:
I'm doing a new compose now, and it does have bash-4.3.24-2.fc22.
(Which, AIUI, may not actually fix everything per
https://lists.fedoraproject.org/pipermail/test/2014-September/122976.html
...but we'll keep the trees flowing)
Hey --
On Thu, Sep 25, 2014, at 04:36 PM, Colin Walters wrote:
This content will land in:
http://dl.fedoraproject.org/pub/alt/fedora-atomic/repo/ under the
fedora-atomic/rawhide/x86_64/docker-host ref.
This is done now, and I'm starting a f21 compose now too
On Wed, Oct 8, 2014, at 12:26 AM, James Antill wrote:
At least one view of the model is that you have atomic upgrades, and
thus. rollback/downgrades. This fits perfectly with the f21/f21/f23
release model (although rpm-ostree rebase is very surprising when it
deletes your refs, you can still
On Thu, Oct 16, 2014, at 11:29 PM, David Gay wrote:
Hi --
At this point, I thought I'd send out an email with my current
understanding of the processes we need to add to the releng scripts for
ostree, as well as some questions regarding these compose scripts,
specifically:
Awesome, thanks
On Thu, Oct 30, 2014, at 09:12 PM, Dusty Mabe wrote:
So.. not the easiest thing to test because I couldn't find any atomic
images with this package installed.
It is possible to compose trees on your own too, using local packages. A quick
HOWTO:
yum install rpm-ostree
cd /srv
git clone
On Thu, Oct 30, 2014, at 09:34 AM, Matthew Miller wrote:
As Joe noted the other day, Fedora Atomic is intended to come with this
service, which will create storage space for Docker images. As
mentioned in the IRC meeting, at this point, the plan is to get this to
stable after the beta
Currently, the Atomic cloud image still tries to contact the compose server
internal mirror for updates.
Do we know what the final mirrorlist URL will be? Where are we on getting
content sync'd out?
___
cloud mailing list
On Mon, Nov 3, 2014, at 11:24 AM, Luke Macken wrote:
I'm not sure exactly where the final bits will live, or what the URL
will be, but the fedmsg-atomic-composer is up and running on the
composer.stg box and successfully spitting out rawhide f21 trees.
Nice. Maybe we can deprecate
this until we get patches landed, please
try:
https://alt.fedoraproject.org/pub/alt/fedora-atomic/testing/f21/20141104.0/fedora-atomic-cloud-direct-lvm-walters-20141104.qcow2.gz
From c314ed756cc3579d305867a7da13127fa6ceeb98 Mon Sep 17 00:00:00 2001
From: Colin Walters walt...@verbum.org
Date: Tue, 4
to do it right. (Will look again tomorrow.)
These are the two patches that should go on f21, backported from master. And
only the first is really needed.
From 6986a630452bb4ed75dbbdb40c0629d238c1e64b Mon Sep 17 00:00:00 2001
From: Colin Walters walt...@verbum.org
Date: Tue, 4 Nov 2014 08:30:28
On Wed, Nov 5, 2014, at 11:45 AM, Matthew Miller wrote:
On Wed, Nov 05, 2014 at 10:37:02AM -0500, Colin Walters wrote:
These are the two patches that should go on f21, backported from master.
And only the first is really needed.
Applied. Don't we also need Point to dl.fedoraproject.org
On Wed, Nov 5, 2014, at 04:11 PM, Matthew Miller wrote:
On Wed, Nov 05, 2014 at 12:22:33PM -0500, Matthew Miller wrote:
In the meantime, I'd argue that changing it for the test candidates is
a step forward from the internal URL.
Although obviously we need it to be more than rawhide.
Koji task: http://koji.fedoraproject.org/koji/taskinfo?taskID=7978937
OZ log:
https://kojipkgs.fedoraproject.org//work/tasks/8937/7978937/oz-x86_64.log
It looks to me like we hung in the rpm -qa listing. Hard to guess why without
being able to get in there with a debugger or something =/ Any
I don't think either of these are the cause of the hang, but I believe they're
both correct. Tested with a local ImageFactory run.
From 41f019b6d58f59863e282727e695ef196deac87e Mon Sep 17 00:00:00 2001
From: Colin Walters walt...@verbum.org
Date: Thu, 6 Nov 2014 20:34:38 -0500
Subject: [PATCH 1
On Fri, Nov 7, 2014, at 09:53 PM, Matthew Miller wrote:
Hi all! https://admin.fedoraproject.org/updates/cloud-init-0.7.5-8.fc21
needs testing — let's get this into F21 (and, more to the point, into
test candidates, so we can make sure it's thoroughly tested).
Hooray. So for Atomic, this gets
On Fri, Nov 7, 2014, at 08:03 AM, Dennis Gilmore wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 02 Nov 2014 16:33:57 -0500
Colin Walters walt...@verbum.org wrote:
Currently, the Atomic cloud image still tries to contact the compose
server internal mirror for updates
8cae1be2139094c173cd0af86e515f363204b9af Mon Sep 17 00:00:00 2001
From: Colin Walters walt...@verbum.org
Date: Sat, 8 Nov 2014 13:27:05 -0500
Subject: [PATCH] cloud-atomic: Re-shrink rootfs partitions
mattdm changed these previously because we hit an ENOSPC error during
qcow2 image creation, but that *really* happened because
Initial cut: https://fedoraproject.org/wiki/Changes/AtomicHost
Notably, adding bare metal (already working) and vagrant boxes (have prototype
code), and I'd like to do a diskless Live PXE image (code exists, need to put
it together and polish).
This is kept in the Cloud group, but I think the
Hi,
On Mon, Nov 10, 2014, at 08:31 AM, Josh Boyer wrote:
Er... that's a strange interpretation of how to not call something a
system wide change. Even if you had someone doing the rel-eng work,
it's still a system wide change. Particularly since it's going across
several groups and
the /dev/null as we'd like to be able to debug if it's
failing.
---
scripts/build-cloud-images | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
From 70667ab32be48c03479cc0651e01c935eee284d1 Mon Sep 17 00:00:00 2001
From: Colin Walters walt...@verbum.org
Date: Tue, 11 Nov 2014 15:39:20
cloud-init 0.7.6 now in rawhide.
This reduces the depchain even more. Worked here in some local testing,
but this is a heads up in case anyone sees fallout:
https://bugzilla.redhat.com/show_bug.cgi?id=974327
___
cloud mailing list
https://admin.fedoraproject.org/updates/rpm-ostree-2014.111-1.fc21
Will allow Atomic to be smaller, and also fixes the wheel bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1164058
Please karma.
___
cloud mailing list
cloud@lists.fedoraproject.org
On Mon, Nov 17, 2014, at 08:18 PM, Matthew Miller wrote:
Colin, what's the easiest way to test this? (Or ostree updates in
general?)
See https://lists.fedoraproject.org/pipermail/cloud/2014-October/004497.html
It'd be pretty awesome to have a test plan:
On Wed, Nov 19, 2014, at 12:06 AM, Dusty Mabe wrote:
So I tested this tonight by doing a compose with the new rpm-ostree
and then rebasing an existing system [1]. I'll give it some karma but
I will note that I don't really know how to test that the wheel group
properly got created (by
On Wed, Nov 19, 2014, at 10:55 AM, Matthew Miller wrote:
On Wed, Nov 19, 2014 at 01:59:45PM +0100, Joe Brockmeier wrote:
IIRC somebody sent the list of AMIs but I have not been able to dig it
up -- do we have a list of AMIs for current Atomic builds to use for
tomorrow's Test Day?
Hi Ravindra,
At the moment, we do not have a formal process for this. The problem is
further compounded by the fact that there is only one tree. Meaning that
open-vm-tools would end up even on other deployment targets such as bare
metal, AWS/GCE, etc.
At a high level, we are trying to coalesce
On Mon, Nov 24, 2014, at 11:09 AM, Peter Robinson wrote:
It needs some fairly low level HW access, not sure how that would
work containerised.
If you docker run --privileged, the container has total access to the host,
it's no different from any other process running as root. Try it:
#
On Tue, Dec 2, 2014, at 03:50 PM, Kushal Das wrote:
Hi everyone,
We have the RC2 cloud images ready [1]. You can help us by testing the
images following [2].
It looks to me like the Atomic tree content is lagging significantly:
# atomic status
TIMESTAMP (UTC) ID
On Tue, Dec 9, 2014, at 01:05 PM, Joe Brockmeier wrote:
It's been documented-ish but we do need to be louder about it. It would
also be awesome if virt-manager handled cloud-init too, the use an ISO
to provide cloud-init info is a little clunky.
If anyone's curious, I was trying to argue that
I should have cross posted, but here's the link:
https://lists.projectatomic.io/projectatomic-archives/atomic/2014-December/msg1.html
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora
On Thu, Jan 15, 2015, at 08:57 AM, P J P wrote:
I'm no expert on Docker(or container) applications. I was wondering if someone
could help in testing Docker(or container) applications with the local DNSSEC
validating resolver on F21.
See https://github.com/docker/docker/pull/9239
My
Hi,
On Mon, Mar 16, 2015, at 06:33 PM, Robyn Bergeron wrote:
Is that doing something different / using something different than the
image linked in
https://fedoraproject.org/wiki/Test_Results:Fedora_22_Beta_TC2_Cloud?rd=Test_Results:Current_Cloud_Test
Not a different image - the Koji one
On Tue, Mar 17, 2015, at 11:29 AM, Joe Brockmeier wrote:
Hey all,
Any Vagrant wizards around? I'd like to figure out how to mount a
directory on my local host as /var/lib/docker for the Atomic Vagrant
boxen - so users don't have to worry about other ways of expanding the
storage to putter
On Thu, Mar 19, 2015, at 12:56 PM, Matt Micene wrote:
I'd be in favor of pulling NetworkManager. It still seems that network is
the way for server class systems to handle networking
It's not that simple, at least for Atomic, because the *exact same* tree
in Fedora 22 can also be deployed
The latest tree update changed the gid for sshkeys (among other things). It
needs a backport of some rpm-ostree fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=1203006
Which are waiting on karma here:
https://admin.fedoraproject.org/updates/rpm-ostree-2015.3-1.fc21
On Thu, Mar 19, 2015, at 11:19 AM, Matthew Miller wrote:
On Thu, Mar 19, 2015 at 11:10:33AM -0400, Colin Walters wrote:
So dgilmore pointed out that f22 docker images will not have yum
installed - which means we need to update the Dockerfiles for f22 to use
dnf and not yum
On Thu, Mar 19, 2015, at 01:09 PM, Matthew Miller wrote:
On Thu, Mar 19, 2015 at 12:47:22PM -0400, Dusty Mabe wrote:
I would suggest that we adopt the approach that Fedora Cloud Base
takes by just having the Network service enabled. This would also mean
we can pull the NetworkManager
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 latest version of Docker, Kubernetes, and
On Mon, Mar 9, 2015, at 12:14 PM, Adam Miller wrote:
For those not familiar with the current release process of Atomic, can
you provide a link to documentation on how that is done as well as
what tooling is involved?
Keep in mind that the original vision for Atomic was *not* to be a
On Mon, Mar 9, 2015, at 02:49 PM, Michael P. McGrath wrote:
This one's new to me, I'm aware of the issues with building images but I
was under the impression that the composed OStree was still happening
successfully
whenever rawhide was building. Are you saying there are sometimes where
On Wed, Mar 11, 2015, at 10:52 AM, Dennis Gilmore wrote:
This is not entirely true, it is just part of the picture. You can install on
bare metal using anaconda with extlinux, exactly the same as we do to make
the
cloud image. But it is not advertised or really well documented.
But that
This change:
https://fedoraproject.org/wiki/Changes/AtomicHost
is presently blocked on:
https://fedorahosted.org/rel-eng/ticket/6119
Currently Fedora 22 will have Atomic cloud images and vagrant boxes (and an
updated tree).
It will be *possible* to install to bare metal using kickstart, but the
On Thu, Mar 19, 2015, at 10:25 AM, Daniel J Walsh wrote:
I think this would break on other machines that do not have libvirt
installed on the host.
Right, it's a problem orthogonal to the Atomic Host.
Scott we found an interesting problem with libvirt protections on
On Mon, Apr 27, 2015, at 12:14 AM, Amit Saha wrote:
Image build FAILED with error: Timed out waiting for guest to boot
There are a number of causes for that unfortunately. So...what i tend
to do is hand-mirror the installer media locally, and then edit the
TDL to point to it. This is a lot
If anyone has information on https://fedorahosted.org/rel-eng/ticket/6170
then please comment (specifically lsm5, but anyone with info).
Also this message should serve as a heads up that at least some
versions of the Fedora base image had a hardcoded root password,
and due to a snafu, we didn't
On Tue, Apr 14, 2015, at 09:41 AM, Matthew Miller wrote:
On Thu, Apr 09, 2015 at 08:31:49AM -0400, Joe Brockmeier wrote:
Here's what I'd say, lemme know if this sounds sane:
[...]
So we've decided that while the technologies are maturing so rapidly,
it's better have a fast-moving remix
[ 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 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.
On Tue, Jun 9, 2015, at 03:37 PM, Michael Adam wrote:
is this the correct place to ask?
Yes.
How are the fedora vagrant boxes created?
I.e. where is the repository describing the building
and how are these things actually built?
See:
https://fedorahosted.org/spin-kickstarts/
and search for
On Thu, Jun 4, 2015, at 12:31 PM, Josh Boyer wrote:
If you
don't have python, you don't have yum/dnf which means updating your
kernel in your cloud image at _runtime_ is a PITA.
OSTree has built in support for updating the kernel at runtime. The fact
that it does so atomically in concert
On Thu, Jul 2, 2015, at 02:39 PM, Matthew Miller wrote:
As you've probably seen, the
change calls for dist-git style management of the dockerfiles, which
would mean one repo for each one, rather than one mega-repo — the
theory being that this can scale better and allow more independence.
On Thu, May 21, 2015, at 02:36 PM, Colin Walters wrote:
On Sat, May 9, 2015, at 12:22 PM, Colin Walters wrote:
Hi,
During the Test day (and before), several people noted this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1219871
It now has a patch. I tested it with a local
On Sat, May 9, 2015, at 12:22 PM, Colin Walters wrote:
Hi,
During the Test day (and before), several people noted this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1219871
It now has a patch. I tested it with a local tree compose. It's nominated
now for Blocker/FE.
So I
On Tue, Jul 14, 2015, at 09:57 AM, P J P wrote:
Hello,
- https://lists.fedoraproject.org/pipermail/cloud/2015-January/004867.html
As per the previous discussion above, I was able to use iptables(8) DNAT rule
to divert DNS traffic from Docker containers to a DNSSEC resolver on the
On Sat, Aug 1, 2015, at 01:34 AM, Sitsofe Wheeler wrote:
The regular Fedora 22 default for password encryption seems to be
SHA512 but I couldn't turn anything up as to why cloud images had made
this change. Could some explain why MD5 is used?
This was just fixed:
Hi Robert,
On Mon, Jul 13, 2015, at 12:08 PM, Robert Knight wrote:
Failed to pull from repository: g-io-error-quark://run/install/repo/
content/repo: open: No such file or directory (1)
This sounds like https://fedorahosted.org/cloud/ticket/104
___
On Wed, Oct 28, 2015, at 08:06 PM, Matthew Miller wrote:
> On Wed, Oct 28, 2015 at 06:45:09PM -0400, Dusty Mabe wrote:
> > Right now the last booting atomic image is TC11. If we don't do
> > another compose then we won't have an atomic image for release.
>
> Can we release the two-week-atomic
On Thu, Oct 29, 2015, at 08:40 PM, Dusty Mabe wrote:
> docker 1.7 is what is in the stable f23 repo. with that we can't run a
> container with root bind mounted into it:
>
> ```
> -bash-4.3# docker run -it --rm -v /:/host busybox
> Error response from daemon: Relabeling of / is not allowed
>
On Tue, Nov 3, 2015, at 04:28 AM, Peter Robinson wrote:
> Is that the same as this procedure [1]? Or else can you point at the details?
>
> [1] http://www.projectatomic.io/blog/2014/10/getting-started-with-cloud-init/
Yes. When I want to test the cloud image I often use:
On Wed, Aug 26, 2015, at 03:00 PM, Fedora Cloud Trac Tickets wrote:
1. The new primary focus of the WG will be the atomic cloud image.
Can we try to consistently say Atomic Host when we mean that?
There's a number of things under the projectatomic/ umbrella now,
and while I know it's
On Wed, Aug 26, 2015, at 05:09 PM, Josh Boyer wrote:
Hi All,
I'm emailing my questions on the topic here as it seems to be the best
Fedora focused place to discuss Atomic Host and kernel interaction.
If that isn't the case, please point me to where you believe that is.
As jbrooks pointed
index 8761464..ebe7300 100644 --- a/fedora-atomic-docker-host.json +++
b/fedora-atomic-docker-host.json @@ -1,5 +1,5 @@ { - "ref":
"fedora-atomic/f23/x86_64/docker-
host", + "ref": "fedora-atomic/rawhide/x86_64/docker-host",
"repos": ["fedora-23"],
A mistake, right? Everything else in
On Thu, Sep 10, 2015, at 12:29 AM, Dusty Mabe wrote:
> Is that the problem that is breaking the builds? How do we get the
> location updated?
Indeed, the TDL file is broken. I believe for Koji -> ImageFactory,
Koji is generating the TDL file from some internal data.
Adam?
On Thu, Sep 10, 2015, at 12:29 AM, Dusty Mabe wrote:
> The bad news is that we are still having the same "mounting" problems
> that we were seeing in the rawhide builds where sysroot isn't mounted
> properly:
See https://bugzilla.redhat.com/show_bug.cgi?id=1235287
Try backporting those systemd
On Wed, Dec 9, 2015, at 11:40 AM, Dusty Mabe wrote:
>
>
>
On 12/04/2015 02:16 PM, Colin Walters wrote:
> > On Mon, Nov 23, 2015, at 10:35 AM, Dusty Mabe wrote:
>>
>>
>> Right, this would affect them all. As you mention below we were
>> intending for this
On Mon, Dec 7, 2015, at 08:39 PM, Adam Williamson wrote:
> Hi folks! For those who aren't aware, Fedora openQA is set up to test
> the Atomic installer image nightly - that's the image that uses
> anaconda to deploy a fixed Atomic host payload. For each day's Rawhide,
> Branched and post-release
On Mon, Nov 23, 2015, at 10:35 AM, Dusty Mabe wrote:
>
>
>
Right, this would affect them all. As you mention below we were
>
intending for this ("eth0") to be the case for a long time so I
>
figured we should fix it. You are right that this would be a change
>
over how we released
https://fedorahosted.org/rel-eng/ticket/6313
On Tue, Dec 15, 2015, at 01:48 PM, Colin Walters wrote:
> See:
> ___
> cloud mailing list
> cloud@lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/cloud@lists.fe
See:
___
cloud mailing list
cloud@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/cloud@lists.fedoraproject.org
On Mon, Dec 14, 2015, at 01:00 PM, Kushal Das wrote:
> This email is to resume the discussion on putting Networkd as network
> stack in Fedora Cloud Atomic and base images.
FWIW, my opinion on this from the Atomic Host perspective hasn't really changed
since:
On Thu, Dec 10, 2015, at 11:09 AM, Dusty Mabe wrote:
> This commit is against master.. Can you apply the change to the f23 branch?
Done: https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f23
___
cloud mailing list
On Wed, Dec 9, 2015, at 12:31 PM, Matthew Miller wrote:
> At Flock and on this list and elsewhere, we've talked about making
> Fedora Atomic our main edition-level deliverable (while still producing
> Cloud Base as something akin to a Spin).
>
> As I understand it, this is officially agreed, but
On Mon, Jan 4, 2016, at 12:35 PM, Colin Walters wrote:
> At a very high level, we need to figure out a better flow/explanation
> from the websites to deliverables. The recently updated and
> revamped ADB should also be part of this I'd say:
On this topic, what if we j
One other idea:
We simply do this by default for all cloud images, without a timeout - if no
cloud-init metadata is provided, you can log in to the hypervisor console and
see an autogenerated root password.
I'd say we should also ensure that *remote* ssh access is disabled in this
scenario -
1 - 100 of 240 matches
Mail list logo
