Skip to content
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

Check Replacing of InitialBaseLines/OldestStream #23

Closed
WtfJoke opened this issue May 26, 2015 · 2 comments
Closed

Check Replacing of InitialBaseLines/OldestStream #23

WtfJoke opened this issue May 26, 2015 · 2 comments
Assignees

Comments

@WtfJoke
Copy link
Member

WtfJoke commented May 26, 2015

Thanks to a StackOverflow-User I found out, that there is some way to find the earliest baseline information of a component.

Following command can be used: lscm list baselines --components

Like that its probably possible to remove the "InitialBaselines" and the "Oldest Stream" options in the config.

This issue can be closed when either one of those or both options can be replaced or when a comment is written about the reason why this cant be accomplished.

@WtfJoke WtfJoke self-assigned this May 26, 2015
@WtfJoke
Copy link
Member Author

WtfJoke commented May 27, 2015

As far as my test went, it looks like both config-entries can be replaced by using this lscm list baselines command.

So far, didnt implemented anything

@WtfJoke
Copy link
Member Author

WtfJoke commented Jun 7, 2015

I almost finished implementing. Atm I am testing if everything still works as expected. I removed the oldeststream option completly but left the initialbaseline. It saves some time to configure it, because the determination takes some minutes, depending how many components the stream has.

@WtfJoke WtfJoke closed this as completed in 65b5d30 Jun 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant