Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sprint 51 blog post - provider fix #468

Merged
merged 2 commits into from
Jan 6, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ In Classic UI, columns displaying virtual CPU and memory values for Cloud Provid

New Chargeback features include support for fixed and allocated costs without metrics, and arbitration logic for multiple assigned rates. On the Automate side, enhanced messaging has been extended to Ansible and Cloud Provisioning, and importing Automate modeling from the UI now honors the tenant.

For VMware vCloud, XLAB added the ability to specify VM attributes when deploying vApps. Another big step for providers in general is the new Provider Generator, which was [proposed](https://www.youtube.com/watch?v=i5ZuTKFQqJ8) in last year's Design Summit. With a single line of command, `rails generate provider ProviderName` will generate the scaffolding for a provider.
For the VMware vCloud provider, XLAB added the ability to specify VM attributes when deploying vApps. As for providers in general, we made a big step with the new Provider Generator, which was [proposed](https://www.youtube.com/watch?v=i5ZuTKFQqJ8) in last year's Design Summit. With a single line of command, `rails generate provider ProviderName` will generate the scaffolding for a provider.

<iframe width="560" height="315" src="https://www.youtube.com/embed/2iRkB_eKb44" frameborder="0" allowfullscreen></iframe>

Expand Down