#603 Set up a Public Openfire server
Closed: Fixed None Opened 15 years ago by steved.

For an upcoming FESCo/Board meeting I would like
to set up Openfire server to allow participants of
the meeting to used a virtual WhiteBoard.

I've done some local testing of both the whiteboard-sharing
Jabber client Coccinella and the Openfire Jabber server.
The software seems to work fairly well so I would like to
make the Jabber server publicly accessible.

The three packages, above and by a "normal" F9 server configuration,
that were needed were: java-1.6.0-openjdk, mysql-5.0.51a-1 and
openfire-3.5.1-1.i386. Openfire was downloaded from:
http://www.igniterealtime.org/downloads)

Note the meeting is schedule for: June 9th, at 3:30pm


If this is something you want setup you'll need to put a little proposal together and get a member of the infrastructure team to sponsor it. The requester (you) would be the project leader in charge of finding sponsorship, making sure the work is getting done, etc.

Replying to [comment:1 mmcgrath]:

If this is something you want setup you'll need to put a little >
proposal together
What is missing from the Description that you need in the proposal?

and get a member of the infrastructure team to sponsor it.
The search is on!! :)

The requester (you) would be the project leader in charge of
finding sponsorship, making sure the work is getting done,
Not a problem... but buck can stop here...

Matt Domsch said he would be willing to sponsor me...

A few problems:

1) Coccinella is not in Fedora
2) Openfire is not in Fedora
3) Less than a week to set up a Jabber/XMPP server isn't a good thing.

Also, from what I can see, Openfire isn't required for Coccinella, any Jabber/XMPP server should do. Not that I have anything against Openfire but we should consider some of the other Jabber/XMPP servers as well.

Apparently the software is somewhat sensitive to the Jabber server. Let's let Steve set this up and see how it goes. I agree it's not ready for production use, but the idea is sound, the software is open source (albeit not in Fedora at the moment), and we'll see how beneficial it is.

SteveD: publictest10 is running RHEL 5.1 - good enough?

Replying to [comment:4 jcollie]:

A few problems:

1) Coccinella is not in Fedora
I'm only bring up the server..

2) Openfire is not in Fedora
Its open source and has the virtual Whiteboard support.

3) Less than a week to set up a Jabber/XMPP server isn't a good thing.
That just make is more fun... Note, it took me less than a day
to get the server up and running... so it should not be a big deal

Also, from what I can see, Openfire isn't required for Coccinella, any Jabber/XMPP server should do. Not that I have anything against Openfire but we should consider some of the other Jabber/XMPP servers as well.

Openfire was suggested because it was open source and well supported.

Matt,

I did all my testing in a fully updated Fedora 9 server...
Would one of those be possible?

SteveD: not trivially. Please try with RHEL 5.1, and if it's really unworkable, I'll have to learn how to set up a publictest instance (I've done app servers in .de exactly once).

Matt,

$ssh publictest10.fedorahosted.org
Permission denied (publickey).
(From a machine with usual know public keys)

Who do I again access? Also is RHTS set up so I
can yum install any needed packages?

Steve, you need to apply for the sysadmin-test group. Go here:

https://admin.fedoraproject.org/accounts/group/view/sysadmin-test

and click "Apply".

Replying to [comment:12 jcollie]:

Steve, you need to apply for the sysadmin-test group. Go here:

https://admin.fedoraproject.org/accounts/group/view/sysadmin-test

and click "Apply".
Done!

I sponsored SteveD into the sysadmin-test group (after Toshio upgraded me to sponsor status, seem I didn't have that before I volunteered to sponsor people!) so after an hour or two when the logins percolate, Steve, you should be able to log into publictest10.fedoraproject.org. From there you should be able to sudo yum install stuff from RHEL or EPEL. You'll need an additional directory to drop your stuff into, so just do it in your home dir for now, and poke me when your ready to move.

I'm going to need a few holes opened in publictest10's firewall
to configure the server and then for normal usage.

The server is configured through an http interface that
listens on port 9090 (i.e. http://127.0.0.1:9090). Now from
local testing I know the server configuration will accept
connections from remote hosts (i.e. http://192.168.62.20:9090).

I tried setting up an ssh tunnel with the following command:
ssh steved@publictest10.fedoraproject.org \
-L 9091:publictest10.fedoraproject.org:9090

But it failed because publictest10 was refusing the
connection. The message was:
channel 3: open failed: connect failed: Connection refused

So either I need the 9090 port opened up or do the magic to
permit ssh tunnels.

Secondly, I'll need ports 5222 and 5269 opened for the server
and client traffic.

I added holes for 5222 and 5269 on publictest10. I added these only on publictest10, and I believe the iptables config on that machine is simply the static file in /etc/sysconfig/iptables, and isn't puppetized. If the config changes in the next couple hours behind your back, I'll have to figure out how to make that change in puppet.

As for 9090, try:

ssh -L 9091:127.0.0.1:9090 steved@publictest10.fedoraproject.org

which will do a localhost connection on the remote side.

No go with the:

ssh -L 9091:127.0.0.1:9090 steved@publictest10.fedoraproject.org

I'm still getting the

channel 3: open failed: connect failed: Connection refused

error message in the publictest10 window...

ITs Alive! downloading the coccinella binary from
http://thecoccinella.org/download I am able to
register a steved account and create a chat room
with an attached whiteboard...

I wonder if we create a jabber.fedoraproject.org alias
which could point to publictest10.fedoraproject.org...

jabber.fp.o alias exists. The jabber server worked for it's purpose yesterday. Thanks to SteveD and everyone who helped.

Going forward, we'll need to decide if we want to keep this implementation of a Jabber server or choose another (Coccinella is a bit buggy, I wouldn't want to decide this based on Coccinella's requirements alone). If a shared whiteboard service using Jabber is deemed useful, then one needs to be integrated with FAS and put into puppet and onto a production app server.

Replying to [comment:19 mdomsch]:

jabber.fp.o alias exists. The jabber server worked for it's purpose yesterday. Thanks to SteveD and everyone who helped.

Going forward, we'll need to decide if we want to keep this
implementation of a Jabber server or choose another (Coccinella
is a bit buggy, I wouldn't want to decide this based on
Coccinella's requirements alone).

I would have no problem continuing to support this or
another implementation of a Jabber server as long as
its deemed useful and its used.

If a shared whiteboard service using Jabber is deemed useful,
then one needs to be integrated with FAS and put into puppet and
onto a production app server.
Does "integrated with FAS" means creating Fedora approved rpms?
Also I'm not familiar with puppet so I would need some guidance
there as well

Replying to [comment:20 steved]:

Does "integrated with FAS" means creating Fedora approved rpms?

Fedora approved RPMs will be necessary, but "integrated with FAS" means that people can use the same username/password that they use with other Fedora services.

Tom Callaway appears to be working on Coccinella packages:

http://spot.livejournal.com/295668.html

Is there any updates on this?

Hi, I'm going to "close first, ask questions later" on this ticket since it hasn't been updated in over 2 years - if I'm mistaken, please feel free to reopen :-)

Login to comment on this ticket.

Metadata