I'm also still confused at the initial report, you have "mpi". On the nova I'm looking at: $ wget http://169.254.169.254/2009-04-04/ -O - -q ; echo meta-data/ user-data $ wget http://169.254.169.254/2009-04-04/meta-data/ -O - -q; echo reservation-id public-keys/ security-groups public-ipv4 ami-manifest-path instance-type instance-id local-ipv4 local-hostname placement/ ami-launch-index public-hostname hostname ami-id instance-action block-device-mapping/
$ wget http://169.254.169.254/2009-04-04/meta-data/mpi -O - --2012-06-04 13:41:23-- http://169.254.169.254/2009-04-04/meta-data/mpi Connecting to 169.254.169.254:80... connected. HTTP request sent, awaiting response... 404 Not Found 2012-06-04 13:41:23 ERROR 404: Not Found.
Attemping to import a 'my brickies' keypair name via either web ui or command line client on HP cloud gives: $ nova keypair-add "my brickies" --pub_key ~/.<email address hidden> ERROR: Invalid keypair name (HTTP 400)
I'm also still confused at the initial report, you have "mpi". On the nova I'm looking at: 169.254. 169.254/ 2009-04- 04/ -O - -q ; echo 169.254. 169.254/ 2009-04- 04/meta- data/ -O - -q; echo mapping/
$ wget http://
meta-data/
user-data
$ wget http://
reservation-id
public-keys/
security-groups
public-ipv4
ami-manifest-path
instance-type
instance-id
local-ipv4
local-hostname
placement/
ami-launch-index
public-hostname
hostname
ami-id
instance-action
block-device-
$ wget http:// 169.254. 169.254/ 2009-04- 04/meta- data/mpi -O - 169.254. 169.254/ 2009-04- 04/meta- data/mpi 169.254: 80... connected.
--2012-06-04 13:41:23-- http://
Connecting to 169.254.
HTTP request sent, awaiting response... 404 Not Found
2012-06-04 13:41:23 ERROR 404: Not Found.
Attemping to import a 'my brickies' keypair name via either web ui or command line client on HP cloud gives:
$ nova keypair-add "my brickies" --pub_key ~/.<email address hidden>
ERROR: Invalid keypair name (HTTP 400)