List view
MULTI-PROVIDER PROVISIONING: To provide the ability to provision a resource in any provider to fulfill the request. This may include either public or private clouds. *This milestone may be out of scope for this REST CLI project, as it will depend heavily on logic defined in Automate. It will be reevaluated as the project proceeds.*
No due dateAUTOMATE-AWARE PROVISIONING: Provide integration with the Automate system during either basic provisioning or provisioning via the service catalog. For example, reference Automate functionality that ensures a given request can be fulfilled based on the available resources (CPU, DISK, RAM) in a provider.
No due dateSERVICE CATALOG/ADDITIONAL PROVIDERS: To support provisioning via service catalog requests and provide CLI support for provisioning for additional providers (Beaker).
No due date•1/1 issues closedBASIC PROVISIONING: To provide a tool for interacting with CloudForms/ManageIQ to provision/teardown resources (virtual machines and containers "pods") in the defined providers.
Overdue by 8 year(s)•Due by March 26, 2018•54/54 issues closed