-
Notifications
You must be signed in to change notification settings - Fork 45
Metaflow UI Cloudformation nested stack support. #42
Conversation
Properties: | ||
Family: !FindInMap ["ServiceInfoUI", "ServiceName", "value"] | ||
Cpu: !FindInMap ["ServiceInfoUI", "ContainerCpu", "value"] | ||
Memory: !FindInMap ["ServiceInfoUI", "ContainerMemory", "value"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we configure SSDs for the cache in fargate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to use higher values?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
IMPORTANT: Do not merge before User Interface is released as part of
netflixoss/metaflow_metadata_service
Docker image.Related Admin Docs PR: Netflix/metaflow-docs#12
User Interface is provided as part of the
metaflow-cfn-template.yml
template 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.