| Age | Commit message (Collapse) | Author | Files | Lines |
|
Implements: blueprint kube-neutron-container
Previously, only the neutron-server service was functional. This
patch adds support the the rest of the neutron services need by
Nova instances to function. The linux-bridge agent is used instead
of the OVS agent to realize network abstractions. This is because
the ovs-agent package will install the kernel module version of OVS
instead of the userspace version. Additionally, the OVS
userspace code is still very experimental and reduces performance.
Requires:
https://github.com/larsks/heat-kubernetes/pull/8
Change-Id: I5ef34ddeb48d4954934571a928cc82ae7f3a0f20
|
|
Horizon requires that Nova, Neutron(Nova Network), Glance,
and Keystone are running. Therefore, the container needs to
check for the availablity of each service on startup.
The config file is not a .ini file, but rather a python file
so it requires using sed instead of crudini.
Change-Id: I5ed14514881fe9aef688ca08bcb94881ef5b25cb
|
|
|
|
|
|
The current implementation has been configured to use sqlite instead of
mongodb, since that container service is not yet available. Also, there
are no Icehouse RPMs available, so the Juno RPMs are fetched and
manually installed.
Implements: blueprint kube-zaqar-container
Change-Id: Ie875ab43ad3db92ae2712492ee151fbad0fec3cc
|
|
Previously, the nova-network service was not fully functional.
This patch adds multi-interface support to the nova-network
container. The eth0 configuration is moved to a bridge (br100 per
nova defaults), and configures eth0 and eth1 as bridged
interfaces. eth0 is used for the nova-flat network and eth1 for
foating-ip's. This model is identical to typical bare-metal
nova-network deployments. The patch depends on the following patch
to kube-heat template that provides multiple interfaces per minion:
https://github.com/larsks/heat-kubernetes/pull/8
Rebased. Fixed merge conflict with k8s/pod/nova-compute-pod.yaml
Change-Id: Ieb59f397981a226555ce55ca621ef578b987e3c6
|
|
Implements: blueprint kube-mongodb-container
Change-Id: If76f6c0be90c3025933795d262304a10bf1a880d
|
|
|
|
Implements: blueprint kube-ceilometer-container
Change-Id: Ic9be6f2fb57641aa77f7f3a31481b166adad3f36
|
|
|
|
Adding Dockerfile, pod and service. Please note
that this uses the Juno version of Barbican
from tar ball and uses uwsgi to run the service.
Addressed review comments and added admin service
as well.
Fixing Maintainer email and yum clean up
Change-Id: If58c5eec00131582024045f8d213e48f9f466f4d
|
|
Change-Id: I6ee985e694142aa7dadeb085b77910667ac6359f
|
|
Remove individual MAINTAINER information from Dockerfiles.
Change-Id: I777df5cde049599dc786176e1d5b4b9597f0b334
|
|
this patch creates a dummy interface ("flat0") and uses that for
flat_interface. This prevents nova from breaking container networking
when it adds the container eth0 to the nova bridge (br100).
Change-Id: I93c696a8476228d6bbca678748170c2a11d5af11
|
|
global script is called "kolla-common.sh" not "config-common.sh".
Change-Id: I0303d33c786d575ac4b061b4060f626213bc583b
|
|
Not all nova services need a bridge. Remove bridge creation from
nova-base config and place in nova-network specifically.
Change-Id: Ia78c65a4661cd95112dca7ffdc1e839d4f648d52
|
|
libvirt-start.sh was missing from nova-compute/nova-compute. Add it
so libvirt is started from a fresh checkout of the repository.
Change-Id: I8b40819629b16e4a63102eb353b3c8682791cf9d
|
|
|
|
The readme was woefully old. Make it more modern to match the current
state of the repository and development.
Change-Id: I9be10ca8565835c784afea63ee70978d10313e4a
|
|
The images are already updated, so this can be approved immediately
following the dependent implementation commit.
Change-Id: Ida3d6b5b64256a63652dffba9dff2365e3755286
|
|
|
|
Loosely followed this document for setting up Heat:
http://docs.openstack.org/icehouse/install-guide/install/yum/content/heat-install.html
Some gotchas:
- crux doesn't require escaping parenthesis for endpoint creation like
keystone client
- heat icehouse packages are configured for qpid, so kombu had to be
specified specifically
This firewall reference was handy for port information:
http://docs.openstack.org/trunk/config-reference/content/firewalls-default-ports.html
Implements: blueprint kube-heat-container
Change-Id: Ie4291a6c4c2b85a23a71fc0a003d9160bf0a32b8
|
|
Neutron is not yet ready, so use flat nova networking instead.
Change-Id: I4905f2a54af2c0c06cc8cf95d21f5831b02fbe5e
|
|
Kubernetes does not have a horizontal scaling feature that works per
node. A workaround is to use hostPort to cause the scheduler not to schedule
several replicationController replicas to each node. By doing so, only one
nova-compute is launched per node up to a total of 6 nodes which is the most
we can generate in testing.
Change-Id: I1621f15cf1ec502418b454300645b46bc796dc8b
|
|
Previously, the k8s neutron pod was pulling the image from
danehans instead of kollaglue. Additionally, the formatting was
incorrect causing kube not to pull the image at all.
Change-Id: I6f787a432ffb9cae404f915ac5228ddcb88e877c
|
|
|
|
Create the nova-novncproxy service for kubernetes.
Change-Id: Id8c0137a271faf832b736e6e1cda0b87bec7e5c2
|
|
Change-Id: Ia0b9057887bf34423546ca36346d9253ef4c90b9
|
|
|
|
|
|
This moves nova-ctr-base one level up and renames it nova-base, so that
we can share the same basic config between compute and controller pods.
Change-Id: I325f70c278744a1e1fe99b891e05c59c4248c55f
|
|
When running Docker, you can unknowingly use up a lot
of memory. This tool will make it easier to clean up
Docker.
Change-Id: Icfd780f12b01956093a2933dd484cde1e2d6d5bc
|
|
This was replaced by glance-pod.yaml.
Change-Id: I9249ae2721e375096fc42e1e8462a024c314118e
|
|
Based on
http://lists.openstack.org/pipermail/openstack/2014-January/004667.html,
there is confusion in the openstack community on how auth_uri in
nova.conf is supposed to interact with the other auth_* settings.
I've modified our config to use both for now.
Change-Id: I1433305e23d872cd773599c85053ba8f9aeb6145
|
|
|
|
|
|
|
|
The endpoints for Nova services needed to be properly created for ports
8773 (ec2/ec2) and 8774(nova/compute) and 8774(novav3/computev3).
Change-Id: I5e1931d2e7ea35f741ab73b070e24926a3763054
|
|
The nova-compute POD now starts and produces nearly correct output.
It may be that the libvirt container needs additional attention as it
is spitting out errors related to the firewall toolchain on the container.
Change-Id: I5bcd21c59f341494206a09e882631185ce66f336
|
|
Libvirt imports from fedora-rdo-base rather then nova-base, so no need
in generating an extra image.
Change-Id: I3ddd3aca54900686e3351de3dc11896347b14b6e
|
|
|
|
config-nova-controller.sh needs to set the nova database connection
string.
Change-Id: I82f61f1c003ef9068a664e2d4cafaab1b5c47a00
|
|
Change-Id: Ia01973ef10b1ab94a2cb5ddd9186adb916066beb
|
|
Not sure if mucking with iptables is safe, but appears required.
Change-Id: I766b0e61e247c47b4449c1ed2c204ddb8919a87d
|
|
|
|
|
|
|
|
Change-Id: Ia0f796b3a580c57b9f84390bae3b1012f99dcce0
|
|
Change-Id: I67f23c1fa987c33abef8607834dfface1de0fee2
|
|
Previously Kolla did not support Neutron. This patch provides
initial Neutron support by implementing neutron-server
functionality. It also creates a neutron-base image that
provides common config and packages for all Neutron-based
services.
Partially Implements: Blueprint Kubernetes Neutron Container
Change-Id: I2399a1331992fae0f387f01e5b5c1c1d34f0637d
|