Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

Revision history [back]

click to hide/show revision 1
initial version

After restart OpenDaylight is out of sync with Openstack after

Hi,

I have installation of Opnestack Kilo (2015.1.1) integrated with OpenDaylight Lithium-SR2. I can create networks, boot instances, assign floating IPs, etc. Everything works fine until I need to restart ODL. To do that I login to karaf and execute shutdown. Then I when I start ODL again I see that it controller API does not return any networks and ports:

curl ... /controller/nb/v2/neutron/networks
{
   "networks" : [ ]
}
curl ... /controller/nb/v2/neutron/ports
{
   "ports" : [ ]
}

At that point the communication with instances is still intact. I am able to boot instance at that stage, and I see that after the instance boots, the "controller/nb/v2/neutron/networks" returns correct list of networks, but the "controller/nb/v2/neutron/ports" returns only ports associated with the newly booted instance.

Then when I reboot any instance there is no communication possible with it, even from it's dhcp or qrouter namespace. I've tried restarting neutron but does not help.

Is there special procedure I should follow to sync OpenDaylight with Openstack after restart?

Currently the only recovery path I know that works is to recreate all networks and reattach interfaces to instance's. I think there must be better way, of restarting OpenDaylight. Please advise.

After restart OpenDaylight is out of sync with Openstack afterOpenstack

Hi,

I have installation of Opnestack Kilo (2015.1.1) integrated with OpenDaylight Lithium-SR2. I can create networks, boot instances, assign floating IPs, etc. Everything works fine until I need to restart ODL. To do that I login to karaf and execute shutdown. Then I when I start ODL again I see that it controller API does not return any networks and ports:

curl ... /controller/nb/v2/neutron/networks
{
   "networks" : [ ]
}
curl ... /controller/nb/v2/neutron/ports
{
   "ports" : [ ]
}

At that point the communication with instances is still intact. I am able to boot instance at that stage, and I see that after the instance boots, the "controller/nb/v2/neutron/networks" returns correct list of networks, but the "controller/nb/v2/neutron/ports" returns only ports associated with the newly booted instance.

Then when I reboot any instance there is no communication possible with it, even from it's dhcp or qrouter namespace. I've tried restarting neutron but does not help.

Is there special procedure I should follow to sync OpenDaylight with Openstack after restart?

Currently the only recovery path I know that works is to recreate all networks and reattach interfaces to instance's. I think there must be better way, of restarting OpenDaylight. Please advise.

After restart OpenDaylight is out of sync with Openstack

Hi,

I have installation of Opnestack Kilo (2015.1.1) integrated with OpenDaylight Lithium-SR2. I can create networks, boot instances, assign floating IPs, etc. Everything works fine until I need to restart ODL. To do that I login to karaf and execute shutdown. Then I when I start ODL again I see that it controller API does not return any networks and ports:

curl ... /controller/nb/v2/neutron/networks
{
   "networks" : [ ]
}
curl ... /controller/nb/v2/neutron/ports
{
   "ports" : [ ]
}

At that point the communication with instances is still intact. I am able to new boot instance at that stage, and I see that after the instance boots, the "controller/nb/v2/neutron/networks" returns correct list of networks, but the "controller/nb/v2/neutron/ports" returns only ports associated with the newly booted instance.

Then when I reboot any instance there is no communication possible with it, even from it's dhcp or qrouter namespace. I've tried restarting neutron but does not help.

Is there special procedure I should follow to sync OpenDaylight with Openstack after restart?

Currently the only recovery path I know that works is to recreate all networks and reattach interfaces to instance's. I think there must be better way, of restarting OpenDaylight. Please advise.

After restart OpenDaylight is out of sync with Openstack

Hi,

I have installation of Opnestack Kilo (2015.1.1) integrated with OpenDaylight Lithium-SR2. I can create networks, boot instances, assign floating IPs, etc. Everything works fine until I need to restart ODL. To do that I login to karaf and execute shutdown. Then when I start ODL again I see that controller API does not return any networks and ports:

curl ... /controller/nb/v2/neutron/networks
{
   "networks" : [ ]
}
curl ... /controller/nb/v2/neutron/ports
{
   "ports" : [ ]
}

At that point the communication with instances is still intact. I am able to new boot instance at that stage, and I see that after the instance boots, the "controller/nb/v2/neutron/networks" returns correct list of networks, but the "controller/nb/v2/neutron/ports" returns only ports associated with the newly booted instance.

Then when I reboot any instance there is no communication possible with it, even from it's dhcp or qrouter namespace. I've tried restarting neutron but does not help.

Is there special procedure I should follow to sync OpenDaylight with Openstack after restart?

Currently the only recovery path I know that works is to recreate all networks and reattach interfaces to instance's. I think there must be better way, of restarting OpenDaylight. Please advise.