I cannot understand following points. It would be appreciated, that suggest me a practical expection
1)config_drive.py (alex: we should get rid of extension, there is one section describe this extension http://developer.openstack.org/api-ref-compute-v2.1.html#os-config-drive-v2.1)
2)(alex: we didn't attach action anymore http://developer.openstack.org/api-ref-compute-v2.1.html#attachVolume)
3)flavors.py (alex: just call this as flavor section? http://developer.openstack.org/api-ref-compute-v2.1.html#os-flavors-v2.1
4)servers.py (alex: http://developer.openstack.org/api-ref-compute-v2.1.html#os-server-usage-v2.1 we should call this as server section? I didn't find out any other section called as servers. As we will get rid of extension, the response should include all the extend attributes.)
I cannot understand following points.
It would be appreciated, that suggest me a practical expection
1)config_drive.py (alex: we should get rid of extension, there is one section describe this extension http:// developer. openstack. org/api- ref-compute- v2.1.html# os-config- drive-v2. 1)
2)(alex: we didn't attach action anymore http:// developer. openstack. org/api- ref-compute- v2.1.html# attachVolume)
3)flavors.py (alex: just call this as flavor section? http:// developer. openstack. org/api- ref-compute- v2.1.html# os-flavors- v2.1
4)servers.py (alex: http:// developer. openstack. org/api- ref-compute- v2.1.html# os-server- usage-v2. 1 we should call this as server section? I didn't find out any other section called as servers. As we will get rid of extension, the response should include all the extend attributes.)