summaryrefslogtreecommitdiffstats
path: root/releasenotes
AgeCommit message (Collapse)AuthorFilesLines
2017-07-18Merge "Enable Neutron LBaaS Integration"Jenkins1-0/+4
2017-07-14Merge "Adds network/cidr mapping into a new service property"Jenkins1-0/+6
2017-07-14Enable Neutron LBaaS IntegrationAndrew Toth1-0/+4
Allows the configuration of the Neutron LBaaS agent. Change-Id: I4c29ece765ec9147cef9b4d74d30e3c4483c48ab Implements: blueprint lbaasv2-service-integration
2017-07-14Adds network/cidr mapping into a new service propertyGiulio Fidente1-0/+6
Makes it possible to resolve network subnets within a service template; the data is transported into a new property ServiceData wired into every service which hopefully is generic enough to be extended in the future and transport more data. Data can be consumed in service templates to set config values which need to know what is the subnet where a deamon operates (for example the Ceph Public vs Cluster network). Change-Id: I28e21c46f1ef609517175f7e7ee19e28d1c0cba2
2017-07-14Disable systemd-networkd & systemd-resolvedEmilien Macchi1-0/+9
Latest commits in puppet-systemd enabled by default systemd-networkd and systemd-resolved but we don't want to manage them for now in TripleO. MySQL and MongoDB services were managing some systemd resources so now we ensure that these 2 systemd services are disabled. In the future, we might want and activate these services and revert that patch but for now we want to disable them. Change-Id: I42c6c9b643a71a0fbb1768bbae91e8bfa916ea00 Closes-Bug: #1704145
2017-07-13Merge "Added OvS permission workaround for enabling DPDK"Jenkins1-0/+6
2017-07-13Merge "Allow to set Notification Driver to 'noop'"Jenkins1-0/+10
2017-07-13Merge "Add DeployedServerEnvironmentOutput"Jenkins1-0/+6
2017-07-12Merge "Switch from oslosphinx to openstackdocstheme"Jenkins1-2/+7
2017-07-11Allow to set Notification Driver to 'noop'Emilien Macchi1-0/+10
This patch does 2 things: * Configure messagingv2 as default driver for Oslo Notifications sent on RPC. * Allow users to choose between messagingv2 (default) and noop when we want to disable notifications (for example, when Telemetry is disabled). * Deprecate KeystoneNotificationDriver in favor of NotificationDriver. Change-Id: Ia547d7f4bfb51e7c45246b097b48fd86da231bd3 Related-Bug: #1701357
2017-07-10Add DeployedServerEnvironmentOutputJames Slagle1-0/+6
Add a new output, DeployedServerEnvionmentOutput, that can be used as the contents of an environment file to input into a services only stack when using split-stack. The parameter simplifies the manual steps needed to deploy split-stack. By default, the resource that generates the output is mapped to OS::Heat::None. implements blueprint split-stack-default Change-Id: I6004cd3f56778f078a69a20e93a0eba0c574b3db
2017-07-10Added OvS permission workaround for enabling DPDKSaravanan KR1-0/+6
The vhost sockets sockets are created with qemu permission, but ovs runs with root permission. In order to allow ovs to access vhost sockets reducing the ovs group permission from root to qemu. This is a temprovary workaround, until ovs fixes the permission issue. The script supports both ovs2.6 and ovs2.7 versions. Change-Id: I172956390c19fc9824bf7590cd48bfcf6201191b
2017-07-07Add in roles data validationAlex Schultz1-0/+8
With the merging of Iad3e9b215c6f21ba761c8360bb7ed531e34520e6 the roles_data.yaml should be generated with tripleoclient rather than edited. This change adds in a pep8 task to verify that the appropriate role files in roles/ have been modified to match how our default roles_data.yaml is constructed. Additionally this change adds a new tox target called 'genrolesdata' that will all you to automatically generate roles_data.yaml and roles_data_undercloud.yaml Change-Id: I5eb15443a131a122d1a4abf6fc15a3ac3e15941b Related-Blueprint: example-custom-role-environments
2017-07-06Switch from oslosphinx to openstackdocsthemeEmilien Macchi1-2/+7
As part of the docs migration work[0] for Pike we need to switch to use the openstackdocstheme. [0] https://review.openstack.org/#/c/472275/ Change-Id: Ib2b6afb7075c68fecf1fbeaf650a31a7494af49f
2017-07-04Enable Neutron LBaaS IntegrationRyan Hefner1-0/+4
Allows the configuration of the Neutron LBaaS agent. Implements: blueprint lbaasv2-service-integration Change-Id: Iae2bf7faeea93d5275994b2ee10f9bf863ed6152 Depends-On: Ieeb21fafd340fdfbaddbe7633946fe0f05c640c9
2017-06-30Merge "Add release note for generated sample environments"Jenkins1-0/+21
2017-06-28Disable swift middleware ceilometer pipeline by defaultPradeep Kilambi1-0/+5
This generates tons of unnecessary events when gnocchi uses swift backend. We end up filtering most of these anyway. So lets disable this so it doesn't put useless load. Also changing the default project to service as thats what gnocchi uses to authenticate with swift. Closes-bug: #1693339 Change-Id: I40f47d46fdb06f31a739b590bf653bca71e33f61
2017-06-27Merge "Adds service for OVS and enables ODL DPDK deployments"Jenkins1-0/+23
2017-06-27Merge "Add flag to enable/disable the HAProxy stats interface"Jenkins1-0/+4
2017-06-27Merge "Allows use of Mistral workflows during deployment steps"Jenkins1-0/+8
2017-06-27Merge "Enable DPDK on boot using PreNetworkConfig"Jenkins1-0/+8
2017-06-26Merge "Add VipMap output"Jenkins1-0/+5
2017-06-26Merge "Add split-stack environments"Jenkins1-0/+7
2017-06-26Merge "Add DeploymentSwiftDataMap parameter"Jenkins1-0/+6
2017-06-26Merge "Add os-collect-config data as an output"Jenkins1-0/+6
2017-06-26Allows use of Mistral workflows during deployment stepsGiulio Fidente1-0/+8
Introduces a general mechanism meant to allow for the execution of workflows during the deployment steps. Services can define workflow actions to be triggered during a step in the newly added service_workflow_tasks section. The syntax is: service_workflow_tasks: step2: - name: my_action_name action: std.echo input: output: 'hello world' Implements: blueprint tripleo-ceph-ansible Depends-On: If02799e7457ca017cc119317dfb2db7198a3559f Depends-On: Ibc5707f9f06266fe84ad1dd91dcb984157871d30 Change-Id: I36a642fbc2076ad9e4a10ffc56d6d16f3ed6f27a
2017-06-26Add flag to enable/disable the HAProxy stats interfaceJuan Antonio Osorio Robles1-0/+4
This was made configurable in a recent commit [1] So this flag makes it easier for deployers to use that functionality. [1] Ic68266eaf39d6803f7c3e299095578bbcfd63b88 Change-Id: Iffff20dcda53bc7237586dd240e581bcb0282844
2017-06-23Merge "Enable periodic task to discover cell hosts when ironic is used"Jenkins1-0/+6
2017-06-23Merge "Fix rpms being installed via DeployArtifactURLs"Jenkins1-0/+4
2017-06-23Enable periodic task to discover cell hosts when ironic is usedDmitry Tantsur1-0/+6
Starting with the Ocata release, bare metal nodes are no longer get recognized by nova automatically. To avoid forcing users into running nova manage command each time they enroll a node, we will have to allow enable the periodic task to do so. Change-Id: I8b0afac54dc9bd51dbe2ae4f237e4de50459be0f Closes-Bug: #1697724
2017-06-23Adds service for OVS and enables ODL DPDK deploymentsTim Rozet1-0/+23
In order to deploy OpenDaylight with DPDK we need to copy the DPDK config for OVS done in the neutron-ovs-dpdk service template, without enabling OVS agent for compute nodes. To do this correctly, we should inherit and openvswitch service which is a common place to set OVS configuration and parameters. Note: vswitch::dpdk config will be called in prenetwork setup with ovs_dpdk_config.yaml so there is no need to include that in the step config for neutron-ovs-dpdk-agent service or opendaylight-ovs-dpdk. Changes Include: - Creates a common openvswitch service template, which in the future will migrate to be its own service. - Renames and fixes OVS DPDK configuration heat parameters in the openvswitch template. - neutron-ovs-dpdk-agent now inherits the common openvswitch template. - Adds opendaylight-ovs-dpdk template which also inherits common ovs template. - Uses OVS DPDK config script to allow configuring OVS DPDK in prenetwork config (before os-net-config runs). This has an issue where hieradata is not present yet, so we have to redefine the heat parameters and pass them via bash. In the future this should be corrected. - Adds opendaylight-dpdk environment file used to deploy an ODL + DPDK deployment. - Updates neutron-ovs-dpdk environment file. Closes-Bug: 1656097 Partial-Bug: 1656096 Depends-On: I3227189691df85f265cf84bd4115d8d4c9f979f3 Change-Id: Ie80e38c2a9605d85cdf867a31b6888bfcae69e29 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-06-23Enable DPDK on boot using PreNetworkConfigSaravanan KR1-0/+8
DPDK has to be enabled on openvswitch on the boot before configuring the network as when the network uses DPDK ports OvS should be ready to handle DPDK. Enabled DPDK via PreNetworkConfig by checking if ServiceNames contains DPDK service. Implements: blueprint ovs-2-6-dpdk Closes-Bug: #1654975 Depends-On: I83a540336c01a696780621fb2b39486a6abf0917 Change-Id: I7af4534d91e67c94ba559b78b9ac6a001e639db3
2017-06-21Fixes incorrect glance api networkTim Rozet1-0/+3
The glance API network was being set to storage and it should be internal_api. Closes-Bug: 1699535 Change-Id: I75bc05aeab999f0e3eb3f4ebaceb276e888addc9 Signed-off-by: Tim Rozet <trozet@redhat.com>
2017-06-20Add release note for generated sample environmentsBen Nemec1-0/+21
This was missed in the original patch series, but this is a significant enough change that it needs to be communicated to users. Change-Id: Ibcfdde3cc544d152e78529fc57a63c7dc6592c4f
2017-06-19Merge "Add an example IronicConductor role"Jenkins1-0/+5
2017-06-16Merge "Make fernet max active keys configurable"Jenkins1-0/+5
2017-06-16Merge "Add templates to configure Ironic inspector"Jenkins1-0/+5
2017-06-16Merge "Pacemaker HA suport for OVN DB servers"Jenkins1-0/+3
2017-06-16Make fernet max active keys configurableJuan Antonio Osorio Robles1-0/+5
This will set the max_active_keys setting in keystone.conf, and furtherly we'll read this value from tripleo-common to do purging of keys if necessary. bp keystone-fernet-rotation Change-Id: I9c6b0708c2c03ad9918222599f8b6aad397d8089
2017-06-15Add VipMap outputJames Slagle1-0/+5
Add VipMap output to the top level stack output. VipMap is a mapping from each network to the VIP address on that network. Also includes the Redis VIP. This output facilitates deploying split-stack so you can feed the VIP addresses from VipMap as inputs into the services stack. implements blueprint split-stack-default Change-Id: I245920994613c9bd10801c25fa545267aa49b239
2017-06-15Add split-stack environmentsJames Slagle1-0/+7
Add 2 new environments to faciltate deploying split-stack: environments/overcloud-baremetal.j2.yaml environments/overcloud-services.j2.yaml The environments are used to deploy 2 separate Heat stacks, one for just the baremetal+network configuration and one for the service configuration. In order to keep Heat's view of the server's hostname consistent across the 2 stacks the 2 environments set the same HostnameFormat with "overcloud" as the stack name. implements blueprint split-stack-default Change-Id: I0b3f282c08af6fecea8f136908b806db70bada46
2017-06-15Add DeploymentSwiftDataMap parameterJames Slagle1-0/+6
The DeploymentSwiftDataMap parameter is used to set the deployment_swift_data property on the Server resoures. The parameter is a map of role names and node indexes to Swift container and object names to be used for storing deployment data. The parameter allows for using predefined Swift objects for storing deployment data instead of container/object names with generated uuid's from Heat. implements blueprint split-stack-default Depends-On: Ia07e9374a4b95bd0e74fc47fb9df4bf6ad096715 Change-Id: I471037de35e7f349d900462ec3ffb16fe2d6ebd9
2017-06-15Add os-collect-config data as an outputJames Slagle1-0/+6
Adds a new output, ServerOsCollectConfigData, which is the os-collect-config configuration associated with each server resource. This can be used to [pre]configure the os-collect-config agents on deployed-server's. Having the data available as a stack output is more user friendly than having to query several nested levels of stack resources, and then inspect resource metadata. implements blueprint split-stack-default Change-Id: Iaf062f1a72e2a9e4d97f84c67f72408a6b5cebfc Depends-On: I8acfd67cd8138d587cc362184c84a08134bf3157
2017-06-15Merge "Modify PreNetworkConfig config inline with role-specific parameters"Jenkins1-0/+11
2017-06-15Add an example IronicConductor roleDmitry Tantsur1-0/+5
Change-Id: I8dca09372a58b6dacbb8e65602e1b0bdb6c01ae7 Related-Blueprint: example-custom-role-environments
2017-06-14Merge "Update Panko api port"Jenkins1-0/+4
2017-06-14Update Panko api portPradeep Kilambi1-0/+4
The current port conflicts with trove. This is updated in puppet module. See related change: https://review.openstack.org/#/c/471551/ Change-Id: Iefacb98320eef0bca782055e3da5d243993828d7
2017-06-14Enable heat/puppet to manage the fernet keys and make it configurableJuan Antonio Osorio Robles1-0/+6
With the addition of the KeystoneFernetKeys parameter, it's now possible to do fernet key rotations using mistral, by modifying the KeystoneFernetKeys variable in mistral; subsequently a rotation could happen when doing a stack update. So this re-enables the managing of the key files by puppet. However, this is left configurable, as folks might want to manage those files out-of-band. bp keystone-fernet-rotation Change-Id: Ic82fb8b8a76481a6e588047acf33a036cf444d7d
2017-06-14Use KeystoneFernetKeys instead of individual parametersJuan Antonio Osorio Robles1-0/+10
This uses the newly introduced dict with the keys and paths instead of the individual keys. Having the advantage that rotation will be possible on stack update, as we no longer have a limit on how many keys we can pass (as we did with the individual parameters). bp keystone-fernet-rotation Change-Id: I7d224595b731d9f3390fce5a9d002282b2b4b8f2 Depends-On: I63ae158fa8cb33ac857dcf9434e9fbef07ecb68d
2017-06-14Merge "Add support for Cinder "NAS secure" driver params"Jenkins1-0/+5