Open Stack

Kiall,

You are right, nothing prevents you from supporting both. It may make sense to have the IP allocation logic defined as a pluggable driver in case some people want to customize it.
In fact, my question, indirectly was that today, IP allocation is not directly generating events since IP addresses are not Quantum resources, and was wondering if DNS records should be tied more to the IP allocation than the life cycle of the users of the IP.

JC

From: Kiall Mac Innes <kiall at managedit.ie<mailto:kiall at managedit.ie>>
Reply-To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Fri, 2 Nov 2012 13:54:54 +0000
To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [Quantum][Nova][DNSaaS] Notification based DNS entry creation

Hi JC,

I'm not sure I understand why we need to only support one or the other.

Once the code to receive notifications and CRUD records is in place, supporting both 'compute.instance.create.end' and 'port.create.end' should be as easy as supporting both 'compute.instance.create.end' and 'compute.instance.delete.start'.

Have I missed something that would require a choice between supporting nova or quantum?

Thanks,
Kiall


On Fri, Nov 2, 2012 at 1:11 AM, JC Martin <jcmartin at ebaysf.com<mailto:jcmartin at ebaysf.com>> wrote:

In DNSaaS, we have a goal to create DNS entries automatically based on notifications corresponding to IP allocation events.

The question is which Notifications/events to use:
    - Nova notifications (e.g. Instance.create.end)
    - Quantum notifications (e.g. Port.create.end)
    - None of the above, we need IP allocation specific events or other events.

Opinion ?

JC





_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


_______________________________________________ OpenStack-dev mailing list OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121102/3560bd0f/attachment.html>