Anton, I should have been a bit more explicit in my previous email.
The SFC103/104 demos are intended for a stand-alone, Non-OpenStack (hence no OPNFV needed) setup. Basically, they use vagrant to setup the necessary VMs. These demos do not use Tacker. In an OPNFV deployment, there needs to be an entity that spins-up and manages VMs for the SFC SFs, and ODL wont (and shouldnt) do that. This functionality is called a VNF Manager. Tacker is a VNF Manager (and some orchestration) as it does VNF management and orchestrates the SF VM info to ODL SFC. If you dont use Tacker, and dont have another VNF Manager, then you'll need to handle the VMs by hand, which is possible, but can be very tedious. Regards, Brady -----Original Message----- From: "Chivkunov, Anton" <achiv...@mera.ru<mailto:%22Chivkunov,%20anton%22%20%3cachiv...@mera.ru%3e>> To: Brady Allen Johnson <brady.allen.john...@ericsson.com<mailto:brady%20allen%20johnson%20%3cbrady.allen.john...@ericsson.com%3e>>, Michail Polenchuk <mpolenc...@mirantis.com<mailto:michail%20polenchuk%20%3cmpolenc...@mirantis.com%3e>>, mb...@suse.com <mb...@suse.com<mailto:%22mb...@suse.com%22%20%3cmb...@suse.com%3e>> Cc: opnfv-tech-discuss@lists.opnfv.org <opnfv-tech-discuss@lists.opnfv.org<mailto:%22opnfv-tech-disc...@lists.opnfv.org%22%20%3copnfv-tech-disc...@lists.opnfv.org%3e>> Subject: RE: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for SFs/SFFs/Classifiers creation Date: Wed, 15 Mar 2017 09:35:45 +0000 Hi Brady. Thank you for your feedback! Yes, I saw demos 103/104 as well and the reason why I interested in 101/102 instead is because they don’t use Tacker, but 103/104 use it. Our current installation based on instruction http://artifacts.opnfv.org/sfc/review/20587/installationprocedure-single/index.html (5.2.4. Feature configuration on existing Fuel), and this instruction didn’t contain installation of Tacker plugin. Only next two are mentioned there: fuel plugins --install fuel-plugin-ovs-*.noarch.rpm fuel plugins --install opendaylight-*.noarch.rpm Therefore we have no Tacker installed currently. It is not big problem (sure we can install Tacker), but this is the reason why we looked for the way how to run SFC without Tacker. Meanwhile, we have setup with 3 Controller and 2 compute nodes. I’m wondering if there are some significant difference in compare with VM setup (we have no virtualbox & vagrant, which were used in SFC103)? BR/Anton. From: Brady Allen Johnson [mailto:brady.allen.john...@ericsson.com] Sent: Wednesday, March 15, 2017 12:22 PM To: Michail Polenchuk; mb...@suse.com; Chivkunov, Anton Cc: opnfv-tech-discuss@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for SFs/SFFs/Classifiers creation Anton, The SFC101 and 102 demos are outdated and no longer supported. Its best to look at either the SFC103 or 104 demos. The sfc-agent is still used in SFC103, but we will soon stop supporting it. The SFC103 demo is a great way to run and execute SFC in a single VM. If you want to create SFs, SFFs, and classifiers in an OPNFV context, the best would be to use Tacker. Regards, Brady -----Original Message----- From: Michael Polenchuk <mpolenc...@mirantis.com<mailto:michael%20polenchuk%20%3cmpolenc...@mirantis.com%3e>> To: "Chivkunov, Anton" <achiv...@mera.ru<mailto:%22Chivkunov,%20anton%22%20%3cachiv...@mera.ru%3e>>, Manuel Buil <mb...@suse.com<mailto:manuel%20buil%20%3cmb...@suse.com%3e>> Cc: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> <opnfv-tech-discuss@lists.opnfv.org<mailto:%22opnfv-tech-disc...@lists.opnfv.org%22%20%3copnfv-tech-disc...@lists.opnfv.org%3e>> Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] SFC agent for SFs/SFFs/Classifiers creation Date: Wed, 15 Mar 2017 11:45:46 +0400 Hi Anton, + Manuel I believe Manuel has more experience with SFC than me. On Wed, Mar 15, 2017 at 10:09 AM, Chivkunov, Anton <achiv...@mera.ru<mailto:achiv...@mera.ru>> wrote: Hi Michael. If I didn’t cross the limit yet, I want to ask one more question about PlugIn ☺ On SFC main page (https://wiki.opendaylight.org/view/Service_Function_Chaining:Main) there are several Demos available. Demos 101&102 describe procedure of SFs/SFFs/Classifiers creation (https://drive.google.com/file/d/0BzS_qWNqsnQbUnEzU3BqVzdueTQ/view). There mentioned that SFC agent have to be started on corresponding node for this purpose. To start SFC agent there is special script “start_agent.sh”. But in our installation, with ODL/SFC as Plugin, we have no this script available. I’m wondering if we need just to load this script from SFC repo and use it, or there is another method for SFs/SFFs/Classifiers creation provided in environments, deployed by Fuel, and we should use some other way to create SFs/SFFs/Classifiers? *Not 100% sure that this question is really related to plugin. If it is not, then please sorry for this. BR/Anton. From: Chivkunov, Anton Sent: Friday, March 03, 2017 11:20 AM To: 'Michael Polenchuk' Cc: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: RE: [opnfv-tech-discuss] [fuel][plugins][odl] HW requirements for ODL Controller with SFC. Hi Michael. Thank you for advice! Currently we are trying to use our most powerful node (16Gb of RAM and 4-cores CPU) for Openstack + ODL Controller. Also we requested additional RAM for all 5 nodes, to have 16-32Gb on each. If it will not help we also will try with dedicated node for ODL controller as you suggested. BR/Anton. From: Michael Polenchuk [mailto:mpolenc...@mirantis.com] Sent: Friday, March 03, 2017 11:10 AM To: Chivkunov, Anton Cc: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: Re: [opnfv-tech-discuss] [fuel][plugins][odl] HW requirements for ODL Controller with SFC. 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<mailto: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: [cid:1489576205.3611.34.camel@ericsson.com] 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<mailto: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] Sent: Monday, February 20, 2017 10:51 AM To: Chivkunov, Anton Cc: opnfv-tech-discuss@lists.opnfv.org<mailto: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<mailto: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<mailto: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): [cid:1489576205.3611.35.camel@ericsson.com] When we try to open 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<mailto: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<mailto: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<mailto:opnfv-tech-discuss@lists.opnfv.org> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
