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.

Sign up for GitHub

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

Jump to bottom

[feature]show the changes after action #115

Open
songbinliu opened this issue Oct 24, 2017 · 0 comments
Open

[feature]show the changes after action #115

songbinliu opened this issue Oct 24, 2017 · 0 comments

Comments

@songbinliu
Copy link
Contributor

After executing the actions successfully, kubeturbo should trigger a discovery request to exhibit the affect the action.

A concern of this feature is that: If there is a lot of actions, and the cost of discovery is high, then it may hurt the performance of kubeturbo.

Another way is that let OpsMgr decide when to send a discovery action: if there are too many actions are going on, OpsMgr should send the discovery action later.
pallavidn pushed a commit to pallavidn/kubeturbo that referenced this issue Mar 29, 2024
@shayne-lin
[TRB-41286] add p2p antiaffinity commodities (turbonomic#115)
ba0d4ae 
* [TRB-41286] add p2p antiaffinity commodities

* [TRB-41286] update antiaffinity commodites sold

* [TRB-41286] append commodity to commododiesBought
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@songbinliu