Bug 867063
Summary: | JBoss app's README can cause some confusion. Some user feedback provided | ||
---|---|---|---|
Product: | OKD | Reporter: | Nam Duong <nduong> |
Component: | Containers | Assignee: | Bill DeCoste <wdecoste> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 2.x | CC: | jhou, jofernan |
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: | 2012-12-19 19:27:19 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
Nam Duong
2012-10-16 16:32:37 UTC
READMEs updated Added line in template README describing and pointing to the markers README https://github.com/openshift/origin-server/pull/841 (In reply to comment #3) > Added line in template README describing and pointing to the markers README > > https://github.com/openshift/origin-server/pull/841 Sorry I didn't make it clear, I mean the contents for deployment markers are removed in current fix. I think they are helpful, so I want to make sure whether they are removed intentionally Thanks! =========================removed contents============================== The filesystem deployment scanner in AS 7 and later works differently from previous JBoss AS releases. The scanner will no longer attempt to directly monitor the deployment content and decide if or when the end user wishes the content to be deployed. Instead, the scanner relies on a system of marker files, with the user's addition or removal of a marker file serving as a sort of command telling the scanner to deploy, undeploy or redeploy content. The marker files always have the same name as the deployment content to which they relate, but with an additional file suffix appended. For example, the marker file to indicate the example.war should be deployed is named example.war.dodeploy. Different marker file suffixes have different meanings. The relevant marker file types are: .dodeploy -- Placed by the user to indicate that the given content should be deployed into the runtime (or redeployed if already deployed in the runtime.) .deploying -- Placed by the deployment scanner service to indicate that it has noticed a .dodeploy file and is in the process of deploying the content. This marker file will be deleted when the deployment process completes. .deployed -- Placed by the deployment scanner service to indicate that the given content has been deployed into the runtime. If an end user deletes this file, the content will be undeployed. .faileddeploy -- Placed by the deployment scanner service to indicate that the given content failed to deploy into the runtime. The content of the file will include some information about the cause of the failure. .undeploying -- Placed by the deployment scanner service to indicate that it has noticed a .deployed file has been deleted and the content is being undeployed. This marker file will be deleted when the undeployment process completes. .undeployed -- Placed by the deployment scanner service to indicate that the given content has been undeployed from the runtime. If an end user deletes this file, it has no impact. Yes, that content was removed intentionally. Users should NOT be using those files. This was the cause of half the confusion from the user. All of the .* files are handled behind the scenes by us and can cause problems if directly used by the user. Verified on devenv_2445 Steps: 1. Create a jbossas/jbosseap/jbossews applications 2. Check README in app root directory READMEs have been updated |