similar to: wiki.centos.org migration plan

Due to a software upgrade and hardware migration, we'll have to move the existing CentOS Wiki instance (aka https://wiki.centos.org) to a new node. Migration is scheduled for """"Monday December 9th, 9:00 am UTC time"""". You can convert to local time with $(date -d '2019-12-9 9:00 UTC') The expected "downtime" is estimated to ~60

On 12/12/17 17:25, Akemi Yagi wrote: > On Mon, Dec 11, 2017 at 1:00 AM, Fabian Arrotin <arrfab at centos.org > <mailto:arrfab at centos.org>> wrote: > > it's all in the title : what's next for wiki.centos.org > <http://wiki.centos.org> ? > > As a reminder, current wiki.centos.org <http://wiki.centos.org> > instance is

On 22/02/18 22:13, John R. Dennison wrote: > On Thu, Feb 22, 2018 at 01:11:20PM +0000, Karanbir Singh wrote: >> On 21/02/18 22:30, Fabian Arrotin wrote: >>> That's a good question, as we'll also have to migration for moinmoin if >>> we can't find a support path to migrate to supported version anyway. >>> So first question (already asked on the list)

Hello Fabien, First, thank you for even trying for what seems to be an impossible task :( Quick points : - if it was decided not to continue, what would happen to the current wiki ? Dismantled or would it remain as read-only for documentation purpose ? - What about Sphinx <http://www.sphinx-doc.org/en/stable/> ? seems to be frequentely used nowadays - As you mentioned, a solution of the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/10/15 18:49, Ilyas Arinov wrote: > Sorry about second post about that, but we need language sensitive > menu links on wiki.centos.org <http://wiki.centos.org>. For > example, if users pick any language and wants to see HowTo section, > they need open "Learn" section and find there "HowTo" section, or >

On Mon, Dec 11, 2017 at 1:00 AM, Fabian Arrotin <arrfab at centos.org> wrote: > it's all in the title : what's next for wiki.centos.org ? > > As a reminder, current wiki.centos.org instance is powered by moinmoin > (https://moinmo.in/) but quite an old version (moin-1.5.8-3.el6.noarch) > > Recently I had a quick look at trying to update/upgrade that version to >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, As I received positive feedback from testers (thank you all !) on the wikitesting.centos.org moin instance, I think we can say that we'll migrate the real wiki.centos.org very soon ... I'm actually moving some services around (pdns/msync roles) to free a machine that will be able to host the moin/wiki role. Depending on the available

On 21/02/18 22:58, Karanbir Singh wrote: > Hi > > the CentOS Cloud images and other things are now built from end to end > automated pipelines, but the wiki content corresponding to them isnt. Is > there something that can be used to do this automation ? > > I have done some stuff many many years ago, via directly mangling > content on the wiki objects, but that might not

Hi nice people interested in CentOS Docs and wiki ! There were already threads about migrating the wiki to something else (mediawiki, $other), or staying with moinmoin (what we now have in place). This mail isn't about that thread (but feel free to start a new one about that possible migration or not), but about just migrating the current moinmoin instance from the current machine to a new

it's all in the title : what's next for wiki.centos.org ? As a reminder, current wiki.centos.org instance is powered by moinmoin (https://moinmo.in/) but quite an old version (moin-1.5.8-3.el6.noarch) Recently I had a quick look at trying to update/upgrade that version to something newer/supported, but it's a nightmare : the data conversion just kill the target server (oom) and no

On Thu, Feb 22, 2018 at 01:11:20PM +0000, Karanbir Singh wrote: > On 21/02/18 22:30, Fabian Arrotin wrote: > > That's a good question, as we'll also have to migration for moinmoin if > > we can't find a support path to migrate to supported version anyway. > > So first question (already asked on the list) : is there a way to get in > > touch with moin people

As pre-announced a long time ago (see https://lists.centos.org/pipermail/centos-devel/2018-October/016997.html) , we'll migrate git.centos.org to a new host/platform (pagure/repospanner) The current migration is planned for : April 8th (more details later about the exact hour, as we need to have acknowledgement from all involved people). Instead of writing a long email, we instead decided to

On 21/02/18 22:30, Fabian Arrotin wrote: > That's a good question, as we'll also have to migration for moinmoin if > we can't find a support path to migrate to supported version anyway. > So first question (already asked on the list) : is there a way to get in > touch with moin people willing to help/assist us ? (as their upgrade > tool wasn't working to test

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd like to start making formal submissions to the wiki. I'm back-filling this request as Jim Perrin already added me to the wiki edit group. I'm relearning how Moin Moin access works (it's been a while but Fedora used to use Moin) and I've been using the MediaWiki style of edit/contributions so I'll need to re-adjust to how

On 11/04/16 21:11, Akemi Yagi wrote: > On Mon, Apr 11, 2016 at 10:37 AM, Karsten Wade <kwade at redhat.com> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 04/11/2016 09:18 AM, Jim Perrin wrote: >>> What are the thoughts or concerns about this sort of workflow >>> change? >> >> Any chance Moin Moin can store wiki

Looking at http://www.fontconfig.org/wiki/TitleIndex I see it's around 99.9% pure spam. Other than the front page, virtually everything else is the moin-moin boilerplate or the hundreds of pages of spam. Even the Recent Changes & Find Page links have been overwritten by spammers hundreds of times, with the spammers fighting each other to crap on it most recently. (I restored them both

Due to a scheduled pagure upgrade, we'll have to move the existing Pagure instance (aka https://git.centos.org) to a new node. Migration is scheduled for """"Monday June 13rd, 7:00 am UTC time"""". You can convert to local time with $(date -d '2022-06-13 07:00 UTC') The expected "downtime" is estimated to ~60 minutes , time needed to

Dear users, I just started my first Gluster test volume using 3 servers (each server contains 12 hdd). I would like to create a "distributed disperse volume? but I?m a little bit confused about the right configuration schema that I should use. Should I use JBOD disks? How many bricks to be defined? Ideal redundancy value? Ideal disperse-data count value? 6x(4+2) or 3x(8+4) volume

On 03/09/2020 20:51, Leon Fauster via CentOS wrote: > > What would you recommend: ansible is in EPEL8 and ConfigSIG. > For the latter I do not see any sources in git.centos.org. > Where they come from? > > I wonder with which repository I should use (long term)? > > dnf not checking gpg signature sounds scary: > >

Hi Nithya, thank you very much for your support and sorry for the late. Below you can find the output of ?gluster volume info tier2? command and the gluster software stack version: gluster volume info Volume Name: tier2 Type: Distributed-Disperse Volume ID: a28d88c5-3295-4e35-98d4-210b3af9358c Status: Started Snapshot Count: 0 Number of Bricks: 6 x (4 + 2) = 36 Transport-type: tcp Bricks: