Re: NetworkManager and network services both enabled in Fedora Atomic

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 deplo

Re: dnf in Dockerfiles

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

Re: dnf in Dockerfiles

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 /dev/

Re: dnf in Dockerfiles

On Wed, Mar 11, 2015, at 10:23 AM, Joe Brockmeier wrote: > Hey all, > > 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. Personally, this feels like a lot of pain for little gain to me.

note: uid/gid breakage in F21 Atomic

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 _

Re: Vagrant mounting /var/lib/docker?

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 p

Re: Testables for beta TC2

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

Re: Testables for beta TC2

On Mon, Mar 16, 2015, at 03:03 PM, M. Edward (Ed) Borasky wrote: > Are there test scenarios somewhere? I can't figure out how to get a > working image from the Docker tarball. We don't have automation for upload to the Hub AFAIK, and no do we have a distribution-specific registry (though I think

Re: Atomic 2 week releases

On Fri, Mar 13, 2015, at 05:13 PM, Michael P. McGrath wrote: > > So the Atomic spins would be $current + the updates-testing packages we > care about (and have tested / have some influence over). That spin > would then be copied to the mirrors and we'd be able to link to it. > > There's a nice s

Re: Atomic 2 week releases

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 th

Re: Atomic 2 week releases

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

Re: Atomic 2 week releases

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

Re: Atomic 2 week releases

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 distrib

Re: qcow2 version woes

On Thu, Mar 5, 2015, at 01:48 PM, Mike Ruckman wrote: > [0] qemu-img amend -f qcow2 -o compat=0.10 See https://github.com/redhat-imaging/imagefactory/commit/7434c9e7506d5896508c23983b55544b0b244164 A version of ImageFactory with this commit just needs to be deployed. __

Re: Local DNSSEC resolver and Docker(containers)

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 thoug

F21 Atomic update available

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

Re: Fedora cloud qcow2 images

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

Re: Need help in testing the RC2 cloud images

On Tue, Dec 2, 2014, at 06:54 PM, Dennis Gilmore wrote: > I suspect you're testing the wrong thing. The log file at > http://koji.fedoraproject.org/koji/taskinfo?taskID=8277497 indicates > the correct version was installed. > Yes, I was thrown for a loop after downloading because the date is i

Re: Need help in testing the RC2 cloud images

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 O

Re: Adding open-vm-tools package to Fedora Atomic

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:

Re: Adding open-vm-tools package to Fedora Atomic

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 a

cloud image network config, virtio-net, libvirt autodetection, and network vs NetworkManager, F20 vs F21

TL;DR: KB, I think the CentOS cloud images should use: https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f21&id=98c48cb2b2051cc8ca81e95a697e4c8d7c5bd939 Dennis, we should revert: https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?h=f21&id=5ae38874c7c69057abd41850ad3ca27cd

Re: AMIs for Test Day?

On Wed, Nov 19, 2014, at 04:16 PM, Matthew Miller wrote: > On Wed, Nov 19, 2014 at 03:16:19PM -0500, Colin Walters wrote: > > I tested this one, it boots. However, I screwed up with: > > https://git.fedorahosted.org/cgit/fedora-atomic.git/c

Re: AMIs for Test Day?

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

Re: Please karma https://admin.fedoraproject.org/updates/rpm-ostree-2014.111-1.fc21

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 re

Re: Please karma https://admin.fedoraproject.org/updates/rpm-ostree-2014.111-1.fc21

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

Please karma https://admin.fedoraproject.org/updates/rpm-ostree-2014.111-1.fc21

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 ht

cloud-init 0.7.6 now in rawhide

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 cloud@lists.fedorapro

[PATCH] build-cloud-images: Use --version of ksflatten, and do show stderr

e 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 Date: Tue, 11 Nov 2014

Re: [atomic-devel] Fedora Change for AtomicHost

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 comp

Fedora Change for AtomicHost

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 d

[PATCH] cloud-atomic: Re-shrink rootfs partitions

From 8cae1be2139094c173cd0af86e515f363204b9af Mon Sep 17 00:00:00 2001 From: Colin Walters 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 the Fedora re

Re: final mirrorlist location for Atomic

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 wrote: > > > Currently, the Atomic cloud image still tries to contact the compose > > serv

Re: cloud init update needs testing

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 ge

Two more (mostly cosmetic) Atomic patches

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 Date: Thu, 6 Nov 2014 20:34:38 -0500 Subject: [PATCH 1/2] at

Debugging the failed Atomic compose

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

Re: help wanted -- test/karma docker-storage-setup

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 rawh

Re: help wanted -- test/karma docker-storage-setup

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

Re: help wanted -- test/karma docker-storage-setup

ocus > than I have right now 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 Date: Tue, 4 Nov

Re: help wanted -- test/karma docker-storage-setup

sting 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 Date: Tue, 4 Nov 2014 08:

Re: final mirrorlist location for Atomic

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 atomic

Re: final mirrorlist location for Atomic

On Tue, Nov 4, 2014, at 10:17 AM, Matthew Miller wrote: > Assuming that this is correct, what needs to change? Is this a > kickstart line? We should make the appropriate change _today_. That's not a globally replicated location, it means we're not taking advantage of mirrorlists. Particularly f

final mirrorlist location for Atomic

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 cloud@lists.fedoraproject.o

Re: help wanted -- test/karma docker-storage-setup

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 (be

Re: help wanted -- test/karma docker-storage-setup

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 h

Re: ostree/atomic composes + MM update

Thanks again for hacking on this! On Thu, Oct 23, 2014, at 06:38 PM, Luke Macken wrote: > > This could be done by looking at the filesystem timestamp, or Colin said > he would probably add a timestamp field to the summary file that we > could pull from. Let's go with filesystem timestamp for now,

Re: ostree compose script developments

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, th

Re: Atomic Updates - do we follow traditional model or a new one?

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

Re: Updated Atomic alpha w/Bash update(s)?

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 sta

Re: Updated Atomic alpha w/Bash update(s)?

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

Re: Updated Atomic alpha w/Bash update(s)?

On Thu, Sep 25, 2014, at 12:25 PM, Joe Brockmeier wrote: > Hi all, > > It occurs to me that the bash update isn't going to be available for the > Atomic image(s) since the users can't install new packages. Right - and this is different from the Docker image base, where users can use yum "manually

Re: [Base] Terminology for docker/atomic images

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: https://docs.docker.com/arti

Minutes for Cloud 2014-08-01

=== #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: https

New Fedora 22 Change Proposal: Fedora Atomic

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, but

Re: Cockpit in Cloud images?

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

Cockpit in Cloud images?

Hi, I was originally including Cockpit in https://fedoraproject.org/wiki/Changes/Atomic_Cloud_Image but rel-eng raised the concern that https://fedoraproject.org/wiki/Changes/CockpitManagementConsole is only listed for Server. Should we include it in Cloud too? Right now it's promoted as par

Re: [PATCH] Don't enable by default

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

[PATCH] Don't enable by default

t. This change 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: Coli

Re: Minutes from today's Cloud SIG meeting (2014-07-10)

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, 14:

Re: Taking a break or whatever - action needed, I guess

On Wed, Jul 2, 2014, at 07:58 AM, Matthew Miller wrote: > > * http://fedoraproject.org/wiki/Changes/Atomic_Cloud_Image I jumped in and added my name to this page, and cleaned it up a bit. What do people think? ___ cloud mailing list cloud@lists.fedorapr

Re: Fedora @ Google Cloud

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, an

Re: Fedora @ Google Cloud

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

Re: Fedora @ Google Cloud

On Wed, Jun 18, 2014, at 01:49 PM, Dennis Gilmore wrote: > > The issue is we are trying to build one image to run in all clouds, so > cloud provider specific tools are out. I faced a similar problem with the images I am generating with ostree, and what I ended up doing was producing a base image,

Reviewer needed for renamed min-cloud-agent

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 appr

Re: Fedora Cloud Workgroup Meeting Minutes 01 May 2014

On Wed, May 7, 2014 at 9:28 AM, Joe Brockmeier 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 people do as it's

Re: The special extlinux + grub1 situation in current Fedora Cloud

new "bootloader --disabled" to skip installing extlinux (or grub2) at all, and kept our hack to create the grub1 config. A perhaps better variant of this is (since I have the Anaconda source code open for ostree stuff anyways) is to support bootloader --pvgrub which would tell Anaconda to jus

The special extlinux + grub1 situation in current Fedora Cloud

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 support

Re: Fedora Cloud Workgroup Meeting Minutes 01 May 2014

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 do

Re: Fedora Cloud Workgroup Meeting Minutes 01 May 2014

On Thu, May 1, 2014 at 2:37 PM, Mike Ruckman 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, 08:15:47) OK, but with rpm-os

Re: Fedora Atomic and Docker Host Image [was Re: Docker Host Image: Requirements?]

On Wed, Mar 12, 2014 at 12:33 PM, James Slagle wrote: But, to be clear, someone* saying the TripleO approach is "incompatible with packaging" is equivalent to saying Fedora's builtin readonly root support is "incompatible with packaging". You are right, I was assuming that what you were t

Re: Fedora Atomic and Docker Host Image [was Re: Docker Host Image: Requirements?]

On Tue, Mar 11, 2014 at 5:17 PM, James Slagle 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 sense for certain ca

Re: Fedora Atomic and Docker Host Image [was Re: Docker Host Image: Requirements?]

On Tue, Mar 11, 2014 at 9:33 AM, James Slagle 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 partition. Such a m

Re: Fedora Atomic and Docker Host Image [was Re: Docker Host Image: Requirements?]

On Mon, Mar 10, 2014 at 8:26 PM, Steven Dake wrote: ‘1’ I would say that there are many valid ways to provision and manage machines, of which Heat/CloudFormation is one. min-metadata-service does exactly what it needs to do to provide the fundamental basis for secure remote access to the

Re: Fedora Atomic and Docker Host Image [was Re: Docker Host Image: Requirements?]

- 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

Re: Fedora Atomic and Docker Host Image [was Re: Docker Host Image: Requirements?]

On Fri, Mar 7, 2014 at 4:42 AM, Sandro red Mathys 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 Anaconda write the bootload

Re: Fedora Atomic and Docker Host Image [was Re: Docker Host Image: Requirements?]

On Thu, Mar 6, 2014 at 11:58 AM, Joe Brockmeier 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 cloud-init, but I won

Re: Fedora Atomic and Docker Host Image [was Re: Docker Host Image: Requirements?]

On Thu, Mar 6, 2014 at 11:52 AM, Matthew Miller 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 build and run the restau

Re: Fedora Atomic and Docker Host Image [was Re: Docker Host Image: Requirements?]

On Thu, Mar 6, 2014 at 8:19 AM, Sandro red Mathys 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 custom %post 3) Anacond

Re: Fedora Atomic and Docker Host Image [was Re: Docker Host Image: Requirements?]

puting 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 s

Re: Automatic Smoketests for the Cloud Images: What to Test?

On Wed, Mar 5, 2014 at 6:58 AM, Sandro red Mathys 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 scale - well, doesn'

Re: min-metadata-service 2014.2

On Tue, Feb 11, 2014 at 6:32 PM, Colin Walters wrote: Hi, https://github.com/cgwalters/min-metadata-service And here's the Fedora review request: https://bugzilla.redhat.com/show_bug.cgi?id=1066176 This got bumped up in priority for me because it needs SELinux policy (equivalent to

Re: ostree and fedora cloud

On Mon, Feb 10, 2014 at 1:37 AM, Matthew Miller 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 or so. But I also menti

min-metadata-service 2014.2

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 2014.2

Re: Future directions for Fedora Cloud

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 smal

<    1   2   3