Metaflow UI Cloudformation nested stack support.#42
Metaflow UI Cloudformation nested stack support.#42savingoyal merged 7 commits intoNetflix:masterfrom
Conversation
| Properties: | ||
| Family: !FindInMap ["ServiceInfoUI", "ServiceName", "value"] | ||
| Cpu: !FindInMap ["ServiceInfoUI", "ContainerCpu", "value"] | ||
| Memory: !FindInMap ["ServiceInfoUI", "ContainerMemory", "value"] |
There was a problem hiding this comment.
Can we configure SSDs for the cache in fargate?
There was a problem hiding this comment.
I don't think it's possible to configure that while using Fargate.
| ContainerCpu: | ||
| value: 512 | ||
| ContainerMemory: | ||
| value: 1024 |
There was a problem hiding this comment.
Do we want to use higher values?
There was a problem hiding this comment.
This is following the same configuration as metadata service. I would keep these values as is and let admin alter resources as needed.
There was a problem hiding this comment.
Yes but the performance profile of the UI service is quite different than the metadata service.
| Type: String | ||
| Default: 'false' | ||
| AllowedValues: ['false', 'true'] | ||
| Description: 'Enable Metaflow UI' |
There was a problem hiding this comment.
We should call out that we strongly recommend deploying the UI against a logical replica of the DB and they should only enable the UI here for testing purposes.
There was a problem hiding this comment.
We can add a pointer to a README on how to create a logical replica in README.md.
There was a problem hiding this comment.
Admin doc PR includes overview of setting up a logical replication https://github.com/Netflix/metaflow-docs/pull/12/files#diff-27c4a28d354456792c127bf0139de4d3f74a9264a4ac176e01dba0b866692240. We can refer to this document once approved and merged.
…g related to UI is now within the main template.
2 participants
IMPORTANT: Do not merge before User Interface is released as part of
netflixoss/metaflow_metadata_serviceDocker image.Related Admin Docs PR: Netflix/metaflow-docs#12
User Interface is provided as part of the
metaflow-cfn-template.ymltemplate and doesn't require any additionalconfiguration besides enabling the
EnableUI-parameter. You can follow the AWS CloudFormation Deployment instructions.Once deployed the Cloudformation Stack will provide two outputs:
UIServiceUrl- Application Load Balancer endpointUIServiceCloudfrontUrl- Cloudfront distribution (using ALB) endpoint with HTTPS enabled (preferred)Please note: Metaflow User Interface doesn't provide any authentication by default.