summaryrefslogtreecommitdiff
path: root/docker/nova-base
AgeCommit message (Collapse)AuthorFilesLines
2015-05-06Add a novnc container running the novnc-proxy.Harm Weites1-6/+0
All VNC-specific configuration bits are moved from nova-api-base to nova-compute and the new nova-novncproxy and nova-consoleauth containers. The compose specification has been updated to reflect this. A future patch will make the desired backend configurable (spice/vnc). Change-Id: I8b64abf125fd1ecd7d3463515e3717dd9bd60420 Blueprint: novnc-container
2015-05-06Change nova net config to work properly with Neutron for Juno and laterSteven Dake1-6/+6
Change nova networking config to work properly with Neutron Juno and later. Partially-implements: blueprint port-kilo Change-Id: I18c324c34b4c3af8526d32b3e42f426ec519750b
2015-05-06Port to icehouseSteven Dake1-1/+1
This represents making build-docker-images --release build with the icehouse tag and causes docker-compsoe to pull from the icehouse tag. Partially-implements: blueprint port-kilo Change-Id: I66b2c39abc55c0f47152dd90e696fc46b9c58f50
2015-05-06Setup nova networking properly for IcehouseSteven Dake1-6/+6
This sets up nova networking properly to work with Neutron in the Icehouse release. Partially-implements: blueprint port-kilo Change-Id: I0d37411c61d0d705d1ddf39c25c6610ea04f56f1
2015-04-27Change the default shell to bashChen Zhiwei1-1/+1
Unify the shell to bash in all Kolla scripts. Change-Id: Ib9591b2f8f344eb88455c5e9b7ecf2164fb5960a Implements: blueprint use-bash-shell
2015-04-14Neutron doa in current formSteven Dake1-2/+2
The nova-config.sh script was exiting because of incorrect shell syntax. The correct syntax for a regex search is [[ haystack =~ needle ]]. The .*needle.* is unnecessary. I think this shell script exited because a period was missing. Change-Id: I3aca5e0729eb5fedbe9ecb4d75ed85d5a1c7815a
2015-04-13Removes check_required_vars for Log FilesDaneyon Hansen1-1/+1
Previously, check_required_vars was requiring log file variables to be set in openstack.env. This would cause an error when starting nova/neutron containers that used default (blank) log file settings. Since the log files are not required for the services to start, the default log files are left blank (without a value in the K/V pair). This patch removes the log_file variable for check_required_vars in each nova/neutron script. Change-Id: I169baab28f63a0e0ae06c8aef21b5e8d3155bdda
2015-04-13Adds Neutron Agents SupportDaneyon Hansen1-1/+5
Previously, the agents ran in seperate containers. Since some of the agents create and use network namespaces, runnning them in seperate containers has become a challenge. This patch adds neutron agent support in a single container. Partially Implements: blueprint compute-operation-neutron Change-Id: If4f893abd50d90b58e8435ec2659870dce36951c
2015-04-10Adds neutron-server to neutron container-setDaneyon Hansen1-0/+9
Adds neutron-server components of the neutron container set. Partially Implements: blueprint compute-operation-neutron Change-Id: I63525ae85f4ead4e010cdb9b6bc8059bb9d252e7
2015-04-07Adds Initial Logging SupportDaneyon Hansen1-5/+7
Previously, logging was hard coded into the nova and neutron containers. This patch creates two common params for logging: DEBUG_LOGGING VERBOSE_LOGGING and sets default values of verbose=true and debug=false. This patch implements logging for Nova and Neutron. Add'l OS service config scripts and images will need to be updated to use the logging params. Change-Id: I03d48005d5b4789aa3c519879a20d963ef1cbaa3
2015-03-25Extends Nova Metadata Service Parameterization and CompositionDaneyon Hansen1-2/+4
Previously, nova enabled_apis was hard coded and metdata_host was using PUBLIC_IP param instead of exposing an individual param. Extending these params and creating a separate compose yml that includes compute/libvirt/network/api is required to support nova network multi_host. Additional details can be found here: http://docs.openstack.org/admin-guide-cloud/content/section_metadata-service.html Change-Id: I5d417a0ee460f8ad9b2982fe83d63ab57013918e
2015-03-24Refactor nova-networkDaneyon Hansen1-2/+2
Previously, eth0 was set as the nova flat interface. This interface is used to bridge VM traffic between instances and should not have an IP. It's a problem when you associate an interface with an IP to the FLAT_INTERFACE. Change-Id: I38c516094430e2d55b1b4c047a1bbcfe711a2dff
2015-03-06Merge "Allow changing base image"Jenkins1-1/+1
2015-03-02Allow changing base imageMartin André1-1/+1
By changing the PREFIX variable in the .buildconf one is now able to build docker images from different bases. For example, add the following line to your .buildconf file to build CentOS based images: PREFIX=centos-rdo- Default base image is Fedora. For now only RH family is supported. Additionally, changing the namespace either with the NAMESPACE variable in .buildconf or via --namespace commandline option now changes the source namespace as well from the default kollaglue one. Implements: blueprint multi-baseos Co-Authored-By: Steven Dake <stdake@cisco.com> Change-Id: I3964cd2292789ea883a1f2d2738a5731a4fff49b
2015-02-27A functional libvirt + nova_compute + nova_networkSteven Dake1-3/+6
This imports sdakes' nova-docker codebase to show that atomic upgrades work atleast with nova networking. This has many corrections. For more details read: http://sdake.io/2015/01/28/an-atomic-upgrade-process-for-openstack-compute-nodes/ Implements-blueprint: blueprint libvirt-container Partially-implements; blueprint container-set-compute-operation-nova Change-Id: I858ea113c5656b6da5d2fd13502fecdbd085c8da
2015-01-21Check for nova DB availability in dependent containersMartin André1-1/+0
When nova-api start and the nova database hasn't yet been created, it would create it itself, preventing the migration in nova-conductor to run and making it unable to start. This commit ensures that nova-api container will not try to steal nova-conductor's job of creating the nova database. Nova-scheduler reacts differently to the missing database and simply exits with a backtrace. This commit also prevents nova-scheduler to start when the nova database cannot be found. Change-Id: Ib6f7521151815faa7a26ec1d170df5a1cdb7fd63 Related-Bug: #1335804
2015-01-19Cleanup required variables checks for all containersMartin André1-2/+5
This allows Kubernetes to reschedule containers in case a required variable is missing, for example when the Kubernetes pod is started before the service. The checks were cleaned using the following method: * remove duplicates * remove check for variables that get a default value in the same file * check for all variables used in the file * check for required services when it is obvious. Change-Id: Ib7e0530c410c61f828d36efe8925a20dc9781eab
2014-12-03Prefer the use PUBLIC_IP over MY_IPMartin André1-2/+2
PUBLIC_IP is more descriptive that MY_IP, it should be used consistently across Kolla. Change-Id: Iff6ae903e794ec84a40a300b36512422b7a81f71
2014-11-25Adds Neutron Networking SupportDaneyon Hansen1-0/+25
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
2014-11-17Adds support for Functional Nova-NetworkDaneyon Hansen1-18/+0
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
2014-10-22Update MAINTAINER in Dockerfiles to Kolla ProjectLars Kellogg-Stedman1-1/+1
Remove individual MAINTAINER information from Dockerfiles. Change-Id: I777df5cde049599dc786176e1d5b4b9597f0b334
2014-10-21workarounds for nova networkingversion-m1Lars Kellogg-Stedman1-1/+1
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
2014-10-21Only create bridge in nova-networkSteven Dake1-3/+1
Not all nova services need a bridge. Remove bridge creation from nova-base config and place in nova-network specifically. Change-Id: Ia78c65a4661cd95112dca7ffdc1e839d4f648d52
2014-10-20Change to using flat nova networking from neutronSteven Dake2-7/+22
Neutron is not yet ready, so use flat nova networking instead. Change-Id: I4905f2a54af2c0c06cc8cf95d21f5831b02fbe5e
2014-10-17introduce a common base for compute and controllerLars Kellogg-Stedman3-0/+108
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
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 20:34:15 +0000