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
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
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
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
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
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
Nova imports python-cinderclinet, which is not present by just
installing python-nova-api. Hard yum-install it until upstream
fixes packaging.
Change-Id: I3187721d3eda7ce81da9540469fcc93b93560d3b
remove nova-controller image, which is not meant to be started directly.
add required NEUTRON_SHARED_SECRET environment variable.
Change-Id: Id671c5473db8e6e222b16ccdfd9eaedc872c60fa
- correct typos/syntax errors in configuration scripts
- make config script consistent with other images
- do not create keystone entries in base image script
Change-Id: I42986fe1b9c80c5b0735fd70294bce1a6223a3ca
