Guillaume Giamarchi

Yes, I forgot to tell it, I managed to make it work using the workspace settings. Does the `wrong usage` label mean you don't consider this behavior as a bug?...

Should be resolved by #281

There's some work... But I definitely agree, it is necessary. We should use Neutron in priority and fallback on nova-network for legacy OpenStack platforms

@micx523 I don't manage to reproduce your issue. Can you provide : * Your Vagrant version (`vagrant --version`) * The plugin list with versions installed (`vagrant plugin list`) * Your...

@jmatt Thank you for this report. I agree with you, the Vagrant standard should be used. Even if this is a breaking change, i think we should do this. It...

The instance log can be fetch using the nova extension api : ``` POST /v2/​{tenant_id}​/servers/​{server_id}​/action { "os-getConsoleOutput": { } } ```

I agree, we should be able to get every information we need using vagrant CLI and nothing more. We talked about something like that in issue #143 but it has...

@kelbyers For your concern, the workaround described by @jessereynolds looks to be good enough to me. By the way, if you or someone wish to contribute an implementation for the...

I would prefer to not change the behavior of `vagrant status`. If we create a new command `vagrant openstack status` it should print a full summary of the instance (state,...

If possible, a better idea would be to add a `--details` parameter to the standard command `vagrant satus`.