In devstack, we have host in Default and in api. To get the HOST_IP
we must look in the api section. Use iniget to take the IP instead of
awk, making more concise where the IP comes from.
Recommend to use --concurrency 1 when running tests to avoid creating
multiple clusters.
Change-Id: I9b38bc88e4157e6692d7cffaed538c4c0a769d03
'code-block' improves the visibility for the pieces of code. This
commit splits code and result message by using 'code-block: python' and
'code-block: console'.
Change-Id: Id11e0990da4dae8d47c6de7d19479cb9940890b2
Magnum CLI now support cluster-config command. However, the quickstart guide
hasn't been updated to use this command yet. This patch added usage for
cluster-config command in quickstart guide.
Change-Id: I21341fe90c09f8f21e33bda4592c9175f3d16375
Closes-Bug: #1614685
Update from this commit https://review.openstack.org/#/c/389971/1
in the openstack-manuals project.
Follow-up of I54a104662081ab7b81e200cf6c23f5a8a1e28d61.
Change-Id: Ide7d831a749c394c90ac8303643fd1184bb0c56f
Related-Bug: #1635615
Updates magnum documentation to reflect the changes made for
bp/rename-id-parameter-names.
Change-Id: I7c0d69970b9ac50649cac0e80932b5971ce09c3f
Depends-on: Idc6b9322ec7c0ecb386162ca46c7d49b910685d8
Implements: blueprint rename-id-parameter-names
In the swarm_atomic and k8s_atomic drivers container images are
stored in a dedicated cinder volume per cluster node. It is
proven that this architecture can be a scalability bottleneck.
Make the use of cinder volumes for container images and opt-in
option. If docker-volume-size is not specified no cinder
volumes will be created. Before, if docker-volume-size wasn't
specified the default value was 25.
To use cinder volumes for container storage the user will
interact with magnum as before, (meaning the valid values are
integers starting from 1).
Closes-Bug: #1638006
Change-Id: I3394c62a43bbf950b7cf0b86a71b1d9b0481d68f
The troubleshooting guide has a python script in it which has invalid
syntax. This removes the extra bracket from that script and makes it
function correctly. I also added some more specificity for credentials.
Change-Id: I9c8b8f861b4226d9eddca4ab44c811faa89160bc
We must add the user-domain to ensure than the user is from
the magnum domain.
Change-Id: I8defb35f745f7df2e20deea759a43ef1bb47d248
Closes-bug: #1635202
Keypair can now be added during Cluster create command. This allows
Clusters to be created from the same ClusterTemplate but have
different keypair values when created. If not specified on create
then the value from the ClusterTemplate will be used. Adds keypair_id
to Cluster object and uses of keypair_id will use the value from Cluster
instead of ClusterTemplate.
Added release note for new features in magnum and magnum CLI.
Change-Id: I177a5aa06f881156944a9f74c9ccc3cd2abac492
Implements: blueprint keypair-override-on-create
There is an environment that the google public DNS is not
able to use for the --dns-servername.
Before specifying the dns-servername, it's better to confirm
that the DNS can resolve server names properly at your
environment, otherwise, you will fail cluster creation.
Also this commit fixes some old links at the network
troubleshooting section of ops guide.
Change-Id: I2f765a8ff94ad54f3fb1fb029a36fdea328ea514
We currently allow Magnum to scale down mesos cluster by removing nodes
from the cluster's ResourceGroup by updating the heat stack that created
the cluster. The problem with this approach is that Heat decides which
nodes to delete, and all containers on that node will also be deleted.
The smart cluster scale down feature has been implemented for k8s bays(
for k8s cluster, we'll ask Heat to delete nodes that have NO CONTAINERS
on them).
This patch proposes a similar implementation for a mesos cluster.
Change-Id: I00cda7f35c9db978bdc604cf86603ef58e339256
Implements: blueprint mesos-smart-bay-scale-down
Fix node name and auth_url
Update the url to Keystone v2 which has been changed.
The name of the node registered in the kube-apiserver
was also changed at some point to use the IP instead of the
Nova instance name as was done originally, and this
broke the Kubernetes plugin code. Change the node name
back to the Nova instance name in the option
--hostname-override for kubelet.
Some update to the document.
With this patch, the load balancer works with Magnum Newton
and later, along with the image fedora-atomic-latest.
Important notes:
1. The current image has Kubernetes release 1.2 and this only
works with neutron LBaaS v1. Support for LBaaS v2 requires
Kubernetes release 1.3 or later. Magnum support for 1.3
is still in development.
2. LBaaS v1 has been removed in Newton and is only available
in Mitaka or by custom installation (likely requires some hacking).
This means to get the load balancer feature, you will want to
install Openstack Mitaka and Magnum Newton.
Change-Id: Ica9d92c8d7410bf30832005687ecce4a90ef6c58
Closes-Bug: #1524025
Add Horizon and Native Clients sections
Describe the Magnum UI plugin for Horizon and how to get it.
Include some screenshots for reference.
Describe the clients for interfacing with the COE and how to
get them.
Change-Id: I2b9c25d3e88f03f4a18278081336e59c7766e775
Partially implements: blueprint user-guide
Update the gate and docs to use "ubuntu-mesos-latest" instead of
"ubuntu-14.04.3-mesos-0.25.0.qcow2". The intent is to make the
image upgrade easier (by using a static image name). In fedorapeople,
a soft link was created from "ubuntu-mesos-latest.qcow2" to
"ubuntu-14.04.3-mesos-0.25.0.qcow2"
Change-Id: I544773d184e5436843595dbfd9ab118b99870281
* Adds a script to install dependancies when building the Ubuntu
Mesos image (used in OpenStack infra)
* Fixes Dockerfile to build the Ubuntu Mesos image
(it was missing components to add Heat agent in the image)
* Changes the name of the Mesos Ubunutu image because the Ubuntu
version and Mesos version has changed
* Fixes a broken link in the doc
Change-Id: I35ffd4bd358a62dd7cf0d0e485b531a36b6c262b
* Use user_domain_name and project_domain_name instead of IDs
* Use trustee_domain_name and trustee_domain_admin_name instead of IDs
Change-Id: I30f0173fb9bf68729fa7f45999765970fe1915cb
Closes-Bug: #1624989
Add magnum-ui panel in horizon
Magnum UI plugin for horizon is nice feature for users
and can now be easily enabled in devstack. There has been
multiple queries on the IRC on how to get the Magnum UI
so this will help.
Change-Id: I31f0c7ec866fbd4629d99da3137931ee30b352c1
Previously, the client was installed in a virtualenv
only accessible by the magnum service user.
Add instructions to install the client as a non-root user.
Change-Id: I865292e69d4a8683aa94440de88e357835feab78
Partially-Implements: blueprint magnum-installation-guide
Fix the bullet list in of optional services in packages install-guide
and in the install-guide from source.
Change-Id: I57154c6afa1c97aee36d58d32352ff91aa14e73a
Partially-Implements: blueprint magnum-installation-guide
The order of enabling devstack plugin is important if project
has dependency of other projects.
Magnum has some dependency of projects, so this patch fixes
the order of enabling plugin.
Change-Id: I733e061fab4ed40fd00bfb017d9c2835c49f6a8f
The Kubernetes external load balancer developer's guide needs to be
updated to reflect the fact that the kubernetes controller manager
has been moved to a separate pod.
Also, the external load balancer dev guide needs to explain that different
versions of Kubernetes require different versions of Neutron LBaaS:
- Kubernetes 1.2 requires Neutron LBaaS v1
- Kubernetes 1.3 (or later) requires Neutron LBaaS v2
Change-Id: I75fcaf0e990944c9eeef31815c2b6646388b5edf
Partial-Bug: #1524025
Now that heat is available as a devstack plugin, we should
use it. In-tree devstack code for heat is planned to be
removed soon[1].
And also, this patch remove `update_heat_policy` function
in devstack plugin. Because fetching global stack list is
already option to use in Magnum.
[1] https://review.openstack.org/#/c/317618/
Change-Id: Iab675da5ea8d02b3f7e71f6169c81724a0066858
Co-Authored-By: OTSUKA, Yuanying <yuanying@fraction.jp>
* Add cli install instructions in the install-guide-from-source
* Link the launch an instance and verify operation sections
Change-Id: I82b029ff85f56ee34e037e9287753d3212fd2982
Partially-Implements: blueprint magnum-installation-guide
* Update the required services for magnum, providing links
for the new ITs (Installations Tutorials).
* Remove bay terminology
Change-Id: If048642876285622466517e541e9028931c71b48
Partially-Implements: blueprint magnum-installation-guide
