demobox 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.

> I guess this would be what most users will already assume?

I was just asking because "link" is bidirectional as a verb (as opposed to, 
say, "use") - it could mean "uses", as in this case, or "connected to", which 
could be the other way around (i.e. "Neutron connected to Nova").

Would it make sense, in the description of context linking, to extend the 
current sentence "...helper methods can be used to easily link one context or 
view to another." to something like "Links are specified in the 'using' context 
and point to the context(s) that it uses."?

-- 
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_r166832158

Reply via email to