-
Notifications
You must be signed in to change notification settings - Fork 603
High: Introduces the docker agent to manage docker containers in an HA environment #370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
update monitor logic |
|
hi ,i used this RA in my pacemaker +corosync cluster. when i started resource sshd,then failed; |
|
@kikupotter Ah yes. I bet there is a bug in how I detect the image when you set the image:tag. I can fix this! It's great you're testing this agent. I'll fix the agent up, we'll both do some testing and then lets get this agent merged finally :) |
59ec814 to
635188f
Compare
|
@kikupotter Alright, the agent is updated. It should work for you now. Please checkout the new changes. |
39db9e5 to
faad7c8
Compare
By default containers started with the docker OCF agent are dynamically created on start and removed after stop. By using the 'reuse' option, containers will never be destroyed after stop, allowing the same container to be reused.
originally the default container name was the resource instance name prefixed with 'HA-'. This is confusing and unncessary. Now the container name defaults directly to the resource instance name with no prefix.
|
this agent should be ready at this point |
|
It is important that we make this agent available as soon as possible. Without any further feedback, I'm planning on merging this agent the beginning of next week. Oct 13th |
High: Introduces the docker agent to manage docker containers in an HA environment
Example:
'docker run --name="cluster-container" myimage sleep 10000'
would be executed and managed by the docker HA agent with these options
OCF_RESKEY_run_cmd="sleep 10000"
OCF_RESKEY_image="myimage"
OCF_RESKEY_container="cluster-container"
If the image did not exist locally and you want the image to be dynamically pulled from the docker registry on startup, the 'allow_pull' option lets this happen.
Also, custom 'docker run' args can be set using the 'run_opts' option.
-- Vossel