Bug 1029410
Summary: | Can not move an OpenShift role to an host that already contains other OpenShift components. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> |
Component: | Node | Assignee: | Luke Meyer <lmeyer> |
Status: | CLOSED WONTFIX | QA Contact: | libra bugs <libra-bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 2.0.0 | CC: | bleanhar, libra-onpremise-devel |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-05-01 20:42:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Johnny Liu
2013-11-12 11:07:31 UTC
Hmmm, looks like this menu is still useful, when user want to customize roles to separate machines with "-a" option, user must select this "move role" menu. That means this "move role" menu is available only when move a role to new host, is not proper when move a role to an existing host. The wizard should be refined after user select "move role" menu. Just like this: Which role do you want to move to a different host?: 1. Broker 2. MsgServer 3. DBServer 4. Node Type a selection and press <return>: 4 Which host should no longer include the role?: 1. msg (MsgServer, Node) 2. node (Node) Type a selection and press <return>: 1 Select a host to use for this role:: 1. Create a new host Type a selection and press <return>: 1 This should be working reasonably well now. I'll give it a try myself - lot of changes recently. It is fine to move roles between hosts as long as they haven't actually been installed yet. I don't think oo-install yet has the logic in place to keep you from modifying hosts that *have* been installed, but that's coming. Seem move operation have some issue now, pls refer to BZ#1032476. (In reply to Luke Meyer from comment #4) > This should be working reasonably well now. I'll give it a try myself - lot > of changes recently. > > It is fine to move roles between hosts as long as they haven't actually been > installed yet. I don't think oo-install yet has the logic in place to keep > you from modifying hosts that *have* been installed, but that's coming. To be more clear, here is a scenarios. 1. Set up env, already installed broker, db, msgserver, node on different vms. 2. Trying to move node role to broker role. You mean in the future this scenarios is not allowed? Right, I don't think we're ever going to go to the trouble to literally remove/disable a component that has been installed on a host and put it on another instead. Once a host has completed installation and configuration, the intention is that oo-install will not modify it, although I don't know how well that's implemented yet. Perhaps we need to adjust the language because the "move" here occurs strictly in the deployment configuration; i.e. "we started oo-install defaulting to everything on one host, but actually you want to separate out activemq to a different host" - but this is before anything is deployed. After you start deploying the components, the only thing that should be allowed is adding nodes. So, just to be clear now... everything currently works as designed. * You can successfully move roles between hosts *in the oo-install configuration* * Right now, I don't think the code distinguishes between hosts that have been installed already and those that haven't, but the intent is that in the future, changes to configuration for installed hosts won't be allowed. For now, hopefully people don't expect to do that. So it needs to be clear that "move" just means changing the configuration of what you intend to install... not updating existing installed hosts. So this: 2. Move an OpenShift role to a different host ...should perhaps be re-worded to something like: 2. Reassign a not-yet-installed role to a different host Truthfully, I can't think of a clear, concise way to get this concept across in a way that will correct someone who assumes, as you did, that we're talking about manipulating already-installed hosts. In any case, I'm going to reduce the severity on this and think about addressing it after 2.0.1. |