I solved the problem by changing the VMs flavour. In fact, packet gen VM is
out of memory so programs crushes immediatly.
For the cloud-init problems, i noticed that scripts and artifacts version
have changed so we can try to browse the repositories url before.
Thanks,
Badr Eddine AY.
2018-07-05
Try to reboot the packet generator. We saw installations going bad due to some
cloud init or network hiccups.
Marco
On Wed, Jul 4, 2018 at 5:51 PM -0400, "A. Yahia Badr Eddine"
mailto:badreddine.aouledya...@gmail.com>>
wrote:
Yes, nothing weird in logs, scripts and files were downloaded an
Yes, nothing weird in logs, scripts and files were downloaded and installed
sucessefully.
2018-07-04 23:05 GMT+02:00 Pedro Barros :
> Did you checked the vnf VMs logs??
>
>
>
> On Wed, Jul 4, 2018 at 9:51 PM +0100, "A. Yahia Badr Eddine" <
> badreddine.aouledya...@gmail.com> wrote:
>
> Hello,
>>
Did you checked the vnf VMs logs??
On Wed, Jul 4, 2018 at 9:51 PM +0100, "A. Yahia Badr Eddine"
mailto:badreddine.aouledya...@gmail.com>>
wrote:
Hello,
I am running the vFWCL use-case on onap Beijing using a single heat template
that specifies the 3 vnfs.
I deployed successfully the service
Hello,
I am running the vFWCL use-case on onap Beijing using a single heat
template that specifies the 3 vnfs.
I deployed successfully the service but when browsing sink_ip:667, no
traffic was captured ( only 4 packets).
I use demo_artifacts_version: "1.2.2" and install_script_version:
"1.2.1-SNAP
