Deploying a HipChat Datacenter OVA

So I just downloaded the latest HipChat Datacenter OVA last week.  I deployed it to a vSphere environment, but I'm struggling to get it to work.  After getting a static IP set (putting the interfaces file in ~admin/config/etc does not do it as the readme.txt states), I browsed to the IP.  I was surprised to see it wanted an external PostgreSQL database.  So I got that setup and now I'm getting an error about being unable to create the schema.  I poked around some logs and see it complaining about not being able to connect to Redis on the localhost (appliance).  I've done some googling and it looks like I need to setup this Redis software on yet another host?  

To me, when I download an appliance, it should prompt for an IP and a password, then "just work".  Sure, maybe a setup wizard or something to configure other stuff -- but it should all be self-contained.  Otherwise, why would I bother with an appliance?  Am I missing something.  Ready to give up on it and stick with my simple Jabber server (that is self-contained).



1 answer

I suggest reading over the documentation. There is a LOT more involved in setting up HipChat Data Center than there was with HipChat Server.  It's not an appliance any more.

A quick summary of what you need to do:

  1. Set up a Postgres database (cluster if you expect high availability)
  2. Set up Redis (cluster if you expect high availability)
  3. Set up a load balancer (cluster if you expect high availability)
  4. Set up your application OVA nodes and connect them to the above components.
  5. Set up anti-affinity on your vSphere environment to ensure that an ESX server failure doesn't bring the cluster down.

If you need some help setting up a highly available HipChat environment, feel free to reach out. We have a proven design that we have implemented for other clients.

Suggest an answer

Log in or Join to answer
Community showcase
Maarten Cautreels
Published Oct 07, 2017 in Hipchat

Bringing Structure to your HipChat Instance

...have mention name FirstnameLastname. Fe.: @MaartenCautreels This certainly helps to know who is being mentioned in a conversation. Imagine your colleague sends the following message...

470 views 1 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot