physical pod
play

Physical POD Test and deployments #OpenCORD Full POD: definition - PowerPoint PPT Presentation

Physical POD Test and deployments #OpenCORD Full POD: definition The minimum amount of hardware that can be used to perform a full test of the current CORD features Mgmt L2 switch Tricks Fabric switch Avoid company proxy servers


  1. Physical POD Test and deployments #OpenCORD

  2. Full POD: definition The minimum amount of hardware that can be used to perform a full test of the current CORD features Mgmt L2 switch Tricks Fabric switch ● Avoid company proxy servers ● Use suggested hardware Fabric switch Fabric Suggested components: 4x white-box switches Fabric switch ● Server QuantaGrid D51B-1U (2x Intel Fabric switch E5-2630 v4 10C 2.2GHz 85W, 64GB of RAM 2133MHz DDR4, 2x hdd500GB) x86 server ● 40G NIC: Intel Ethernet Converged Compute Network Adapters XL710 10/40 GbE x86 server 3x standard x86 servers PCIe 3.0, x8 Dual port ● Switches: Accton 6712 - 32x40GE x86 server 2 #OpenCORD

  3. Network connectivity: user / data plane Spine 1 Spine 2 Fabric 4x whitebox switches Metro network Access devices Leaf 1 Leaf 2 Head node 1 Compute node 1 Compute 3x standard x86 servers Compute node 2 3 #OpenCORD

  4. Network connectivity: a complete view Fabric Linux mgmt to leafs to external Linux mgmt to internal Head node IPMI External network L2 Fabric to leafs switch IPMI Linux mgmt to internal Compute node 1 Internal mgmt L2 switch Fabric to leafs IPMI Linux mgmt to internal Compute node 2 Mgmt Spine 1 Internet Mgmt Fabric External access to the POD Spine 2 Where the operator connects Mgmt Fabric Leaf 1 Mgmt Fabric Leaf 2 Fabric 4 #OpenCORD

  5. Deployment steps Steps to deploy: Compute node 1 1. Download CORD repo on the dev machine Compute node 2 2. Create the CORD dev VM on the dev Internet machine Spine 1 3. Fetch CORD packages on the dev machine Head node Spine 2 4. Push the software to the head node 5. Deploy and configure the head node Leaf 1 Operator - 6. Reboot (to deploy) the compute Dev machine Leaf 2 nodes and the switches Runs ● OpenStack head node 7. Add your configurations ● ONOS ● XOS ● ... ● MAAS 5 #OpenCORD

  6. Issues ● Building a CORD POD requires ~3-4 hours (human interaction) ● Is there a way to automatically reset a POD? ● How do I do “CI”? What if I want to test a fresh installation with the latest changes every day? 6 #OpenCORD

  7. Jenkins integration Internet Compute node 1 Compute node 2 Spine 1 External network L2 Head node switch Spine 2 Leaf 1 Leaf 2 Operator 7 #OpenCORD

  8. Current status ! k c l i c a n i D O P D R O C a d l i u b n a c e W Partner 1 POD Partner 4 PODs 1 POD Nightly building master and CORD 2.0 Partner 8 1 POD #OpenCORD

  9. References Documentation http://wiki.opencord.org ● ● https://github.com/opencord/cord/blob/cord-2.0/docs/quickstart_physica l.md Contacts ● Mailing-list: cord-dev@opencord.org Slack: slack.opencord.org ● Presenter Luca Prete / luca@onlab.us ● 9 #OpenCORD

Recommend


More recommend