[VoiceOps] Broadsoft / Puppet

John Botha johnbotha at hotmail.com
Mon Dec 8 07:57:26 EST 2014


Hoping i am not getting wires crossed or misunderstanding here. I administer the broadsoft and sbc voip platform, our sysadmins uses puppet not for orchestration or vm management but for configuration management with a puppet client (http://puppetlabs.com/)
The puppet deployment we have focuses on keeping configuration files in sync and current and have rollback in case someone badly fubar the OS platform.

Date: Mon, 8 Dec 2014 02:35:53 -0800
From: ahardie at bellsouth.net
Subject: Re: [VoiceOps] Broadsoft / Puppet
To: johnbotha at hotmail.com
CC: peeip989 at gmail.com; voiceops at voiceops.org

Right - understood - 
My question was around the AS/XS server - the one housing all the service logic.  That system may be problematic since the service model is usually a fixed number of features in inventory.  I would think you could use puppet to spin up media servers as needed - and network servers to a lesser extent.  
As for engaging  BroadSoft TAC I would ask them this  - if the server was provisioned and placed into server in a more traditional manner - would BroadSoft TAC allow tickets to be opened? Assuming the answer would be yes - I would then position your Puppet deployment to BroadSoft TAC as just that - your deployment platform (jump box to them).  
Other than asking permission I doubt you would need to ask BroadSoft anything around Puppet in particular - just tell them your servers are being provisioned via Puppet.  If the servers are provisioned to BSFT spec then you should be ok.
Hope this helps,
Alex Hardie 

     On Monday, December 8, 2014 12:48 AM, John Botha Hotmail <johnbotha at hotmail.com> wrote:
    

 
    Broadsoft at an application layer itself isn't aware of it. When we
    queried them around the use of puppet or any other 3d party software
    of any kind, their reply was that general policy is not to support
    any software not loaded by Broadsoft that can even remotely possibly
    interfere with the working of the application.
    
    Anything we cannot raise a TAC on is not supported.
    
    On 07/12/2014 21:22, Alex Hardie wrote:
    
    
      Wait - why would BroadSoft even be aware of Puppet?  I assume
        orchestration was around spinning up
      various servers - AS servers are the only ones that would be
        bound by licenses.  Spinning up NS or MS should be transparent -
        they (BroadSoft) wouldn't care.
      
      
      What servers were you provisioning ?
      
      
      Alex Hardie
      
        On Dec 7, 2014, at 1:27 AM, johnbotha <johnbotha at hotmail.com>
        wrote:
        
      
      
        
          
            We tried using puppet, but had top remove it due to
              broadsoft policy on unsupported software.
            
            
            
            
            
              Sent from Samsung
                Mobile
            
          
          
          
          
          -------- Original message --------
          From: Peter E <peeip989 at gmail.com>
          
          Date: 05/12/2014 22:57 (GMT+02:00) 
          To: VoiceOps <voiceops at voiceops.org>
          
          Subject: [VoiceOps] Broadsoft / Puppet 
          
          
          Anyone out there using Puppet to help manage their Broadsoft
          servers? Any conflicts or issues? Any feedback appreciated.
          
          Thanks,
          Pete
          
          
          _______________________________________________
          VoiceOps mailing list
          VoiceOps at voiceops.org
          https://puck.nether.net/mailman/listinfo/voiceops
        
      
      
        _______________________________________________
          VoiceOps mailing list
          VoiceOps at voiceops.org
          https://puck.nether.net/mailman/listinfo/voiceops
        
      
    
    
  

       		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20141208/d9a090a7/attachment.html>


More information about the VoiceOps mailing list