Welcome and first task
Igor Minar
Thanks for joining.
Let me start by defining my objectives for this mailing list:
- gather people who run or develop for large confluence instances for
enterprises, government agencies, universities, etc
- share knowledge - this includes:
- discoveries of scalability issues and security issues
- development of plugins/patches or other solutions that make
confluence scale better
- discussion about jvm/confluence/os tuning
- collaborate on creating solutions that could are generally useful
for large instances
- join forces (and budgets?) when negotiating with atlassian and/or
atlassian partners
There are probably more things we could do together, so feel free to
add your idea.
I think that we should start by gathering all the JIRAs that make our
large instances suffer. Can all of you please go through your list of
unresolved JIRAs and post them to the list. I propose this format:
BUGs:
http://jira.atlassian.com/browse/CONF-12319 - Adding users to a large
group is slow with default (Hibernate) user management
...
RFEs:
http://jira.atlassian.com/browse/CONF-9335 - In cluster, allow
attachments to be stored on file system in network-shared directory
...
Please order the issues by *your* priority from the most important to
the less important and please limit the number of issue to only those
that are really important to you.
If you think that it would be better to post this information on a
wiki, then I created a wiki space for this mailing list at
wikis.sun.com [1] or we can use the "page" functionality of the google
groups.
I won't be online much next week, so feel free to take several days to
create the list of issues.
PS: Please spread the word about this mailing list among relevant
Confluence users/partners/developers.
cheers,
Igor
Mark Nye (UIUC)
Here's our list. There may be more to come.
1) LDAP performance is a serious issue. We don't want to go down the
path of writing importer scripts to move our LDAP users and groups in
the Confluence user database.
http://jira.atlassian.com/browse/CONF-11926
http://jira.atlassian.com/browse/CONF-8925
http://jira.atlassian.com/browse/CONF-10557
2) Nested LDAP groups should be built into Confluence. The lack of
Atlassian response to comments on this ticket is unfortunate.
http://jira.atlassian.com/browse/USER-101
3) We need a tool that allows the Confluence admin to do site-wide
checks for plugin/macro usage. Right now we're relatively blind to
who's using what and where, which makes it difficult to plan plugin
upgrades, retirements, etc.
http://jira.atlassian.com/browse/CONF-10572
4) Related to this, how about an Atlassian-certified plugin library?
(Atlassian may be missing out on a potential income stream here.) It
would be very useful to have access to a list of plugins that have
been tested and are known to perform well on large-scale
installations. I'm not aware of a related jira ticket.
5) We need a clean, simple way to change usernames.
http://jira.atlassian.com/browse/CONF-4063
I understand why Atlassian uses the voting system for addressing
issues, but I'm not sure that they're taking install size into
account. When we vote, we're voting for 60,000 users, but I'm not sure
that our input is weighted any differently than a vote from a 25 user
Confluence admin. Maybe the problem is Atlassian's pricing model --
Confluence is incredibly cheap to license compared to all of the other
major services we run. I think I'm speaking safely for my management
when I say that we'd be happy to pay more for Confluence, if it means
that scalability issues will get some attention.
I should note that overall, we've been relatively happy with Atlassian
support. They've been very responsive in helping us to troubleshoot
service outages and other problems. They simply need to put more
emphasis on enterprise-scale feature requests.