I took a look at what rhel6 instances we have left and wrote up a little status report:
easy:·
These just need a sysadmin-main person to do them. I might try and do them before freeze, but if someone else wants to, great:
smtp-mm* (one done in prod, just do other 2) unbound-tummy01 (others already done in prod, 1 left)
not too hard:·
These are the ones where we need a playbook written or where they are already in ansible, but we need to reinstall them with 7 and make sure all the needed packages for that application are available there.
fas* (needs playbook) ns* (needs playbook) secondary01 (needs playbook) virthosts (some need outage) sign-vaults (needs being careful) backup03 (needs outage and being careful) blockerbugs* (needs playbook) (all these are in ansible, just need reinstall for rhel7) (all these have multiple instances, so no outage hopefully) badges-web* download-rdu* elections* fedocal* github2fedmsg* notifs-web* nuancier* packages* pkgdb* summershum* tagger* value*·
hard:·
These are ones we need outages for or more thought, or work on packages. I don't think we will be doing any of these until after f21 is out, but over the holidays might be a nice time to do some of them when things are quiet.
pkgs01 (done in stg, needs testing and outage) proxies (needs thought about how to setup) db* (playbooks done, needs outages) hosted* (needs thinking) koji* (needs replacement for heartbeat) kojipkgs* (needs outage) paste* (needs new paste version in epel7 with unbundling) ask* (need to try and get askbot working in epel7) people03 (outage, lots of data to move) torrent02 (needs whatever torrent software we can stand in epel7) wiki (waiting on next LTR mediawiki)
impossible:·
These are ones where it's not really possible to move the current thing to 7, and we are waiting for the next major version.
bodhi* (bodhi1) collab* (mailman2) hosted-lists* (mailman2) mirrorlists (mirrormanager) releng* (bodhi1) sundries* (mirrormanager)
kevin
On Fri, Oct 10, 2014, at 01:51 PM, Kevin Fenzi wrote:
impossible:·
These are ones where it's not really possible to move the current thing to 7, and we are waiting for the next major version.
bodhi* (bodhi1) collab* (mailman2) hosted-lists* (mailman2) mirrorlists (mirrormanager) releng* (bodhi1) sundries* (mirrormanager)
Have you looked at containerizing at all? That would allow you to keep the apps in RHEL6 containers, as was just announced: http://rhelblog.redhat.com/2014/10/14/run-red-hat-enterprise-linux-6-applica... While moving the hosts forward, thus taking advantage of a more modern kernel and userspace management tools.
On Thu, 16 Oct 2014 18:04:45 -0400 Colin Walters walters@verbum.org wrote:
On Fri, Oct 10, 2014, at 01:51 PM, Kevin Fenzi wrote:
impossible:·
These are ones where it's not really possible to move the current thing to 7, and we are waiting for the next major version.
bodhi* (bodhi1) collab* (mailman2) hosted-lists* (mailman2) mirrorlists (mirrormanager) releng* (bodhi1) sundries* (mirrormanager)
Have you looked at containerizing at all? That would allow you to keep the apps in RHEL6 containers, as was just announced: http://rhelblog.redhat.com/2014/10/14/run-red-hat-enterprise-linux-6-applica... While moving the hosts forward, thus taking advantage of a more modern kernel and userspace management tools.
No, but containers could well be very handy for a number of things for us down the road. Just will take someone investigating and figuring out how we can use them.
In the case of the above, we are actively replacing all those things with newer things, so we can move them when those are done...
Mirrormanager3, mailman3, bodhi2, etc.
kevin
What's holding up mirrormanager(v1) on rhel7? Curious more than anything; I haven't tried.
-- Matt Domsch Distinguished Engineer, Director Dell | Software Group
On 16 October 2014 18:45, Matt_Domsch@dell.com wrote:
What's holding up mirrormanager(v1) on rhel7? Curious more than anything; I haven't tried.
I believe the turbogears was the hold up, but that was moons ago and my brain is full.
-- Matt Domsch Distinguished Engineer, Director Dell | Software Group _______________________________________________ infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
On Oct 16, 2014 5:46 PM, Matt_Domsch@dell.com wrote:
What's holding up mirrormanager(v1) on rhel7? Curious more than
anything; I haven't tried.
Just a guess as I don't know what's been tested since I've stopped being as active:
It's likely that a subset of the older tg1 stack isn't being maintained in epel7. Maybe sqlobject and kid. Some people picked up the core tg1 packages that they needed but I believe they were using sqlalchemy (not sure which templating engine they were using.)
I don't know if there'd be code work needed to get those deps onto epel7; I suspect it's just lack of maintenance as I think all of those were present in fedora 20.
-Toshio
On Oct 16, 2014 3:57 PM, "Kevin Fenzi" kevin@scrye.com wrote:
On Thu, 16 Oct 2014 18:04:45 -0400 Colin Walters walters@verbum.org wrote:
On Fri, Oct 10, 2014, at 01:51 PM, Kevin Fenzi wrote:
impossible:·
These are ones where it's not really possible to move the current thing to 7, and we are waiting for the next major version.
bodhi* (bodhi1) collab* (mailman2) hosted-lists* (mailman2) mirrorlists (mirrormanager) releng* (bodhi1) sundries* (mirrormanager)
Have you looked at containerizing at all? That would allow you to keep the apps in RHEL6 containers, as was just announced:
http://rhelblog.redhat.com/2014/10/14/run-red-hat-enterprise-linux-6-applica...
While moving the hosts forward, thus taking advantage of a more modern kernel and userspace management tools.
No, but containers could well be very handy for a number of things for us down the road. Just will take someone investigating and figuring out how we can use them.
I've recently taken a look at socket as part of working at ansible. It should definitely be possible to do this (and even to use ansible playbooks to partially provision/configure the containers. However you would need to have someone updating the images periodically just like you presently need to update the virtual machines you maintain.
It would probably be best to have the whole sysadmin team become somewhat versed in docker usage (to the same extent as they're aware of virtual machines at least). There isn't a whole lot to learn for basic proficiency, though, so this wouldn't take too long. If you don't want to train everyone, having a docker czar and a couple helpers would be enough to actually do the work.
-Toshio
In the case of the above, we are actively replacing all those things with newer things, so we can move them when those are done...
Mirrormanager3, mailman3, bodhi2, etc.
kevin
infrastructure mailing list infrastructure@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/infrastructure
On Thu, Oct 16, 2014, at 10:08 PM, Toshio Kuratomi wrote:
I've recently taken a look at socket as part of working at ansible.
Socket?
It should definitely be possible to do this (and even to use ansible playbooks to partially provision/configure the containers. However you would need to have someone updating the images periodically just like you presently need to update the virtual machines you maintain.
Yes. There is no free lunch =) We need better tools in this area. If anyone's interested, I'm trying to centralize some RPM-based-distribution + Docker discussion on projectatomic.io, e.g.:
[1]https://lists.projectatomic.io/projectatomic-archives/atomic -devel/2014-October/msg00031.html
It would probably be best to have the whole sysadmin team become somewhat versed in docker usage (to the same extent as they're aware of virtual machines at least). There isn't a whole lot to learn for basic proficiency, though, so this wouldn't take too long. If you don't want to train everyone, having a docker czar and a couple helpers would be enough to actually do the work.
Yeah, the plus side is it is very easy to get started.
References
1. https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2014-Octo...
On Fri, Oct 10, 2014 at 11:51:29AM -0600, Kevin Fenzi wrote:
I took a look at what rhel6 instances we have left and wrote up a little status report:
[...]
not too hard:·
These are the ones where we need a playbook written or where they are already in ansible, but we need to reinstall them with 7 and make sure all the needed packages for that application are available there.
fas* (needs playbook
FAS2 is still TG1, so we will have the same problem here as we have for the other TG1 application. There is FAS3 in progress, so one option would be to wait for FAS3 to upgrade the FAS servers to RHEL7. This would also put a little more pressure on us to work on FAS3.
ns* (needs playbook) secondary01 (needs playbook) virthosts (some need outage) sign-vaults (needs being careful) backup03 (needs outage and being careful) blockerbugs* (needs playbook) (all these are in ansible, just need reinstall for rhel7) (all these have multiple instances, so no outage hopefully) badges-web* download-rdu* github2fedmsg* notifs-web* packages* summershum* tagger*
fedocal*
Done in stg and prod
elections* nuancier* pkgdb*
Done in stg, will be done in prod after freeze
Missing: darkserver, I'll see with Kushal if/when/how we can do it.
Pierre
infrastructure@lists.fedoraproject.org
-
Colin Walters -
Kevin Fenzi -
Matt Domsch -
Pierre-Yves Chibon -
Stephen John Smoogen -
Toshio Kuratomi