Add an infoblox backend about ip-address-manager HOT 12 CLOSED

@maelk edit access has been added for [email protected]. if any others need please ping here.

from ip-address-manager.

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

from ip-address-manager.

/remove-lifecycle stale

from ip-address-manager.

+1

from ip-address-manager.

@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.

from ip-address-manager.

@mariusgrigoriu Can you please review the design doc and comment if needed?

from ip-address-manager.

Thanks. It's a good start. I will get some other folks on the team to review too.

from ip-address-manager.

Could you please give write access to [email protected] 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.

from ip-address-manager.

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

from ip-address-manager.

Stale issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle stale.

/close

from ip-address-manager.

Stale issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle stale.

/close

from ip-address-manager.

@metal3-io-bot: Closing this issue.

from ip-address-manager.