[openstack-dev] [gluon] why gluon network and subnet info not updated to backends plugin like gluon port

mohammad shahid shahidcse2012 at gmail.com
Mon Apr 3 07:05:47 UTC 2017


Hi,

I have couple of doubts regarding gluon core plugin code, which are listed
below

1) https://github.com/openstack/gluon/blob/master/gluon/plugin/core.py

def *create_subnet*(self, context, subnet): #Line 176-191
        """
        Comment
        """
        result = super(GluonPlugin, self).create_subnet(context, subnet)
        LOG.debug(result)
        return result

def *create_network*(self, context, network): #Line 350-365
        """Comment
        """
        result = super(GluonPlugin, self).create_network(context, network)
        LOG.debug(result)
        return result
def *create_port*(self, context, port):  #Line 466-481
        """
        Comment
        """
        *self.update_gluon_objects(context)*
        result = super(GluonPlugin, self).create_port(context, port)
        LOG.debug(result)
        return result
*def update_gluon_port(self, backend, id, port): *#Line 135-160
        result = dict()
        try:
            driver = self.backend_manager.get_backend_driver(
                backend, self.gluon_network, self.gluon_subnet)
            port_data = port["port"]
            host_id = port_data.get('binding:host_id', None)
            LOG.debug("host_id = %s" % host_id)
            if host_id is None:
                LOG.debug("Performing unbind")


why create network and subnet information only added to GluonPlugin(here
Gluon work as core plugin). and it is not updated to any backend like how
gluon create port does ?

2) As gluon network and subnet information not updated to backend. How SDN
controller will realize network and subnet information from openstack
controller node ? I think, after updating ml2 mechanism driver in ml2.ini
file, right ?


Thanks and Regards,
Mohammad Shahid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170403/ee245c7f/attachment.html>


More information about the OpenStack-dev mailing list