User Tools

Site Tools


pharos:spirentvctlab

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
pharos:spirentvctlab [2015/10/16 15:03]
Iben Rodriguez
pharos:spirentvctlab [2016/01/26 18:34] (current)
Iben Rodriguez
Line 5: Line 5:
   * **Lab name:** Spirent VCT Lab   * **Lab name:** Spirent VCT Lab
   * **Lab location:** USA West and East availability zones   * **Lab location:** USA West and East availability zones
-  * **Who to contact:​** ​dl-vct@spirent.com (Iben Rodriguez) - Use Slack for discussion: https://​opnfv.slack.com/​ +  * **Who to contact:​** ​iben.rodriguez@vmsec.com (Iben Rodriguez) - Use Slack for discussion: https://​opnfv.slack.com/​ 
-  * **Any main focus areas:** Network Testing and Measurement - IPv6, Storage, OpenDaylight,​ OpenContrail,​ MaaS, SaltStack, SDN and NFV Technology+  * **Any main focus areas:** Network Testing and Measurement - IPv6, Storage, OpenDaylight,​ OpenContrail, ONOS, MaaS, SaltStack, SDN and NFV Technology
   * **Any other details that should be shared to help increase involvement:​** This lab is used to develop the low level test scripts used to identify functional and performance limits of network devices. ​   * **Any other details that should be shared to help increase involvement:​** This lab is used to develop the low level test scripts used to identify functional and performance limits of network devices. ​
 +  * Support of the VCT Lab is provided by https://​cloudbase.it/​
  
 We have various hardware and software in the lab linked together with 40 Gigabit Ethernet. There are mostly whitebox x86 servers with ARM CPUs in the pipeline. We have various hardware and software in the lab linked together with 40 Gigabit Ethernet. There are mostly whitebox x86 servers with ARM CPUs in the pipeline.
Line 14: Line 15:
 We have a /48 and a /64 IPv6 as well as multiple /24 and smaller IPv4 publicly routable IPv6 subnets. We have a /48 and a /64 IPv6 as well as multiple /24 and smaller IPv4 publicly routable IPv6 subnets.
  
-As much as possible all activities should be scripted via Jenkins jobs using: https://​jenkins.vctlab.com:​9443/​+As much as possible all activities should be scripted via **Jenkins** jobs using: https://​jenkins.vctlab.com:​9443/​
  
-**Spirent VCT Lab** is currently working on 3 different **OpenStack** environments each one of them deployed on different *physical* hardware configuration:​+New nodes are created and managed with **Mist.IO** to support the following functions:​ 
 +  * SSH Key Management 
 +  * New system setup and provisioning - ability to deploy 10s and 100s machines at a time with manually or via a script 
 +  * Role Based Access 
 +  * Monitoring and Alerting for Windows, VMware, Linux, KVM, OpenStack and other platforms 
 +  * Run scripts and access shell console for remote administration 
 +  * IP Address Management 
 +  * Web UI, Command Line (CLI), and Rest API available 
 + 
 +**Spirent VCT Lab** is currently working on 3 different **OpenStack** environments each one of them deployed on different ​**physical** hardware configuration:​
   * **OpenStack Juno** (Ubuntu 14.04.1 LTS, 10 cores, 64GB RAM, 1TB SATA, 40 Gbps) - snsj53 <-- used for 40 gbps SR-IOV performance testing   * **OpenStack Juno** (Ubuntu 14.04.1 LTS, 10 cores, 64GB RAM, 1TB SATA, 40 Gbps) - snsj53 <-- used for 40 gbps SR-IOV performance testing
   * **OpenStack Kilo** (CentOS 7.1, 10 cores, 64GB RAM, 1TB SATA, 40 Gbps) - snsj54 <-- shared between OPNFV and 40 gbps SR-IOV performance testing   * **OpenStack Kilo** (CentOS 7.1, 10 cores, 64GB RAM, 1TB SATA, 40 Gbps) - snsj54 <-- shared between OPNFV and 40 gbps SR-IOV performance testing
pharos/spirentvctlab.1445007786.txt.gz · Last modified: 2015/10/16 15:03 by Iben Rodriguez