Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== OPNFV hosted infrastructure scenario's ======

This page provides an outline of the options available for establishing a CI and development environment for OPNFV.
The infrastrcuture required can be evaluated in terms of the baseline deployment POD's needed to support OPNFV activities.  Each POD is assumed to be made up of:
    3 x Control node (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 (FUEL/TripleO/Oscar)

==== 2 POD LinuxFoundation hosted CI & CD blade environment - preferred ====
Acquisition cost - 50K USD

Lead Time to operation -  2 weeks delivery, 1 week installation, 1 week infra flushing

Power Needs - >5KW (in one rack)

Running costs - Hosted in existing rack, (+2K USD per month, accommodated in existing infra budget)

Notes:  
Limitations 2 HDD per blade, Connectivity to be via OpenVPN or equivalent, gigabit access, suitable for at least a 3 year period

==== 2 POD LinuxFoundation hosted CI & CD Rack Mounted environment ====
Acquisition cost - 70K USD (requires a switch)

Lead Time to operation -  2 weeks delivery, 1 week installation, 1 week infra flushing

Power Needs - >5KW (in one rack)

Running costs - Hosted in existing rack, (+2K USD per month, accommodated in existing infra budget)

Notes:  
Connectivity to be via OpenVPN or equivalent, gigabit access, suitable for at least a 3 year period

==== 2 POD Metal as a Service hosted development environment ====

Unable to find a suitable provider with required access and no reduction in costs.

Acquisition cost - 0

Lead Time to operation - 

Power Needs - 0

Running costs - Approx 4K USD/month (first year)
Wiki

User Tools

Site Tools

Page Tools
