You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Goals
- Use API Integration to communicate with BlueCat address manager (IPAM) to share bi-directional support information:
Background and strategic fit
ManuLife has identified this integration as a business need. Other customers have asked in the past, but we now have a point of contact to work with from BlueCat.
Server - https://bluecat
admin/admin
Assumptions
- Customers will provide information as needed for the integration and build out detailed use case
- Lumeta will have access to the credentials needed to communicate with the BlueCat server
- The APIs available will return the data we are looking to surface
Requirements
| # | Title | User Story | Importance | Notes |
|---|
| Connect to the management server | Use Lumeta to retrieve information from the server via API | Must Have | - Need to have proper credentials and achieve handshake
|
| Configuration | Configuration will be implemented in Integrations section of the application. | Must Have |
|
| Configuration screen | This screen will allow the user to input needed configuration values to connect to and poll the BlueCat management server (server, credentials, polling interval) | Must Have |
|
| Configuration form input validation | All fields need to perform input validation to ensure proper input types. Form fields need to be able to support input as required and allowed by BlueCat management server in terms of characters allowed/disallowed, string size limits, etc. | Must Have |
|
| Connection Status UI | Visual indicator showing connection status (connected / Disconnected). | Must Have |
|
| Test Connection Status UI | There will be a "Test Configuration" button to verify connectivity on demand. This button should return either a a positive result or the the best available error message to help the user trouble shoot the connection. | Must Have |
|
| CLI configuration commands | BlueCat connection must be able to be configured, tested, and enabled via the CLI | Must Have |
|
| Discovery | Use the BlueCat API capability to retrieve information from the management station (network, device, interface) |
| May be possible Phase II effort |
| Logging | At log level "info" system should log successful poll or error message, time of poll, At log level "debug: system should log successful poll or error message, time of poll, size of response in bytes | Must Have |
|
| Dashboard | New dashboard will be created for this feature and added to the Integrations category | Must Have |
|
| Widget | Standard implementation : - What Lumeta knows
- What BlueCat knows
- What both platforms are managing
| Must Have |
|
| Data Management | Each polled response, when not an error or empty response, will replace the previous existing set of devices/information. |
|
|
Epic
LUM-662 - Getting issue details... STATUS
| Key | Summary | T | Assignee | Status | Resolution | qa assignee |
|---|
Loading...
Refresh
Milestones
| Milestone | Date Complete | Notes |
|---|
SPIKE Requirements: - Design Document
- Architecture Document
- Tasks / Tickets that have values less that 13 Points
- Review meeting with Engineering and QA
|
|
|
QA Review: - Review All documentation and artifacts
- Prepare initial test plan
|
|
|
QA Meeting: - Attendees are Product Owner, Engineering and QA
- Question and Answer session
- Review Test Plan
|
|
|
| Feature Demo for Product owner |
|
|
User interaction and design
Questions
Below is a list of questions to be addressed as a result of this requirements document: