SA NREN Mconf Systems Hardware and Support Infrastructure Presented by Patrick Holahan TENET Senior...

download SA NREN Mconf Systems Hardware and Support Infrastructure Presented by Patrick Holahan TENET Senior Network Engineer patrickh@tenet.ac.za.

If you can't read please download the document

Transcript of SA NREN Mconf Systems Hardware and Support Infrastructure Presented by Patrick Holahan TENET Senior...

  • Slide 1
  • SA NREN Mconf Systems Hardware and Support Infrastructure Presented by Patrick Holahan TENET Senior Network Engineer [email protected]
  • Slide 2
  • Covering? Hardware and remote management Software Monitoring Support procedures Notifications / Maintenance Access to the systems Mconfsa blog Summary Questions and Answers 2
  • Slide 3
  • Hardware Physical Server 1x Dell R520 server 2x Intel Xeon E5-2440 CPUs running at 1.9Ghz 4x 1TB HDDs RAID10 64Gb RAM Dell iDRAC (integrated Dell Remote Access Control) Redundancy? None as of yet Plans for a 2 nd machine in JNB A VMware system, easy to backup/replicate 3
  • Slide 4
  • 4
  • Slide 5
  • 5
  • Slide 6
  • 6
  • Slide 7
  • 7
  • Slide 8
  • 8
  • Slide 9
  • 9
  • Slide 10
  • 10
  • Slide 11
  • 11
  • Slide 12
  • 12
  • Slide 13
  • 13
  • Slide 14
  • 14
  • Slide 15
  • 15
  • Slide 16
  • Software Base machine ESXi 6.0 VMwares hypervisor engine VMware ESXi (formerly ESX) is an enterprise-class, type-1 hypervisor developed by VMware for deploying and serving virtual computers. As a type- 1 hypervisor, ESXi is not a software application that one installs in an operating system; instead, it includes and integrates vital OS components, such as a kernel. A hypervisor or virtual machine monitor (VMM) is a piece of computer software, firmware or hardware that creates and runs virtual machines. A computer on which a hypervisor is running one or more virtual machines is defined as a host machine. Each virtual machine is called a guest machine. 16
  • Slide 17
  • VMware Machines 6x Ubuntu 14.04.2 machines 1x mconf web server https://mconf.sanren.ac.za https://mconf.sanren.ac.za 3x mconf live servers mconf-live-01.sanren.ac.za mconf-live-02.sanren.ac.za mconf-live.sanren.ac.za (Hosted at CSIR/SANReN) 1x mconf recording server mconf-rec-01.sanren.ac.za 1x SAML idP server idp-01.tenet.ac.za No defined architecture (part of the SA NREN contribution to mconf is updating this) 17
  • Slide 18
  • 18
  • Slide 19
  • 19
  • Slide 20
  • 20
  • Slide 21
  • 21
  • Slide 22
  • 22
  • Slide 23
  • 23
  • Slide 24
  • 24
  • Slide 25
  • Mconf network architecture 25
  • Slide 26
  • Mconf web server Ubuntu latest stable (14.04.2) The web application that provides access to Mconf Allows users to register locally or via FID intergration Ruby (via Ruby Version Manager) Phusion Passenger (Ruby app server) Apache (can use nginx the live servers do) MySQL database SSL certificate 26
  • Slide 27
  • 27
  • Slide 28
  • 28
  • Slide 29
  • 29
  • Slide 30
  • 30
  • Slide 31
  • 31
  • Slide 32
  • 32
  • Slide 33
  • 33
  • Slide 34
  • Mconf live servers Ubuntu latest stable (14.04.2) 3x Mconf live servers 2 hosted at TENET mconf-live-01.sanren.ac.za mconf-live-02.sanren.ac.za 1 hosted at SANReN mconf-live.sanren.ac.za Based on BigBlueButton Open source web conferencing software Completely scalable, continually adding new live servers Accommodates usage peaks Geographically assigning the closest server Run on nginx Use ruby on rails JSON & Chef recipes for management and deployment Managed by mconf technologia 34
  • Slide 35
  • Mconf recording server Ubuntu latest stable (14.04.2) 1x mconf recording server at present Recordings are processed once a meeting completes Pauses / stopping recording Still one file Pushed after processing to the recording server Available for download via the meeting space JSON & Chef recipes for management and deployment Managed by mconf technologia From a software/setup perspective Managed by TENET From a space/utilisation perspective/policy perspective (needs to be decided upon) 35
  • Slide 36
  • Monitoring IRIS snmpd Process monitoring Mconf http://lb2.mconf.org http://lb2.mconf.org Dashboard See images 36
  • Slide 37
  • IRIS 37
  • Slide 38
  • 38
  • Slide 39
  • 39
  • Slide 40
  • 40
  • Slide 41
  • Mconf Load Balancer Generic Stats 41
  • Slide 42
  • 42
  • Slide 43
  • 43
  • Slide 44
  • 44
  • Slide 45
  • 45
  • Slide 46
  • 46
  • Slide 47
  • 47
  • Slide 48
  • 48
  • Slide 49
  • 49
  • Slide 50
  • Mconf Load Balancer Admin Section 50
  • Slide 51
  • 51
  • Slide 52
  • 52
  • Slide 53
  • 53
  • Slide 54
  • 54
  • Slide 55
  • 55
  • Slide 56
  • 56
  • Slide 57
  • 57
  • Slide 58
  • 58
  • Slide 59
  • 59
  • Slide 60
  • 60
  • Slide 61
  • 61
  • Slide 62
  • 62
  • Slide 63
  • 63
  • Slide 64
  • 64
  • Slide 65
  • 65
  • Slide 66
  • 66
  • Slide 67
  • Support Procedures Ideal vs real world Ideally, we want a tiered structure Campus user reports to local IT department Local IT department logs a ticket with TENET TENET logs a ticket with Mconf Real world At present, this structure is not in place This launch is, to some, the first youre hearing of Mconf Unknown skillsets at the campus regarding Mconf Some systems in place, not finalised in terms of configuration Train the trainer sessions? 67
  • Slide 68
  • Support Procedures Current support options Ticket logging Service Operations Centre [email protected] [email protected] Telephonic Helpdesk 24x7 call centre 021 763 7147 Who do tickets get assigned to? TENET Engineering team Specifically Patrick and Kasandra for now Escalation? TENET to escalate to Mconf Technologia via email & Skype 68
  • Slide 69
  • Pro-active Support & Notifications Email alerts - Mailman mailing list IRIS Graphing and alerts Mconfsa blog 69
  • Slide 70
  • Pro-active Support & Notifications Email alerts - Mailman mailing list alerts Maintenance or planned work/outages Specific to Mconf Not separate notifications from ren-news http://lists.tenet.ac.za/mailman/listinfo/ren-newshttp://lists.tenet.ac.za/mailman/listinfo/ren-news Subscribe - http://lists.tenet.ac.za/mailman/listinfo/mconfhttp://lists.tenet.ac.za/mailman/listinfo/mconf List is moderated and requires both confirmation and approval To be manually populated by TENET for the initial group FID users will need to subscribe manually as theyre not in the Mconf user database 70
  • Slide 71
  • 71
  • Slide 72
  • 72
  • Slide 73
  • 73
  • Slide 74
  • 74
  • Slide 75
  • Pro-active Support & Notifications Graphing & Alerts IRIS The IRIS system generates alerts for all managed servers Emails to both IRIS and TENET when an event occurs Notifications to IRIS dashboard Graphs that are pro-actively monitored 75
  • Slide 76
  • 76
  • Slide 77
  • 77
  • Slide 78
  • 78
  • Slide 79
  • 79
  • Slide 80
  • 80
  • Slide 81
  • 81
  • Slide 82
  • Mconfsa Blog The Mconfsa Blog http://mconfsa.wordpress.com http://mconfsa.wordpress.com Articles indicating status of the project, events, notifications Help guides for the use of the system Still being expanded Please feel free to add your input/suggestions 82
  • Slide 83
  • 83
  • Slide 84
  • 84
  • Slide 85
  • 85
  • Slide 86
  • Access to the systems? Registration on mconf web Requires a browser Firefox preferred (chrome not preferred) Requires a camera/microphone, unless you wish to just listen, like to a lecture/presentation Open registration for now Later, only available to FID members via SAFIRE (2016) Log a ticket for access [email protected] or the 24x7 helpdesk 021 763 [email protected] 86
  • Slide 87
  • Review Hardware & Remote access Software Base machine and virtual machines Types of Mconf servers - web, live, and recording Monitoring, graphing, and Pro-active alerting MconfSA Blog How to access the systems Call/Ticket logging procedures 87
  • Slide 88
  • Where to from here? Continue to enhance and establish the tiered support infrastructure Enhance the skillsets on campus and within TENET/SANReN Continue to build on the platform another VM in JNB for redundancy customising the design/colours to suit our branding See what the community has to offer Development skills, feature requests, etc 88
  • Slide 89
  • In summary Currently 1 physical server, multiple VMs Still integrating the monitoring, alerting, and email notifications Need people to start using it to stress test and feedback Utilising a world class OSS web conferencing platform (based on BBB) Constantly being developed and enhanced by Mconf Technologia Feeding their enhancements back into BBB The SA NREN aim is to supply complementary systems that work together to enhance learning and collaboration for all our member institutions in a reliable and continously improving way. 89
  • Slide 90
  • Questions? 90
  • Slide 91
  • References Mconf network https://github.com/mconf/wiki/wiki/Mconf-Network https://github.com/mconf/wiki/wiki/Mconf-Network Mconf web https://github.com/mconf/mconf-web/wiki https://github.com/mconf/mconf-web/wiki Mconf live https://github.com/mconf/wiki/wiki/Mconf-Live & https://github.com/mconf/wiki/wiki/Mconf-Live https://github.com/mconf/wiki/wiki/Mconf-Network#requirements-for-the-mconf-live-server https://github.com/mconf/wiki/wiki/Mconf-Network#requirements-for-the-mconf-live-server Mconf blog https://mconfsa.wordpress.comhttps://mconfsa.wordpress.com ren-news & mconf mailinst lists http://lists.tenet.ac.za/mailman/listinfo/ http://lists.tenet.ac.za/mailman/listinfo/ General info about TENET and SANReN http://www.tenet.ac.za http://www.tenet.ac.za http://www.sanren.ac.za http://www.sanren.ac.za Graphing & monitoring page IRIS http://graphs.tenet.ac.za http://graphs.tenet.ac.za 91
  • Slide 92
  • 92 Contact Details. Service Operations Centre 24x7 email logging [email protected]. Service Desk 24x7 Call Logging 021 763 7147. Patrick Holahan [email protected] 079 523 [email protected]@tenet.ac.za