Hi yongiman: I wander what’s the difference between your ‘auto HA’ API and ‘evacuate’
------------------------------------------------------------ Lingxian Kong Huawei Technologies Co.,LTD. IT Product Line CloudOS PDU China, Xi'an Mobile: +86-18602962792 Email: konglingx...@huawei.com From: yongi...@gmail.com [mailto:yongi...@gmail.com] Sent: Tuesday, August 13, 2013 9:12 PM To: OpenStack Development Mailing List Cc: OpenStack Development Mailing List Subject: Re: [openstack-dev] 答复: Proposal for approving Auto HA development blueprint. For realizing auto HA function, we need monitoring service like ceilometer. Ceilometer monitors status of compute nodes ( network interface..connection, healthcheck,,etc,,) What I focus on is that this operation goes on automatically. Nova expose auto ha API. When nova received a auto api call. VMs automatically migrate to auto ha host.( which is extra compute node for only auto ha) All of information of auto ha is stored in auto_ha_hosts table. In this tables, used column of auto ha hosts is changed to true Administrator check broken compute node and fix( or replace ) the compute node. After fixing the compute node, VMs is migrating to operating compute nodes. Now auto ha host is empty again. When the number of runnning VMs in the auto ha host is zero, used column is replaced to false for using again by periodic task. Combination with monitoring service is important. Howerver in this blueprint, I want to realize nova's auto ha operation. My wiki page is still building now, I will fill out as soon as possbile. I am expecting your advices . Thank you very much~! Sent from my iPad On 2013. 8. 13., at 오후 8:01, balaji patnala <patnala...@gmail.com<mailto:patnala...@gmail.com>> wrote: Potential candidate as new service like Ceilometer, Heat etc for OpenStack and provide High Availability of VMs. Good topic to discuss at Summit for implementation post Havana Release. On Tue, Aug 13, 2013 at 12:03 PM, Alex Glikson <glik...@il.ibm.com<mailto:glik...@il.ibm.com>> wrote: Agree. Some enhancements to Nova might be still required (e.g., to handle resource reservations, so that there is enough capacity), but the end-to-end framework probably should be outside of existing services, probably talking to Nova, Ceilometer and potentially other components (maybe Cinder, Neutron, Ironic), and 'orchestrating' failure detection, fencing and recovery. Probably worth a discussion at the upcoming summit. Regards, Alex From: Konglingxian <konglingx...@huawei.com<mailto:konglingx...@huawei.com>> To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, Date: 13/08/2013 07:07 AM Subject: [openstack-dev] 答复: Proposal for approving Auto HA development blueprint. ________________________________ Hi yongiman: Your idea is good, but I think the auto HA operation is not OpenStack’s business. IMO, Ceilometer offers ‘monitoring’, Nova offers ‘evacuation’, and you can combine them to realize HA operation. So, I’m afraid I can’t understand the specific implementation details very well. Any different opinions? 发件人: yongi...@gmail.com<mailto:yongi...@gmail.com> [mailto:yongi...@gmail.com] 发送时间: 2013年8月12日 20:52 收件人: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org> 主题: Re: [openstack-dev] Proposal for approving Auto HA development blueprint. Hi, Now, I am developing auto ha operation for vm high availability. This function is all progress automatically. It needs other service like ceilometer. ceilometer monitors compute nodes. When ceilometer detects broken compute node, it send a api call to Nova, nova exposes for auto ha API. When received auto ha call, nova progress auto ha operation. All auto ha enabled VM where are running on broken host are all migrated to auto ha Host which is extra compute node for using only Auto-HA function. Below is my blueprint and wiki page. Wiki page is not yet completed. Now I am adding lots of information for this function. Thanks https://blueprints.launchpad.net/nova/+spec/vm-auto-ha-when-host-broken https://wiki.openstack.org/wiki/Autoha_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto:OpenStack-dev@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
