Bharath,
1) You are right, the vFW/vLB VNFs have multiple vNICs, one of these
attached to the public network. We tested them successfully in 3-4 different
vanilla OpenStack environments (Liberty and Mitaka versions) plus Rackspace. It
may be that your OpenStack configuration doesn’t allow you to attach vNICs
directly to public networks, but this feature can be enabled (although I can’t
help here, sorry for that)
2) The v_lb_init.sh script allows VPP to take over eth0 and eth1 in the
vLB VM. This doesn’t mean that you can’t reach the VM. It’s true that PING and
SSH don’t work, but VPP will accept nslookup requests on eth0 from an external
VM and use eth1 to forward those requests to one or more vDNS. We didn’t test
the vLB with floating IPs though. I remember that the configuration currently
in place couldn’t work straight away with floating IPs, so for the moment we
abandoned that path. As for the vDNS not connected to the vLB, try to see if
Java is downloaded and installed correctly, and if dnsmembership.sh and
dns_client.sh in vLB and vDNS VMs, respectively, are running. These scripts
launch a service that vLB and vDNS use to discover each other via the ONAP OAM
network.
3) The vFW/vLB demos work in ONAP release 1.0.0, in Rackspace. The ONAP
code currently in the master branch is supposed to support vFW/vLB demos in
vanilla OpenStack, although the code is being tested right now. Some issue is
preventing the closed loop to work correctly. If you want to test the closed
loop in OpenStack, you may consider to install ONAP 1.0.0 plus DCAE 1.1.0 and
MSO 1.1.0 in OpenStack. This will require some manual tinkering to Heat
templates and environment files. Josef succeeded in this. Here’s a summary of
his effort
artifacts_version: 1.1.0-SNAPSHOT
docker_version: 1.0-STAGING-latest
gerrit_branch: master
.
.
.
###########################
# #
# Parameters used by DCAE #
# #
###########################
dcae_base_environment: 1-NIC-FLOATING-IPS
dcae_zone: ZONE
dcae_state: STATE
nexus_repo_root:
https://nexus.onap.org<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.onap.org_&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=N1MCKelImtHVwwy-6Q4Pq6FahrJuv334be4HHcZj8ow&s=ClAys-4XzXIVtZym-43pxMoFzmi0omIL8uNH_lAgkkY&e=>
nexus_url_snapshot:
https://nexus.onap.org/content/repositories/snapshots<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.onap.org_content_repositories_snapshots&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=N1MCKelImtHVwwy-6Q4Pq6FahrJuv334be4HHcZj8ow&s=KdChJYaBpbLYlQJIX4e2ISysLoszOf078cyUiJfd6eI&e=>
gitlab_branch: master
dcae_code_version: 1.1.0
and I changed a line in the heat template for the dcae controller vm to use
docker version 1.1
echo "__docker_version__" > /opt/config/docker_version.txt
echo "1.1-STAGING-latest" > /opt/config/docker_version.txt
Thanks,
Marco
From: <[email protected]> on behalf of bharath thiruveedula
<[email protected]>
Date: Thursday, August 24, 2017 at 12:05 PM
To: "[email protected]" <[email protected]>, Josef
Reisinger <[email protected]>
Subject: [onap-discuss] vLB/vDNS Queries
Hi.
I am trying to setup vLB demo using 1.0.0 heat
template(https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/vLB/base_vlb.yaml;h=c292f2957d97bd7839d7fa7fcf55e04c1e9718ba;hb=refs/heads/release-1.0.0<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dheat_vLB_base-5Fvlb.yaml-3Bh-3Dc292f2957d97bd7839d7fa7fcf55e04c1e9718ba-3Bhb-3Drefs_heads_release-2D1.0.0&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=gNKFnl3Kv6KErWPFzYgVBPPuhce-0nLK0C_a-e10kXQ&s=qu0N5DWKPJmjJS1Eu3K1o6oS-nd-kY3iC-X06FIi1Rs&e=>).
But I have few queries/issue with the demo:
1) LB and DNS VMs has one network interface attached to public network, which
in most of the openstack environments won't assign the IP address. This issue
also faced in vFW also.
So in this case, I attached to another private network and launched the VMs
2) According to the
v_lb_init.sh<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dvnfs_vLB_scripts_v-5Flb-5Finit.sh-3Bh-3Dd130c1ec7eacab9dd8275ad2a43bf3f073bae861-3Bhb-3Drefs_heads_release-2D1.0.0&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=gNKFnl3Kv6KErWPFzYgVBPPuhce-0nLK0C_a-e10kXQ&s=KSbCDR8m6RKkoR4KnkPV35unXlmU2Q9W7RtBoId6h4I&e=>
script, it brings down both eth0 and eth1 interfaces and attach to them to
corresponding bridges along with the tap interfaces. In this case, I observed
it lost the connectivity to those interfaces. So I can't send the DNS queries
using Loadbalancer public IP(I assigned floating IP). I am not completely aware
of VPP and loadbalancer plugin it uses, so I might be missing something here.
I checked the VIPs using vppctl lb vip verbose, I couldn't see any AS here. I
tried to manually add AS pointing to DNS private IP. But that too doesn't work.
3) In one of the previous mail, I read that DNS scaling works with DCAE 1.0
only at the moment. In the DCAE 1.0 I can observe only one container which is
controller, I couldn't see any collector container. Am is missing something
here?
Any suggestions/help are much appreciated.
Best Regards
Bharath T
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
