ddl007

OpenStack源码分析之cinder-api服务启动

cat /usr/bin/cinder-api

#!/usr/bin/python
# EASY-INSTALL-SCRIPT: 'cinder==2013.1.g3','cinder-api'
__requires__ = 'cinder==2013.1.g3'
import pkg_resources
pkg_resources.run_script('cinder==2013.1.g3', 'cinder-api')

run_script第一参数指向了site-packages/cinder-2013.1.g3-py2.6.egg，第二个参数为要运行的脚本名cinder-api，查看该目录下的EGG-INFO/scripts目录，找到cinder-api

cat cinder-api

import eventlet
eventlet.monkey_patch()

import os
import sys

possible_topdir = os.path.normpath(os.path.join(os.path.abspath(
        sys.argv[0]), os.pardir, os.pardir))
if os.path.exists(os.path.join(possible_topdir, "cinder", "__init__.py")):
    sys.path.insert(0, possible_topdir)

from cinder import flags
from cinder.openstack.common import log as logging
from cinder import service
from cinder import utils

if __name__ == '__main__':
    flags.parse_args(sys.argv)
    logging.setup("cinder")
    utils.monkey_patch()
    server = service.WSGIService('osapi_volume')
    service.serve(server)
    service.wait()

启动了一个WSGIService服务，下面具体分析启动过程。

cinder/service.py

class WSGIService(object):

"""Provides ability to launch API from a 'paste' configuration."""

def __init__(self, name, loader=None):

"""Initialize, but do not start the WSGI server.

:param name: The name of the WSGI server given to the loader.

:param loader: Loads the WSGI application using the given name.

:returns: None

"""

self.name = name

self.manager = self._get_manager() //初始化服务管理对象

self.loader = loader or wsgi.Loader() //指定apploader

self.app = self.loader.load_app(name) //加载app，这个过程相对复杂，涉及到paste模块-配置文件解析、模块加载

self.host = getattr(FLAGS, '%s_listen' % name, "0.0.0.0") //从flages.py或配置文件中获取osapi_volume_listen配置参数

self.port = getattr(FLAGS, '%s_listen_port' % name, 0)

self.server = wsgi.Server(name,

self.app,

host=self.host,

port=self.port) //初始化一个wsgi的Server

def _get_manager(self):

fl = '%s_manager' % self.name //在flages.py中无osapi_volume_manager配置项，因此返回None

if fl not in FLAGS:

return None

manager_class_name = FLAGS.get(fl, None)

if not manager_class_name:

return None

manager_class = importutils.import_class(manager_class_name)

return manager_class()

def start(self):

if self.manager:

self.manager.init_host()

self.server.start()

self.port = self.server.port

def serve(*servers):

global _launcher

if not _launcher:

_launcher = Launcher()

for server in servers:

_launcher.launch_server(server)

self.loader = loader or wsgi.Loader()

self.app = self.loader.load_app(name)

既加载osapi_volume程序

cinder/wsgi.py

class Loader(object):
    def __init__(self, config_path=None):
         config_path = config_path or FLAGS.api_paste_config   //此处指向 /etc/cinder/api-paste.ini
        self.config_path = utils.find_config(config_path)

     def load_app(self, name):
        try:
            return deploy.loadapp("config:%s" % self.config_path, name=name)
        except LookupError as err:
            LOG.error(err)
            raise exception.PasteAppNotFound(name=name, path=self.config_path)

deploy.loadapp("config:%s" % self.config_path, name=name)

deploy源自PasteDeploy-1.5.0-py2.6.egg/paste/deploy，加载了loadwsgi.py

PasteDeploy-xxx/pasete/deploy/loadwsgi.py

class _App(_ObjectType):

    name = 'application'
    egg_protocols = ['paste.app_factory', 'paste.composite_factory',
                     'paste.composit_factory']
    config_prefixes = [['app', 'application'], ['composite', 'composit'],
                       'pipeline', 'filter-app']

    def invoke(self, context):
        if context.protocol in ('paste.composit_factory',
                                'paste.composite_factory'):
            return fix_call(context.object, context.loader, context.global_conf,**context.local_conf)
        elif context.protocol == 'paste.app_factory':
            return fix_call(context.object, context.global_conf, **context.local_conf)
        else:
            assert 0, "Protocol %r unknown" % context.protocol

APP = _App()

def loadapp(uri, name=None, **kw):
return loadobj( APP, uri, name=name, **kw)

def loadobj(object_type, uri, name=None, relative_to=None,global_conf=None):
    context = loadcontext(object_type, uri, name=name, relative_to=relative_to, global_conf=global_conf)
    return context.create()

def loadcontext(object_type, uri, name=None, relative_to=None, global_conf=None):
    if '#' in uri:
        if name is None:    //此处第一次调用时name=osapi_volume , uri=config:/etc/cinder/api-paste.ini
            uri, name = uri.split('#', 1)
        else:
            # @@: Ignore fragment or error?
            uri = uri.split('#', 1)[0]
    if name is None:
        name = 'main'
    if ':' not in uri:
        raise LookupError("URI has no scheme: %r" % uri)
    scheme, path = uri.split(':', 1) //此处第一次得到的scheme 是config，path是/etc/cinder/api-paste.ini 因此reuturn 返回的是 _loacer['config'] ，具体指向看后面的部分
    scheme = scheme.lower()
    if scheme not in _loaders:
        raise LookupError(
            "URI scheme not known: %r (from %s)"
            % (scheme, ', '.join(_loaders.keys())))
    return _loaders[scheme](object_type, uri, path, name=name, relative_to=relative_to,global_conf=global_conf)

其中

def _loadegg(object_type, uri, spec, name, relative_to, global_conf):
loader = EggLoader(spec)
return loader.get_context(object_type, name, global_conf)

def _loadfunc(object_type, uri, spec, name, relative_to, global_conf):
    loader = FuncLoader(spec)
    return loader. get_context(object_type, name, global_conf) //返回了一个LoaderContext,包含了一个ConfigLoader(_Loader)对象

_loaders['config'] = _loadconfig

_loaders['egg'] = _loadegg

_loaders['call'] = _loadfunc

class FuncLoader(_Loader): //继承自_Loader类

def __init__(self, spec):

self.spec = spec

def get_context(...):

obj = lookup_object(self.spec) //该方法来自paste/deploy/util.py

return LoaderContext(obj,object_type,None, global_conf or {},{},self,)

class LoaderContext(object):

def create(self):

return self. object_type. invoke(self) //此处的object_type为APP，所以调用的是class _APP的invoke方法，从上面的代码可以看到，该方法返回的是一个 fix_call的调用结果，下面具体分析

fix_call方法来自于paste/deploy/util.py

def fix_call(callable, *args, **kw):
try:
val = callable(*args, **kw)

//此处的callable指向api的一些功能入口api/__init__.py:root_app_factory api/middleware/auth.py:pipeline_factory 可以看出此处进行了接口的实际调用，其中root_app_factory实际出发了Paste/paste/urlmap.py:urlmap_factory的调用，后者调用了loader.get_app() ，laoder对象是一个PasteDeploy/paste/deploy/loadwsgi.py中的ConfigLoader(_Loader)类对象。urlmap_factory中的local_conf.items() 为

/: apiversions
/v1: openstack_volume_api_v1
/v2: openstack_volume_api_v2

参看/etc/cinder/api-paste.ini

因此loader.get_app()的解析是逐个加载下面几个字段，直到所有字段加载完成，后面的其它模块加载流程基本相同

[composite:openstack_volume_api_v2]

[composite:openstack_volume_api_v1]

[pipeline:apiversions]

参看/etc/cinder/api-paste.ini

    except TypeError:
        exc_info = fix_type_error(None, callable, args, kw)
        reraise(*exc_info)
    return val

def lookup_object(spec):    //此处的spec值类似于 cinder.api:root_app_factory、cinder.api.middleware.auth:pipeline_factory
    parts, target = spec.split(':') if ':' in spec else (spec, None)
    module = __import__(parts)
    for part in parts.split('.')[1:] + ([target] if target else []):
        module = getattr(module, part)
     return module

Paste/paste/urlmap.py

def urlmap_factory(loader, global_conf, **local_conf):
    if 'not_found_app' in local_conf:
        not_found_app = local_conf.pop('not_found_app')
    else:
        not_found_app = global_conf.get('not_found_app')
    if not_found_app:
        not_found_app = loader.get_app(not_found_app, global_conf=global_conf)
    urlmap = URLMap(not_found_app=not_found_app)
    for path, app_name in local_conf.items():
        path = parse_path_expression(path)
        app = loader.get_app(app_name, global_conf=global_conf)
        urlmap[path] = app
    return urlmap

整个load_app加载了多个模块，最终返回的就是一个urlmap的列表，看下面的调用流程

****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name openstack_volume_api_v1
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name call:cinder.api.middleware.auth:pipeline_factory
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name:call:cinder.api.middleware.auth:pipeline_factory have a sechema
****** PasteDeploy:paste:deploy:loadwsgi.py:loadcontext: uri:call:cinder.api.middleware.auth:pipeline_factory name:main scheme:call:
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <module 'cinder.api' from '/usr/lib/python2.6/site-packages/cinder-2013.1.g3-py2.6.egg/cinder/api/__init__.pyc'>
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <module 'cinder.api.middleware' from '/usr/lib/python2.6/site-packages/cinder-2013.1.g3-py2.6.egg/cinder/api/middleware/__init__.pyc'>
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <module 'cinder.api.middleware.auth' from '/usr/lib/python2.6/site-packages/cinder-2013.1.g3-py2.6.egg/cinder/api/middleware/auth.pyc'>
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <function pipeline_factory at 0x2538e60>
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <function pipeline_factory at 0x2538e60>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name faultwrap
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.middleware.fault.FaultWrapper'>>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name sizelimit
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.middleware.sizelimit.RequestBodySizeLimiter'>>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name authtoken
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <function filter_factory at 0x26d2668>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name keystonecontext
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.middleware.auth.CinderKeystoneContext'>>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name apiv1
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.v1.router.APIRouter'>>
2013-02-03 02:59:41.295 4294 AUDIT cinder.api.extensions [-] Initializing extension manager.
2013-02-03 02:59:41.296 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-vol-image-meta
2013-02-03 02:59:41.297 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-hosts
2013-02-03 02:59:41.297 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-types-manage
2013-02-03 02:59:41.297 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-volume-actions
2013-02-03 02:59:41.298 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-vol-host-attr
2013-02-03 02:59:41.298 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-admin-actions
2013-02-03 02:59:41.299 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-extended-snapshot-attributes
2013-02-03 02:59:41.299 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-services
2013-02-03 02:59:41.300 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-image-create
2013-02-03 02:59:41.300 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-vol-tenant-attr
2013-02-03 02:59:41.300 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-quota-class-sets
2013-02-03 02:59:41.301 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-types-extra-specs
2013-02-03 02:59:41.301 4294 AUDIT cinder.api.extensions [-] Loaded extension: os-quota-sets
2013-02-03 02:59:41.301 4294 AUDIT cinder.api.extensions [-] Loaded extension: backups
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name apiversions
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name osvolumeversionapp
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name faultwrap
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.versions.Versions'>>
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.middleware.fault.FaultWrapper'>>
****** Paste:paste:urlmap.py:urlmap_factory: app: <cinder.api.middleware.fault.FaultWrapper object at 0x3480fd0>

其中，在加载cinder.api.v1.router.APIRouter模块时，会有一个加载extension manager的过程，这个部分加载的模块是api服务的关键，完成实际服务的app来自于这些扩展，manager来进行管理，在有web请求时进过路由到对应的app

下面分析cinder.api.v2.router.APIRouter 模块的加载过程：

cinder/api/v2/router.py

class APIRouter(cinder.api.openstack.APIRouter):

ExtensionManager = extensions.ExtensionManager

def _setup_routes(self, mapper, ext_mgr):

self.resources['versions'] = versions.create_resource()

mapper.connect("versions", "/", controller=self.resources['versions'], action='show')

api/openstack/__init__.py

class APIRouter(base_wsgi.Router):

def __init__(self, ext_mgr=None):

        if ext_mgr is None:
            if self.ExtensionManager:
                ext_mgr = self.ExtensionManager() 此处触发一个 standard api extension 程序的加载过程
            else:
                raise Exception(_("Must specify an ExtensionManager class"))

        mapper = ProjectMapper()
        self.resources = {}
        self._setup_routes(mapper, ext_mgr)
        self._setup_ext_routes(mapper, ext_mgr)
        self._setup_extensions(ext_mgr)
        super(APIRouter, self).__init__(mapper)

def _setup_ext_routes(self, mapper, ext_mgr):
        for resource in ext_mgr.get_resources():
            LOG.debug(_('Extended resource: %s'),
                      resource.collection)

            wsgi_resource = wsgi.Resource(resource.controller)
            self.resources[resource.collection] = wsgi_resource
            kargs = dict(
                controller=wsgi_resource,
                collection=resource.collection_actions,
                member=resource.member_actions)

            if resource.parent:
                kargs['parent_resource'] = resource.parent

            mapper.resource(resource.collection, resource.collection, **kargs)

            if resource.custom_routes_fn:
                resource.custom_routes_fn(mapper, wsgi_resource)

    def _setup_extensions(self, ext_mgr):
        for extension in ext_mgr.get_controller_extensions():
            ext_name = extension.extension.name
            collection = extension.collection
            controller = extension.controller

if collection not in self.resources:
                LOG.warning(_('Extension %(ext_name)s: Cannot extend '
                              'resource %(collection)s: No such resource') %
                            locals())
                continue

            LOG.debug(_('Extension %(ext_name)s extending resource: '
                        '%(collection)s') % locals())

            resource = self.resources[collection]
            resource.register_actions(controller)
            resource.register_extensions(controller)

    def _setup_routes(self, mapper, ext_mgr):
        raise NotImplementedError

cinder/api/extensions.py

class ExtensionManager(object):

def __init__(self):
        LOG.audit(_('Initializing extension manager.'))

        self.cls_list = FLAGS.osapi_volume_extension 在flages.py配置文件中，osapi_volume_extension的配置值为cinder.api.contrib.standard_extensions
        self.extensions = {}
        self. _load_extensions() 开始加载standard api extension类

   def _load_extensions(self):
        """Load extensions specified on the command line."""
        extensions = list(self.cls_list)
        for ext_factory in extensions:
            try:
                self. load_extension(ext_factory) 此处ext_factory 为cinder.api.contrib.standard_extensions

   def load_extension(self, ext_factory):
        factory = importutils.import_class(ext_factory) 此处ext_factory 为cinder.api.contrib. standard_extensions，此处调用了cinder/api/contrib/__init__.py: standard_extensions(ext_mgr):
        factory(self)

cinder/api/contrib/__init__.py

def standard_extensions(ext_mgr):

extensions. load_standard_extensions(ext_mgr, LOG, __path__, __package__) 调用的是extensions.py中的load_standard_extensions 方法.

cinder/api/extensions.py

def load_standard_extensions(ext_mgr, logger, path, package, ext_list=None):
    """Registers all standard API extensions."""

    # Walk through all the modules in our directory...
    our_dir = path[0]
    for dirpath, dirnames, filenames in os.walk(our_dir):
        # Compute the relative package name from the dirpath
        relpath = os.path.relpath(dirpath, our_dir)
        if relpath == '.':
            relpkg = ''
        else:
            relpkg = '.%s' % '.'.join(relpath.split(os.sep))

        # Now, consider each file in turn, only considering .py files

//下面的这个循环根据文件名遍历了standard API extension的.py文件
        for fname in filenames:
            root, ext = os.path.splitext(fname)

            # Skip __init__ and anything that's not .py
            if ext != '.py' or root == '__init__':
                continue

            # Try loading it
            classname = "%s%s" % (root[0].upper(), root[1:]) //root第一个字符变为大写后作为类名
            classpath = ("%s%s.%s.%s" % (package, relpkg, root, classname))

//根据文件名及路径信息构造类的路径信息，类似于cinder.api.contrib.volume_image_metadata.Volume_image_metadata

            if ext_list is not None and classname not in ext_list:
                logger.debug("Skipping extension: %s" % classpath)
                continue

            try:
                ext_mgr. load_extension(classpath) //根据给定的路径加载类
            except Exception as exc:
                logger.warn(_('Failed to load extension %(classpath)s: '
                              '%(exc)s') % locals())

        # Now, let's consider any subdirectories we may have...
        subdirs = []
        for dname in dirnames: //子目录同样的加载过程
            # Skip it if it does not have __init__.py
            if not os.path.exists(os.path.join(dirpath, dname,
                                               '__init__.py')):
                continue

            # If it has extension(), delegate...
            ext_name = ("%s%s.%s.extension" %
                        (package, relpkg, dname))
            try:
                ext = importutils.import_class(ext_name)
            except common_exception.NotFound:
                # extension() doesn't exist on it, so we'll explore
                # the directory for ourselves
                subdirs.append(dname)
            else:
                try:
                    ext(ext_mgr)

except Exception as exc:
                    logger.warn(_('Failed to load extension %(ext_name)s: '
                                  '%(exc)s') % locals())

        # Update the list of directories we'll explore...
        dirnames[:] = subdirs

在基本的standard api extension加载完成后，APIRouter的初始化并没有结束，还有如下的一个过程

mapper = ProjectMapper()
        self.resources = {}
         self._setup_routes(mapper, ext_mgr)
        self._setup_ext_routes(mapper, ext_mgr)
        self._setup_extensions(ext_mgr)
        super(APIRouter, self).__init__(mapper)

cinder/api/v2/router.py

class APIRouter(cinder.api.openstack.APIRouter):

   def _setup_routes(self, mapper, ext_mgr):
        self.resources['versions'] = versions.create_resource()
        mapper.connect("versions", "/",
                       controller=self.resources['versions'],
                       action='show')

        mapper.redirect("", "/")

        self.resources['volumes'] = volumes.create_resource(ext_mgr)
        mapper.resource("volume", "volumes",
                        controller=self.resources['volumes'],
                        collection={'detail': 'GET'},
                        member={'action': 'POST'})

以volumes.create_resource(ext_mgr) 为例创建一个resource

cinder/api/v2/volume.py

def create_resource(ext_mgr):
return wsgi.Resource( VolumeController(ext_mgr))

class VolumeController(wsgi.Controller):
    """The Volumes API controller for the OpenStack API."""
    _view_builder_class = volume_views.ViewBuilder
    def __init__(self, ext_mgr):
         self.volume_api = volume.API() volume驱动API接口
        self.ext_mgr = ext_mgr
        super(VolumeController, self).__init__()
    @wsgi.serializers(xml=VolumeTemplate)
    def show(self, req, id):
        """Return data about the given volume."""
    def delete(self, req, id):
        """Delete a volume."""

def index(self, req):
        """Returns a summary list of volumes."""
    @wsgi.serializers(xml=VolumesTemplate)
    def detail(self, req):
        """Returns a detailed list of volumes."""

可以看出该类包含了对卷的操作方法、show、delete等，最终都是调用的self.volume_api来进行操作的。

cinder/volume.py

API = cinder.openstack.common.importutils.import_class(cinder.flags.FLAGS.volume_api_class)

在flages.py中volume_api_class默认值为 cinder.volume.api.API

cinder/volume/api.py

from cinder.scheduler import rpcapi as scheduler_rpcapi
from cinder.volume import rpcapi as volume_rpcapi

class API(base.Base):
    """API for interacting with the volume manager."""

    def __init__(self, db_driver=None, image_service=None):
        self.image_service = (image_service or glance.get_default_image_service())
        self.scheduler_rpcapi = scheduler_rpcapi. SchedulerAPI()
        self.volume_rpcapi = volume_rpcapi. VolumeAPI()
        super(API, self).__init__(db_driver)

def create(self, context, size, name, description, snapshot=None,
image_id=None, volume_type=None, metadata=None,
availability_zone=None, source_volume=None):
.....................................................

        self._check_metadata_properties(context, metadata)
        options = {'size': size,
                   'user_id': context.user_id,
                   'project_id': context.project_id,
                   'snapshot_id': snapshot_id,
                   'availability_zone': availability_zone,
                   'status': "creating",
                   'attach_status': "detached",
                   'display_name': name,
                   'display_description': description,
                   'volume_type_id': volume_type_id,
                   'metadata': metadata,

'source_volid': source_volid}
        try:
            volume = self.db.volume_create(context, options)
            QUOTAS.commit(context, reservations)
        request_spec = {'volume_properties': options,
                        'volume_type': volume_type,
                        'volume_id': volume['id'],
                        'snapshot_id': volume['snapshot_id'],
                        'image_id': image_id,
                        'source_volid': volume['source_volid']}

        filter_properties = {}
        self. _cast_create_volume(context, request_spec, filter_properties)
        return volume

    def _cast_create_volume(self, context, request_spec, filter_properties):

             source_volume_ref = self.db.volume_get(context,source_volid)
            now = timeutils.utcnow()
            values = {'host': source_volume_ref['host'], 'scheduled_at': now}
            volume_ref = self.db.volume_update(context, volume_id, values)

            # bypass scheduler and send request directly to volume
            self. volume_rpcapi.create_volume(context,............

cinder/volume/rpcapi.py

class VolumeAPI( cinder.openstack.common.rpc.proxy.RpcProxy):

BASE_RPC_API_VERSION = '1.0'

    def __init__(self, topic=None):
        super(VolumeAPI, self).__init__(topic=topic or FLAGS.volume_topic,default_version=self.BASE_RPC_API_VERSION)

def create_volume(self, ctxt, volume, host, request_spec, filter_properties,allow_reschedule=True, snapshot_id=None, image_id=None, source_volid=None):
self. cast(ctxt,

self.make_msg('create_volume',volume_id=volume['id'], request_spec=request_spec,filter_properties=filter_properties,
                                allow_reschedule=allow_reschedule,snapshot_id=snapshot_id,image_id=image_id,source_volid=source_volid),
                  topic=rpc.queue_get_for(ctxt,self.topic,host),
                  version='1.4')

使用cast方法发送了一个methord:create_volume的消息到AMQP服务器，另外本类还提供了其它针对volume操作的方法。

再回过来看 wsgi.Resource

cinder/api/openstack/wsgi.py

class Resource(wsgi.Application):

def __init__(self, controller, action_peek=None, **deserializers):
self.controller = controller 从上面的调用wsgi.Resource( VolumeController(ext_mgr))可以看出controller是一个 VolumeController控制对象
default_deserializers = dict(xml=XMLDeserializer,

.......

经过上面的这段代码流程的分析，可以看出，self._setup_routes(mapper, ext_mgr) 是对resource和controller进行初始化操作

下面继续

api/openstack/__init__.py

class APIRouter(base_wsgi.Router):__init__初始化中的 self._setup_ext_routes(mapper, ext_mgr) 过程分析

//此方法主要是生成controller字典

def _setup_ext_routes(self, mapper, ext_mgr):
        for resource in ext_mgr.get_resources():
            LOG.debug(_('Extended resource: %s'),
                      resource.collection)

            wsgi_resource = wsgi.Resource(resource.controller)
            self.resources[resource.collection] = wsgi_resource
            kargs = dict(
                controller=wsgi_resource,
                collection=resource.collection_actions,
                member=resource.member_actions)

            if resource.parent:
                kargs['parent_resource'] = resource.parent

            mapper.resource(resource.collection, resource.collection, **kargs)

            if resource.custom_routes_fn:

resource.custom_routes_fn(mapper, wsgi_resource)

//本方法主要是注册controller

def _setup_extensions(self, ext_mgr):
        for extension in ext_mgr.get_controller_extensions():
            ext_name = extension.extension.name
            collection = extension.collection
            controller = extension.controller

            if collection not in self.resources:
                LOG.warning(_('Extension %(ext_name)s: Cannot extend '
                              'resource %(collection)s: No such resource') %
                            locals())
                continue

            LOG.debug(_('Extension %(ext_name)s extending resource: '
                        '%(collection)s') % locals())

            resource = self.resources[collection]
            resource.register_actions(controller)
            resource.register_extensions(controller)

最后一步：

cinder/wsgi.py

class Router(object):

def __init__(self, mapper):

        """Create a router for the given routes.Mapper.
        self.map = mapper
        self._router = routes.middleware.RoutesMiddleware(self._dispatch,  self.map)

   @webob.dec.wsgify(RequestClass=Request)   此处使用了“装饰者”模式，将__call__方法的返回值作为参数传给webob.dec.wsgify的同名方法__call__
    def __call__(self, req):
        """Route the incoming request to a controller based on self.map.

        If no match, return a 404.

        """

return self._router

@staticmethod
    @webob.dec.wsgify(RequestClass=Request)
    def _dispatch(req):
        """Dispatch the request to the appropriate controller.

        Called by self._router after matching the incoming request to a route
        and putting the information into req.environ. Either returns 404
        or the routed WSGI app's response.

        """
        match = req.environ['wsgiorg.routing_args'][1]
        if not match:
            return webob.exc.HTTPNotFound()
        app = match['controller']

return app

当有web请求时，请求的入口就是__call__方法

最后在看WSGIService启动的最后一个步骤serve函数

cinder/service.py

def serve(*servers):
    global _launcher
    if not _launcher:
        _launcher = Launcher()
    for server in servers:
        _launcher. launch_server(server)

class Launcher(object):

@staticmethod
    def run_server(server):
        """Start and wait for a server to finish.

        :param service: Server to run and wait for.
        :returns: None

        """
         server.start()
        server.wait()

     def launch_server(self, server):
        """Load and start the given server.

        :param server: The server you would like to start.
        :returns: None

        """
        gt = eventlet.spawn(self.run_server, server)
        self._services.append(gt)

可以看出最终是调用了wsgi. Server的start方法

cinder/wsgi.py

def _start(self):
        eventlet.wsgi.server(self._socket,
                             self.app, 这里的app就是经过多层包装的 APIRouter
                             protocol=self._protocol,
                             custom_pool=self._pool,
                             log=self._wsgi_logger)

    def start(self, backlog=128):
        """Start serving a WSGI application.
        """
        if backlog < 1:
            raise exception.InvalidInput(
                reason='The backlog must be more than 1')
        self._socket = self._get_socket(self._host,

self._port,
                                        backlog=backlog)
        self._server = eventlet.spawn(self._start)
        (self._host, self._port) = self._socket.getsockname()[0:2]
        LOG.info(_("Started %(name)s on %(_host)s:%(_port)s") % self.__dict__)

补充一些程序的调用流程输出，也许可以帮助我们理解：

****** PasteDeploy:paste:deploy:loadwsgi.py:loadcontext: uri:config:/etc/cinder/api-paste.ini name:osapi_volume scheme:config:
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name osapi_volume
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: composite:osapi_volume
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_use ******
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name call:cinder.api:root_app_factory
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name:call:cinder.api:root_app_factory have a sechema
****** PasteDeploy:paste:deploy:loadwsgi.py:loadcontext: uri:call:cinder.api:root_app_factory name:main scheme:call:
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <module 'cinder.api' from '/usr/lib/python2.6/site-packages/cinder-2013.1.g3-py2.6.egg/cinder/api/__init__.pyc'>
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <function root_app_factory at 0x20b0e60>
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <function root_app_factory at 0x20b0e60>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name openstack_volume_api_v2
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: composite:openstack_volume_api_v2
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_use ******
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name call:cinder.api.middleware.auth:pipeline_factory
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name:call:cinder.api.middleware.auth:pipeline_factory have a sechema
****** PasteDeploy:paste:deploy:loadwsgi.py:loadcontext: uri:call:cinder.api.middleware.auth:pipeline_factory name:main scheme:call:
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <module 'cinder.api' from '/usr/lib/python2.6/site-packages/cinder-2013.1.g3-py2.6.egg/cinder/api/__init__.pyc'>
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <module 'cinder.api.middleware' from '/usr/lib/python2.6/site-packages/cinder-2013.1.g3-py2.6.egg/cinder/api/middleware/__init__.pyc'>
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <module 'cinder.api.middleware.auth' from '/usr/lib/python2.6/site-packages/cinder-2013.1.g3-py2.6.egg/cinder/api/middleware/auth.py'>
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <function pipeline_factory at 0x20bbed8>
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <function pipeline_factory at 0x20bbed8>
****** api.middleware.auth.pipeline_factory: call get_context method of loader for N times in pipeline: ['faultwrap', 'sizelimit', 'authtoken', 'keystonecontext', 'apiv2']
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name faultwrap
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: filter:faultwrap
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_filter ******
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.middleware.fault.FaultWrapper'>>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name sizelimit
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: filter:sizelimit
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_filter ******
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.middleware.sizelimit.RequestBodySizeLimiter'>>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name authtoken
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: filter:authtoken
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_filter ******
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <function filter_factory at 0x22536e0>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name keystonecontext
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: filter:keystonecontext
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_filter ******
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.middleware.auth.CinderKeystoneContext'>>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name apiv2
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: app:apiv2
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_filter ******
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.v2.router.APIRouter'>>
2013-02-08 05:28:49.000 39038 AUDIT cinder.api.extensions [-] Initializing extension manager.
2013-02-08 05:28:49.002 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-vol-image-meta
2013-02-08 05:28:49.003 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-hosts
2013-02-08 05:28:49.004 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-types-manage
2013-02-08 05:28:49.005 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-volume-actions
2013-02-08 05:28:49.006 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-vol-host-attr
2013-02-08 05:28:49.007 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-admin-actions
2013-02-08 05:28:49.007 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-extended-snapshot-attributes
2013-02-08 05:28:49.008 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-services
2013-02-08 05:28:49.008 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-image-create
2013-02-08 05:28:49.009 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-vol-tenant-attr
2013-02-08 05:28:49.010 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-quota-class-sets
2013-02-08 05:28:49.011 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-types-extra-specs
2013-02-08 05:28:49.122 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-quota-sets
2013-02-08 05:28:49.123 39038 AUDIT cinder.api.extensions [-] Loaded extension: backups
****** api.middleware.auth.pipeline_factory: filter(app) : <cinder.api.middleware.auth.CinderKeystoneContext object at 0x2db0950>
****** api.middleware.auth.pipeline_factory: filter(app) : <keystoneclient.middleware.auth_token.AuthProtocol object at 0x2ed2810>
****** api.middleware.auth.pipeline_factory: filter(app) : <cinder.api.middleware.sizelimit.RequestBodySizeLimiter object at 0x2ed2c50>
****** api.middleware.auth.pipeline_factory: filter(app) : <cinder.api.middleware.fault.FaultWrapper object at 0x2ed2e50>
****** Paste:paste:urlmap.py:urlmap_factory: local_conf, app: {'/v2': 'openstack_volume_api_v2', '/v1': 'openstack_volume_api_v1', '/': 'apiversions'} <cinder.api.middleware.fault.FaultWrapper object at 0x2ed2e50>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name openstack_volume_api_v1
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: composite:openstack_volume_api_v1
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_use ******
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name call:cinder.api.middleware.auth:pipeline_factory
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name:call:cinder.api.middleware.auth:pipeline_factory have a sechema
****** PasteDeploy:paste:deploy:loadwsgi.py:loadcontext: uri:call:cinder.api.middleware.auth:pipeline_factory name:main scheme:call:
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <module 'cinder.api' from '/usr/lib/python2.6/site-packages/cinder-2013.1.g3-py2.6.egg/cinder/api/__init__.pyc'>
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <module 'cinder.api.middleware' from '/usr/lib/python2.6/site-packages/cinder-2013.1.g3-py2.6.egg/cinder/api/middleware/__init__.pyc'>
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <module 'cinder.api.middleware.auth' from '/usr/lib/python2.6/site-packages/cinder-2013.1.g3-py2.6.egg/cinder/api/middleware/auth.py'>
****** PasteDeploy:paste:deploy:util.py:lookup_object: module <function pipeline_factory at 0x20bbed8>
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <function pipeline_factory at 0x20bbed8>
****** api.middleware.auth.pipeline_factory: call get_context method of loader for N times in pipeline: ['faultwrap', 'sizelimit', 'authtoken', 'keystonecontext', 'apiv1']
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name faultwrap
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: filter:faultwrap
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_filter ******
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.middleware.fault.FaultWrapper'>>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name sizelimit
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: filter:sizelimit
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_filter ******
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.middleware.sizelimit.RequestBodySizeLimiter'>>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name authtoken
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: filter:authtoken
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_filter ******
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <function filter_factory at 0x22536e0>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name keystonecontext
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: filter:keystonecontext
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_filter ******
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.middleware.auth.CinderKeystoneContext'>>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name apiv1
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: app:apiv1
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_filter ******
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.v1.router.APIRouter'>>
2013-02-08 05:28:49.145 39038 AUDIT cinder.api.extensions [-] Initializing extension manager.
2013-02-08 05:28:49.146 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-vol-image-meta
2013-02-08 05:28:49.146 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-hosts
2013-02-08 05:28:49.147 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-types-manage
2013-02-08 05:28:49.147 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-volume-actions
2013-02-08 05:28:49.148 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-vol-host-attr
2013-02-08 05:28:49.148 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-admin-actions
2013-02-08 05:28:49.148 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-extended-snapshot-attributes
2013-02-08 05:28:49.149 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-services
2013-02-08 05:28:49.149 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-image-create
2013-02-08 05:28:49.150 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-vol-tenant-attr
2013-02-08 05:28:49.150 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-quota-class-sets
2013-02-08 05:28:49.150 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-types-extra-specs
2013-02-08 05:28:49.151 39038 AUDIT cinder.api.extensions [-] Loaded extension: os-quota-sets
2013-02-08 05:28:49.151 39038 AUDIT cinder.api.extensions [-] Loaded extension: backups
****** api.middleware.auth.pipeline_factory: filter(app) : <cinder.api.middleware.auth.CinderKeystoneContext object at 0x2fd3810>
****** api.middleware.auth.pipeline_factory: filter(app) : <keystoneclient.middleware.auth_token.AuthProtocol object at 0x30016d0>
****** api.middleware.auth.pipeline_factory: filter(app) : <cinder.api.middleware.sizelimit.RequestBodySizeLimiter object at 0x3001950>
****** api.middleware.auth.pipeline_factory: filter(app) : <cinder.api.middleware.fault.FaultWrapper object at 0x3001b10>
****** Paste:paste:urlmap.py:urlmap_factory: local_conf, app: {'/v2': 'openstack_volume_api_v2', '/v1': 'openstack_volume_api_v1', '/': 'apiversions'} <cinder.api.middleware.fault.FaultWrapper object at 0x3001b10>
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name apiversions
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: pipeline:apiversions
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_pipeline ******
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name osvolumeversionapp
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: app:osvolumeversionapp
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_filter ******
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: name faultwrap
****** PasteDeploy:paste:deploy:loadwsgi.py:ConfigLoader:get_context: section: filter:faultwrap
****** PasteDeploy.paste.deploy.loadwsgi.get_context: section_start_with_filter ******
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.versions.Versions'>>
****** PasteDeploy:paste:deploy:util.py:fix_call: callable: <bound method type.factory of <class 'cinder.api.middleware.fault.FaultWrapper'>>
****** Paste:paste:urlmap.py:urlmap_factory: local_conf, app: {'/v2': 'openstack_volume_api_v2', '/v1': 'openstack_volume_api_v1', '/': 'apiversions'} <cinder.api.middleware.fault.FaultWrapper object at 0x30090d0>

你可能感兴趣的:(openstack源码分析,cinder源码分析)

JVM源码分析之堆外内存完全解读 HeapDump性能社区
概述广义的堆外内存说到堆外内存，那大家肯定想到堆内内存，这也是我们大家接触最多的，我们在jvm参数里通常设置-Xmx来指定我们的堆的最大值，不过这还不是我们理解的Java堆，-Xmx的值是新生代和老生代的和的最大值，我们在jvm参数里通常还会加一个参数-XX:MaxPermSize来指定持久代的最大值，那么我们认识的Java堆的最大值其实是-Xmx和-XX:MaxPermSize的总和，在分代算法
Golang Channel PandaSkr golang
Channel解析1.Channel源码分析1.1Channel数据结构typehchanstruct{qcountuint//channel的元素数量dataqsizuint//channel循环队列长度bufunsafe.Pointer//指向循环队列的指针elemsizeuint16//元素大小closeduint32//channel是否关闭0-未关闭elemtype*_type//元素类
Java集合类框架源码分析之 RoleList源码解析【6】 yunzhonghefei Java集合类源码分析 RoleList源码解析
该类继承于ArrayList，针对Role进行了一些扩展。其他方法和ArrayList中基本相同，源码不做针对性分析：看一下类简介：/***代表了一个roles的列表，作为方法setRoles()的参数，去创建一个关联关系，并且尝试在同一个关系中设置多个角色。*ARoleListrepresentsalistofroles(Roleobjects).Itisusedas*parameterwhen
【鸿蒙OH-v5.0源码分析之 Linux Kernel 部分】004 - Kernel 启动引导代码head.S 源码逐行分析 "小夜猫&小懒虫&小财迷"的男人鸿蒙OH-v5.0源码分析之 Uboot+Kernel 部分 harmonyos linux 华为
【鸿蒙OH-v5.0源码分析之LinuxKernel部分】004-Kernel启动引导代码head.S源码逐行分析系列文章汇总：《鸿蒙OH-v5.0源码分析之Uboot+Kernel部分】000-文章链接汇总》本文链接：《【鸿蒙OH-v5.0源码分析之LinuxKernel部分】004-Kernel启动引导代码head.S源码逐行分析》head.S主要工作如下：保存内核启动参数,无效化处理器缓存(
Java高并发编程详解系列-深入理解Thread构造 nihui123 高并发 Java高并发 Java 高并发
上篇分享中主要是对线程的基本概念和基本操作做了一个分享，同时提出了两种常用的创建多线程的方法，当然在后期的分享中也会提及到更多的创建线程的方式，到后期的分享的时候再说。这次主要是深入的理解一下Thread的构造函数，通过构造函数对于Thread有一个更加深入的了解。这里首先提供一个JDK1.6的ThreadAPI截图线程命名规范从源码分析可以看到在Thread类中默认提供了线程的命名方式，这个
【QT教程】QT6硬件图形界面编程 QT硬件编程 QT性能优化QT原理源码QT界面美化 qt qt6.3 qt5 c++QT教程
QT6硬件图形界面编程使用AI技术辅助生成QT界面美化视频课程QT性能优化视频课程QT原理与源码分析视频课程QTQMLC++扩展开发视频课程免费QT视频课程您可以看免费1000+个QT技术视频免费QT视频课程QT统计图和QT数据可视化视频免费看免费QT视频课程QT性能优化视频免费看免费QT视频课程QT界面美化视频免费看1QT6硬件图形界面编程概述1.1QT6硬件图形界面编程简介1.1.1QT6硬件
Jetpack LiveData源码分析 xiangxiongfly915 #Android Jetpack系列 Jetpack LiveData 源码分析
文章目录JetpackLiveData源码分析前提源码分析注册订阅流程LiveData#observe()LifecycleRegistry#addObserver()ObserverWithState#dispatchEvent()LiveData#removeObserver()LiveData$LifecycleBoundObserver类LifecycleBoundObserver#sho
ExoPlayer架构详解与源码分析（17）——TrackSelector 山雨楼 ExoPlayer 架构 android 音视频 ExoPlayer Media3 源码
系列文章目录ExoPlayer架构详解与源码分析（1）——前言ExoPlayer架构详解与源码分析（2）——PlayerExoPlayer架构详解与源码分析（3）——TimelineExoPlayer架构详解与源码分析（4）——整体架构ExoPlayer架构详解与源码分析（5）——MediaSourceExoPlayer架构详解与源码分析（6）——MediaPeriodExoPlayer架构详解与
ExoPlayer架构详解与源码分析（12）——Cache 山雨楼 ExoPlayer 架构 android 音视频 ExoPlayer Media3 源码
系列文章目录ExoPlayer架构详解与源码分析（1）——前言ExoPlayer架构详解与源码分析（2）——PlayerExoPlayer架构详解与源码分析（3）——TimelineExoPlayer架构详解与源码分析（4）——整体架构ExoPlayer架构详解与源码分析（5）——MediaSourceExoPlayer架构详解与源码分析（6）——MediaPeriodExoPlayer架构详解与
ExoPlayer架构详解与源码分析（7）——SampleQueue(4) 2401_83740189 程序员架构
long[]newSourceIds=newlong[newCapacity];long[]newOffsets=newlong[newCapacity];long[]newTimesUs=newlong[newCapacity];int[]newFlags=newint[newCapacity];int[]newSizes=newint[newCapacity];CryptoData[]newC
【HarmonyOS】- 常见算法简单写法数的羊都睡了 HarmonyOS ArkTS 鸿蒙
文章目录知识回顾前言源码分析1.冒泡排序2.二分法查找拓展知识时间、空间复杂度总结知识回顾前言常见算法简单写法源码分析1.冒泡排序functionbubbleSort(arr:number[]):number[]{constn=arr.length;for(leti=0;iarr[j+1]){//交换元素consttemp=arr[j];arr[j]=arr[j+1];arr[j+1]=temp;
[ docker-ce源码分析系列 ] 修改resolv.conf文件被还原的原因 nangonghen docker docker
1概述：1.1环境版本信息如下：a、操作系统：centos7.6，amd64b、服务器docker版本：v18.09.22resolv.conf文件被还原的现象：容器中的/etc/resolv.conf文件，是由宿主机/var/lib/docker/containers/xxxx/resolv.conf文件挂载。在dockerrestart容器之前，手动修改了/var/lib/docker/con
dispatch_once源码分析福伟_Y
GCD里的单例函数dispatch_once是我们经常会用到的，今天我们来稍做深入分析一下。GCD的源码都在libdispatch.dylib库里，这个库在libSystem_initializer被初始化，可理解为在dyld里被加载和初始化的(之前的文章有分析过)。dispatch_once作为单例的使用入口，通过分析得到它是一个宏定义，_dispatch_once函数在libdispatch.
jQuery Easyui 源码分析之combo组件 90后北京程序员前端-easyui easyui之combobox
/***jQueryEasyUI1.3.1*该源码完全由压缩码翻译而来，并非网络上放出的源码，请勿索要。*/(function($){functionsetSize(target,width){varopts=$.data(target,"combo").options;varcombo=$.data(target,"combo").combo;varpanel=$.data(target,"co
html5carousel图片轮播,全面解析Bootstrap中Carousel轮播的使用方法 RemusrickCat
本文实例为大家全面的解析了Bootstrap中Carousel的使用方法，供大家参考，具体内容如下源码文件：Carousel.scssCarousel.js实现原理：隐藏所有要显示的元素，然后指定当前要显示的为block，宽、高自适应源码分析：1、Html结构：主要分为以四个部分1.1、容器：最外层div，需要一个data-ride=”carousel”来指定为轮播放插件，并且提供一个Id，方便圆
Java集合-----List接口及其实现类：ArrayList、LinkedList、Vector Colourful． Java集合 java 集合
文章目录List接口概述List接口的常用方法List接口的实现类ArrayList源码分析类继承关系ArrayList中的属性：ArrayList构造函数：ArrayList中常用方法添加操作：add()删除操作：remove()获取元素：get()ArrayList是如何实现序列化的？ArrayList的总结LinkedList源码分析类继承关系类成员属性类构造器LinkedList的List
React Native通讯原理 zbl_zbl android ReactNativ
之前写过一篇文章ReactNativeAndroid源码分析，在此文章的基础上分析和总结下RN与Native的通讯流程。本文基于Android代码分析，iOS实现原理类似。1.通讯框架图先来解析下各个模块的角色与作用：Java层，这块的实现在ReactAndroid中-ReactContext:Android上下文子类，包含一个CatalystInstance实例，用于获取NativeModule
[linux 驱动]增加一个文件节点控制led灯亮灭嵌入式成长家 linux内核的系统实战 linux驱动 linux驱动 led灯驱动
目录1修改设备树2修改驱动3驱动源码3.1驱动源码3.2设备树节点3.3驱动源码分析3.3.1##解释3.3.2class_create解释3.3.3class_create_file解释3.3.4of_get_named_gpio_flags解释3.3.5devm_gpio_request解释3.3.6platform_driver_register解释3.3.7platform_driver_
【QT教程】QT6对话框编程 QT性能优化QT原理源码QT界面美化 qt qt6.3 qt5 c++QT教程
QT6对话框编程使用AI技术辅助生成QT界面美化视频课程QT性能优化视频课程QT原理与源码分析视频课程QTQMLC++扩展开发视频课程免费QT视频课程您可以看免费1000+个QT技术视频免费QT视频课程QT统计图和QT数据可视化视频免费看免费QT视频课程QT性能优化视频免费看免费QT视频课程QT界面美化视频免费看1QT6对话框编程基础1.1QT6对话框简介1.1.1QT6对话框简介QT6对话框简介
鸿蒙轻内核M核源码分析系列十二事件Event OpenHarmony_小贾 OpenHarmony HarmonyOS 鸿蒙开发 harmonyos openharmony 鸿蒙内核鸿蒙开发移动开发嵌入式硬件驱动开发
事件（Event）是一种任务间通信的机制，可用于任务间的同步。多任务环境下，任务之间往往需要同步操作，一个等待即是一个同步。事件可以提供一对多、多对多的同步操作。本文通过分析鸿蒙轻内核事件模块的源码，深入掌握事件的使用。本文中所涉及的源码，以OpenHarmonyLiteOS-M内核为例，均可以在开源站点https://gitee.com/openharmony/kernel_liteos_m获取
鸿蒙轻内核M核源码分析系列四中断Hwi OpenHarmony_小贾鸿蒙开发 OpenHarmony HarmonyOS harmonyos 单片机 OpenHarmony 嵌入式硬件鸿蒙开发移动开发鸿蒙内核
在鸿蒙轻内核源码分析系列前几篇文章中，剖析了重要的数据结构。本文，我们讲述一下中断，会给读者介绍中断的概念，鸿蒙轻内核的中断模块的源代码。本文中所涉及的源码，以OpenHarmonyLiteOS-M内核为例。1、中断概念介绍中断是指出现需要时，CPU暂停执行当前程序，转而执行新程序的过程。当外设需要CPU时，将通过产生中断信号使CPU立即中断当前任务来响应中断请求。在剖析中断源代码之前，下面介绍些
鸿蒙轻内核M核源码分析系列五时间管理 OpenHarmony_小贾 HarmonyOS OpenHarmony 鸿蒙开发 harmonyos openharmony 鸿蒙开发 NAPI 鸿蒙内核移动开发嵌入式
在鸿蒙轻内核源码分析上一篇文章中，我们剖析了中断的源码，简单提到了Tick中断。本文会继续分析Tick和时间相关的源码，给读者介绍鸿蒙轻内核的时间管理模块。本文中所涉及的源码，以OpenHarmonyLiteOS-M内核为例，均可以在开源站点https://gitee.com/openharmony/kernel_liteos_m获取。时间管理模块以系统时钟为基础，可以分为2部分，一部分是SysT
鸿蒙轻内核M核源码分析系列六任务及任务调度（1）任务栈 OpenHarmony_小贾鸿蒙开发 OpenHarmony HarmonyOS HarmonyOS openharmony 鸿蒙开发移动开发鸿蒙内核驱动开发嵌入式硬件
继续分析鸿蒙轻内核源码，我们本文开始要分析下任务及任务调度模块。首先，我们介绍下任务栈的基础概念。任务栈是高地址向低地址生长的递减栈，栈指针指向即将入栈的元素位置。初始化后未使用过的栈空间初始化的内容为宏OS_TASK_STACK_INIT代表的数值0xCACACACA，栈顶初始化为宏OS_TASK_MAGIC_WORD代表的数值0xCCCCCCCC。一个任务栈的示意图如下，其中，栈底指针是栈的最
鸿蒙轻内核M核源码分析系列三数据结构-任务排序链表 OpenHarmony_小贾 HarmonyOS OpenHarmony 鸿蒙开发数据结构 harmonyos 移动开发 OpenHarmony 鸿蒙内核鸿蒙开发嵌入式硬件
在鸿蒙轻内核源码分析系列一和系列二，我们分析了双向循环链表、优先级就绪队列的源码。本文会继续给读者介绍鸿蒙轻内核源码中重要的数据结构：任务排序链表TaskSortLinkAttr。鸿蒙轻内核的任务排序链表，用于任务延迟到期/超时唤醒等业务场景，是一个非常重要、非常基础的数据结构。本文中所涉及的源码，以OpenHarmonyLiteOS-M内核为例。1任务排序链表我们先看下任务排序链接的数据结构。任
鸿蒙轻内核A核源码分析系列七进程管理 (2) OpenHarmony_小贾 HarmonyOS 鸿蒙开发 OpenHarmony harmonyos OpenHarmony 移动开发驱动开发鸿蒙内核 LiteOS-A内核进程通信
本文先熟悉下进程管理的文件kernel\base\core\los_process.c中的内部接口，读读代码，做些记录。1、LiteOS-A内核进程全局变量⑴是进程池，存放各个进程控制块LosProcessCB的信息。⑵处开始的g_freeProcess是空闲进程链表，挂载各个空闲进程控制块；g_processRecycleList是待回收进程控制块链表，挂载各个等待回收的进程控制块。⑶处开始的g
鸿蒙原生开发——轻内核A核源码分析系列三物理内存（2） OpenHarmony_小贾鸿蒙开发 HarmonyOS OpenHarmony harmonyos openharmony 移动开发程序人生鸿蒙开发
3.1.2.3函数OsVmPhysLargeAlloc当执行到这个函数时，说明空闲链表上的单个内存页节点的大小已经不能满足要求，超过了第9个链表上的内存页节点的大小了。⑴处计算需要申请的内存大小。⑵从最大的链表上进行遍历每一个内存页节点。⑶根据每个内存页的开始内存地址，计算需要的内存的结束地址，如果超过内存段的大小，则继续遍历下一个内存页节点。⑷处此时paStart表示当前内存页的结束地址，接下来
OpenStack添加新硬盘到LVM逻辑卷组 LianZhenLiang
参考：CinderLVM配置https://www.cnblogs.com/sammyliu/p/4159147.htmlConfigureandusevolumenumberweigherhttps://docs.openstack.org/cinder/queens/admin/blockstorage-volume-number-weigher.html一、知识：cinderlvm配置(/e
JsonCpp源码分析——Reader 哎呦，帅小伙哦 #jsoncpp json
1、与Writer模块功能相反，可以将Reader理解成一个反序列化的工具，Writer的作用主要是将Value对象转成string或者流式的结构，Reader的作用主要是将流式的结构转成Value类型的对象。Reader类的主要职责有3个，解析JSON字符串：将JSON格式的字符串读取并解析成相应的C++数据结构。处理不同的数据类型，支持解析JSON对象、数组、字符串、数字、布尔值和null。处
vue源码分析-挂载流程和模板编译 yyzzabc123 vue.js
前面几节我们从newVue创建实例开始，介绍了创建实例时执行初始化流程中的重要两步，配置选项的资源合并,以及响应式系统的核心思想，数据代理。在合并章节，我们对Vue丰富的选项合并策略有了基本的认知，在数据代理章节我们又对代理拦截的意义和使用场景有了深入的认识。按照Vue源码的设计思路，初始化过程还会进行很多操作，例如组件之间创建关联，初始化事件中心，初始化数据并建立响应式系统等，并最终将模板和数据
鸿蒙内核解析,鸿蒙内核源码分析(内存概念篇)|解读鸿蒙源码刘轩鸿鸿蒙内核解析
提示：本文基于开源鸿蒙内核分析，官方源码【kernel_liteos_a】官方文档【docs】参考文档【HuaweiLiteOS】本文作者：鸿蒙内核发烧友，用生活场景讲故事的方式去解构内核，一窥究竟，让神秘的内核栩栩如生，浮现眼前。博文全部原创，持续更新，敬请关注。内容仅代表个人观点，错误之处，欢迎大家指正完善。本系列全部文章进入鸿蒙源码分析(总目录)查看目录最难讲的章节坦白讲内存是整个系列里面最
java封装继承多态等麦田的设计者 java eclipse jvm c encapsulatopn
最近一段时间看了很多的视频却忘记总结了，现在只能想到什么写什么了，希望能起到一个回忆巩固的作用。 1、final关键字译为：最终的 &
F5与集群的区别 bijian1013 weblogic 集群 F5
http请求配置不是通过集群，而是F5；集群是weblogic容器的，如果是ejb接口是通过集群。 F5同集群的差别，主要还是会话复制的问题，F5一把是分发http请求用的，因为http都是无状态的服务，无需关注会话问题，类似
LeetCode[Math] - #7 Reverse Integer Cwind java 题解 Math LeetCode Algorithm
原题链接：#7 Reverse Integer 要求：按位反转输入的数字例1：输入 x = 123, 返回 321 例2：输入 x = -123, 返回 -321 难度：简单分析：对于一般情况，首先保存输入数字的符号，然后每次取输入的末位（x%10）作为输出的高位（result = result*10 + x%10）即可。但
BufferedOutputStream 周凡杨
首先说一下这个大批量，是指有上千万的数据量。例子：有一张短信历史表，其数据有上千万条数据，要进行数据备份到文本文件，就是执行如下SQL然后将结果集写入到文件中！ select t.msisd
linux下模拟按键输入和鼠标被触发 linux
查看/dev/input/eventX是什么类型的事件， cat /proc/bus/input/devices 设备有着自己特殊的按键键码，我需要将一些标准的按键，比如0－9，X－Z等模拟成标准按键，比如KEY_0,KEY-Z等，所以需要用到按键模拟，具体方法就是操作/dev/input/event1文件，向它写入个input_event结构体就可以模拟按键的输入了。 linux/in
ContentProvider初体验肆无忌惮_ ContentProvider
ContentProvider在安卓开发中非常重要。与Activity，Service，BroadcastReceiver并称安卓组件四大天王。在android中的作用是用来对外共享数据。因为安卓程序的数据库文件存放在data/data/packagename里面，这里面的文件默认都是私有的，别的程序无法访问。如果QQ游戏想访问手机QQ的帐号信息一键登录，那么就需要使用内容提供者COnte
关于Spring MVC项目（maven）中通过fileupload上传文件 843977358 mybatis spring mvc 修改头像上传文件 upload
Spring MVC 中通过fileupload上传文件，其中项目使用maven管理。 1.上传文件首先需要的是导入相关支持jar包：commons-fileupload.jar,commons-io.jar 因为我是用的maven管理项目，所以要在pom文件中配置（每个人的jar包位置根据实际情况定） <!-- 文件上传 start by zhangyd-c --&g
使用svnkit api，纯java操作svn，实现svn提交，更新等操作 aigo svnkit
原文：http://blog.csdn.net/hardwin/article/details/7963318 import java.io.File; import org.apache.log4j.Logger; import org.tmatesoft.svn.core.SVNCommitInfo; import org.tmateso
对比浏览器，casperjs，httpclient的Header信息 alleni123 爬虫 crawler header
@Override protected void doGet(HttpServletRequest req, HttpServletResponse res) throws ServletException, IOException { String type=req.getParameter("type"); Enumeration es=re
java.io操作 DataInputStream和DataOutputStream基本数据流百合不是茶 java 流
1，java中如果不保存整个对象，只保存类中的属性，那么我们可以使用本篇文章中的方法，如果要保存整个对象先将类实例化后面的文章将详细写到 2，DataInputStream 是java.io包中一个数据输入流允许应用程序以与机器无关方式从底层输入流中读取基本 Java 数据类型。应用程序可以使用数据输出流写入稍后由数据输入流读取的数据。
车辆保险理赔案例 bijian1013 车险
理赔案例：一货运车，运输公司为车辆购买了机动车商业险和交强险，也买了安全生产责任险，运输一车烟花爆竹，在行驶途中发生爆炸，出现车毁、货损、司机亡、炸死一路人、炸毁一间民宅等惨剧，针对这几种情况，该如何赔付。赔付建议和方案：客户所买交强险在这里不起作用，因为交强险的赔付前提是：“机动车发生道路交通意外事故”；如果是交通意外事故引发的爆炸，则优先适用交强险条款进行赔付，不足的部分由商业
学习Spring必学的Java基础知识(5)—注解 bijian1013 java spring
文章来源：http://www.iteye.com/topic/1123823，整理在我的博客有两个目的：一个是原文确实很不错，通俗易懂，督促自已将博主的这一系列关于Spring文章都学完；另一个原因是为免原文被博主删除，在此记录，方便以后查找阅读。有必要对
【Struts2一】Struts2 Hello World bit1129 Hello world
Struts2 Hello World应用的基本步骤创建Struts2的Hello World应用，包括如下几步： 1.配置web.xml 2.创建Action 3.创建struts.xml，配置Action 4.启动web server，通过浏览器访问配置web.xml <?xml version="1.0" encoding="
【Avro二】Avro RPC框架 bit1129 rpc
1. Avro RPC简介 1.1. RPC RPC逻辑上分为二层，一是传输层，负责网络通信；二是协议层，将数据按照一定协议格式打包和解包从序列化方式来看，Apache Thrift 和Google的Protocol Buffers和Avro应该是属于同一个级别的框架，都能跨语言，性能优秀，数据精简，但是Avro的动态模式（不用生成代码，而且性能很好）这个特点让人非常喜欢，比较适合R
lua　set get cookie ronin47 lua cookie
lua: local access_token = ngx.var.cookie_SGAccessToken if access_token then ngx.header["Set-Cookie"] = "SGAccessToken="..access_token.."; path=/;Max-Age=3000" end
java-打印不大于N的质数 bylijinnan java
public class PrimeNumber { /** * 寻找不大于N的质数 */ public static void main(String[] args) { int n=100; PrimeNumber pn=new PrimeNumber(); pn.printPrimeNumber(n); System.out.print
Spring源码学习-PropertyPlaceholderHelper bylijinnan java spring
今天在看Spring 3.0.0.RELEASE的源码，发现PropertyPlaceholderHelper的一个bug 当时觉得奇怪，上网一搜，果然是个bug，不过早就有人发现了，且已经修复：详见： http://forum.spring.io/forum/spring-projects/container/88107-propertyplaceholderhelper-bug
[逻辑与拓扑]布尔逻辑与拓扑结构的结合会产生什么? comsci 拓扑
如果我们已经在一个工作流的节点中嵌入了可以进行逻辑推理的代码,那么成百上千个这样的节点如果组成一个拓扑网络,而这个网络是可以自动遍历的,非线性的拓扑计算模型和节点内部的布尔逻辑处理的结合,会产生什么样的结果呢? 是否可以形成一种新的模糊语言识别和处理模型呢? 大家有兴趣可以试试,用软件搞这些有个好处,就是花钱比较少,就算不成
ITEYE 都换百度推广了 cuisuqiang Google AdSense 百度推广广告外快
以前ITEYE的广告都是谷歌的Google AdSense，现在都换成百度推广了。为什么个人博客设置里面还是Google AdSense呢？都知道Google AdSense不好申请，这在ITEYE上也不是讨论了一两天了，强烈建议ITEYE换掉Google AdSense。至少，用一个好申请的吧。什么时候能从ITEYE上来点外快，哪怕少点
新浪微博技术架构分析 dalan_123 新浪微博架构
新浪微博在短短一年时间内从零发展到五千万用户，我们的基层架构也发展了几个版本。第一版就是是非常快的，我们可以非常快的实现我们的模块。我们看一下技术特点，微博这个产品从架构上来分析，它需要解决的是发表和订阅的问题。我们第一版采用的是推的消息模式，假如说我们一个明星用户他有10万个粉丝，那就是说用户发表一条微博的时候，我们把这个微博消息攒成10万份，这样就是很简单了，第一版的架构实际上就是这两行字。第
玩转ARP攻击 dcj3sjt126com r
我写这片文章只是想让你明白深刻理解某一协议的好处。高手免看。如果有人利用这片文章所做的一切事情，盖不负责。网上关于ARP的资料已经很多了，就不用我都说了。用某一位高手的话来说，“我们能做的事情很多，唯一受限制的是我们的创造力和想象力”。 ARP也是如此。以下讨论的机子有一个要攻击的机子：10.5.4.178 硬件地址：52:54:4C:98
PHP编码规范 dcj3sjt126com 编码规范
一、文件格式 1. 对于只含有 php 代码的文件，我们将在文件结尾处忽略掉 "?>" 。这是为了防止多余的空格或者其它字符影响到代码。例如：<?php$foo = 'foo';2. 缩进应该能够反映出代码的逻辑结果，尽量使用四个空格，禁止使用制表符TAB，因为这样能够保证有跨客户端编程器软件的灵活性。例
linux 脱机管理（nohup） eksliang linux nohup nohup
脱机管理 nohup 转载请出自出处：http://eksliang.iteye.com/blog/2166699 nohup可以让你在脱机或者注销系统后，还能够让工作继续进行。他的语法如下 nohup [命令与参数] --在终端机前台工作 nohup [命令与参数] & --在终端机后台工作但是这个命令需要注意的是，nohup并不支持bash的内置命令，所
BusinessObjects Enterprise Java SDK greemranqq java BO SAP Crystal Reports
最近项目用到oracle_ADF 从SAP/BO 上调用水晶报表，资料比较少，我做一个简单的分享，给和我一样的新手提供更多的便利。首先，我是尝试用JAVA JSP 去访问的。官方API：http://devlibrary.businessobjects.com/BusinessObjectsxi/en/en/BOE_SDK/boesdk_ja
系统负载剧变下的管控策略 iamzhongyong 高并发
假如目前的系统有100台机器，能够支撑每天1亿的点击量（这个就简单比喻一下），然后系统流量剧变了要，我如何应对，系统有那些策略可以处理，这里总结了一下之前的一些做法。 1、水平扩展这个最容易理解，加机器，这样的话对于系统刚刚开始的伸缩性设计要求比较高，能够非常灵活的添加机器，来应对流量的变化。 2、系统分组假如系统服务的业务不同，有优先级高的，有优先级低的，那就让不同的业务调用提前分组
BitTorrent DHT 协议中文翻译 justjavac bit
前言做了一个磁力链接和BT种子的搜索引擎 {Magnet & Torrent}，因此把 DHT 协议重新看了一遍。 BEP: 5Title: DHT ProtocolVersion: 3dec52cb3ae103ce22358e3894b31cad47a6f22bLast-Modified: Tue Apr 2 16:51:45 2013 -070
Ubuntu下Java环境的搭建 macroli java 工作 ubuntu
配置命令：　　$sudo apt-get install ubuntu-restricted-extras 　　再运行如下命令：　　$sudo apt-get install sun-java6-jdk 　　待安装完毕后选择默认Java. 　　$sudo update- alternatives --config java 　　安装过程提示选择，输入“2”即可，然后按回车键确定。
js字符串转日期（兼容IE所有版本） qiaolevip TO Date String IE
/** * 字符串转时间（yyyy-MM-dd HH:mm:ss） * result （分钟） */ stringToDate : function(fDate){ var fullDate = fDate.split(" ")[0].split("-"); var fullTime = fDate.split("
【数据挖掘学习】关联规则算法Apriori的学习与SQL简单实现购物篮分析 superlxw1234 sql 数据挖掘关联规则
关联规则挖掘用于寻找给定数据集中项之间的有趣的关联或相关关系。关联规则揭示了数据项间的未知的依赖关系，根据所挖掘的关联关系，可以从一个数据对象的信息来推断另一个数据对象的信息。例如购物篮分析。牛奶 ⇒ 面包 [支持度：3%，置信度：40%] 支持度3%：意味3%顾客同时购买牛奶和面包。置信度40%：意味购买牛奶的顾客40%也购买面包。规则的支持度和置信度是两个规则兴
Spring 5.0 的系统需求，期待你的反馈 wiselyman spring
Spring 5.0将在2016年发布。Spring5.0将支持JDK 9。 Spring 5.0的特性计划还在工作中，请保持关注，所以作者希望从使用者得到关于Spring 5.0系统需求方面的反馈。