Hi Anton, Definitely the timeout and low performance caused by RAM capacity. I guess you have a lot of processes in swap. I would recommend to dedicate one node to opendaylight controller since 8Gb is actually ain't enough for openstack+odl. Also for the openstack controllers itself the minimum/required RAM is ~10-11Gb.
On Thu, Mar 2, 2017 at 2:33 PM, Chivkunov, Anton <achiv...@mera.ru> wrote: > Hi all. > > > > Sorry to bother you again, but we want to consult regarding HW > requirements for Controller node, which act as ODL controller as well. > > As it was described in initial mail, we have an environment, which consist > of Fuel master node, 3 Controller and 2 compute nodes. > > Controller nodes have 2-core Intel(R) Core(TM) i3-2100 CPUs. Two out of 3 > controllers have 8Gb of RAM, and one – 6 (not 16)Gb. ODL controller is one > of 8Gb nodes. > > > > Compute nodes have 16Gb RAM and next CPUs: > > Intel(R) Core(TM) i5-4460 CPU > > Intel(R) Core(TM) i3 CPU > > > > First of all, quite often during deployments in this configuration one or > few nodes can go away and back online: > Node 'Controller1 n103262' is back online > > Node 'Controller1 n103262' has gone away > > > > After such attempts part of functions are not operational and many tests > fails. > > When we are lucky and nodes were not away during deploy, most part of > tests works, only few of them may fail due to timeouts and work only after > several re-runs. > > At this step we are able to create/ping instances and so on, but as soon > as we install SFC UI and try do to something there everything breaks: > > - Existing instances are not pingable > > - New instances can’t be created due to error from > nova-scheduler (no hosts found) > > - CPU load on ODL controller becomes extremely high (up to > 100%) and even Controller restart doesn’t help > > - ODL controller goes away and back online in fuel time to time > > - SFC UI very-very slow > > > > I’m wondering if all these problems are due to low performance of our > node? In presentation from Luis Gomez I fount next table with requirements > and we are above minimum values: > > > > But I guess it might be for configurations without OpenStack and when ODL > work as PlugIn for Fuel/Openstack requirements should be higher? > > For example on http://artifacts.opnfv.org/pharos/docs/pharos-spec.html I > see that 32Gb and Intel Xeon E5-2600v2 Series (Ivy Bridge and newer, or > similar) are mentioned. > > > > Could you please confirm if our problems are really due to too low > performance of HW and if so, then which characteristics are recommended? > > > > Thank you in advance! > > BR/Anton. > > > > *From:* Chivkunov, Anton > *Sent:* Monday, February 20, 2017 11:28 AM > *To:* 'Michael Polenchuk' > *Cc:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* RE: [opnfv-tech-discuss] [fuel][plugins][odl] SFC UI > > > > Hi Michael. > > > > Ok, clear, thank you for clarifications! > > I’m really happy that we were able to get UI after installing > “feature:install odl-sfc-ui”, proposed by Pau. > > > > Thanks to both of you for quick response! > > > > BR/Anton. > > > > > > *From:* Michael Polenchuk [mailto:mpolenc...@mirantis.com > <mpolenc...@mirantis.com>] > *Sent:* Monday, February 20, 2017 10:51 AM > *To:* Chivkunov, Anton > *Cc:* opnfv-tech-discuss@lists.opnfv.org > *Subject:* Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC UI > > > > Hi Anton, > > The patch is on review: > https://review.openstack.org/435878 > > > > On Fri, Feb 17, 2017 at 3:06 PM, Chivkunov, Anton <achiv...@mera.ru> > wrote: > > Just want to modify subject. > > > > *From:* Chivkunov, Anton > *Sent:* Friday, February 17, 2017 1:53 PM > *To:* 'opnfv-tech-discuss@lists.opnfv.org' > *Subject:* [fuel][plugins][odl] > > > > Hi Experts! > > > > We have an environment, which consist of 3 Controller and 2 compute nodes, > where we would like to try SFC. > > Deployment was done using Fuel, with OpenDaylight (with SFC features) and > Openvswitch plugins installed. But after deployment in OpenDaylight DLUX > user interface we don’t have anything related to SFC. It refer us to page > like this (not …/sfc/index.html): > > > > When we try to open http://192.168.203.210:8181/*sfc/*index.htm > <http://192.168.203.210:8181/sfc/index.htm> manually, we getting error > (no such page) > > > > When I go to OpenDaylight shell on controller node, I see in the list of > installed features that next SFC-related features are installed: > > opendaylight-user@root>feature:list -i | grep -i sfc > > odl-ovsdb-sfc-api | 1.3.0-Boron | > x | odl-ovsdb-sfc-1.3.0-Boron | OpenDaylight :: > ovsdb-sfc :: api > > odl-ovsdb-sfc | 1.3.0-Boron | > x | odl-ovsdb-sfc-1.3.0-Boron | OpenDaylight :: > ovsdb-sfc > > odl-ovsdb-sfc-rest | 1.3.0-Boron | > x | odl-ovsdb-sfc-1.3.0-Boron | OpenDaylight :: > ovsdb-sfc :: REST > > odl-sfc-model | 0.3.0-Boron | > x | odl-sfc-0.3.0-Boron | OpenDaylight :: sfc :: > Model > > odl-sfc-provider | 0.3.0-Boron | > x | odl-sfc-0.3.0-Boron | OpenDaylight :: sfc :: > Provider > > odl-sfc-provider-rest | 0.3.0-Boron | > x | odl-sfc-0.3.0-Boron | OpenDaylight :: sfc :: > Provider > > odl-sfc-ovs | 0.3.0-Boron | > x | odl-sfc-0.3.0-Boron | OpenDaylight :: > OpenvSwitch > > odl-sfc-openflow-renderer | 0.3.0-Boron | > x | odl-sfc-0.3.0-Boron | OpenDaylight :: > sfc-openflow-renderer > > > > I’m wondering if we have to do some additional steps after Fuel deployment > with plugin to get SFC UI available? I was not able to find any instruction > for this part and supposed that OpenDaylight DLUX user interface will open > SFC UI. > > > > Thank you in advance! > > BR/Anton. > > > _______________________________________________ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > > > -- > > Michael Polenchuk > Private Cloud / Mirantis Inc. > > _______________________________________________ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > -- Michael Polenchuk Private Cloud / Mirantis Inc.
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
