Cloud SIG meeting minutes from 2015/01/21
by Kushal Das
===================================
#fedora-meeting-1: Fedora Cloud SIG
===================================
Meeting started by kushal at 19:01:59 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2015-01-21/fedora_cloud...
.
Meeting summary
---------------
* Roll Call (kushal, 19:02:19)
* Action items from last meeting (kushal, 19:08:10)
* LINK: https://fedoraproject.org/wiki/Changes/Vagrant_Box_Atomic
(jzb, 19:15:41)
* LINK: https://fedoraproject.org/wiki/Changes/Bare_Metal_Atomic
(jzb, 19:15:54)
* LINK: https://fedoraproject.org/wiki/Changes/tunir (kushal,
19:15:55)
* LINK: https://fedoraproject.org/wiki/Changes/Local_Test_Cloud
(jzb, 19:16:22)
* LINK: https://fedorahosted.org/cloud/report/9 current meeting
tickets (kushal, 19:17:11)
* support HVM instances in EC2 (#68) (kushal, 19:17:27)
* ACTION: oddshocks should get access to the website to update AMI
ID(s) (kushal, 19:21:23)
* publicize fedora-dockerfiles #84 (kushal, 19:23:12)
* Update Timezone for the docker images #91 (kushal, 19:25:17)
* ACTION: kushal should commit the new patch for docker kickstart and
update #91 (kushal, 19:26:02)
* Getting sha256sum published for the cloud images #93 (kushal,
19:26:41)
* LINK:
http://mirror.pnl.gov/fedora/linux/releases/21/Cloud/Images/x86_64/
(dustymabe, 19:27:43)
* Decide whether to update cloud image to not include ruby #09 (kushal,
19:33:34)
* Decide whether to update cloud image to not include ruby #90 (kushal,
19:33:37)
* Open floor (kushal, 19:35:47)
Meeting ended at 20:08:15 UTC.
Action Items
------------
* oddshocks should get access to the website to update AMI ID(s)
* kushal should commit the new patch for docker kickstart and update #91
Action Items, by person
-----------------------
* kushal
* kushal should commit the new patch for docker kickstart and update
#91
* oddshocks
* oddshocks should get access to the website to update AMI ID(s)
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* kushal (109)
* jzb (51)
* dustymabe (47)
* langdon (39)
* oddshocks (17)
* zodbot (13)
* roshi (12)
* jsmith (7)
* lsm5 (6)
* nirik (3)
* gholms (2)
* scollier (1)
* misc (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Kushal
--
Fedora Cloud Engineer
CPython Core Developer
Director Python Software Foundation
http://kushaldas.in
9 years, 3 months
[PATCH] fedora-atomic-docker-host: Add the docker python module
by Luke Macken
Including the docker python client enables people to use Ansible to
manage containers.
diff --git a/fedora-atomic-docker-host.json b/fedora-atomic-docker-host.json
index 2d22efa..784e82f 100644
--- a/fedora-atomic-docker-host.json
+++ b/fedora-atomic-docker-host.json
@@ -51,7 +51,8 @@
"cockpit",
"kubernetes", "etcd", "cadvisor",
"flannel",
- "docker-io"],
+ "docker-io",
+ "python-docker-py"],
"default_target": "multi-user.target",
--
2.1.0
9 years, 3 months
[cloud] #90: Decide whether to update cloud image to not include ruby
by Fedora Cloud Trac Tickets
#90: Decide whether to update cloud image to not include ruby
------------------------------+---------------------
Reporter: ryansb | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Cloud Base Image | Keywords: meeting
------------------------------+---------------------
Now that heat-cfntools has removed its dep on Ruby, the cloud image should
be able to remove it.
Should it be rebuilt without ruby, or will users have an expectation that
it will always be included?
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/90>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
9 years, 3 months
Re: Local DNSSEC resolver and Docker(containers)
by P J P
Hello Lokesh,
> On Monday, 19 January 2015 11:01 AM, Lokesh Mandvekar wrote:
> RE: docker, I could probably patch it out at build time to use 127.0.0.1 instead
> of google DNS.
> Sound good?
I doubt if that would suffice. IIUC, the issue is that currently containerised applications have no way to reach 127.0.0.1:53 on the host. We might need a dedicated network interface on the host with a consistent IP plus few iptables(8) rules to direct traffic through.
---
Regards
-Prasad
http://feedmug.com
9 years, 3 months
Re: [atomic-devel] Fedora Activity Day at SCALE (Atomic & Cloud)
by Joe Brockmeier
On 01/15/2015 09:56 PM, Jon Stanley wrote:
> I'm more than likely going to be at SCaLE this year again, and would
> love to participate in this. I'm obviously very interested in Atomic
> and what work we can get done on that front, though I see on the
> schedule that we're more interested in Kubernetes and Dockerfiles -
> which is cool as well. I can help on the latter a bit, not so much the
> former (but would LOVE to learn!!)
That's a draft, and the schedule can be changed / driven by those who
are going to show up.
Feel free to add ideas/topics. Glad to know you'll be attending - look
forward to seeing you at SCALE!
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
9 years, 3 months
Local DNSSEC resolver and Docker(containers)
by P J P
Hello all,
Please see:
-> https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver
-> https://pjps.wordpress.com/2014/05/02/local-dns-resolver-in-fedora/
This is an upcoming F22 feature; it proposes to install a local DNSSEC
validating DNS resolver running at 127.0.0.1:53 on Fedora systems. This
feature is already available in F21. One can easily run the local DNSSEC
enabled resolver by
$ sudo yum install dnssec-trigger
$ sudo systemctl enable dnssec-triggerd.service
$
$ # disable and stop any existing DNS service, e.g., dnsmasq
$ sudo systemctl start dnssec-triggerd.service
Though it works for most of the use-cases. Docker(or container) applications
seem to face problems in accessing the host's DNS resolver at 127.0.0.1:53.
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.
Any results from this exercise would be immensely helpful in fixing bugs and
sorting out edge cases, thus making the solution robust and ready for F22 release.
I'm willing to help in any way I could. As always, your comments and suggestions
are most welcome!
Thank you.
---
Regards
-Prasad
http://feedmug.com
9 years, 3 months