Summary/Minutes from today's Fedora Infrastructure meeting (2015-02-05)
#fedora-meeting: Infrastructure (2015-02-05) Meeting started by nirik at 18:00:05 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2015-02-05/infrastructure.2015-02-05-18.00.log.html . Meeting summary --- * aloha (nirik, 18:00:05) * New folks introductions and Apprentice tasks. (nirik, 18:04:30) * Applications status / discussion (nirik, 18:07:46) * LINK: http://whatcanidoforfedora.org/ (threebean, 18:08:45) * Sysadmin status / discussion (nirik, 18:18:29) * Upcoming Tasks/Items (nirik, 18:24:52) * LINK: https://apps.fedoraproject.org/calendar/list/infrastructure/ (nirik, 18:24:52) * Open Floor (nirik, 18:34:23) Meeting ended at 18:42:54 UTC. Action Items Action Items, by person --- * **UNASSIGNED** * (none) People Present (lines said) --- * nirik (67) * threebean (19) * smooge (7) * lmacken (6) * andreasch (4) * taedori (4) * zodbot (4) * mizdebsk (2) * mhurron (2) * relrod (2) * mpduty (2) * sborza (1) * oddshocks (1) * tflink (1) * janeznemanic (1) * puiterwijk (0) * abadger1999 (0) * mdomsch (0) * pingou (0) * dgilmore (0) -- 18:00:05 #startmeeting Infrastructure (2015-02-05) 18:00:05 Meeting started Thu Feb 5 18:00:05 2015 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:05 #meetingname infrastructure 18:00:05 #topic aloha 18:00:05 #chair smooge relrod nirik abadger1999 lmacken dgilmore mdomsch threebean pingou puiterwijk 18:00:05 The meeting name has been set to 'infrastructure' 18:00:05 Current chairs: abadger1999 dgilmore lmacken mdomsch nirik pingou puiterwijk relrod smooge threebean 18:00:25 * tflink is here 18:00:29 hi 18:00:34 * lmacken 18:01:00 * sborza here 18:01:31 * threebean is here 18:01:46 hlo 18:03:07 * mizdebsk here 18:03:26 * relrod here 18:03:33 here 18:03:33 ish 18:04:17 alright then. 18:04:19 here 18:04:30 #topic New folks introductions and Apprentice tasks. 18:04:40 any new folks like to introduce themselves today? 18:04:46 or apprentices with questions or comments? 18:05:03 i'm a new apprentice, i already introduced myself on mailing list 18:05:19 mizdebsk: welcome again. ;) 18:05:27 Not to sound like a broken record, but I'm happy to update the appretice wiki page with the ansible workflow information if I can get some notes on it 18:06:24 mhurron: I'm happy to help you with that when I get time to do so. :) 18:06:29 feel free to keep nagging me. 18:06:46 yep, just keeping it on the table 18:07:35 cool. will try and get to it soon 18:07:46 #topic Applications status / discussion 18:07:54 any applications news this week? 18:08:42 It's somewhat application-related, but I've been working on a site for new contributors 18:08:45 http://whatcanidoforfedora.org/ 18:09:07 still needs work. I'm fiddling with some css issues now. 18:09:11 threebean: awesome. 18:09:23 so would this be a replacement for the join stuff? 18:09:28 hosting is on openshift. 18:10:00 nirik: yeah, well, I'm hoping it can just be another layer of links on top of that (unless people out there think the join.fedoraproject.org stuff should be ditched) 18:10:39 A bunch of work was done last week porting bodhi away from yum, which is now done. I'm currently working on porting a few other corners to createrepo_c/modifyrepo_c. 18:11:12 threebean: well, join.fedoraproject.org already is gone isn't it? 18:11:28 it just redirects to the wiki 18:11:41 oh. I didn't know there was something other than the wiki page there.. 18:11:42 lmacken: how's dnf to work with? 18:11:57 threebean: I thought there was in the past? perhaps I am misremembering 18:12:04 nirik: bodhi won't have to touch dnf at all... only librepo+createrepo_c so far. 18:12:31 lmacken: the code of that that I saw looked really nice :) 18:12:57 threebean: I tried doing it in pure-python, but hit some issues issues. In the mean time I'm just shelling out to the cli tools :\ 18:13:12 *python-creatrepo_c issues, that is 18:13:55 cool. 18:13:56 threebean, ah I was wondering who owned that website since it wasn't RH 18:14:37 smooge: been meaning to bring that up.. I can transfer the domain if that's preferred. 18:15:21 threebean, it depends on how 'official' it is 18:15:49 if it is going to be a main stream thing that has to deal with trademarks etc.. it can be easier 18:16:02 also if we plan to get a real ssl cert for it... 18:16:40 * oddshocks pops in late 18:17:38 hm, will think about it and ask around. 18:17:54 sure, sounds good. 18:18:06 any other applications news this week? 18:18:29 #topic Sysadmin status / discussion 18:18:52 lets see... I have been working on a kojipkgs01. I think I might try and swap it in tomorrow for kojipkgs02. 18:
Re: Route to Dell EquaLogic
On 02/05/2015 11:40 AM, Miroslav Suchý wrote: > 172.24.0.0 0.0.0.0 255.255.255.0 U 0 00 br-tun Hmm, I rebooted the machine and this ^^^ line disappeared from route and 172.24.0.100 is now reachable. I wish I knew what is going on. -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Route to Dell EquaLogic
On Thu, 05 Feb 2015 11:40:30 +0100 Miroslav Suchý wrote: > [root@fed-cloud09 ~(keystone_admin)]# ssh grpadmin@172.24.0.100 > ssh: connect to host 172.24.0.100 port 22: No route to host > > Nirik can this be result of your (?) change in routes that > [root@fed-cloud09 ~(keystone_admin)]# route -n > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref > Use Iface ... > 172.24.0.0 0.0.0.0 255.255.255.0 U 0 0 > 0 eth1 172.24.0.0 0.0.0.0 255.255.255.0 U 0 > 00 br-tun > > So EquaLogic is actually not routable? I didn't change any routes that I know of, nor did I change anything on the storage unit. ;( kevin pgpXkeunAM_ZU.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Proper SSL cert for fed-cloud09?
On Thu, 05 Feb 2015 10:05:22 +0100 Miroslav Suchý wrote: > On 02/05/2015 01:13 AM, Kevin Fenzi wrote: > > Could we instead call it 'openstack.cloud.fedoraproject.org' or > > 'controller.cloud.fedoraproject.org' or something? Not sure if that > > needs us to rename/reinstall the node, or can just be done in the > > cert... > > It can be just cname + name in cert. Reinstall is quite fast with > ansible, that is no problem. I automated all but one workaround > (there is still usually need one reboot). Sure, true. > > Along those same lines, how about we move the existing host > > playbooks to a group/openstack-controller.yml (currently just > > fed-cloud09, but I'd like to see if we can allocate one machine > > moving forward to be our test for the 'next' openstack) and > > group/openstack-compute.yml (fed-cloud10/11, but some more will be > > installed next week) to make them more generic and ready for more > > nodes? > > Compute node is already in roles/cloud_compute/tasks/main.yml so > migration to groups should be easy (not my priority thou). Sure. Just makes more sense to me. > I see no > benefits in migrating controller playbook to group or roles. It is > only one. I +1 to controller-next instance, because upgrade of > OpenStack is not supported. However those playbook will be quite > different and it does not have sense to have them in one playbook > with "when" directives. Good point. So how about: hosts/fed-cloud09.cloud.fedoraproject.org.yml -> hosts-> openstack-icehouse-controller.yml hosts/fed-cloud* -> groups/openstack-icehouse-compute.yml Of course this is all just somewhat cosmetic. I just wanted to do it before we added more compute nodes. kevin pgpsNRHeMTPIX.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Route to Dell EquaLogic
[root@fed-cloud09 ~(keystone_admin)]# ssh grpadmin@172.24.0.100 ssh: connect to host 172.24.0.100 port 22: No route to host Nirik can this be result of your (?) change in routes that [root@fed-cloud09 ~(keystone_admin)]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface ... 172.24.0.0 0.0.0.0 255.255.255.0 U 0 00 eth1 172.24.0.0 0.0.0.0 255.255.255.0 U 0 00 br-tun So EquaLogic is actually not routable? -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Proper SSL cert for fed-cloud09?
On 02/05/2015 01:13 AM, Kevin Fenzi wrote: > Could we instead call it 'openstack.cloud.fedoraproject.org' or > 'controller.cloud.fedoraproject.org' or something? Not sure if that > needs us to rename/reinstall the node, or can just be done in the > cert... It can be just cname + name in cert. Reinstall is quite fast with ansible, that is no problem. I automated all but one workaround (there is still usually need one reboot). > Along those same lines, how about we move the existing host playbooks > to a group/openstack-controller.yml (currently just fed-cloud09, but > I'd like to see if we can allocate one machine moving forward to be > our test for the 'next' openstack) and group/openstack-compute.yml > (fed-cloud10/11, but some more will be installed next week) to make them > more generic and ready for more nodes? Compute node is already in roles/cloud_compute/tasks/main.yml so migration to groups should be easy (not my priority thou). I see no benefits in migrating controller playbook to group or roles. It is only one. I +1 to controller-next instance, because upgrade of OpenStack is not supported. However those playbook will be quite different and it does not have sense to have them in one playbook with "when" directives. -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
