[openstack-dev] [Horizon] Can not connect to Openstack Dashboard
Hi all, I've installed Openstack Prod env with Fuel and I would like to customize the dashboard by using my own logo.png and logo-splash.png. I've changed all logo and logo-splash in these folders and restarted services apache2 and memcached : /usr/share/openstack-dashboard/openstack_dashboard/themes/vendor/static/img/ /var/lib/openstack-dashboard/static/themes/vendor/img/ /usr/lib/python2.7/dist-packages/openstack_dashboard/static/dashboard/img/ /var/lib/openstack-dashboard/static/dashboard/img/ After that I was able to connect to the dashboard with my customizations but few hours after I got the error in [1]. All others openstack services ares correctly running in commands lines. Someone knows what's wrong with my configurations ? How to customize the horizon to avoid such an error ? Best Regards, [1] http://paste.openstack.org/show/588038/ __ 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
Re: [openstack-dev] [networking-sfc][devstack][mitaka] Chain doesn't work
Any suggestion ?
On Monday, 24 October 2016, Alioune <baliou...@gmail.com> wrote:
> Hi all,
>
> I'm trying to implement service chain in OpenStack using networking-sfc
> (stable/mitaka) and OVS 2.5.90
>
>
> The following is the architecture I used :
>
> SRC DST
> ||
> == br-int
> |
>SF1
> SF1: 55.55.55.3
> SRC: 55.55.55.4
> DST: 55.55.55.5
>
> I can create port-pairs, port-pair-group, classifier and chain with these
> commands:
>
> neutron flow-classifier-create --ethertype IPv4 --source-ip-prefix
> 55.55.55.4/32 --logical-source-port 0009034f-4c39-4cbf-be7d-fcf82dad024c
> --protocol icmp FC1
> neutron port-pair-create --ingress=p1 --egress=p1 PP1
> neutron port-pair-group-create --port-pair PP1 PG1
> neutron port-chain-create --port-pair-group PG1 --flow-classifier FC1 PC1
>
> I could ping from SRC to DST before setting the chain, but after the chain
> creating ping doesn't work.
>
> ICMP echo request packets arrive to SF1 port but it doesn't send back the
> packets in order to allow them to get their destination DST (see output
> below).
>
> The Opendaylight/SFC project uses NSH aware service function (SF) that
> send back packets to the chains after analyzing them, I would like to know :
>
> - How networking-sfc configures SF to send back packets to the chain as
> seem in some of your presentation ?
> - What's wrong in my configurations (see commands and ovs-ofctl output
> below) ? I've followed the main steps described in your wiki page.
>
> Best Regards,
>
>
> vagrant@vagrant-ubuntu-trusty-64:~$ neutron port-list
> +--+--+-
> --+-
> -+
> | id | name | mac_address |
> fixed_ips
> |
> +--+--+-
> --+-
> -+
> | 0009034f-4c39-4cbf-be7d-fcf82dad024c | | fa:16:3e:dd:16:f7 |
> {"subnet_id": "8bf8a2e1-ecad-4b4b-beb1-d760a16667bc", "ip_address":
> "55.55.55.4"}|
> | 082e896d-5982-458c-96e7-0dd372d3d7d9 | p1 | fa:16:3e:90:b4:67 |
> {"subnet_id": "8bf8a2e1-ecad-4b4b-beb1-d760a16667bc", "ip_address":
> "55.55.55.3"}|
> | 2ad109e4-42a8-4554-b884-a32344e91036 | | fa:16:3e:74:9a:fa |
> {"subnet_id": "3cf6eb27-7258-4252-8f3d-b6f9d27c948b", "ip_address":
> "192.168.105.2"} |
> | 51f055c0-ff4d-47f4-9328-9a0d7ca204f3 | | fa:16:3e:da:f9:93 |
> {"subnet_id": "8bf8a2e1-ecad-4b4b-beb1-d760a16667bc", "ip_address":
> "55.55.55.1"}|
> | 656ad901-2bc0-407a-a581-da955ecf3b59 | | fa:16:3e:7f:44:01 |
> {"subnet_id": "8bf8a2e1-ecad-4b4b-beb1-d760a16667bc", "ip_address":
> "55.55.55.2"}|
> | b1d14a4f-cde6-4c44-b42e-0f0466dba32a | | fa:16:3e:a6:c6:35 |
> {"subnet_id": "8bf8a2e1-ecad-4b4b-beb1-d760a16667bc", "ip_address":
> "55.55.55.5"}|
> +--+--+-
> --+-
> -+
>
> vagrant@vagrant-ubuntu-trusty-64:~$ ifconfig |grep 082e896d
> qbr082e896d-59 Link encap:Ethernet HWaddr b6:96:27:fa:ab:af
> qvb082e896d-59 Link encap:Ethernet HWaddr b6:96:27:fa:ab:af
> qvo082e896d-59 Link encap:Ethernet HWaddr 7e:1a:7b:7d:09:df
> tap082e896d-59 Link encap:Ethernet HWaddr fe:16:3e:90:b4:67
>
> vagrant@vagrant-ubuntu-trusty-64:~$ sudo tcpdump -i tap082e896d-59 icmp
> tcpdump: WARNING: tap082e896d-59: no IPv4 address assigned
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on tap082e896d-59, link-type EN10MB (Ethernet), capture size
> 65535 bytes
> 10:51:10.229674 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
> seq 61, length 64
> 10:51:11.230318 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
> seq 62, length 64
> 10:51:12.233451 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
> seq 63, length 64
> 10:51:13.234496 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
> seq 64, length 64
> 10:51:14.235583 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
> seq 65, length 64
> 10:51:15.236585 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
> se
[openstack-dev] [networking-sfc][devstack][mitaka] Chain doesn't work
Hi all,
I'm trying to implement service chain in OpenStack using networking-sfc
(stable/mitaka) and OVS 2.5.90
The following is the architecture I used :
SRC DST
||
== br-int
|
SF1
SF1: 55.55.55.3
SRC: 55.55.55.4
DST: 55.55.55.5
I can create port-pairs, port-pair-group, classifier and chain with these
commands:
neutron flow-classifier-create --ethertype IPv4 --source-ip-prefix
55.55.55.4/32 --logical-source-port 0009034f-4c39-4cbf-be7d-fcf82dad024c
--protocol icmp FC1
neutron port-pair-create --ingress=p1 --egress=p1 PP1
neutron port-pair-group-create --port-pair PP1 PG1
neutron port-chain-create --port-pair-group PG1 --flow-classifier FC1 PC1
I could ping from SRC to DST before setting the chain, but after the chain
creating ping doesn't work.
ICMP echo request packets arrive to SF1 port but it doesn't send back the
packets in order to allow them to get their destination DST (see output
below).
The Opendaylight/SFC project uses NSH aware service function (SF) that send
back packets to the chains after analyzing them, I would like to know :
- How networking-sfc configures SF to send back packets to the chain as
seem in some of your presentation ?
- What's wrong in my configurations (see commands and ovs-ofctl output
below) ? I've followed the main steps described in your wiki page.
Best Regards,
vagrant@vagrant-ubuntu-trusty-64:~$ neutron port-list
+--+--+---+--+
| id | name | mac_address |
fixed_ips
|
+--+--+---+--+
| 0009034f-4c39-4cbf-be7d-fcf82dad024c | | fa:16:3e:dd:16:f7 |
{"subnet_id": "8bf8a2e1-ecad-4b4b-beb1-d760a16667bc", "ip_address":
"55.55.55.4"}|
| 082e896d-5982-458c-96e7-0dd372d3d7d9 | p1 | fa:16:3e:90:b4:67 |
{"subnet_id": "8bf8a2e1-ecad-4b4b-beb1-d760a16667bc", "ip_address":
"55.55.55.3"}|
| 2ad109e4-42a8-4554-b884-a32344e91036 | | fa:16:3e:74:9a:fa |
{"subnet_id": "3cf6eb27-7258-4252-8f3d-b6f9d27c948b", "ip_address":
"192.168.105.2"} |
| 51f055c0-ff4d-47f4-9328-9a0d7ca204f3 | | fa:16:3e:da:f9:93 |
{"subnet_id": "8bf8a2e1-ecad-4b4b-beb1-d760a16667bc", "ip_address":
"55.55.55.1"}|
| 656ad901-2bc0-407a-a581-da955ecf3b59 | | fa:16:3e:7f:44:01 |
{"subnet_id": "8bf8a2e1-ecad-4b4b-beb1-d760a16667bc", "ip_address":
"55.55.55.2"}|
| b1d14a4f-cde6-4c44-b42e-0f0466dba32a | | fa:16:3e:a6:c6:35 |
{"subnet_id": "8bf8a2e1-ecad-4b4b-beb1-d760a16667bc", "ip_address":
"55.55.55.5"}|
+--+--+---+--+
vagrant@vagrant-ubuntu-trusty-64:~$ ifconfig |grep 082e896d
qbr082e896d-59 Link encap:Ethernet HWaddr b6:96:27:fa:ab:af
qvb082e896d-59 Link encap:Ethernet HWaddr b6:96:27:fa:ab:af
qvo082e896d-59 Link encap:Ethernet HWaddr 7e:1a:7b:7d:09:df
tap082e896d-59 Link encap:Ethernet HWaddr fe:16:3e:90:b4:67
vagrant@vagrant-ubuntu-trusty-64:~$ sudo tcpdump -i tap082e896d-59 icmp
tcpdump: WARNING: tap082e896d-59: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on tap082e896d-59, link-type EN10MB (Ethernet), capture size
65535 bytes
10:51:10.229674 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
seq 61, length 64
10:51:11.230318 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
seq 62, length 64
10:51:12.233451 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
seq 63, length 64
10:51:13.234496 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
seq 64, length 64
10:51:14.235583 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
seq 65, length 64
10:51:15.236585 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
seq 66, length 64
10:51:16.237568 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
seq 67, length 64
10:51:17.238974 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
seq 68, length 64
10:51:18.244244 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
seq 69, length 64
10:51:19.245758 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
seq 70, length 64
10:51:20.246521 IP 55.55.55.4 > 55.55.55.5: ICMP echo request, id 15617,
seq 71, length 64
vagrant@vagrant-ubuntu-trusty-64:~/openstack_networking/simple-sf$ sudo
ovs-ofctl dump-flows br-int -O OpenFlow13
2016-10-24T11:28:43Z|1|ofp_actions|INFO|OFPAT_SET_MPLS_TTL is
deprecated in OpenFlow13 (use Set-Field)
OFPST_FLOW reply (OF1.3) (xid=0x2):
cookie=0xbbf3cb977f3738c7, duration=2418.957s, table=0, n_packets=2297,
n_bytes=225106,
[openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC
Hi all, Thanks Vincent for this confimation. I've noticed that error to the team here [1]. I think it could be interesting to update the wiki in order to signal new comer the network requirements for building a chain. @ Cathy: I can create port chain but it just works once for me. After analysing OVS entries, it's probably due to flows misconfiguration. Regards, [1] http://lists.openstack.org/pipermail/openstack-dev/2016- August/101817.html On 1 September 2016 at 04:42, Vincent.Chao <vincentcha...@gmail.com <javascript:_e(%7B%7D,'cvml','vincentcha...@gmail.com');>> wrote: > Hi Neutrons, > > I met this situation once in the release Liberty. > Here is the thing. > When the create_port_chain() is called, (@networking-sfc/networking_sf > c/services/sfc/drivers/ovs/driver.py) > it goes the following code path >-> _thread_update_path_nodes() >->_update_path_node_flowrules() >->_update_path_node_port_flowrules() >->_build_portchain_flowrule_body() >->_update_path_node_next_hops() >->_get_port_subnet_gw_info_by_port_id >->_get_port_subnet_gw_info()raise exc.SfcNoSubnetGateway > if you didn't give the network a router, it raises SfcNoSubnetGateway . > And then back to the plugin.py: create_port_chain(), cache the exception > sfc_exc.SfcDriverError as e > In this exception, there is a delete_port_chain() method. > But due to the synchronization problem between DB and ovs-bridge, it will > delete failure. > I hope this info. could help anyone who uses a liberty version. > Next time, don't forget giving a router before creating a port chain. > > I don't see this code path in the master branch. > It may be better in mitaka. > > Thanks > Vincent > > > > 2016-08-31 2:19 GMT+08:00 Cathy Zhang <cathy.h.zh...@huawei.com > <javascript:_e(%7B%7D,'cvml','cathy.h.zh...@huawei.com');>>: > >> Hi Alioune, >> >> >> >> It is weird that when you create a port chain, you get a “chain delete >> failed” error message. >> >> We never had this problem. Chain deletion is only involved when you do >> “delete chain” or “update chain”. >> >> Not sure which networking code file combination you are using or whether >> it is because your system is not properly cleaned up or not properly >> installed. >> >> We are going to release the networking-sfc mitaka version soon. >> >> I would suggest that you wait a little bit and then use the official >> released mitaka version and reinstall the feature on your system. >> >> >> >> Thanks, >> >> Cathy >> >> >> >> *From:* Alioune [mailto:baliou...@gmail.com >> <javascript:_e(%7B%7D,'cvml','baliou...@gmail.com');>] >> *Sent:* Tuesday, August 30, 2016 8:03 AM >> *To:* OpenStack Development Mailing List (not for usage questions) >> *Cc:* Cathy Zhang; Mohan Kumar; Henry Fourie >> *Subject:* Re: [openstack-dev][neutron][networking-sfc] Unable to create >> openstack SFC >> >> >> >> Hi, >> >> Have you received my previous email ? >> >> >> >> Regards, >> >> >> >> On 15 August 2016 at 13:39, Alioune <baliou...@gmail.com >> <javascript:_e(%7B%7D,'cvml','baliou...@gmail.com');>> wrote: >> >> Hi all, >> >> I'm trying to launch Openstack SFC as explained in[1] by creating 2 SFs, >> 1 Web Server (DST) and the DHCP namespace as the SRC. >> >> I've installed OVS (Open vSwitch) 2.3.90 with Linux kernel 3.13.0-62 and >> the neutron L2-agent runs correctly. >> >> I followed the process by creating classifier, port pairs and port_group >> but I got a wrong message "delete_port_chain failed." when creating >> port_chain [2] >> >> I tried to create the neutron ports with and without the option >> "--no-security-groups" then tcpdpump on SFs tap interfaces but the ICMP >> packets don't go through the SFs. >> >> >> >> Can anyone advice to fix? that ? >> >> What's your channel on IRC ? >> >> >> >> Regards, >> >> >> >> >> >> [1] https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining >> >> [2] >> >> vagrant@ubuntu:~/openstack_sfc$ ./08-os_create_port_chain.sh >> >> delete_port_chain failed. >> >> vagrant@ubuntu:~/openstack_sfc$ cat 08-os_create_port_chain.sh >> >> #!/bin/bash >> >> >> >> neutron port-chain-create --port-pair-group PG1 --port-pair-group PG2 >> --flow-classifier FC1 PC1 >> >> >> >> [3] Output OVS
Re: [openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC
Hi, Have you received my previous email ? Regards, On 15 August 2016 at 13:39, Alioune <baliou...@gmail.com> wrote: > Hi all, > I'm trying to launch Openstack SFC as explained in[1] by creating 2 SFs, 1 > Web Server (DST) and the DHCP namespace as the SRC. > I've installed OVS (Open vSwitch) 2.3.90 with Linux kernel 3.13.0-62 and > the neutron L2-agent runs correctly. > I followed the process by creating classifier, port pairs and port_group > but I got a wrong message "delete_port_chain failed." when creating > port_chain [2] > I tried to create the neutron ports with and without the option > "--no-security-groups" then tcpdpump on SFs tap interfaces but the ICMP > packets don't go through the SFs. > > Can anyone advice to fix? that ? > What's your channel on IRC ? > > Regards, > > > [1] https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining > [2] > vagrant@ubuntu:~/openstack_sfc$ ./08-os_create_port_chain.sh > delete_port_chain failed. > vagrant@ubuntu:~/openstack_sfc$ cat 08-os_create_port_chain.sh > #!/bin/bash > > neutron port-chain-create --port-pair-group PG1 --port-pair-group PG2 > --flow-classifier FC1 PC1 > > [3] Output OVS Flows > > vagrant@ubuntu:~$ sudo ovs-ofctl dump-flows br-tun -O OpenFlow13 > OFPST_FLOW reply (OF1.3) (xid=0x2): > cookie=0xbc2e9105125301dc, duration=9615.385s, table=0, n_packets=146, > n_bytes=11534, priority=1,in_port=1 actions=resubmit(,2) > cookie=0xbc2e9105125301dc, duration=9615.382s, table=0, n_packets=0, > n_bytes=0, priority=0 actions=drop > cookie=0xbc2e9105125301dc, duration=9615.382s, table=2, n_packets=5, > n_bytes=490, priority=0,dl_dst=00:00:00:00:00:00/01:00:00:00:00:00 > actions=resubmit(,20) > cookie=0xbc2e9105125301dc, duration=9615.381s, table=2, n_packets=141, > n_bytes=11044, priority=0,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00 > actions=resubmit(,22) > cookie=0xbc2e9105125301dc, duration=9615.380s, table=3, n_packets=0, > n_bytes=0, priority=0 actions=drop > cookie=0xbc2e9105125301dc, duration=9615.380s, table=4, n_packets=0, > n_bytes=0, priority=0 actions=drop > cookie=0xbc2e9105125301dc, duration=8617.106s, table=4, n_packets=0, > n_bytes=0, priority=1,tun_id=0x40e actions=push_vlan:0x8100,set_ > field:4097->vlan_vid,resubmit(,10) > cookie=0xbc2e9105125301dc, duration=9615.379s, table=6, n_packets=0, > n_bytes=0, priority=0 actions=drop > cookie=0xbc2e9105125301dc, duration=9615.379s, table=10, n_packets=0, > n_bytes=0, priority=1 actions=learn(table=20,hard_ > timeout=300,priority=1,cookie=0xbc2e9105125301dc,NXM_OF_ > VLAN_TCI[0..11],NXM_OF_ETH_DST[]=NXM_OF_ETH_SRC[],load:0- > >NXM_OF_VLAN_TCI[],load:NXM_NX_TUN_ID[]->NXM_NX_TUN_ID[], > output:NXM_OF_IN_PORT[]),output:1 > cookie=0xbc2e9105125301dc, duration=9615.378s, table=20, n_packets=5, > n_bytes=490, priority=0 actions=resubmit(,22) > cookie=0xbc2e9105125301dc, duration=9615.342s, table=22, n_packets=146, > n_bytes=11534, priority=0 actions=drop > vagrant@ubuntu:~$ sudo ovs-ofctl dump-flows br-int -O OpenFlow13 > OFPST_FLOW reply (OF1.3) (xid=0x2): > cookie=0xbc2e9105125301dc, duration=6712.090s, table=0, n_packets=0, > n_bytes=0, priority=10,icmp6,in_port=7,icmp_type=136 actions=resubmit(,24) > cookie=0xbc2e9105125301dc, duration=6709.623s, table=0, n_packets=0, > n_bytes=0, priority=10,icmp6,in_port=8,icmp_type=136 actions=resubmit(,24) > cookie=0xbc2e9105125301dc, duration=6555.755s, table=0, n_packets=0, > n_bytes=0, priority=10,icmp6,in_port=10,icmp_type=136 > actions=resubmit(,24) > cookie=0xbc2e9105125301dc, duration=6559.596s, table=0, n_packets=0, > n_bytes=0, priority=10,icmp6,in_port=9,icmp_type=136 actions=resubmit(,24) > cookie=0xbc2e9105125301dc, duration=6461.028s, table=0, n_packets=0, > n_bytes=0, priority=10,icmp6,in_port=11,icmp_type=136 > actions=resubmit(,24) > cookie=0xbc2e9105125301dc, duration=6712.071s, table=0, n_packets=13, > n_bytes=546, priority=10,arp,in_port=7 actions=resubmit(,24) > cookie=0xbc2e9105125301dc, duration=6709.602s, table=0, n_packets=0, > n_bytes=0, priority=10,arp,in_port=8 actions=resubmit(,24) > cookie=0xbc2e9105125301dc, duration=6555.727s, table=0, n_packets=0, > n_bytes=0, priority=10,arp,in_port=10 actions=resubmit(,24) > cookie=0xbc2e9105125301dc, duration=6559.574s, table=0, n_packets=12, > n_bytes=504, priority=10,arp,in_port=9 actions=resubmit(,24) > cookie=0xbc2e9105125301dc, duration=6461.005s, table=0, n_packets=15, > n_bytes=630, priority=10,arp,in_port=11 actions=resubmit(,24) > cookie=0xbc2e9105125301dc, duration=9620.388s, table=0, n_packets=514, > n_bytes=49656, priority=0 actions=NORMAL > cookie=0xbc2e9105125301dc, duration=9619.277s, table=0, n_packets=0, > n_bytes=0, priority=2
Re: [openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC
mpls:0x8847,set_field:65791->mpls_label,set_mpls_ttl(255),push_vlan:0x8100,set_field:4097->vlan_vid,set_field:fa:16:3e:8f:83:a7->eth_src,resubmit(,10) cookie=0x990756dc81846819, duration=660.097s, table=5, n_packets=0, n_bytes=0, priority=0,dl_dst=fa:16:3e:9b:2b:91 actions=push_mpls:0x8847,set_field:65790->mpls_label,set_mpls_ttl(254),push_vlan:0x8100,set_field:4097->vlan_vid,set_field:fa:16:3e:8f:83:a7->eth_src,resubmit(,10) [3] sudo tcpdump -i tap9ee874fc-aa tcpdump: WARNING: tap9ee874fc-aa: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on tap9ee874fc-aa, link-type EN10MB (Ethernet), capture size 65535 bytes 20:14:07.965348 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 82, length 64 20:14:08.967031 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 83, length 64 20:14:09.968351 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 84, length 64 20:14:10.969454 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 85, length 64 20:14:11.970705 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 86, length 64 20:14:12.972184 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 87, length 64 20:14:13.973142 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 88, length 64 20:14:14.974222 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 89, length 64 20:14:15.975291 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 90, length 64 20:14:16.976012 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 91, length 64 20:14:17.977478 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 92, length 64 20:14:18.978457 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 93, length 64 20:14:19.979777 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 94, length 64 20:14:20.980652 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 95, length 64 20:14:21.982147 IP 55.55.55.8 > 55.55.55.7: ICMP echo request, id 22017, seq 96, length 64 On 18 August 2016 at 08:46, Mohan Kumar <nmohankumar1...@gmail.com> wrote: > Hi Alioune, > > You can remove security - groups after launching VM too . If you still > facing issues in sfc setup please ping me over IRC ( channel : > *#openstack-neutron > *name:* mohankumar **). * I believe that is the fastest way to sync-up. > > > Thanks., > Mohankumar.N > > On Wed, Aug 17, 2016 at 7:28 PM, Alioune <baliou...@gmail.com> wrote: > >> Hi Muhata, >> Should I do these before launching the SFs or they could be done afer ? >> I run these command on all ports from p1 to p4 and neutron port-show pi >> for each pi port show : port_security_enabled : Falseand >> security_groups : ' ' . >> But I still can not snif packets >> >> On 17 August 2016 at 15:30, Mohan Kumar <nmohankumar1...@gmail.com> >> wrote: >> >>> Alioune, >>> >>> tcpdump in SF ingress / egress tap interfaces will show packets flows . >>> I guess the packet not going through SFs . >>> >>> You may check flow_rules packet counter and actions >>> field (actions=drop) on br_int to find where the packet actually get >>> dropping . >>> >>> Please make sure you disabled security groups on SF attached ports : >>> >>> neutron port-update --no-security-groups >>> neutron port-update --port-security-enabled=False >>> >>> Thanks., >>> Mohankumar.N >>> >>> On Wed, Aug 17, 2016 at 6:01 PM, Alioune <baliou...@gmail.com> wrote: >>> >>>> Hi all, >>>> I've solved the error. >>>> In fact I did not create a router attached to the tenant subnet and >>>> according to neutron logs that was the first exception raised while >>>> creating port-chain. >>>> Now the port-chain has been created and some flows entries have been >>>> pushed in br-int. I think I could be interesting to update the wiki. >>>> >>>> When running a ping from the source to the dst, I can see ICMP (request >>>> and reply) packets from the Tap interface of the source but I can not see >>>> them in the Taps of SFs. >>>> Is there a way to display packets (with wireshark or tcpdump ) going >>>> inbout and outbount of the SFs ? >>>> >>>> Regards, >>>> >>>> On 16 August 2016 at 16:06, Mohan Kumar <nmohankumar1...@gmail.com> >>>> wrote: >>>> >>>>> Hi Alioune, >>>>> >>>>> Could you share neutron log as well ? also let us know your sfc code >>>>> ba
Re: [openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC
Hi all, I've solved the error. In fact I did not create a router attached to the tenant subnet and according to neutron logs that was the first exception raised while creating port-chain. Now the port-chain has been created and some flows entries have been pushed in br-int. I think I could be interesting to update the wiki. When running a ping from the source to the dst, I can see ICMP (request and reply) packets from the Tap interface of the source but I can not see them in the Taps of SFs. Is there a way to display packets (with wireshark or tcpdump ) going inbout and outbount of the SFs ? Regards, On 16 August 2016 at 16:06, Mohan Kumar <nmohankumar1...@gmail.com> wrote: > Hi Alioune, > > Could you share neutron log as well ? also let us know your sfc code > base., If possible shall we have quick chat on this in neutron IRC channel ? > > Thanks., > Mohankumar.N > > On Mon, Aug 15, 2016 at 5:09 PM, Alioune <baliou...@gmail.com> wrote: > >> Hi all, >> I'm trying to launch Openstack SFC as explained in[1] by creating 2 SFs, >> 1 Web Server (DST) and the DHCP namespace as the SRC. >> I've installed OVS (Open vSwitch) 2.3.90 with Linux kernel 3.13.0-62 and >> the neutron L2-agent runs correctly. >> I followed the process by creating classifier, port pairs and port_group >> but I got a wrong message "delete_port_chain failed." when creating >> port_chain [2] >> I tried to create the neutron ports with and without the option >> "--no-security-groups" then tcpdpump on SFs tap interfaces but the ICMP >> packets don't go through the SFs. >> >> Can anyone advice to fix? that ? >> What's your channel on IRC ? >> >> Regards, >> >> >> [1] https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining >> [2] >> vagrant@ubuntu:~/openstack_sfc$ ./08-os_create_port_chain.sh >> delete_port_chain failed. >> vagrant@ubuntu:~/openstack_sfc$ cat 08-os_create_port_chain.sh >> #!/bin/bash >> >> neutron port-chain-create --port-pair-group PG1 --port-pair-group PG2 >> --flow-classifier FC1 PC1 >> >> [3] Output OVS Flows >> >> vagrant@ubuntu:~$ sudo ovs-ofctl dump-flows br-tun -O OpenFlow13 >> OFPST_FLOW reply (OF1.3) (xid=0x2): >> cookie=0xbc2e9105125301dc, duration=9615.385s, table=0, n_packets=146, >> n_bytes=11534, priority=1,in_port=1 actions=resubmit(,2) >> cookie=0xbc2e9105125301dc, duration=9615.382s, table=0, n_packets=0, >> n_bytes=0, priority=0 actions=drop >> cookie=0xbc2e9105125301dc, duration=9615.382s, table=2, n_packets=5, >> n_bytes=490, priority=0,dl_dst=00:00:00:00:00:00/01:00:00:00:00:00 >> actions=resubmit(,20) >> cookie=0xbc2e9105125301dc, duration=9615.381s, table=2, n_packets=141, >> n_bytes=11044, priority=0,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00 >> actions=resubmit(,22) >> cookie=0xbc2e9105125301dc, duration=9615.380s, table=3, n_packets=0, >> n_bytes=0, priority=0 actions=drop >> cookie=0xbc2e9105125301dc, duration=9615.380s, table=4, n_packets=0, >> n_bytes=0, priority=0 actions=drop >> cookie=0xbc2e9105125301dc, duration=8617.106s, table=4, n_packets=0, >> n_bytes=0, priority=1,tun_id=0x40e actions=push_vlan:0x8100,set_f >> ield:4097->vlan_vid,resubmit(,10) >> cookie=0xbc2e9105125301dc, duration=9615.379s, table=6, n_packets=0, >> n_bytes=0, priority=0 actions=drop >> cookie=0xbc2e9105125301dc, duration=9615.379s, table=10, n_packets=0, >> n_bytes=0, priority=1 actions=learn(table=20,hard_ti >> meout=300,priority=1,cookie=0xbc2e9105125301dc,NXM_OF_VLAN_ >> TCI[0..11],NXM_OF_ETH_DST[]=NXM_OF_ETH_SRC[],load:0->NXM_ >> OF_VLAN_TCI[],load:NXM_NX_TUN_ID[]->NXM_NX_TUN_ID[],output: >> NXM_OF_IN_PORT[]),output:1 >> cookie=0xbc2e9105125301dc, duration=9615.378s, table=20, n_packets=5, >> n_bytes=490, priority=0 actions=resubmit(,22) >> cookie=0xbc2e9105125301dc, duration=9615.342s, table=22, n_packets=146, >> n_bytes=11534, priority=0 actions=drop >> vagrant@ubuntu:~$ sudo ovs-ofctl dump-flows br-int -O OpenFlow13 >> OFPST_FLOW reply (OF1.3) (xid=0x2): >> cookie=0xbc2e9105125301dc, duration=6712.090s, table=0, n_packets=0, >> n_bytes=0, priority=10,icmp6,in_port=7,icmp_type=136 >> actions=resubmit(,24) >> cookie=0xbc2e9105125301dc, duration=6709.623s, table=0, n_packets=0, >> n_bytes=0, priority=10,icmp6,in_port=8,icmp_type=136 >> actions=resubmit(,24) >> cookie=0xbc2e9105125301dc, duration=6555.755s, table=0, n_packets=0, >> n_bytes=0, priority=10,icmp6,in_port=10,icmp_type=136 >> actions=resubmit(,24) >> cookie=0xbc2e9105125301dc, duration=6559.596s, table=0, n_packets=0
Re: [openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC
rt_chains.json -H "User-Agent:
python-neutronclient" -H "Content-Type: application/json" -H "Accept:
application/json" -H "X-Auth-Token:
{SHA1}b64a4351e9ee74a640d7070a3a16db1961215260" -d '{"port_chain":
{"flow_classifiers": ["020a9ceb-3451-47af-ba09-650202009217"], "name":
"PC1", "port_pair_groups": ["128aee07-96b7-45cd-9090-699a60e57bf4",
"d4f47717-2dd0-4c2f-84a2-469802c0c922"]}}'
DEBUG: keystoneclient.session RESP: [500] Date: Mon, 15 Aug 2016 14:36:03
GMT Connection: keep-alive Content-Type: application/json; charset=UTF-8
Content-Length: 98 X-Openstack-Request-Id:
req-5f9778ab-90c7-4434-ae0b-0a2ee10505e9
RESP BODY: {"NeutronError": {"message": "delete_port_chain failed.",
"type": "SfcDriverError", "detail": ""}}
DEBUG: neutronclient.v2_0.client Error message: {"NeutronError":
{"message": "delete_port_chain failed.", "type": "SfcDriverError",
"detail": ""}}
ERROR: neutronclient.shell delete_port_chain failed.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/neutronclient/shell.py",
line 814, in run_subcommand
return run_command(cmd, cmd_parser, sub_argv)
File "/usr/local/lib/python2.7/dist-packages/neutronclient/shell.py",
line 110, in run_command
return cmd.run(known_args)
File
"/usr/local/lib/python2.7/dist-packages/neutronclient/common/command.py",
line 29, in run
return super(OpenStackCommand, self).run(parsed_args)
File "/usr/local/lib/python2.7/dist-packages/cliff/display.py", line 92,
in run
column_names, data = self.take_action(parsed_args)
File
"/usr/local/lib/python2.7/dist-packages/neutronclient/common/command.py",
line 35, in take_action
return self.get_data(parsed_args)
File
"/usr/local/lib/python2.7/dist-packages/neutronclient/common/extension.py",
line 72, in get_data
return self.execute(parsed_args)
File
"/usr/local/lib/python2.7/dist-packages/neutronclient/common/extension.py",
line 75, in execute
return super(ClientExtensionCreate, self).get_data(parsed_args)
File
"/usr/local/lib/python2.7/dist-packages/neutronclient/neutron/v2_0/__init__.py",
line 500, in get_data
data = obj_creator(body)
File
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line
1735, in _fx
return self.create_ext(path, body)
File
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line
102, in with_params
ret = self.function(instance, *args, **kwargs)
File
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line
492, in create_ext
return self.post(path, body=body)
File
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line
298, in post
headers=headers, params=params)
File
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line
211, in do_request
self._handle_fault_response(status_code, replybody)
File
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line
185, in _handle_fault_response
exception_handler_v20(status_code, des_error_body)
File
"/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line
70, in exception_handler_v20
status_code=status_code)
InternalServerError: delete_port_chain failed.
On 15 August 2016 at 13:39, Alioune <baliou...@gmail.com> wrote:
> Hi all,
> I'm trying to launch Openstack SFC as explained in[1] by creating 2 SFs, 1
> Web Server (DST) and the DHCP namespace as the SRC.
> I've installed OVS (Open vSwitch) 2.3.90 with Linux kernel 3.13.0-62 and
> the neutron L2-agent runs correctly.
> I followed the process by creating classifier, port pairs and port_group
> but I got a wrong message "delete_port_chain failed." when creating
> port_chain [2]
> I tried to create the neutron ports with and without the option
> "--no-security-groups" then tcpdpump on SFs tap interfaces but the ICMP
> packets don't go through the SFs.
>
> Can anyone advice to fix? that ?
> What's your channel on IRC ?
>
> Regards,
>
>
> [1] https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining
> [2]
> vagrant@ubuntu:~/openstack_sfc$ ./08-os_create_port_chain.sh
> delete_port_chain failed.
> vagrant@ubuntu:~/openstack_sfc$ cat 08-os_create_port_chain.sh
> #!/bin/bash
>
> neutron port-chain-create --port-pair-group PG1 --port-pair-group PG2
> --flow-classifier FC1 PC1
>
> [3] Output OVS Flows
>
> vagrant@ubuntu:~$ sudo ovs-ofctl dump-flows br-tun -O OpenFlow13
> OFPST_FLOW reply (OF1.3) (xid=0x2):
> cookie=0xbc2e91051253
[openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC
Hi all, I'm trying to launch Openstack SFC as explained in[1] by creating 2 SFs, 1 Web Server (DST) and the DHCP namespace as the SRC. I've installed OVS (Open vSwitch) 2.3.90 with Linux kernel 3.13.0-62 and the neutron L2-agent runs correctly. I followed the process by creating classifier, port pairs and port_group but I got a wrong message "delete_port_chain failed." when creating port_chain [2] I tried to create the neutron ports with and without the option "--no-security-groups" then tcpdpump on SFs tap interfaces but the ICMP packets don't go through the SFs. Can anyone advice to fix? that ? What's your channel on IRC ? Regards, [1] https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining [2] vagrant@ubuntu:~/openstack_sfc$ ./08-os_create_port_chain.sh delete_port_chain failed. vagrant@ubuntu:~/openstack_sfc$ cat 08-os_create_port_chain.sh #!/bin/bash neutron port-chain-create --port-pair-group PG1 --port-pair-group PG2 --flow-classifier FC1 PC1 [3] Output OVS Flows vagrant@ubuntu:~$ sudo ovs-ofctl dump-flows br-tun -O OpenFlow13 OFPST_FLOW reply (OF1.3) (xid=0x2): cookie=0xbc2e9105125301dc, duration=9615.385s, table=0, n_packets=146, n_bytes=11534, priority=1,in_port=1 actions=resubmit(,2) cookie=0xbc2e9105125301dc, duration=9615.382s, table=0, n_packets=0, n_bytes=0, priority=0 actions=drop cookie=0xbc2e9105125301dc, duration=9615.382s, table=2, n_packets=5, n_bytes=490, priority=0,dl_dst=00:00:00:00:00:00/01:00:00:00:00:00 actions=resubmit(,20) cookie=0xbc2e9105125301dc, duration=9615.381s, table=2, n_packets=141, n_bytes=11044, priority=0,dl_dst=01:00:00:00:00:00/01:00:00:00:00:00 actions=resubmit(,22) cookie=0xbc2e9105125301dc, duration=9615.380s, table=3, n_packets=0, n_bytes=0, priority=0 actions=drop cookie=0xbc2e9105125301dc, duration=9615.380s, table=4, n_packets=0, n_bytes=0, priority=0 actions=drop cookie=0xbc2e9105125301dc, duration=8617.106s, table=4, n_packets=0, n_bytes=0, priority=1,tun_id=0x40e actions=push_vlan:0x8100,set_field:4097->vlan_vid,resubmit(,10) cookie=0xbc2e9105125301dc, duration=9615.379s, table=6, n_packets=0, n_bytes=0, priority=0 actions=drop cookie=0xbc2e9105125301dc, duration=9615.379s, table=10, n_packets=0, n_bytes=0, priority=1 actions=learn(table=20,hard_timeout=300,priority=1,cookie=0xbc2e9105125301dc,NXM_OF_VLAN_TCI[0..11],NXM_OF_ETH_DST[]=NXM_OF_ETH_SRC[],load:0->NXM_OF_VLAN_TCI[],load:NXM_NX_TUN_ID[]->NXM_NX_TUN_ID[],output:NXM_OF_IN_PORT[]),output:1 cookie=0xbc2e9105125301dc, duration=9615.378s, table=20, n_packets=5, n_bytes=490, priority=0 actions=resubmit(,22) cookie=0xbc2e9105125301dc, duration=9615.342s, table=22, n_packets=146, n_bytes=11534, priority=0 actions=drop vagrant@ubuntu:~$ sudo ovs-ofctl dump-flows br-int -O OpenFlow13 OFPST_FLOW reply (OF1.3) (xid=0x2): cookie=0xbc2e9105125301dc, duration=6712.090s, table=0, n_packets=0, n_bytes=0, priority=10,icmp6,in_port=7,icmp_type=136 actions=resubmit(,24) cookie=0xbc2e9105125301dc, duration=6709.623s, table=0, n_packets=0, n_bytes=0, priority=10,icmp6,in_port=8,icmp_type=136 actions=resubmit(,24) cookie=0xbc2e9105125301dc, duration=6555.755s, table=0, n_packets=0, n_bytes=0, priority=10,icmp6,in_port=10,icmp_type=136 actions=resubmit(,24) cookie=0xbc2e9105125301dc, duration=6559.596s, table=0, n_packets=0, n_bytes=0, priority=10,icmp6,in_port=9,icmp_type=136 actions=resubmit(,24) cookie=0xbc2e9105125301dc, duration=6461.028s, table=0, n_packets=0, n_bytes=0, priority=10,icmp6,in_port=11,icmp_type=136 actions=resubmit(,24) cookie=0xbc2e9105125301dc, duration=6712.071s, table=0, n_packets=13, n_bytes=546, priority=10,arp,in_port=7 actions=resubmit(,24) cookie=0xbc2e9105125301dc, duration=6709.602s, table=0, n_packets=0, n_bytes=0, priority=10,arp,in_port=8 actions=resubmit(,24) cookie=0xbc2e9105125301dc, duration=6555.727s, table=0, n_packets=0, n_bytes=0, priority=10,arp,in_port=10 actions=resubmit(,24) cookie=0xbc2e9105125301dc, duration=6559.574s, table=0, n_packets=12, n_bytes=504, priority=10,arp,in_port=9 actions=resubmit(,24) cookie=0xbc2e9105125301dc, duration=6461.005s, table=0, n_packets=15, n_bytes=630, priority=10,arp,in_port=11 actions=resubmit(,24) cookie=0xbc2e9105125301dc, duration=9620.388s, table=0, n_packets=514, n_bytes=49656, priority=0 actions=NORMAL cookie=0xbc2e9105125301dc, duration=9619.277s, table=0, n_packets=0, n_bytes=0, priority=20,mpls actions=resubmit(,10) cookie=0xbc2e9105125301dc, duration=6712.111s, table=0, n_packets=25, n_bytes=2674, priority=9,in_port=7 actions=resubmit(,25) cookie=0xbc2e9105125301dc, duration=6559.621s, table=0, n_packets=24, n_bytes=2576, priority=9,in_port=9 actions=resubmit(,25) cookie=0xbc2e9105125301dc, duration=6555.777s, table=0, n_packets=2, n_bytes=140, priority=9,in_port=10 actions=resubmit(,25) cookie=0xbc2e9105125301dc, duration=6461.082s, table=0, n_packets=47, n_bytes=4830, priority=9,in_port=11 actions=resubmit(,25) cookie=0xbc2e9105125301dc, duration=6709.646s, table=0, n_packets=3,
Re: [openstack-dev] [Fuel] Failed to install fuel master
Hi guys, I'm using Fuel-8.0 iso, I used "Lili USB Creator" to write ISO to the USB. (I tried this process for ubuntu-server.iso and it worked correctly). Regards, On 7 July 2016 at 09:54, Stanislaw Bogatkin <sbogat...@mirantis.com> wrote: > Hi guys, > > could you tell which way you used to write ISO to the USB stick? > > On Thu, Jul 7, 2016 at 9:17 AM, Jack Morgan <jack.mor...@intel.com> wrote: > >> I'm pretty sure this is a USB stick install as I've seen the same failure >> on Fuel-8.0. Basically, the installer is not able to find the mounted drive >> to run the kickstart file. Duel layer DVD media or a virtual Fuel master >> are the only ways I've gotten Fuel-8.0 to install. >> >> On 07/05/2016 05:22 AM, Vladimir Kuklin wrote: >> >> Hi, Alioune >> >> Let's start with the most basic steps. Which Fuel are you using? >> And how do you install the node? Do you use USB stick or DVD or some IPMI >> virtual media? From what I see here it pretty much looks like, that this >> media is not inserted into the host. >> >> On Tue, Jul 5, 2016 at 3:11 PM, Alioune <baliou...@gmail.com> wrote: >> >>> Hi all, >>> >>> I'm trying to install fuel master using [1] on phycal server but the >>> installation process fails and switches to a dracut console with the >>> following error: >>> >>> dracut-initqueue[595] floppy0: no floppy controllers found >>> dracut-initqueue[595] Warning: failed to fetck kickstart from >>> hd:sr0:/ks.cfg >>> dracut-initqueue[595] mount: no medium found on /dev/sr0 >>> dracut-initqueue[595] Warning: Cloud not boot >>> dracut-initqueue[595] Warning: /dev/root does not exist >>> >>> >>> Starting Dracut Emergency Shell >>> Warning: /dev/root does not exist >>> Generating "/run/initramfs/rdsosreport.txt" >>> dracut:/# >>> >>> Any suggestion for solving that error ? >>> >>> Regards, >>> >>> [1] >>> http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_prepare_install_media.html >>> >>> >>> __ >>> 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 >>> >>> >> >> >> -- >> Yours Faithfully, >> Vladimir Kuklin, >> Fuel Library Tech Lead, >> Mirantis, Inc. >> +7 (495) 640-49-04 >> +7 (926) 702-39-68 >> Skype kuklinvv >> 35bk3, Vorontsovskaya Str. >> Moscow, Russia, >> www.mirantis.com <http://www.mirantis.ru/> >> www.mirantis.ru >> vkuk...@mirantis.com >> >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> -- >> Jack Morgan >> OPNFV Pharos Intel Lab >> >> >> __ >> 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 >> >> > > > -- > with best regards, > Stan. > > __ > 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] [Fuel] Failed to install fuel master
Hi all, I'm trying to install fuel master using [1] on phycal server but the installation process fails and switches to a dracut console with the following error: dracut-initqueue[595] floppy0: no floppy controllers found dracut-initqueue[595] Warning: failed to fetck kickstart from hd:sr0:/ks.cfg dracut-initqueue[595] mount: no medium found on /dev/sr0 dracut-initqueue[595] Warning: Cloud not boot dracut-initqueue[595] Warning: /dev/root does not exist Starting Dracut Emergency Shell Warning: /dev/root does not exist Generating "/run/initramfs/rdsosreport.txt" dracut:/# Any suggestion for solving that error ? Regards, [1] http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/install/install_prepare_install_media.html __ 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] [murano] Fail to install murano in Pro environment / Ansible cookbook for murano
Hi all, I'm trying to install murano in existing openstack platform following [1]. So the installation process fails at step [2] with this error. Any suggestion for solving that ? Is there existing murano playbook for easy deployment with ansible ? You can find my murano.conf in [3] [1] http://docs.openstack.org/developer/murano/install/manual.html [2] sudo tox -e venv -- murano-api --config-file ./etc/murano/murano.conf [3] https://drive.google.com/file/d/0B-bfET74f0WZd2N6WGR0Szh1UUE/view?usp=sharing ERROR: 2016-07-04 14:06:59.960 9251 WARNING keystonemiddleware.auth_token [-] Use of the auth_admin_prefix, auth_host, auth_port, auth_protocol, identity_uri, admin_token, admin_user, admin_password, and admin_tenant_name configuration options was deprecated in the Mitaka release in favor of an auth_plugin and its related options. This class may be removed in a future release. 2016-07-04 14:06:59.960 9251 WARNING keystonemiddleware.auth_token [-] Configuring admin URI using auth fragments was deprecated in the Kilo release, and will be removed in the N release, use 'identity_uri\ instead. 2016-07-04 14:07:00.252 9251 CRITICAL murano [-] TypeError: __init__() takes exactly 3 arguments (5 given) 2016-07-04 14:07:00.252 9251 ERROR murano Traceback (most recent call last): 2016-07-04 14:07:00.252 9251 ERROR murano File ".tox/venv/bin/murano-api", line 10, in 2016-07-04 14:07:00.252 9251 ERROR murano sys.exit(main()) 2016-07-04 14:07:00.252 9251 ERROR murano File "/home/vagrant/murano/murano/cmd/api.py", line 66, in main 2016-07-04 14:07:00.252 9251 ERROR murano launcher.launch_service(server.get_notification_service()) 2016-07-04 14:07:00.252 9251 ERROR murano File "/home/vagrant/murano/murano/common/server.py", line 235, in get_notification_service 2016-07-04 14:07:00.252 9251 ERROR murano NOTIFICATION_SERVICE = _prepare_notification_service(str(uuid.uuid4())) 2016-07-04 14:07:00.252 9251 ERROR murano File "/home/vagrant/murano/murano/common/server.py", line 219, in _prepare_notification_service 2016-07-04 14:07:00.252 9251 ERROR murano [s_target], endpoints, None, True) 2016-07-04 14:07:00.252 9251 ERROR murano TypeError: __init__() takes exactly 3 arguments (5 given) 2016-07-04 14:07:00.252 9251 ERROR murano ERROR: InvocationError: '/home/vagrant/murano/.tox/venv/bin/murano-api --config-file etc/murano/murano.conf' _ summary _ ERROR: venv: commands failed __ 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] [murano] Load murano Apps
Hi all, I've downloaded murano apps from [1] and I would like to upload them as package. I would like to know which folders into murano-apps to zip and load from "Package Definition" ? How to add these apps with murano package-import ? Regards, [1] https://github.com/openstack/murano-apps __ 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
Re: [openstack-dev] [Fuel] Failed to build the bootstrap image
Maksim, The bootstrap process woks fine without error but the slave can boot from network. I think that the issue is due TFTP process, it tries to reach http://10.20.0.2/cobbler/boot, I used my web browser but there is not directory named boot in cobbler folder. Should the bootstrap create this directory ? On 28 June 2016 at 15:59, Maksim Malchuk <mmalc...@mirantis.com> wrote: > You can start build command with debug options enabled for example and > copy/paste output: >> >> fuel-bootstrap --verbose --debug build --activate >> > > Very bad idea to remove logfile, it's better to empty it not remove. > > If you don't have the logfile, so recreate it with command: > >> touch /var/log/fuel-bootstrap-image-build.log >> > > > On Tue, Jun 28, 2016 at 4:09 PM, Alioune <baliou...@gmail.com> wrote: > >> I've removed /var/log/fuel-bootstrap-image-build.log, created new >> bootstrap ubuntu again after setting proxy parameters and reboot. >> After the there is no /var/log/fuel-bootstrap-image-build.log create from >> the new bootstrap but slave doesn't boot correctly. >> Is there another way to detect slave nodes without creating image ? >> Regards, >> [image: Inline images 2] >> >> On 28 June 2016 at 13:34, Maksim Malchuk <mmalc...@mirantis.com> wrote: >> >>> You have an issue with connectivity from the Fuel master node to >>> http://archive.ubuntu.com >>> from the log: >>> >>>> Command: debootstrap --include=ca-certificates,apt-transport-https >>>> --verbose --no-check-gpg --arch=amd64 trusty >>>> /tmp/tmp1K2haC.fuel-agent-image http://archive.ubuntu.com/ubuntu >>>> Exit code: 1 >>>> Stdout: 'I: Retrieving Release \nE: Failed getting release file >>>> http://archive.ubuntu.com/ubuntu/dists/trusty/Release\n' >>>> Stderr: '' >>>> Failed to execute command: Unexpected error while running command. >>>> >>>> please check your network connectivity, maybe firewall or nat settings. >>> >>> >>> On Tue, Jun 28, 2016 at 2:28 PM, Alioune <baliou...@gmail.com> wrote: >>> >>>> Hi all, >>>> I tried to create ubuntu bootstrap using [0] but the slave can still >>>> not booting. You can find the bootstrap log following [1]. >>>> >>>> Noticed that I've deleted the depot [2] from fuelmenu because it >>>> generated an error "URL for repository mos is not accessible". >>>> >>>> Regards, >>>> >>>> [0] fuel-bootstrap build --ubuntu-release trusty --activate >>>> [1] >>>> https://drive.google.com/folderview?id=0B-bfET74f0WZWE9Uc1lVOXJLcWM=sharing >>>> [2] http://127.0.0.1:8080/ubuntu/x86_64/ mos8.0 main restricted >>>> >>>> On 27 June 2016 at 17:48, Maksim Malchuk <mmalc...@mirantis.com> wrote: >>>> >>>>> Maybe the problem because you create the CentOS bootstrap which is >>>>> deprecated now. >>>>> If You really need the CentOS bootstrap, need to look into the >>>>> mentioned log file for this issue. >>>>> >>>>> >>>>> On Mon, Jun 27, 2016 at 6:33 PM, Alioune <baliou...@gmail.com> wrote: >>>>> >>>>>> Thanks for your response, >>>>>> >>>>>> I've created and activated a new centOS bootstrap as suggested Sergi. >>>>>> Now the fuel-slave tries to boot from network but it fails at step >>>>>> TFTP http://10.20.0.2/cobbler/boot (unable to locate configuration >>>>>> file ). >>>>>> The bootstrap zip was generated in >>>>>> /tmp/a721103c-8693-4c58-985d-3f8223bdbc88.tar.gz, it seems that the slave >>>>>> can not retreive the config files of the bootstrap. >>>>>> Are there additional config to do on the master side ? >>>>>> Regards >>>>>> >>>>>> fuel-bootstrap list >>>>>> >>>>>> +--+--++ >>>>>> | uuid | label >>>>>> | status | >>>>>> >>>>>> +--+--++ >>>>>> | a721103c-8693-4c58-985d-3f8223bdbc88 | >>>>>> a721103c-8693-4c58-985d-3f8223bdbc88 | active | >>>>>> | centos
Re: [openstack-dev] [Fuel] Failed to build the bootstrap image
I've removed /var/log/fuel-bootstrap-image-build.log, created new bootstrap ubuntu again after setting proxy parameters and reboot. After the there is no /var/log/fuel-bootstrap-image-build.log create from the new bootstrap but slave doesn't boot correctly. Is there another way to detect slave nodes without creating image ? Regards, [image: Inline images 2] On 28 June 2016 at 13:34, Maksim Malchuk <mmalc...@mirantis.com> wrote: > You have an issue with connectivity from the Fuel master node to > http://archive.ubuntu.com > from the log: > >> Command: debootstrap --include=ca-certificates,apt-transport-https --verbose >> --no-check-gpg --arch=amd64 trusty /tmp/tmp1K2haC.fuel-agent-image >> http://archive.ubuntu.com/ubuntu >> Exit code: 1 >> Stdout: 'I: Retrieving Release \nE: Failed getting release file >> http://archive.ubuntu.com/ubuntu/dists/trusty/Release\n' >> Stderr: '' >> Failed to execute command: Unexpected error while running command. >> >> please check your network connectivity, maybe firewall or nat settings. > > > On Tue, Jun 28, 2016 at 2:28 PM, Alioune <baliou...@gmail.com> wrote: > >> Hi all, >> I tried to create ubuntu bootstrap using [0] but the slave can still not >> booting. You can find the bootstrap log following [1]. >> >> Noticed that I've deleted the depot [2] from fuelmenu because it >> generated an error "URL for repository mos is not accessible". >> >> Regards, >> >> [0] fuel-bootstrap build --ubuntu-release trusty --activate >> [1] >> https://drive.google.com/folderview?id=0B-bfET74f0WZWE9Uc1lVOXJLcWM=sharing >> [2] http://127.0.0.1:8080/ubuntu/x86_64/ mos8.0 main restricted >> >> On 27 June 2016 at 17:48, Maksim Malchuk <mmalc...@mirantis.com> wrote: >> >>> Maybe the problem because you create the CentOS bootstrap which is >>> deprecated now. >>> If You really need the CentOS bootstrap, need to look into the mentioned >>> log file for this issue. >>> >>> >>> On Mon, Jun 27, 2016 at 6:33 PM, Alioune <baliou...@gmail.com> wrote: >>> >>>> Thanks for your response, >>>> >>>> I've created and activated a new centOS bootstrap as suggested Sergi. >>>> Now the fuel-slave tries to boot from network but it fails at step TFTP >>>> http://10.20.0.2/cobbler/boot (unable to locate configuration file ). >>>> The bootstrap zip was generated in >>>> /tmp/a721103c-8693-4c58-985d-3f8223bdbc88.tar.gz, it seems that the slave >>>> can not retreive the config files of the bootstrap. >>>> Are there additional config to do on the master side ? >>>> Regards >>>> >>>> fuel-bootstrap list >>>> >>>> +--+--++ >>>> | uuid | label >>>>| status | >>>> >>>> +--+--++ >>>> | a721103c-8693-4c58-985d-3f8223bdbc88 | >>>> a721103c-8693-4c58-985d-3f8223bdbc88 | active | >>>> | centos | deprecated >>>> || >>>> >>>> +--+--++ >>>> >>>> On 27 June 2016 at 16:58, Sergii Golovatiuk <sgolovat...@mirantis.com> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I would suggest to build image from CLI using [0]. That will give more >>>>> details to you. >>>>> >>>>> [0] >>>>> http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/bootstrap/bootstrap_builder.html >>>>> >>>>> -- >>>>> Best regards, >>>>> Sergii Golovatiuk, >>>>> Skype #golserge >>>>> IRC #holser >>>>> >>>>> On Mon, Jun 27, 2016 at 3:20 PM, Maksim Malchuk <mmalc...@mirantis.com >>>>> > wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> The error about an internet connection is the only common case. You >>>>>> should check the actual error in the log file >>>>>> /var/log/fuel-bootstrap-image-build.log. >>>>>> You can also share this file with us via any public service >>>>>> (GoogleDrive, DropBox, etc) and we will check it for you. >>>&g
Re: [openstack-dev] [Fuel] Failed to build the bootstrap image
Hi all, I tried to create ubuntu bootstrap using [0] but the slave can still not booting. You can find the bootstrap log following [1]. Noticed that I've deleted the depot [2] from fuelmenu because it generated an error "URL for repository mos is not accessible". Regards, [0] fuel-bootstrap build --ubuntu-release trusty --activate [1] https://drive.google.com/folderview?id=0B-bfET74f0WZWE9Uc1lVOXJLcWM=sharing [2] http://127.0.0.1:8080/ubuntu/x86_64/ mos8.0 main restricted On 27 June 2016 at 17:48, Maksim Malchuk <mmalc...@mirantis.com> wrote: > Maybe the problem because you create the CentOS bootstrap which is > deprecated now. > If You really need the CentOS bootstrap, need to look into the mentioned > log file for this issue. > > > On Mon, Jun 27, 2016 at 6:33 PM, Alioune <baliou...@gmail.com> wrote: > >> Thanks for your response, >> >> I've created and activated a new centOS bootstrap as suggested Sergi. >> Now the fuel-slave tries to boot from network but it fails at step TFTP >> http://10.20.0.2/cobbler/boot (unable to locate configuration file ). >> The bootstrap zip was generated in >> /tmp/a721103c-8693-4c58-985d-3f8223bdbc88.tar.gz, it seems that the slave >> can not retreive the config files of the bootstrap. >> Are there additional config to do on the master side ? >> Regards >> >> fuel-bootstrap list >> >> +--+--++ >> | uuid | label >> | status | >> >> +--+--++ >> | a721103c-8693-4c58-985d-3f8223bdbc88 | >> a721103c-8693-4c58-985d-3f8223bdbc88 | active | >> | centos | deprecated >> || >> >> +--+--++ >> >> On 27 June 2016 at 16:58, Sergii Golovatiuk <sgolovat...@mirantis.com> >> wrote: >> >>> Hi, >>> >>> I would suggest to build image from CLI using [0]. That will give more >>> details to you. >>> >>> [0] >>> http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/bootstrap/bootstrap_builder.html >>> >>> -- >>> Best regards, >>> Sergii Golovatiuk, >>> Skype #golserge >>> IRC #holser >>> >>> On Mon, Jun 27, 2016 at 3:20 PM, Maksim Malchuk <mmalc...@mirantis.com> >>> wrote: >>> >>>> Hi, >>>> >>>> The error about an internet connection is the only common case. You >>>> should check the actual error in the log file >>>> /var/log/fuel-bootstrap-image-build.log. >>>> You can also share this file with us via any public service >>>> (GoogleDrive, DropBox, etc) and we will check it for you. >>>> >>>> On Mon, Jun 27, 2016 at 4:08 PM, Maksim Malchuk <mmalc...@mirantis.com> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> The error about an internet connection is the only common case. You >>>>> should check the actual error in the log file >>>>> /var/log/fuel-bootstrap-image-build.log. >>>>> You can also share this file with us via any public service >>>>> (GoogleDrive, DropBox, etc) and we will check it for you. >>>>> >>>>> >>>>> On Mon, Jun 27, 2016 at 1:43 PM, Alioune <baliou...@gmail.com> wrote: >>>>> >>>>>> hi all, >>>>>> >>>>>> I'm trying to install fuel in VirtualBox, the fuel master is >>>>>> correctly running but I'm receiving the this error on the fuel GUI: >>>>>> >>>>>> WARNING: Failed to build the bootstrap image, see >>>>>> /var/log/fuel-bootstrap-image-build.log for details. >>>>>> Perhaps your Internet connection is broken. Please fix the problem >>>>>> and run `fuel-bootstrap build --activate`. >>>>>> While you don't activate any bootstrap - new nodes cannot be >>>>>> discovered and added to cluster. >>>>>> For more information please visit >>>>>> https://docs.mirantis.com/openstack/fuel/fuel-master/ >>>>>> >>>>>> The fuel server has access to internet even though it could not find >>>>>> depots during install, I ran "yum update" and reboot but I still get this >>>>>> error.
Re: [openstack-dev] [Fuel] Failed to build the bootstrap image
Thanks for your response, I've created and activated a new centOS bootstrap as suggested Sergi. Now the fuel-slave tries to boot from network but it fails at step TFTP http://10.20.0.2/cobbler/boot (unable to locate configuration file ). The bootstrap zip was generated in /tmp/a721103c-8693-4c58-985d-3f8223bdbc88.tar.gz, it seems that the slave can not retreive the config files of the bootstrap. Are there additional config to do on the master side ? Regards fuel-bootstrap list +--+--++ | uuid | label | status | +--+--++ | a721103c-8693-4c58-985d-3f8223bdbc88 | a721103c-8693-4c58-985d-3f8223bdbc88 | active | | centos | deprecated || +--+--++ On 27 June 2016 at 16:58, Sergii Golovatiuk <sgolovat...@mirantis.com> wrote: > Hi, > > I would suggest to build image from CLI using [0]. That will give more > details to you. > > [0] > http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide/bootstrap/bootstrap_builder.html > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > On Mon, Jun 27, 2016 at 3:20 PM, Maksim Malchuk <mmalc...@mirantis.com> > wrote: > >> Hi, >> >> The error about an internet connection is the only common case. You >> should check the actual error in the log file >> /var/log/fuel-bootstrap-image-build.log. >> You can also share this file with us via any public service (GoogleDrive, >> DropBox, etc) and we will check it for you. >> >> On Mon, Jun 27, 2016 at 4:08 PM, Maksim Malchuk <mmalc...@mirantis.com> >> wrote: >> >>> Hi, >>> >>> The error about an internet connection is the only common case. You >>> should check the actual error in the log file >>> /var/log/fuel-bootstrap-image-build.log. >>> You can also share this file with us via any public service >>> (GoogleDrive, DropBox, etc) and we will check it for you. >>> >>> >>> On Mon, Jun 27, 2016 at 1:43 PM, Alioune <baliou...@gmail.com> wrote: >>> >>>> hi all, >>>> >>>> I'm trying to install fuel in VirtualBox, the fuel master is correctly >>>> running but I'm receiving the this error on the fuel GUI: >>>> >>>> WARNING: Failed to build the bootstrap image, see >>>> /var/log/fuel-bootstrap-image-build.log for details. >>>> Perhaps your Internet connection is broken. Please fix the problem and >>>> run `fuel-bootstrap build --activate`. >>>> While you don't activate any bootstrap - new nodes cannot be discovered >>>> and added to cluster. >>>> For more information please visit >>>> https://docs.mirantis.com/openstack/fuel/fuel-master/ >>>> >>>> The fuel server has access to internet even though it could not find >>>> depots during install, I ran "yum update" and reboot but I still get this >>>> error. >>>> I configured a fuel-slave server boot from network attached to the >>>> fuel-master but the process failed also. >>>> Any help please to solve this ? >>>> >>>> Regards, >>>> >>>> >>>> __ >>>> 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 >>>> >>>> >>> >>> >>> -- >>> Best Regards, >>> Maksim Malchuk, >>> Senior DevOps Engineer, >>> MOS: Product Engineering, >>> Mirantis, Inc >>> <vgor...@mirantis.com> >>> >> >> >> >> -- >> Best Regards, >> Maksim Malchuk, >> Senior DevOps Engineer, >> MOS: Product Engineering, >> Mirantis, Inc >> <vgor...@mirantis.com> >> >> __ >> 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 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] [Fuel] Failed to build the bootstrap image
hi all, I'm trying to install fuel in VirtualBox, the fuel master is correctly running but I'm receiving the this error on the fuel GUI: WARNING: Failed to build the bootstrap image, see /var/log/fuel-bootstrap-image-build.log for details. Perhaps your Internet connection is broken. Please fix the problem and run `fuel-bootstrap build --activate`. While you don't activate any bootstrap - new nodes cannot be discovered and added to cluster. For more information please visit https://docs.mirantis.com/openstack/fuel/fuel-master/ The fuel server has access to internet even though it could not find depots during install, I ran "yum update" and reboot but I still get this error. I configured a fuel-slave server boot from network attached to the fuel-master but the process failed also. Any help please to solve this ? Regards, __ 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] [ansible] Fail to install Openstack all in one
Hi all, I'm trying to install OpenStack all in one using ansible but I got the error bellow. Someone knows how to solve this error? Regards, ERROR: + openstack-ansible --forks 1 openstack-hosts-setup.yml Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml " ERROR: Inventory script (inventory/dynamic_inventory.py) had an execution error: No user config loadaed No openstack_user_config files are available in either the base location or the conf.d directory + (( RETRY++ )) + (( 1 != 0 && RETRY < MAX_RETRIES )) + '[' 1 -gt 1 ']' + openstack-ansible --forks 1 openstack-hosts-setup.yml Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml " ERROR: Inventory script (inventory/dynamic_inventory.py) had an execution error: No user config loadaed No openstack_user_config files are available in either the base location or the conf.d directory + (( RETRY++ )) + (( 1 != 0 && RETRY < MAX_RETRIES )) + '[' 2 -gt 1 ']' + openstack-ansible --forks 1 openstack-hosts-setup.yml - Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml " ERROR: Inventory script (inventory/dynamic_inventory.py) had an execution error: No user config loadaed No openstack_user_config files are available in either the base location or the conf.d directory + (( RETRY++ )) + (( 1 != 0 && RETRY < MAX_RETRIES )) + '[' 3 -gt 1 ']' + openstack-ansible --forks 1 openstack-hosts-setup.yml - Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml " ERROR: Inventory script (inventory/dynamic_inventory.py) had an execution error: No user config loadaed No openstack_user_config files are available in either the base location or the conf.d directory __ 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
Re: [openstack-dev] [neutron][SFC]
Hi all,
I 'm still trying to integrate sfc project with devstack using [1] but the
L2 agent is unable to chech status of br-int (see error bellow).
I think that the error is not due to OpenFlow version negociation since I
can execute the command "sudo ovs-ofctl dump-flows br-int -O OpenFlow13
table=23"
Someone knows how to solve this error ?
Regards,
Here are some information about my environement:
uname -r
3.16.0-30-generic
sudo ovs-vsctl --version
ovs-vsctl (Open vSwitch) 2.4.1
Compiled Jun 20 2016 14:56:46
DB Schema 7.12.1
sudo ovs-vsctl show
83a36bf9-e7fd-40cc-bd6e-fefb3119ff0c
Bridge br-int
Port br-int
Interface br-int
type: internal
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
ovs_version: "2.4.1"
sudo ovs-ofctl dump-flows br-int -O OpenFlow13 table=23
OFPST_FLOW reply (OF1.3) (xid=0x2):
ERROR:
opt/stack/neutron/neutron/agent/linux/utils.py:101
2016-06-21 14:49:26.470 ERROR neutron.agent.linux.utils
[req-775e942c-237f-4872-9dd2-cf6cae7b34ed None None]
Command: ['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int', 'table=23']
Exit code: 1
Stdin:
Stdout:
Stderr: ovs-ofctl: br-int is not a bridge or a socket
2016-06-21 14:49:26.485 ERROR
networking_sfc.services.sfc.common.ovs_ext_lib
[req-775e942c-237f-4872-9dd2-cf6cae7b34ed None None]
Command: ['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int', 'table=23']
Exit code: 1
Stdin:
Stdout:
Stderr: ovs-ofctl: br-int is not a bridge or a socket
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Traceback (most recent call
last):
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib File
"/opt/stack/networking-sfc/networking_sfc/services/sfc/common/ovs_ext_lib.py",
line 125, in run_ofctl
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib
process_input=process_input)
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib File
"/opt/stack/neutron/neutron/agent/linux/utils.py", line 159, in execute
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib raise RuntimeError(m)
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib RuntimeError:
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Command: ['ovs-ofctl', '-O
openflow13', 'dump-flows', 'br-int', 'table=23']
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Exit code: 1
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Stdin:
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Stdout:
2016-06-21 14:49:26.485 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Stderr: ovs-ofctl: br-int is
not a bridge or a socket
2016-06-21 14:49:26.485 TRACE networking_sfc.services.sfc.common.ovs_ext_lib
2016-06-21 14:49:26.485 TRACE networking_sfc.services.sfc.common.ovs_ext_lib
2016-06-21 14:49:26.492 ERROR
networking_sfc.services.sfc.common.ovs_ext_lib
[req-775e942c-237f-4872-9dd2-cf6cae7b34ed None None] Unable to execute
['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int', 'table=23'].
2016-06-21 14:49:26.495 WARNING
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
[req-775e942c-237f-4872-9dd2-cf6cae7b34ed None None] OVS is dead.
OVSNeutronAgent will keep running and checking OVS status periodically.
2016-06-21 14:49:26.498 DEBUG
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
[req-775e942c-237f-4872-9dd2-cf6cae7b34ed None None] Agent rpc_loop -
iteration:1983 completed. Processed ports statistics: {'regular':
{'updated': 0, 'added': 0, 'removed': 0}}. Elapsed:0.050 from (pid=7331)
loop_count_and_wait
/opt/stack/neutron/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:1680
[1] https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining
On 15 June 2016 at 16:22, Mohan Kumar <nmohankumar1...@gmail.com> wrote:
> could you ping in IRC channel handle #openstack-neutron name : mohankumar
>
> On Wed, Jun 15, 2016 at 7:50 PM, Alioune <baliou...@gmail.com> wrote:
>
>> Mohan,
>> Is it possible to configure the neutron-plugin-ovs-agent to use
>> OpenFlow13 ?
>>
>> Please could you tell me versions of your openstack environment ?
>>
>> Regards,
>>
>> On 15 June 2016 at 12:58, Alioune <baliou...@gmail.com> wrote:
>>
>>> Sorry for not being clear,
>>> I juste have the same architecture like in your ONOS demo but I'm only
>>> using neutron without any SDN controller in backend.
>>>
>>> On Wednesday, 15 June 2016, Mohan Kumar <nmohankumar1...@gmail.com>
>>> wrote:
>>>
>>>> Alioune ,
>>>>
>>>> I suspect this could be OVS cleanup issue , you have to delete ovs
>>>> b
Re: [openstack-dev] [neutron][SFC]
Hi Mohan, Even if I clone the master branch of networking-sfc project,I get the following errir when creating flow-classifier, therefore I do precise the logical-source-port. 2016-06-10 05:34:05.693 10799 ERROR neutron.api.v2.resource DBError: (pymysql.err.IntegrityError) (1048, u"Column 'logical_source_port' cannot be null") I'm trying the example in [1] Here is a "ovs-ofctl dump-flows" on br-int ofter creating port-chain, I expected to see vxlan or gre tunnel encapsulation entries as explained in [1], may I know why there is no tunnel entry in br-int ? sudo ovs-ofctl dump-flows br-int NXST_FLOW reply (xid=0x4): cookie=0x90444f3c8fabcbe0, duration=2840.983s, table=0, n_packets=0, n_bytes=0, idle_age=2840, priority=10,icmp6,in_port=16,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2837.039s, table=0, n_packets=0, n_bytes=0, idle_age=2837, priority=10,icmp6,in_port=17,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2831.688s, table=0, n_packets=0, n_bytes=0, idle_age=2831, priority=10,icmp6,in_port=19,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2831.038s, table=0, n_packets=0, n_bytes=0, idle_age=2831, priority=10,icmp6,in_port=18,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2801.555s, table=0, n_packets=0, n_bytes=0, idle_age=2801, priority=10,icmp6,in_port=20,icmp_type=136 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2840.605s, table=0, n_packets=8, n_bytes=336, idle_age=2591, priority=10,arp,in_port=16 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2836.759s, table=0, n_packets=0, n_bytes=0, idle_age=2836, priority=10,arp,in_port=17 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2831.485s, table=0, n_packets=0, n_bytes=0, idle_age=2831, priority=10,arp,in_port=19 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2830.816s, table=0, n_packets=21, n_bytes=882, idle_age=1605, priority=10,arp,in_port=18 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=2801.309s, table=0, n_packets=10, n_bytes=420, idle_age=545, priority=10,arp,in_port=20 actions=resubmit(,24) cookie=0x90444f3c8fabcbe0, duration=15755.073s, table=0, n_packets=3241, n_bytes=366555, idle_age=545, priority=0 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=15754.687s, table=23, n_packets=0, n_bytes=0, idle_age=15754, priority=0 actions=drop cookie=0x90444f3c8fabcbe0, duration=2841.201s, table=24, n_packets=0, n_bytes=0, idle_age=2841, priority=2,icmp6,in_port=16,icmp_type=136,nd_target=fe80::f816:3eff:fe2d:c29d actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2837.177s, table=24, n_packets=0, n_bytes=0, idle_age=2837, priority=2,icmp6,in_port=17,icmp_type=136,nd_target=fe80::f816:3eff:fee0:f8ca actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2831.794s, table=24, n_packets=0, n_bytes=0, idle_age=2831, priority=2,icmp6,in_port=19,icmp_type=136,nd_target=fe80::f816:3eff:fe86:a668 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2831.150s, table=24, n_packets=0, n_bytes=0, idle_age=2831, priority=2,icmp6,in_port=18,icmp_type=136,nd_target=fe80::f816:3eff:feb4:965f actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2801.675s, table=24, n_packets=0, n_bytes=0, idle_age=2801, priority=2,icmp6,in_port=20,icmp_type=136,nd_target=fe80::f816:3eff:fe5a:3097 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2840.794s, table=24, n_packets=8, n_bytes=336, idle_age=2591, priority=2,arp,in_port=16,arp_spa=55.55.55.3 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2836.901s, table=24, n_packets=0, n_bytes=0, idle_age=2836, priority=2,arp,in_port=17,arp_spa=55.55.55.4 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2831.587s, table=24, n_packets=0, n_bytes=0, idle_age=2831, priority=2,arp,in_port=19,arp_spa=55.55.55.6 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2830.933s, table=24, n_packets=21, n_bytes=882, idle_age=1605, priority=2,arp,in_port=18,arp_spa=55.55.55.5 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=2801.431s, table=24, n_packets=10, n_bytes=420, idle_age=545, priority=2,arp,in_port=20,arp_spa=55.55.55.8 actions=NORMAL cookie=0x90444f3c8fabcbe0, duration=15754.273s, table=24, n_packets=0, n_bytes=0, idle_age=15754, priority=0 actions=drop is there a link that explains how pipelines are created by SFC in br-int to compare with my flows entries ? Does the flow-classifier referer to floating IPs or tenant network IPs to do the classification ? Regards, [1] http://docs.openstack.org/developer/networking-sfc/system_design%20and_workflow.html On 9 June 2016 at 18:59, Henry Fourie <louis.fou...@huawei.com> wrote: > Alioune, > >The logical-source-port refers to a Neutron port of the VM that > > originates the traffic that is to be processed by the port-chain. > > -Louis > > > > *From:* Alioune [mailto:baliou...@gmail.com] > *Sent:* Thursday, June 09, 2016 6:50 AM
Re: [openstack-dev] [neutron][SFC]
Mohan, I would like to redirect all http flows in tenant network to the port-chain and according to your explanation I do specify the neutron-port of source vm in the classifier. is there a generic way to to put into the chain all traffc going to a web server the tenant network ? (to avoide setting neutron-port of source vm) Regards, On 9 June 2016 at 16:32, Mohan Kumar <nmohankumar1...@gmail.com> wrote: > Alioune, > >logical-source-port is egress neutron-port of source vm , typically > flow-classifier will classifies packets coming to this neutron port and > forwards to the rest of port-chain if other classifier conditions are > matches. > > Thanks., > Mohankumar.N > > > > On Thu, Jun 9, 2016 at 7:20 PM, Alioune <baliou...@gmail.com> wrote: > >> Thanks Mohan, >> >> After setting service_plugins and adding sfc tables to neutrondb, I can >> create port-pair, port-pair-group but classifier creation still claim a >> logical-source-port parameter. >> >> neutron flow-classifier-create --ethertype IPv4 --source-ip-prefix >> 55.55.55.2/32 --destination-ip-prefix 55.55.55.9/32 --protocol tcp >> --source-port 22:22 --destination-port 1:65000 FC1 >> ERROR: >> neutron flow-classifier-create: error: argument --logical-source-port is >> required >> Try 'neutron help flow-classifier-create' for more information. >> >> Please someone can explain what does --logical-source-port correspond to ? >> Does the classifier require port-create like SF ? >> >> Regards, >> >> >> On 9 June 2016 at 09:21, Mohan Kumar <nmohankumar1...@gmail.com> wrote: >> >>> Alioune, >>> >>> networking-sfc resources not installed / not reachable , If installation >>> is okay, Possibly you may missed service_plugins entry in *neutron.conf >>> *( in case of manual networking-sfc installation) >>> >>> it should be , >>> >>> *service_plugins = >>> neutron.services.l3_router.l3_router_plugin.L3RouterPlugin,networking_sfc.services.flowclassifier.plugin.FlowClassifierPlugin,networking_sfc.services.sfc.plugin.SfcPlugin* >>> >>> *and restart q-svc services in screen -x * >>> >>> *Thanks.,* >>> *Mohankumar.N * >>> >>> On Thu, Jun 9, 2016 at 12:58 AM, Alioune <baliou...@gmail.com> wrote: >>> >>>> I've switched from devstack to a normal deployment of openstack/mitaka >>>> and neutron-l2 agent is working fine with sfc. I can boot instances, create >>>> ports. >>>> However I can not create neither flow-classifier nor port-pair ... >>>> >>>> neutron flow-classifier-create --ethertype IPv4 --source-ip-prefix >>>> 22.1.20.1/32 --destination-ip-prefix 172.4.5.6/32 --protocol tcp >>>> --source-port 23:23 --destination-port 100:100 FC1 >>>> >>>> returns: neutron flow-classifier-create: error: argument >>>> --logical-source-port is required >>>> Try 'neutron help flow-classifier-create' for more information. >>>> >>>> neutron port-pair-create --ingress=p1 --egress=p2 PP1 >>>> 404 Not Found >>>> >>>> The resource could not be found. >>>> >>>> Neutron server returns request_ids: >>>> ['req-1bfd0983-4a61-4b32-90b3-252004d90e65'] >>>> >>>> neutron --version >>>> 4.1.1 >>>> >>>> p1,p2,p3,p4 have already been created, I can ping instances attached to >>>> these ports. >>>> Since I've not installed networking-sfc, are there additional config to >>>> set in neutron config files ? >>>> Or is it due to neutron-client version ? >>>> >>>> Regards >>>> >>>> On 8 June 2016 at 20:31, Mohan Kumar <nmohankumar1...@gmail.com> wrote: >>>> >>>>> neutron agent not able to fetch details from ovsdb . Could you check >>>>> below options 1.restart ovsdb-server and execute ovs_vsctl list-br 2. >>>>> execute ovs- vsctl list-br manually and try to check error. >>>>> >>>>> 3. Could be ovs cleanup issue , please check the output of sudo >>>>> service openvswitch restart and /etc/init.d/openvswich** restart , both >>>>> should be same >>>>> >>>>> Thanks., >>>>> Mohankumar.N >>>>> On Jun 7, 2016 6:04 PM, "Alioune" <baliou...@gmail.com> wrote: >>>>> >>>>>> Hi Mohan/Cathy >>>>>> I'v
Re: [openstack-dev] [neutron][SFC]
Thanks Mohan, After setting service_plugins and adding sfc tables to neutrondb, I can create port-pair, port-pair-group but classifier creation still claim a logical-source-port parameter. neutron flow-classifier-create --ethertype IPv4 --source-ip-prefix 55.55.55.2/32 --destination-ip-prefix 55.55.55.9/32 --protocol tcp --source-port 22:22 --destination-port 1:65000 FC1 ERROR: neutron flow-classifier-create: error: argument --logical-source-port is required Try 'neutron help flow-classifier-create' for more information. Please someone can explain what does --logical-source-port correspond to ? Does the classifier require port-create like SF ? Regards, On 9 June 2016 at 09:21, Mohan Kumar <nmohankumar1...@gmail.com> wrote: > Alioune, > > networking-sfc resources not installed / not reachable , If installation > is okay, Possibly you may missed service_plugins entry in *neutron.conf *( > in case of manual networking-sfc installation) > > it should be , > > *service_plugins = > neutron.services.l3_router.l3_router_plugin.L3RouterPlugin,networking_sfc.services.flowclassifier.plugin.FlowClassifierPlugin,networking_sfc.services.sfc.plugin.SfcPlugin* > > *and restart q-svc services in screen -x * > > *Thanks.,* > *Mohankumar.N * > > On Thu, Jun 9, 2016 at 12:58 AM, Alioune <baliou...@gmail.com> wrote: > >> I've switched from devstack to a normal deployment of openstack/mitaka >> and neutron-l2 agent is working fine with sfc. I can boot instances, create >> ports. >> However I can not create neither flow-classifier nor port-pair ... >> >> neutron flow-classifier-create --ethertype IPv4 --source-ip-prefix >> 22.1.20.1/32 --destination-ip-prefix 172.4.5.6/32 --protocol tcp >> --source-port 23:23 --destination-port 100:100 FC1 >> >> returns: neutron flow-classifier-create: error: argument >> --logical-source-port is required >> Try 'neutron help flow-classifier-create' for more information. >> >> neutron port-pair-create --ingress=p1 --egress=p2 PP1 >> 404 Not Found >> >> The resource could not be found. >> >> Neutron server returns request_ids: >> ['req-1bfd0983-4a61-4b32-90b3-252004d90e65'] >> >> neutron --version >> 4.1.1 >> >> p1,p2,p3,p4 have already been created, I can ping instances attached to >> these ports. >> Since I've not installed networking-sfc, are there additional config to >> set in neutron config files ? >> Or is it due to neutron-client version ? >> >> Regards >> >> On 8 June 2016 at 20:31, Mohan Kumar <nmohankumar1...@gmail.com> wrote: >> >>> neutron agent not able to fetch details from ovsdb . Could you check >>> below options 1.restart ovsdb-server and execute ovs_vsctl list-br 2. >>> execute ovs- vsctl list-br manually and try to check error. >>> >>> 3. Could be ovs cleanup issue , please check the output of sudo service >>> openvswitch restart and /etc/init.d/openvswich** restart , both should be >>> same >>> >>> Thanks., >>> Mohankumar.N >>> On Jun 7, 2016 6:04 PM, "Alioune" <baliou...@gmail.com> wrote: >>> >>>> Hi Mohan/Cathy >>>> I've installed now ovs 2.4.0 and followed >>>> https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining but >>>> I got this error : >>>> Regards, >>>> >>>> + neutron-ovs-cleanup >>>> 2016-06-07 11:25:36.465 22147 INFO neutron.common.config [-] Logging >>>> enabled! >>>> 2016-06-07 11:25:36.468 22147 INFO neutron.common.config [-] >>>> /usr/local/bin/neutron-ovs-cleanup version 7.1.1.dev4 >>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl [-] >>>> Unable to execute ['ovs-vsctl', '--timeout=10', '--oneline', >>>> '--format=json', '--', 'list-br']. >>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl >>>> Traceback (most recent call last): >>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl >>>> File "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 63, in >>>> run_vsctl >>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl >>>> log_fail_as_error=False).rstrip() >>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl >>>> File "/opt/stack/neutron/neutron/agent/linux/utils.py", line 159, in >>>> execute >>>> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl >>>> raise RuntimeError(m) >>>&g
Re: [openstack-dev] [neutron][SFC]
I've switched from devstack to a normal deployment of openstack/mitaka and neutron-l2 agent is working fine with sfc. I can boot instances, create ports. However I can not create neither flow-classifier nor port-pair ... neutron flow-classifier-create --ethertype IPv4 --source-ip-prefix 22.1.20.1/32 --destination-ip-prefix 172.4.5.6/32 --protocol tcp --source-port 23:23 --destination-port 100:100 FC1 returns: neutron flow-classifier-create: error: argument --logical-source-port is required Try 'neutron help flow-classifier-create' for more information. neutron port-pair-create --ingress=p1 --egress=p2 PP1 404 Not Found The resource could not be found. Neutron server returns request_ids: ['req-1bfd0983-4a61-4b32-90b3-252004d90e65'] neutron --version 4.1.1 p1,p2,p3,p4 have already been created, I can ping instances attached to these ports. Since I've not installed networking-sfc, are there additional config to set in neutron config files ? Or is it due to neutron-client version ? Regards On 8 June 2016 at 20:31, Mohan Kumar <nmohankumar1...@gmail.com> wrote: > neutron agent not able to fetch details from ovsdb . Could you check below > options 1.restart ovsdb-server and execute ovs_vsctl list-br 2. execute > ovs- vsctl list-br manually and try to check error. > > 3. Could be ovs cleanup issue , please check the output of sudo service > openvswitch restart and /etc/init.d/openvswich** restart , both should be > same > > Thanks., > Mohankumar.N > On Jun 7, 2016 6:04 PM, "Alioune" <baliou...@gmail.com> wrote: > >> Hi Mohan/Cathy >> I've installed now ovs 2.4.0 and followed >> https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining but >> I got this error : >> Regards, >> >> + neutron-ovs-cleanup >> 2016-06-07 11:25:36.465 22147 INFO neutron.common.config [-] Logging >> enabled! >> 2016-06-07 11:25:36.468 22147 INFO neutron.common.config [-] >> /usr/local/bin/neutron-ovs-cleanup version 7.1.1.dev4 >> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl [-] >> Unable to execute ['ovs-vsctl', '--timeout=10', '--oneline', >> '--format=json', '--', 'list-br']. >> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl >> Traceback (most recent call last): >> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl File >> "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 63, in >> run_vsctl >> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl >> log_fail_as_error=False).rstrip() >> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl File >> "/opt/stack/neutron/neutron/agent/linux/utils.py", line 159, in execute >> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl >> raise RuntimeError(m) >> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl >> RuntimeError: >> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl >> Command: ['sudo', 'ovs-vsctl', '--timeout=10', '--oneline', >> '--format=json', '--', 'list-br'] >> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl Exit >> code: 1 >> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl >> 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl >> 2016-06-07 11:25:36.512 22147 CRITICAL neutron [-] RuntimeError: >> Command: ['sudo', 'ovs-vsctl', '--timeout=10', '--oneline', >> '--format=json', '--', 'list-br'] >> Exit code: 1 >> >> 2016-06-07 11:25:36.512 22147 ERROR neutron Traceback (most recent call >> last): >> 2016-06-07 11:25:36.512 22147 ERROR neutron File >> "/usr/local/bin/neutron-ovs-cleanup", line 10, in >> 2016-06-07 11:25:36.512 22147 ERROR neutron sys.exit(main()) >> 2016-06-07 11:25:36.512 22147 ERROR neutron File >> "/opt/stack/neutron/neutron/cmd/ovs_cleanup.py", line 89, in main >> 2016-06-07 11:25:36.512 22147 ERROR neutron ovs_bridges = >> set(ovs.get_bridges()) >> 2016-06-07 11:25:36.512 22147 ERROR neutron File >> "/opt/stack/neutron/neutron/agent/common/ovs_lib.py", line 132, in >> get_bridges >> 2016-06-07 11:25:36.512 22147 ERROR neutron return >> self.ovsdb.list_br().execute(check_error=True) >> 2016-06-07 11:25:36.512 22147 ERROR neutron File >> "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 83, in execute >> 2016-06-07 11:25:36.512 22147 ERROR neutron txn.add(self) >> 2016-06-07 11:25:36.512 22147 ERROR neutron File >> "/opt/stack/neutron/neutron/agent/ovsdb/api.py", line 70, in __exit__ >> 2016-06-07 11:25:36.512 22147 ERROR neutron
Re: [openstack-dev] [neutron][SFC]
Hi Mohan/Cathy I've installed now ovs 2.4.0 and followed https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining but I got this error : Regards, + neutron-ovs-cleanup 2016-06-07 11:25:36.465 22147 INFO neutron.common.config [-] Logging enabled! 2016-06-07 11:25:36.468 22147 INFO neutron.common.config [-] /usr/local/bin/neutron-ovs-cleanup version 7.1.1.dev4 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl [-] Unable to execute ['ovs-vsctl', '--timeout=10', '--oneline', '--format=json', '--', 'list-br']. 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl Traceback (most recent call last): 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl File "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 63, in run_vsctl 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl log_fail_as_error=False).rstrip() 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl File "/opt/stack/neutron/neutron/agent/linux/utils.py", line 159, in execute 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl raise RuntimeError(m) 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl RuntimeError: 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl Command: ['sudo', 'ovs-vsctl', '--timeout=10', '--oneline', '--format=json', '--', 'list-br'] 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl Exit code: 1 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl 2016-06-07 11:25:36.505 22147 ERROR neutron.agent.ovsdb.impl_vsctl 2016-06-07 11:25:36.512 22147 CRITICAL neutron [-] RuntimeError: Command: ['sudo', 'ovs-vsctl', '--timeout=10', '--oneline', '--format=json', '--', 'list-br'] Exit code: 1 2016-06-07 11:25:36.512 22147 ERROR neutron Traceback (most recent call last): 2016-06-07 11:25:36.512 22147 ERROR neutron File "/usr/local/bin/neutron-ovs-cleanup", line 10, in 2016-06-07 11:25:36.512 22147 ERROR neutron sys.exit(main()) 2016-06-07 11:25:36.512 22147 ERROR neutron File "/opt/stack/neutron/neutron/cmd/ovs_cleanup.py", line 89, in main 2016-06-07 11:25:36.512 22147 ERROR neutron ovs_bridges = set(ovs.get_bridges()) 2016-06-07 11:25:36.512 22147 ERROR neutron File "/opt/stack/neutron/neutron/agent/common/ovs_lib.py", line 132, in get_bridges 2016-06-07 11:25:36.512 22147 ERROR neutron return self.ovsdb.list_br().execute(check_error=True) 2016-06-07 11:25:36.512 22147 ERROR neutron File "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 83, in execute 2016-06-07 11:25:36.512 22147 ERROR neutron txn.add(self) 2016-06-07 11:25:36.512 22147 ERROR neutron File "/opt/stack/neutron/neutron/agent/ovsdb/api.py", line 70, in __exit__ 2016-06-07 11:25:36.512 22147 ERROR neutron self.result = self.commit() 2016-06-07 11:25:36.512 22147 ERROR neutron File "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 50, in commit 2016-06-07 11:25:36.512 22147 ERROR neutron res = self.run_vsctl(args) 2016-06-07 11:25:36.512 22147 ERROR neutron File "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 70, in run_vsctl 2016-06-07 11:25:36.512 22147 ERROR neutron ctxt.reraise = False 2016-06-07 11:25:36.512 22147 ERROR neutron File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in __exit__ 2016-06-07 11:25:36.512 22147 ERROR neutron six.reraise(self.type_, self.value, self.tb) 2016-06-07 11:25:36.512 22147 ERROR neutron File "/opt/stack/neutron/neutron/agent/ovsdb/impl_vsctl.py", line 63, in run_vsctl 2016-06-07 11:25:36.512 22147 ERROR neutron log_fail_as_error=False).rstrip() 2016-06-07 11:25:36.512 22147 ERROR neutron File "/opt/stack/neutron/neutron/agent/linux/utils.py", line 159, in execute 2016-06-07 11:25:36.512 22147 ERROR neutron raise RuntimeError(m) 2016-06-07 11:25:36.512 22147 ERROR neutron RuntimeError: 2016-06-07 11:25:36.512 22147 ERROR neutron Command: ['sudo', 'ovs-vsctl', '--timeout=10', '--oneline', '--format=json', '--', 'list-br'] 2016-06-07 11:25:36.512 22147 ERROR neutron Exit code: 1 2016-06-07 11:25:36.512 22147 ERROR neutron 2016-06-07 11:25:36.512 22147 ERROR neutron + exit_trap + local r=1 ++ jobs -p + jobs= + [[ -n '' ]] + kill_spinner + '[' '!' -z '' ']' + [[ 1 -ne 0 ]] + echo 'Error on exit' Error on exit + generate-subunit 1465296797 1939 fail + [[ -z /opt/stack/logs ]] + /home/alioune/devstack/tools/worlddump.py -d /opt/stack/logs World dumping... see /opt/stack/logs/worlddump-2016-06-07-112537.txt for details + exit 1 On 7 June 2016 at 12:08, Mohan Kumar <nmohankumar1...@gmail.com> wrote: > Hi shihanzhang / Alioune , > > *your kernel (check with uname -r ) should support OVS version , below > table compare kern*el versions and corresponding Open vSwitch release > support > > | Open vSwitch
[openstack-dev] [neutron][SFC]
Probleme with OpenStack SFC
Hi all,
I've installed Openstack SFC with devstack and all module are corretly
running except the neutron L2-agent
After a "screen -rd", it seems that there is a conflict between l2-agent
and SFC (see trace bellow).
I solved the issue with "sudo ovs-vsctl set bridge br
protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow13" on all openvswitch
bridge (br-int, br-ex, br-tun and br-mgmt0).
I would like to know:
- If someone knows why this error arrises ?
- is there another way to solve it ?
Regards,
2016-06-03 12:51:56.323 WARNING
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
[req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] OVS is dead.
OVSNeutronAgent will keep running and checking OVS status periodically.
2016-06-03 12:51:56.330 DEBUG
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
[req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] Agent rpc_loop -
iteration:4722 completed. Processed ports statistics: {'regular':
{'updated': 0, 'added': 0, 'removed': 0}}. Elapsed:0.086 from (pid=12775)
loop_count_and_wait
/opt/stack/neutron/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:1680
2016-06-03 12:51:58.256 DEBUG
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
[req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] Agent rpc_loop -
iteration:4723 started from (pid=12775) rpc_loop
/opt/stack/neutron/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:1732
2016-06-03 12:51:58.258 DEBUG neutron.agent.linux.utils
[req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] Running command
(rootwrap daemon): ['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int',
'table=23'] from (pid=12775) execute_rootwrap_daemon
/opt/stack/neutron/neutron/agent/linux/utils.py:101
2016-06-03 12:51:58.311 ERROR neutron.agent.linux.utils
[req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None]
Command: ['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int', 'table=23']
Exit code: 1
Stdin:
Stdout:
Stderr:
2016-06-03T12:51:58Z|1|vconn|WARN|unix:/var/run/openvswitch/br-int.mgmt:
version negotiation failed (we support version 0x04, peer supports version
0x01)
ovs-ofctl: br-int: failed to connect to socket (Broken pipe)
2016-06-03 12:51:58.323 ERROR
networking_sfc.services.sfc.common.ovs_ext_lib
[req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None]
Command: ['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int', 'table=23']
Exit code: 1
Stdin:
Stdout:
Stderr:
2016-06-03T12:51:58Z|1|vconn|WARN|unix:/var/run/openvswitch/br-int.mgmt:
version negotiation failed (we support version 0x04, peer supports version
0x01)
ovs-ofctl: br-int: failed to connect to socket (Broken pipe)
2016-06-03 12:51:58.323 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Traceback (most recent call
last):
2016-06-03 12:51:58.323 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib File
"/opt/stack/networking-sfc/networking_sfc/services/sfc/common/ovs_ext_lib.py",
line 125, in run_ofctl
2016-06-03 12:51:58.323 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib
process_input=process_input)
2016-06-03 12:51:58.323 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib File
"/opt/stack/neutron/neutron/agent/linux/utils.py", line 159, in execute
2016-06-03 12:51:58.323 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib raise RuntimeError(m)
2016-06-03 12:51:58.323 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib RuntimeError:
2016-06-03 12:51:58.323 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Command: ['ovs-ofctl', '-O
openflow13', 'dump-flows', 'br-int', 'table=23']
2016-06-03 12:51:58.323 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Exit code: 1
2016-06-03 12:51:58.323 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Stdin:
2016-06-03 12:51:58.323 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Stdout:
2016-06-03 12:51:58.323 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib Stderr:
2016-06-03T12:51:58Z|1|vconn|WARN|unix:/var/run/openvswitch/br-int.mgmt:
version negotiation failed (we support version 0x04, peer supports version
0x01)
2016-06-03 12:51:58.323 TRACE
networking_sfc.services.sfc.common.ovs_ext_lib ovs-ofctl: br-int: failed to
connect to socket (Broken pipe)
2016-06-03 12:51:58.323 TRACE networking_sfc.services.sfc.common.ovs_ext_lib
2016-06-03 12:51:58.323 TRACE networking_sfc.services.sfc.common.ovs_ext_lib
2016-06-03 12:51:58.335 ERROR
networking_sfc.services.sfc.common.ovs_ext_lib
[req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] Unable to execute
['ovs-ofctl', '-O openflow13', 'dump-flows', 'br-int', 'table=23'].
2016-06-03 12:51:58.337 WARNING
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
[req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None None] OVS is dead.
OVSNeutronAgent will keep running and checking OVS status periodically.
2016-06-03 12:51:58.341 DEBUG
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
[req-1258bbbc-7211-4cfd-ab7c-8b856604f768 None
[openstack-dev] [Tacker] Can not launch new VNF
Hi all,
It's my first time using Tacker, I've installed it with Openstack/libery
using [1].
I've created a VNFD but I always got the following erreor when I tried to
launch new VNF.
Someone knowshow to correct that error ?
Regards,
tacker vnfd-list
+--+-+--+--+-+
| id | name|
description| infra_driver | mgmt_driver |
+--+-+--+--+-+
| 10813e8e-1375-4751-ab49-db2dfcf1cb27 | my_vnfd | demo-example | heat
| noop|
+--+-+--+--+-+-
vnf-create --name my_vnf --vnfd-id 10813e8e-1375-4751-ab49-db2dfcf1cb27
2 ERROR root [-] Original exception being dropped: ['Traceback (most recent
call last):\n',
' File "/usr/local/lib/python2.7/dist-packages/tacker/vm/plugin.py", line
249, in _create_device\ncontext=context, device=device_dict)\n',
' File
"/usr/local/lib/python2.7/dist-packages/tacker/common/driver_manager.py",
line 75, in invoke\nreturn getattr(driver, method_name)(**kwargs)\n',
' File "/usr/local/lib/python2.7/dist-packages/tacker/common/log.py",
line 34, in wrapper\nreturn method(*args, **kwargs)\n',
' File
"/usr/local/lib/python2.7/dist-packages/tacker/vm/drivers/heat/heat.py",
line 320, in create\nstack = heatclient_.create(fields)\n',
' File
"/usr/local/lib/python2.7/dist-packages/tacker/vm/drivers/heat/heat.py",
line 486, in create\nreturn self.stacks.create(**fields)\n',
' File "/usr/lib/python2.7/dist-packages/heatclient/v1/stacks.py", line
136, in create\ndata=kwargs, headers=headers)\n',
' File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py", line
287, in post\nreturn self.client_request("POST", url, **kwargs)\n',
' File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py", line
277, in client_request\nresp, body = self.json_request(method, url,
**kwargs)\n',
' File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py", line
266, in json_request\nresp = self._http_request(url, method,
**kwargs)\n',
' File "/usr/lib/python2.7/dist-packages/heatclient/common/http.py", line
196, in _http_request\n**kwargs)\n',
' File "/usr/lib/python2.7/dist-packages/requests/api.py", line 50, in
request\nresponse = session.request(method=method, url=url,
**kwargs)\n',
' File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 465,
in request\nresp = self.send(prep, **send_kwargs)\n',
' File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 573,
in send\nr = adapter.send(request, **kwargs)\n',
' File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 415,
in send\nraise ConnectionError(err, request=request)\n',
"ConnectionError: ('Connection aborted.', error(111, 'ECONNREFUSED'))\n"]
2016-05-17 14:19:55.814 29892 ERROR tacker.api.v1.resource
[req-9a0ae91c-6e98-4f95-8548-697874339b1e None] create failed
[1]
http://tacker-docs.readthedocs.io/en/latest/install/manual_installation.html
__
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
