| Table of Contents |
|---|
Define a Vendor Virtual Software Product (VSP)
At this point, we can proceed to define our vendor virtual software product. Hover over the "Add" box in the Onboarding Catalog and click on "New Vendor Virtual Software Product":
In the form that comes up, give the new software product a name of your choosing, and from the "Vendor" list, select the licensing model we created in the first part of this tutorial.
...
Now, we can upload the ZIP file containing the Heat templates and scripts that describe our product. Click on "Overview" to return to the main page for the product we're creating. Click on the "Select File" button in the right-hand section of the page (or drag and drop your zip file). The zip file we're using for this tutorial is vFW 14.2.17as of 20170608 for 1.0.0 vFW_100_20170608.zip in the reference page, which can be obtained from the Reference Documents page.
This vFW example is hardcoded to the EAST coast IAD region - to use the DFW region we should be able adjust the env file - see
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
TODO:20170517: actually the vFW zip in the reference page states it is "old not for use" since 5 May - we will need to verify which of the 3 sets of yaml/env pairs are valid (zip contains base_vfw but I would expect we should be running base_vfw_rackspace under \demo\heat\vFW
Repackage the ZIP - by following Pre-Onboarding
The Heat template and environment file will be processed by SDC and a page showing the contents of the uploaded zip file will be displayed. The warnings in the right panel can be ignored. This page can be reached from the "Attachments" link in the left sidebar. Click on proceed on validation and then click on Submit
Now, we can "Check In", and then "Submit" our software product. If no problems are encountered, an alert showing the the product has been successfully submitted will be briefly displayed.
...
Clicking on left pane "Composition" under "Properties" takes us into the actual Design Studio, where a graphical representation of our underlying VSP is shown on the canvas. To return to the VF specification, click on "VF: tutorial firewall" in the bread crumbs above the canvas.
Dont need to connect the two parts of the firewall - they are already in the same network
The "Activity Log" page tracks all changes to the VF.
...