70 lines
2.9 KiB
Markdown
70 lines
2.9 KiB
Markdown
- Service Desc #call
|
|
collapsed:: true
|
|
- standalone CapEX
|
|
- covered by EULA / ALA
|
|
- under GL sale (Opex)
|
|
- what does it bring othe solution
|
|
- how is it paid for
|
|
- is it a seperate item ont he bill
|
|
- term based license
|
|
- fixed fee
|
|
- not dynamically metered
|
|
- good example template
|
|
- [Zerto service description Greenlake Flex.docx](https://hpe.sharepoint.com/:w:/r/sites/msteams_289393/Shared%20Documents/General/Template%20Lifecyle/Contract%20Requests/CR199-%20Zerto/Zerto%20service%20description%20Greenlake%20Flex.docx?d=w0d108cc1d0e5402ea53b2c617ab268e6&csf=1&web=1&e=X8mADH)
|
|
- <!--EndFragment-->
|
|
- 
|
|
-
|
|
- Update
|
|
- Service Desc.
|
|
- review
|
|
- Morpheus Equinix #call
|
|
collapsed:: true
|
|
- network edge /
|
|
- fabric cloud router (VRF)
|
|
- L3 forwarded
|
|
- 10Gb limit
|
|
-
|
|
- how were network providers integrated?
|
|
-
|
|
- main thing EQ is focused on
|
|
- automating processes for customers
|
|
- build rpivate and publically conneted services
|
|
- customers looks for faster consume optins
|
|
- looks to become more API centric in delivery
|
|
- what is the roadmap for routers?
|
|
- what would the licensing look like?
|
|
- what are the scale limits for network management?
|
|
-
|
|
-
|
|
-
|
|
-
|
|
-
|
|
-
|
|
- Openshift integration #call
|
|
- GCC under A&PS?
|
|
- onboard partner
|
|
- Need to get clarity on coding standards/architecture
|
|
- Customer:
|
|
- Partner: Kogo
|
|
- if Kogo how do they integrate
|
|
- Development scope:
|
|
- OCP integration
|
|
- Create cluster
|
|
- 
|
|
- #Morpheus #[[plugins and integrations]]
|
|
id:: 6814dcc8-7ce7-4825-bd25-6ed26710a902
|
|
- Developer Docs https://developer.morpheusdata.com/docs
|
|
- Groovy based (like typescript for Java)
|
|
- plugins must use common models from https://developer.morpheusdata.com/api/com/morpheusdata/model/package-summary.html to ensure data stored correct format and is cross compatible
|
|
- Gradle build system
|
|
- Open Questions:
|
|
- The Roadmap looks to show migrating existing integrations to plugins (this makes good sense). Will these be equal citizens, or will internally developed plugins have extra capabilites (ie. being installed be default)
|
|
- Is there a documented style guide published that could be used to enable internal/external developed to create plugins that could be 'gradated' to core (ie. HPE managed)?
|
|
- e.g. if GCC (or other internal HPE team) were to develop a plugin could that eventually become a core plugin?
|
|
- Is there a program in place for third parties to certify their plugins? e.g. can Zerto manage the lifecycle of their own plugin and have the Morpheus team bless it?
|
|
-
|
|
- OpsRamp #call
|
|
- PCAI being pushed to be an engineered system for observability
|
|
- Sounds like the plan is for Morpheus at act as the aggregation layer for metrics/logs
|
|
- unclear what the tech stack looks like (opentelem?)
|
|
- recommended talking to David Estes for technical direction |