outdated --block-device doc for nova boot in user guide

[Mike Spreitzer]

http://docs.openstack.org/user-guide/content/attach_volume_to_instance.html and siblings document a --block-device argument to `nova boot` but that is outdated. Now `nova boot` takes a --block-device-mapping argument instead, with a difference syntax for its value.

[Andreas Jaeger (jaegerandi)]

Where does it say that --block-device is outdated? Looking at "nova help boot" I see no deprecation notice.

[Mike Spreitzer (mike-spreitzer)]

Perhaps the vintage I am running was some bad interim state, but there was no --block-device available.

But there is now a --block-device-mapping now available and it needs documentation, right?

[Andreas Jaeger (jaegerandi)]

Sure, it's nice to document it. But there's no need IMHO to change the existing documentation...

Btw. the CLI Reference documents both options.

[Anne Gentle (annegentle)]

I agree that the user guide instructions themselves can be updated. Apparently there's also a --block-device-mapping-v2 which makes things even more confusing.

[Anne Gentle (annegentle)]

Woops, I don't mean there's a second parameter. I mean there's this:

http://developer.openstack.org/api-ref-compute-v2-ext.html#ext-os-block-device-mapping-v2-boot

which causes confusion.

The basic explanation for the v2 is that in that call, nova is passing info on to cinder and booting, but in in the other version, (block-device-mapping) you've already done the volume creation and you're just using nova to boot from it.

[Tom Fifield (fifieldt)]

This is now in http://docs.openstack.org/cli-reference/content/novaclient_commands.html