Re: [openstack-dev] [Tacker] Unable to assign IP address to connection points.

2016-11-16 Thread HADDLETON, Robert W (Bob) 

Hi Prasad:
The first two things to check are:

1 - Check the VM instance in Horizon to confirm that there are three IP 
addresses assigned to it.  If there is only one IP address assigned to 
the VM, check the subnet configuration for the vnf_private and private 
networks and make sure they have DHCP enabled.


2 - Verify that the image you are using is configured to enable DHCP on 
eth1 and eth2 or their equivalent network interfaces.


If there ARE three IP addresses assigned to the VM from step 1 then it 
is likely that the image is not configured to support DHCP on eth1 and eth2.
You would need to either modify the image to enabled DHCP on eth1 and 
eth2 and then save the modified image, or find a new image that has DHCP 
enabled on those ports.


Hope this helps

Bob


On 11/16/2016 4:11 AM, prasad kokkula wrote:

Hi All,

[Tacker]   I have tried to launch the vnf Instance using Tacker. vnf 
is launched succesfully and able to do SSH.


I have faced the issue, the connection points (CP2, CP3) are not 
getting ip addreess except managament CP (CP1). Could you please let 
me know is this Tacker issue or any configuration mismatch.


I have installed openstack newton release on Centos 7. Please let me 
know if you need any other configuration.




=
Below are the net-list ip's

[root@localhost (keystone_admin)]# neutron net-list
+--+-+---+
| id   | name| subnets 
  |

+--+-+---+
| 55077c0e-8291-4730-99b4-f280967cb69e | public  | 
39256aad-d075-4c38-bf2c-14613df2252e 172.24.4.224/28 
  |
| 73bbaf70-9bdd-4359-a3a2-09dbd5734341 | private | 
09b9018c-ca3b-46ee-9a4e-507e5124139f 10.0.0.0/24 
  |
| d0560ee9-9ab0-4df8-a0d2-14064950a17c | vnf_mgmt  | 
01d2b67c-ee28-4875-92e0-a8e51fdf8401 192.168.200.0/24 
 |
| f98f38b8-8b6c-4adb-b0e9-a265ce969acf | vnf_private | 
61d39f59-2ff7-4292-afd9-536f007fd30c 192.168.201.0/24 
 |

+--+-+---+
[root@localhost (keystone_admin)]#

Tosca file used for vnf creation.


[root@localhost (keystone_admin)]# cat sample-vnfd.yaml

tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0

description: Demo vCPE example

metadata:
  template_name: sample-tosca-vnfd

topology_template:
  node_templates:
VDU1:
  type: tosca.nodes.nfv.VDU.Tacker
  capabilities:
nfv_compute:
  properties:
num_cpus: 1
mem_size: 512 MB
disk_size: 1 GB
  properties:
image: cirros1
availability_zone: nova
mgmt_driver: noop
user_data_format: RAW
config: |
  param0: key1
  param1: key2

CP1:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
management: true
  requirements:
- virtualLink:
node: VL1
- virtualBinding:
node: VDU1

CP2:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
anti_spoofing_protection: false
  requirements:
- virtualLink:
node: VL2
- virtualBinding:
node: VDU1

CP3:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
anti_spoofing_protection: false
  requirements:
- virtualLink:
node: VL3
- virtualBinding:
node: VDU1

VL1:
  type: tosca.nodes.nfv.VL
  properties:
network_name: vnf_mgmt
vendor: Tacker

VL2:
  type: tosca.nodes.nfv.VL
  properties:
network_name: vnf_private
vendor: Tacker

VL3:
  type: tosca.nodes.nfv.VL
  properties:
network_name: private
vendor: Tacker

===


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


<>__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Tacker] Unable to assign IP address to connection points.

2016-11-16 Thread prasad kokkula 
Hi All,

[Tacker]   I have tried to launch the vnf Instance using Tacker. vnf is
launched succesfully and able to do SSH.

I have faced the issue, the connection points (CP2, CP3) are not getting ip
addreess except managament CP (CP1). Could you please let me know is this
Tacker issue or any configuration mismatch.

I have installed openstack newton release on Centos 7. Please let me know
if you need any other configuration.




=
Below are the net-list ip's

[root@localhost (keystone_admin)]# neutron net-list
+--+-+--
-+
| id   | name| subnets
  |
+--+-+--
-+
| 55077c0e-8291-4730-99b4-f280967cb69e | public  |
39256aad-d075-4c38-bf2c-14613df2252e 172.24.4.224/28  |
| 73bbaf70-9bdd-4359-a3a2-09dbd5734341 | private |
09b9018c-ca3b-46ee-9a4e-507e5124139f 10.0.0.0/24  |
| d0560ee9-9ab0-4df8-a0d2-14064950a17c | vnf_mgmt|
01d2b67c-ee28-4875-92e0-a8e51fdf8401 192.168.200.0/24 |
| f98f38b8-8b6c-4adb-b0e9-a265ce969acf | vnf_private |
61d39f59-2ff7-4292-afd9-536f007fd30c 192.168.201.0/24 |
+--+-+--
-+
[root@localhost (keystone_admin)]#

Tosca file used for vnf creation.


[root@localhost (keystone_admin)]# cat sample-vnfd.yaml

tosca_definitions_version: tosca_simple_profile_for_nfv_1_0_0

description: Demo vCPE example

metadata:
  template_name: sample-tosca-vnfd

topology_template:
  node_templates:
VDU1:
  type: tosca.nodes.nfv.VDU.Tacker
  capabilities:
nfv_compute:
  properties:
num_cpus: 1
mem_size: 512 MB
disk_size: 1 GB
  properties:
image: cirros1
availability_zone: nova
mgmt_driver: noop
user_data_format: RAW
config: |
  param0: key1
  param1: key2

CP1:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
management: true
  requirements:
- virtualLink:
node: VL1
- virtualBinding:
node: VDU1

CP2:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
anti_spoofing_protection: false
  requirements:
- virtualLink:
node: VL2
- virtualBinding:
node: VDU1

CP3:
  type: tosca.nodes.nfv.CP.Tacker
  properties:
anti_spoofing_protection: false
  requirements:
- virtualLink:
node: VL3
- virtualBinding:
node: VDU1

VL1:
  type: tosca.nodes.nfv.VL
  properties:
network_name: vnf_mgmt
vendor: Tacker

VL2:
  type: tosca.nodes.nfv.VL
  properties:
network_name: vnf_private
vendor: Tacker

VL3:
  type: tosca.nodes.nfv.VL
  properties:
network_name: private
vendor: Tacker


===
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev