This is an automated email from the ASF dual-hosted git repository. duncangrant pushed a commit to branch ruby-3 in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
commit cf28bf43e0ee3c14a1f65381cf04b43bfbac9993 Merge: d4f7185 2f2ed97 Author: Alex Heneveld <[email protected]> AuthorDate: Tue Sep 4 15:12:20 2018 +0100 Merge commit '2f2ed97c' into release-5.0-reverted-222 guide/locations/_openstack.md | 67 ++++++++++++++++++++++++++++++++++++------- 1 file changed, 56 insertions(+), 11 deletions(-) diff --cc guide/locations/_openstack.md index 942eaa5,2d0061f..33d3748 --- a/guide/locations/_openstack.md +++ b/guide/locations/_openstack.md @@@ -1,17 -1,21 +1,28 @@@ +--- +section: OpenStack +title: OpenStack +section_type: inline +section_position: 7 +--- + ## OpenStack - ### Apache jclouds - Support for OpenStack is provided by Apache jclouds. For more information, see their guide - [here](https://jclouds.apache.org/guides/openstack/). + Brooklyn requires the following API to deploy an application onto an OpenStack-based provider + + - Identity API (a.k.a. OpenStack Keystone): [Identity API v2](https://developer.openstack.org/api-ref/identity/v2/) and [Identity API v3](https://developer.openstack.org/api-ref/identity/v3/) The Identity API provides an authentication and authorization service for other OpenStack services. It also provides a catalog of endpoints for all OpenStack services, like the Compute service, a.k.a OpenStack Nova. + + - Compute API (a.k.a. OpenStack Nova): [Compute API](https://developer.openstack.org/api-ref/compute/) manages the lifecycle of compute instances in an OpenStack environment. Responsibilities include spawning, scheduling and decommissioning of machines on demand by talking to different hypervisors. + In some old OpenStack installations, `Nova SecurityGroupAPI extension` is generally used to manage Security Groups, when required. + + - Networking API (a.k.a OpenStack Neutron): [Network API v2.0](https://developer.openstack.org/api-ref/network/v2) enables network connectivity as a service for other OpenStack services, such as OpenStack Compute. It provides an API for users to define networks and the attachments into them. It has a pluggable architecture that supports many popular networking vendors and technologies. + + Apache jclouds may optionally need to talk to the `OpenStack Neutron API` to manage networks, subnets, security groups and ports, by linking [Neutron Context to Nova Context](http://jclouds.apache.org/blog/2018/02/06/nova-neutron/). + In some cases it may be required to leverage OpenStack Neutron Extensions such as LoadBalancer-aaS, the FloatingIp API, the Router API or the Firewall-aaS API when available. + + Brooklyn offers supports up to [OpenStack Pike](https://releases.openstack.org/pike/index.html) release via Apache jclouds. For more information, see their guide + [here](https://jclouds.apache.org/guides/openstack/). ### Connection Details @@@ -31,10 -70,9 +77,9 @@@ as an openrc.sh file. It is usually ava This file will normally contain the identity and credential. Users are strongly recommended to use -[externalized configuration]({{book.path.docs}}/ops/externalized-configuration.md) for better +[externalized configuration]({{ site.path.guide }}/ops/externalized-configuration.html) for better credential management, for example using [Vault](https://www.vaultproject.io/). - ### Common Configuration Options Below are examples of configuration options that use values specific to OpenStack environments:
