summaryrefslogtreecommitdiff
path: root/k8s
AgeCommit message (Collapse)AuthorFilesLines
2014-10-21Merge "Implement containers for heat-engine and heat-api"Jenkins2-10/+17
2014-10-20Implement containers for heat-engine and heat-apiJeff Peeler2-10/+17
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
2014-10-20Change to using flat nova networking from neutronSteven Dake1-1/+3
Neutron is not yet ready, so use flat nova networking instead. Change-Id: I4905f2a54af2c0c06cc8cf95d21f5831b02fbe5e
2014-10-20Use hostPort to lock 1 nova-compute/nova-network per nodeSteven Dake1-3/+7
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
2014-10-17Fixes k8s neutron pod image source and formattingDaneyon Hansen1-18/+18
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
2014-10-17Merge "Add nova-novncproxy as a kube service"Jenkins1-0/+7
2014-10-17Add nova-novncproxy as a kube serviceRyan Hallisey1-0/+7
Create the nova-novncproxy service for kubernetes. Change-Id: Id8c0137a271faf832b736e6e1cda0b87bec7e5c2
2014-10-17Merge "Adds Neutron Server Support"Jenkins2-0/+37
2014-10-17remove glance-pod.jsonLars Kellogg-Stedman1-68/+0
This was replaced by glance-pod.yaml. Change-Id: I9249ae2721e375096fc42e1e8462a024c314118e
2014-10-17Merge "Make nova-compute work properly with libvirt"Jenkins2-2/+2
2014-10-16Make nova-compute work properly with libvirtSteven Dake2-2/+2
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
2014-10-16Run nova-api as privileged so it can muck with iptablesSteven Dake1-0/+2
Not sure if mucking with iptables is safe, but appears required. Change-Id: I766b0e61e247c47b4449c1ed2c204ddb8919a87d
2014-10-16Adds Neutron Server SupportDaneyon Hansen2-0/+37
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
2014-10-16fix nova-controller podLars Kellogg-Stedman1-13/+6
remove nova-controller image, which is not meant to be started directly. add required NEUTRON_SHARED_SECRET environment variable. Change-Id: Id671c5473db8e6e222b16ccdfd9eaedc872c60fa
2014-10-14Merge "nova-compute-service doesn't expose a port"Jenkins1-5/+0
2014-10-14Convert nova-compute-replication to yamlSteven Dake2-66/+37
Yaml is the future - json is the past \o/ Change-Id: I36a9cbf8db034d1e8deba040a22e556d791c65ed
2014-10-14nova-compute-service doesn't expose a portSteven Dake1-5/+0
AFAIK the service files are only for services with ports exposed. Since nova-compute doesn't expose a port, kubecfg returns an error when attempting to register it: F1014 17:06:34.329482 32317 kubecfg.go:395] Got request error: service "novacompute" is invalid: port: invalid value '0' Change-Id: I4d9f8d50d538f42d520f3d9437ab32aa6a226d2b
2014-10-14Merge "Add kube services"Jenkins3-0/+21
2014-10-14Add kube servicesRyan Hallisey3-0/+21
Add kubernetes services so that the nova controller can use the ports 8773, 8774, and 8775, which correspond with nova-api, nova-ec2-api, and metadata-api. Change-Id: Idb083e2e0745c6587f9fa4f01a068727a435c2c6
2014-10-14Update nova-controller's container portsRyan Hallisey1-7/+3
The previous values were just stand in values. The new ports support nova-api, ec2 api, and metadata api. Change-Id: I330575d9b53b69bcacc61061b271252e61e64d4b
2014-10-13add kubernetes volumes to glance podLars Kellogg-Stedman2-26/+43
Use kubernetes volumes for data storage rather than placing data directly on the container filesystem. That provides a starting point for thinking about persistent data -- one could replace the emptyDir source with an explicit path via hostDir, and then you would have storage that would persist over a container delete/re-create. Change-Id: Ifade1cb2ba546e5e0207c3d8c84965dc2195716b
2014-10-13keystone pod needs KEYSTONE_DB_PASSWORDLars Kellogg-Stedman1-0/+2
if we want to be able to run multiple keystone container instances, the password cannot be generated as part of the container boot process; it must be passed it as part of the pod template. Change-Id: Idd1b50b6bdb3788eec316bf22fb954f5ecbaa4be
2014-10-13glance images need keystone passwordLars Kellogg-Stedman1-0/+4
glance keystone password cannot be generated during container boot because we need the same value in both the -api and -registry containers. Change-Id: I4099ca19bd7433ff2a75ffba3a1597eff0be2ce4
2014-10-13Merge "Rename nova-libvirt to libvirt"Jenkins1-0/+10
2014-10-13Rename nova-libvirt to libvirtSteven Dake1-1/+1
nova-libvirt doesn't make sense as a name since nova is not the upstream of libvirt Change-Id: I3e396b5a0897649312f3552a791c82429013f5ae
2014-10-13convert all configs to yamlLars Kellogg-Stedman31-467/+291
Change-Id: I7edbd3a59007d9e2f7f5ab5e4c020eeb58d03dd3
2014-10-13Merge "Add a replicationController for nova-compute so it runs on each minion"Jenkins1-0/+66
2014-10-13correct various issues with glance images and configsLars Kellogg-Stedman1-56/+64
- update keystone endpoints/user on boot (to avoid problems caused by, e.g., a stale password or invalid endpoint urls) - require GLANCE_DB_PASSWORD and GLANCE_KEYSTONE_PASSWORD in the environment, since we start multiple containers Change-Id: I31214b81280ed34409f92e79003c1116d5737d2e
2014-10-08Add a replicationController for nova-compute so it runs on each minionSteven Dake1-0/+66
We want the nova-compute controller to run on each minion Change-Id: If0355034927e195d1dd5482dab1026418185e9c6
2014-10-08Modify rabbitmq pod to point to right imageSteven Dake1-1/+1
The image location for rabbitmq was incorrectly pointing at Lars private repository. Change it to point to the global kollaglue repo. Change-Id: Ib4fd84db9410fa7057730ff74be2acc0babfa438
2014-10-07Reorganize k8s structureSteven Dake16-0/+527
All services go to TLD/k8s/service All pods go to TLD/k8s/pod Change-Id: Iad2977a9f0cd5f430c4e0a566846bf4681618379
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 18:27:49 +0000