You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2018. It is now read-only.
Will repo locations for MaaS streams as well as platform packages be part of the site design or will they be configured as part of the MaaS service deployment? If the former, need to add them to the Drydock object model.
The text was updated successfully, but these errors were encountered:
Wouldn't that somewhat depend on whether we have some sort of local repo (with some convention that asserts its always the same regardless of a location) vs it might vary from deployment to deployment. If its the later I think it becomes part of the UnderCloud configuration information. Which in my mind is either a subset of a Site Description (Site Manifest) or a standalone SiteUnderCloudConfigManifest. The later case we would have workflows to manage that, similar to any other site workflow . But i.e. operations to modify configuration of UnderCloud components . i.e. k8s, docker, dry dock (maas) etc.
I think I am leaning towards the later. Which in a sense maps to "MaaS streams as well as platform packages WILL be part of the site design"
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Will repo locations for MaaS streams as well as platform packages be part of the site design or will they be configured as part of the MaaS service deployment? If the former, need to add them to the Drydock object model.
The text was updated successfully, but these errors were encountered: