Age | Commit message (Collapse) | Author | Files | Lines |
|
Build script is executed with its heat template.
script_status.txt in /opt folder will show the status of execution of build and install script.
Issue-ID: INT-620
Change-Id: I4b0b5c49ed20458b21423fc83545203e1aea02f5
Signed-off-by: Praneta Paithankar <praneta.paithankar@intel.com>
|
|
Separate heat/env templates and build scripts have been created for vG-MUX and vG
The build logic and parameters are removed from the install scripts and
the base heat/env files used to deploy the VMs.
For backwards compatibility, the compile_state parameter was added to both VMs.
Small corrections were made to the heat templates for clarity.
Issue-ID: INT-615
Change-Id: I3180654f959776ebd4706613e00b9faff3f72e9e
Signed-off-by: Praneta Paithankar <praneta.paithankar@intel.com>
|
|
Replace the use of sites/raw in vnf HEAT templates
with zipped script artifacts
Change-Id: I93c331c0f4753e8bf661e5a577463ab38bd116f5
Issue-ID: INT-592
Signed-off-by: Gary Wu <gary.i.wu@huawei.com>
|
|
The vgmux env, yaml, install script, and hc2vpp patch files were edited to remove snapshot dependencies.
Change-Id: Ibfdef8cf35013c4fea8254437d12098a0bb82575
Issue-ID: INT-525
Signed-off-by: Enyinna Ochulor <enyinna.ochulor@intel.com>
|
|
Adds logic to reset the VES packet loss rate to 0%
when the vg-mux is rebooted.
As part of this change, the VES agent configuration
will only be restored via the honeycomb persistence
mechanism. So, if the VES agent is configured via
the vppctl CLI, that setting will not be saved during
shutdown. In other words, setting of the VES agent
and VES mode should be done via the honeycomb REST
API in order for the configuration to be persisted
across reboot (with the pkt loss rate being reset to
0 %).
Change-Id: I8d1f43316d9608f8d7e7ce919f129ce8fe48aa7f
Issue-ID: INT-63
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
|
|
Add parameters to the heat template to allow
configuration of the route the vBRG from the vGMUX
via the vBNG.
Change-Id: I7aef31af7470ceb264af06326af8724246c7d8ed
Issue-ID: INT-63
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
|
|
Move configuration of disabling auto upgrade to the
'build' phase of the install script.
Also, disable the setting in the /etc/apt/apt.conf.d/20auto-upgrades
file.
Auto upgrade of the kernel without associated packages can
cause vpp to stop working. This should help keep the demo
instances running without occasional failures.
Change-Id: Ief46bc7866a94d67fe2c3d2fe2d1f22bb4433aa9
Issue-ID: INT-63
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
|
|
Instead of hard coding VPP interface names, derive them from
the PCI addresses of the network devices when setting up the
default vpp configuration in /etc/vpp/setup.gate.
Also, remove the vxlan tunnel configuration from the default
vpp configuration - this will be created by SDNC.
Change-Id: Ife48ac19b8d3869c7d65e83bdf8ab9a5a2c3301c
Issue-ID: INT-63
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
|
|
This change improves the vG-MUX install script by:
- setting bng-mux network IP and mux-gw IP from environment
variables instead of hardcoded values
- provides ability to use script to prepare a snapshot image
with the vpp and honeycomb binaries pre-compiles to improve
vnf deployment time (was taking about 40 minutes).
Change-Id: Ib5423af6d88f4501ac3ecfd4a4cbc9b315460194
Issue-ID: INT-63
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
|
|
Correct a couple typos made in the vgmux install script.
Change-Id: Ib6eff3a875c3588bb1aad42a4105827d883b9c8d
Issue-ID: INT-63
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
|
|
Addresses the following items:
- Do not setup auto configuration for eth1 and eth3
These interfaces will be used by vpp so they need to be down
- Fix pci bus numbering for vpp interfaces
- Fixes to properly create the 'save_config' script
- Install linux-image-extra package to get uio_pci_generic
driver module for the vpp dpdk interfaces
- fix build of honeycomb so the jvpp-ves module built by vpp
can be found
- Patch libevel.so code to tweak the VES data produced
so that sourceId and sourceName come from the openstack
vnf_id property (instead of vm_uuid and vm_name)
Issue-ID: INT-63
Change-Id: I469c2377df9dd9920a5769628b2b14d043d55d63
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
|
|
Fixup URLs for the patch files to be applied to
VPP and honeycomb components.
Fix what looked like a typo in vgmux key attribute.
Create maven ~/.m2 directory before saving file to it.
Change-Id: Iccd10dac44b51a3ad4721422619c8823d8fa65bb
Issue-ID: INT-63
Signed-off-by: Eric Multanen <eric.w.multanen@intel.com>
|
|
Issue-ID: INT-80
Change-Id: I6ae3cabf62c85a8da85c8a4623db4aae0e5e4281
Signed-off-by: Johnson Li <johnson.li@intel.com>
|
|
Add Framework codes for the vCPE VNFs
Issue-ID: INT-80
Change-Id: I312aef9631636f0e2273f482f5db44ca93a55983
Signed-off-by: Johnson Li <johnson.li@intel.com>
Signed-off-by: root <rujun.li@intel.com>
|
|
- ONAP install
- vCPE/vFW/vLB use cases
- Use sources.list.d instead of apt-add-repository
- Parametrize the OS name
Change-Id: I7287fda8c5f3aa4ecd42ff576ebfd3b937bfa549
Issue-ID: INT-129
Signed-off-by: Marco Platania <platania@research.att.com>
|
|
- Add repos to sources.list.d instead of using add-apt-repository
Change-Id: I3f84bce0e189c3c0eed3d3dd2a292761726ec236
Issue-ID: INT-129
Signed-off-by: Marco Platania <platania@research.att.com>
|
|
Change-Id: I787ea63999ab302c064f4288ea68bd0de5139d37
Signed-off-by: Marco Platania <platania@research.att.com>
|
|
Change-Id: I36085089fcb524f9b0526717449feefc1c45f73b
Signed-off-by: Marco Platania <platania@research.att.com>
|