Just to clarify, @nerdsville is asking if the infra team would like to migrate the Fedora planet from venus to pluto.

I do note that pluto in its simple form does not have all the features that venus has (like generating FOAF blog roll exports and the combined RSS/Atom feed for the planet), but it can be combined with jekyll to make this possible (which is how OpenSuse seems to do it):

https://github.com/feedreader/planet.rb

I don't know how the sub-planets work with pluto either (but then I don't know how they work with venus either :D). If they're all just separate planets, that should be doable with pluto too.

The Neuro SIG's simple planets can be seen here:

• https://neuroblog.fedoraproject.org/planet-neuroscientists/
• https://neuroblog.fedoraproject.org/planet-neuroscience/

sources:

• https://github.com/neurofedora/planet-neuroscientists
• https://github.com/neurofedora/planet-neuroscience

So, if I recall right, pluto is a bunch of rubygems? and it's not packaged in Fedora?

Yeh, it's gems and it isn't in Fedora at the moment.

For our bits, we gem install it as part of the GH workflow that periodically builds the planet:

https://github.com/neurofedora/planet-neuroscience/blob/master/update.sh#L26

Before embarking on this, what does updating to a new piece of software here give us?

Pretty sure our theme will have to be ported over, as well as implement the support for the subplanets we already have. Also, our planet setup allows users to add a configuration file on their fedora people to add their blog to the planet. This will need to be re-implemented for this new system

IMHO, unless there is a pressing security concern or severe bug with the current venus based system, that we cant rectify, we should keep the fedora planet as is.

Yeah, porting of the templates would need to be done as well (there is a well-documented migration path, and it should be fairly easy to port).

However, I do agree with "why fix what isn't broken", and I don't believe there is a severe bug (security related, or otherwise). The motivation to migrate for NeuroFedora was simply because Venus isn't supported/is deprecated.

As an aside:

Personally, I like how OpenSUSE has people fork and make a PR (which gets approved) to add a feed into the planets (see: https://github.com/openSUSE/planet-o-o/blob/master/README.md), but that also would mean a pretty significant shift in the way things are currently done.

Before embarking on this, what does updating to a new piece of software here give us?

A working/supported planet software?
Venus is really not in a good shape:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/FN53VHUTYYH6GBDNCYKTBRTQRHH55SKL/

I wonder if we could use openshift to run Pluto, which may help with the
packaging rubygems question.

Yeah, porting of the templates would need to be done as well (there is a well-documented migration path, and it should be fairly easy to port).

Here's the template migration doc:

https://feedreader.github.io/#planet-planet--pluto---template-cheatsheet

Also, our planet setup allows users to add a configuration file on their fedora people to add their blog to the planet. This will need to be re-implemented for this new system

The current system works, but it isn't written in stone and can always be modified to something else (better?) if it can't be reimplemented. Given how normal the PR system is in Fedora now, I don't think folks would find it any harder than setting up fedorapeople etc.

Out of curiosity, how is it currently implemented though? Were changes made to venus or do we just cat all the planet files on fedorapeople: cat /home/fedora/*/.planet >> allplanets.ini types?

I wonder if we could use openshift to run Pluto, which may help with the
packaging rubygems question.

We could look into packaging pluto too if that'll help. It seems to be quite a simple gem, so it shouldn't be too much work. (I seem to remember there's a gem2spec tool that helps get an initial spec). I see jekyll is in the repos too:

https://packages.fedoraproject.org/pkgs/rubygem-jekyll/rubygem-jekyll/

How are the sub-planets implemented? Did we modify venus?

Out of curiosity, how is it currently implemented though? Were changes made to pluto or do we just cat all the planet files on fedorapeople: cat /home/fedora/*/.planet >> allplanets.ini types?

IIRC it's the latter

IIRC it's the latter

OK, so that'll remain the same then.

@nerdsville : do you want to start looking at migrating the planet template, and we can test it out with some example sources and see how things look? Then we can look into the jekyll integration bit?

Additionally note that fedoraplanet runs on people02 which is a rhel7 instance currently.

I opened another discussion on this on the infrastructure list. :) Feedback welcome there.

So, @phsmoura is going to look into this from our side.

Would @ankursinha / @nerdsville be available to meet with him sometime and talk about the setup you used, etc?

I'm happy to attend as well if you like, or just let you all hash things out.

@ankursinha , @nerdsville Is there someone working on this? Do we have pluto already running somewhere? Id like to help if its okay :)

@phsmoura - thanks for reaching out :) I'm happy to show you what we have done and help point you in the right direction. Would you be able to join the fedora Neuro IRC? We can chat there

Hi @nerdsville , are you still interested to help with the migration from Venus to Pluto?

Basically, fedora planet didn't have a repo. So I had to gather info from the server to see how it was working.
I created a repo for it (https://github.com/fedora-infra/planet) and started changing the templates in dev branch. Fedora planet has a lot of "planets" and each one has its own template. So, help is welcome :)
Please, let me know if you're still interested. I'm on fedora-neuro on IRC if you prefer, but there could be delays on replies because of the timezone

Update: Created an repo in github and migrated venus to pluto. Now working to deploy it on OCP

@phsmoura How it goes?

[backlog refinement]
@phsmoura What is the situation around the upgrade?

[backlog refinement]
From what I see there is a progress in staging deployment
@phsmoura Do you have more info?

I know I started this a couple years ago and dropped the ball on this - is there some way I can help @phsmoura @zlopez

@nerdsville There is a PR open from @phsmoura, you can look at it

@zlopez - thanks - I've left some comments

So, thanks to @phsmoura planet is now running in prod openshift:

https://planet.apps.ocp.stg.fedoraproject.org/

So, here's what I think are next steps:

• I think we need to tell infrastructure list and discussion about it and ask people to check and see if they see problems, make sure and add their blogs to their accounts and confirm they show up there, etc.

• We also may want to write up a SOP on it. How to update it, how to remove blog posts if we need to, etc.

• If that all looks good, we should mail devel-announce and perhaps do a community blog post telling people that we are moving planets and that they should make sure to have their blog listed in their account so it's picked up by the new system. We should at this time set a sunset date for the old planet. A few weeks at least for people to make sure to have their blog updated in their account.

• We need to take the current wiki page about planet and move it to docs somewhere and redirect the old wiki page. This should describe the new way to enroll your blog (have it in your account and be a contibutor).

• On the sunset date we change dns / web config to point planet.fedoraproject.org and fedoraplanet.org to the new planet.

Sound reasonable? @phsmoura let me know if you want me to do any of those things, or if you just would like to do them. :)

@kevin : sounds good, I can do those things np