puppet to ansible migration status (2015-02-20)
Greetings. I thought I would send out a little status on where we are with puppet->ansible migration currently. We are currently down to 28 machines left in puppet: "app01.stg.phx2.fedoraproject.org" I think the only thing left here is the websites building stuff. We could move that to sundries01.stg and nuke it. "bapp02.phx2.fedoraproject.org" This needs the mm2 deployment to finish as well as the websites building stuff. We could move that to sundries01 now I guess, but the rest will depend on mm2. "backup02.fedoraproject.org" I have been keeping this around until our backup storage in RDU2 is live. I was hoping that to have already happened, so I might rebuild this somewhere and make it use rdiff-backup. "bastion-comm01.qa.fedoraproject.org" Need to schedule a time to rebuild this with qa folks. "bodhost01.fedoraproject.org" "proxy07.fedoraproject.org" This needs to be re-installed. We may be able to get an unattended ks to work on it now that we know some of the pitfalls better. "collab03.fedoraproject.org" "collab04.fedoraproject.org" "hosted-lists01.fedoraproject.org" I was hoping for hyperkitty/mailman01/02 to be live so we wouldn't need to migrate these, but again I am loosing hope and we might just look at making a mailman 2 playbook and migrating them to get it done. "darkserver01.phx2.fedoraproject.org" Needs kushal to confirm it's all working on rhel7 and then we can reinstall. "db02.stg.phx2.fedoraproject.org" This needs the rest of the postgresql db's migrated to db01.stg and/or dumped/restored from production. Then, it also needs new mediawiki and paste so we can get rid of mysql. However, I fear that also will not happen anytime soon, so I might make a db03.stg that is mariadb. "db05.phx2.fedoraproject.org" This was waiting for mediawiki and paste to move to postgres, but I guess I will look at making a playbook and moving it to ansible/mariadb before then sometime. Probibly after alpha. "hosted03.fedoraproject.org" "hosted04.fedoraproject.org" I need to build out the trac stack on epel7 for this. I am thinking I might try and do so during freeze if anyone would like to help out. Then, we can look at moving them after freeze. They also will need playbooks. "internetx01.fedoraproject.org" "proxy02.fedoraproject.org" These need reinstall (but hosted-lists01 is also there, so it needs migrating first). "osuosl02.fedoraproject.org" This has collab03 and hosted03 on it. Need to ansiblize them and move them to osuosl03 and then we can reinstall this one. "people03.fedoraproject.org" Needs playbook. We could also look at migrating it somewhere else to get it off the ibiblio servers we need to reinstall. "releng01.stg.phx2.fedoraproject.org" "releng04.phx2.fedoraproject.org" "relepel01.phx2.fedoraproject.org" I am going to work on these today/this weekend. They need to stay rhel6 due to bodhi1, but shouldn't be too hard to bang out playbooks for them. If I can get them in time I would love to finish them before freeze. "serverbeach09.fedoraproject.org" Smooge was going to do this one soon... "secondary01.phx2.fedoraproject.org" This one needs a playbook. Should be pretty easy if someone would like to whip one up. "torrent02.fedoraproject.org" Needs figuring our our torrent seed software and seeing if there's any chance there's something better out there. Also needs playbook. "virthost-comm01.qa.fedoraproject.org" Need to migrate everything off this and retire it. Should be able to do so soon as we have virthost-comm04 up and ready. Might try and work on these during freeze as well. "ibiblio02.fedoraproject.org" "ibiblio03.fedoraproject.org" These need reinstall and it's going to be a bit tricky as the reinstall from 6->7 needs a full wipe. We should hopefully be able to migrate things around to 04 enough to do this as well as moving things we don't need. "lockbox01.phx2.fedoraproject.org" This will be the last machine to leave the building. ;) So, I am hoping to work on legwork during freeze and push again after freeze to get more done. Ideally we could get this done before Beta freeze if all the stars align. ;) kevin pgpPn4a7bxM_K.pgp Description: OpenPGP digital signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: [release] pkgdb2 1.23.995
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dne 20.2.2015 v 16:47 Pierre-Yves Chibon napsal(a): > > - Replace the monitoring toggle button by one that might be clearer > Beauty, thx :) Vít -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJU51jTAAoJEAzgnueZF7h8TUgP/1Si44BmqqJylHcM0aiJvje6 Pf1KCmDHQtm/WxSfeNWBQK2evs32nlHvSQetCzxN24aUs/ZB7daPLncgvwYsFxE3 zXY+y8hgxfwjFZzCy2n+QPdwwkeRo/Za4T5oIfXFgZETHLI5SaQB3wyt4u6Deeeq 5eldevmt0a0yD2mk1qrXbqpsidKDc2E2P49l4eTv1fXpR3NHGe+a5cdNuyQVdnJJ aKntm67KGIreVqQXwpxHI12XUiFqzvGD4ppRNGrkNIq35q0w/6AJCP2VvH17WjAW E4kUXdTyby1j4/FCWoFGt0Bc0lOAuwEPW/NblE1fU5KeDqdsHwGoR1vSwKdoCqQK uEGX/yHmxZqJmHRuXb8utRwWEls/BUDSTwMO3Ms/pDbPaQXbQhtQ4ntgc0T7ctcV 5nnApUnt7iR9gCrbIDuDMIR3lxdog9dyEM0HkfGtG2o2JahMICfLJNsyk2A1PIn4 4qA3bSRXMVyMdMSVnWUhBvDYPECQC+ICsf5bxlce30Vv16JuTDWugtDuNXCXDbim FMEtQs5b5b5X9g/zdd4z0Y2QRHE/ytK8NpFOtnwoGDAmBksLd8LEiIl+4OPMJtSH cqj7UXkKG7aMHEs9Kjh9skvsx3Ps2qud25Lxxub/Iz/25acr4yED42nZKUuXmoV6 443LZawvK9w0iDsWmgHd =fLAq -END PGP SIGNATURE- ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
[release] pkgdb2 1.23.995
Hi all, To keep up with the good habit, here is today's pkgdb2 release: 1.23.994 and since I am not sure I'll be able to make another one tomorrow, I did a second one just after to be sure: 1.23.995 :-) Changelog: * Fri Feb 20 2015 Pierre-Yves Chibon - 1.23.995-1 - Update to 1.23.995 (pre-release of 1.24) - Fix the link to `My Requests` on the API documentation page * Fri Feb 20 2015 Pierre-Yves Chibon - 1.23.994-1 - Update to 1.23.994 (pre-release of 1.24) - Do not use insecure connection to pkgdb in set_monitoring_status (Till Maas) - Add documentation for the API endpoint to set the monitoring status of a package - Replace the monitoring toggle button by one that might be clearer - Fix actually setting the monitoring flag of new package to True (and adjust the tests for this) Enjoy and as usual, feel free to complain :) Pierre pgp0PPHX_h8kI.pgp Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
New OpenStack instance - status
Since I'm leaving for one week vacation, I think I may write down current status of our new OpenStack instance and write down TODO list. Just in case someone is desperate enough to do some fixes. I updated docs.git/cloud.txt - mainly which playbooks we use right now and where to write down IP, when you add new compute node. Controller - should be OK. At least I see no problems there right now. Network is stable. I can log to EqualLogic (credentials are at bottom of cinder.conf). Volumes are created correctly. I can reach compute nodes. AMQP works and is reachable from Compute nodes (do not try to play with SSL&RabbitMQ it will never work on RHEL7). Horizon works (over https). Compute nodes - it looks good until you try to start VM. :) I fixed several problems, but new ones still pop ups. If you want to debug it, just go to dashboard and start new VM (note that m1.tiny is too small for Fedora image) and on controller do: tail -f /var/log/nova/nova-scheduler.log And look for something like: Choosing host WeighedHost [host: fed-cloud13.cloud.fedoraproject.org, weight: 1.0] for instance 75f1b5ca-88d5-4e57-8c18-8d6554e1f2bc then log to that instance (right now root@fed-cloud09 can ssh directly as root@fed-cloudXX) and tail -f /var/log/nova/nova-compute.log /var/log/neutron/openvswitch-agent.log When spin up of VM fail, then controller try 2 next machines before giving up. Right now there is some error: TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'\n" which is new to me and which I will not manage to fix before I will leave today. It may be last one problem or they may be dozen other still waiting in queue. It's hard to tell. Smaller fixes to do: * playbook hosts/fed-cloud09.cloud.fedoraproject.org.yml can be enhanced that after packstack execution the machine should be restarted. Right now I am waiting for first error after packstack and then I restart the machine manualy and re-run playbook again. This is last manual workaround. Everything else was already automated. * routing between compute nodes and controller using public IP does not work. Not fatal right now, but nice to have. -- 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
Meeting Agenda Item: Introduction Taehwan Kim
Hello I would like to become a Fedora Infrastructure Apprentice. My name is Taehwan Kim aspiring a python developer that want to work and contribute to open source community such as fedora. First of all, I have looked up Fedora apps several times, but I can't figure out where to start exactly. I am interested in project that python developer can participate to contribute and learn from. what about bohdi or badge? (I found those project uses python and pyramid web framework) ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
Re: Removing item from fedocal
On Fri, Feb 20, 2015 at 08:58:31AM +0100, Honza Horak wrote: > Hi, > > I'd like to ask for removing the following fedocal event: > > https://apps.fedoraproject.org/calendar/location/fedora-meeting%40irc.freenode.net/#m391 > > (env&stacks meeting was moved to another room and slot) > > I've tried to contact organizers, but they didn't respond. > > Is anybody from admins able to do that for me, please? Deleted :) Pierre ___ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
