Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
1openUC and sipXecs Architecture & Directionmoderator: michael picherMarch 10, 2013 / Bentley Univesity / Boston MA
Intro of Presenters Team                               2> Load Testing & Build Team: > Douglas Hubler > Ciprian Hacman> SI...
Agenda                                               3> openUC & sipXecs 4.6 Architecture Overview> Testing Procedure> Tes...
Typical openUC / sipXecs Cluster
Multi-master (Before… 4.4 and earlier)
Single Master - Now
Message Queuing Introduced                                              7> Needed better interprocess communications > Lig...
Message QueuingPublisher / Subscriber                         8
Message QueuingDealer / Worker                  9
openUC 4.6 ArchitectureSQA                          10
Testing Procedure                                                         11> Manual smoke test    >Basic tests that catch...
Automated Load Tests                                                                                  12 sipxtest> Placing...
sipxtest - Architecture                                      13> Simple install ‘yum install sipxtest’> Pink – Files or Co...
Load Test Numbers                                                14 What do we do as part of build testing?> 3 days of loa...
openUC & sipXecs 4.6 Status                                                                       15> eZuce running in hou...
Roadmap – Near Term End of Q1 to End of Q2                                                                               1...
Roadmap – Longer Term                                                                                                17> o...
End      18
19> What is different as compared to traditional architectures?> What makes openUC an IT application?> High-level intro to...
Status of the 4.6 Release                                      20> What is new?> Experience with 4.6 in the field> Test re...
Deployment Examples                                               21> Pick 2 to 3 examples. E.g. Axcess Finacial
Roadmap                                              22> Discuss near term and longer term roadmap> What is our goal?
23
24
3:00-4:00            openUC and sipXecs    Moderator: Mike                                 ArchitectureParticipants: Dougl...
Prochain SlideShare
Chargement dans…5
×

openUC & sipXecs Architecture

  • Soyez le premier à commenter

openUC & sipXecs Architecture

  1. 1. 1openUC and sipXecs Architecture & Directionmoderator: michael picherMarch 10, 2013 / Bentley Univesity / Boston MA
  2. 2. Intro of Presenters Team 2> Load Testing & Build Team: > Douglas Hubler > Ciprian Hacman> SIP Core Team: > Joegen Baclor > Daniel Tacalau
  3. 3. Agenda 3> openUC & sipXecs 4.6 Architecture Overview> Testing Procedure> Test Automation> Status of 4.6> Roadmap Near-Term / Long-Term
  4. 4. Typical openUC / sipXecs Cluster
  5. 5. Multi-master (Before… 4.4 and earlier)
  6. 6. Single Master - Now
  7. 7. Message Queuing Introduced 7> Needed better interprocess communications > Lightweight > Robust> Evaluated several > Build? > RabbitMQ > ZeroMQ
  8. 8. Message QueuingPublisher / Subscriber 8
  9. 9. Message QueuingDealer / Worker 9
  10. 10. openUC 4.6 ArchitectureSQA 10
  11. 11. Testing Procedure 11> Manual smoke test >Basic tests that catch major issues> Manual sanity test >Detailed tests for each feature> Manual regression tests >Complex tests for features that are added/changed> Automated Load Tests> Deployment for a week on eZuce Production System >Dog fooding…
  12. 12. Automated Load Tests 12 sipxtest> Placing and receiving calls is the core feature and we want this to be stable> Basic testing cannot predict >How a server behaves over time >How a server behaves under stress> Call Load tests helps address both problems> Allows determination the performance of a Certain Server >All servers are different (physical, virtual)> Allows for determining how well openUC scales
  13. 13. sipxtest - Architecture 13> Simple install ‘yum install sipxtest’> Pink – Files or Commands that test user can interact with.> Yellow – Generated files (you can edit these files, but know that sipxtest changes overwrite edits)
  14. 14. Load Test Numbers 14 What do we do as part of build testing?> 3 days of load testing for all major builds> 15 calls per second> 4 million calls total
  15. 15. openUC & sipXecs 4.6 Status 15> eZuce running in house on production system since end of July 2012> Controlled release since August 2012> GA December 1, 2013> Update 1, February 5 > Polycom Firmware Updates, New iptables capabilities, bug fixes.> Update 2, February 6 (small revert)> Update 3, March 13 > fail2ban, bug fixes.
  16. 16. Roadmap – Near Term End of Q1 to End of Q2 16> openACD w/Supervisor & Agent Portals (openUC)> Multiple Level Administrator (openUC)> Multiple Time Zone (openUC & sipXecs)> Polycom VVX 300/400 Support> sipXsbc (openUC & sipXecs)> Session State Services – SSS (openUC & sipXecs?, clean up RLS / XMPP link)> Improvements to HA (get rid of odd # of server requirement, openUC & sipXecs)> Call Queueing> Unite 2.0 (openUC)
  17. 17. Roadmap – Longer Term 17> openACD Reporting (openUC)> Branch Office Solution (openUC & sipXecs?) > Will likely involve looking at User & System management differenly (i.e., more like a directory structure).> User Portal re-write (openUC) > Browser based client, WebRTC. Zero Install Communications Solution.> New Admin GUI (openUC & sipXecs) > Time to modernize a bit. The old interface is efficient but dated.
  18. 18. End 18
  19. 19. 19> What is different as compared to traditional architectures?> What makes openUC an IT application?> High-level intro to openUC architecture (diagram)> Hardware independence: What does this mean?> Resulting deployment options: Focus on flexibility, global scale, redundancy> Redundancy, branch redundancy> Focus on our ‘secret sauce’. What makes this architecture better than all the others?
  20. 20. Status of the 4.6 Release 20> What is new?> Experience with 4.6 in the field> Test results and test methodology
  21. 21. Deployment Examples 21> Pick 2 to 3 examples. E.g. Axcess Finacial
  22. 22. Roadmap 22> Discuss near term and longer term roadmap> What is our goal?
  23. 23. 23
  24. 24. 24
  25. 25. 3:00-4:00 openUC and sipXecs Moderator: Mike ArchitectureParticipants: Douglas, Daniel, Joegen, CiprianEngineering provided content:•Architecture overview (Mongo, SIP, XMPP, CFEngine high-level arch diagram).•Features and improvements delivered with 4.6•Test automation (how do we test?)•Status of 4.6•Deployment examples (distributed, virtualized, redundancy)•Roadmap – what to come next?

×