Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Using OpenStack to Accelerate New Product Development: Rik Harris, Telstra

2,377 views

Published on

Audience: Intermediate

About: Developing a new product from scratch in a large business can be a time- and effort-consuming exercise. When Telstra started our journey on a new initiative developing a new platform to support bringing new products to market more quickly and cost-effectively, we knew that we would need to do things a bit differently. How can we build faster and cheaper? Can we do it without deploying any physical elements? How can we get closer to our aspirations for a Continuous Deployment model? How can we start small(ish) and grow rather than deploying everything up front? This presentation will talk about these questions and how they lead to our use of OpenStack for both application deployment and a Network Functions Virtualisation platform.

Speaker Bio: Rik Harris – Cloud Technology Strategy, Telstra

Rik is an experienced IT professional who has been working in corporate and government Australia for around 25 years. He has been with Telstra since 2003 in several roles, including running IT infrastructure deployment teams, managing engineering for Telstra internal shared infrastructure and currently responsible for technology strategy for Telstra’s Cloud business.

OpenStack Australia Day - Sydney 2016
http://australiaday.openstack.org.au/sydney-2016/

Published in: Technology
  • Be the first to comment

Using OpenStack to Accelerate New Product Development: Rik Harris, Telstra

  1. 1. OpenStack Australia Day 2016 Rik Harris – Telstra Use Case: Telstra using OpenStack to accelerate new product development ©2016 Telstra Corporation Limited ABN 33 051 775 556
  2. 2. This presentation is intended to provide personal observations about using OpenStack to develop a service provider product. Examples and diagrams are illustrative only. It is not intended to provide guidance on Telstra’s products and services. The content is not to be used without the author’s permission.
  3. 3. Dynamic Network – Customer Benefits Empowering business with unified on demand ICT services Unified Product Experience Help increase customers speed to market Increase service velocity Faster activation Platform for innovation Goal ©2016 Telstra Corporation Limited ABN 33 051 775 556
  4. 4. The Dynamic Network Orchestration Virtualisation (NFV) Software defined networking Infrastructure Customer Premises Core Cloud Customer DC Managed Router NTU Service Edge Cloud Edge SaaS Bandwidth On Demand Path Selection High Availability Dynamic DDOS Self Healing 1100 01011010 0100 1100 01011010 0100 1100 01011010 0100 1100 01011010 0100 1100 01011010 0100 1100 01011010 0100 1100 01011010 0100 1100 01011010 0100 vFirewall vAnalyticsvRouter ©2016 Telstra Corporation Limited ABN 33 051 775 556
  5. 5. Network Overview Cisco Intercloud Services (OpenStack) Next IP® Gateway customer Next IP® (MPLS) VPN customer sites other customer projects/ tenancies Dynamic Networks Application project/ tenant Dynamic Networks VNF project/ tenant customer traffic portal traffic Telstra core systems mgmt traffic Internet ©2016 Telstra Corporation Limited ABN 33 051 775 556
  6. 6. Tenancy Architecture – Application VMSaaS Application OpenStack project ManagementVPNManagementVPN VNF Management VRF VNF Management VRF VNFManagementVNFManagement Telstra core systems PublicInternetPublicInternet LocalInternet(NAT)LocalInternet(NAT) Internet neutron router Internet neutron router NSONSO ESCESC CloudFoundryCluster Internet TransitionTransitionTransitionTransition VNF Management neutron router VNF Management neutron router Symphony VPN neutron router Symphony VPN neutron router ©2016 Telstra Corporation Limited ABN 33 051 775 556 ESC, NSO and VMS are Cisco products.
  7. 7. Tenancy Architecture – VNF VNF OpenStack project VNFManagementVNFManagement VNF Management VRF VNF Management VRF Internet InternetDirect(noNAT)InternetDirect(noNAT) Customer2Customer2 ASAvASAv Customer 2 VPN Customer1Customer1 Customer 1 VPN WSAvWSAv ASAvASAv TransitionTransition Customer3Customer3 CSRCSR ASAvASAv WSAvWSAv VNF Management neutron router VNF Management neutron router Next IP® Gateway Next IP® Gateway ©2016 Telstra Corporation Limited ABN 33 051 775 556 CSR, ASAv and WSAv are Cisco products.
  8. 8. Orchestration Architecture VNF Application VMS Application Control Plane Data Plane Cisco ESC Next IP® Gateway Internet OpenStack API Customer Site Next IP® (MPLS) VPN Customer Site Customer Site Network Orchestrator VNF 2 VNF 1 VNF 3 Portal/UI Cisco NSO Portal User ©2016 Telstra Corporation Limited ABN 33 051 775 556 ESC, NSO and VMS are Cisco products.
  9. 9. Benefits of using OpenStack Speed Initial development environments New application environments for testing ©2016 Telstra Corporation Limited ABN 33 051 775 556
  10. 10. Benefits of using OpenStack Flexibility Experiment with environment structure prior to go-live VNF Environments expand based on demand Speed Initial development environments New application environments for testing ©2016 Telstra Corporation Limited ABN 33 051 775 556
  11. 11. Benefits of using OpenStack Innovation Easy to try (and abandon) new product ideas Sandboxes for ongoing experimentation Flexibility Experiment with environment structure prior to go-live VNF Environments expand based on demand Speed Initial development environments New application environments for testing ©2016 Telstra Corporation Limited ABN 33 051 775 556
  12. 12. Benefits of using OpenStack Connectivity Direct connectivity available to Telstra’s Next IP® (MPLS) network Granular control over traffic flows (ACLs) – orchestrated as part of VNF deployment ©2016 Telstra Corporation Limited ABN 33 051 775 556
  13. 13. Benefits of using OpenStack Automation (Close to) full automation of application deployment using Cloud Foundry Opportunity for full test automation, including network elements Connectivity Direct connectivity available to Telstra’s Next IP® (MPLS) network Granular control over traffic flows (ACLs) – orchestrated as part of VNF deployment ©2016 Telstra Corporation Limited ABN 33 051 775 556
  14. 14. Observations & Challenges • Geographical locations for VNFs currently limited to CIS points of presence. • Using public cloud platform means we (mostly) can’t change the underlying platform capabilities. • Mix of neutron and VNF-based networking fitted our needs. ©2016 Telstra Corporation Limited ABN 33 051 775 556
  15. 15. Observations & Challenges • Generally run 6-8 environments concurrently, plus development. • Automation tools capabilities with OpenStack remains nascent – Puppet, Chef, Ansible, Salt. ©2016 Telstra Corporation Limited ABN 33 051 775 556 Puppet, Chef, Ansible and Salt are trademarked by their respective owners
  16. 16. Observations & Challenges • Generally run 6-8 environments concurrently, plus development. • Automation tools capabilities with OpenStack remains nascent – Puppet, Chef, Ansible, Salt. • Ansible 2.0 (beta, at the time) provided best support, but… ©2016 Telstra Corporation Limited ABN 33 051 775 556 Puppet, Chef, Ansible and Salt are trademarked by their respective owners
  17. 17. Observations & Challenges • Generally run 6-8 environments concurrently, plus development. • Automation tools capabilities with OpenStack remains nascent – Puppet, Chef, Ansible, Salt. • Ansible 2.0 (beta, at the time) provided best support, but… --- - name: create environment testing server os_server: state: present cloud: "{{ Symphony_Project }}" name: env-test-{{ Symphony_Project }} image: testimage key_name: symphony-testing timeout: 200 flavor: Micro-Small floating-ips: - 200.199.198.197 security_groups: - testservers nics: - net-name: "{{ Symphony_Internet_Name }}" - net-name: "{{ Symphony_Network_Name }}" ©2016 Telstra Corporation Limited ABN 33 051 775 556 Puppet, Chef, Ansible and Salt are trademarked by their respective owners
  18. 18. Observations & Challenges • Generally run 6-8 environments concurrently, plus development. • Automation tools capabilities with OpenStack remains nascent – Puppet, Chef, Ansible, Salt. • Ansible 2.0 (beta, at the time) provided best support, but… --- - name: create environment testing server os_server: state: present cloud: "{{ Symphony_Project }}" name: env-test-{{ Symphony_Project }} image: testimage key_name: symphony-testing timeout: 200 flavor: Micro-Small floating-ips: - 200.199.198.197 security_groups: - testservers nics: - net-name: "{{ Symphony_Internet_Name }}" - net-name: "{{ Symphony_Network_Name }}" Non-deterministic ©2016 Telstra Corporation Limited ABN 33 051 775 556 Puppet, Chef, Ansible and Salt are trademarked by their respective owners
  19. 19. Observations & Challenges • Lots of virtual networks! ©2016 Telstra Corporation Limited ABN 33 051 775 556
  20. 20. Observations & Challenges • Lots of virtual networks! • But they’re mostly managed by orchestration so we never have to use the topology view. ©2016 Telstra Corporation Limited ABN 33 051 775 556
  21. 21. Observations & Challenges • Lots of virtual networks! • But they’re mostly managed by orchestration so we never have to use the topology view. • Too many routes and ACLs to handle manually, even in the application projects. ©2016 Telstra Corporation Limited ABN 33 051 775 556
  22. 22. Observations & Challenges • Needed to provide access to OpenStack CLI and Ansible tools to various people • However the dependencies are still messy • Docker to the rescue! ©2016 Telstra Corporation Limited ABN 33 051 775 556
  23. 23. Observations & Challenges • Needed to provide access to OpenStack CLI and Ansible tools to various people • However the dependencies are still messy • Docker to the rescue! $ cat Dockerfile FROM ubuntu:15.10 ARG DEBIAN_FRONTEND=noninteractive ARG TERM=linux RUN apt-get -y update RUN apt-get install -y sudo make git python RUN apt-get install –y python-setuptools python-pip fping jq RUN apt-get install –y vim python-dev ssh-client RUN pip install shade RUN git clone git://github.com/ansible/ansible.git --recursive RUN cd ./ansible && make install && mkdir -p /etc/ansible && echo '[local]nlocalhost ansible_connection=localn' > /etc/ansible/hosts RUN useradd -d /home/symphony -M -G sudo symphony USER symphony ADD 90-symphony /etc/sudoers.d/90-symphony # default command: display Ansible version WORKDIR /home/symphony/Symphony CMD [ "ansible-playbook", "--version" ] ©2016 Telstra Corporation Limited ABN 33 051 775 556
  24. 24. Future Direction and Ideas • More VNF types, greater variety of product offerings, integration with more networks, etc. • Extend automated testing from unit and system to full integration. • Use additional (still OpenStack) VNF environments to improve geographic options. • Enhance Ansible OpenStack modules. ©2016 Telstra Corporation Limited ABN 33 051 775 556

×