Differences

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

--- lab4_huawei [2015/03/09 08:25]
Jun Li created
+++ lab4_huawei [2015/03/09 09:36]
Hai Liu
@@ Line 4: / Line 4: @@
 While to be able to connect this environment, a remote user/client (e.g. PC with Internet access using Browser or ssh) should be able to connect to internet (http://publicip<addr>) and then be allocated a private IP address (192.168.x.y) from LNS (L2TP Network Server) via L2TP over IPsec. The remote user/client could use VPN for connection, e.g. download “Secoway VPN Client” software (Copyright of Huawei, Click “here” for download and use for OPNFV freely) and make configuration once it completes to register and apply for the access. An email with the guideline will be sent to you to show how to configure the client and make sure you can access the environment.
 The server cluster environment is illustrated below for the project BGS:
-{{ :testlabhw.png?direct&200 |}}
+{{ :huaweitestlab.png?direct&700 |}}
+//Figure 1: Huawei service cluster environment overview//
-Currently there are 3 "PODs" (a BGS POD has with 6 servers) operational and short term plan is stand-up 5 PODs. The first 2 PODs are being used by BGS project (which is driving compute, network and storage requirements). For support reasons all PODs will have identical network configurations however exceptions can be made if a project has a specific need.
-Current POD assignments ...
-  * POD 1 - Bootstrap/Get started - Development
-  * POD 2 - Bootstrap/Get started - Run/Verify
-  * POD 3 - Characterize vSwitch Performance (special requirements for test equipment and network configurations)
-  * POD 4 - Available April - to be assigned
-  * POD 5 - Available April - to be assigned
-Remote access uses OpenVPN via a 100 Mbps (symmetrical) internet link ... VPN Quickstart instructions are here:{{:pharos:opnfv_intel_hf_testbed_-_quickstart_vpn_.docx|}}
-All servers are PXE boot enabled and can also be accessed "out-of-band" using the lights-out network with RMM/BMC. Servers are current or recent generation Xeon-DP ... specs for each POD/server to be documented here.
-BGS environment details are here: https://wiki.opnfv.org/get_started/get_started_work_environment. The basic compute setup is as follows:
-  * 3 x Control nodes (for HA/clustered setup of OpenStack and OpenDaylight)
-  * 2 x Compute node (to bring up/run VNFs)
-  * 1 x Jump Server/Landing Server in which the installer runs in a VM
-Each POD (environment) supports 5 VLANs using pre-defined subnets. BGS networks are 1) Public 2) Private 3) Admin 4) Lights-out. Configuration details are here {{:pharos:opnfv_intel_hf_testbed_-_configuration.xlsx|}} Information includes physical network configuration (IPs etc.), NIC MAC addresses, IPMI logins, etc. Full specs for each node will also be captured here.
+The Jump Sever (192.168.100.2/24) is a Linux server and can be accessed by SSH/SFTP. All the Controller nodes/Compute nodes are PXE enabled, so you can re-deploy the OS to Controller node/Compute node from jump server via Linux Command line Interface (cli) or some GUI (later stages, not now). .
-**Collaborating**
+There are 3 pre-defined networks (i.e. Mgmt, O&M and ExtAPI), and all the gateways are configured on the Router. In the above environment, the VLAN number 111 (VLAN111) and 112 (VLAN112) are assigned for O&M network and ExtAPI network, and 2 IP subnets 192.168.111.0/24 and 192.168.112.0/24 are assigned to the 2 networks separately. VLAN numbers from 200 to 999 are reserved for private network, and users can define the IP subnet for specific VLAN if necessary. The IP subnet 192.168.110.0/24 is assigned for Mgmt network (i.e. VLAN110 in the above figure).
-  * Best practices for collaborating in the test environment are being developed and will be documented here
+Such a server cluster environment could be used as the infrastructure for OPNFV projects test, integration and education purpose. While it can also be extended to more PODs later for dedicated projects or purpose, e.g. POD for BGS, POD for ONOS integration, and etc. BGS may be considered for transition to CI after release 1
-  * The landing server is provisioned with CentOS 7. The project decides configurations for other servers and provisions accordingly
-  * The landing server has a VNC server for shared VNC sessions
-  * While VNC allows screens to be shared an audio session may be useful ... setup an audio-bridge or try a collaboration tool such as Lync, WebEx, Google Hangouts, Blue Jeans, etc.
+The BGS server cluster environment is available, to be used by OPNFV developers. As project mature and facility is expanded, we may consider adding PODs and introducing reservation systems with focused deliverables. If you have any question about the environment, please contact Jian Li (lijian20@huawei.com).
+Note: Currently there is no facility to save or backup the configurations, and will consider such requirements once the usage pattern and requirements get clearer. Until then please ensure backups of your work at client end. Also the facility may face downtime during weekends which will be notified to users of the server clusters via email.
-{{ :get_started:bgs-intel-pod1-network.jpg |}}
+**subject**: opnfv_huawei_access.
-//Figure 1: Intel OPNFV test-bed environment - overview of POD 1//
+Following information should be provided in the request:
+  * Full name
+  * e-mail
+  * Phone
+  * Organization
+  * OPNFV Contributor/Committer name :
+  * OPNFV Project(s) Association:
+  * LF ID:
+  * Recommended by:
+  * PGP public key (preferably registered with a PGP PKI server)
+  * SSH public key
-TAGS: BGS, Bootstrap Getting Started, Intel,Test, Lab
+Granting access normally takes 3-5 business days.
+Detailed access descriptions will be provided with your access grant e-mail, an excerpt version can be found here (https://wiki.opnfv.org/get_started/huawei_hosting/access)

Wiki

User Tools

Site Tools

Differences

Page Tools