| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Kubernetes no longer uses 'kubecfg', but rather 'kubectl'.
Therefore, the way that pods and services are being created
needs to be changed.
In order to create a pod, the parameter 'kind' needs to be set
to 'pod' in the yaml file and the api version specified.
The stop script now reads from k8s/{pod,service,replication}/ in order
to stop all the started pods, services, and replication controllers.
Change-Id: Ibd39fa402e9df883df83272c3aefbb69009dfbd2
|
|
Previously, the k8s neutron-server service was using a selector
for the neutron pod that did not exist. The selector name defined
in the service yaml was more appropriate than the label (neutron)
defined in the pod yaml, so the label was updated in the pod
yaml.
Additionally, the naming convention for the neutron pod was
changed from neutron-controller to neutron-server to more
correctly depict the pods functionality.
Change-Id: I99465069bb3c37e7bf17c6d7a8f3559f87bf7140
|
|
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
|
|
The images are already updated, so this can be approved immediately
following the dependent implementation commit.
Change-Id: Ida3d6b5b64256a63652dffba9dff2365e3755286
|
|
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
|
|
Start all of the nova-controller services and pods with the start-all-pods
and start-all-services startup scripts
Change-Id: I47fe15d67ef177fbecf342357bff44cf2fdb5d9e
|
|
- use new yaml config files
- provide separate service- and pod- start/stop scripts
Change-Id: Iaff2a5b4d5a33467a9d10b10e9bd5c922eeed3aa
|
