[opnfv-tech-discuss] [XCI][OS-ODL-SFC] Deployment failure

[andres sanchez ramos]

Hello,


I am trying to deploy the xci os-odl-sfc environment in a server using the mini 
flavor! I have previously deployed the OPNFV xci version on this server without 
any issues, but now i am trying to deploy the os-odl-sfc version following this 
guides:


https://wiki.opnfv.org/display/sfc/Deploy+OPNFV+SFC+scenarios

http://docs.opnfv.org/en/latest/submodules/releng-xci/docs/xci-user-guide.html

The installation fails at this point:


---
Info: Configured localhost host for openstack-ansible
Info: Configuring opnfv deployment host for openstack-ansible
---
 [WARNING]: Found both group and host with same name: opnfv


PLAY [opnfv] ***

TASK [Gathering Facts] *
fatal: [opnfv]: FAILED! => {"changed": false, "failed": true, "module_stderr": 
"Shared connection to 192.168.122.2 closed.\r\n", "module_stdout": "/bin/sh: 1: 
/usr/local/python: not found\r\n", "msg": "MODULE FAILURE", "rc": 0}
to retry, use: --limit 
@/tmp/.xci-deploy-env/releng-xci/xci/playbooks/configure-opnfvhost.retry

PLAY RECAP *
opnfv  : ok=0changed=0unreachable=0failed=1

Here follows the information printed at failure:

Do not forget to submit the following information on your bug report:

Not a git repository
To compare two paths outside a working tree:
usage: git diff [--no-index]  
releng-xci tree status: local modifications
fatal: Not a git repository (or any of the parent directories): .git
opnfv/releng-xci version:
openstack/bifrost version: db9f2f556bf92558275c0422beafb5e68eff59f1
openstack/openstack-ansible version: stable/ocata
xci flavor: mini
Environment variables:
XCI_PATH=/home/lab325/releng-xci/xci
OPNFV_SCENARIO=os-odl-sfc
XCI_FLAVOR=mini
OPENSTACK_BIFROST_PATH=/tmp/.xci-deploy-env/bifrost
XCI_ANSIBLE_VERBOSITY=
OPENSTACK_OSA_OPENRC_PATH=/tmp/.xci-deploy-env/openstack-ansible-openstack_openrc
OPENSTACK_OSA_VERSION=stable/ocata
OPNFV_RELENG_PATH=/tmp/.xci-deploy-env/releng-xci
OPNFV_RELENG_DEV_PATH=/home/lab325/releng-xci/
OPENSTACK_OSA_GIT_URL=https://git.openstack.org/openstack/openstack-ansible
OPNFV_OSA_PLAYBOOK=/tmp/.xci-deploy-env/openstack-ansible/playbooks/setup-openstack.yml
OPNFV_SSH_HOST_KEYS_PATH=/tmp/.xci-deploy-env/ssh_host_keys
XCI_SSL_SUBJECT=/C=US/ST=California/L=San Francisco/O=IT/CN=xci.releng.opnfv.org
XCI_ANSIBLE_PIP_VERSION=2.3.2.0
XCI_DEVEL_ROOT=/tmp/.xci-deploy-env
OPENSTACK_OSA_OPENRC_GIT_URL=https://git.openstack.org/openstack/openstack-ansible-openstack_openrc
OPNFV_RELENG_VERSION=master
OPENSTACK_OSA_ETC_PATH=/etc/openstack_deploy
OPNFV_HOST_IP=192.168.122.2
OPNFV_RELENG_GIT_URL=https://gerrit.opnfv.org/gerrit/releng-xci.git
OPENSTACK_BIFROST_GIT_URL=https://git.openstack.org/openstack/bifrost
OPENSTACK_BIFROST_VERSION=db9f2f556bf92558275c0422beafb5e68eff59f1
OPENSTACK_OSA_PATH=/tmp/.xci-deploy-env/openstack-ansible
OPNFV_XCI_PATH=/tmp/.xci-deploy-env/releng-xci/xci
XCI_EXTRA_VARS_PATH=
XCI_FLAVOR_ANSIBLE_FILE_PATH=/tmp/.xci-deploy-env/releng-xci/xci/file/mini

If I understand correctly it is not finding python in the remote machine, I 
have checked and the remote machine appears to have python3 but no python2.7, 
should I modifiy the playbooks so that they work with python3?

Best regards,





Enviado desde Outlook
___
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

[andres . sanchez . ramos]

Good morning Manuel!

It looks good, here is my output:

lab232@lab232-G31M-ES2C:~$ curl -u admin:admin -H 'Content-type:  
application/json' -X GET  
http://192.168.0.9:8282/controller/nb/v2/neutron/networks

{
   "networks" : [ {
  "id" : "fb38dc83-fc4a-453a-babf-2c09e2b7f6de",
  "tenant_id" : "cb1d668144054ca0a00138154f5e58cd",
  "name" : "admin_floating_net",
  "admin_state_up" : true,
  "shared" : false,
  "router:external" : true,
  "provider:network_type" : "flat",
  "provider:physical_network" : "physnet1",
  "status" : "ACTIVE",
  "segments" : [ ]
   }, {
  "id" : "cd412027-506a-4ae5-a790-41391845e775",
  "tenant_id" : "cb1d668144054ca0a00138154f5e58cd",
  "name" : "admin_internal_net",
  "admin_state_up" : true,
  "shared" : false,
  "router:external" : false,
  "provider:network_type" : "vxlan",
  "provider:segmentation_id" : "2",
  "status" : "ACTIVE",
  "segments" : [ ]
   }, {
  "id" : "bcba2ab6-44c8-411a-b021-439291f14c09",
  "tenant_id" : "ff9c3c34411a4edbb807b236a8ea20ef",
  "name" : "example-net",
  "admin_state_up" : true,
  "shared" : false,
  "router:external" : false,
  "provider:network_type" : "vxlan",
  "provider:segmentation_id" : "26",
  "status" : "ACTIVE",
  "segments" : [ ]
   } ]


Quoting "Manuel Buil" :


Is your ODL listening on: 192.168.0.9:8282?

Give me the output of:

curl -u admin:admin -H 'Content-type: application/json' -X GET http://1
92.168.0.9:8282/controller/nb/v2/neutron/networks

Regards,
Manuel


On Thu, 2017-07-20 at 14:06 +0200,
andres.sanchez.ra...@estudiant.upc.edu wrote:

Manuel,

I am deploying using fuel and ODL plug-in. You will find both files
in  
the attachement.

Regards,

Quoting "Manuel Buil" :

>
> Hi,
>
> I just checked your logs. It seems the ml2_conf.ini file is wrong.
> Are
> you deploying openstack using fuel and ODL plug-in? Can you post:
>
> /etc/neutron/neutron.conf
> /etc/neutron/plugins/ml2/ml2_conf.ini
>
> They are in the controller
>
> Regards,
> Manuel
>
> On Thu, 2017-07-20 at 12:34 +0200,
> andres.sanchez.ra...@estudiant.upc.edu wrote:
> >
> > Good morning to both!
> >
> > Manuel let me know if it is alright to post this issues on IRC
> > channel  
> > in case you are unable to help us! i am experiencing similar
> > issues
> > to  
> > Pavan. I am doing the setup using just one controller-ODL-tacker
> > and  
> > one compute-Cinder. My compute has only 2 cpu cores and 8 GB
> > memory  
> > (maybe this is not enough to hold the scenario), i understand
> > the  
> > scenario consists of 2 SFs, 1 client and 1 server. I am only
> > executing  
> > sfc_two_chains_SSH_and_HTTP.py.
> >
> > This is the relevant info of my sfc.log:
> >
> > 2017-07-20 09:20:59,069 - ovs_logger - ERROR - list index out of
> > range
> > 2017-07-20 09:20:59,072 - sfc.lib.utils - INFO - This is the
> > first_RSP:
> > 2017-07-20 09:20:59,281 - ovs_logger - ERROR - list index out of
> > range
> > 2017-07-20 09:20:59,284 - sfc.lib.utils - INFO - This is the
> > rsps:  
> > [u'0x4e', u'0x4e']
> > 2017-07-20 09:21:00,285 - sfc.lib.utils - INFO - classification
> > rules
> > updated
> > 2017-07-20 09:21:00,286 - functest_utils - INFO -  
> > wait_for_classification_rules(*( >   
> > object at 0x7f058c453750>,
> > [ > object at 0x7f059c25aed0>], 2), **{}) took: 1.40145111084 sec
> > 2017-07-20 09:21:06,518 - sfc.lib.utils - INFO - Instance name
> > and
> > ip  
> > ta-5164-beb5-4ac6-89fc-c8feefec494a-vdu1-
> > lgypmueg7aus:172.16.10.48
> > 2017-07-20 09:21:06,518 - sfc.lib.utils - INFO - Waiting for
> > instance  
> > ta-5164-beb5-4ac6-89fc-c8feefec494a-vdu1-
> > lgypmueg7aus:172.16.10.48
> > to  
> > come up
> > 2017-07-20 09:22:47,839 - sfc.lib.utils - INFO - Instance  
> > ta-5164-beb5-4ac6-89fc-c8feefec494a-vdu1-
> > lgypmueg7aus:172.16.10.48  
> > didn't come up
> > 2017-07-20 09:22:47,840 - __main__ - ERROR - Exception when
> > executing:  
> > sfc_two_chains_SSH_and_HTTP
> > 2017-07-20 09:22:47,840 - __main__ - ERROR - 'NoneType' object is
> > not
> > iterable
> > .
> > .
> > .
> > 2017-07-20 09:22:48,910 - __main__ - INFO - Results of test
> > case  
> > 'sfc_two_chains_SSH_and_HTTP - ODL-SFC tests':
> > {'status': 'FAILED'}
> >
> > 2017-07-20 09:22:49,308 - sfc.lib.cleanup - INFO - Removing sfc  
> > classifier: 2c63594c-1266-4162-b159-cde4575d8fd7
> > 2017-07-20 09:22:49,386 - sfc.lib.cleanup - INFO - Removing sfc  
> > classifier: 873a693d-345f-4569-af73-4910b7a00b5d
> > 2017-07-20 09:22:49,717 - sfc.lib.cleanup - INFO - Removing
> > sfc:  
> > 81debb08-a506-4ba9-bc13-4e3046f2b8e6
> > 2017-07-20 09:22:49,783 - sfc.lib.cleanup - INFO - Removing
> > sfc:  
> > e5a2b2f1-e53c-4745-8e90-943cd1c16c2e
> > 2017-07-20 09:22:50,147 - sfc.lib.cleanup - INFO - Removing
> > vnf:  
> > 4d837dae-d334-406f-8ce9-9c2997857838
> > 2017-07-20 09:22:50,785 - sfc.lib.cleanup - INFO - 

Re: [opnfv-tech-discuss] SFC Project

[andres . sanchez . ramos]

Manuel,

I am deploying using fuel and ODL plug-in. You will find both files in  
the attachement.


Regards,

Quoting "Manuel Buil" :


Hi,

I just checked your logs. It seems the ml2_conf.ini file is wrong. Are
you deploying openstack using fuel and ODL plug-in? Can you post:

/etc/neutron/neutron.conf
/etc/neutron/plugins/ml2/ml2_conf.ini

They are in the controller

Regards,
Manuel

On Thu, 2017-07-20 at 12:34 +0200,
andres.sanchez.ra...@estudiant.upc.edu wrote:

Good morning to both!

Manuel let me know if it is alright to post this issues on IRC
channel  
in case you are unable to help us! i am experiencing similar issues
to  
Pavan. I am doing the setup using just one controller-ODL-tacker
and  
one compute-Cinder. My compute has only 2 cpu cores and 8 GB memory  
(maybe this is not enough to hold the scenario), i understand the  
scenario consists of 2 SFs, 1 client and 1 server. I am only
executing  
sfc_two_chains_SSH_and_HTTP.py.

This is the relevant info of my sfc.log:

2017-07-20 09:20:59,069 - ovs_logger - ERROR - list index out of
range
2017-07-20 09:20:59,072 - sfc.lib.utils - INFO - This is the
first_RSP:
2017-07-20 09:20:59,281 - ovs_logger - ERROR - list index out of
range
2017-07-20 09:20:59,284 - sfc.lib.utils - INFO - This is the rsps:  
[u'0x4e', u'0x4e']
2017-07-20 09:21:00,285 - sfc.lib.utils - INFO - classification rules
updated
2017-07-20 09:21:00,286 - functest_utils - INFO -  
wait_for_classification_rules(*(, [], 2), **{}) took: 1.40145111084 sec
2017-07-20 09:21:06,518 - sfc.lib.utils - INFO - Instance name and
ip  
ta-5164-beb5-4ac6-89fc-c8feefec494a-vdu1-lgypmueg7aus:172.16.10.48
2017-07-20 09:21:06,518 - sfc.lib.utils - INFO - Waiting for
instance  
ta-5164-beb5-4ac6-89fc-c8feefec494a-vdu1-lgypmueg7aus:172.16.10.48
to  
come up
2017-07-20 09:22:47,839 - sfc.lib.utils - INFO - Instance  
ta-5164-beb5-4ac6-89fc-c8feefec494a-vdu1-lgypmueg7aus:172.16.10.48  
didn't come up
2017-07-20 09:22:47,840 - __main__ - ERROR - Exception when
executing:  
sfc_two_chains_SSH_and_HTTP
2017-07-20 09:22:47,840 - __main__ - ERROR - 'NoneType' object is not
iterable
.
.
.
2017-07-20 09:22:48,910 - __main__ - INFO - Results of test case  
'sfc_two_chains_SSH_and_HTTP - ODL-SFC tests':
{'status': 'FAILED'}

2017-07-20 09:22:49,308 - sfc.lib.cleanup - INFO - Removing sfc  
classifier: 2c63594c-1266-4162-b159-cde4575d8fd7
2017-07-20 09:22:49,386 - sfc.lib.cleanup - INFO - Removing sfc  
classifier: 873a693d-345f-4569-af73-4910b7a00b5d
2017-07-20 09:22:49,717 - sfc.lib.cleanup - INFO - Removing sfc:  
81debb08-a506-4ba9-bc13-4e3046f2b8e6
2017-07-20 09:22:49,783 - sfc.lib.cleanup - INFO - Removing sfc:  
e5a2b2f1-e53c-4745-8e90-943cd1c16c2e
2017-07-20 09:22:50,147 - sfc.lib.cleanup - INFO - Removing vnf:  
4d837dae-d334-406f-8ce9-9c2997857838
2017-07-20 09:22:50,785 - sfc.lib.cleanup - INFO - Removing vnf:  
d9ca5164-beb5-4ac6-89fc-c8feefec494a
2017-07-20 09:22:52,421 - sfc.lib.cleanup - INFO - Removing vnfd:  
33c9890a-4f22-4261-9351-be6376f41228
2017-07-20 09:22:52,467 - sfc.lib.cleanup - INFO - Removing vnfd:  
9c1012f0-9474-4b4c-b0c9-d2d05902311b
.
.
.

I dont see errors on my nova.log on the compute. But i have lots of  
errors in my neutron-server.log:

2017-07-20 09:21:06.556 1011 ERROR
networking_odl.ml2.network_topology  
[req-2564f0f0-51ca-4860-b739-7beed79c384e - - - - -] Network
topology  
element has failed binding port:
{
 "class":
"networking_odl.ml2.ovsdb_topology.OvsdbNetworkTopologyElement",
 "has_datapath_type_netdev": false,
 "host_addresses": [
 "192.168.0.6"
 ],
 "support_vhost_user": false,
 "uuid": "1c374e96-b809-434b-b540-2a3062ec04f6",
 "valid_vif_types": [
 "ovs"
 ]
}
2017-07-20 09:21:06.556 1011 ERROR
networking_odl.ml2.network_topology  
Traceback (most recent call last):
2017-07-20 09:21:06.556 1011 ERROR
networking_odl.ml2.network_topology  
   File  
"/usr/lib/python2.7/dist-
packages/networking_odl/ml2/network_topology.py",  
line 117, in bind_port
2017-07-20 09:21:06.556 1011 ERROR
networking_odl.ml2.network_topology  
 port_context, vif_type, self._vif_details)
2017-07-20 09:21:06.556 1011 ERROR
networking_odl.ml2.network_topology  
   File  
"/usr/lib/python2.7/dist-
packages/networking_odl/ml2/ovsdb_topology.py", line  
175, in bind_port
2017-07-20 09:21:06.556 1011 ERROR
networking_odl.ml2.network_topology  
 _('Unable to find any valid segment in given context.'))
2017-07-20 09:21:06.556 1011 ERROR
networking_odl.ml2.network_topology  
ValueError: Unable to find any valid segment in given context.
2017-07-20 09:21:06.556 1011 ERROR
networking_odl.ml2.network_topology
2017-07-20 09:21:06.561 1011 ERROR
networking_odl.ml2.network_topology  
[req-2564f0f0-51ca-4860-b739-7beed79c384e - - - - -] Unable to bind  
port element for given host and valid VIF types:

Re: [opnfv-tech-discuss] SFC Project

[andres . sanchez . ramos]

Hello Pavan,

I encountered similar errors in my SFC log, my script also gave an  
error when waiting the instance to come up but i have not been able to  
resolve it. Looking into your logs I think the problem is in Neutron  
so you should probably check Neutron logs, and also validate that you  
can manually start instances and assign floating IPs to them. I will  
let you know if i am able to resolve my issues.


Best regards,

Quoting "Pavan Gupta" :


Hi Andres,
I ran ‘functest openstack clean’ and that tool care of ‘SFC already  
exist’ error. The test ran further till it hit the following issue.  
In case, you have come across this issue, let me know.




SFC.log

2017-07-18 08:45:38,445 - ovs_logger - ERROR - list index out of range
2017-07-18 08:45:38,447 - sfc.lib.utils - INFO - This is the first_RSP:
2017-07-18 08:45:38,589 - ovs_logger - ERROR - list index out of range
2017-07-18 08:45:38,590 - sfc.lib.utils - INFO - These are the rsps:  
[u'0x24d']

2017-07-18 08:45:39,592 - sfc.lib.utils - INFO - classification rules updated
2017-07-18 08:45:39,592 - functest_utils - INFO -  
wait_for_classification_rules(*(object at 0x7f32305748d0>, [object at 0x7f3254435790>], 1), **{}) took: 1.26158809662 sec
2017-07-18 08:45:40,972 - sfc.lib.utils - INFO - Instance name and  
ip ta-1583-7563-4451-9c72-4401f96ca366-vdu1-x5gpjvyrdt6n:172.26.48.61
2017-07-18 08:45:40,973 - sfc.lib.utils - INFO - Waiting for  
instance  
ta-1583-7563-4451-9c72-4401f96ca366-vdu1-x5gpjvyrdt6n:172.26.48.61  
to come up
2017-07-18 08:47:28,837 - sfc.lib.utils - INFO - Instance  
ta-1583-7563-4451-9c72-4401f96ca366-vdu1-x5gpjvyrdt6n:172.26.48.61  
didn't come up
2017-07-18 08:47:28,837 - __main__ - ERROR - Exception when  
executing: sfc_one_chain_two_service_functions
2017-07-18 08:47:28,838 - __main__ - ERROR - 'NoneType' object is  
not iterable


Nova Log:

2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager  
[req-0dcc028d-b285-476e-a890-89a13dfd137f  
e7d3de05afef47ac9ead04257febcb70 517aa5fe041d47ba89b8d90be739e741 -  
- -] Instance failed network setup after 1 attempt(s)
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager Traceback  
(most recent call last):
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager   File  
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line  
1401, in _allocate_network_async
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager  
bind_host_id=bind_host_id)
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager   File  
"/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py",  
line 881, in allocate_for_instance
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager  
bind_host_id, dhcp_opts, available_macs)
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager   File  
"/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py",  
line 1000, in _update_ports_for_instance

2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager vif.destroy()
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager   File  
"/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220,  
in __exit__
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager  
self.force_reraise()
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager   File  
"/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196,  
in force_reraise
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager  
six.reraise(self.type_, self.value, self.tb)
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager   File  
"/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py",  
line 970, in _update_ports_for_instance
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager  
port_client, instance, port_id, port_req_body)
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager   File  
"/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py",  
line 437, in _update_port
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager  
_ensure_no_port_binding_failure(port)
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager   File  
"/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py",  
line 175, in _ensure_no_port_binding_failure
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager raise  
exception.PortBindingFailed(port_id=port['id'])
2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager  
PortBindingFailed: Binding failed for port  
c062c57e-95dc-4c7b-b7a6-0cc003b3a0db, please check neutron logs for  
more information.

2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager

Pavan


On 17-Jul-2017, at 7:14 PM, andres.sanchez.ra...@estudiant.upc.edu wrote:

Pavan,


I have not encountered those errors! It looks like there is already  
and SFC classifier already declared, but i thought that if you run  
the functest script it deleted anything that was previously  
declared. Maybe Manuel has any idea, i am still working on my  
scenario trying to set it up correctly.


Best regards,

Re: [opnfv-tech-discuss] SFC Project

[andres . sanchez . ramos]

Pavan,


I have not encountered those errors! It looks like there is already  
and SFC classifier already declared, but i thought that if you run the  
functest script it deleted anything that was previously declared.  
Maybe Manuel has any idea, i am still working on my scenario trying to  
set it up correctly.


Best regards,

Quoting "Pavan Gupta" :


HI Andres,
Thanks to your inputs, the test moved forward, though it failed.  
Here’s the log snippe. Let me know if you know how to fix this issue:


2017-07-17 12:24:16,434 - tacker_utils - ERROR - error  
[create_sfc(tacker_client, 'red', 'None', '['testVNF1',  
'testVNF2']')]: SFC with name red already exists!
2017-07-17 12:24:16,463 - tacker_utils - ERROR - error  
[create_sfc_classifier(tacker_client, 'red_http', 'None','red',  
'{'source_port': 0, 'protocol': 6, 'dest_port': 80}')]: 'SFC  
Classifier with name red_http already exists!’


2017-07-17 12:24:18,094 - ovs_logger - ERROR - list index out of range
2017-07-17 12:24:18,096 - sfc.lib.utils - INFO - This is the first_RSP:
2017-07-17 12:24:18,355 - ovs_logger - ERROR - list index out of range
2017-07-17 12:24:18,356 - sfc.lib.utils - INFO - These are the rsps: []
2017-07-17 12:24:19,435 - ovs_logger - ERROR - list index out of range
2017-07-17 12:24:19,437 - sfc.lib.utils - INFO - These are the rsps: []
2017-07-17 12:24:20,262 - sfc.lib.utils - INFO - Instance name and  
ip ta-8503-b3cf-4764-9894-f449e803e904-vdu1-ncexgzd3abmm:172.26.48.54
2017-07-17 12:24:20,263 - sfc.lib.utils - INFO - Waiting for  
instance  
ta-8503-b3cf-4764-9894-f449e803e904-vdu1-ncexgzd3abmm:172.26.48.54  
to come up


Pavan


On 17-Jul-2017, at 5:44 PM, andres.sanchez.ra...@estudiant.upc.edu wrote:

Hello Pavan,

I encountered a similar problem in my setting, it appears that the  
problem is that the configuration file is not updated with your  
installer IP address. So what i did was: edit the file  
"/home/opnfv/repos/sfc/sfc/tests/functest/config.yaml" and modify  
the installer IP address and cluster number. You can get the  
cluster number by executing the command "fuel node list" in your  
Fuel master machine.


I hope this helps you.

Best regards,

Quoting "Pavan Gupta" :


HI Andres,
I now hit issue related to 10.20.0.2 IP address. Though at time of  
starting the container I gave a different IP address, I see there  
are several files that have 10.20.0.2 IP address. Shouldn’t that  
change? This is where my script fails:

root@c8fc69ea9256:~# cat /home/opnfv/functest/results/sfc.log
2017-07-17 10:40:22,732 - SSH utils - ERROR - timed out
Traceback (most recent call last):
 File "./run_tests.py", line 189, in 
   main(report=args.report)
 File "./run_tests.py", line 81, in main
   installer_pwd=COMMON_CONFIG.installer_password)
 File  
"/home/opnfv/repos/releng/modules/opnfv/deployment/factory.py",  
line 43, in get_handler

   installer_pwd=installer_pwd)
 File  
"/home/opnfv/repos/releng/modules/opnfv/deployment/fuel/adapter.py", line  
26, in __init__

   pkey_file=None)
 File  
"/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py",  
line 332, in __init__

   'Cannot establish connection to the installer node!')
Exception: Cannot establish connection to the installer node!

Pavan


On 13-Jul-2017, at 6:35 PM, andres.sanchez.ra...@estudiant.upc.edu wrote:

Hello Manuel | Pavan,

The error where 10.20.0.2 occurs afterwards (when executing  
functest testcase run odl-sfc), for what I can see this is  
ocurring at executing "functest env prepare".


If I understand correctly this error is indicating that the  
machine where you are executing the test does not have  
connectivity to Openstack admin endpoints (which are located in  
the admin network you set up in Fuel - 192.168.0.0/24 by  
default). So it is probably a networking configuration issue: you  
must be either on the same network as openstack admin endpoints  
(192.168.0.0) or your networking equipment must be able to route  
packets to this network. In my setup I did not have any problem  
with iptables so if you are using fuel this is probably not the  
issue.


Best regards,

Quoting "Manuel Buil" :


Andres, can you explain Pavan what you did to solve your issue? I think
he is also hitting the error you found that 10.20.0.2 is hardcoded.

Thanks,
Manuel


On Thu, 2017-07-13 at 15:28 +0530, Pavan Gupta wrote:

> Ok. Any idea what needs to be done. I am trying things at my

side.Pavan


> > > On 12-Jul-2017, at 7:32 PM, Manuel Buil  wrote:
> Hey Pavan,
>
> > > > > The container must be able to contact the openstack  
environment,

otherwise it cannot trigger openstack actions. Do you have perhaps
a problem with iptables?

>
> Regards,
> Manuel
> On Wed, 2017-07-12 at 19:05 +0530, Pavan Gupta wrote:
> > Hi Manuel,
> > > > > I have deployed the setup for SFC Functest now. However, while

preparing the environment, I see the following error:

> >
> >
> > > 

Re: [opnfv-tech-discuss] SFC Project

[andres . sanchez . ramos]

Hello Pavan,

I encountered a similar problem in my setting, it appears that the  
problem is that the configuration file is not updated with your  
installer IP address. So what i did was: edit the file  
"/home/opnfv/repos/sfc/sfc/tests/functest/config.yaml" and modify the  
installer IP address and cluster number. You can get the cluster  
number by executing the command "fuel node list" in your Fuel master  
machine.


I hope this helps you.

Best regards,

Quoting "Pavan Gupta" :


HI Andres,
I now hit issue related to 10.20.0.2 IP address. Though at time of  
starting the container I gave a different IP address, I see there  
are several files that have 10.20.0.2 IP address. Shouldn’t that  
change? This is where my script fails:

root@c8fc69ea9256:~# cat /home/opnfv/functest/results/sfc.log
2017-07-17 10:40:22,732 - SSH utils - ERROR - timed out
Traceback (most recent call last):
  File "./run_tests.py", line 189, in 
main(report=args.report)
  File "./run_tests.py", line 81, in main
installer_pwd=COMMON_CONFIG.installer_password)
  File  
"/home/opnfv/repos/releng/modules/opnfv/deployment/factory.py", line  
43, in get_handler

installer_pwd=installer_pwd)
  File  
"/home/opnfv/repos/releng/modules/opnfv/deployment/fuel/adapter.py",  
line 26, in __init__

pkey_file=None)
  File  
"/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line  
332, in __init__

'Cannot establish connection to the installer node!')
Exception: Cannot establish connection to the installer node!

Pavan


On 13-Jul-2017, at 6:35 PM, andres.sanchez.ra...@estudiant.upc.edu wrote:

Hello Manuel | Pavan,

The error where 10.20.0.2 occurs afterwards (when executing  
functest testcase run odl-sfc), for what I can see this is ocurring  
at executing "functest env prepare".


If I understand correctly this error is indicating that the machine  
where you are executing the test does not have connectivity to  
Openstack admin endpoints (which are located in the admin network  
you set up in Fuel - 192.168.0.0/24 by default). So it is probably  
a networking configuration issue: you must be either on the same  
network as openstack admin endpoints (192.168.0.0) or your  
networking equipment must be able to route packets to this network.  
In my setup I did not have any problem with iptables so if you are  
using fuel this is probably not the issue.


Best regards,

Quoting "Manuel Buil" :


Andres, can you explain Pavan what you did to solve your issue? I think
he is also hitting the error you found that 10.20.0.2 is hardcoded.

Thanks,
Manuel


On Thu, 2017-07-13 at 15:28 +0530, Pavan Gupta wrote:

> Ok. Any idea what needs to be done. I am trying things at my

side.Pavan


> > > On 12-Jul-2017, at 7:32 PM, Manuel Buil  wrote:
> Hey Pavan,
>
> > > > > The container must be able to contact the openstack environment,

otherwise it cannot trigger openstack actions. Do you have perhaps
a problem with iptables?

>
> Regards,
> Manuel
> On Wed, 2017-07-12 at 19:05 +0530, Pavan Gupta wrote:
> > Hi Manuel,
> > > > > I have deployed the setup for SFC Functest now. However, while

preparing the environment, I see the following error:

> >
> >
> > > > > 2017-07-12 13:31:30,091 - prepare_env - INFO - >>Verifying

connectivity to the admin endpoint 192.168.0.2:35357...

> > > > > 2017-07-12 13:33:20,236 - prepare_env - ERROR - ERROR: Cannot

talk to the admin endpoint 192.168.0.2:35357 .

> > > > > 2017-07-12 13:33:20,236 - prepare_env - ERROR - Problem while

running 'check_os.sh'.
> > > > > > > > 2017-07-12 13:33:20,299 - functest_utils - ERROR  
- The command

'python /home/opnfv/repos/functest/functest/ci/prepare_env.py
start' failed.

> >
> >
> > > > > In case, you know if there is a fix for this issue,  
kindly let me

know.

> > Thanking you.
> > Regards,
> > Pavan
> >
> >
> > > > > > > On 11-Jul-2017, at 1:20 PM, Manuel Buil  
 wrote:

> > > Hello,
> > >
> > > > > > > Ok, if you are familiar with the fuel installer, then follow

this

> > > guide:
> > >
> > > > > > >  
https://wiki.opnfv.org/display/sfc/OPNFV-SFC+Functest+test+case

s

> > >
> > > Regards,
> > > Manuel
> > >
> > > On Mon, 2017-07-10 at 23:13 +0530, Pavan Gupta wrote:
> > > > Hi Manuel,
> > > > > > > > > Thank you for your reply. We are using Fuel installer to

create a

> > > > > > > > > setup within the company. In addition, we have access to

OPNFV

> > > > > > > > > community lab (Fuel Installer). I can try SFC in the

community lab if
> > > > > > > > > things are available. Kindly let me know what  
needs to be

done.

> > > > Pavan
> > > >
> > > > > > > > > > > > > > > > > On 10-Jul-2017, at 10:56 PM,  
Manuel Buil 

wrote:

> > > > >
> > > > > Hi Pavan,
> > > > >
> > > > > > > > > > > Yes, you can use OPNFV and the SFC project.  
When would you

like to
> > > > > > > > > > > deploy it? We are currently changing the  
platform and

moving 

Re: [opnfv-tech-discuss] SFC Project

[andres . sanchez . ramos]

Hello Manuel | Pavan,

The error where 10.20.0.2 occurs afterwards (when executing functest  
testcase run odl-sfc), for what I can see this is ocurring at  
executing "functest env prepare".


If I understand correctly this error is indicating that the machine  
where you are executing the test does not have connectivity to  
Openstack admin endpoints (which are located in the admin network you  
set up in Fuel - 192.168.0.0/24 by default). So it is probably a  
networking configuration issue: you must be either on the same network  
as openstack admin endpoints (192.168.0.0) or your networking  
equipment must be able to route packets to this network. In my setup I  
did not have any problem with iptables so if you are using fuel this  
is probably not the issue.


Best regards,

Quoting "Manuel Buil" :


Andres, can you explain Pavan what you did to solve your issue? I think
he is also hitting the error you found that 10.20.0.2 is hardcoded.

Thanks,
Manuel


On Thu, 2017-07-13 at 15:28 +0530, Pavan Gupta wrote:

> Ok. Any idea what needs to be done. I am trying things at my

side.Pavan


> > > On 12-Jul-2017, at 7:32 PM, Manuel Buil  wrote:
> Hey Pavan,
>
> > > > > The container must be able to contact the openstack environment,

otherwise it cannot trigger openstack actions. Do you have perhaps
a problem with iptables?

>
> Regards,
> Manuel
> On Wed, 2017-07-12 at 19:05 +0530, Pavan Gupta wrote:
> > Hi Manuel,
> > > > > I have deployed the setup for SFC Functest now. However, while

preparing the environment, I see the following error:

> >
> >
> > > > > 2017-07-12 13:31:30,091 - prepare_env - INFO - >>Verifying

connectivity to the admin endpoint 192.168.0.2:35357...

> > > > > 2017-07-12 13:33:20,236 - prepare_env - ERROR - ERROR: Cannot

talk to the admin endpoint 192.168.0.2:35357 .

> > > > > 2017-07-12 13:33:20,236 - prepare_env - ERROR - Problem while

running 'check_os.sh'.
> > > > > > > > 2017-07-12 13:33:20,299 - functest_utils - ERROR -  
The command

'python /home/opnfv/repos/functest/functest/ci/prepare_env.py
start' failed.

> >
> >
> > > > > In case, you know if there is a fix for this issue, kindly let me

know.

> > Thanking you.
> > Regards,
> > Pavan
> >
> >
> > > > > > > On 11-Jul-2017, at 1:20 PM, Manuel Buil  
 wrote:

> > > Hello,
> > >
> > > > > > > Ok, if you are familiar with the fuel installer, then follow

this

> > > guide:
> > >
> > > > > > >  
https://wiki.opnfv.org/display/sfc/OPNFV-SFC+Functest+test+case

s

> > >
> > > Regards,
> > > Manuel
> > >
> > > On Mon, 2017-07-10 at 23:13 +0530, Pavan Gupta wrote:
> > > > Hi Manuel,
> > > > > > > > > Thank you for your reply. We are using Fuel installer to

create a

> > > > > > > > > setup within the company. In addition, we have access to

OPNFV

> > > > > > > > > community lab (Fuel Installer). I can try SFC in the

community lab if

> > > > > > > > > things are available. Kindly let me know what needs to be

done.

> > > > Pavan
> > > >
> > > > > > > > > > > > > > > > > On 10-Jul-2017, at 10:56 PM,  
Manuel Buil 

wrote:

> > > > >
> > > > > Hi Pavan,
> > > > >
> > > > > > > > > > > Yes, you can use OPNFV and the SFC project.  
When would you

like to

> > > > > > > > > > > deploy it? We are currently changing the platform and

moving from

> > > > > fuel
> > > > > to openstack-ansible, however, we will not be ready before
> > > > > September.
> > > > >
> > > > > Are you familiar with the fuel installer?
> > > > >
> > > > > Regards,
> > > > > Manuel
> > > > >
> > > > > On Mon, 2017-07-10 at 18:23 +0530, Pavan Gupta wrote:
> > > > > > > > > > > > > I am Pavan Gupta from Calsoft Inc., Pune  
(India) and we

are

> > > > > > actively
> > > > > > > > > > > > > engaging ourselves with the OPNFV community and

development

> > > > > > projects.
> > > > > > > > > > > > > As part of this exercise, we are creating  
an OPNFV setup

and

> > > > > > would
> > > > > > > > > > > > > like to run sample VNFs and also service  
chain them

together. I

> > > > > > would
> > > > > > > > > > > > > like to understand from you if the SFC  
project can be

used to

> > > > > > create
> > > > > > a trial NFV system. 
> > > > > >
> > > > > > > > > > > > > Also, it would be helpful if you could share any

documents that

> > > > > > would
> > > > > > help us get started.
> > > > > > Thanking you.
> > > > > > Regards,
> > > > > > Pavan Gupta
> > > >
> > >
> >
>






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

Re: [opnfv-tech-discuss] OPNFV Danube SFC physical scenario deployment doubts

[andres . sanchez . ramos]

Manuel,

Thank you for your proposal it has been very helpful, i have already  
deployed the Openstack environment and it looks good, it passed the  
health check made by fuel, i also deployed a VM and connected to it  
successfully and have ODL up and running.


I am having a problem to make the functest because i am doing it  
inside a workstation that does not have access to the Openstack  
management network, it is located inside the public network. I am not  
sure which is the best way to proceed:


A) if I give the workstation an IP address inside the management  
network will it work? or maybe IP tables are configured to reject that.

B) Do the functest from my Fuel master (it is a PC that only runs Fuel).

I read the posts in your blog that you sent Rosa and found them  
extremely interesting, it has been very educative. I have some  
questions regarding that scenario that you built (If you have no  
problem answering them):

- What OS and application do you use for deploying the SF? do you use OVS?
- Once you deploy a SFC does tacker pushes the configuration to ODL  
via REST? or do you configure the SFF and SF manually on ODL?

- Do you have any more tutorials or videos similar?
- I have read that OVS+NSH implementation that you use is developed by  
OPNFV and is not mainstream in OVS. Is it possible to use that OVS+NSH  
on a physical device running openWRT?


I ask all this questions because we are interested in setting up a  
similar scenario!


Thank you in advance for your response.

Best regards,

Quoting "Manuel Buil" :


Hi Andres,

Please find my answers below.

Try to run the environment which is supported and after that you can
add stuff like ceilometer. Having a base that works should be your
target right now, later you can add stuff to that base.

Regards,
Manuel

On Mon, 2017-07-10 at 13:51 +0200,
andres.sanchez.ra...@estudiant.upc.edu wrote:

Hello Manuel,

Thank you for your quick response! you are right that scenario is
not  
supported sorry for that! I am trying to set up a NFV environment  
(using SFC) with the ability to monitor cloud resources using  
Openstack APIs, and according to what i have been able to read  
ceilometer provides that information!

Ok since no SFC chains are supposed to be declared i am guessing i
am  
close to deploying the scenario correctly, but i am having these  
issues (let me know if you how to address them):

- Once I create a VM I am not being able to access them (ping fails).


If you list the VM with 'nova list', does it say it is active? Does it
list an ip? Check that it receives an IP lease from the server with
nova console-log



- When I restart a compute node it will take an IP address from my  
public network and after that I cannot ssh into the node.


Strange... but why do you reboot a compute? Are you trying to test some
HA behaviour?



I have the following doubts regarding the deployment options being
set  
up in fuel:

- When creating the environment in fuel what networking option
should  
i choose: Neutron with ML2 plugin & Neutron with tunneling  
segmentation or OpenDaylight with tunneling segmentation?


If you want to try SFC, you should use OpenDaylight


- Right now i am choosing the following role distribution:  
controller-ceph, controller-tacker, controller-ODL, compute-ceph,  
compute-ceph. Is this appropriate?


Start with a simpler env. with one controller and one compute. The
controller should act as cotroller, OpenDaylight controller and Tacker
VNF Manager. Ceph should work but better simpligy things and use
'Cinder LVM'


- I am using the option that states: Assign public network to all  
nodes (I read in the guide that this should be checked). But i
think  
this is causing the communication issue to the nodes.


I have that option checked too but I never reboot computes ;)


- I install Open vSwitch with the checkbox that says install NSH.
Is  
this correct?


Yes


- When marking the ODL Plugin I only check the box that says: SFC  
features with NetVirt classifier. What about use ODL to manage L3  
traffic? should I mark it.


It is not needed for sfc. That one allows you to connect several
openstack deployments among them using L3VPN.


- Do I need to install any other features in ODL (i.e l2switch) in  
order to communicate with my VMs or do I need to declare some SFC  
chains?


Nothing else. When the deployment succeeds, you should be able to run
tests. To run them, you should follow this guide (note that we just
realized that Danube 2.0 is throwing errors... try Danube 1.0 instead):

https://wiki.opnfv.org/display/sfc/OPNFV-SFC+Functest+test+cases



Thank you in advance for your help, i tried to write as clear as i  
could but english is not my native tongue


You write very clearly!



Quoting "Manuel Buil" :

>
> Hi Andres,
>
> Unfortunately, that scenario is not supported in Danube. These are
> the
> ones supported:
>
> 

Re: [opnfv-tech-discuss] OPNFV Danube SFC physical scenario deployment doubts

[andres . sanchez . ramos]

Manuel,

Thanks again for the quick response. After looking through your  
answers I will delete my actual environment and deploy it again! Next  
you can find the answers to your questions:


If you list the VM with 'nova list', does it say it is active? Does it
list an ip? Check that it receives an IP lease from the server with
nova console-log
- Yes, they were active and had a floating IP assigned.

Strange... but why do you reboot a compute? Are you trying to test some
HA behaviour?
- I work on a couple of labs where other people have access so  
sometimes i find "strange" things, so I need to test that kind of  
behavior because it will happen eventually hahaha you know how that  
works.


If you want to try SFC, you should use OpenDaylight
- Ok, that is what i chose. I got confused because of instructions i  
found on this link:

http://opnfvdocsdemo.readthedocs.io/en/latest/submodules/fuel/docs/release/installation/installation.instruction.html
Select “Neutron with tunneling segmentation” (Required when using the  
ODL or ONOS plugins)


Start with a simpler env. with one controller and one compute. The
controller should act as cotroller, OpenDaylight controller and Tacker
VNF Manager. Ceph should work but better simpligy things and use
'Cinder LVM'
- Ok, I am on it

I will deploy an escenario as proposed and will get back to you, thank  
you very much for your help.


Quoting "Manuel Buil" :


Hi Andres,

Please find my answers below.

Try to run the environment which is supported and after that you can
add stuff like ceilometer. Having a base that works should be your
target right now, later you can add stuff to that base.

Regards,
Manuel

On Mon, 2017-07-10 at 13:51 +0200,
andres.sanchez.ra...@estudiant.upc.edu wrote:

Hello Manuel,

Thank you for your quick response! you are right that scenario is
not  
supported sorry for that! I am trying to set up a NFV environment  
(using SFC) with the ability to monitor cloud resources using  
Openstack APIs, and according to what i have been able to read  
ceilometer provides that information!

Ok since no SFC chains are supposed to be declared i am guessing i
am  
close to deploying the scenario correctly, but i am having these  
issues (let me know if you how to address them):

- Once I create a VM I am not being able to access them (ping fails).


If you list the VM with 'nova list', does it say it is active? Does it
list an ip? Check that it receives an IP lease from the server with
nova console-log



- When I restart a compute node it will take an IP address from my  
public network and after that I cannot ssh into the node.


Strange... but why do you reboot a compute? Are you trying to test some
HA behaviour?



I have the following doubts regarding the deployment options being
set  
up in fuel:

- When creating the environment in fuel what networking option
should  
i choose: Neutron with ML2 plugin & Neutron with tunneling  
segmentation or OpenDaylight with tunneling segmentation?


If you want to try SFC, you should use OpenDaylight


- Right now i am choosing the following role distribution:  
controller-ceph, controller-tacker, controller-ODL, compute-ceph,  
compute-ceph. Is this appropriate?


Start with a simpler env. with one controller and one compute. The
controller should act as cotroller, OpenDaylight controller and Tacker
VNF Manager. Ceph should work but better simpligy things and use
'Cinder LVM'


- I am using the option that states: Assign public network to all  
nodes (I read in the guide that this should be checked). But i
think  
this is causing the communication issue to the nodes.


I have that option checked too but I never reboot computes ;)


- I install Open vSwitch with the checkbox that says install NSH.
Is  
this correct?


Yes


- When marking the ODL Plugin I only check the box that says: SFC  
features with NetVirt classifier. What about use ODL to manage L3  
traffic? should I mark it.


It is not needed for sfc. That one allows you to connect several
openstack deployments among them using L3VPN.


- Do I need to install any other features in ODL (i.e l2switch) in  
order to communicate with my VMs or do I need to declare some SFC  
chains?


Nothing else. When the deployment succeeds, you should be able to run
tests. To run them, you should follow this guide (note that we just
realized that Danube 2.0 is throwing errors... try Danube 1.0 instead):

https://wiki.opnfv.org/display/sfc/OPNFV-SFC+Functest+test+cases



Thank you in advance for your help, i tried to write as clear as i  
could but english is not my native tongue


You write very clearly!



Quoting "Manuel Buil" :

>
> Hi Andres,
>
> Unfortunately, that scenario is not supported in Danube. These are
> the
> ones supported:
>
> https://wiki.opnfv.org/display/SWREL/Danube+Scenario+Status
>
> What statistics do you need from SFC? Maybe you can collect them in
> another way.
>
> When the sfc scenarios are successfully 

Re: [opnfv-tech-discuss] OPNFV Danube SFC physical scenario deployment doubts

[andres . sanchez . ramos]

Hello Manuel,

Thank you for your quick response! you are right that scenario is not  
supported sorry for that! I am trying to set up a NFV environment  
(using SFC) with the ability to monitor cloud resources using  
Openstack APIs, and according to what i have been able to read  
ceilometer provides that information!


Ok since no SFC chains are supposed to be declared i am guessing i am  
close to deploying the scenario correctly, but i am having these  
issues (let me know if you how to address them):


- Once I create a VM I am not being able to access them (ping fails).
- When I restart a compute node it will take an IP address from my  
public network and after that I cannot ssh into the node.


I have the following doubts regarding the deployment options being set  
up in fuel:


- When creating the environment in fuel what networking option should  
i choose: Neutron with ML2 plugin & Neutron with tunneling  
segmentation or OpenDaylight with tunneling segmentation?
- Right now i am choosing the following role distribution:  
controller-ceph, controller-tacker, controller-ODL, compute-ceph,  
compute-ceph. Is this appropriate?
- I am using the option that states: Assign public network to all  
nodes (I read in the guide that this should be checked). But i think  
this is causing the communication issue to the nodes.
- I install Open vSwitch with the checkbox that says install NSH. Is  
this correct?
- When marking the ODL Plugin I only check the box that says: SFC  
features with NetVirt classifier. What about use ODL to manage L3  
traffic? should I mark it.
- Do I need to install any other features in ODL (i.e l2switch) in  
order to communicate with my VMs or do I need to declare some SFC  
chains?


Thank you in advance for your help, i tried to write as clear as i  
could but english is not my native tongue


Quoting "Manuel Buil" :


Hi Andres,

Unfortunately, that scenario is not supported in Danube. These are the
ones supported:

https://wiki.opnfv.org/display/SWREL/Danube+Scenario+Status

What statistics do you need from SFC? Maybe you can collect them in
another way.

When the sfc scenarios are successfully deployed, no VMs or SFC chains
exist.

Regards,
Manuel


On Fri, 2017-07-07 at 10:58 +0200,
andres.sanchez.ra...@estudiant.upc.edu wrote:

Hello,

My name is Andrés Sánchez, i am working on deploying the OPNFV HA  
scenario on a laboratory on my university. I have been trying to  
deploy the scenario manually but have been encountering some
problems.  
My actual environment consists of:

5 Nodes: 2 CPUs, 8GB RAM.
1 Fuel master: 2 CPUs, 8GB RAM.
1 workstation: 2CPUs, 4GB RAM.

I am trying to deploy the  
"ha_odl-l2_sfc_heat_ceilometer_scenario.yaml" on this lab, i have  
previously deployed other Openstack scenarios on this lab so the  
networking configuration is properly configured: on each Openstack  
node port i assigned untagged traffic to PXE-admin, vlan 200 to
public  
network, and defaults to storage,management and private
(102,101,103).  
PXE-admin network is 192.168.100.0/24 and public network is  
172.16.10.0/24 with gateways being .1 respectively.

I already set up the fuel master with the Danube ISO  
"opnfv-danube.1.0.iso". I previously correctly deployed an
openstack  
cluster manually installing ODL and tacker plugins, but then i
found  
that did not appear to be correctly configured and neither ODL (I  
created a couple of VMs and could not connect to them). When
creating  
the environment which option is supposed to be selected: Neutron
with  
ML2 plugin & Neutron with tunneling segmentation or OpenDaylight
with  
tunneling segmentation. Another thing i found is that fuel did not  
provide the option for adding Telemetry-Mongo DB in node assignment
(i  
am requiring to have Telemetry because i need to check the meters
it  
provides). I did check the box for ?Assign public network to all
nodes?

I am trying to deploy now from my workstation but i have doubts  
regarding the way the DHA-DEA files are supposed to be written, i
am  
interested in:
A) Using the actual fuel master as fuel:

sudo bash ./deploy.sh -b file:///home/lab232/fuel/deploy/config -f
-l  
devel-pipeline -p lab232 -s  
ha_odl-l2_sfc_heat_ceilometer_scenario.yaml -i  
file:///home/lab232/opnfv-danube.1.0.iso -e

B) Create a VM inside my workstation to host Fuel master and use
all  
the other nodes as Openstack nodes.

sudo bash ./deploy.sh -b file:///home/lab232/fuel/deploy/config -F
-l  
devel-pipeline -p lab232 -s  
ha_odl-l2_sfc_heat_ceilometer_scenario.yaml -i  
file:///home/lab232/opnfv-danube.1.0.iso -e

For both scenarios i have encountered several issues an errors, i
am  
attaching the configuration files i use. Could you please provide
some  
guidance in the correct way to write these files.

When i try to deploy scenario A i am finding ipmi adapter errors:
Exception: Address lookup for None failed
Could not open socket!
Error: Unable to establish IPMI v2 / RMCP+ session

[opnfv-tech-discuss] OPNFV Danube SFC physical scenario deployment doubts

[andres . sanchez . ramos]

Hello,

My name is Andrés Sánchez, i am working on deploying the OPNFV HA  
scenario on a laboratory on my university. I have been trying to  
deploy the scenario manually but have been encountering some problems.  
My actual environment consists of:


5 Nodes: 2 CPUs, 8GB RAM.
1 Fuel master: 2 CPUs, 8GB RAM.
1 workstation: 2CPUs, 4GB RAM.

I am trying to deploy the  
"ha_odl-l2_sfc_heat_ceilometer_scenario.yaml" on this lab, i have  
previously deployed other Openstack scenarios on this lab so the  
networking configuration is properly configured: on each Openstack  
node port i assigned untagged traffic to PXE-admin, vlan 200 to public  
network, and defaults to storage,management and private (102,101,103).  
PXE-admin network is 192.168.100.0/24 and public network is  
172.16.10.0/24 with gateways being .1 respectively.


I already set up the fuel master with the Danube ISO  
"opnfv-danube.1.0.iso". I previously correctly deployed an openstack  
cluster manually installing ODL and tacker plugins, but then i found  
that did not appear to be correctly configured and neither ODL (I  
created a couple of VMs and could not connect to them). When creating  
the environment which option is supposed to be selected: Neutron with  
ML2 plugin & Neutron with tunneling segmentation or OpenDaylight with  
tunneling segmentation. Another thing i found is that fuel did not  
provide the option for adding Telemetry-Mongo DB in node assignment (i  
am requiring to have Telemetry because i need to check the meters it  
provides). I did check the box for ?Assign public network to all nodes?


I am trying to deploy now from my workstation but i have doubts  
regarding the way the DHA-DEA files are supposed to be written, i am  
interested in:

A) Using the actual fuel master as fuel:

sudo bash ./deploy.sh -b file:///home/lab232/fuel/deploy/config -f -l  
devel-pipeline -p lab232 -s  
ha_odl-l2_sfc_heat_ceilometer_scenario.yaml -i  
file:///home/lab232/opnfv-danube.1.0.iso -e


B) Create a VM inside my workstation to host Fuel master and use all  
the other nodes as Openstack nodes.


sudo bash ./deploy.sh -b file:///home/lab232/fuel/deploy/config -F -l  
devel-pipeline -p lab232 -s  
ha_odl-l2_sfc_heat_ceilometer_scenario.yaml -i  
file:///home/lab232/opnfv-danube.1.0.iso -e


For both scenarios i have encountered several issues an errors, i am  
attaching the configuration files i use. Could you please provide some  
guidance in the correct way to write these files.


When i try to deploy scenario A i am finding ipmi adapter errors:
Exception: Address lookup for None failed
Could not open socket!
Error: Unable to establish IPMI v2 / RMCP+ session

When i try to deploy scenario B i am finding: "Exception: Device  
"pxebr" does not exist." I am guessing i need to declare a bridge  
called pxebr on my host machine, please confirm.


I am attaching my Dea/Dha files!

One final question: when the environment is correctly deployed is  
openstack supposed to have some VMs declared? is ODL supposed to have  
any SFC paths or something declared?


Thank you in advance for your help!

Best regards,



dea-pod-override (1).yaml
Description: application/yaml


dha (1).yaml
Description: application/yaml
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss