Page tree
Skip to end of metadata
Go to start of metadata

This info is not up to date.

Hardware setup

IP rules for the class-C networks: (UCSM, CIMC usage)

  • 172.30.8.1-63 : reserved LF use
  • 172.30.8.64-255 : project use

similar rules for 172.30.9-13.0/24 subnet: (POD1-POD5 subnets)

  • 172.30.x.1-63 : reserved LF use
  • 172.30.x.64-255 : project use

Traffic filtering

There are three main firewall zones:

Zone name

VLAN

IP range

Description

nfvad

 

172.30.15.0/24

Admin P2P VPN access

nfvlo

410

172.30.8.0/24

Lights-out Management

nfvp1-5

411-415

172.30.9-13/0/24

POD1-5 subnets

ext

  

Public internet

The following traffic is allowed:

From

To

Proto

Ports

Description

nfvad

nfvp1,nfvp2

all

all

 

nfvad

nfvlo

all

all

 

nfvp1-5

ext

tcp

80, 443

Web

nfvp1-5

ext

udp

123

NTP

nfvp1-5

ext:8.8.8.8, ext:8.8.4.4

udp

53

DNS

nfvlo

ext

tcp

80, 443

Web

nfvlo

ext

udp

123

NTP

nfvlo

ext:8.8.8.8, ext:8.8.4.4

udp

53

DNS

nfvp1-5

nfvlo

udp

623

IPMI

Requesting Access to Linux Foundation Lab

Follow this guide: https://wiki.opnfv.org/display/INF/Infra+Lab+Support

 

STEP 1

Please send your access request to infra-steering@lists.opnfv.org. The following information should be included ...

  Name:
  Company:
  Approved Project:
  Project role:
  Why is access needed:
  How long is access needed (either a specified time period or define "done"):
  What specific POD/machines will be accessed:
  What support is needed from LF admins and LF community support team:


STEP 2

Should further clarifications be needed you may be asked to attend the next Pharos meeting (Weekly meetings logistics: https://wiki.opnfv.org/meetings#pharos_meetings) to discuss your request with the Pharos community.

STEP 3

Once access is approved please follow instructions for setting up VPN access ... https://wiki.opnfv.org/get_started/lflab_hosting

OPNFV Community Members with Access to OPNFV LF Lab

Below community members currently have the access to OPNFV LF Lab.

 

Member Name

POD/Resource

Project and Role

Why the Access is Needed

Revoke AccessReason to revoke access

1

fatih.degirmenci@ericsson.com

 

 

 

  

2

trozet@redhat.com

 

 

 

  

3

morgan.richomme@orange.com

 

 

 

  

5

vluc@cisco.com

 

 

 

  

6

juraj.linkes@pantheon.sk

 

 

 

  

7

viktor.tikkanen@nokia.com

 

 

 

  

8

juha.kosonen@nokia.com

 

 

 

  

9

r-mibu@cq.jp.nec.com

 

 

 

  

10

yroblamo@redhat.com

 

 

 

  

11

fpan@redhat.com

 

 

 

  

12

mpolenchuk@mirantis.com

 

 

 

  
13alexandru.avadanii@enea.com     

 

 

  • No labels