Add an infoblox backend
maelk opened this issue · 12 comments
User Story
As a user I would like to be able to use infoblox to manage my IP addresses allocation to integrate with my current solutions.
Detailed Description
Some investigation is needed to figure out if it would be possible to use infoblox as a backend for the IP address generation. If possible, a design proposal should be submitted to propose the changes needed to do that. Then implementation could follow. This is a high level issue to track work in this area.
/kind feature
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle stale
/remove-lifecycle stale
+1
@maelk @dhawal55 @abhinavnagaraj I've started a rough design doc here. Would appreciate any inputs.
https://docs.google.com/document/d/1gfJleq34l-ZTOKJ30UYSQqmlTj7FHqEyMF3q4_W4zMc/edit?usp=sharing
Please comment and then I can add you as editors.
@mariusgrigoriu Can you please review the design doc and comment if needed?
Thanks. It's a good start. I will get some other folks on the team to review too.
Could you please give write access to metal3-dev@googlegroups.com for edit rights ? (or at least suggestions)
This is a nice first step with clear user stories and goals. I think we should take the discussion further with the design part, in order to make a mechanism that would allow us to plug more than the infoblox backend.
@maelk edit access has been added for metal3-dev@googlegroups.com. if any others need please ping here.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle stale.
/close
Stale issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle stale.
/close
@metal3-io-bot: Closing this issue.
In response to this:
Stale issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle stale./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.