![]() Next, I just clicked on “Generate” and what you see above is the result. The parameters (2048 bit RSA key) can be left in default. I added the VM name as a key comment and set a passphrase. I used PuTTYgen for creating my SSH key, since it’s simple and free. SSH key PuTTYgen’s interface is really selfexplanatory Azure creates the corresponding VNet and IP for me. Additional disks are not necessary since I’m not planning on persisting any data. I’ve dialed the OS disk down to a Standard SSD to save a bit of money. I’ll be locking that further down later on. When creating a Linux VM, port 22 is opened by default. For now, I’ve opened the Port 22 for SSH so I can connect to the VM and configure it. I’ll be describing the creation of the SSH key briefly in the “SSH key” section below. I’ve decided against a Spot instance, that’s something I want to test another time (watch this space □). The Ubuntu Server 18.04 LTS image is the one I want and I selected “Standard B2ms” as the size. The VM name is the same as the name of the resource group, I don’t need redundancy for my test system. I created the VM inside the resource group, so it’s automatically selected. I used “jitsimeet” for the VM name as well. ![]() Ubuntu Server is in spot 2 of the popular offers. The marketplace has a lot of fancy stuff. When clicking adding a new resource, Ubuntu Server is right up there in the recommendation. I’ve decided to deploy everything in West Europe. There’s not much to creating a resource group… I created a new resource group called “jitsimeet” for this. The little experience with Linux I was able to make so far was with Ubuntu – so obviously I went with that (Ubuntu Server 18.04 LTS to be precise). So? Ehrm? I just decided to spin up a B2ms (2 vcpus, 8 GiB memory) for now and see how it responds to load… OS I’ve been digging through forums to get to basically the following information: Turns out, it’s virtually impossible to get proper information on the hardware requirements for Jitsi Meet. I’d be very happy about a comment, if you spot a mistake or see room for improvement somewhere! Infrastructure Requirements I’m an absolute Linux-noob, so please bear with me if I have strange stuff in here – I just followed the documentation. So I set out to install Jitsi Meet on an Azure VMĭisclaimer: Jitsi Meet runs on Linux. * But wait! The end-to-end encryption only works in 1:1 meetings! Multiparty meetings use Jitsi Videobridge instead of the P2P mode and they are decrypted at the server!Īccording to Jitsi the decrypted data is never persisted to storage and handled exclusively in memory (except meeting recordings that are saved at the Jitsi server until they have been delivered to your storage), but I wanted to see what I could do on my own instance. ![]() Of course you can set an additional password for joining the meeting. You can share the meeting ID with people and when they enter it, they join your meeting. Jitsi offers a free Video Conferencing Service at – just enter any meeting ID (or use the auto-generated one) and click start. What’s big about Jitsi Meet is the fact, that it’s completely open source ( GitHub Repo) and really focused on security and privacy. Jitsi’s Service “Jitsi Meet” – like Zoom – focusses on meetings without collaboration or document sharing and on video calls above text based chat. I heard of quite a few people leaving Zoom over those concerns and moving to Jitsi instead. If you haven’t already, check out “Security Now” with Steve Gibson, in particular these two episodes are relevant to this: ![]() Zoom has been poked at quite a lot recently for security concerns but I feel like they’re handling themselves really well in this extreme situation. ![]() I fully agree with Ben and Scott: All those services have things they do better than others and searching for the holy grail of conferencing might be a waste of time. Teams tends to have quite the steep learning curve…Īnd don’t get me started on Chat in Teams vs. It’s dead simple to log into a meeting and the interface is super straight forward. However, for a quick call without any document collaboration or with people with limited technical expertise, Zoom might be the better fit. It’s wonderful for collaboration and the enterprise capabilities (especially around security and compliance) are top notch. In my day to day work, I use Microsoft Teams constantly. It doesn’t make sense to just pit them against each other to find the “best solution” without clearly defining the problem. When listening to Ben Stegink and Scott Hoag on episode 173 of the Microsoft Cloud IT Pro Podcast, I found them making a compelling point:Īll these solutions (Teams, Zoom, etc.) have a different focus for different use cases. Lately everybody has been discussing the advantages and disadvantages of different video-conferencing-solutions. ![]()
0 Comments
Leave a Reply. |