Public bug reported:

https://review.openstack.org/273439
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

commit aadf2f30f84dff3d85f380a7ff4e16dbbb0c6bb0
Author: armando-migliaccio <arma...@gmail.com>
Date:   Thu Jan 28 01:39:00 2016 -0800

    Add the ability to load a set of service plugins on startup
    
    Service plugins are a great way of adding functionality in a
    cohesive way. Some plugins (e.g. network ip availability or
    auto_allocate) extend the capabilities of the Neutron server
    by being completely orthogonal to the core plugin, and yet may
    be considered an integral part of functionality available in
    any Neutron deployment. For this reason, it makes sense to
    include them seamlessly in the service plugin loading process.
    
    This patch, in particular, introduces the 'auto_allocate' service
    plugin for default loading, as we'd want this feature to be enabled
    for Nova to use irrespective of the chosen underlying core plugin.
    
    The feature requires subnetpools, external_net and router, while
    the first is part of the core, the others can be plugin specific
    and they must be explicitly advertised. That said, they all are
    features that any deployment can hardly live without.
    
    DocImpact: The "get-me-a-network" feature simplifies the process
    for launching an instance with basic network connectivity (via an
    externally connected private tenant network).
    
    Once leveraged by Nova, a tenant/admin is no longer required to
    provision networking resources ahead of boot process in order to
    successfully launch an instance.
    
    Implements: blueprint get-me-a-network
    
    Change-Id: Ia35e8a946bf0ac0bb085cde46b675d17b0bb2f51

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: doc neutron

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1544383

Title:
      Add the ability to load a set of service plugins on startup

Status in neutron:
  New

Bug description:
  https://review.openstack.org/273439
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit aadf2f30f84dff3d85f380a7ff4e16dbbb0c6bb0
  Author: armando-migliaccio <arma...@gmail.com>
  Date:   Thu Jan 28 01:39:00 2016 -0800

      Add the ability to load a set of service plugins on startup
      
      Service plugins are a great way of adding functionality in a
      cohesive way. Some plugins (e.g. network ip availability or
      auto_allocate) extend the capabilities of the Neutron server
      by being completely orthogonal to the core plugin, and yet may
      be considered an integral part of functionality available in
      any Neutron deployment. For this reason, it makes sense to
      include them seamlessly in the service plugin loading process.
      
      This patch, in particular, introduces the 'auto_allocate' service
      plugin for default loading, as we'd want this feature to be enabled
      for Nova to use irrespective of the chosen underlying core plugin.
      
      The feature requires subnetpools, external_net and router, while
      the first is part of the core, the others can be plugin specific
      and they must be explicitly advertised. That said, they all are
      features that any deployment can hardly live without.
      
      DocImpact: The "get-me-a-network" feature simplifies the process
      for launching an instance with basic network connectivity (via an
      externally connected private tenant network).
      
      Once leveraged by Nova, a tenant/admin is no longer required to
      provision networking resources ahead of boot process in order to
      successfully launch an instance.
      
      Implements: blueprint get-me-a-network
      
      Change-Id: Ia35e8a946bf0ac0bb085cde46b675d17b0bb2f51

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1544383/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to