Comments (10)
OK, those things all make sense at first glance. Thanks for adding the details!
from dev-scripts.
What sorts of configuration changes do you anticipate needing?
from dev-scripts.
For downstream testing, we are setting the following:
allowUnsupported: true
so that we can install private versions of Ceph- The rook versions are changed to specify the source of the containers (again, these are non-public)
- Both
ROOK_ALLOW_MULTIPLE_FILESYSTEMS
andROOK_HOSTPATH_REQUIRES_PRIVILEGED
- The ceph container version is also changed to point to a private one
Some of these, like the container versions change often, while others are always set.
We also want to keep our validation as close as possible to what Rook is providing with their sample YAML files, so that we can catch regressions as soon as we rebase from upstream.
from dev-scripts.
There are a lot of things in this repo, and I'd like to understand the future of dev-scripts.git . Is is a long-term project? Will non-developers eventually use this?
from dev-scripts.
There are a lot of things in this repo, and I'd like to understand the future of dev-scripts.git . Is is a long-term project? Will non-developers eventually use this?
We are using this repository as a work space while we figure out what the installer needs to do. As that logic is ironed out, we are moving it into the go-based installer in https://github.com/openshift-metalkube/kni-installer. Eventually that fork of the openshift installer will be merged back, and we won't need much or any of this.
For now, these tools are the canonical way to set up a cluster, regardless of its purpose.
from dev-scripts.
@ktdreyer yeah I named the repo dev-scripts deliberately, to indicate this is a developer test-harness/prototype, and as @dhellmann says most logic will ultimately end up in kni-installer, openshift-install, or in a few cases the facet wrapper API (this should in general call kni-installer, but I think there will be a few additional cases like node auto-discovery which may not fit well into kni-installer's normal workflow, at least for now).
from dev-scripts.
Thanks Doug. I opened #265 to capture this. (Like Steve mentioned, it would be helpful to point new users at the facet repo as well.)
from dev-scripts.
Does this issue need to remain open? It sounds like PRs should just be submitted adding configuration to the rook setup as needed?
from dev-scripts.
I think this issue should remain open until a PR is submitted. For the reasons listed above, it is crucial to avoid hard-coding versions and sources for rook, ceph, and its containers. We have shifted focus to other targets for installation and I can't provide a PR to address this problem.
from dev-scripts.
rook is going to be dropped from dev-scripts, see #603 -- as you said, focus for installation will not be this PoC / demo integration, so best not to spend more energy on it
from dev-scripts.
Related Issues (20)
- A cluster name that exceeds 14 characters causes an error during bridge creation HOT 5
- error TASK [libvirt : Create libvirt networks] HOT 5
- Deployment throws error with config OPENSHIFT_VERSION=4.5.0
- FATAL failed to fetch Master Machines: failed to load asset "Install Config": invalid "install-config.yaml" HOT 3
- Error when chown runs and user name differs from group name
- Use openshift-install coreos print-stream-json HOT 3
- Allow creating a custom number of extra disks HOT 2
- Align Ansible version to metal3-dev-env one HOT 2
- libvirt net ostestbm won't start after reboot HOT 2
- make agent fails with error AGENT_E2E_TEST_SCENARIO is missing
- lxml install needs devel packages for arm64
- The Cluster creation fails with Error: could not contact Ironic API: context deadline exceeded HOT 6
- openshift-sdn support is about to be removed from the installer
- Wrong command in ./01_install_requirements.sh script HOT 6
- Make sure NetworkManager-initscripts-updown is installed on RHEL9 host.
- Failure to create dualstack v6 primary cluster
- Error: failed to dial libvirt: dial unix /var/run/libvirt/libvirt-sock: connect: no such file or directory HOT 3
- 01_requirements.sh errors when `go` is pre-installed.
- Suspect yq doesn't always successfully install on 01_install_requirements.sh L100 HOT 3
- RHEL9: libvirt-sock file not found error during cluster bringup
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dev-scripts.