This is what I typically do. I modify /etc/mso/config.d/cloud_config.json in
the SO docker from:
{
"cloud_config":
{
"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"
}
},
"cloud_sites":
{
"RegionOne":
{
"region_id": "RegionOne",
"clli": "RegionOne",
"aic_version": "2.5",
"identity_service_id": "DEFAULT_KEYSTONE"
}
}
}
}
To
{
"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"
}
}
The identity_url in REGION_TWO_KEYSTONE uses MultiVIM as mediation layer, but
that’s not necessary. It depends on your environment. In my case, the second
region uses keystone v3, which is not supported by SO.
Do not restart your container, otherwise changes are lost. After you change
/etc/mso/config.d/cloud_config.json, you can look at any log, e.g.
/var/log/ecomp/MSO/BPMN/auditmso.log. It should tell you that a new config has
been loaded.
Marco
From: <[email protected]> on behalf of "A. Yahia Badr Eddine"
<[email protected]>
Date: Tuesday, July 3, 2018 at 8:43 AM
To: "[email protected]" <[email protected]>
Subject: [onap-discuss] Add new vim to onap
Hello,
I am performing the steps described in this link
https://wiki.onap.org/pages/viewpage.action?pageId=25431491<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D25431491&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=vvZJ0Wmb4Xzwee5xWvS2PcNCMrzFTmF-OIxMG0idelk&s=SPSBJX5PQrxymXKj987PbjDwo0goZIgGkFr6jOvMYW4&e=>
to add a new vim and i am facing a problem after updating the
/etc/mso/config.d/cloud_config.json file.
In fact, when i check the new config
(http://<so-vm-ip>:8080/networks/rest/cloud/showConfig<https://urldefense.proofpoint.com/v2/url?u=http-3A__-253Cso-2Dvm-2Dip-253E-3A8080_networks_rest_cloud_showConfig&d=DwQFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=vvZJ0Wmb4Xzwee5xWvS2PcNCMrzFTmF-OIxMG0idelk&s=gVM8xynNMbdTlkMcOGgYgmBetgRmpIWNOFpRBmxUcmg&e=>),
nothing changed and when verifying the cloud_config.json file, i did not find
my updates.
I replayed the config and restarted the mso docker but the problem persists.
Does anyone have any idea about the problem ?
Thanks,
Badr Eddine
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#10781): https://lists.onap.org/g/onap-discuss/message/10781
Mute This Topic: https://lists.onap.org/mt/23023672/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
