VNFs

There are different vendors providing uCPE based on multiple CPU architecture (x86, Arm, MIPS). VNF vendors cannot make their product be able to run over all these uCPEs. In our community, member companies will provide developer environment to adapt VNFs to different uCPEs. Most importantly, the community developers will help to finish the development. The VNF vendors need to clearly state their requirements or cooperate with member companies in their  Blueprint validation/integration labs. In this way, the VNF venders  are more likely to find potential partners and potential commercial market.


Company NameMain ContactWebsiteGet Started

NameEmail

Riverbed

https://www.riverbed.com/
FortinetYining Xingjxing@fortinet.comhttps://www.fortinet.com/
Mr. Huddhu@fortinet.com
Palo Alto Networks

John McDowall

jmcdowall@paloaltonetworks.comhttps://www.paloaltonetworks.com/
Lin Shuslin@paloaltonetworks.com
Wei Huangwhuang@paloaltonetworks.com
CheckpointPulin Wangpulinw@checkpoint.comhttps://www.checkpoint.com/
F5

https://www.f5.com/
6WINDKelly LeBlanckelly.leblanc@6wind.comhttps://www.6wind.com/

vRouter + IPSEC

https://doc.6wind.com/turbo-ipsec-2.0/index.html

Related blueprints

ELIOT: Edge Lightweight and IoT Blueprint Family

Related feature projects

Akraino Blueprint Validation Framework