Need to restrict how many people can join a meeting and handle notifications for the same.
— A ticket has been filed for above, can we give it a higher priority? Need to handle user notification if the BBB server is at or near capacity.
Meeting Capacity = 50/MAX_USERS per meeting restriction.
Capacity evaluation possible at create time and “Play” run time.
—- Assuming we don't expect to have substantial traffic in the next 1-3 months, do we add this logic with this release?

0) Research the mConf project. Possibility of using a network bus architecture to decouple meetings / users from servers.\\ 
1) Discuss Sharding vs mConf
2) Discuss restrictions
3) Discuss LB / DNS implementation.

Not much info yet.

1) Multiple BBB servers. 2) Users goto the first least used BBB server (and the meeting gets locked there).

 i)  least used: active lookup of total number of current users + buffer based on number of meetings.
ii)  Once enough use data is available: determine cost recoup methods. 

0) CM'ize BBB creation/
  i) Receipes to build a BBB server.
  ii) Integration w/ Capistrano.
  iii) Receipe to build image out from a run.
1) Rollout / Rollin receipes based off the image.
2) Monitors: traffic / users / meetings / bw.