Problems deploying SVMP in Openstack

97 views
Skip to first unread message

Ferdi Llaca

unread,
Aug 6, 2015, 12:10:03 PM8/6/15
to SVMP Developers

Hi,

I have deployed SVMP in my Openstack system and I can query the images, flavors and volumes and so from the “svmp-confgi” cli tool. But when I try to connect a user to the system from the Android client app, the SVMP Overseer throws the following error log message:

error: setUpVm failed: VM setup failed: createAndStartVM failed, couldn't create server: openstack Error (400): Bad Request

This is my Openstack config:

 

new_vm_defaults:

    images:

        # Mapping of cloud image ID to a friendly name. These are the names used by the

        # configuration tool's add-user command.

        # each device type should have its own name and image ID in key/value format, e.g.:

        # "device_type": "imageID",

        note2: "2472109c-f3af-4429-83be-355b1b51c634"

        # example_type_2: "image id"

    vmflavor: "f226712c-6a69-4353-bbc9-9fd1f64802b0"

    #vmflavor: "f226712c-6a69-4353-bbc9-9fd1f64802b0"

    goldsnapshotId: "5c10ec54-2476-4050-8b3e-9426a267e468"

    goldsnapshotSize: 8

    use_floating_ips: true

    floating_ip_pool: "ext-net"

    pollintervalforstartup: 2000

 

(…)

 

cloud_platform: "openstack"

 

# Openstack cloud connection details

openstack:

    # only required if 'cloud_platform' is set to 'openstack'

    authUrl: "http://X.X.X.X:5000"

    username: "admin"

    password: "blahblah"

    # tenantId: "0123456789abcdef0123456789abcdef"

    # tenantId: "3133c6096801417b8492003464501f97"

    tenantName: "admin"

    region: "RegionOne"

 

I would greatly appreciate any help.

Regards, Fernando

Ferdi Llaca

unread,
Aug 7, 2015, 7:44:47 AM8/7/15
to SVMP Developers
digging a little on the http responses, I found that the error was due to the several existing networks in my Openstack tenant. Here you can see one of these responses:

{ [Error: openstack Error (400): Bad Request]
  name: 'Error',
  provider: 'openstack',
  failCode: 'Bad Request',
  statusCode: 400,
  href: 'http://192.168.50.64:8774/v2/3133c6096801417b8492003464501f97/servers',
  method: 'POST',
  headers:
   { 'content-length': '115',
     'content-type': 'application/json; charset=UTF-8',
     'x-compute-request-id': 'req-03d00dd4-627a-47c0-b35a-e15676134620',
     date: 'Fri, 07 Aug 2015 10:22:14 GMT',
     connection: 'keep-alive' },
  result:
   { badRequest:
      { message: 'Multiple possible networks found, use a Network ID to be more specific.',
        code: 400 } } }

I solved this by adding a new config parameter in "config-local.yaml",  networkId and making up a little the lib/cloud/openstack.js module to use this parameter. After this, the system is able to create the virtual machine for the user but it fails now when trying to associate the floating ip:

{ [Error: openstack Error (400): Bad Request]
  name: 'Error',
  provider: 'openstack',
  failCode: 'Bad Request',
  statusCode: 400,
  href: 'http://192.168.50.64:8774/v2/3133c6096801417b8492003464501f97/servers/78c2efd6-0186-4e27-9726-1e0e5b7093b9/action',
  method: 'POST',
  headers:
   { 'content-length': '82',
     'content-type': 'application/json; charset=UTF-8',
     'x-compute-request-id': 'req-de703274-a174-4308-ac05-790c97183443',
     date: 'Fri, 07 Aug 2015 11:17:06 GMT',
     connection: 'keep-alive' },
  result: { badRequest: { message: 'Error. Unable to associate floating ip', code: 400 } } }

Maybe this new error is caused by my modifications, but i think that the system can get to be able to hold several networks in tenant. 

Any approach will be very appreciate, 

Fernando
Reply all
Reply to author
Forward
0 new messages