Please join and post "validated" actions/config/results - but do not move or edit this page until we get a complete vFW run before Ideally the 4 Dec KubCon conference and worst case the 11 Dec ONAP Conference - thank you
Under construction - this page is a consolidation of all details in getting the vFirewall running over the next 2 weeks in prep of anyone that would like to demo it for the F2F in Dec.
ADD content ONLY when verified - with evidence (screen-cap, JSON output etc..) DO paste any questions and unverified config/actions in the comment section at the end - for the team to verify |
Daily meeting at 1200 EDT noon - https://zoom.us/j/7939937123 see schedule at https://lists.onap.org/pipermail/onap-discuss/2017-November/006483.html
Statement of Work
Ideally we provide this page as a the draft that will go into ReadTheDocs.io - where this page gets deleted and referenced there.
There are currently 3 or more distinct pages, email threads, presentations, phone calls, meetings where all the details needed to "Step by Step" get a running vFirewall up are located.
We would like to get to the point where we were before Aug 2017 where an individual with an Openstack environment (OOM as well now) - could follow each instruction point (action - and expected/documented result/output) and end up with our current minimal sanity usecase - the vFirewall
If you have any details on configuration of getting up the vFirewall post them to the comments section and it will be tested and incorporated
Ideally any action added to this page itself - is fully tested with resulting output (text/screencap) - pasted as a reference.
Output
1- This set of instructions below - to go from an empty OOM host or OpenStack lab - all the way to closed loop running.
2 - A set of videos - the vFirewall from an already deployed OOM and HEAT deployment - see the reference videos from Running the ONAP Demos#ONAPDeploymentVideos see - INT-333Getting issue details... STATUS
3- Secondary videos on bringing up OOM and HEAT deployments
Running the vFirewall Demo
Prerequisites
OOM
HEAT
Get an openlab account - Integration / Developer Lab Access | |
Install openVPN - Using Lab POD-ONAP-01 Environment | |
Login to Openstack |
vFirewall Tasks
Ideally we have an automated one-click vFW deployment - in the works -
T# | Task | Action Rest URL+JSON payload | Result JSON / Text / Screencap | Artifacts Link or attach file | Env OOM HEAT or both | Last run | Notes |
---|---|---|---|---|---|---|---|
Before robot init (init_customer and distribute | |||||||
1 | TBD - cloud region PUT to AAI | TBD 201711xx | |||||
TBD Customer creation | |||||||
TBD SDC Distribution | |||||||
TBD VID Service creation | |||||||
TBD VID Service Instance deployment | |||||||
TBD VID Create VNF | |||||||
TBD VNF preload | |||||||
TBD VID Create VF-Module | |||||||
TBD Robot Heatbridge | |||||||
TBD APPC mountpoint (Robot or REST) |
Verifying the vFirewall
Original/Ongoing Doc References
running vFW Demo on ONAP Amsterdam Release
Clearwater vIMS Onboarding and Instantiation
Integration Test - could not find vFW content here
ONAP master branch Stabilization
Questions to Resolve
20171122: Do we run the older robot preload or do we do the SDNC rest PUT manually
Older Tutorial: Creating a Service Instance from a Design Model#RunRobotdemo.shpreloadofDemoModule
20171122: Do we use the older June vFW zip (yaml + env) or must we use a new split template
investigate Brian's comment on running vFW Demo on ONAP Amsterdam Release - "If you want to do closed loop for vFW there is a new two VNF service for Amsterdam (vFWCL - it is in the demo repo) that separates the traffic generator into a second VNF/Heat stack so that Policy an associate the event on the LB with the VNF to be controlled (the traffic generator) through APPC. Contact Pam and Marco for details."
- INT-342Getting issue details... STATUS
20171122: Do we run the older robot appc mountpoint or do we do the APPC rest PUT manually
List of ONAP Implementations by Environment
Please add yourself to the list so we can target EPIC work based on environment affinity
Environment | Deployer | Contacts | Status/Notes/vFW-status |
---|---|---|---|
Intel Openlab | HEAT | Starting up (20171123) | |
Intel Openlab | OOM Kubernetes | ||
Rackspace | OOM Kubernetes | (non-DCAE ONAP components only) DCAEGEN2 not tested yet for R1 | |
Continuous Deployment References
Tech | Servers | Details |
---|---|---|
HEAT | ||
Kubernetes | Jobs Analytics CD servers cd2.onap.info | OOM R2 Master (Beijing) http://jenkins.onap.info/job/oom-cd-release-110-branch/ OOM R1 (Amsterdam) |