In our specs we not correctly reference as rst format, which
is not good to display well for readers.
Change-Id: Idca82ae3b2b447a40870b38b820c008db219165b
Allow configuring Flannel with 3 different backends
Magnum deploys k8s/swarm over a dedicated neutron private network,
possibly using flannel. Flannel's `host-gw` backend gives the best
performance in this topopolgy (private layer2): no packet processing
overhead, no reduction to MTU, scales to many hosts as well as the
alternatives. The performance difference is significant, see bug for
performance numbers for the 3 backend options.
Note that part of this change involves relaxing the minion IP spoofing
rules to allow traffic from all dynamically-allocated flannel subnets.
This is morally equivalent to what we were doing previously with
encapsulation - only now neutron is able to see the inner IP header
directly.
This patch repurposes the label "flannel_use_vxlan" when the network
driver is flannel.
1. Rename the label flannel_use_vxlan to flannel_backend
2. Redefine the value of this label from "yes/no"
to "udp/vxlan/host-gw"
For example, to create a bay model with flannel as network driver:
--network-driver flannel --labels flannel_backend=host-gw
Other backend options are udp and vxlan.
Co-Authored-By: Ton Ngo <ton@us.ibm.com>
Partial-Bug: #1518605
Closes-Bug: #1516789
Change-Id: I6d2441664ad1baaca14d0e6ff4bcddbe75bee094
Divided to different sections in Definitions area, because that was one sentences.
Change-Id: I548defff0e462ee15dd150a6b0d5c4337b1cdaf0
Closes-Bug: 1516261
There are multiple ways to slice an OpenStack cloud. Imposing
quota on these various slices puts a limitation on the amount
of resources that can be consumed by a project which helps to
guarantee "fairness" or fair distribution of resource. If a
particular project needs more resources, the concept of
quota, gives the ability to increase the resource count
on-demand, given that the system constraints are not exceeded.
Change-Id: I6013057d689deb66a371adace96082df747f2b54
Partially-Implements: blueprint resource-quota
Now libnetwork-driver was changed to network-driver. and the
labels is now flannel_network_cidr', 'flannel_use_vxlan',
'flannel_network_subnetlen'.
The patch update the network-driver and labels attributes.
Change-Id: I10265fffcb09632b3230b60369ac08637bd038ec
Some services which are running in a bay need to access OpenStack
services. In order to access OpenStack services, we can create a
trustee for each bay and delegate a limited set of rights to the
trustee.
Partially-Implements: blueprint create-trustee-user-for-each-bay
Change-Id: Ifbb5b536201a6f65038be94118b36e6033b88512
This change include spec and related general architecture fig
Partially-Implements: blueprint magnum-integrate-with-cinder
Change-Id: I76104c17082c3173b33f0dec28f22160171fe41a
Rename heat-kubernetes to kubernetes, heat-mesos to mesos,
docker-swarm to swarm in templates. We use heat templates and
no other methods, so I think it is unnecessary to add heat before
coe. kubernetes, mesos, swarm are better than
heat-kubernetes, heat-mesos, docker-swarm.
Change-Id: I257b35c1c4ef55d3172095736f550f2c55c8d81f
Closes-Bug: #1514682
To make magnum more secure to be used in real production
environment, we should support authentication using TLS.
This spec defines the implementation design.
Change-Id: Ieefe2ffaa6cbf2d2a1446f97aee9c70ad4b99a03
Co-Authored-By: Motohiro OTSUKA<ootsuka@mxs.nes.nec.co.jp>
Co-Authored-By: Adrian Otto <adrian.otto@rackspace.com>
Partially-Implements: bp secure-kubernetes
Update examples in docs to use fedora-21-atomic-5
This patch will update documentation for use
of magnum as we know new image of fedora 1.0.4
has been built.
Change-Id: Ic02428237d12478a7f1e43510865258f5f837d18
Partially-Implements: blueprint kubernetes-v1
Add doc8 to `tox -edocs` command. doc8 will check syntax/style check
rst documents and fail if not compliant.
Change-Id: Id2e9ed1f96cac27dc5e38f828fd2d824dad31c49
The link given to Docker API getting error as it
is old version. So I removed the version extension
and also named it as "Docker Remote API"
Change-Id: If3d6ce2c74455a2d8c2c9fff51af1f5cbe330e76
Closes-Bug: #1488708
According to the wikipedia page, Representational
state transfer should be written as REST but in some
files it is written as ReST, so I changed it to
correct one
Change-Id: I1909b09fbe3e4ed99d817fdaf0006ef55367e74d
Closes-Bug: #1488816
Previously, Magnum did not contain a specification that outlines
how the project intends to provide networking to containers. This
patch provides an initial container networking specification.
Change-Id: I7783dc3c351dbcba63b74f5fdf3223e664f3af13
Currently there is no way for a user to interact with Magnum through a web based
user interface, as they are used to doing with other OpenStack components. This
implementation aims to introduce this interface as an extension of Horizon (the
OpenStack Dashboard) and expose all the features of Magnum in a way familiar to
users.
Implements: blueprint magnum-horizon-plugin
Change-Id: I832ee1fdf0c9b2f1ece8b01329d5c7f5bec8ae3c
The specs/containers-services.rst contains several trailing white
spaces. They makes it less compliant with PEP8, which all the other
python files are following, even though this file is .rst. Also,
trailing white spaces are marked red in the review page, which makes
them annoying. This patch removes them.
Change-Id: I3cb75922d15d42740523257c8420086fdcaab0f9