Hi Ciprian,
Thank you for checking out Doctor project and reaching out us. In Danube, we officially support OpenStack Congress, but haven’t supported Vitrage yet. See, our release notes [1]. I’m not a fuel expert, but doctor driver in Congress may not be enabled in default, as it is not in the default driver list to be loaded in upstream codebase. but it is available with proper Congress configuration. Otherwise, the driver code was omitted from the original Congress code in fuel plugin. Such situation couldn’t happen normally. Regarding Vitrage, I know they have doctor driver and you can check out [2]. We found there is polling mechanism in Zabbix, that is potentially make a delay in passing fault notification to Consumers. Due to that observation, we are not pushing Zabbix as typical Doctor Component so far, although it sometimes makes sense when you see benefits in other aspects, e.g. you want to integrate software you or operators are familiar with. You can also get our sample implementation of Doctor Components in Doctor repo [2]. Those may provide more detail of how to integrate. Regarding the demo you pointed, we used Nova, Congress, Ceilometer and Aodh along with sample Monitor and Consumer which are similar to what we have in Doctor repo. We changed Monitor to monitor redundant NIC ports and had a quick hack in Consumer to handle commercial EPC though. Vitrage was also used to receive the fault notification from Monitor and to show the holistic view of system status, along with fault propagation. [1] http://docs.opnfv.org/en/stable-danube/submodules/doctor/docs/release/release-notes/releasenotes.html [2] https://gerrit.opnfv.org/gerrit/gitweb?p=doctor.git;a=blob;f=docs/release/configguide/feature.configuration.rst#l81 [3] https://gerrit.opnfv.org/gerrit/gitweb?p=doctor.git;a=tree;f=tests; Best regards, Ryota From: Ciprian Barbu [mailto:ciprian.ba...@enea.com] Sent: Monday, July 24, 2017 7:23 AM To: Mibu Ryota(壬生 亮太) <r-m...@cq.jp.nec.com> Cc: Cristina Pauna <cristina.pa...@enea.com>; opnfv-tech-discuss@lists.opnfv.org Subject: [opnfv-tech-discuss][Doctor] Integration with VNFM Hello, I’ve been studying closely the Doctor Documentation and trying to understand the Doctor Architecture, particularly the applicability in a real life situation. I’m trying to understand how are the Doctor components supposed to interact in order to fulfill an end-to-end HA solution. Looking at the documentation, the roles of the Consumer and Administrator, are loosely defined, I only found some information about these being out of the scope of the Doctor project. However, I’m trying to get some sort of guidance on how to connect the Doctor components with an existing VNFM/MANO solution, like Tacker for example. For now, we have an OPNFV Danube Fuel based deployment that also contains the following components: - Vitrage as Doctor Inspector - Congress as Doctor Inspector/Policy enforcer, as an alternative to Vitrage; note that the Congress Fuel Plugin in OPNFV does not contain Doctor driver, so a newer version is used instead - Zabbix as Doctor Monitor; also configured to work with Vitrage The other roles, as described by Doctor Architecture, should be covered by Openstack components, Nova, Neutron, Cinder, Ceilometer etc. On top of these there should be a Consumer, in this case we’re looking at the Tacker Fuel Plugin available with OPNFV Fuel. At first look Tacker seems to lack a proper Northbound interface that would implement the NFV IFA Vi-Vnfm Reference Point, but there is a blueprint [1] that was completed and included in a newer version. I know that the Doctor project worked with Vitrage and possibly even Zabbix, so I’m interested to learn more about the capability of Vitrage to generate alarms that would be sent to the Consumer. I also found out that the alarms can be in fact sent by Openstack itself when the virtual resources change states, like the nova-force-down API. But in one of the Doctor demo’s, the one on the community page [2], there is a different scenario where a network cable is unplugged. So I would like answers for a few questions: 1. What components does the live call demo make use of? 2. Is there any kind of VNF Manager in there or is there a simple sample consumer, like in the functest tests? 3. Will Doctor consider covering the role of Consumer, and if yes, what are the likely candidates? 4. What kind of work/usecases has been done with VItrage? [1] https://blueprints.launchpad.net/tacker/+spec/alarm-based-monitoring-driver [2] https://www.opnfv.org/community/projects/doctor Thank you and best regards, Ciprian Barbu
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
