This repository has been archived by the owner on Oct 31, 2024. It is now read-only.
Feature/manila #7
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Feature/single signon
upload-puppet-modules ends up causing problems because of the way it places patched modules in /etc/puppet/modules.
we're currently carrying the patch locally (in patches/tripleo-heat-template), but the new packages should show up shortly.
going forward, eth0 and eth1 (which on our physical machines will be two 1Gb interfaces) are no longer used. Move storage to eth3, and everything else stays on eth2.
with the new network configuration, the only route to the repository server @ 10.13.96.252 is via the default route, which unfortunately is a "public" address that cannot reach our internal networks. This adds a static route out eth2 to the repository server.
The default DeployArtifacts feature in Tripleo [1] is not able to cleanly install patched puppet modules. This commit introduces a new service explicitly for patching puppet modules that ensures any existing module is completely removed before installing the replacement. [1]: http://hardysteven.blogspot.com/2016/08/tripleo-deploy-artifacts-and-puppet.html
this better integrates the feature/patch-puppet changes into the configuration and adds a service to create the keystone federation resource (identity provider, mapping, and protocol) during the deploy.
this better integrates the feature/patch-puppet changes into the configuration and adds a service to create the keystone federation resource (identity provider, mapping, and protocol) during the deploy.
we can't use host_prep_tasks for creating the keystone resources because the prep tasks run before keystone is available.
these are executable ansible playbooks that I've been using while testing things out.
With this pull request, federated logins work properly on a fresh installation.
these prevents a longer failure mode if you try running this script when you have overcloud credentials loaded.
this commit includes tooling to build patched Docker images, including a patched version of the Horizon image which contains the MOC theme for Horizon.
Support a custom Horizon theme.
by cloning the theme repository through a pre-build hook, we can avoid either (a) missing changes due to docker caching or (b) unnecessary rebuilds with --no-cache.
teach build-images about --date and --force-revision
this adds the roles directory from tripleo-heat-templates to our local repository
- move templating of deploy.yaml into makefile - add rules for generating custom roles - add rules for generating html version of README
this adds three new roles: - ControllerDeployedServer - ComputeDeployedServer - NetworkerDeployedServer
Feature/custom roles
larsks
reviewed
Jul 17, 2018
| # Manila deployment documentations suggests there should be a bridge for storage network interface | ||
| # https://docs.openstack.org/tripleo-docs/latest/install/advanced_deployment/deploy_manila.html | ||
| # If a dedicated interface (eth3) is used for storage network, update storage interface for each node type ti use bridge | ||
| # May not need this since Ceph traffic aready goes over storage network? |
There was a problem hiding this comment.
I think we're still going to need the bridge because, based on your earlier comment, we need to be able to expose the storage network to tenants as a provider network. This means we're going to need br-storage on the compute nodes, and then a corresponding bridge mapping in the deploy configuration, and then we'll need to create the necessary provider network post-deploy. I already have a request from rado to enable a few additional provider networks, so I will try to get to that relatively soon.
There was a problem hiding this comment.
Would we need it on the controller nodes too?
There was a problem hiding this comment.
I would guess maybe not, but I will have to take a look at the Manila documentation for a more authoritative answer.
There was a problem hiding this comment.
Docs suggested configuring the interface this way on each type of node where tennants needed access to the storage network.
larsks
force-pushed
the
master
branch
3 times, most recently
from
47d118a to
f3725e0
Compare
larsks
force-pushed
the
master
branch
2 times, most recently
from
b3eaf1f to
3a80d25
Compare
larsks
force-pushed
the
master
branch
8 times, most recently
from
c6026fe to
8d44a66
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enabling the manila environment files should allow it to run on top of the existing ceph configuration