cloud December 2016

cloud@lists.fedoraproject.org

20 participants
47 discussions

[atomic-wg] Issue #184 `ISO file is missing`
by Pagure 14 Jul '17

14 Jul '17

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Try to download the ISO at this location, as supplied by GetFedora.org: https://download.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-2… You'll find that there is no file there, and your download does not start. There is currently no way to download the Atomic ISO. In fact, it appears that none of the alternate downloads are available for 12/7: http://mirror.math.princeton.edu/pub/alt//atomic/stable/ `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/184

3 14

[atomic-wg] Issue #181 `Vagrant cannot create synced folder`
by Pagure 26 May '17

26 May '17

jorti reported a new issue against the project: `atomic-wg` that you are following: `` I just launch an unmodified fedora/25-atomic-host box and I get the error that it cannot create the /vagrant synced dir. ``` $ vagrant up Bringing machine 'default' up with 'libvirt' provider... ==> default: Creating image (snapshot of base box volume). ==> default: Creating domain with the following settings... ==> default: -- Name: mail-server_default ==> default: -- Domain type: kvm ==> default: -- Cpus: 1 ==> default: -- Memory: 512M ==> default: -- Management MAC: ==> default: -- Loader: ==> default: -- Base box: fedora/25-atomic-host ==> default: -- Storage pool: default ==> default: -- Image: /var/lib/libvirt/images/mail-server_default.img (41G) ==> default: -- Volume Cache: default ==> default: -- Kernel: ==> default: -- Initrd: ==> default: -- Graphics Type: vnc ==> default: -- Graphics Port: 5900 ==> default: -- Graphics IP: 127.0.0.1 ==> default: -- Graphics Password: Not defined ==> default: -- Video Type: cirrus ==> default: -- Video VRAM: 9216 ==> default: -- Keymap: en-us ==> default: -- TPM Path: ==> default: -- INPUT: type=mouse, bus=ps2 ==> default: -- Command line : ==> default: Creating shared folders metadata... ==> default: Starting domain. ==> default: Waiting for domain to get an IP address... ==> default: Waiting for SSH to become available... default: default: Vagrant insecure key detected. Vagrant will automatically replace default: this with a newly generated keypair for better security. default: default: Inserting generated public key within guest... default: Removing insecure key from the guest if it's present... default: Key inserted! Disconnecting and reconnecting using new SSH key... ==> default: Configuring and enabling network interfaces... ==> default: Rsyncing folder: /home/juan/Vagrant/mail-server/ => /vagrant The following SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed! mkdir -p /vagrant Stdout from the command: Stderr from the command: mkdir: cannot create directory ‘/vagrant’: Operation not permitted ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/181

2 6

[atomic-wg] Issue #180 `Future of Fedora Dockerfiles`
by Pagure 22 Feb '17

22 Feb '17

scollier reported a new issue against the project: `atomic-wg` that you are following: `` We need to decide what is going to happen with the Fedora-Dockerfiles repo located here: https://github.com/fedora-cloud/Fedora-Dockerfiles Right now I don't have enough time to maintain these properly. According to these messages: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org… and this one: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org… Looks like the direction is to deprecate Fedora-Dockerfiles. This also impacts all of the images on: https://hub.docker.com/u/fedora/ Where fedora/apache has > 1 million pulls, the rest are in the thousands and lower. So, we just need to decide, support this as a Fedora project and find a co-maintainer, or shut this down? If we shut it down, I'd like to know what the transition strategy is for moving to dist-git so I can add a message to the repo as a redirect. FWIW, I'm in favor of closing it down if the barrier to entry to dist-git isn't to high. Just looking to get final word here. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/180

3 9

next steps for migrating Cloud Base image to Fedora Server?
by Matthew Miller 08 Feb '17

08 Feb '17

I think we had general agreement around what we want to do here: have the Cloud Base Image become instead Fedora Server, but shipped as a cloud image and made available in cloud providers. What are the next steps to actually get there? -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

4 6

[atomic-wg] Issue #185 `November 21 ISO is not bootable`
by Pagure 19 Jan '17

19 Jan '17

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` I'm currently testing the November 21 ISOs by installing on my minnowboard cluster. It seems to be the case that these ISOs are not bootable; after getting through most of the install, they give the following error: failed to write boot loader configration Once the new ISOs are available, we need to retest and see if this is a general issue. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/185

3 34

Proposal: require DESCRIPTION, USAGE label for images
by Josh Berkus 11 Jan '17

11 Jan '17

Folks, Looking at the new FDLIBS, I'm noticing that there's not a narrative description of the image required or provided anywhere that I can find. Clearly one is needed for users. So, here's a proposal: New Required LABELs: USAGE: single command line giving usage example for invoking the container; will be "N/A" for some containers. DESCRIPTION: Narrative description incuding: * What service/software it provides * What specific purpose it fulfills, if required * Notes on how to use it, if not covered by USAGE, such as how to supply configuration files * Depedencies on other images (e.g. "requires a database") * Links to documentation for the Software, if any -- -- Josh Berkus Project Atomic Red Hat OSAS

4 10

[atomic-wg] Issue #182 `Autocloud is testing the wrong number of images`
by Pagure 06 Jan '17

06 Jan '17

dustymabe reported a new issue against the project: `atomic-wg` that you are following: `` Auto cloud is testing extraneous images and failing them: https://apps.fedoraproject.org/autocloud/jobs/511 There are many fewer images than that: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-2016120… `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/182

1 10

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 26 Dec '16

26 Dec '16

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2016-12-28 from 17:00:00 to 18:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Standing meeting for the Fedora Cloud Workgroup Source: https://apps.fedoraproject.org/calendar/meeting/1999/

1 0

patch for mariadb image
by Casper 25 Dec '16

25 Dec '16

Hi everybody, As I can see, the automated build on the official registry (hub.dokcer.com) is in failure since few months. I tried to reproduce it and I think I found a solution. Here is the patch, not very complex. Merry Chrismas Fedoristas! --- Dockerfile.old 2016-12-25 19:28:04.307064692 +0100 +++ Dockerfile.new 2016-12-25 19:28:51.489582337 +0100 @@ -32,7 +32,7 @@ RUN INSTALL_PKGS="rsync tar gettext host rpm -V $INSTALL_PKGS && \ dnf clean all && \ mkdir -p /var/lib/mysql/data && chown -R mysql.0 /var/lib/mysql && \ - rpm -q --qf '%{version}' mariadb-server | grep -e '10\.0\.' && \ + rpm -q --qf '%{version}' mariadb-server | grep -e '10\.1\.' && \ test "$(id mysql)" = "uid=27(mysql) gid=27(mysql) groups=27(mysql)" # Get prefix path and path to scripts rather than hard-code them in scripts -- GPG Key ID: 83288189 @ hkp://keys.fedoraproject.org Empreinte: CC26 692F 5205 AC8F 7912 7783 D7A7 F4C5 8328 8189 x509 C.A.: https://dl.casperlefantom.net/pub/root.pem Empreinte: 0975 864A 2036 0F94 A139 114A D32E 8EBE 30F2 2429

1 0

Announcing Fedora Atomic "latest" download URLs
by Adam Miller 23 Dec '16

23 Dec '16

Hello all, On behalf of the Fedora Cloud Working Group, I am happy to announce that we now have a persistent point of download for users who would like to simply reference a single URL for scripting purposes or otherwise. There is also a companion set of URLs that provide the image name that can be downloaded for informational purposes or scripting. This will allow users to download the image and know the resulting image name without any human interaction needed. The rationale behind this was to make sure that 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. The new URLs are below: https://getfedora.org/atomic_qcow2_latest https://getfedora.org/atomic_raw_latest https://getfedora.org/atomic_vagrant_libvirt_latest https://getfedora.org/atomic_vagrant_virtualbox_latest https://getfedora.org/atomic_qcow2_latest_filename https://getfedora.org/atomic_raw_latest_filename https://getfedora.org/atomic_vagrant_libvirt_latest_filename https://getfedora.org/atomic_vagrant_virtualbox_latest_filename I have also updated the Cloud Wiki[0] page to include information about these as well as a sample script of how to use them together. Thank you, -AdamM [0] - https://fedoraproject.org/wiki/Cloud#Fedora_Cloud_Atomic_Image_Download_Lin…

5 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud December 2016