Hi, all. I have just finished tagging the availability repo for the Danube release. Everything seems quite OK. Thank you for everyone for the work in the D release, especially to Greg for the API work, and Qiu Juan and Kanglin for the HA testcase work.
-----邮件原件----- 发件人: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Fu Qiao 发送时间: 2017年3月28日 14:41 收件人: greg.wai...@windriver.com; opnfv-tech-discuss@lists.opnfv.org; 'Yin Tony'; 'juan_qiu' 抄送: 'Edgar StPierre'; 'Hui Wang'; 'Yue Yuan' 主题: [opnfv-tech-discuss] [opnfv-tech-discussion][availability]project meeting on Mar. 29 Hi, Greg. Thank you for the update. I arrange another meeting tomorrow on Mar. 29th to continue the discussion. I suggest we go through the heartbeat section first and see if we can reach an agreement. Meetings for High Availability Project Next Meeting on 13:00-14:00 UTC, Wednesday, Mar. 29th https://global.gotomeeting.com/join/772448949 Toll free NO. USA: +1 (646) 749-3117 Meeting ID: 772-448-949 Agenda HA API doc updates – Greg -----邮件原件----- 发件人: Greg Waines (OPNFV Code Review) [mailto:ger...@opnfv.org] 发送时间: 2017年3月28日 0:36 抄送: Ulrich Kleber; Hui Wang; Stefan Arntzen; Qiao Fu; Ian Jolliffe; Edgar StPierre; Yue Yuan 主题: Change in availability[master]: Updating Commit based on third round of review during OPNFV ... Greg Waines has posted comments on this change. ( https://gerrit.opnfv.org/gerrit/26663 ) Change subject: Updating Commit based on third round of review during OPNFV HA meetings, as well as submitted comments on the review. ...................................................................... Patch Set 4: (11 comments) Updated based on recent comments. And added HTML and PDF versions of document for easier reading. https://gerrit.opnfv.org/gerrit/#/c/26663/4/Support_For_HA_Guest_APIs/OPNFV_HA_Guest_APIs-Overview_HLD.rst File Support_For_HA_Guest_APIs/OPNFV_HA_Guest_APIs-Overview_HLD.rst: PS4, Line 15: bstract: This document provides an overview of a set of new : optional capabilities where the OpenStack Cloud messages : into the Guest VMs in order to provide improved Availability : of the hosted VMs. These new capabilities include: enabling : the detection of and recovery from internal VM faults, enabling : Guest VMs to gracefully handle and provide loss-of-service : warnings to cloud adminstrative operations on the VM and : providing a simple out-of-band messaging service to prevent : scenarios such as split brain. > Hi, Greg. You may find more info in the following link. Ugh ... couldn't figure out how to do it from these instructions. I generated an HTML version and PDF version and included it in COMMIT along with the .rst file. PS4, Line 42: VM Heartbeating and Health Checking : - VM Event Notification and Feedback : - VM Peer State Notification and Messaging > Good to hear. I think we should not merge this patch without this being doc I added more explicit indication in the INTRODUCTION that VNFM interactions were discussed in the specific sections. AND in the VM Event Notification and Feedback section, i added a note at the beginning discussing the open item that this currently solicits feedback from VM and notifies VM of upcoming command 'independent' of VNFM. i.e. even for commands issued by the VNFM, this service provides an optional check on the state of the VM and a Notification to the VM for graceful handling of the command. An alternative approach would be to go thru the VNFM to both check the state of the VM and notify the VM of the event. More discussion is required here with the Management and Orchestration OPNFV Team. PS4, Line 51: lifecycle of the VM > I think the host-to-guest message cannot be earlier than the VNFM having st I changed the wording to say "... is available very early after spawning the VM." There is not intent for host-to-guest VM messaging to be used for high-level VM lifecycle management. The intent of the sentence is to say that the messaging mechanism is quite simple and therefore can be available very early after booting the VM. i.e. there are very few dependencies on the messaging mechanism. PS4, Line 53: interaction with : the Guest VM > I think the relation of host-to-guest messaging to VNFM must be covered in I added a more explicit statement in this introduction to indicate that the interaction of these services with the VNFM are further explained in the following sections. PS4, Line 109: This would then enable VNF Managers listening to : OPNFV's DOCTOR External Alarm Reporting through Telemetry's AODH, to initiate : any required fault recovery actions > Happy to hear this same heartbeating will be reported via doctor. I didn't I suspect being able to see the diagrams will help with this as well. PS4, Line 121: A daemon within the Guest VM will register with the OpenStack Guest : Heartbeat Service on the compute node to initiate the heartbeating. > I think your first paragraph clarifies the main question. I added this clarification PS4, Line 128: final fault recovery actions are the responsiblilty/authority of the VNF Managers > Thanks, now I understand this part. Maybe mention this relation to vitrage I updated this section. PS4, Line 155: Host Deliverables > Please clarify whether "host deliverable" means that you write OpenStack bl Updated. PS4, Line 169: Guest Deliverables > OK. If this was a separate project proposal, this would be part of the deli Updated PS4, Line 218: VM Event Notifications > I think with your answers above, things get clearer. I suggest to add that Updated PS4, Line 323: Server Group > Please clarify what is a server group. Please use NFV terminology. Updated with description of Server Group and Peer VM -- To view, visit https://gerrit.opnfv.org/gerrit/26663 To unsubscribe, visit https://gerrit.opnfv.org/gerrit/settings Gerrit-MessageType: comment Gerrit-Change-Id: I1e44efe6052dfa84cdffd9bbebe8be86e4992121 Gerrit-PatchSet: 4 Gerrit-Project: availability Gerrit-Branch: master Gerrit-Owner: Greg Waines <greg.wai...@windriver.com> Gerrit-Reviewer: Edgar StPierre <edgar.stpie...@dell.com> Gerrit-Reviewer: Greg Waines <greg.wai...@windriver.com> Gerrit-Reviewer: Hui Wang <wanghu...@huawei.com> Gerrit-Reviewer: Ian Jolliffe <ian.jolli...@windriver.com> Gerrit-Reviewer: Qiao Fu <fuq...@chinamobile.com> Gerrit-Reviewer: Stefan Arntzen <stefan.arnt...@huawei.com> Gerrit-Reviewer: Ulrich Kleber <ulrich.kle...@huawei.com> Gerrit-Reviewer: Yue Yuan <yuan....@zte.com.cn> Gerrit-HasComments: Yes _______________________________________________ opnfv-tech-discuss mailing list 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
