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

Vagrant Openstack should works in degraded mode id only Keystone and Nova are availables #142

Closed
ggiamarchi opened this issue Oct 26, 2014 · 0 comments · Fixed by #147
Closed
Assignees
Milestone

Comments

@ggiamarchi
Copy link
Owner

At the moment, the plugin always calls Neutron and Cinder to get information about networks and volumes. This makes possible to indicate in the Vagrantfile the name of a network rather than its id, for instance. If neutron or cinder api is not available, the plugin should works correctly if the Vagrantfile contains all the needed information for nova, i.e. only ids.

If the Vagrantfile configuration is valid regarding to the documentation but cannot be perfom because an api is unavailable, vagrant will fail with an explicit message that explain how to workaround the problem.

@ggiamarchi ggiamarchi added this to the 0.5 milestone Oct 26, 2014
@ggiamarchi ggiamarchi self-assigned this Oct 26, 2014
@ggiamarchi ggiamarchi changed the title Vagrant Openstack should works in degraded mode id only Keystone and Nova are available Vagrant Openstack should works in degraded mode id only Keystone and Nova are availables Nov 3, 2014
Sharpie pushed a commit to Sharpie/vagrant-openstack-provider that referenced this issue Jan 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant