Hi Venkat, I'm using Helium SR2 as it is suggested in the wiki. So you suggest to use Lithium or it is a negligible problem? Thanks. Silvia
2015-07-13 21:04 GMT+02:00 Venkatrangan G - ERS, HCL Tech < venkatrang...@hcl.com>: > Hi Silvia, > > > > It is enough to just stack again. To provide more info, Can you please > confirm if you are using Helium or Lithium release of OpenDayLight. With > the Helium release, the removed switches may still feature in the dlux > topology but with no ports. But the new topology will work fine with no > issues. This may not occur in the Lithium release. Please let us know in > case of any queries > > > > Regards, > > Venkat G > > > > *From:* Silvia Fichera [mailto:fichera....@gmail.com] > *Sent:* Wednesday, July 8, 2015 3:04 AM > > *To:* Venkatrangan G - ERS, HCL Tech > *Cc:* vtn-...@lists.opendaylight.org; openstack@lists.openstack.org > *Subject:* Re: [vtn-dev] Broken links > > > > Hi Venkat, > > according to the last problem I reported, could also be that the ODL > controller sees pending instances? > > I mean, if the odl controller goes down when there are some lauched > instances, when I restart it and I stack again the ODL COntroller still > sees instances that are no more launched in OpenStack. So I have to install > again also ODL, not only stack again. > > Could you confirm this? > > > > Thanks > > Silvia > > > > 2015-06-26 19:43 GMT+02:00 Venkatrangan G - ERS, HCL Tech < > venkatrang...@hcl.com>: > > Hi Silvia, > > Good that you are able to sort out the topology view. > > I believe that openstack creates the public network and sub network when > it starts up. so my opinion is when the controller was restarted these > references got removed. so please restack. also to avoid manual > configuraton of ovs please create vtn.ini and restart odl. if you stack > after that the ovs settings would be done by vtn manager in odl. > > kindly let us know in case of any queries. > > Regards, > Venkat George > > > > On Fri, Jun 26, 2015 at 2:38 AM -0700, "Silvia Fichera" < > fichera....@gmail.com> wrote: > > Hi Venkat, > > I've verified if eth1 was mapped on br-int and it was not. So I've > unstacked and restart everything and than eth1 was mapped. Now it works. > Thanks. > > > > There is still a problem when I restart the ODL controller. > > In fact after restarting ODL if I try to add a network I have this error > in Openstack: > > > > *Error: *Failed to create network "Net": create_network_postcommit failed. > > > > And if I try to create a new instance: > > > > *Error: *Failed to launch instance "asd": Please try again later [Error: > No valid host was found. Exceeded max scheduling attempts 3 for instance > 87a3545e-e067-4193-8aaf-8bfa9de6385d. Last exception: [u'Traceback (most > recent call last):\n', u' File "/opt/stack/nova/nova/compute/manager.py", > line 2081, in _do_build_and_run_in]. > > > > What happens? > > I don't think that I have to reinstall everything everytime that I restart > the controller... > > > > Thanks for your support > > > > 2015-06-25 18:15 GMT+02:00 Venkatrangan G - ERS, HCL Tech < > venkatrang...@hcl.com>: > > Hi Silvia, > > > > I hope you have checked the sudo ovs-vsctl show annd the correct port > eth1 is mapped to br-int?, Can you share that output if possible. > > > > This command to dump flows is actually for Openflow 1.0, Please try sudo > ovs-ofctl dump-flows –OopenFlow13, that will work successfully. > > > > > > Regards, > > Venkat G > > > > > > *From:* Silvia Fichera [mailto:fichera....@gmail.com] > *Sent:* 25 June 2015 07:43 > *To:* Venkatrangan G - ERS, HCL Tech > *Cc:* vtn-...@lists.opendaylight.org; openstack@lists.openstack.org > *Subject:* Re: [vtn-dev] Broken links > > > > I also noticed that when I try: > > > > sudo ovs-ofctl dump-flows br-int > > > > to check if the flow was installed properly I receive this message: > > > > 2015-06-25T14:36:37Z|00001|vconn|WARN|unix:/var/run/openvswitch/br-int.mgmt: > version negotiation failed (we support version 0x01, peer supports version > 0x04) > > ovs-ofctl: br-int: failed to connect to socket (Broken pipe) > > > > Moreover, in Karaf, I've done: > > > > web:list > > > > and I can see that the services related to neutron are active but in a > failed web state. > > > > ID | State | Web-State | Level | Web-ContextPath > | Name > > > ------------------------------------------------------------------------------------------------------------------------------------------------- > > 219 | Active | Failed | 80 | > /controller/nb/v2/connectionmanager | connectionmanager.northbound > (0.1.4.Helium-SR2) > > 220 | Active | Failed | 80 | /controller/nb/v2/flowprogrammer > | flowprogrammer.northbound (0.4.4.Helium-SR2) > > 221 | Active | Failed | 80 | /controller/nb/v2/hosttracker > | hosttracker.northbound (0.4.4.Helium-SR2) > > 222 | Active | Failed | 80 | > /controller/nb/v2/networkconfig/bridgedomain | > networkconfig.bridgedomain.northbound (0.0.5.Helium-SR2) > > 223 | Active | Failed | 80 | /controller/nb/v2/neutron > | networkconfig.neutron.northbound (0.4.4.Helium-SR2) > > 224 | Active | Failed | 80 | /controller/nb/v2/staticroute > | forwarding.staticrouting.northbound (0.4.4.Helium-SR2) > > 225 | Active | Failed | 80 | /controller/nb/v2/statistics > | statistics.northbound (0.4.4.Helium-SR2) > > 226 | Active | Failed | 80 | /controller/nb/v2/subnetservice > | subnets.northbound (0.4.4.Helium-SR2) > > 227 | Active | Failed | 80 | /controller/nb/v2/switchmanager > | switchmanager.northbound (0.4.4.Helium-SR2) > > 228 | Active | Failed | 80 | /controller/nb/v2/topology > | topology.northbound (0.4.4.Helium-SR2) > > 229 | Active | Failed | 80 | /controller/nb/v2/usermanager > | usermanager.northbound (0.0.4.Helium-SR2) > > 232 | Active | Failed | 80 | /controller/nb/v2/vtn > | manager.northbound (0.2.2.Helium-SR2) > > 238 | Active | Failed | 80 | /ovsdb/nb > | OpenDaylight OVSDB Northbound APIs (0.6.2.Helium-SR2) > > > > Could this be helpful? > > Thanks > > > > 2015-06-25 11:45 GMT+02:00 Silvia Fichera <fichera....@gmail.com>: > > I'm sorry, I have another doubt about promiscuos mode. > > The controller node and the compute nodes, as you said, are created with > vSphere. But in this environment there is not only those VMs that I'm > using, but also some other. Who manages this system enabled in promiscuos > mode the bridges that connect my VMs (data network), and the bridge related > to the management network. > > I did not enabled the bridge that exposes externally ALL VMs that are in > the server (security reasons). Could be this the problem? > > > > Thanks > > > > 2015-06-24 15:17 GMT+02:00 Silvia Fichera <fichera....@gmail.com>: > > Hi Venkat, > > I've checked that everything is in promiscuos mode, the interfaces are > enabled and I have also added the flow that you told me (it's the same of > the wiki). > > Nothing has changed, links are still broken. > > Any other hypothesis or something that I could try? > > > > 2015-06-23 21:09 GMT+02:00 Venkatrangan G - ERS, HCL Tech < > venkatrang...@hcl.com>: > > Hi Silvia, > > > > Thanks for your interest in this integration. > > Assuming you are using Helium release (these are some tested steps in > Helium when the same problems were reported). > > There are multiple things that you could do to debug this situation > > a. If you are using vsphere to create the control node and compute > VM’s then please enable the (Accept Promiscuous mode) > > > > b. Sometimes, the Ethernet interfaces may not be “UP” so please > check ifconfig and if the interface name does ot show up, it is probably > nnot iun UP. Please bring it up manually ifup <interface_name> > > > > > > c. Finally, try adding the default flow > > ovs-ofctl --protocols=OpenFlow13 add-flow br-int > priority=0,actions=output:CONTROLLER > > > > in all the nodes and try the dlux GUI to cjheck if the links appeared. > > > > > > Kindly let us know in case of any queries. > > > > Regards, > > Venkat G > > > > > > *From:* vtn-dev-boun...@lists.opendaylight.org [mailto: > vtn-dev-boun...@lists.opendaylight.org] *On Behalf Of *Silvia Fichera > *Sent:* 23 June 2015 08:50 > *To:* vtn-...@lists.opendaylight.org; openstack@lists.openstack.org > *Subject:* [vtn-dev] Broken links > > > > Hi all, > > I have installed openstack following the wiki for VTN integration, but > when I visualize the topology I can see the switches but there are no links > between them. > > The stacking operation seems to be successful. > > Someone can help me. > > Ask if you need further details. > > Regards > > > > -- > > Silvia Fichera > > > > ::DISCLAIMER:: > > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > E-mail transmission is not guaranteed to be secure or error-free as > information could be intercepted, corrupted, > lost, destroyed, arrive late or incomplete, or may contain viruses in > transmission. The e mail and its contents > (with or without referred errors) shall therefore not attach any liability > on the originator or HCL or its affiliates. > Views or opinions, if any, presented in this email are solely those of the > author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, > distribution and / or publication of this message without the prior > written consent of authorized representative of > HCL is strictly prohibited. If you have received this email in error > please delete it and notify the sender immediately. > Before opening any email and/or attachments, please check them for viruses > and other defects. > > > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > > > > > -- > > Silvia Fichera > > > > > > -- > > Silvia Fichera > > > > > > -- > > Silvia Fichera > > > > > > -- > > Silvia Fichera > > > > > > -- > > Silvia Fichera > -- Silvia Fichera
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack