Right now, every time a new team wants a new room in our Jangouts instance, they have to ping me and I have to manually create the room. That means:
- Adding some lines to the corresponding config file
- For the room to be available immediately, either restarting the service, either creating the room also through the REST interface.
I want to explore Salt to see how it can be used in order to provide a better way to create/destroy rooms, so every admin can easily do it. I have never used Salt, so I'm open to suggestions about the approach.
On the other hand, I would also like to come up with a more sustainable organization of the rooms. We started with one room per team because we didn't expected so many teams adopting Jangouts. Now we have more than 15 rooms, so maybe we should switch to other approach, like having a defined set of rooms (named with colors, cities, whatever) that everybody shares. Once again, I'm open to suggestion.
The SaltStack part is done. Now we have a Salt execution module that allows not only to create rooms (persistent and with immediate effect) but also to inspect the status of the Janus instance (for example, listing the connected users). Here is the repository and here the rpm packages.
- Putting pieces together: check! (Jangouts + Salt)
- Learning: check! (I have learned the Salt essentials and played with it... and I REALLY like it)
- Improving the world: check! (Now all admins can manage rooms from the Janus host or from the salt master)
- Collaboration: check! (Pablo rocks!)
Still pending: coming up with a more sustainable organization of the rooms. Still open to suggestions.
Looking for mad skills in:
jangouts salt saltstack
This project is part of:
Hack Week 14
This project is one of its kind!