cloud October 2016

cloud@lists.fedoraproject.org

21 participants
110 discussions

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

26 Oct '16

walters added a new comment to an issue you are following: `` The previous discussion on this was https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2016-Apr… which I didn't reply to. Okay, so you said: ``` The file /etc/motdgen.d/02-updateinfo.sh does nothing but cat the content of /var/run/updateinfo.txt if available. ``` which, looking at https://kojipkgs.fedoraproject.org//packages/fedora-motd/0.1.2/2.fc25/noarc… isn't true, since I see this code: ``` cat etc/motdgen.d/02-updateinfo.sh ... if [ ! -f "$firstrun" ]; then touch $firstrun nohup /usr/bin/motdgen-cache-updateinfo & fi # cat usr/bin/motdgen-cache-updateinfo #!/bin/sh if [ -f /run/ostree-booted ]; then rpm-ostree upgrade --check --preview > /var/run/rpmostree_updateinfo.out ... ``` We're hence starting a potentially long running process out of the PAM stack, which is really not a good idea. Invoking rpm-ostree like this will also block other clients as I said (And that's also true of yum/dnf) - which is again very problematic if the "login" is actually Ansible where you're trying to do things like configure a proxy or mirror. Deleting the first run bit would deal with the biggest of my objections, but then we'd still have the cron job (which itself is problematic because we *just* got rid of cron - this should be a systemd timer) An architecture which is event driven and would implement the "only check automatically if explicitly invoked at least once" is to patch rpm-ostree to do something like `systemctl start --no-block system-motdgen.service` after it's completed a transaction. Then the motd code could call back with the DBus API for `GetCachedUpdateDetails`. `` 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 26 Oct '16

26 Oct '16

1 0

Deploy Containers, Containerized Application on Atomic host with Ansible
by Trishna Guha 25 Oct '16

25 Oct '16

Hi, The purpose is to make Fedora atomic host production ready. I have been working with containers on Atomic host a lot. The idea is to automate docker build, run process for docker image and containers on atomic host, this is where Ansible comes in to play. There is also an interesting tool Ansible-container [0] which helps to build docker image and orchestrate docker container without writing Dockerfiles (Only with playbooks). Also we have a great tool Cockpit to manage containers using web interface. I have recently written an article [1] on Fedora magazine which describes how to deploy containers on Atomic host with Ansible and manage with Cockpit. This blog [2] gives an insight on containerization and deployment of application on Atomic host with Ansible playbook. Here is the repository where I am keeping the playbooks [3]. If the idea seems interesting to cloud-wg/atomic-wg it would be nice to have a repository under github.com/fedora-cloud :-). Also feel free to dive into the project if you really find it interesting :-). [0] https://docs.ansible.com/ansible-container [1] https://fedoramagazine.org/deploy-containers-atomic-host-ansible-cockpit [2] https://trishnag.wordpress.com/2016/10/25/containerization-and-deployment-o… [3] https://github.com/trishnaguha/fedora-cloud-ansible Any suggestion or comment will be appreciated. Thanks, Trishna

1 0

Test Day: Docker Swarm Test -- PASSED
by Josh Berkus 24 Oct '16

24 Oct '16

As an additional test, I set up a 3-node Docker Swarm cluster. This worked fine (after fixing the docker-storage-setup issues). I was able to deploy a service to multiple nodes. Note that the Docker documentation isn't accurate when it comes to what ports you need to expose. -- -- Josh Berkus Red Hat OSAS (any opinions are my own)

1 0

should we release new fedora cloud image for f24
by Dusty Mabe 24 Oct '16

24 Oct '16

As part of the next release of Fedora 24 atomic host should we also release the Fedora 24 base image so that the released version doesn't have the latest huge kernel bug in it by default? Dusty

2 3

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

24 Oct '16

rtnpro added a new comment to an issue you are following: `` @walters could you outline the steps to ship fedora-motd in fedora atomic image build? `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/160

1 0

[Fedocal] Reminder meeting : Fedora Cloud Workgroup
by Dusty Mabe 24 Oct '16

24 Oct '16

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

weird error with docker-storage-setup
by Dusty Mabe 24 Oct '16

24 Oct '16

I haven't had time to really investigate but figured I would pass this along: qcow: http://kojipkgs.fedoraproject.org/compose/branched/Fedora-25-20161021.n.0/c… test results from last night's test run: https://apps.fedoraproject.org/autocloud/jobs/971/output error: [fedora@cloudhost ~]$ sudo systemctl status -l docker-storage-setup.service ● docker-storage-setup.service - Docker Storage Setup Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; enabled; vendor preset: disabled) Active: inactive (dead) Oct 21 18:40:37 localhost.localdomain systemd[1]: docker-storage-setup.service: Job docker-storage-setup.service/start deleted to break ordering cycle starting with multi-user.target/start Warning: docker-storage-setup.service changed on disk. Run 'systemctl daemon-reload' to reload units. [fedora@cloudhost ~]$ echo $? 3

3 5

Join Us for a Fedora 25 Test Day Next Week (October 24, 2016)
by Jason Brooks 24 Oct '16

24 Oct '16

Want to help make Fedora Atomic Host even better? Join us next week for the Fedora Cloud Test Day, where we’ll be banging on the Atomic Host image for Fedora. As always, we’re looking for many hands to help put the release through its paces. To participate, you’ll need a system with Vagrant, libvirt/KVM, or access to OpenStack or another IaaS that can consume the qcow or raw images for Atomic. Alternately, if you have an Amazon Web Services account, there will be AMIs you can test; check the wiki page for links on the test day. Grab the image from the wiki [0], and then check out the test results page [1] to see the tests you should run and report the results. [0] https://fedoraproject.org/w/index.php?title=Test_Day:2016_10_24_Cloud [1] http://testdays.fedorainfracloud.org/events/11 We also encourage freestyle testing as well, so if you have use cases that go beyond the described tests please do put the image through those tests as well. For example, you could test setting up a Kubernetes cluster or even OpenShift. Found bugs? Be sure to report them on Bugzilla. Always Be Testing If you can’t make it for the scheduled test day, no sweat. You can play along at home any time. You can find updated nightly images for Fedora Atomic and Fedora Cloud Base, alongside the results of automated tests, at the Autocloud site [2]. You can find an image type and version you’re interested in testing, click the Output button next to the test results, and download the image using the Download Image on the output page. [2] https://apps.fedoraproject.org/autocloud/jobs/ Communicating During and After Test Days We’ll have folks watching #fedora-test-day on Freenode, and (as always) folks in #fedora-cloud and #atomic. If you have questions, or think you can help others, please join in! Also, there’s always the cloud(a)lists.fedoraproject.org mailing list [3] for additional conversations around the Fedora Atomic Host images. Please sign up, and feel free to chime in any time with questions, comments, suggestions, or to raise a hand to help out. See you on Test Day! [3] https://lists.fedoraproject.org/admin/lists/cloud.lists.fedoraproject.org/

2 3

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

20 Oct '16

jasonbrooks added a new comment to an issue you are following: `` @imcleod What do you think of this: https://github.com/jasonbrooks/imagefactory/commit/fab77b7824167ea7bfc6cd51… I experimented with the route you took and wasn't getting it working, but this is working for me. It adds an empty optical drive as a slave to the existing controller. If it'd be better to add another controller for this, that should be doable, too. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/136

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cloud October 2016