Re: [opnfv-tech-discuss] [release][euphrates] Milestone 3.2 - installers deploy scenario withintegrated SDN and pass health check

2017-07-14 Thread hu.zhijiang
Hi David,




There are the results for Daisy




latest result for Bare Metal

os-odl_l3-nofeature-ha scenario (passed healthcheck)


https://build.opnfv.org/ci/job/functest-daisy-baremetal-daily-master/14/console




latest result for Virtual

os-odl_l3-nofeature-ha scenario (passed healthcheck)


https://build.opnfv.org/ci/job/functest-daisy-virtual-daily-master/117/console





B. R.,

Zhijiang






原始邮件



发件人: 
收件人:
  
 胡智江10080967 

抄送人:   

日 期 :2017年07月10日 23:49
主 题 :[release][euphrates] Milestone 3.2 - installers deploy scenario 
withintegrated SDN and pass health check






Installer teams,
Milestone 3.2 is scheduled for tomorrow, July 11.  Please provide the following:
Identify a scenario that includes an integrated SDN controller that 
demonstrates that your installer meets the requirements of MS3.2.

Provide a pointer to test results that demonstrate that health check passes for 
the identified scenario.


David

-- 




David McBride
Release Manager, OPNFV

Mobile: +1.805.276.8018

Email/Google Talk: dmcbr...@linuxfoundation.org

Skype: davidjmcbride1

IRC: dmcbride___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


[opnfv-tech-discuss] [OPNFV Helpdesk #43045] RE: [barometer] I would like to contribute to the PROJECT

2017-07-14 Thread Trevor Bramwell via RT
Hi Maryam,

I've sent an invite to Emma.

Hi Emma,

I have sent you an invite to join the Barometer contributors group. This will 
prompt you to create a Linux Foundation account if you don't already have one.
Please choose a username without spaces or special characters as Gerrit
requires a valid unix username. You will also need to sign the
individual CLA[1] and upload an ssh key in Gerrit[2] before you can push code.

Don't hesitate to get in touch (helpd...@opnfv.org) if you have any further
questions.

Welcome to OPNFV and thanks for contributing to barometer!

Regards,
Trevor Bramwell

[1] https://gerrit.opnfv.org/gerrit/#/settings/agreements
[2] https://gerrit.opnfv.org/gerrit/#/settings/ssh-keys

On Fri Jul 14 03:57:29 2017, maryam.tah...@intel.com wrote:
> Hi Aric
> Can you please give Emma Permissions to contribute to barometer?
> 
> Thanks
>  Maryam
> 
> > -Original Message-
> > From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-
> > discuss-
> > boun...@lists.opnfv.org] On Behalf Of Foley, Emma L
> > Sent: Friday, July 14, 2017 10:55 AM
> > To: opnfv-tech-discuss@lists.opnfv.org
> > Subject: [opnfv-tech-discuss] [barometer] I would like to contribute
> > to the
> > PROJECT
> >
> >
> > ___
> > opnfv-tech-discuss mailing list
> > opnfv-tech-discuss@lists.opnfv.org
> > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss



___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


[opnfv-tech-discuss] FW: Fuel and Armband Fuel Danube 3.0 ISOs

2017-07-14 Thread Alexandru Avadanii
Hi,
Fuel and Armband projects are pleased to announce the public release of Danube 
3.0.

1. Fuel artifacts
Git tag at [1], ISO build logs [3], ISO [5], documentation [7, 8, 9].

2. Armband artifacts
Git tag at [2], ISO build logs [4], ISO [6], documentation [10, 11, 12].

BR,
Alex

[1] https://git.opnfv.org/fuel/tag/?h=danube.3.0
[2] https://git.opnfv.org/armband/tag/?h=danube.3.0
[3] https://build.opnfv.org/ci/view/fuel/job/fuel-build-daily-danube/738/console
[4] 
https://build.opnfv.org/ci/view/armband/job/armband-fuel-build-daily-danube/28/console
[5] http://artifacts.opnfv.org/fuel/danube/opnfv-2017-07-14_14-00-12.iso
[6] http://artifacts.opnfv.org/armband/danube/opnfv-2017-07-14_13-43-04.iso
[7] 
http://docs.opnfv.org/en/stable-danube/submodules/fuel/docs/development/overview/build/build.instruction.html
[8] 
http://docs.opnfv.org/en/stable-danube/submodules/fuel/docs/release/release-notes/release-notes.html
[9] 
http://docs.opnfv.org/en/stable-danube/submodules/fuel/docs/release/installation/installation.instruction.html
[10] 
http://docs.opnfv.org/en/stable-danube/submodules/armband/docs/development/overview/build/build.instruction.html
[11] 
http://docs.opnfv.org/en/stable-danube/submodules/armband/docs/release/release-notes/release-notes.html
[12] 
http://docs.opnfv.org/en/stable-danube/submodules/armband/docs/release/installation/installation.instruction.html
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] [release][danube] Danube 3 release on July 14

2017-07-14 Thread David McBride
If you haven't already done so, please tag your repo by the end of the day
(5 p.m. Pacific).  Tagging instructions here
.

David

On Wed, Jul 12, 2017 at 10:27 AM, David McBride <
dmcbr...@linuxfoundation.org> wrote:

> Reminder - testing should be complete today, followed by documentation and
> JIRA updates tomorrow.  Let me know if you have questions.
>
> David
>
> On Mon, Jul 10, 2017 at 5:27 PM, David McBride <
> dmcbr...@linuxfoundation.org> wrote:
>
>> Reminder...
>>
>> On Thu, Jul 6, 2017 at 5:20 PM, David McBride <
>> dmcbr...@linuxfoundation.org> wrote:
>>
>>> Reminder... as approved by the TSC last week, Danube 3 will be released
>>> 1 week from tomorrow on July 14.  The schedule is as follows:
>>>
>>>- July 12 - complete testing
>>>- July 13 - finish document updates / update JIRA
>>>- July 14 - tag repos and release
>>>- Week of July 17 - download page goes live
>>>
>>> Let me know if you have questions.
>>>
>>> David
>>>
>>> --
>>> *David McBride*
>>> Release Manager, OPNFV
>>> Mobile: +1.805.276.8018
>>> Email/Google Talk: dmcbr...@linuxfoundation.org
>>> Skype: davidjmcbride1
>>> IRC: dmcbride
>>>
>>
>>
>>
>> --
>> *David McBride*
>> Release Manager, OPNFV
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> Skype: davidjmcbride1
>> IRC: dmcbride
>>
>
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>



-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Manuel Buil
Hey Pavan,

Just ssh into the VM or host that is acting as openstack controller and
it should be in the home directory together with openrc

Regards,
Manuel

On Fri, 2017-07-14 at 19:43 +0530, Pavan Gupta wrote:
> > Ok. Not sure Manuel how to get tacker file. Do you have any ideas or
suggestions? I am quite new to openstack in general.Pavan
> > > > On 14-Jul-2017, at 7:35 PM, Manuel Buil  wrote:
> > tackerc file not found, fetching it from controller
> 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Pavan Gupta
Ok. Not sure Manuel how to get tacker file. Do you have any ideas or 
suggestions? I am quite new to openstack in general.
Pavan
> On 14-Jul-2017, at 7:35 PM, Manuel Buil  wrote:
> 
> tackerc file not found, fetching it from controller

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Pavan Gupta
HI Manuel,
Tacker was deployed in the beginning itself. Please check the attached image.  
Is there anything else I need to deploy Tacker?
Pavan


> On 14-Jul-2017, at 7:07 PM, Manuel Buil  wrote:
> 
> Hello Pavan,
> 
> In the logs you sent previously, that step worked but it was not able to 
> fetch tackerc. Did you deploy your environment activating tacker? It should 
> be under settings > openstack services.
> 
> -Manuel
> 
> On Fri, 2017-07-14 at 18:36 +0530, Pavan Gupta wrote:
>> HI Jose,
>> This is sfc.log
>> 
>> 
>> 2017-07-14 12:57:13,258 - SSH utils - ERROR - timed out
>> 2017-07-14 12:58:13,319 - SSH utils - ERROR - timed out
>> 2017-07-14 12:59:13,348 - SSH utils - ERROR - timed out
>> 2017-07-14 13:00:13,405 - SSH utils - ERROR - timed out
>> 2017-07-14 13:00:13,406 - __main__ - INFO - Fetch /etc/heat/heat.conf from 
>> controller 10.192.3.70
>> 2017-07-14 13:00:13,406 - opnfv.deployment.manager - INFO - Fetching 
>> /etc/heat/heat.conf from 10.192.3.70
>> 2017-07-14 13:00:13,406 - SSH utils - ERROR - Error [get_file(ssh_conn, 
>> '/etc/heat/heat.conf', '/tmp/heat.conf']: 'NoneType' object has no attribute 
>> 'open_sftp'
>> 2017-07-14 13:00:13,406 - opnfv.deployment.manager - ERROR - SFTP failed to 
>> retrieve the file.
>> 2017-07-14 13:00:13,407 - __main__ - INFO - Replace /etc/heat/heat.conf with 
>> /tmp/heat.conf in controller 10.192.3.70
>> 10.20.0.2
>> root
>> r00tme
>> None
>> --*-*
>> Installer Connection =  
>> Traceback (most recent call last):
>>   File "./run_tests.py", line 189, in 
>> main(report=args.report)
>>   File "./run_tests.py", line 91, in main
>> disable_heat_resource_finder_cache(nodes)
>>   File "./run_tests.py", line 67, in disable_heat_resource_finder_cache
>> controller.run_cmd('rm -f {0}'.format(remote_heat_conf))
>>   File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line 
>> 184, in run_cmd
>> _, stdout, stderr = (self.ssh_client.exec_command(cmd))
>> AttributeError: 'NoneType' object has no attribute ‘exec_command'
>> 
>> 
>> Pavan
>> 
>> 
>>> On 14-Jul-2017, at 6:32 PM, Jose Lausuch >> > wrote:
>>> 
>>> Hi,
>>> 
>>> Functest looks fine. Can you now attach sfc.log located in the same 
>>> directory? Maybe it’s a problem with the test case as such while trying to 
>>> access the deployment. Maybe Manuel has more experience with it.
>>> 
>>> - Jose -
>>> 
>>> 
 On 14 Jul 2017, at 14:47, Pavan Gupta >>> > wrote:
 
 HI Jose,
 - I have attached the log file this time.
 
 - Output of docker images:
 
 REPOSITORY  TAG IMAGE ID
 CREATED SIZE
 opnfv/functest  stable  2553087919e09 days 
 ago  1.57GB
 ryu7249125/yardsticklatest  e37ee4c07ca82 
 months ago3.52GB
 opnfv/yardstick stable  7fc31a6fc1d52 
 months ago1.2GB
 autolytiks_logstash latest  0b8f850cf5922 
 months ago565MB
 autolytiks_elasticsearchlatest  f73bc006eb572 
 months ago352MB
 autolytiks_nginxlatest  b3d688b354172 
 months ago206MB
 autolytiks_web  latest  7c2907bd15d82 
 months ago727MB
 python  3.5-onbuild 2d1685b88f322 
 months ago689MB
 redis   latest  e32ef7250bc12 
 months ago184MB
 postgreslatest  3902208677552 
 months ago267MB
 influxdblatest  95b868946bae2 
 months ago224MB
 logstash5.2 e2e0c054df393 
 months ago494MB
 elasticsearch   5.2 0206b7302cfe3 
 months ago352MB
 grafana/grafana latest  8c4ef64b4ad13 
 months ago278MB
 autolytiks_kibana   latest  724639b709153 
 months ago329MB
 kibana  5.2 724639b709153 
 months ago329MB
 hello-world latest  c54a2cc56cbb12 
 months ago   1.85kB
 opennetworklinux/builder7   1.2 a0a471ea8d5513 
 months ago   1.92GB
 tutum/nginx latest  a2e9b71ed36616 
 months ago   206MB
 
 
 - Output of docker ps:
 CONTAINER IDIMAGECOMMAND  
 CREATED STATUS  PORTS  
  

Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Pavan Gupta
HI Jose,
This is sfc.log


2017-07-14 12:57:13,258 - SSH utils - ERROR - timed out
2017-07-14 12:58:13,319 - SSH utils - ERROR - timed out
2017-07-14 12:59:13,348 - SSH utils - ERROR - timed out
2017-07-14 13:00:13,405 - SSH utils - ERROR - timed out
2017-07-14 13:00:13,406 - __main__ - INFO - Fetch /etc/heat/heat.conf from 
controller 10.192.3.70
2017-07-14 13:00:13,406 - opnfv.deployment.manager - INFO - Fetching 
/etc/heat/heat.conf from 10.192.3.70
2017-07-14 13:00:13,406 - SSH utils - ERROR - Error [get_file(ssh_conn, 
'/etc/heat/heat.conf', '/tmp/heat.conf']: 'NoneType' object has no attribute 
'open_sftp'
2017-07-14 13:00:13,406 - opnfv.deployment.manager - ERROR - SFTP failed to 
retrieve the file.
2017-07-14 13:00:13,407 - __main__ - INFO - Replace /etc/heat/heat.conf with 
/tmp/heat.conf in controller 10.192.3.70
10.20.0.2
root
r00tme
None
--*-*
Installer Connection =  
Traceback (most recent call last):
  File "./run_tests.py", line 189, in 
main(report=args.report)
  File "./run_tests.py", line 91, in main
disable_heat_resource_finder_cache(nodes)
  File "./run_tests.py", line 67, in disable_heat_resource_finder_cache
controller.run_cmd('rm -f {0}'.format(remote_heat_conf))
  File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line 
184, in run_cmd
_, stdout, stderr = (self.ssh_client.exec_command(cmd))
AttributeError: 'NoneType' object has no attribute ‘exec_command'


Pavan


> On 14-Jul-2017, at 6:32 PM, Jose Lausuch  wrote:
> 
> Hi,
> 
> Functest looks fine. Can you now attach sfc.log located in the same 
> directory? Maybe it’s a problem with the test case as such while trying to 
> access the deployment. Maybe Manuel has more experience with it.
> 
> - Jose -
> 
> 
>> On 14 Jul 2017, at 14:47, Pavan Gupta > > wrote:
>> 
>> HI Jose,
>> - I have attached the log file this time.
>> 
>> - Output of docker images:
>> 
>> REPOSITORY  TAG IMAGE IDCREATED  
>>SIZE
>> opnfv/functest  stable  2553087919e09 days 
>> ago  1.57GB
>> ryu7249125/yardsticklatest  e37ee4c07ca82 months 
>> ago3.52GB
>> opnfv/yardstick stable  7fc31a6fc1d52 months 
>> ago1.2GB
>> autolytiks_logstash latest  0b8f850cf5922 months 
>> ago565MB
>> autolytiks_elasticsearchlatest  f73bc006eb572 months 
>> ago352MB
>> autolytiks_nginxlatest  b3d688b354172 months 
>> ago206MB
>> autolytiks_web  latest  7c2907bd15d82 months 
>> ago727MB
>> python  3.5-onbuild 2d1685b88f322 months 
>> ago689MB
>> redis   latest  e32ef7250bc12 months 
>> ago184MB
>> postgreslatest  3902208677552 months 
>> ago267MB
>> influxdblatest  95b868946bae2 months 
>> ago224MB
>> logstash5.2 e2e0c054df393 months 
>> ago494MB
>> elasticsearch   5.2 0206b7302cfe3 months 
>> ago352MB
>> grafana/grafana latest  8c4ef64b4ad13 months 
>> ago278MB
>> autolytiks_kibana   latest  724639b709153 months 
>> ago329MB
>> kibana  5.2 724639b709153 months 
>> ago329MB
>> hello-world latest  c54a2cc56cbb12 
>> months ago   1.85kB
>> opennetworklinux/builder7   1.2 a0a471ea8d5513 
>> months ago   1.92GB
>> tutum/nginx latest  a2e9b71ed36616 
>> months ago   206MB
>> 
>> 
>> - Output of docker ps:
>> CONTAINER IDIMAGECOMMAND  
>> CREATED STATUS  PORTS
>> NAMES
>> 9b1c47899d65opnfv/functest:stable"/bin/bash"  6 
>> hours ago Up 6 hours 
>>   sfc
>> 0eb2d3ff7e4dautolytiks_nginx "/usr/sbin/nginx"2 
>> months agoUp 8 days   0.0.0.0:80->80/tcp 
>>   autolytiks_nginx_1
>> ce4e265af4cdgrafana/grafana:latest   "/run.sh"2 
>> months agoUp 8 days   0.0.0.0:3000->3000/tcp 
>>   autolytiks_grafana_1
>> 87e2e67d8924autolytiks_web   "/usr/local/bin/gu..."   2 
>> months agoUp 8 days   8000/tcp

Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Pavan Gupta
Hi Jose,
1. I have attached functest.log.

2. Docker image: Docker version 17.04.0-ce, build 4845c56

3. Installer: Fuel, version 10.0.0

4. Credentials: Same as mentioned in the link (root, r00tme)

Thank you.
Pavan

> On 14-Jul-2017, at 5:15 PM, Jose Lausuch  wrote:
> 
> /home/opnfv/functest/results/functest.log 

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Pavan Gupta
Hi Manuel,
- I am using funkiest command list. I run this command: 'functest testcase run 
odl-sfc’

- I am new openstack as well, can you please tell me, what all env variables 
need to be set. Do I need to copy these in openstack.creds. This is what is 
there at present in this file:
OS_REGION_NAME=RegionOne
OS_DEFAULT_DOMAIN=default
OS_USER_DOMAIN_NAME=Default
OS_PROJECT_NAME=admin
OS_IDENTITY_API_VERSION=3
OS_PASSWORD=admin
OS_AUTH_STRATEGY=keystone
OS_AUTH_URL=http://192.168.0.2:5000/ 
OS_USERNAME=admin
OS_TENANT_NAME=admin
OS_ENDPOINT_TYPE=internalURL
OS_NO_CACHE=true
OS_PROJECT_DOMAIN_NAME=Default

- Where do I run ‘openstack server list’ command. I tried running it on node-1 
machine, which is a controller machine, the output was blank.

Any useful pointer would be appreciated.
Pavan
- 
> On 14-Jul-2017, at 4:49 PM, Manuel Buil  wrote:
> 
> HI Pavan,
> 
> I think your openstack env. variables are not set. How do you execute the 
> tests?
> 
> If you are not using the functest command line, you need to source the env 
> variables (from openrc or tackerc). To check that everything is ok, try to 
> execute one openstack command before executing the test and check that you 
> don't get any error (e.g. openstack server list).
> 
> Regards,
> Manuel
> 
> On Fri, 2017-07-14 at 16:40 +0530, Pavan Gupta wrote:
>> Hello Folks,
>> I have managed to begin the test but hit across this error:
>> 
>> Traceback (most recent call last):
>>   File "./run_tests.py", line 189, in 
>> main(report=args.report)
>>   File "./run_tests.py", line 91, in main
>> disable_heat_resource_finder_cache(nodes)
>>   File "./run_tests.py", line 67, in disable_heat_resource_finder_cache
>> controller.run_cmd('rm -f {0}'.format(remote_heat_conf))
>>   File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line 
>> 184, in run_cmd
>> _, stdout, stderr = (self.ssh_client.exec_command(cmd))
>> AttributeError: 'NoneType' object has no attribute ‘exec_command'
>> 
>> 
>> Does anyone know fix for this?
>> Pavan
>> 
>>> On 14-Jul-2017, at 12:56 PM, Jose Lausuch >> > wrote:
>>> 
>>> Ok, just for your information: 
>>> if you are using Functest Danube, you need connectivity to the admin 
>>> network. We are working on removing that constraint in Euphrates against 
>>> OpenStack Ocata.
>>> 
>>> Thanks,
>>> Jose
>>> 
>>> 
>>> 
 On 14 Jul 2017, at 08:45, Pavan Gupta >>> > wrote:
 
 Hi Jose,
 I added the following route on Junper host and connectivity worked, so the 
 SFC test environment was successfully prepared.
 sudo route add -net 192.168.0.0 netmask 255.255.255.0 gw 172.26.48.23
 
 Thanks for your help.
 Pavan
 
> On 13-Jul-2017, at 7:06 PM, Jose Lausuch  > wrote:
> 
> Hi Pavan,
>  
> It seems your installer is not supported by the script fetch_os_creds.sh
>  
> In that case, you need to provide the openstack RC file from your 
> deployment manually to the container, or just copy the content to  
> /home/opnfv/functest/conf/openstack.creds
>  
> Let me know if it still fails that way.
>  
> Regards,
> Jose
>  
>  
> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
>  
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org 
> ] On Behalf Of Pavan 
> Gupta
> Sent: Thursday, July 13, 2017 14:29 PM
> To: Manuel Buil mailto:mb...@suse.com>>
> Cc: andres.sanchez.ra...@estudiant.upc.edu 
> ; OPNFV-TECH-DISCUSS OPNFV 
>  >
> Subject: Re: [opnfv-tech-discuss] SFC Project
>  
> Hi Manuel/Andres,
> When I run 'functest env prepare’, I also see this issue:
> 
> 
> /home/opnfv/repos/releng/utils/fetch_os_creds.sh: line 76: 
> SALT_MASTER_IP: unbound variable
>  
> What should be SALT_MASTER_IP address?
> Pavan
>  
> On 13-Jul-2017, at 3:37 PM, Manuel Buil  > wrote:
>  
> 10.20.0.2
 
>>> 
>> 

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Pavan Gupta
Hello Folks,
I have managed to begin the test but hit across this error:

Traceback (most recent call last):
  File "./run_tests.py", line 189, in 
main(report=args.report)
  File "./run_tests.py", line 91, in main
disable_heat_resource_finder_cache(nodes)
  File "./run_tests.py", line 67, in disable_heat_resource_finder_cache
controller.run_cmd('rm -f {0}'.format(remote_heat_conf))
  File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line 
184, in run_cmd
_, stdout, stderr = (self.ssh_client.exec_command(cmd))
AttributeError: 'NoneType' object has no attribute ‘exec_command'


Does anyone know fix for this?
Pavan

> On 14-Jul-2017, at 12:56 PM, Jose Lausuch  wrote:
> 
> Ok, just for your information: 
> if you are using Functest Danube, you need connectivity to the admin network. 
> We are working on removing that constraint in Euphrates against OpenStack 
> Ocata.
> 
> Thanks,
> Jose
> 
> 
> 
>> On 14 Jul 2017, at 08:45, Pavan Gupta > > wrote:
>> 
>> Hi Jose,
>> I added the following route on Junper host and connectivity worked, so the 
>> SFC test environment was successfully prepared.
>> sudo route add -net 192.168.0.0 netmask 255.255.255.0 gw 172.26.48.23
>> 
>> Thanks for your help.
>> Pavan
>> 
>>> On 13-Jul-2017, at 7:06 PM, Jose Lausuch >> > wrote:
>>> 
>>> Hi Pavan,
>>>  
>>> It seems your installer is not supported by the script fetch_os_creds.sh
>>>  
>>> In that case, you need to provide the openstack RC file from your 
>>> deployment manually to the container, or just copy the content to  
>>> /home/opnfv/functest/conf/openstack.creds
>>>  
>>> Let me know if it still fails that way.
>>>  
>>> Regards,
>>> Jose
>>>  
>>>  
>>> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
>>>  
>>> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org 
>>> ] On Behalf Of Pavan 
>>> Gupta
>>> Sent: Thursday, July 13, 2017 14:29 PM
>>> To: Manuel Buil mailto:mb...@suse.com>>
>>> Cc: andres.sanchez.ra...@estudiant.upc.edu 
>>> ; OPNFV-TECH-DISCUSS OPNFV 
>>> >> >
>>> Subject: Re: [opnfv-tech-discuss] SFC Project
>>>  
>>> Hi Manuel/Andres,
>>> When I run 'functest env prepare’, I also see this issue:
>>> 
>>> 
>>> /home/opnfv/repos/releng/utils/fetch_os_creds.sh: line 76: SALT_MASTER_IP: 
>>> unbound variable
>>>  
>>> What should be SALT_MASTER_IP address?
>>> Pavan
>>>  
>>> On 13-Jul-2017, at 3:37 PM, Manuel Buil >> > wrote:
>>>  
>>> 10.20.0.2
>> 
> 

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Pavan Gupta
Hi Jose,
- I run the docker within Jumphost machine. 
- I have put the following content in openstack.creds file:
OS_REGION_NAME=RegionOne
OS_DEFAULT_DOMAIN=default
OS_USER_DOMAIN_NAME=Default
OS_PROJECT_NAME=admin
OS_IDENTITY_API_VERSION=3
OS_PASSWORD=admin
OS_AUTH_STRATEGY=keystone
OS_AUTH_URL=http://192.168.0.2:5000/
OS_USERNAME=admin
OS_TENANT_NAME=admin
OS_ENDPOINT_TYPE=internalURL
OS_NO_CACHE=true
OS_PROJECT_DOMAIN_NAME=Default
- IP address 192.168.0.2 isn’t accessible for the docker and the Jumphost. If I 
give public IP address, then the connectivity works. Is it possible to use 
public ip addresses and get the test going?
Pavan

> On 13-Jul-2017, at 7:06 PM, Jose Lausuch  wrote:
> 
> /home/opnfv/functest/conf/openstack.creds

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Pavan Gupta
Hi Jose,
I added the following route on Junper host and connectivity worked, so the SFC 
test environment was successfully prepared.
sudo route add -net 192.168.0.0 netmask 255.255.255.0 gw 172.26.48.23

Thanks for your help.
Pavan

> On 13-Jul-2017, at 7:06 PM, Jose Lausuch  wrote:
> 
> Hi Pavan,
>  
> It seems your installer is not supported by the script fetch_os_creds.sh
>  
> In that case, you need to provide the openstack RC file from your deployment 
> manually to the container, or just copy the content to  
> /home/opnfv/functest/conf/openstack.creds
>  
> Let me know if it still fails that way.
>  
> Regards,
> Jose
>  
>  
> From: opnfv-tech-discuss-boun...@lists.opnfv.org 
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Pavan Gupta
> Sent: Thursday, July 13, 2017 14:29 PM
> To: Manuel Buil 
> Cc: andres.sanchez.ra...@estudiant.upc.edu; OPNFV-TECH-DISCUSS OPNFV 
> 
> Subject: Re: [opnfv-tech-discuss] SFC Project
>  
> Hi Manuel/Andres,
> When I run 'functest env prepare’, I also see this issue:
> 
> 
> /home/opnfv/repos/releng/utils/fetch_os_creds.sh: line 76: SALT_MASTER_IP: 
> unbound variable
>  
> What should be SALT_MASTER_IP address?
> Pavan
>  
> On 13-Jul-2017, at 3:37 PM, Manuel Buil  > wrote:
>  
> 10.20.0.2

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-14 Thread Jose Lausuch
Hi Alec,
Sounds good. We can talk about that during the meeting. Thanks for proposing it.
Jose

-Original Message-
From: Alec Hothan (ahothan) [mailto:ahot...@cisco.com] 
Sent: Friday, July 14, 2017 16:53 PM
To: Jose Lausuch 
Cc: Morgan Richomme ; Mark Beierl 
; opnfv-tech-discuss@lists.opnfv.org; 
test...@lists.opnfv.org; Fatih Degirmenci 
Subject: Re: [test-wg] docker container versioning

Hi Jose,

I have moved this topic and added a sub-agenda to the July 27 test-wg weekly 
meeting agenda 
(https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting)
It is good that this issue has not caused any big problem yet for container 
owners (likely because none of the artifacts has been widely deployed outside 
of OPNFV labs yet) but I’d like to recommend to address it very quickly. 
Fatih has noted rightly that this is actually a larger scope issue (extending 
to all other artifacts: VM images, doc, rpms). It is good to see the larger 
picture but I’d like to avoid making it too complex and start with container 
images with adoption of simple industry best practice versioning.

Thanks

   Alec




On 7/13/17, 8:43 AM, "Jose Lausuch"  wrote:

Hi Alec,

The versioning is not an urgent matter and it is working well today.  I 
agree it is a topic to be discussed but maybe it is better to wait until 
everyone is back from PTO as it will be difficult to align without the 
participation of the people who are really involved.

- Jose -




> On 13 Jul 2017, at 17:00, Alec Hothan (ahothan)  wrote:
> 
> Jose,
> 
> You should start the discussion at the next infra wg meeting (I’ll be on 
PTO whole of next week). I think if the issue can be raised and acknowledged it 
will already be a good step.
> I will just note that:
> - this has to be a joint work by both infra and project teams
> - perhaps we could use some help from OPNFV members who do 
packaging/versioning for a living ;-) (e.g. Linux distro vendors
> 
> To clarify, I’m willing to help on the container/VM image/docs 
workflow/versioning since my project produces those. Not so much on the other 
artifacts such as RPM (which might be more complex).
> I’m not familiar enough with OPNFV to know who works on what, I was 
hoping to get more active feedback from at least the main/most active OPNFV 
container owners. The current versioning is clearly insufficient and I’d like 
to get the input from projects that have been publishing containers for a while.
> 
> Can anybody describe quickly how specs are usually being 
discussed/redacted by working groups? Email is usually not the best (written) 
format. OpenStack uses etherpads or text files that are reviewed through gerrit.
> 
> Thanks
> 
>  Alec
> 
> 
> On 7/12/17, 11:35 PM, "Jose Lausuch"  wrote:
> 
>Hi,
> 
>Is there time to discuss this during the next infra wg meeting on 
Monday? Although the test projects are the main ones using docker containers, 
we are talking about versioning here, which I believe is topic the Infra team 
should address.
> 
>I also would like to add to the agenda:
>  -  decision on where to host the docker build scripts (common one or 
project´s repo?). It has been proposed but not decided.
> 
>Thanks,
>Jose
> 
> 
> 
>> On 12 Jul 2017, at 20:10, Alec Hothan (ahothan)  
wrote:
>> 
>> July/August is tricky with PTOs.
>> Perhaps we should start the discussion by email on this mailer and 
discuss about it in 2 weeks at the test-wg meeting? 
>> Do you guys usually use a text document reviewed with gerrit to 
discuss/collaborate on a spec? Or any other method? Please let me know and I 
can get a head start on this.
>> 
>> Thanks
>> 
>> Alec
>> 
>> On 7/12/17, 8:54 AM, "morgan.richo...@orange.com" 
 wrote:
>> 
>>   I will be in PTO too :)
>> 
>>   Unfortunately the weekly meeting was today at 8 UTC (APAC slot)
>>   we will use the slot of tomorrow to organize an ad-hoc meeting with 
>>   Bitergia on result vizualization
>>   not sure we will have 15 minutes for another topic
>> 
>>   It is maybe possible to organize an ad-hoc meeting on this topic after 
>>   the point with Bitergia?
>> 
>>   Do not hesitate to modify directly the agenda at your convenience 
>>   
(https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting)
>> 
>>   /Morgan
>> 
>> 
>> 
>>   On 12/07/2017 17:43, Alec Hothan (ahothan) wrote:
>>> Morgan,
>>> 
>>> Unfortunately, I won’t be able to attend next week (on PTO).
>>> Can this be squeezed into tomorrow’s meeting (July 13)? We could 
shorten it and follow up with a separate meeting or on email/IRC.
>>> 
>>> Thanks
>>> 
>>>  Alec
>>> 
>>> 
>>> 
>>> On 7/12/17, 8:32 AM, "morgan.richo...@oran

Re: [opnfv-tech-discuss] [test-wg] docker container versioning

2017-07-14 Thread Alec Hothan (ahothan)
Hi Jose,

I have moved this topic and added a sub-agenda to the July 27 test-wg weekly 
meeting agenda 
(https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting)
It is good that this issue has not caused any big problem yet for container 
owners (likely because none of the artifacts has been widely deployed outside 
of OPNFV labs yet) 
but I’d like to recommend to address it very quickly. 
Fatih has noted rightly that this is actually a larger scope issue (extending 
to all other artifacts: VM images, doc, rpms). It is good to see the larger 
picture but I’d like to avoid making it too complex and start with container 
images with adoption of simple industry best practice versioning.

Thanks

   Alec




On 7/13/17, 8:43 AM, "Jose Lausuch"  wrote:

Hi Alec,

The versioning is not an urgent matter and it is working well today.  I 
agree it is a topic to be discussed but maybe it is better to wait until 
everyone is back from PTO as it will be difficult to align without the 
participation of the people who are really involved.

- Jose -




> On 13 Jul 2017, at 17:00, Alec Hothan (ahothan)  wrote:
> 
> Jose,
> 
> You should start the discussion at the next infra wg meeting (I’ll be on 
PTO whole of next week). I think if the issue can be raised and acknowledged it 
will already be a good step.
> I will just note that:
> - this has to be a joint work by both infra and project teams
> - perhaps we could use some help from OPNFV members who do 
packaging/versioning for a living ;-) (e.g. Linux distro vendors
> 
> To clarify, I’m willing to help on the container/VM image/docs 
workflow/versioning since my project produces those. Not so much on the other 
artifacts such as RPM (which might be more complex).
> I’m not familiar enough with OPNFV to know who works on what, I was 
hoping to get more active feedback from at least the main/most active OPNFV 
container owners. The current versioning is clearly insufficient and I’d like 
to get the input from projects that have been publishing containers for a while.
> 
> Can anybody describe quickly how specs are usually being 
discussed/redacted by working groups? Email is usually not the best (written) 
format. OpenStack uses etherpads or text files that are reviewed through gerrit.
> 
> Thanks
> 
>  Alec
> 
> 
> On 7/12/17, 11:35 PM, "Jose Lausuch"  wrote:
> 
>Hi,
> 
>Is there time to discuss this during the next infra wg meeting on 
Monday? Although the test projects are the main ones using docker containers, 
we are talking about versioning here, which I believe is topic the Infra team 
should address.
> 
>I also would like to add to the agenda:
>  -  decision on where to host the docker build scripts (common one or 
project´s repo?). It has been proposed but not decided.
> 
>Thanks,
>Jose
> 
> 
> 
>> On 12 Jul 2017, at 20:10, Alec Hothan (ahothan)  
wrote:
>> 
>> July/August is tricky with PTOs.
>> Perhaps we should start the discussion by email on this mailer and 
discuss about it in 2 weeks at the test-wg meeting? 
>> Do you guys usually use a text document reviewed with gerrit to 
discuss/collaborate on a spec? Or any other method? Please let me know and I 
can get a head start on this.
>> 
>> Thanks
>> 
>> Alec
>> 
>> On 7/12/17, 8:54 AM, "morgan.richo...@orange.com" 
 wrote:
>> 
>>   I will be in PTO too :)
>> 
>>   Unfortunately the weekly meeting was today at 8 UTC (APAC slot)
>>   we will use the slot of tomorrow to organize an ad-hoc meeting with 
>>   Bitergia on result vizualization
>>   not sure we will have 15 minutes for another topic
>> 
>>   It is maybe possible to organize an ad-hoc meeting on this topic after 
>>   the point with Bitergia?
>> 
>>   Do not hesitate to modify directly the agenda at your convenience 
>>   
(https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting)
>> 
>>   /Morgan
>> 
>> 
>> 
>>   On 12/07/2017 17:43, Alec Hothan (ahothan) wrote:
>>> Morgan,
>>> 
>>> Unfortunately, I won’t be able to attend next week (on PTO).
>>> Can this be squeezed into tomorrow’s meeting (July 13)? We could 
shorten it and follow up with a separate meeting or on email/IRC.
>>> 
>>> Thanks
>>> 
>>>  Alec
>>> 
>>> 
>>> 
>>> On 7/12/17, 8:32 AM, "morgan.richo...@orange.com" 
 wrote:
>>> 
>>>topic added for the next meeting (20th of July)
>>>
https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting
>>> 
>>>Mark and Jose are already involved in several activities dealing with
>>>docker.
>>>Cedric has a good view on this topic.
>>> 
>>>/Morgan
>>> 
>>>On 12/07/2017 17:27, Alec

Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Manuel Buil
Ok. Check the first log you sent:







017-07-14
11:18:47,630 - __main__ - INFO - Restart heat-engine in 10.192.3.71

2017-07-14
11:18:47,630 - __main__ - INFO - Waiting for heat-engine to restart
in controllers

2017-07-14
11:18:57,641 - __main__ - INFO - tackerc file not found, fetching it
from controller

Tacker should have created a tackerc file in the controller when deployed

-Manuel

On Fri, 2017-07-14 at 19:12 +0530, Pavan Gupta wrote:
> > HI Manuel,Tacker was deployed in the beginning itself. Please check
the attached image.  Is there anything else I need to deploy Tacker?
> Pavan
> 
> 
> > > > On 14-Jul-2017, at 7:07 PM, Manuel Buil  wrote:
> > Hello Pavan,
> > 
> > > > > > In the logs you sent previously, that step worked but it was not
able to fetch tackerc. Did you deploy your environment activating
tacker? It should be under settings > openstack services.
> > 
> > -Manuel
> > 
> > On Fri, 2017-07-14 at 18:36 +0530, Pavan Gupta wrote:
> > > HI Jose,
> > > This is sfc.log
> > > 
> > > 
> > > 
> > > 
> > > 2017-07-14 12:57:13,258 - SSH utils - ERROR - timed out
> > > 2017-07-14 12:58:13,319 - SSH utils - ERROR - timed out
> > > 2017-07-14 12:59:13,348 - SSH utils - ERROR - timed out
> > > 2017-07-14 13:00:13,405 - SSH utils - ERROR - timed out
> > > > > > 2017-07-14 13:00:13,406 - __main__ - INFO - Fetch
/etc/heat/heat.conf from controller 10.192.3.70
> > > > > > 2017-07-14 13:00:13,406 - opnfv.deployment.manager - INFO -
Fetching /etc/heat/heat.conf from 10.192.3.70
> > > > > > > > > 2017-07-14 13:00:13,406 - SSH utils - ERROR - Error
[get_file(ssh_conn, '/etc/heat/heat.conf', '/tmp/heat.conf']:
'NoneType' object has no attribute 'open_sftp'
> > > > > > 2017-07-14 13:00:13,406 - opnfv.deployment.manager - ERROR - SFTP
failed to retrieve the file.
> > > > > > 2017-07-14 13:00:13,407 - __main__ - INFO - Replace
/etc/heat/heat.conf with /tmp/heat.conf in controller 10.192.3.70
> > > 10.20.0.2
> > > root
> > > r00tme
> > > None
> > > --*-*
> > > > > > Installer Connection =  
> > > Traceback (most recent call last):
> > >   File "./run_tests.py", line 189, in 
> > >     main(report=args.report)
> > >   File "./run_tests.py", line 91, in main
> > >     disable_heat_resource_finder_cache(nodes)
> > > > > >   File "./run_tests.py", line 67, in
disable_heat_resource_finder_cache
> > >     controller.run_cmd('rm -f {0}'.format(remote_heat_conf))
> > > > > > > > >   File
"/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py",
line 184, in run_cmd
> > >     _, stdout, stderr = (self.ssh_client.exec_command(cmd))
> > > AttributeError: 'NoneType' object has no attribute ‘exec_command'
> > > 
> > > 
> > > 
> > > 
> > > Pavan
> > > 
> > > 
> > > 
> > > 
> > > > > > > > On 14-Jul-2017, at 6:32 PM, Jose Lausuch  wrote:
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Hi,
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > > > > > > > > > > > > Functest looks fine. Can you now attach sfc.log 
> > > > > > > > > > > > > > > > located in the
same directory? Maybe it’s a problem with the test case as such
while trying to access the deployment. Maybe Manuel has more
experience with it.
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > - Jose -
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > > > > > > On 14 Jul 2017, at 14:47, Pavan Gupta 
> > > > > > > > > >  wrote:
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > HI Jose,
> > > > > 
> > > > > - I have attached the log file this time.
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > - Output of docker images:
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > > > > > > REPOSITORY                  TAG                 IMAGE ID    
> > > > > > > > > >  
      CREATED             SIZE
> > > > > 
> > > > > 
> > > > > > > > > > opnfv/functest              stable              
> > > > > > > > > > 2553087919e0 
      9 days ago          1.57GB
> > > > > 
> > > > > 
> > > > > > > > > > ryu7249125/yardstick        latest              
> > > > > > > > > > e37ee4c07ca8 
      2 months ago        3.52GB
> > > > > 
> > > > > 
> > > > > > > > > > opnfv/yardstick             stable              
> > > > > > > > > > 7fc31a6fc1d5 
      2 months ago        1.2GB
> > > > > 
> > > > > 
> > > > > > > > > > autolytiks_logstash         latest              
> > > > > > > > > > 0b8f850cf592 
      2 months ago        565MB
> > > > > 
> > > > > 
> > > > > > > > > > autolytiks_elasticsearch    latest              
> > > > > > > > > > f73bc006eb57 
      2 months ago        352MB
> > > > > 
> > > > > 
> > > > > > > > > > autolytiks_nginx            latest              
> > > > > > > > > > b3d688b35417 
      2 months ago        206MB
> > > > > 
> > > > > 
> > > > > > > > > > autolytiks_web              latest              
> > > > > > > > > > 7c2907bd15d8 
      2 months ago        727MB
> 

Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Manuel Buil
Hello Pavan,

In the logs you sent previously, that step worked but it was not able
to fetch tackerc. Did you deploy your environment activating tacker? It
should be under settings > openstack services.

-Manuel

On Fri, 2017-07-14 at 18:36 +0530, Pavan Gupta wrote:
> HI Jose,
> This is sfc.log
> 
> 
> 
> 
> 2017-07-14 12:57:13,258 - SSH utils - ERROR - timed out
> 2017-07-14 12:58:13,319 - SSH utils - ERROR - timed out
> 2017-07-14 12:59:13,348 - SSH utils - ERROR - timed out
> 2017-07-14 13:00:13,405 - SSH utils - ERROR - timed out
> > 2017-07-14 13:00:13,406 - __main__ - INFO - Fetch /etc/heat/heat.conf
from controller 10.192.3.70
> > 2017-07-14 13:00:13,406 - opnfv.deployment.manager - INFO - Fetching
/etc/heat/heat.conf from 10.192.3.70
> > > 2017-07-14 13:00:13,406 - SSH utils - ERROR - Error
[get_file(ssh_conn, '/etc/heat/heat.conf', '/tmp/heat.conf']:
'NoneType' object has no attribute 'open_sftp'
> > 2017-07-14 13:00:13,406 - opnfv.deployment.manager - ERROR - SFTP
failed to retrieve the file.
> > 2017-07-14 13:00:13,407 - __main__ - INFO - Replace
/etc/heat/heat.conf with /tmp/heat.conf in controller 10.192.3.70
> 10.20.0.2
> root
> r00tme
> None
> --*-*
> > Installer Connection =  
> Traceback (most recent call last):
>   File "./run_tests.py", line 189, in 
>     main(report=args.report)
>   File "./run_tests.py", line 91, in main
>     disable_heat_resource_finder_cache(nodes)
> >   File "./run_tests.py", line 67, in
disable_heat_resource_finder_cache
>     controller.run_cmd('rm -f {0}'.format(remote_heat_conf))
> > >   File
"/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line
184, in run_cmd
>     _, stdout, stderr = (self.ssh_client.exec_command(cmd))
> AttributeError: 'NoneType' object has no attribute ‘exec_command'
> 
> 
> 
> 
> Pavan
> 
> 
> 
> 
> > > > On 14-Jul-2017, at 6:32 PM, Jose Lausuch  wrote:
> > 
> > 
> > 
> > 
> > 
> > Hi,
> > 
> > 
> > 
> > 
> > > > > > > > Functest looks fine. Can you now attach sfc.log located in the 
> > > > > > > > same
directory? Maybe it’s a problem with the test case as such while
trying to access the deployment. Maybe Manuel has more experience
with it.
> > 
> > 
> > 
> > 
> > 
> > - Jose -
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > > > > > On 14 Jul 2017, at 14:47, Pavan Gupta  wrote:
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > HI Jose,
> > > 
> > > - I have attached the log file this time.
> > > 
> > > 
> > > 
> > > 
> > > 
> > > - Output of docker images:
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > > > > REPOSITORY                  TAG                 IMAGE ID         
  CREATED             SIZE
> > > 
> > > 
> > > > > > opnfv/functest              stable              2553087919e0     
  9 days ago          1.57GB
> > > 
> > > 
> > > > > > ryu7249125/yardstick        latest              e37ee4c07ca8     
  2 months ago        3.52GB
> > > 
> > > 
> > > > > > opnfv/yardstick             stable              7fc31a6fc1d5     
  2 months ago        1.2GB
> > > 
> > > 
> > > > > > autolytiks_logstash         latest              0b8f850cf592     
  2 months ago        565MB
> > > 
> > > 
> > > > > > autolytiks_elasticsearch    latest              f73bc006eb57     
  2 months ago        352MB
> > > 
> > > 
> > > > > > autolytiks_nginx            latest              b3d688b35417     
  2 months ago        206MB
> > > 
> > > 
> > > > > > autolytiks_web              latest              7c2907bd15d8     
  2 months ago        727MB
> > > 
> > > 
> > > > > > python                      3.5-onbuild         2d1685b88f32     
  2 months ago        689MB
> > > 
> > > 
> > > > > > redis                       latest              e32ef7250bc1     
  2 months ago        184MB
> > > 
> > > 
> > > > > > postgres                    latest              390220867755     
  2 months ago        267MB
> > > 
> > > 
> > > > > > influxdb                    latest              95b868946bae     
  2 months ago        224MB
> > > 
> > > 
> > > > > > logstash                    5.2                 e2e0c054df39     
  3 months ago        494MB
> > > 
> > > 
> > > > > > elasticsearch               5.2                 0206b7302cfe     
  3 months ago        352MB
> > > 
> > > 
> > > > > > grafana/grafana             latest              8c4ef64b4ad1     
  3 months ago        278MB
> > > 
> > > 
> > > > > > autolytiks_kibana           latest              724639b70915     
  3 months ago        329MB
> > > 
> > > 
> > > > > > kibana                      5.2                 724639b70915     
  3 months ago        329MB
> > > 
> > > 
> > > > > > hello-world                 latest              c54a2cc56cbb     
  12 months ago       1.85kB
> > > 
> > > 
> > > > > > opennetworklinux/builder7   1.2                 a0a471ea8d55     
  13 months ago       1.92GB
> > > 
> > > 
> > > > > > tutum/nginx                 latest              a2e9b71ed366     
  16 months ago       206MB
> > > 
> > > 
> > > 
>

Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Jose Lausuch
Hi,

Functest looks fine. Can you now attach sfc.log located in the same directory? 
Maybe it’s a problem with the test case as such while trying to access the 
deployment. Maybe Manuel has more experience with it.

- Jose -


On 14 Jul 2017, at 14:47, Pavan Gupta 
mailto:pavan.gu...@calsoftinc.com>> wrote:

HI Jose,
- I have attached the log file this time.

- Output of docker images:

REPOSITORY  TAG IMAGE IDCREATED 
SIZE
opnfv/functest  stable  2553087919e09 days ago  
1.57GB
ryu7249125/yardsticklatest  e37ee4c07ca82 months 
ago3.52GB
opnfv/yardstick stable  7fc31a6fc1d52 months 
ago1.2GB
autolytiks_logstash latest  0b8f850cf5922 months 
ago565MB
autolytiks_elasticsearchlatest  f73bc006eb572 months 
ago352MB
autolytiks_nginxlatest  b3d688b354172 months 
ago206MB
autolytiks_web  latest  7c2907bd15d82 months 
ago727MB
python  3.5-onbuild 2d1685b88f322 months 
ago689MB
redis   latest  e32ef7250bc12 months 
ago184MB
postgreslatest  3902208677552 months 
ago267MB
influxdblatest  95b868946bae2 months 
ago224MB
logstash5.2 e2e0c054df393 months 
ago494MB
elasticsearch   5.2 0206b7302cfe3 months 
ago352MB
grafana/grafana latest  8c4ef64b4ad13 months 
ago278MB
autolytiks_kibana   latest  724639b709153 months 
ago329MB
kibana  5.2 724639b709153 months 
ago329MB
hello-world latest  c54a2cc56cbb12 months 
ago   1.85kB
opennetworklinux/builder7   1.2 a0a471ea8d5513 months 
ago   1.92GB
tutum/nginx latest  a2e9b71ed36616 months 
ago   206MB


- Output of docker ps:
CONTAINER IDIMAGECOMMAND  CREATED   
  STATUS  PORTS 
   NAMES
9b1c47899d65opnfv/functest:stable"/bin/bash"  6 hours 
ago Up 6 hours  
 sfc
0eb2d3ff7e4dautolytiks_nginx "/usr/sbin/nginx"2 months 
agoUp 8 days   0.0.0.0:80->80/tcp   
autolytiks_nginx_1
ce4e265af4cdgrafana/grafana:latest   "/run.sh"2 months 
agoUp 8 days   0.0.0.0:3000->3000/tcp   
autolytiks_grafana_1
87e2e67d8924autolytiks_web   "/usr/local/bin/gu..."   2 months 
agoUp 8 days   8000/tcp 
autolytiks_web_1
f7e290be942dinfluxdb:latest  "/entrypoint.sh in..."   2 months 
agoUp 8 days   0.0.0.0:8084->8083/tcp, 0.0.0.0:8087->8086/tcp, 
0.0.0.0:8090->8089/tcp   autolytiks_influxdb_1
6e77fd10b6c8postgres:latest  "docker-entrypoint..."   2 months 
agoUp 8 days   0.0.0.0:5432->5432/tcp   
autolytiks_postgres_1
da192814b82bredis:latest "docker-entrypoint..."   2 months 
agoUp 8 days   0.0.0.0:6379->6379/tcp   
autolytiks_redis_1


Please let me know if you need any other information.
Pavan

On 14-Jul-2017, at 6:09 PM, Jose Lausuch 
mailto:jose.laus...@ericsson.com>> wrote:

Pavan,

I don’t see any attachment.

| 2. Docker image: Docker version 17.04.0-ce, build 4845c56
I meant the Functest docker image. Just run: docker ps or docker images to see 
which Functest version you are using.

- Jose -

From: Pavan Gupta [mailto:pavan.gu...@calsoftinc.com]
Sent: Friday, July 14, 2017 14:28 PM
To: Jose Lausuch mailto:jose.laus...@ericsson.com>>
Cc: Manuel Buil mailto:mb...@suse.com>>; 
andres.sanchez.ra...@estudiant.upc.edu;
 OPNFV-TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] SFC Project

Hi Jose,
1. I have attached functest.log.

2. Docker image: Docker version 17.04.0-ce, build 4845c56

3. Installer: Fuel, version 10.0.0

4. Credentials: Same as mentioned in the link (root, r00tme)

Thank you.
Pavan

On 14-Jul-2017, at 5:15 PM, Jose Lausuch 
mailto:jose.laus...@ericsson.com>> wrote:

/hom

Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Jose Lausuch
Pavan,

I don't see any attachment.

| 2. Docker image: Docker version 17.04.0-ce, build 4845c56
I meant the Functest docker image. Just run: docker ps or docker images to see 
which Functest version you are using.

- Jose -

From: Pavan Gupta [mailto:pavan.gu...@calsoftinc.com]
Sent: Friday, July 14, 2017 14:28 PM
To: Jose Lausuch 
Cc: Manuel Buil ; andres.sanchez.ra...@estudiant.upc.edu; 
OPNFV-TECH-DISCUSS OPNFV 
Subject: Re: [opnfv-tech-discuss] SFC Project

Hi Jose,
1. I have attached functest.log.

2. Docker image: Docker version 17.04.0-ce, build 4845c56

3. Installer: Fuel, version 10.0.0

4. Credentials: Same as mentioned in the link (root, r00tme)

Thank you.
Pavan

On 14-Jul-2017, at 5:15 PM, Jose Lausuch 
mailto:jose.laus...@ericsson.com>> wrote:

/home/opnfv/functest/results/functest.log

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Jose Lausuch
Hi Pavan,

Can you please attach functest log, located in 
/home/opnfv/functest/results/functest.log ?

Also answer to the following questions about your environment:

Which docker image (tag) are you using?
Which installer? Version?

The credentials to access the installer node are in [1]. If you have deployed 
your installer node with different user/password, make sure you update that as 
well.

Jose

[1] 
https://git.opnfv.org/functest/tree/functest/ci/installer_params.yaml?h=stable/danube




On 14 Jul 2017, at 13:31, Pavan Gupta 
mailto:pavan.gu...@calsoftinc.com>> wrote:

Hi Manuel,
- I am using funkiest command list. I run this command: 'functest testcase run 
odl-sfc’

- I am new openstack as well, can you please tell me, what all env variables 
need to be set. Do I need to copy these in openstack.creds. This is what is 
there at present in this file:
OS_REGION_NAME=RegionOne
OS_DEFAULT_DOMAIN=default
OS_USER_DOMAIN_NAME=Default
OS_PROJECT_NAME=admin
OS_IDENTITY_API_VERSION=3
OS_PASSWORD=admin
OS_AUTH_STRATEGY=keystone
OS_AUTH_URL=http://192.168.0.2:5000/
OS_USERNAME=admin
OS_TENANT_NAME=admin
OS_ENDPOINT_TYPE=internalURL
OS_NO_CACHE=true
OS_PROJECT_DOMAIN_NAME=Default

- Where do I run ‘openstack server list’ command. I tried running it on node-1 
machine, which is a controller machine, the output was blank.

Any useful pointer would be appreciated.
Pavan
-
On 14-Jul-2017, at 4:49 PM, Manuel Buil mailto:mb...@suse.com>> 
wrote:

HI Pavan,

I think your openstack env. variables are not set. How do you execute the tests?

If you are not using the functest command line, you need to source the env 
variables (from openrc or tackerc). To check that everything is ok, try to 
execute one openstack command before executing the test and check that you 
don't get any error (e.g. openstack server list).

Regards,
Manuel

On Fri, 2017-07-14 at 16:40 +0530, Pavan Gupta wrote:
Hello Folks,
I have managed to begin the test but hit across this error:

Traceback (most recent call last):
  File "./run_tests.py", line 189, in 
main(report=args.report)
  File "./run_tests.py", line 91, in main
disable_heat_resource_finder_cache(nodes)
  File "./run_tests.py", line 67, in disable_heat_resource_finder_cache
controller.run_cmd('rm -f {0}'.format(remote_heat_conf))
  File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line 
184, in run_cmd
_, stdout, stderr = (self.ssh_client.exec_command(cmd))
AttributeError: 'NoneType' object has no attribute ‘exec_command'


Does anyone know fix for this?
Pavan

On 14-Jul-2017, at 12:56 PM, Jose Lausuch 
mailto:jose.laus...@ericsson.com>> wrote:

Ok, just for your information:
if you are using Functest Danube, you need connectivity to the admin network. 
We are working on removing that constraint in Euphrates against OpenStack Ocata.

Thanks,
Jose



On 14 Jul 2017, at 08:45, Pavan Gupta 
mailto:pavan.gu...@calsoftinc.com>> wrote:

Hi Jose,
I added the following route on Junper host and connectivity worked, so the SFC 
test environment was successfully prepared.
sudo route add -net 192.168.0.0 netmask 255.255.255.0 gw 172.26.48.23

Thanks for your help.
Pavan

On 13-Jul-2017, at 7:06 PM, Jose Lausuch 
mailto:jose.laus...@ericsson.com>> wrote:

Hi Pavan,

It seems your installer is not supported by the script fetch_os_creds.sh

In that case, you need to provide the openstack RC file from your deployment 
manually to the container, or just copy the content to  
/home/opnfv/functest/conf/openstack.creds

Let me know if it still fails that way.

Regards,
Jose


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Pavan Gupta
Sent: Thursday, July 13, 2017 14:29 PM
To: Manuel Buil mailto:mb...@suse.com>>
Cc: 
andres.sanchez.ra...@estudiant.upc.edu;
 OPNFV-TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] SFC Project

Hi Manuel/Andres,
When I run 'functest env prepare’, I also see this issue:


/home/opnfv/repos/releng/utils/fetch_os_creds.sh: line 76: SALT_MASTER_IP: 
unbound variable

What should be SALT_MASTER_IP address?
Pavan

On 13-Jul-2017, at 3:37 PM, Manuel Buil mailto:mb...@suse.com>> 
wrote:

10.20.0.2





___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Manuel Buil
HI Pavan,

I think your openstack env. variables are not set. How do you execute
the tests?

If you are not using the functest command line, you need to source the
env variables (from openrc or tackerc). To check that everything is ok,
try to execute one openstack command before executing the test and
check that you don't get any error (e.g. openstack server list).

Regards,
Manuel

On Fri, 2017-07-14 at 16:40 +0530, Pavan Gupta wrote:
> Hello Folks,
> I have managed to begin the test but hit across this error:
> 
> Traceback (most recent call last):
>   File "./run_tests.py", line 189, in 
>     main(report=args.report)
>   File "./run_tests.py", line 91, in main
>     disable_heat_resource_finder_cache(nodes)
> >   File "./run_tests.py", line 67, in
disable_heat_resource_finder_cache
>     controller.run_cmd('rm -f {0}'.format(remote_heat_conf))
> > >   File
"/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line
184, in run_cmd
>     _, stdout, stderr = (self.ssh_client.exec_command(cmd))
> AttributeError: 'NoneType' object has no attribute ‘exec_command'
> 
> 
> 
> 
> 
> Does anyone know fix for this?
> Pavan
> 
> > > > On 14-Jul-2017, at 12:56 PM, Jose Lausuch  wrote:
> > 
> > 
> > 
> > 
> > 
> > Ok, just for your information: 
> > > > > > if you are using Functest Danube, you need connectivity to the
admin network. We are working on removing that constraint in
Euphrates against OpenStack Ocata.
> > 
> > 
> > 
> > 
> > 
> > Thanks,
> > 
> > Jose
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > > > > > On 14 Jul 2017, at 08:45, Pavan Gupta  wrote:
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Hi Jose,
> > > > > > I added the following route on Junper host and connectivity
worked, so the SFC test environment was successfully prepared.
> > > 
> > > 
> > > 
> > > > > > sudo route add -net 192.168.0.0 netmask 255.255.255.0 gw
172.26.48.23
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > Thanks for your help.
> > > 
> > > 
> > > Pavan
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > > > > > > On 13-Jul-2017, at 7:06 PM, Jose Lausuch  wrote:
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Hi Pavan,
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > > > > > It seems your installer is not supported by the script
fetch_os_creds.sh
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > > > > > > > > > In that case, you need to provide the openstack RC file 
> > > > > > > > > > > > from
your deployment manually to the container, or just copy the
content to  /home/opnfv/functest/conf/openstack.creds
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > Let me know if it still fails that way.
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > Regards,
> > > > 
> > > > 
> > > > Jose
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > > > > > > > > From: opnfv-tech-discuss-boun...@lists.opnfv.org 
> > > > > > > > > > > > [mailto:opnfv-
tech-discuss-boun...@lists.opnfv.org] On
> > > >  Behalf Of Pavan Gupta
> > > > 
> > > > Sent: Thursday, July 13, 2017 14:29 PM
> > > > 
> > > > > > > > To: Manuel Buil 
> > > > 
> > > > > > > > > > > > > > > > Cc: andres.sanchez.ra...@estudiant.upc.edu; 
> > > > > > > > > > > > > > > > OPNFV-TECH-DISCUSS
OPNFV 
> > > > 
> > > > Subject: Re: [opnfv-tech-discuss] SFC Project
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > Hi Manuel/Andres,
> > > > 
> > > > 
> > > > 
> > > > 
> > > > When I run 'functest env prepare’, I also see this issue:
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > > > > /home/opnfv/repos/releng/utils/fetch_os_creds.sh: line 76:
SALT_MASTER_IP: unbound variable
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > What should be SALT_MASTER_IP address?
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > Pavan
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > > > > > On 13-Jul-2017, at 3:37 PM, Manuel Buil  wrote:
> > > > 
> > > > 
> > > > 
> > > > 
> > > >  
> > > > 
> > > > 
> > > > 
> > > > 10.20.0.2
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] [barometer] I would like to contribute to the PROJECT

2017-07-14 Thread Tahhan, Maryam
Hi Aric
Can you please give Emma Permissions to contribute to barometer?

Thanks
Maryam 

> -Original Message-
> From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-
> boun...@lists.opnfv.org] On Behalf Of Foley, Emma L
> Sent: Friday, July 14, 2017 10:55 AM
> To: opnfv-tech-discuss@lists.opnfv.org
> Subject: [opnfv-tech-discuss] [barometer] I would like to contribute to the
> PROJECT
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


[opnfv-tech-discuss] [barometer] I would like to contribute to the PROJECT

2017-07-14 Thread Foley, Emma L

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] [anteater] build log for anteator

2017-07-14 Thread Luke Hinds
On Fri, Jul 14, 2017 at 1:43 AM, Yujun Zhang (ZTE)  wrote:

> Yes, that's what I am seeking.
>
> When a comment is posted by a bot, I would be curious on where this
> message is coming from. I suppose it is posted from some periodic check
> task?
>
>
So we have a jira open to provide a snippet of text on what the 'thinking'
is behind the block, I believe that is what Julien is going to address.

>
> On Fri, Jul 14, 2017 at 7:00 AM Julien  wrote:
>
>> Oh,
>>
>> I understand the issue: no output of the detailed log of the Jenkins task.
>>
>> Luke, I will deal with this.
>>
>>
Thanks Julien.


>
>> Luke Hinds 于2017年7月13日周四 下午10:13写道:
>>
>>> How do you mean by build log Yujun? I am always interested in feedback /
>>> improvements.
>>>
>>>
>>> On Wed, Jul 12, 2017 at 4:10 AM, Yujun Zhang (ZTE) <
>>> zhangyujun+...@gmail.com> wrote:
>>>
 I notices a warning on license header in https://gerrit.opnfv.org/
 gerrit/#/c/36839/

 [image: Screen Shot 2017-07-12 at 11.03.55 AM.png]

 However the build log is not posted. It's OK for now since the failure
 is clear enough. But it would be nice to have the build log as well as
 other CI jobs.

 --
 Yujun

 --
 Yujun Zhang

 ___
 opnfv-tech-discuss mailing list
 opnfv-tech-discuss@lists.opnfv.org
 https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


>>>
>>>
>>> --
>>> Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
>>> e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 |
>>> t: +44 12 52 36 2483
>>> ___
>>> opnfv-tech-discuss mailing list
>>> opnfv-tech-discuss@lists.opnfv.org
>>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>>
>> --
> Yujun Zhang
>



-- 
Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat
e: lhi...@redhat.com | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44
12 52 36 2483
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


[opnfv-tech-discuss] Secure use of curl / wget and external artefacts

2017-07-14 Thread Luke Hinds
Anteater has raised that a lot of projects are using curl / wget to pull
down artefacts from external sites that are often instantiated (in the case
of an IMG file) or piped through bash (in the case of a shell script).

This is dangerous and has known risks, so I have put together a wiki page
explaining what the risks are and how to mitigate them (with example code
and script snippets):

https://wiki.opnfv.org/display/security/How+to+handle+leverage+artefacts+in+a+secure+manner

Please do read, and consider patching your code where it does the above.
You have E release to do so, but for F release it will be blocked by
Anteater and for the more dangerous examples I will make a recommendation
to release to consider its impact when released to end users.

Thanks,

Luke
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] SFC Project

2017-07-14 Thread Jose Lausuch
Ok, just for your information:
if you are using Functest Danube, you need connectivity to the admin network. 
We are working on removing that constraint in Euphrates against OpenStack Ocata.

Thanks,
Jose



On 14 Jul 2017, at 08:45, Pavan Gupta 
mailto:pavan.gu...@calsoftinc.com>> wrote:

Hi Jose,
I added the following route on Junper host and connectivity worked, so the SFC 
test environment was successfully prepared.
sudo route add -net 192.168.0.0 netmask 255.255.255.0 gw 172.26.48.23

Thanks for your help.
Pavan

On 13-Jul-2017, at 7:06 PM, Jose Lausuch 
mailto:jose.laus...@ericsson.com>> wrote:

Hi Pavan,

It seems your installer is not supported by the script fetch_os_creds.sh

In that case, you need to provide the openstack RC file from your deployment 
manually to the container, or just copy the content to  
/home/opnfv/functest/conf/openstack.creds

Let me know if it still fails that way.

Regards,
Jose


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Pavan Gupta
Sent: Thursday, July 13, 2017 14:29 PM
To: Manuel Buil mailto:mb...@suse.com>>
Cc: 
andres.sanchez.ra...@estudiant.upc.edu;
 OPNFV-TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] SFC Project

Hi Manuel/Andres,
When I run 'functest env prepare’, I also see this issue:


/home/opnfv/repos/releng/utils/fetch_os_creds.sh: line 76: SALT_MASTER_IP: 
unbound variable

What should be SALT_MASTER_IP address?
Pavan

On 13-Jul-2017, at 3:37 PM, Manuel Buil mailto:mb...@suse.com>> 
wrote:

10.20.0.2


___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss