SO should have information about both regions/tenants, as below:

/etc/mso/config.d/cloud_config.json:

{
    "identity_services":
    {
        "DEFAULT_KEYSTONE":
        {
          "identity_url": "http://135.197.225.10:35357/v2.0";,
          "mso_id": "admin",
          "mso_pass": "2fa2266344b4caaca1eba8264d277831",
          "admin_tenant": "service",
          "member_role": "admin",
          "tenant_metadata": true,
          "identity_server_type": "KEYSTONE",
          "identity_authentication_type": "USERNAME_PASSWORD"
        },
        "REGION_TWO_KEYSTONE":
        {
          "identity_url": 
"http://10.43.213.157:9001/api/multicloud/v0/CloudOwner_RegionTwo/identity/v2.0";,
          "mso_id": "marco",
          "mso_pass": "f461eb3230f0b4b7b1ce8ed018da155f",
          "admin_tenant": "service",
          "member_role": "admin",
          "tenant_metadata": true,
          "identity_server_type": "KEYSTONE",
          "identity_authentication_type": "USERNAME_PASSWORD"
        }
    },
    "cloud_sites":
    {
        "RegionOne":
        {
          "region_id": "RegionOne",
          "clli": "RegionOne",
          "aic_version": "2.5",
          "identity_service_id": "DEFAULT_KEYSTONE"
        },
        "RegionTwo":
        {
          "region_id": "RegionTwo",
          "clli": "RegionTwo",
          "aic_version": "2.5",
          "identity_service_id": "REGION_TWO_KEYSTONE"
        }
    }

You need to create a separate OAM network in the other region, such that VNFs 
can use it. ONAP and VNFs will communicate using public IPs. So, when you 
create a VNF, you need to provide the public IP of the DCAE collector instead 
of the private one. Likewise, when you mount the VNF into APPC, you need to use 
the public IP of the VNF (vPacketGen in the vFWCL case).

Marco

From: <onap-discuss@lists.onap.org> on behalf of "A. Yahia Badr Eddine" 
<badreddine.aouledya...@gmail.com>
Date: Tuesday, July 3, 2018 at 3:31 PM
To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: [onap-discuss] Run vFWCL on newly registered VIM

Hello,
I am trying to run the vFWCL on a newly registered VIM.
The ONAP instance runs on a tenant1 in regionOne.
As i don't have enough resources in tenant1, i should deploy the vFW and run 
the close loop on another tenant2 on regionTwo.
I have a problem to connect the use-case VMs to the ONAP OAM network because 
they are not on the same tenant. And so, the vfw VM cannot reach the DCAE to 
send mesures and i cannot perform the appc mount point.
Does anyone have an idea how to enable the vFWCL use-case VMs to reach ONAP OAM 
network in order to run the close loop?
Thanks,
Badr Eddine AY.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10811): https://lists.onap.org/g/onap-discuss/message/10811
Mute This Topic: https://lists.onap.org/mt/23026962/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to