November 2016 - cloud - Fedora mailing-lists

Python is missing in Fedora AWS AMIs
by Danishka Navin 29 Dec '22

29 Dec '22

Hi team, Is there any specific reason to drop python from Fedora AMIs in AWS? Regards, -- Danishka Navin http://danishkanavin.blogspot.com http://twitter.com/danishkanavin

6 5

[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

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

[atomic-wg] Issue #176 `status of kubernetes on fedora atomic 25`
by Pagure 22 Dec '16

22 Dec '16

jasonbrooks reported a new issue against the project: `atomic-wg` that you are following: `` We removed kubernetes, etcd, flannel, gluster and ceph from the atomic host for Fedora 25: https://pagure.io/fedora-atomic/c/219c9bb26426811a5f32188c59682ad70c3283e5?… The idea is that these pkgs can/should be run as docker containers or system containers. I wrote a post about running kube in containers on CentOS Atomic, but things work the same for Fedora Atomic: http://www.projectatomic.io/blog/2016/09/running-kubernetes-in-containers-o… However, we don't currently have fedora containers for kubernetes. There's a year-old PR for this: https://github.com/fedora-cloud/Fedora-Dockerfiles/pull/112. I used this PR as the basis for kube containers for CentOS: https://github.com/CentOS/CentOS-Dockerfiles/tree/master/kubernetes. Another option is using package layering to install the removed rpms if desired: http://www.projectatomic.io/blog/2016/07/hacking-and-extending-atomic-host/. This works, mostly, but the kube-apiserver that comes with kubernetes-master is granted CAP_NET_BIND_SERVICE so it can use port 443, and package layering won't support this: https://github.com/projectatomic/rpm-ostree/issues/462. Whether we install kubernetes via package layering or containers, another issue is that the kube we have for fedora 25 is very old, 1.2, and current is 1.4.5. There's a kube 1.4.5 in koji for fc26 (http://koji.fedoraproject.org/koji/buildinfo?buildID=816481) and I've asked Jan about making it available for fedora 25. I built it for f25 and el7 in this copr: https://copr.fedorainfracloud.org/coprs/jasonbrooks/kubernetes/. kubeadm (http://kubernetes.io/docs/getting-started-guides/kubeadm/) is a slick way to run an up-to-date kube cluster, and the kubernetes project offers rpms for kubeadm, but the kubernetes-cni package they provide doesn't work with atomic. I made a patched package in a copr for f25 and el7 (https://copr.fedorainfracloud.org/coprs/jasonbrooks/kube-release/) and wrote about it here: https://jebpages.com/2016/11/01/installing-kubernetes-on-centos-atomic-host…. The rpm grabs the binaries from the upstream project, if fedora were to provide this package, we'd probably want to build the binaries ourselves. kubeadm runs kubernetes and etcd in containers, and these containers aren't fedora-based, and they come from upstream. They appear to be based on busybox. Also, kubeadm is considered alpha at this point. We should: * try to move to a more recent kubernetes version * get kubernetes containers in place for fedora * get fedora versions of the flannel and etcd system containers in place * document how to install kubernetes and how to use package layering on fedora * look further into kubeadm `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/176

1 12

Issue with bodhi ostree composes
by Dusty Mabe 01 Dec '16

01 Dec '16

There is an error that is happening in the composes. Here is the full log: https://paste.fedoraproject.org/494447/raw/ here is the specific error I think: error: bwrap test failed, see <https://github.com/projectatomic/rpm-ostree/pull/429>: Child process exited with code 1 Any ideas on getting this one fixed? Dusty

1 1

List of F26 features from Atomic Working Group
by Kushal Das 01 Dec '16

01 Dec '16

Hi all. It is time again to create the list of features we (Atomic Working Group) will be working on for Fedora 26. We want to discuss the features in this week's IRC meeting. But first everyone should put up the ideas to this thread. This will help us to create a proper agenda for Wednesday's meeting. Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org

2 2

[atomic-wg] Issue #160 `Ship fedora-motd in F24 atomic image`
by Pagure 30 Nov '16

30 Nov '16

rtnpro added a new comment to an issue you are following: `` @walters I created an issue[1] to work on migrating from cron to systemd. Regarding the first run of ``motdgen-cache-updateinfo``, I am not a big fan of it being run from the PAM stack. That's why I have a workaround in place. ## Use cases ### Installing fedora-motd manually User can run ``/usr/bin/motdgen`` manually post install to cache update details. Hence, in subsequent runs, neither ``atomic`` or ``dnf`` update info will be checked. May be we can run ``/usr/bin/motdgen`` post install. Also, another way is to start ``motdgen.service`` or enable it at boot. So, ``atomic`` and ``dnf`` commands won't be run at all from the PAM stack, because it has already been run, post install or at system boot. ### Enabling fedora-motd in images We can enable ``motdgen.service`` at system boot. This will execute ``atomic`` and ``dnf`` commands only during first boot and cache the results. This will result in displaying the motd data from the cached update info result. @walters what do you think? Is this workaround good enough? [1]: https://github.com/rtnpro/motdgen/issues/8 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/160

1 0

[atomic-wg] Issue #160 `Ship fedora-motd in F24 atomic image`
by Pagure 30 Nov '16

30 Nov '16

rtnpro added a new comment to an issue you are following: `` I did not manage to work on it post walter's review. I will be off for quite some time from next week on account of my marriage. It will be great if someone can lend me a hand to see this feature to completion. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/160

1 0

Atomic Composes since 11/21
by Dusty Mabe 29 Nov '16

29 Nov '16

It looks like all composes but rawhide composes have been failing since 11/21. Do we know what the problem is here? Similarly there haven't been any new f25 ostrees since 11/16. I don't know if the two are related or not (probably). Anybody know what is going on or do I need to start digging? Dusty

2 2

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 28 Nov '16

28 Nov '16

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2016-11-30 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

Article idea: Launch fedora on dply.co
by Matthew Miller 25 Nov '16

25 Nov '16

I came across this on Reddit yesterday — a Digital Ocean employee has a service where you can launch test images in a cloud environment really easily from a website with a github account. You get two hours for free. Since Digital Ocean has Fedora (Dusty tells me Fedora 25 should be available RSN), Fedora is an option. I was thinking about a Fedora Magazine article once F25 is available, with a direct link to actually launch a Fedora instance, and some screenshots showing how it works. I'm talking with the creator about also adding Fedora Atomic, and it occured to me that we could have some followup articles with things like "set up Wordpress in a container on Fedora Atomic" with pre-cooked configs for doing that with a button press. To try it (Fedora 24), click this: https://dply.co/b/fz95S8RH -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

2 1

[atomic-wg] Issue #5 `tracker for GCE work`
by Pagure 24 Nov '16

24 Nov '16

mattdm added a new comment to an issue you are following: `` CentOS isn't officially there directly - it's provided by SoftLayer. I'm not sure of all of the details behind that. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/5

1 0

[atomic-wg] Issue #5 `tracker for GCE work`
by Pagure 24 Nov '16

24 Nov '16

pschiffe added a new comment to an issue you are following: `` Is there somewhere more information about the legal issues? For example, why it's ok for centos to be there? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/5

1 0

[atomic-wg] Issue #5 `tracker for GCE work`
by Pagure 24 Nov '16

24 Nov '16

mattdm added a new comment to an issue you are following: `` We are probably still blocked on legal issues for getting a listing, but that doesn't mean it shouldn't _work_. We could also better document the process by which users can get the image uploaded themselves. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/5

1 0

[atomic-wg] Issue #5 `tracker for GCE work`
by Pagure 24 Nov '16

24 Nov '16

pschiffe added a new comment to an issue you are following: `` This seems to be some kind of regression, Fedora 24 cloud image (`Fedora-Cloud-Base-24-1.2.x86_64.raw.xz`) works fine. I've created bug: https://bugzilla.redhat.com/show_bug.cgi?id=1398388 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/5

1 0

[atomic-wg] Issue #5 `tracker for GCE work`
by Pagure 24 Nov '16

24 Nov '16

pschiffe added a new comment to an issue you are following: `` Hello, could we reopen this? Fedora still doesn't work correctly in GCE. I've just tried F25 cloud image (`Fedora-Cloud-Base-25-1.3.x86_64.raw.xz`), but the cloud-init is unable to communicate with GCE metadata servers. Full log can be seen here http://paste.fedoraproject.org/489121/47999081/ There is Cloud-init v. 0.7.8. In current state, it's not possible to login to such instance. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/5

1 0

The Fedora Prioritized bugs and issues process
by Jan Kurik 24 Nov '16

24 Nov '16

Hi everybody, as discussed in [1] email thread, we are starting the "Fedora Prioritized bugs and issues process" [2]. The main goal is to identify and make more visible bugs and issues which have critical impact on a Fedora Edition or on a council-approved Fedora Objective. We will start with our first evaluation meeting on Wednesday November the 30th, 2016 at 15:00 UTC on #fedora-meeting IRC channel [3]. I will be happy if people interested in participation on the evaluation will let me know, so we can setup the initial Evaluation team. [1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… [2] https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_a… [3] https://apps.fedoraproject.org/calendar/Fedora%20release/2016/11/28/#m5154 Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic

1 0

Fedora 25 Cloud Base Images
by Dusty Mabe 23 Nov '16

23 Nov '16

We currently don't have a download page for the Fedora 25 cloud base image. This is because we did a poor job of communicating with the websites team (our fault, not theirs) before Fedora 25 release. There will be a new site for the cloud base image at https://cloud.fedoraproject.org/ This is tracked by https://pagure.io/fedora-websites/issue/57 In the meantime here is the information for the cloud base image for Fedora 25 release: RAW - https://download.fedoraproject.org/pub/fedora/linux/releases/25/CloudImages… QCOW - https://download.fedoraproject.org/pub/fedora/linux/releases/25/CloudImages… Vagrant Libvirt - https://download.fedoraproject.org/pub/fedora/linux/releases/25/CloudImages… Vagrant Virtualbox - https://download.fedoraproject.org/pub/fedora/linux/releases/25/CloudImages… And for AWS: Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-1) ami-c28bdea2 hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-2) ami-0bea476b hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (sa-east-1) ami-001c836c hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-west-1) ami-ffe8b88c hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-central-1) ami-b2c603dd hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-2) ami-499ea12a hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-1) ami-992182fa hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (sa-east-1) ami-031c836f paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-2) ami-8aeb46ea paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-1) ami-688edb08 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-west-1) ami-c8e7b7bb paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-central-1) ami-2ac10445 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-2) ami-eb9ea188 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-1) ami-6a258609 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-2) ami-36eb4656 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-northeast-1) ami-633f9402 hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-northeast-1) ami-f3248f92 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-2) ami-3dea475d hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (sa-east-1) ami-c51986a9 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-1) ami-6889dc08 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-1) ami-5c8bde3c hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (sa-east-1) ami-021c836e hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-west-1) ami-40e6b633 hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-central-1) ami-bac603d5 hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-2) ami-ca9fa0a9 hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-1) ami-00278463 hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-northeast-1) ami-68389309 hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-west-1) ami-03e6b670 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-central-1) ami-fec60391 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-2) ami-cb9fa0a8 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-1) ami-6e25860d paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-northeast-1) ami-663f9407 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-east-1) ami-e5ad85f2 hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-east-1) ami-0fac8418 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-east-1) ami-86ac8491 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-east-1) ami-56a08841 hvm gp2 - Dusty

1 0

Cloud Meeting Minutes 2016-11-23
by Trishna Guha 23 Nov '16

23 Nov '16

Summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-23/fedora_atomic… Full Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-23/fedora_atomic… ============================================== #fedora-meeting-1: Fedora Atomic Working Group ============================================== Meeting started by kushal at 17:03:57 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-23/fedora_atomic… . Meeting summary --------------- * Roll Call (kushal, 17:04:05) * Action items from last meeting (trishnag, 17:06:12) * Future of Fedora Dockerfiles https://pagure.io/atomic-wg/issue/180 (trishnag, 17:08:57) * ACTION: kushal will write to list for the agenda of the features meeting for Atomic group (sayan, 17:09:12) * Fedora Cloud Base Vagrant Boxes Don't Allow Vagrant User To su To Other Users https://pagure.io/atomic-wg/issue/173 (trishnag, 17:11:11) * Finish new Fedora Cloud PRD https://pagure.io/atomic-wg/issue/170 (trishnag, 17:12:49) * Spec for IRC bot to notify about blockers https://pagure.io/atomic-wg/issue/169 (trishnag, 17:14:23) * ACTION: kushal to update #169 (kushal, 17:24:58) * Ship fedora-motd in F24 atomic image https://pagure.io/atomic-wg/issue/160 (trishnag, 17:25:34) * Proposed website changes for Cloud Base → Atomic Host switch https://pagure.io/atomic-wg/issue/158 (trishnag, 17:27:22) * make Fedora Atomic download page clearer https://pagure.io/atomic-wg/issue/154 (trishnag, 17:29:23) * design, deploy and document Fedora OpenShift Playground (FOSP) https://pagure.io/atomic-wg/issue/153 (trishnag, 17:30:12) * vagrant boxes fixups https://pagure.io/atomic-wg/issue/136 (trishnag, 17:38:35) * Future of Fedora Dockerfiles https://pagure.io/atomic-wg/issue/180 (trishnag, 17:43:13) * Open Floor (trishnag, 17:53:18) * LINK: https://pagure.io/fedora-websites/issue/57 (dustymabe, 17:54:27) Meeting ended at 18:00:25 UTC. Action Items ------------ * kushal will write to list for the agenda of the features meeting for Atomic group * kushal to update #169 Action Items, by person ----------------------- * kushal * kushal will write to list for the agenda of the features meeting for Atomic group * kushal to update #169 * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * trishnag (73) * dustymabe (65) * kushal (35) * scollier (23) * misc (19) * zodbot (15) * gholms (13) * sayan (12) * maxamillion (9) * rmartinelli (6) * jbrooks (2) * bowlofeggs (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[atomic-wg] Issue #160 `Ship fedora-motd in F24 atomic image`
by Pagure 23 Nov '16

23 Nov '16

trishnag added a new comment to an issue you are following: `` We need to ship this for f25. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/160

1 0

[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
by Pagure 23 Nov '16

23 Nov '16

mattdm added a new comment to an issue you are following: `` I have two small ones. First, I think the freshness indicator is not visible enough in the top bar. Maybe that's just me. I guess, for one thing, it's easy to gloss over header-section text, but also, there's no indication that that's a dynamic value. What about changing "Produced N days ago" to "Produced N days ago, on YYYY-MM-DD" (or whatever internationalized date format the web team prefers)? Second, it currently says "1 days ago". I'd love that to be properly special-cased to "1 day ago", or even better, "yesterday". And "0 days ago" could be "today" or "fresh for you just today!" `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154

1 0

[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
by Pagure 23 Nov '16

23 Nov '16

dustymabe added a new comment to an issue you are following: `` I would say update the wiki page, but whatever works. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154

1 0

[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
by Pagure 23 Nov '16

23 Nov '16

mattdm added a new comment to an issue you are following: `` Should we update Josh's wiki page above or put proposals here? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154

1 0

[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
by Pagure 23 Nov '16

23 Nov '16

dustymabe added a new comment to an issue you are following: `` @jberkus - now we can propose new changes to the F25 page. please schedule some time for interested parties to get together and go over your proposed changes. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154

1 0

[atomic-wg] Issue #173 `Fedora Cloud Base Vagrant Boxes Don't Allow Vagrant User To su To Other Users`
by Pagure 23 Nov '16

23 Nov '16

The issue: `Fedora Cloud Base Vagrant Boxes Don't Allow Vagrant User To su To Other Users` of project: `atomic-wg` has been assigned to `dustymabe` by trishnag. https://pagure.io/atomic-wg/issue/173

1 0

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
by Pagure 23 Nov '16

23 Nov '16

walters added a new comment to an issue you are following: `` Oh, sorry, I was reading the git log and missed that we already did back out the change: https://pagure.io/fedora-kickstarts/c/6f3661e3a5f2625b73ee8e998087285d7c6e7… Nevermind. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174

1 0

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
by Pagure 23 Nov '16

23 Nov '16

dustymabe added a new comment to an issue you are following: `` > One should be able to configure static IPs via nmcli in bootcmd hooks in cloud-init, so I'd like to back out the change to enable network.service. hmm. I don't think we enabled network.service ``` -bash-4.3# systemctl status NetworkManager | cat ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2016-11-22 20:20:04 UTC; 19h ago Docs: man:NetworkManager(8) Main PID: 32401 (NetworkManager) Tasks: 4 (limit: 4915) Memory: 44.0M CPU: 1min 29.555s CGroup: /system.slice/NetworkManager.service ├─32401 /usr/sbin/NetworkManager --no-daemon └─32465 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-eth0.pid -lf /var/lib/NetworkManager/dhclient-5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0 Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6560] device (veth01b40c4): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6563] policy: disabling autoconnect for connection 'Wired connection 6'. Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <warn> [1479915956.6564] device (veth01b40c4): Activation: failed for connection 'Wired connection 6' Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6565] device (veth158a7ac): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6567] policy: disabling autoconnect for connection 'Wired connection 5'. Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <warn> [1479915956.6568] device (veth158a7ac): Activation: failed for connection 'Wired connection 5' Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6575] device (veth01b40c4): state change: failed -> disconnected (reason 'none') [120 30 0] Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6584] device (veth158a7ac): state change: failed -> disconnected (reason 'none') [120 30 0] Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6595] device (veth01b40c4): enslaved to non-master-type device ovs-system; ignoring Nov 23 15:45:56 ip-10-0-177-155.ec2.internal NetworkManager[32401]: <info> [1479915956.6597] device (veth158a7ac): enslaved to non-master-type device ovs-system; ignoring Warning: NetworkManager.service changed on disk. Run 'systemctl daemon-reload' to reload units. -bash-4.3# -bash-4.3# systemctl status network | cat Warning: network.service changed on disk. Run 'systemctl daemon-reload' to reload units. ● network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network; generated; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174

1 0

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
by Pagure 23 Nov '16

23 Nov '16

jasonbrooks added a new comment to an issue you are following: `` We talked about enabling the network service, but we instead patched cloud-init to make NM work. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174

1 0

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
by Pagure 23 Nov '16

23 Nov '16

kushal added a new comment to an issue you are following: `` Somehow I want to shout "networkd" "networkd" :) `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174

1 0

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
by Pagure 23 Nov '16

23 Nov '16

walters added a new comment to an issue you are following: `` I think this: `` this has prevented me from then managing the network (I tried w/ a static ip) from a cloud-init datasource. I'm pretty sure we don't want that. ``` is independent of the "no networking on boot" problem, which is what was fixed by cloud-init. One should be able to configure static IPs via `nmcli` in `bootcmd` hooks in cloud-init, so I'd like to back out the change to enable `network.service`. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174

1 0

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
by Pagure 23 Nov '16

23 Nov '16

dustymabe added a new comment to an issue you are following: `` @walters. what exactly do you want to revert? We added the [patch](http://pkgs.fedoraproject.org/cgit/rpms/cloud-init.git/commit/?id=b4… to cloud-init to make it so that networkmanager can read the files and bring up networking. @gholms we need to send that patch upstream. Are you game? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174

1 0

[atomic-wg] Issue #174 `network not coming up in fah25 qcow2`
by Pagure 23 Nov '16

23 Nov '16

walters added a new comment to an issue you are following: `` Err wait, so can't we revert this now? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/174

1 0

Fedora Atomic Host Two Week Release Announcement
by noreply＠fedoraproject.org 22 Nov '16

22 Nov '16

2 1

[atomic-wg] Issue #178 `Locales are completely broken in the base image.`
by Pagure 22 Nov '16

22 Nov '16

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` TL;DR: it is impossible to load a real locale in the base image. This breaks many applications. In regular Fedora, locale is now part of systemd. The mini-systemd in the container base image does not include localctl, and as a result no real locale can be loaded. Try, for example, getting your locale set to en_US.utf8. You can't do it. This means that any server application which depends on server locale ... such as PostgreSQL or HTTPD ... cannot be delpoyed to production on our base image. Currently there's no workaround for this except installing *all* of systemd, which is like 100MB of packages. Must fix. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/178

1 14

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 21 Nov '16

21 Nov '16

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2016-11-23 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

Fedora 25 Compose for Release Day
by Dusty Mabe 21 Nov '16

21 Nov '16

Looks like we have a candidate for release for F25 Atomic this week. This is the Fedora-Atomic-25-20161120.0 production compose and all links to ISOs and cloud images are below. The autocloud tests all passed https://apps.fedoraproject.org/autocloud/jobs/491. Please take some time and see if everything works as expected. ISO - https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-2016112… QCOW - https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-2016112… Vagrant Libvirt - https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-2016112… Vagrant Virtualbox - https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-2016112… The AWS AMIs are: Fedora-Atomic-25-20161120.0.x86_64 EC2 (us-west-2) ami-928428f2 hvm standard Fedora-Atomic-25-20161120.0.x86_64 EC2 (us-west-2) ami-9f8b27ff hvm gp2 Fedora-Atomic-25-20161120.0.x86_64 EC2 (sa-east-1) ami-f93ca395 hvm standard Fedora-Atomic-25-20161120.0.x86_64 EC2 (us-west-1) ami-65065205 hvm standard Fedora-Atomic-25-20161120.0.x86_64 EC2 (eu-west-1) ami-c6c290b5 hvm standard Fedora-Atomic-25-20161120.0.x86_64 EC2 (eu-central-1) ami-3c71b453 hvm standard Fedora-Atomic-25-20161120.0.x86_64 EC2 (ap-southeast-2) ami-882d13eb hvm standard Fedora-Atomic-25-20161120.0.x86_64 EC2 (ap-southeast-1) ami-68af0d0b hvm standard Fedora-Atomic-25-20161120.0.x86_64 EC2 (ap-northeast-1) ami-f846f399 hvm standard Fedora-Atomic-25-20161120.0.x86_64 EC2 (us-west-1) ami-dd0652bd hvm gp2 Fedora-Atomic-25-20161120.0.x86_64 EC2 (sa-east-1) ami-63fb650f hvm gp2 Fedora-Atomic-25-20161120.0.x86_64 EC2 (eu-west-1) ami-f6dd8f85 hvm gp2 Fedora-Atomic-25-20161120.0.x86_64 EC2 (eu-central-1) ami-e970b586 hvm gp2 Fedora-Atomic-25-20161120.0.x86_64 EC2 (ap-southeast-2) ami-ef2b158c hvm gp2 Fedora-Atomic-25-20161120.0.x86_64 EC2 (ap-southeast-1) ami-c2a90ba1 hvm gp2 Fedora-Atomic-25-20161120.0.x86_64 EC2 (ap-northeast-1) ami-dd45f0bc hvm gp2 Fedora-Atomic-25-20161120.0.x86_64 EC2 (us-east-1) ami-32251225 hvm standard Fedora-Atomic-25-20161120.0.x86_64 EC2 (us-east-1) ami-a7380fb0 hvm gp2 Dusty

2 1

Testing the RC1.3 images
by Dusty Mabe 18 Nov '16

18 Nov '16

I think RC1.3 is what we are going with on Tuesday. Please take some time to test out the RC1.3 images so we can find/document any issues that we need to. You can find them on this page: https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.3_Cloud Also, the EC2 images are: Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-1) ami-c28bdea2 hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-2) ami-0bea476b hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (sa-east-1) ami-001c836c hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-west-1) ami-ffe8b88c hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-central-1) ami-b2c603dd hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-2) ami-499ea12a hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-1) ami-992182fa hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (sa-east-1) ami-031c836f paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-2) ami-8aeb46ea paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-1) ami-688edb08 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-west-1) ami-c8e7b7bb paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-central-1) ami-2ac10445 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-2) ami-eb9ea188 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-1) ami-6a258609 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-2) ami-36eb4656 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-northeast-1) ami-633f9402 hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-northeast-1) ami-f3248f92 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-2) ami-3dea475d hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (sa-east-1) ami-c51986a9 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-1) ami-6889dc08 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-west-1) ami-5c8bde3c hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (sa-east-1) ami-021c836e hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-west-1) ami-40e6b633 hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-central-1) ami-bac603d5 hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-2) ami-ca9fa0a9 hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-1) ami-00278463 hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-northeast-1) ami-68389309 hvm gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-west-1) ami-03e6b670 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (eu-central-1) ami-fec60391 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-2) ami-cb9fa0a8 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-southeast-1) ami-6e25860d paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (ap-northeast-1) ami-663f9407 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-east-1) ami-e5ad85f2 hvm standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-east-1) ami-0fac8418 paravirtual standard Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-east-1) ami-86ac8491 paravirtual gp2 Fedora-Cloud-Base-25-1.3.x86_64 EC2 (us-east-1) ami-56a08841 hvm gp2

2 1

[atomic-wg] Issue #153 `design, deploy and document Fedora OpenShift Playground (FOSP)`
by Pagure 18 Nov '16

18 Nov '16

misc added a new comment to an issue you are following: `` So I was a bit tired, and replaced "roundrobin" with "balance", then spent 5 minutes pondering why it was "balance balance" in the config file, and how did I managed to make a wrong search/replace.... So yeah, replacing roundrobin by source make it work better, so next step is "plugging to fedora auth". And then deploy something. We also need a domain name, IIRC we had one, no ? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/153

1 0

Discussion about overlay vs devicemapper for docker-storage-setup in Fedora
by Dusty Mabe 17 Nov '16

17 Nov '16

dwalsh sent a message to the devel list about this. Follow along/respond here: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…

1 0

[atomic-wg] Issue #153 `design, deploy and document Fedora OpenShift Playground (FOSP)`
by Pagure 17 Nov '16

17 Nov '16

misc added a new comment to an issue you are following: `` @walters yep, origin. https://github.com/fedora-cloud/fosp-playbooks/blob/master/hosts#L42 @scollier I just see firefox asking me to always accept the certificate (even when I did accept 5 seconds ago), but I didn't dig into why (as it was kinda working before I did clean the config file and refactored it). my intuition was that Firefox was just seeing a different certificate on each request due to the load balancing on tcp level rather than http. I will try "balance". `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/153

1 0

[atomic-wg] Issue #154 `make Fedora Atomic download page clearer`
by Pagure 17 Nov '16

17 Nov '16

dustymabe added a new comment to an issue you are following: `` This is going to need to be reworked for F25. After next week let's sit down and apply your sketch to the new pages. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/154

1 0

Separate Repository for Atomic Specific Fedora-Dockerfiles
by Trishna Guha 17 Nov '16

17 Nov '16

Hi, We have a repository on Github named Fedora-Dockerfiles [0]. The Repository contains Dockerfiles but those are not **atomic** specific. So adding ability to use **atomic** command will make **other hosts** lose the ability to use the Dockerfiles. Since we are focusing on having production ready Dockerfiles for Atomic host, Should we create a separate repository that contains Atomic specific Dockerfiles? [0] https://github.com/fedora-cloud/Fedora-Dockerfiles -- Regards, Trishna Guha

4 6

Move F25 Atomic to "Production" composes
by Dusty Mabe 17 Nov '16

17 Nov '16

Hi releng, It is a week before Fedora 25 will be released and the Atomic images are still using the "nightly" composes. When can we expect the production composes that run daily (i.e. RC-20161114.0) to start producing F25 images rather than F24 images? We really need this so that we can test things before next week. Thanks! Dusty

1 2

[atomic-wg] Issue #153 `design, deploy and document Fedora OpenShift Playground (FOSP)`
by Pagure 16 Nov '16

16 Nov '16

scollier added a new comment to an issue you are following: `` > So, I have added my own auth there. For now, i suspect I have been a bit too optimist with haproxy and the roundrobin setup is not working as I hope (I am just forwarding the port 8443 to the 3 master nodes, so maybe I should just set a ssl certificate on the bastion and be done with it). FWIW, we have been using "balance" as the method, not roundrobin. Things seem to be working on our end. What did you end up doing here? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/153

1 0

Cloud Meeting Minutes 2016-11-16
by Trishna Guha 16 Nov '16

16 Nov '16

Full Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-16/fedora_atomic… Summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-16/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by trishnag at 17:00:37 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-16/fedora_atomic… . Meeting summary --------------- * Roll Call (trishnag, 17:00:41) * ACTION: kushal will write to list for the agenda of the features meeting for Atomic group (kushal, 17:05:26) * Action items from last meeting (trishnag, 17:07:07) * LINK: https://pagure.io/atomic-wg/issue/176 (jbrooks, 17:07:37) * Fedora Cloud Base Vagrant Boxes Don't Allow Vagrant User To su To Other Users https://pagure.io/atomic-wg/issue/173 (trishnag, 17:31:42) * ACTION: trishnag will create an issue on tunirtests for https://pagure.io/atomic-wg/issue/173 (trishnag, 17:35:29) * Finish new Fedora Cloud PRD https://pagure.io/atomic-wg/issue/170 (trishnag, 17:36:07) * Spec for IRC bot to notify about blockers https://pagure.io/atomic-wg/issue/169 (trishnag, 17:37:55) * Ship fedora-motd in F24 atomic image https://pagure.io/atomic-wg/issue/160 (trishnag, 17:39:51) * Proposed website changes for Cloud Base → Atomic Host switch https://pagure.io/atomic-wg/issue/158 (trishnag, 17:42:27) * make Fedora Atomic download page clearer https://pagure.io/atomic-wg/issue/154 (trishnag, 17:45:30) * design, deploy and document Fedora OpenShift Playground (FOSP) https://pagure.io/atomic-wg/issue/153 (trishnag, 17:47:44) * vagrant boxes fixups https://pagure.io/atomic-wg/issue/136 (trishnag, 17:50:38) * LINK: https://github.com/redhat-imaging/imagefactory/pull/392 (jbrooks, 17:55:06) * Open Floor (trishnag, 17:57:46) Meeting ended at 18:01:04 UTC. Action Items ------------ * kushal will write to list for the agenda of the features meeting for Atomic group * trishnag will create an issue on tunirtests for https://pagure.io/atomic-wg/issue/173 Action Items, by person ----------------------- * kushal * kushal will write to list for the agenda of the features meeting for Atomic group * trishnag * trishnag will create an issue on tunirtests for https://pagure.io/atomic-wg/issue/173 * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * trishnag (55) * dustymabe (44) * jbrooks (32) * kushal (23) * maxamillion (19) * zodbot (15) * scollier (10) * walters (3) * sayan (2) * bowlofeggs (1) * rtnpro (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[atomic-wg] Issue #136 `vagrant boxes fixups`
by Pagure 16 Nov '16

16 Nov '16

jasonbrooks added a new comment to an issue you are following: `` for discussion, I created this PR: https://github.com/redhat-imaging/imagefactory/pull/392 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/136

1 0

[atomic-wg] Issue #158 `Proposed website changes for Cloud Base → Atomic Host switch`
by Pagure 16 Nov '16

16 Nov '16

dustymabe added a new comment to an issue you are following: `` mattdm and I are meeting with robyduck today to try to get a formal request in for cloud.fp.o `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/158

1 0

Proposal: su-exec in Fedora Base Image
by Josh Berkus 15 Nov '16

15 Nov '16

Someone's written a tiny C implementation of gosu: https://github.com/ncopa/su-exec This is invaluable for entrypoint scripts, as a way of demoting permissions without losing TTY. Could we include it? -- -- Josh Berkus Project Atomic Red Hat OSAS

4 3

[atomic-wg] Issue #153 `design, deploy and document Fedora OpenShift Playground (FOSP)`
by Pagure 15 Nov '16

15 Nov '16

walters added a new comment to an issue you are following: `` Are you deploying Origin? See also https://github.com/openshift/openshift-ansible/issues/1560 `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/153

1 0

[atomic-wg] Issue #153 `design, deploy and document Fedora OpenShift Playground (FOSP)`
by Pagure 15 Nov '16

15 Nov '16

misc added a new comment to an issue you are following: `` As Patrick asked on IRC, by "my own auth", I have used the Htpassword provider for now. I plan to switch to using the Fedora auth system once I have at least a clue on what I am doing regarding auth, and making susre the system work. There is also a bit of refactoring to do, cause for now, there is no role at all. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/153

1 0

[atomic-wg] Issue #153 `design, deploy and document Fedora OpenShift Playground (FOSP)`
by Pagure 15 Nov '16

15 Nov '16

misc added a new comment to an issue you are following: `` So, I have added my own auth there. For now, i suspect I have been a bit too optimist with haproxy and the roundrobin setup is not working as I hope (I am just forwarding the port 8443 to the 3 master nodes, so maybe I should just set a ssl certificate on the bastion and be done with it). `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/153

1 0

[atomic-wg] Issue #153 `design, deploy and document Fedora OpenShift Playground (FOSP)`
by Pagure 15 Nov '16

15 Nov '16

misc added a new comment to an issue you are following: `` So, summit took more of my time, and so did vacations, and Centos interlock meeting as well. But I did manage to get openshift exposed on the web, then found that default auth is "all is valid". I acurrently redeploying the cluster with a regular user (instead of admin/admin). `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/153

1 0

[atomic-wg] Issue #177 `Disable interactive "cp" in fedora base image`
by Pagure 15 Nov '16

15 Nov '16

jberkus reported a new issue against the project: `atomic-wg` that you are following: `` Currently, the "cp" command in fedora base image is "cp -i" interactive, as is it with Fedora Workstation. This can cause "cp" commands in dockerfile scripts to fail, because of the interactive prompt, causing a lot of debugging frustration. We should switch to standard "cp" in the base image. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/177

1 10

[atomic-wg] Issue #179 `Improve mechanism to disable predictable network interface names`
by Pagure 14 Nov '16

14 Nov '16

spasche reported a new issue against the project: `atomic-wg` that you are following: `` Cloud images are currently masking /etc/udev/rules.d/80-net-setup-link.rules to disable predictable network interface names (https://pagure.io/fedora-kickstarts/blob/9e8d98f16315a05ebf953ee6a165b70a05…) This has the unwanted side effect of breaking systemd-networkd in some cases (details here: https://lists.freedesktop.org/archives/systemd-devel/2016-November/037796.h…) Lennart found an alternative that consists of masking /etc/systemd/network/99-default.link instead. Official wiki page was updated accordingly: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfa… Cheers, Sylvain `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/179

1 0

[atomic-wg] Issue #158 `Proposed website changes for Cloud Base → Atomic Host switch`
by Pagure 14 Nov '16

14 Nov '16

dustymabe added a new comment to an issue you are following: `` I gave review and feedback in the original ticket that was opened for this: https://fedorahosted.org/fedora-websites/ticket/406#comment:1 Please make any further comments/review there. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/158

1 0

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 14 Nov '16

14 Nov '16

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2016-11-16 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

Meeting minutes from 2016-11-09
by Kushal Das 14 Nov '16

14 Nov '16

============================================== #fedora-meeting-1: Fedora Atomic Working Group ============================================== Meeting started by kushal at 17:01:59 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-09/fedora_atomic… . Meeting summary --------------- * Roll call (kushal, 17:02:11) * https://pagure.io/atomic-wg/issue/158 website change for atomic (kushal, 17:08:30) * LINK: https://stg.getfedora.org/en/cloud/ (kushal, 17:10:59) * Open Floor (kushal, 17:16:11) * ACTION: jbrooks to file issue on kube situation w/ f25 atomic (jbrooks, 17:27:41) * LINK: https://lists.fedoraproject.org/archives/list/cloud@lists.fedoraproject.org… (dustymabe, 17:36:55) Meeting ended at 17:40:45 UTC. Action Items ------------ * jbrooks to file issue on kube situation w/ f25 atomic Action Items, by person ----------------------- * jbrooks * jbrooks to file issue on kube situation w/ f25 atomic * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * kushal (58) * dustymabe (34) * jbrooks (34) * zodbot (15) * bowlofeggs (5) * maxamillion (5) * walters (4) * sayan (3) * trishnag (2) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org

1 0

Re: [Marketing] Feedback needed on Fedora 25 announcements
by Dusty Mabe 10 Nov '16

10 Nov '16

On 11/10/2016 12:01 PM, Brian Proffitt wrote: > Dusty: > > Added your changes. in them, you mentioned a "yum/rpm environment". Should that be "dnf/rpm"? > Yep! Thanks

1 0

[Marketing] Feedback needed on Fedora 25 announcements
by Brian Proffitt 10 Nov '16

10 Nov '16

All: To prepare for the anticipated release of Fedora 25, we have started the process of drafting the Fedora 25 release announcement and press release. The release announcement[1] needs the most input. I have based it on the Fedora 25 beta release announcement and will be going through the document today to clean up any obvious beta mentions. Members of each workgroup should focus on: * Additional features to highlight that were not in the beta announcement * Important stories that you think this announcement should be telling * Particular focus on the change from "Cloud" to "Atomic." The press release is templated from the Fedora 24 press release[2] and will be revised based on the release announcement. Therefore, the priority is on the release announcement, and feedback should be given to that document by close of business (2100 UTC) November 7, 2016. Thank you, Brian Proffitt

2 1

Blogs for F25 release
by Dusty Mabe 10 Nov '16

10 Nov '16

I believe we need to communicate a few things for F25: 1 - overlayfs - what it is, how to enable it in the various f25 images we release 2 - containerized k8s - no longer in atomic host so we have to show people how to use it I am already planning to write the first blog post. Any volunteers for the 2nd one. Any more blogs that need to go out? Dusty

4 7

Re: [Test-Announce] Fedora 25 Candidate RC-1.2 Available Now!
by Adam Williamson 10 Nov '16

10 Nov '16

On Wed, 2016-11-09 at 16:02 -0800, rawhide(a)fedoraproject.org wrote: > According to the schedule [1], Fedora 25 Candidate RC-1.2 is now > available for testing. Please help us complete all the validation > testing! For more information on release validation testing, see: > https://fedoraproject.org/wiki/QA:Release_validation_test_plan > > Test coverage information for the current release can be seen at: > https://www.happyassassin.net/testcase_stats/25 > > You can see all results, find testing instructions and image download > locations, and enter results on the Summary page: > > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Summary > > The individual test result pages are: > > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Installation > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Base > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Server > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Cloud > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Desktop > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.2_Security_Lab > > All RC priority test cases for each of these test pages [2] must > pass in order to meet the RC Release Criteria [3]. > > Help is available on #fedora-qa on irc.freenode.net [4], or on the > test list [5]. There are two changes from RC-1.1 in RC-1.2: libblockdev-1.9-8.fc25 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-76a96e8bf3 selinux-policy-3.13.1-224.fc25 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-f29b746f2e those fix a couple of partitioning bugs kparal found in RC-1.1: https://bugzilla.redhat.com/show_bug.cgi?id=1393379 https://bugzilla.redhat.com/show_bug.cgi?id=1393373 Unfortunately both packages can at least *theoretically* affect almost anything else (selinux-policy for obvious reasons, and libblockdev because anaconda uses it), so it would be good to re-run as many tests as we can with this compose. Sorry for the extra work, folks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Fedora Atomic 2016-11-09 RC Testing == Nightly Testing
by Dusty Mabe 09 Nov '16

09 Nov '16

Hey all, In Fedora Atomic the release process is disjoint from the rest of Fedora in that our images aren't produced as part of the normal "production" composes and RCs. I will make it a point to send out an email like this on the same day that every RC is created in Fedora so that we can attempt to verify our images continue to work throughout the process. Please take some time and attempt to confirm our images from last nights compose is working: [qcow] http://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161109.n.0/c… [vagrant-libvirt] http://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161109.n.0/c… [vagrant-virtualbox] http://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161109.n.0/c… Note that currently the ISO images aren't getting created. This is tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1392698 Dusty

2 1

Re: [Test-Announce] Fedora 25 Candidate RC-1.1 Available Now!
by Adam Williamson 09 Nov '16

09 Nov '16

On Wed, 2016-11-09 at 00:36 -0800, rawhide(a)fedoraproject.org wrote: > According to the schedule [1], Fedora 25 Candidate RC-1.1 is now > available for testing. Please help us complete all the validation > testing! For more information on release validation testing, see: > https://fedoraproject.org/wiki/QA:Release_validation_test_plan > > Test coverage information for the current release can be seen at: > https://www.happyassassin.net/testcase_stats/25 > > You can see all results, find testing instructions and image download > locations, and enter results on the Summary page: > > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Summary > > The individual test result pages are: > > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Installation > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Base > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Server > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Cloud > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Desktop > https://fedoraproject.org/wiki/Test_Results:Fedora_25_RC_1.1_Security_Lab > > All RC priority test cases for each of these test pages [2] must > pass in order to meet the RC Release Criteria [3]. > > Help is available on #fedora-qa on irc.freenode.net [4], or on the > test list [5]. > > Current Blocker and Freeze Exception bugs: > http://qa.fedoraproject.org/blockerbugs/current > > [1] http://fedorapeople.org/groups/schedule/f-25/f-25-quality-tasks.html > [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan > [3] https://fedoraproject.org/wiki/Fedora_25_RC_Release_Criteria > [4] irc://irc.freenode.net/fedora-qa > [5] https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/ Hi folks! Sending this along to more lists, with an extra note: the Fedora 25 Go/No-Go is on Thursday - yes, tomorrow for most of the world - so we need YOU to help run all the tests! We need to fill out all of the Alpha, Beta and Final (not 'RC', as the mail says...I should fix that) tests on all the validation pages. Some particular tests that it'd be great to have people working on are the Server tests, non- English installs, and the Desktop 'menus' tests, which basically mean 'install Workstation or KDE and run every single app that's installed and make sure they all at least basically work'. If you run into any serious issues, please propose them as Final blockers, either using blockerbugs: https://qa.fedoraproject.org/blockerbugs/propose_bug or simply by marking the bug as 'Blocks: FinalBlocker' (and please add a comment with an explanation of why you think it should block release). Thanks a lot, everyone! Note, there is one bug currently accepted as a blocker which is not addressed by this compose: https://bugzilla.redhat.com/show_bug.cgi?id=1382001 but there is clearly some sentiment to drop its blocker status, so we decided to go ahead and run a compose and get it tested so if we do decide to drop that bug from the blocker list, and no other blockers appear, we can ship. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

2 1

[atomic-wg] Issue #158 `Proposed website changes for Cloud Base → Atomic Host switch`
by Pagure 09 Nov '16

09 Nov '16

dustymabe added a new comment to an issue you are following: `` > The dark text on purple around "atomic cli" is a little tough to read. Yeah, on this page: https://stg.getfedora.org/en/cloud/ - the Atomic CLI section does not look good. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/158

1 0

[atomic-wg] Issue #158 `Proposed website changes for Cloud Base → Atomic Host switch`
by Pagure 09 Nov '16

09 Nov '16

jasonbrooks added a new comment to an issue you are following: `` The dark text on purple around "atomic cli" is a little tough to read. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/158

1 0

[atomic-wg] Issue #160 `Ship fedora-motd in F24 atomic image`
by Pagure 09 Nov '16

09 Nov '16

rtnpro added a new comment to an issue you are following: `` @walters I got that. I will fix fedora-motd based on your feedback and share it for review by this weekend. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/160

1 0

Fedora Release Tools Demo (Canceled) - Written Status
by Amanda Carter 07 Nov '16

07 Nov '16

Hi folks, due to travel and various obstacles, we're not able to host a recorded demo this month. Instead we've put together a status report that includes some additional highlights we think you might be interested in. If you have feedback and/or think this works well, I'd love to know b/c I think this vehicle covers more information than a demo alone so I might do both in the future if it's worth it. Apologies for missing the actual show and tell - if there's anything you'd like to see specifically, I'm sure we can arrange something. https://fedoraproject.org/wiki/ReleaseEngineering/StatusReport#13SEP2016 -- Amanda Carter

1 2

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 07 Nov '16

07 Nov '16

Dear all, You are kindly invited to the meeting: Fedora Cloud Workgroup on 2016-11-09 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

[atomic-wg] Issue #175 `Fedora 24 atomic image Fedora-Atomic-24-20161025.0.x86_64.qcow is not allowing ssh`
by Pagure 04 Nov '16

04 Nov '16

kushal reported a new issue against the project: `atomic-wg` that you are following: `` Even though autocloud managed to ssh, when I tried to ssh into an instance on our OpenStack, it never allowed a connection. Opening this ticket to dig more into this. * https://apps.fedoraproject.org/autocloud/jobs/1016/output * http://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-24-20161025… `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/175

1 5

Connection Refused on SSH to Fedora Atomic 24 QCOW2 Image
by Trishna Guha 03 Nov '16

03 Nov '16

Hi all, There is Connection refused issue when I am trying to ssh to the current Fedora Atomic 24 Qcow2 image [1]. Here is the connection refused failure for it on Autocloud [2]. [1] http://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-24-20161031… [2] https://apps.fedoraproject.org/autocloud/jobs/1083/output

2 2

Docker Layered Image Naming and Tagging
by Adam Miller 02 Nov '16

02 Nov '16

Hello all, I was recently discussing some items around docker layered image release process in the future with Randy (bowlofeggs) and Patrick (puiterwijk). As a side effect of our discussion there were two questions I wanted to ask of the Cloud WG: 1) Do we want to maintain docker images for every Fedora Release or do we want to focus only on latest? (i.e. - do we want to maintain them like we do rpms or take a different position) 2) Do we want to keep around multiple versions of a container? For example: If we had the following images: registry.fedoraproject.org/cockpit:0.95-1.23 registry.fedoraproject.org/cockpit:0.95-1.24 registry.fedoraproject.org/cockpit:0.95-1.25 One we release to stable 0.95-1.25, can we delete -1.24 and/or -1.23? What kind of retention do we want here? (Note that rpm content does not currently maintain a N and N-1 in the repositories) Thank you, -AdamM

4 14

FYI: F25 image builds - none for the past few days
by Dusty Mabe 01 Nov '16

01 Nov '16

On thursday night the image builds didn't run because pagure was intermittently down. For the past 2 nights they have failed to build. I'm not sure why exactly but there is some libvirt error [1] in the logs. Dennis has been looking into this for us. I'm hoping we can an image built to look at before the freeze on Tuesday. If we do get one I'll post here and ask everyone to give it a spin if they can. Dusty [1] https://kojipkgs.fedoraproject.org//work/tasks/4430/16254430/oz-x86_64.log

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud November 2016