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":
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",
The two lines below are not a problem:
./v_firewall_init.sh: line 67: /var/lib/honeycomb/persist/context/data.json: No
such file or directory
./v_firewall_init.sh: line 68: /var/lib/honeycomb/persist/config/data.json: No
such file or directory
During initialization, it’s just deleting old
Andrew,
I think it’s a good idea. I remember we talked about this a while ago, and I
still believe it’s worth the effort. In particular, I agree on implementing
APIs that can be used by controllers to execute LCM operations against the
VNFs. In this regard, we have experience with Honeycomb,
+ Vijay for the VES collector part.
Marco
From: Badr Eddine Aouled Yahia
Date: Monday, July 16, 2018 at 12:41 PM
To: "PLATANIA, MARCO (MARCO)"
Cc: "onap-discuss@lists.onap.org"
Subject: Re: [onap-discuss] vFwcl: no mesurements published to dmaap
It is heat based and i use the right ip and
Are you using Heat or OOM to install ONAP? IP 10.0.4.1 and port 8081 are used
for Heat only. For OOM you can use any IP address in the K8S cluster and port
30235.
Marco
From: Badr Eddine Aouled Yahia
Date: Monday, July 16, 2018 at 12:22 PM
To: "PLATANIA, MARCO (MARCO)"
Cc:
Enyinna,
This problem should be solved now. Please try the updated heat templates.
Thanks,
Marco
From: "Ochulor, Enyinna"
Date: Friday, July 20, 2018 at 7:37 PM
To: 'Gary Wu' , "PLATANIA, MARCO (MARCO)"
Cc: "Multanen, Eric W" ,
"'onap-discuss@lists.onap.org'"
Subject: RE: ONAP VCPE Install
Is the VES agent running in the vFW VM? What parameters did you use for
demo_artifacts_version and install_script_version in the Heat env file or SDNC
preload for the vFW installation?
Marco
From: on behalf of "A. Yahia Badr Eddine"
Reply-To: "onap-discuss@lists.onap.org" ,
There’s something missing… working on this right now.
Marco
From: Gary Wu
Date: Friday, July 20, 2018 at 7:53 PM
To: "Ochulor, Enyinna" , "PLATANIA, MARCO (MARCO)"
Cc: "Multanen, Eric W" ,
"'onap-discuss@lists.onap.org'"
Subject: RE: ONAP VCPE Install Script Changes
The parameter should
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
Try to run “vppctl show pac” in the traffic generator and see if traffic
streams are active. You should see at least one stream active. If not, or if
you are experiencing issues with VPP, something could be wrong with cloud init,
so you may need to restart the vPacketGen, as Brian suggested.
There is a bunch of information here:
https://wiki.onap.org/display/DW/Running+the+ONAP+Demos
In particular, I’d give a look at the videos in this section: “VNF Onboarding,
Instantiation, and Closed-loop Operations”
They refer to Amsterdam, but for Beijing is pretty much the same. Note that if
Stephen,
Thanks for checking. I just destroyed one ONAP instance in SB00 plus some VNFs
in SB07.
All,
Please, delete instances and VNFs that you aren’t using. DO NOT delete the ONAP
instance in SB07.
Thanks,
Marco
From: on behalf of "Gooch, Stephen"
Date: Tuesday, July 3, 2018 at 9:32
Jing,
Which VES library are you using? Is it the one in the demo repository or
something else?
Marco
From: on behalf of Jing Wang
Reply-To: "onap-discuss@lists.onap.org" ,
"jing.wa...@huawei.com"
Date: Thursday, October 11, 2018 at 5:30 PM
To: "onap-discuss@lists.onap.org"
Subject:
Thanks Jing,
I didn’t see that problem before, it seemed to run fine, but I’ll investigate
more.
Marco
From: on behalf of Jing Wang
Reply-To: "onap-discuss@lists.onap.org" ,
"jing.wa...@huawei.com"
Date: Friday, October 12, 2018 at 8:59 AM
To: "onap-discuss@lists.onap.org"
Subject: Re:
Yes, you can. You need to modify /etc/mso/config.d/cloud_config.json in the SO
container to have multiple cloud sites and multiple keystones, if the tenants
belong to different OpenStack labs. Otherwise, one identity service will
suffice. Something like this
{
"identity_services":
{
Vamshi,
Are you running ONAP Beijing or the current master/Casablanca branch?
If Beijing, then you don’t need to create a closed loop via CLAMP. The old
vLB/vDNS scale out use case (not to be confused with the new scale out use case
described here:
There must be something wrong with your settings then, I just copied and pasted
your command in my shell and run it in the WindRiver lab. I get this:
* Trying 10.12.6.0...
* Connected to 10.12.6.0 (10.12.6.0) port 30230 (#0)
* Server auth using Basic with user 'admin'
> PUT
>
Gary,
Change Management Team is using Integration-SB-04, while HPA Team is using
Integration-SB-06. I would leave those instances up for the moment. We should
be fine deleting Integration-SB-02.
Marco
From: on behalf of Gary Wu
Reply-To: "onap-discuss@lists.onap.org" ,
Itohan,
Thanks for the correction ☺
Let’s keep Integration-SB-04 though, that’s in use by Change Management folks.
Marco
From: on behalf of "Ukponmwan, Itohan"
Reply-To: "onap-discuss@lists.onap.org" ,
"itohan.ukponm...@intel.com"
Date: Tuesday, November 27, 2018 at 4:02 PM
To:
The port number that you are using is wrong. You should use 30230.
Marco
From: on behalf of "Prakash via Lists.Onap.Org"
Reply-To: "onap-discuss@lists.onap.org" ,
"prakas...@verizon.com"
Date: Wednesday, November 28, 2018 at 7:00 AM
To: "onap-discuss@lists.onap.org"
Subject: [onap-discuss]
Cristina,
Please follow this webpage to download VM images:
https://docs.openstack.org/image-guide/obtain-images.html
I typically use whatever is in the current directory here:
http://cloud-images.ubuntu.com/trusty/
I just spun up a vFW in my private lab and it worked as expected.
Marco
22 matches
Mail list logo