Of course, It should be optional, not complusory. And It doesn't mean check the security group rule test. I have one example, https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/issues/14#issuecomment-10277135 Not only this, there are so many unusual case that vm creation success but cannot connect.
If network connectivity check code is added, It'll be very helpful for debug these case. 2013/8/12 Jeff Peeler <jpee...@redhat.com> > On 08/11/2013 04:13 AM, Jae Sang Lee wrote: > >> Hi stackers, >> >> I registerd a blueprint for this proposal, https://blueprints.launchpad.* >> *net/nova/+spec/check-network-**connectivity<https://blueprints.launchpad.net/nova/+spec/check-network-connectivity> >> >> If you have permission to approve who read this mail, please review and >> approve my blueprint. >> >> Thanks. >> > > I would think compulsory instance probing would not be welcomed. However, > I do wonder if new functionality (for Neutron) along the lines of > security-group-rule-test <rule_id> <instance_id> would be helpful. Not sure > how UDP checking would work though. > > > ______________________________**_________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.**org <OpenStack-dev@lists.openstack.org> > http://lists.openstack.org/**cgi-bin/mailman/listinfo/**openstack-dev<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
