Repository: jclouds-site Updated Branches: refs/heads/nova-neutron bd13a7ee8 -> e32f77e7e
Review comments Project: http://git-wip-us.apache.org/repos/asf/jclouds-site/repo Commit: http://git-wip-us.apache.org/repos/asf/jclouds-site/commit/e32f77e7 Tree: http://git-wip-us.apache.org/repos/asf/jclouds-site/tree/e32f77e7 Diff: http://git-wip-us.apache.org/repos/asf/jclouds-site/diff/e32f77e7 Branch: refs/heads/nova-neutron Commit: e32f77e7eb4f0abaef4a07bdf8e35dd454e5654b Parents: bd13a7e Author: Ignasi Barrera <n...@apache.org> Authored: Fri Feb 23 08:56:15 2018 +0100 Committer: Ignasi Barrera <n...@apache.org> Committed: Fri Feb 23 08:56:15 2018 +0100 ---------------------------------------------------------------------- _layouts/home.html | 2 +- _posts/2018-02-06-nova-neutron.md | 17 +++++++++++------ 2 files changed, 12 insertions(+), 7 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/jclouds-site/blob/e32f77e7/_layouts/home.html ---------------------------------------------------------------------- diff --git a/_layouts/home.html b/_layouts/home.html index c0b481f..b7dff6b 100644 --- a/_layouts/home.html +++ b/_layouts/home.html @@ -40,7 +40,7 @@ </div> <div id="keystonev3" class="alert alert-success"> - <p>If you are an OpenStack user, read our blog posts about the <a href="/blog/2018/01/16/keystone-v3/">OpenStack Keystone V3</a> and <a href="/blog/2018/02/06/nova-neutron">OpenStack Nova and Neutron</a> integrations that will be released in jclouds <strong>2.1.0</strong>!</p> + <p>Read our blog posts about the <a href="/blog/2018/01/16/keystone-v3/">OpenStack Keystone V3</a> and <a href="/blog/2018/02/06/nova-neutron">Context linking & Neutron support for Nova</a> integrations released in jclouds <strong>2.1.0</strong>!</p> </div> <div id="releasenews" class="alert alert-info"> http://git-wip-us.apache.org/repos/asf/jclouds-site/blob/e32f77e7/_posts/2018-02-06-nova-neutron.md ---------------------------------------------------------------------- diff --git a/_posts/2018-02-06-nova-neutron.md b/_posts/2018-02-06-nova-neutron.md index b9929a8..a761255 100644 --- a/_posts/2018-02-06-nova-neutron.md +++ b/_posts/2018-02-06-nova-neutron.md @@ -4,19 +4,24 @@ comments: true date: 2018-02-06 07:00:00+00:00 layout: post slug: nova-neutron -title: OpenStack Nova and Neutron +title: Introducing context linking & Neutron support for Nova --- -One of the limitations of the jclouds implementation of the OpenStack Nova API is that is was not able to directly talk to the Neutron service. It used legacy security group APIs to manage access to instances, and there was no proper support for custom networking. +One of the limitations of some jclouds APIs and Providers is that they are isolated libraries that cannot directly interact between them. There are scenarios where this would be desirable, such as letting OpenStack Nova (compute) use the OpenStack Neutron API (networking) to perform all networking related operations. There was no direct way to implement this in the jclouds APIs code, and users were left with the responsibility of invoking both APIs to have the desired behavior. + +Apache jclouds 2.1.0 comes with a **context linking** feature, where APIs and providers that have dependencies between them can be *linked* so they can call each other where needed. -Starting from Apache jclouds 2.1.0, an integration with OpenStack Neutron will be provided and users will be able to configure their Nova APIs to interact with a custom Neutron deployment. <!-- more --> -To achieve this, users will be able to use the recent **context linking** feature, where APIs and providers that have dependencies between them can be *linked* so they can call each other where needed. +## Context Linking -## Linking OpenStack Nova to Neutron +Linking one API or Provider to another is something that has to be defined in the API or Provider itself. It is a mechanism that allows users to inject an API or Provider *inside* a given jclouds context, so the API that *receives* the linked context can use it internally. Linking is not supposed to be used to link arbitrary APIs and Providers (that would have no effect), but APIs that are *prepared* to receive linked contexts and call its API methods. + +For example, in jclouds 2.1.0, OpenStack Nova has been integrated with Neutron, and users will be able to link the `openstack-nova` context to an `openstack-neutron` one so the Nova API can use the Neutron features to manage all networking stuff. On the other hand, linking other APIs or providers together may have no effect, as the code for those APIs and providers may not expect any linked context. When thinking about linking two contexts together, please refer to the docs. -Links between APIs and providers are done at *context* level. This isolates each individual context and allows users to configure an independent set of properties for each one without overlapping issues. The `ContextLinking.linkContext` and `ContextLinking.linkView` helper methods can be used to easily link one context or view to another. +Linking is done at *context* level, and links are specified in the *using* context and point to the context(s) that it uses. This isolates each individual context and allows users to configure an independent set of properties for each one without overlapping issues. The `ContextLinking.linkContext` and `ContextLinking.linkView` helper methods can be used to easily link one context or view to another. + +## Linking OpenStack Nova to Neutron The following example shows how to link an OpenStack Nova API to a Neutron API context, to leverage Neutron features when provisioning instances with Nova:
