Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,036
Community Members
 
Community Events
176
Community Groups

How can I automate Crowd installation and configuration for deployment on a Docker cluster.

I'm using the blacklabelops/crowd Docker image as a baseline and auto-generating the crowd.cfg.xml file in the ENTRYPOINT script for my image so it contains our server ID, license, and database settings.

I'm having trouble figuring out how to initialize the database though -- when Crowd starts up, it doesn't create the schema, instead generating errors in the DB logs because the requested tables don't exist.

Is there a way to specify all relevant parameters at startup so Crowd will initialize if settings don't exist and use existing settings if the database is found? Or do I have to run a bootstrap container and manually configure Crowd before I can launch my runtime containers for an HA solution?

1 answer

0 votes
Marcin Kempa Atlassian Team Jan 26, 2018

Hi @Gordon Shankman,

Indeed there is no headless setup for Crowd at the moment. However, the approach you've taken with generating crowd.cfg.xml, looks like a way to go.

In order to overcome the problem with empty database, I would suggest doing a backup and then reapplying it on a fresh DB before Crowd is started. It can be a DB dump from a previous startup as Crowd will automatically upgrade DB schema and data to a version you currently run.

You've mentioned HA solution you are building with docker containers. I guess it is more disaster recovery mode then active-active clustering?

Did you tried our Crowd Data Center for HA capabilities in Active - Active cluster mode?

 

Hope that helps,

Marcin Kempa

any update on this question?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events