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

implement rest call GET /plans #66

Closed
ypujante opened this Issue Jun 5, 2011 · 8 comments

Comments

Projects
None yet
3 participants
@ypujante
Member

ypujante commented Jun 5, 2011

Orchestration engine should expose the plans. Implement GET /plans

@li-mdubey

This comment has been minimized.

Contributor

li-mdubey commented Jul 21, 2011

Allow upgrading agents via REST

@ghost ghost assigned ypujante Jul 27, 2011

@ezbz

This comment has been minimized.

ezbz commented Jul 28, 2011

Any updates on this issue? I'd like to use this to prevent execution of automated tests on production machines while deployment is in progress (causes false negative test failures)

@ypujante

This comment has been minimized.

Member

ypujante commented Jul 28, 2011

I am currently working on it. Most likely ETA will be end of this week.

Yan

On Thu, Jul 28, 2011 at 6:46 AM, erezmazor <
reply@reply.github.com>wrote:

Any updates on this issue? I'd like to use this to prevent execution of
automated tests on production machines while deployment is in progress
(causes false negative test failures)

Reply to this email directly or view it on GitHub:
https://github.com/linkedin/glu/issues/66#issuecomment-1672716

@ezbz

This comment has been minimized.

ezbz commented Jul 28, 2011

Great, thanks!

ypujante added a commit that referenced this issue Jul 31, 2011

#83: fixed NPE by returning archived plan
#66: implements GET /plans and /xxx/executions

added unit tests

ypujante added a commit that referenced this issue Jul 31, 2011

ypujante added a commit that referenced this issue Jul 31, 2011

@ypujante

This comment has been minimized.

Member

ypujante commented Jul 31, 2011

Implemented in 3.2.0

@ypujante ypujante closed this Jul 31, 2011

@ezbz

This comment has been minimized.

ezbz commented Aug 2, 2011

I this supposed to give out only active plans or all plans?

I get back JSON containing the 3 most recent completed plans when there are no active ones.

Is there anyway to filter them to active only?

@ypujante

This comment has been minimized.

Member

ypujante commented Aug 2, 2011

Did you check the documentation? I would recommend reading this section: http://linkedin.github.com/glu/docs/latest/html/orchestration-engine.html#a-few-concepts

That being said, I think for your purpose you should use /deployments/current (instead of /plans) as the /plans* api are used mostly to create/execute a plan. The /deployments/current call will return exactly what you see when you go to the Plans tab in the console, so both currently running and completed plans that have not been archived.

Currently there is no way to ask for only running (which is something that I can add in the future), but you can do it 2 ways in the meantime:

  1. simply look at the status column of all entries returned.. it will say RUNNING if one is currently executing
  2. you can archive all current deployments (see documentation) which will obviously archive only the ones that are completed... so if you retrieve them right after issuing an archive you should get the list of all running ones (minus some race condition of course, which is why you should always do 1) no matter what...)

Hope this helps

@ezbz

This comment has been minimized.

ezbz commented Aug 2, 2011

oops (my RTFM, read the documentation previously didn't see it has been updated) thanks for the reply though /deployments/current gives me what I need. Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment