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

Feature: Create an API Interface #18

Open
gyptazy opened this issue Jul 12, 2024 · 1 comment
Open

Feature: Create an API Interface #18

gyptazy opened this issue Jul 12, 2024 · 1 comment
Assignees
Labels
Milestone

Comments

@gyptazy
Copy link
Owner

gyptazy commented Jul 12, 2024

General

It would be cool to have an API Interface providing multiple different endpoints and returning JSON content for further parsing. Therefore, it would great to obtain the best optimal new node for placing new VMs (which could be easily used by Ansible, Terraform etc.,) and also providing the current and planned statistics of nodes and VMs.

It should at least contain the following ones:

Option Endpoint
Best new node /cluster/placement/nextnode
Current VM overview /cluster/placement/statistics/current/vms
Current Node overview  /cluster/placement/statistics/current/nodes
Rebalanced VM overview /cluster/placement/statistics/rebalanced/vms
Rebalanced Node overview /cluster/placement/statistics/rebalanced/nodes

Tasks

  • Validate for dependencies
  • Integrate web server
  • Integrate API Endpoints
  • API should be optional (should also run without and without dependencies)
@gyptazy gyptazy added this to the Release 1.1.0 milestone Jul 12, 2024
@gyptazy gyptazy self-assigned this Jul 12, 2024
@gyptazy
Copy link
Owner Author

gyptazy commented Jul 26, 2024

Instead of creating an own API interface by using http.server and doing everything on my own, I probably should consider switching to a framework which might offer more benefits and also a better maintenance in long-term.

I closed the idea PR with the old solution and will stick with a framework solution after releasing version 1.0.0.

gyptazy added a commit that referenced this issue Aug 9, 2024
  * Add rolling updates feature.
  * Add own (ProxLB) API integration.

Fixes: #39
Fixes: #18
gyptazy added a commit that referenced this issue Aug 9, 2024
  * Add rolling updates feature.
  * Add own (ProxLB) API integration.

Fixes: #39
Fixes: #18
gyptazy added a commit that referenced this issue Aug 9, 2024
  * Add rolling updates feature.
  * Add own (ProxLB) API integration.

Fixes: #39
Fixes: #18
gyptazy added a commit that referenced this issue Aug 9, 2024
  * Add rolling updates feature.
  * Add own (ProxLB) API integration.

Fixes: #39
Fixes: #18
gyptazy added a commit that referenced this issue Aug 10, 2024
  * Add rolling updates feature.
  * Add own (ProxLB) API integration.

Fixes: #39
Fixes: #18
@gyptazy gyptazy modified the milestones: Release 1.2.0, Release 1.1.0 Sep 11, 2024
@gyptazy gyptazy modified the milestones: Release 1.1.0, Release 1.2.0 Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant