A couple of notes:
1. There should not be multiple endpoints with the same name defined in
OpenStack. It's likely that one is a remainder from some earlier test. You may
need to use "openstack endpoint delete ..." to remove one of the endpoints.
Being related to keystone in this case, it's not something that was setup by
this test script. It may also be some quirk in the way that MOS sets up the
endpoints, that I have not encountered so far.
* Send me the result of "openstack endpoints list" and "openstack
endpoint show <id of the duplicate endpoints>" for each endpoint. I will see if
I can mod the script to handle it, if it's not some error in the Fuel setup.
2. "OS_CACERT=/etc/ssl/certs/mcp_os_cacert" looks like some Fuel-specific
cert file. I'm not sure what the effects related to that might be. You will
probably need Fuel team support. It could indicate that for Fuel, there needs
to be some additional file installed on the Tacker client... I have not
encountered such an error on Apex or JOID.
Thanks,
Bryan Sullivan | AT&T
From: [email protected] [mailto:[email protected]]
Sent: Tuesday, January 09, 2018 9:05 PM
To: SULLIVAN, BRYAN L (BRYAN L) <[email protected]>; Tina Tsou
<[email protected]>; [email protected]; UKASICK, AIMEE L (AIMEE L)
<[email protected]>; Joe Kidder <[email protected]>
Cc: '[email protected]' <[email protected]>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates
Hi Bryan and Joe,
I could create an image for tacker on ARM Pod using tacker.sh. I had to change
start.sh in /tmp/models/ to account for a change in "endpoint create" API
syntax and also to account for multiple endpoints with the same name in
openstack. The Tacker container is now started but still encounters an error
for "tacker vim-register" as below. I also encountered some auth failure for
this command on last Friday (for auth_url:
http://172.16.10.10:35357/v3<https://urldefense.proofpoint.com/v2/url?u=http-3A__172.16.10.10-3A35357_v3&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=LziGvWKWfpDSxEcmkC8XcJwgqCg0TyKTCQWLSJhUYXw&s=Dqvdqx1SEDw9iIydILAy9Xx3TKFem1c-xvfDGYMzvyc&e=>
and OS_PROJECT_DOMAIN_ID=Default). I was also wondering about the non-existent
file for OS_CACERT=/etc/ssl/certs/mcp_os_cacert being used in env. Complete
session logs are attached.
main:203 (Wed Jan 10 03:39:11 UTC 2018) Register default VIM
SSL exception connecting to
https://10.10.50.103:5000/v2.0:<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.10.50.103-3A5000_v2.0-3A&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=LziGvWKWfpDSxEcmkC8XcJwgqCg0TyKTCQWLSJhUYXw&s=PBLuYji938qnVhsaxYC7LmQvnjmWEE6ZesHAaX0kxOo&e=>
None: Max retries exceeded with url: /v2.0 (Caused by None)
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource return
method(*args, **kwargs)
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource File
"/usr/local/lib/python2.7/dist-packages/tacker/nfvo/drivers/vim/openstack_driver.py",
line 203, in register_vim
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource ks_client =
self.authenticate_vim(vim_obj)
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource File
"/usr/local/lib/python2.7/dist-packages/tacker/nfvo/drivers/vim/openstack_driver.py",
line 120, in authenticate_vim
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource keystone_version
= self._validate_auth_url(auth_url)
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource File
"/usr/local/lib/python2.7/dist-packages/tacker/nfvo/drivers/vim/openstack_driver.py",
line 158, in _validate_auth_url
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource raise
nfvo.VimConnectionException(message=str(e))
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource
VimConnectionException: SSL exception connecting to
https://10.10.50.103:5000/v2.0:<https://urldefense.proofpoint.com/v2/url?u=https-3A__10.10.50.103-3A5000_v2.0-3A&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=LziGvWKWfpDSxEcmkC8XcJwgqCg0TyKTCQWLSJhUYXw&s=PBLuYji938qnVhsaxYC7LmQvnjmWEE6ZesHAaX0kxOo&e=>
None: Max retries exceeded with url: /v2.0 (Caused by None)
2018-01-10 03:39:38.028 1310 ERROR tacker.api.v1.resource
2018-01-10 03:39:38.036 INFO tacker.wsgi
[req-69c4ec56-0faf-4de2-9f13-4d2c43176720 admin admin] 172.17.0.2 - -
[10/Jan/2018 03:39:38] "POST /v1.0/vims.json HTTP/1.1" 500 417 1.900016
Regards,
Pramod
From: SULLIVAN, BRYAN L (BRYAN L) [mailto:[email protected]]
Sent: Tuesday, January 9, 2018 5:50 PM
To: Pramod Sudrik (Product Engineering Service)
<[email protected]<mailto:[email protected]>>; Tina Tsou
<[email protected]<mailto:[email protected]>>; Eric DMaye (Product Engineering
Service) <[email protected]<mailto:[email protected]>>; UKASICK, AIMEE L
(AIMEE L) <[email protected]<mailto:[email protected]>>; Joe Kidder
<[email protected]<mailto:[email protected]>>
Cc: '[email protected]'
<[email protected]<mailto:[email protected]>>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates
** This mail has been sent from an external source **
Re ARM arch, good point. I don't have ARM hw and did not build this for ARM.
You can try to build it using the script (tacker.sh) in the models build
folder. If it works, you will need to push the container to docker hub and
patch the vHello_Tacker.sh script to reference it, or figure out how to pull it
as a local container image.
Thanks,
Bryan Sullivan | AT&T
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]]
Sent: Tuesday, January 09, 2018 3:09 PM
To: SULLIVAN, BRYAN L (BRYAN L)
<[email protected]<mailto:[email protected]>>; Tina
Tsou <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>; UKASICK, AIMEE L (AIMEE L)
<[email protected]<mailto:[email protected]>>; Joe Kidder
<[email protected]<mailto:[email protected]>>
Cc: '[email protected]'
<[email protected]<mailto:[email protected]>>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates
Hi Bryan,
I am copying Joe for getting info/process used by him to deploy OPNFV/Fuel in
this ARM Pod.
The sudo docker logs -f tacker shows "standard_init_linux.go:178: exec user
process caused "exec format error"". The "sudo docker image inspect
blsaws/models-tacker" shows "Architecture": "amd64", so I was wondering whether
we need specific docker image for ARM architecture.
Regards,
Pramod
From: SULLIVAN, BRYAN L (BRYAN L) [mailto:[email protected]]
Sent: Tuesday, January 9, 2018 4:25 PM
To: Pramod Sudrik (Product Engineering Service)
<[email protected]<mailto:[email protected]>>; Tina Tsou
<[email protected]<mailto:[email protected]>>; Eric DMaye (Product Engineering
Service) <[email protected]<mailto:[email protected]>>; UKASICK, AIMEE L
(AIMEE L) <[email protected]<mailto:[email protected]>>
Cc: '[email protected]'
<[email protected]<mailto:[email protected]>>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates
** This mail has been sent from an external source **
Two minor edits:
1. The link to start.sh (thanks, outook):
https://git.opnfv.org/models/tree/build/tacker/start.sh<https://urldefense.proofpoint.com/v2/url?u=https-3A__clicktime.symantec.com_a_1_Hrc5FkwpOuR8oAokrxZxTcfkcUrwV51dApwrhglEbQU-3D-3Fd-3DRUYeklrPVwVzZE5eiA5cg3dR4EYyLEGe2F-5F8lh-5F2kzeC5uCLQj9r7PM10v7jkOTnDcm6ECMCqMeWqJ1RQrrGBFi51-2D-5FdJeN0nn1K01wo6IXxU1MwTcJzgrZKLKSe9-2Dw6m471SIQlS0JwMYX18HBJaKwUBKDT41N7aEaD-2D2GWzOiMGohQIfgWJ-5FZcMdpUPDzbW-2DpJYpJJdKt7RTLJWGQ-2DC9UjdF03zvxqPmDOh8t0ZcYy9EeQ-2DOIdhFQg-5FWFKMqz0-5FO54TYg4-2DVxZVycFnxKLnbx70svqhg-5FWcIGsN1Ih1Lg7LOrVFT4A5ehNSWBmx6kz9sQRCpJ-5F-2DhwYhARmU6kW8Rkqp3nlg5DfnJWsZ4jEajEVQX8qVMYAPbqC9odOgnO6gidOuoWuJhPW00lcHu-5FyBP7hviQNUjqLbwf7MxV8llE12XUZqqj3WFBgEJXS-26u-3Dhttps-253A-252F-252Fgit.opnfv.org-252Fmodels-252Ftree-252Fbuild-252Ftacker-252Fstart.sh&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=iDExEl-ilkVzCpkvtfMQmWqql4dCX4h0UZeZO2g2E2s&s=uaesfvInkRWLGR6yrtUmC5rrHURq8TfHA6viCcH98KA&e=>
2. start.sh already discovers the region name via the API so I'm not sure
what's going on as reported in your log. See the line:
region=$(openstack endpoint list | awk "/ nova / { print \$4 }" | head -1)
Thanks,
Bryan Sullivan | AT&T
From: SULLIVAN, BRYAN L (BRYAN L)
Sent: Tuesday, January 09, 2018 2:13 PM
To: '[email protected]'
<[email protected]<mailto:[email protected]>>; Tina Tsou
<[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>; UKASICK, AIMEE L (AIMEE L)
<[email protected]<mailto:[email protected]>>
Cc: '[email protected]'
<[email protected]<mailto:[email protected]>>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates
Can you send directly the info/process you used to deploy Fuel, in as much
detail as possible? I will try to duplicate it in my lab so I have enough info
to see what's going on. My tests so far were under Centos with Apex.
Some answers to your specific questions:
1. If the tacker container exited, then there is an issue with the tacker
setup and I would not expect the "tacker vnf-create" step to work.
2. The nfv-orchestration endpoint is created in the process of start.sh in
the container: see https://git.opnfv.org/models/tree/build/tacker/start.sh line
55<https://urldefense.proofpoint.com/v2/url?u=https-3A__clicktime.symantec.com_a_1_SVYSmBwMT4BKSWX8bLMlbbG9P18CUTaQ-5FXNbDME-2DSNA-3D-3Fd-3DRUYeklrPVwVzZE5eiA5cg3dR4EYyLEGe2F-5F8lh-5F2kzeC5uCLQj9r7PM10v7jkOTnDcm6ECMCqMeWqJ1RQrrGBFi51-2D-5FdJeN0nn1K01wo6IXxU1MwTcJzgrZKLKSe9-2Dw6m471SIQlS0JwMYX18HBJaKwUBKDT41N7aEaD-2D2GWzOiMGohQIfgWJ-5FZcMdpUPDzbW-2DpJYpJJdKt7RTLJWGQ-2DC9UjdF03zvxqPmDOh8t0ZcYy9EeQ-2DOIdhFQg-5FWFKMqz0-5FO54TYg4-2DVxZVycFnxKLnbx70svqhg-5FWcIGsN1Ih1Lg7LOrVFT4A5ehNSWBmx6kz9sQRCpJ-5F-2DhwYhARmU6kW8Rkqp3nlg5DfnJWsZ4jEajEVQX8qVMYAPbqC9odOgnO6gidOuoWuJhPW00lcHu-5FyBP7hviQNUjqLbwf7MxV8llE12XUZqqj3WFBgEJXS-26u-3Dhttps-253A-252F-252Fgit.opnfv.org-252Fmodels-252Ftree-252Fbuild-252Ftacker-252Fstart.sh-2520line-252055&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=iDExEl-ilkVzCpkvtfMQmWqql4dCX4h0UZeZO2g2E2s&s=nnyXSouE7RIC_evhcyXeNkw617VbOMWUM_OtDXu8emo&e=>.
3. Note that you can dump the tacker container log with "sudo docker logs
tacker" or follow it (tail) with "sudo docker logs -f tacker". Do that and you
will likely see the issue that led to the endpoint not being created. If the
container is running, you can use "sudo docker exec -it /bin/bash" to poke
around in the container, e.g. to debug using the openstack CLI etc from within
the container.
4. I have no idea where "fatal: /home/ubuntu/auto/keystonercv3:
'/home/ubuntu/auto/keystonercv3' is outside repository" comes from. This looks
like something Fuel is complaining about.
5. "internal endpoint for nfv-orchestration service in RegionOne region not
found" is a bug, but one due to a persistent problem with OPNFV ... in that the
different distros use inconsistent naming for key common attributes such as the
region name. In Apex, this is "regionOne" and the case difference matters. But
I will try to find a way for the test to be more intelligent, i.e. discover the
actual value and use it. I've done this in the past, I just need to recall
where and how.
For reference, For Apex the whole test process including the following is
posted at
https://etherpad.opnfv.org/p/bryan-models<https://urldefense.proofpoint.com/v2/url?u=https-3A__clicktime.symantec.com_a_1_6UGdJuMDs3ZtcP265Cb9jSJD9hicAroB-5FPKznP65bjk-3D-3Fd-3DRUYeklrPVwVzZE5eiA5cg3dR4EYyLEGe2F-5F8lh-5F2kzeC5uCLQj9r7PM10v7jkOTnDcm6ECMCqMeWqJ1RQrrGBFi51-2D-5FdJeN0nn1K01wo6IXxU1MwTcJzgrZKLKSe9-2Dw6m471SIQlS0JwMYX18HBJaKwUBKDT41N7aEaD-2D2GWzOiMGohQIfgWJ-5FZcMdpUPDzbW-2DpJYpJJdKt7RTLJWGQ-2DC9UjdF03zvxqPmDOh8t0ZcYy9EeQ-2DOIdhFQg-5FWFKMqz0-5FO54TYg4-2DVxZVycFnxKLnbx70svqhg-5FWcIGsN1Ih1Lg7LOrVFT4A5ehNSWBmx6kz9sQRCpJ-5F-2DhwYhARmU6kW8Rkqp3nlg5DfnJWsZ4jEajEVQX8qVMYAPbqC9odOgnO6gidOuoWuJhPW00lcHu-5FyBP7hviQNUjqLbwf7MxV8llE12XUZqqj3WFBgEJXS-26u-3Dhttps-253A-252F-252Fetherpad.opnfv.org-252Fp-252Fbryan-2Dmodels&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=iDExEl-ilkVzCpkvtfMQmWqql4dCX4h0UZeZO2g2E2s&s=WsBypVD8npaUeML3GLIUUWfcfyQXuCxTa0hN1sZ7lxA&e=>:
* Test setup
* Tacker container logs
* Test start
* Output of CLI calls for openstack user, endpoint, and service
* Test stop
* Test clean
* Output of CLI calls for openstack user, endpoint, and service (verifying
cleanup)
Note you will still see some reports of "Neutron CLI is deprecated...." Since
it's taking time to convert all the CLI calls to use the openstack client. But
they work.
Thanks,
Bryan Sullivan | AT&T
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]]
Sent: Tuesday, January 09, 2018 12:43 PM
To: SULLIVAN, BRYAN L (BRYAN L)
<[email protected]<mailto:[email protected]>>; Tina
Tsou <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>; UKASICK, AIMEE L (AIMEE L)
<[email protected]<mailto:[email protected]>>
Cc: '[email protected]'
<[email protected]<mailto:[email protected]>>
Subject: RE: [Models][Auto] vHello_Tacker updated for Euphrates
Thanks Bryan for the changes.
I tried the latest Models Project in ARM Pod (with OPNFV) and found that the
setup for vHello_Tacker.sh indicates that it succeeded, but the session logs
(as attached) show some issues. I did not see the logic to create an endpoint
nfv-orchestration anymore. The subsequent vHello_Tacker.sh start execution
fails to find this endpoint during "tacker vnf-create" processing. Is this
endpoint not needed anymore with this change ? The logs are given below.
The docker status also shows as exited.
(venv) ubuntu@localhost:/opt/tacker$ sudo docker ps -a
CONTAINER ID IMAGE COMMAND
CREATED STATUS PORTS NAMES
982486b7290c blsaws/models-tacker:latest "/bin/bash /opt/ta..."
About an hour ago Exited (1) About an hour ago tacker
~/auto/models/tests$ ./vHello_Tacker.sh setup /home/ubuntu/auto/keystonercv3
setup:165 (Tue Jan 9 18:28:11 UTC 2018) run tacker-setup.sh
...snip...
create_container:99 (Tue Jan 9 18:28:23 UTC 2018) Start tacker container with
image blsaws/models-tacker:latest
Missing parameter(s):
Set a username with --os-username, OS_USERNAME, or auth.username
Set an authentication URL, with --os-auth-url, OS_AUTH_URL or auth.auth_url
Set a scope, such as a project or domain, set a project scope with
--os-project-name, OS_PROJECT_NAME or auth.project_name, set a domain scope
with --os-domain-name, OS_DOMAIN_NAME or auth.domain_name
982486b7290c9338979d216dbb8b285431f275028754e75605dbef160501a21e
pass:40 (Tue Jan 9 18:28:26 UTC 2018) Hooray!
...snip...
Create virtualenv
New python executable in /home/ubuntu/venv/bin/python
..snip...
fatal: /home/ubuntu/auto/keystonercv3: '/home/ubuntu/auto/keystonercv3' is
outside repository
...snip..
setup:232 (Tue Jan 9 18:32:25 UTC 2018) Add router interface for vnf_private
network
neutron CLI is deprecated and will be removed in the future. Use openstack CLI
instead.
Added interface f2a6a8b3-bb70-4587-958b-3903629973b9 to router
vnf_private_router.
pass:100 (Tue Jan 9 18:32:38 UTC 2018) Hooray!
pass:103 (Tue Jan 9 18:32:38 UTC 2018) Test Duration = 267 seconds
ubuntu@localhost: ~/auto/models/testsubuntu@localhost:~/auto/models/tests$
source ~/venv/bin/activate
(venv) ]0;ubuntu@localhost:
~/auto/models/testsubuntu@localhost:~/auto/models/tests$ bash vHello_Tacker.sh
start
copy_blueprint:238 (Tue Jan 9 18:43:11 UTC 2018) copy test script to
/opt/tacker
copy_blueprint:241 (Tue Jan 9 18:43:11 UTC 2018) reset blueprints folder
copy_blueprint:247 (Tue Jan 9 18:43:11 UTC 2018) copy
tosca-vnfd-hello-world-tacker to blueprints folder
start:255 (Tue Jan 9 18:43:11 UTC 2018) setup OpenStack CLI environment
start:258 (Tue Jan 9 18:43:11 UTC 2018) Create Nova key pair
Generating public/private rsa key pair.
Your identification has been saved in /opt/tacker/vHello.
Your public key has been saved in /opt/tacker/vHello.pub.
The key fingerprint is:
SHA256:Dsb4XhltfFrri54PGHy94bCmuyPd9v+iiiP7dw6sBPM ubuntu@vHello
The key's randomart image is:
+---[RSA 2048]----+
| |
| |
| |
| o . o . |
| . * S * = |
| o * O B + |
| ..E.B + |
| .oo+=+*. . |
| o=BO=*B+.o.|
+----[SHA256]-----+
Key pair 'vHello' already exists. (HTTP 409) (Request-ID:
req-d86d9a31-5f6a-41a9-aa56-3ee9f80b51c6)
vHello_Tacker.sh test assertion passed: models-nova-001 (Keypair creation)
start:265 (Tue Jan 9 18:43:16 UTC 2018) Inject public key into blueprint
start:269 (Tue Jan 9 18:43:16 UTC 2018) Get external network for Floating IP
allocations
neutron CLI is deprecated and will be removed in the future. Use openstack CLI
instead.
neutron CLI is deprecated and will be removed in the future. Use openstack CLI
instead.
neutron CLI is deprecated and will be removed in the future. Use openstack CLI
instead.
neutron CLI is deprecated and will be removed in the future. Use openstack CLI
instead.
neutron CLI is deprecated and will be removed in the future. Use openstack CLI
instead.
neutron CLI is deprecated and will be removed in the future. Use openstack CLI
instead.
start:272 (Tue Jan 9 18:43:40 UTC 2018) create VNFD
internal endpoint for nfv-orchestration service in RegionOne region not found
vHello_Tacker.sh test assertion failed: models-tacker-002 (VNFD creation)
fail:108 (Tue Jan 9 18:43:43 UTC 2018) Test Failed!
fail:112 (Tue Jan 9 18:43:43 UTC 2018) Test Duration = 0 seconds
(venv) ]0;ubuntu@localhost:
~/auto/models/testsubuntu@localhost:~/auto/models/tests$
Regards,
Pramod
From: SULLIVAN, BRYAN L (BRYAN L) [mailto:[email protected]]
Sent: Tuesday, January 9, 2018 11:50 AM
To: Pramod Sudrik (Product Engineering Service)
<[email protected]<mailto:[email protected]>>; Tina Tsou
<[email protected]<mailto:[email protected]>>; Eric DMaye (Product Engineering
Service) <[email protected]<mailto:[email protected]>>; UKASICK, AIMEE L
(AIMEE L) <[email protected]<mailto:[email protected]>>
Cc: '[email protected]'
<[email protected]<mailto:[email protected]>>
Subject: [Models][Auto] vHello_Tacker updated for Euphrates
** This mail has been sent from an external source **
Pramod,
Bringing this offline discussion to the list...
The Models vHello_Tacker test is now updated/merged and working for Euphrates
(verified for Apex virtual install). There were a variety of API/CLI and other
changes in OpenStack Ocata, and I took the opportunity to refactor the test. It
now uses a docker container for Tacker, that is pre-built and downloaded from
docker hub
(https://hub.docker.com/r/blsaws/models-tacker/<https://urldefense.proofpoint.com/v2/url?u=https-3A__clicktime.symantec.com_a_1_5Ui1GdbStcFBk6r-5FUcMl2tYQ3sv2ja8Et4-5FE6gRSlPQ-3D-3Fd-3DF9CfajAIt2tbfL3WjZEEFxlMY6SVKR9HdFdALf7d-5FdCoG0fk5UyxEclqkQT29RVRqQgjFwg1EpdQToEZ3UnZpNuPH67h9aeZ-2D5zSpBhP01-2DBU6HfFxczUtU98-5F6zAeGa4eIym5ZMzGag4Z2xOEgz0cuiTFNIgSPS4-2DIMVZMnELTdYg6Wkdzo331nMTG5c0V-5FgdG-5F2iSFoSTClRlG-2Dh7X83KHeGR1qRsqRBpwjRjNvxv-2DvjTfOBL1fLQlEqU9rwUJPCPaL3eYwukjGAsz6HASvA1txLMR2dHIKW2lv53YEW9WUgAsa3b9qK72a8BAd4uTiR5jsFqvDbn8XGRRpNdHIR0ipmyn5GNzbnZkiPe5qb1-2DENlwbYsmEjtCIldMEHhKOeBVeAZuM5pupFwnA3wyyoXfzTnbH-5FU3wotge0v3Zpn6ye4YpkvvzLNszA-253D-253D-26u-3Dhttps-253A-252F-252Fhub.docker.com-252Fr-252Fblsaws-252Fmodels-2Dtacker-252F&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=GJwswiiioBemmeNmoAwEzUieaV0jk3YipB9SinJqQfc&s=c_ky8T4Pb37dk_OKgW4EcqXZvV_eSAvovBQP19FHg7c&e=>).
The test overall runs much faster. The comments at the start of the script
describe the updated process. The main difference is that the OpenStack
commands require activation of a virtual env that is installed in the setup
step.
Thanks,
Bryan Sullivan | AT&T
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit
http://www.symanteccloud.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.symanteccloud.com&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=GJwswiiioBemmeNmoAwEzUieaV0jk3YipB9SinJqQfc&s=D908OLI1rWKHIEh1ki1ztXiTwT0NoiE6_a7Su6u20wE&e=>
______________________________________________________________________
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary, confidential or privileged information. If you are not the
intended recipient, you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately and destroy all copies of this message and
any attachments. WARNING: Computer viruses can be transmitted via email. The
recipient should check this email and any attachments for the presence of
viruses. The company accepts no liability for any damage caused by any virus
transmitted by this email.
www.wipro.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.wipro.com&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=GJwswiiioBemmeNmoAwEzUieaV0jk3YipB9SinJqQfc&s=paZ-Nl1yUBV83w_SOxfQqC0cjVolyj3dnC86NtppGv0&e=>
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit
http://www.symanteccloud.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.symanteccloud.com&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=GJwswiiioBemmeNmoAwEzUieaV0jk3YipB9SinJqQfc&s=D908OLI1rWKHIEh1ki1ztXiTwT0NoiE6_a7Su6u20wE&e=>
______________________________________________________________________
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit
http://www.symanteccloud.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.symanteccloud.com&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=iDExEl-ilkVzCpkvtfMQmWqql4dCX4h0UZeZO2g2E2s&s=A6HcULIg7lhhTYEcsOaffzQn-V310rmmqZcVPXlTXwU&e=>
______________________________________________________________________
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary, confidential or privileged information. If you are not the
intended recipient, you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately and destroy all copies of this message and
any attachments. WARNING: Computer viruses can be transmitted via email. The
recipient should check this email and any attachments for the presence of
viruses. The company accepts no liability for any damage caused by any virus
transmitted by this email.
www.wipro.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.wipro.com&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=iDExEl-ilkVzCpkvtfMQmWqql4dCX4h0UZeZO2g2E2s&s=6Xy3cWHMl1WVqEuHce0RytlZrDvOT2IpxQ3Bu-eHPZw&e=>
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit
http://www.symanteccloud.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.symanteccloud.com&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=iDExEl-ilkVzCpkvtfMQmWqql4dCX4h0UZeZO2g2E2s&s=A6HcULIg7lhhTYEcsOaffzQn-V310rmmqZcVPXlTXwU&e=>
______________________________________________________________________
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit
http://www.symanteccloud.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.symanteccloud.com&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=LziGvWKWfpDSxEcmkC8XcJwgqCg0TyKTCQWLSJhUYXw&s=r6ovYCgPzYbWvtOLZvyOYfK_XEI0is6pkAwtUiPkP_4&e=>
______________________________________________________________________
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary, confidential or privileged information. If you are not the
intended recipient, you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately and destroy all copies of this message and
any attachments. WARNING: Computer viruses can be transmitted via email. The
recipient should check this email and any attachments for the presence of
viruses. The company accepts no liability for any damage caused by any virus
transmitted by this email.
www.wipro.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.wipro.com&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=LziGvWKWfpDSxEcmkC8XcJwgqCg0TyKTCQWLSJhUYXw&s=4zaQBS93Z5OyUj2oQkTYHPG5fmrfBTRUT_OZbmprhh8&e=>
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit
http://www.symanteccloud.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.symanteccloud.com&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=ML-JPRZQOfToJjMwlJLPlcWimAEwMA5DZGNIrk-cgy0&m=LziGvWKWfpDSxEcmkC8XcJwgqCg0TyKTCQWLSJhUYXw&s=r6ovYCgPzYbWvtOLZvyOYfK_XEI0is6pkAwtUiPkP_4&e=>
______________________________________________________________________
_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
