/usr/lib/python2.6/site-packages/novaclient/tests/functional/v2/legacy
Edit: /usr/lib/python2.6/site-packages/novaclient/tests/functional/v2/legacy/test_instances.pyc (2431B)
Ñò
=vVc @ s- d d k l Z d e i f d „ ƒ YZ d S( iÿÿÿÿ( t baset TestInstanceCLIc B s e Z d Z d „ Z RS( s 2.1c C sd | i d ƒ } | i i i ƒ d } | i d d d | i i | i i | | i f ƒ| i i i d h | d 6ƒ } | i
d t | ƒ | ƒ | d } | i | i
ƒ | i i i d ƒ } | i | i d d | i ƒ| i | d
ƒ | i d d d | | i f ƒ| i | d
ƒ | i d d d | | i f ƒ| i | d
ƒ | i d d | i ƒd S( s* Test we can attach a volume via the cli.
This test was added after bug 1423695. That bug exposed
inconsistencies in how to talk to API services from the CLI
vs. API level. The volumes api calls that were designed to
populate the completion cache were incorrectly routed to the
Nova endpoint. Novaclient volumes support actually talks to
Cinder endpoint directly.
This would case volume-attach to return a bad error code,
however it does this *after* the attach command is correctly
dispatched. So the volume-attach still works, but the user is
presented a 404 error.
This test ensures we can do a through path test of: boot,
create volume, attach volume, detach volume, delete volume,
destroy.
t Instancei t boott paramss0 --flavor %s --image %s %s --nic net-id=%s --pollt search_optst namei s
volume-deletet availables
volume-attachs %s %ss in-uses
volume-detachN( t
name_generatet clientt networkst listt novat flavorR t imaget idt serverst assertEqualt lent
addCleanupt deletet volumest createt wait_for_volume_status( t selfR t networkR t servert volume( ( s_ /tmp/pip-build-cD3xZi/python-novaclient/novaclient/tests/functional/v2/legacy/test_instances.pyt test_attach_volume s" #
( t __name__t
__module__t COMPUTE_API_VERSIONR ( ( ( s_ /tmp/pip-build-cD3xZi/python-novaclient/novaclient/tests/functional/v2/legacy/test_instances.pyR s N( t novaclient.tests.functionalR t ClientTestBaseR ( ( ( s_ /tmp/pip-build-cD3xZi/python-novaclient/novaclient/tests/functional/v2/legacy/test_instances.pyt
s