nacx commented on this pull request.
> + .overrides(neutronProperties)
+ .modules(ImmutableSet.of(new SLF4JLoggingModule()))
+ .build();
+
+// Create the connection to OpenStack nova and link it to Neutron
+NovaApi nova = ContextBuilder.newBuilder("openstack-nova")
+ .endpoint("http://localhost/identity/v3/";)
+ .credentials("domain:user", "password")
+ .overrides(novaProperties)
+ .modules(ImmutableSet.of(
+ ContextLinking.linkContext(neutronCtx),
+ new SLF4JLoggingModule()))
+ .buildApi(NovaApi.class);
+{% endhighlight %}
+
+With this configuration the `nova` API is configured to use the linked
`neutron` for all networking operations.
Because of the natural meaning of the APIs. Neutron is just a networking API,
whilst Nova is the compute API that also performs networking operations when
creating servers. It is nova the one that logically uses neutron, not the other
way. I guess this would be what most users will already assume?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/209#discussion_r166658210
