Installing and Configuring OpenStack in Oracle® Solaris 11.2

Exit Print View

Updated: April 2015

Known Limitations

The following are known issues with OpenStack (Havana 2013.2.3) in Oracle Solaris 11.2:

  • Remote console access to VM instances by using the OpenStack dashboard is not supported. Instead, use the dashboard to upload an SSH keypair. This keypair will be pushed into the authorized_keys file for root for that VM instance.

  • Only Nova nodes running Solaris are fully supported because Neutron supports only a single plugin for network virtualization.

  • Currently the Cinder volume attachment is not supported in the non-global zones.

  • VM instances must be running Oracle Solaris 11.2.

  • Resizing VM instances is not supported.

    The nova resize command is not supported. Output from the nova resize command might say the command completed, but the nova resize-confirm command reports that the resizing of the instance cannot be confirmed, and the nova show command shows that the instance is not resized.

  • VM instance live migration is not supported.

    The nova live-migration command is not supported.

  • Cinder backup is not supported.

    The cinder-backup service is installed when you install the cinder package, but the service is disabled and you should leave it disabled.

  • On the Launch Instance dialog in the dashboard, only Boot from image is supported for the Instance Boot Source. On the Project → Images & Snapshots → Actions menu, CreateVolumeFromImage is not supported. See Solaris OpenStack Horizon customizations for information about other customizations for the Solaris OpenStack dashboard.

  • VXLAN datalinks are not supported as the value for the external_network_datalink option in the /etc/neutron/l3_agent.ini file. If you set a VXLAN datalink as the value for the external_network_datalink option, the Neutron L3 agent fails to create and plumb a VNIC on the external network.

  • You must use the command line to modify the quota for a network resource for a project.

    The quota for a network resource cannot be modified from Horizon. You can use the Horizon dashboard to create a project or modify non-network resources of an existing project. To modify the quota for networks, subnets, ports, routers, or floating IP addresses of a project, you must use the neutron quota-update command.

    Even when you modify a non-network resource, you see the following error message. You can ignore this message. Contrary to this message, the quota for the non-network resource has been applied.

    Error: Modified project information and members, but unable to modify project quotas.
  • Service status might be reported differently by SMF and by OpenStack.

    The following example shows that the nova-cert service is disabled in OpenStack, even though SMF shows the service as online:

    root@c190-133:~# nova service-disable c190-133 nova-cert
    | Host     | Binary    | Status   |
    | c190-133 | nova-cert | disabled |
    root@c190-133:~# svcs nova-cert
    STATE          STIME    FMRI
    online         21:14:11 svc:/application/openstack/nova/nova-cert:default
  • The neutron-l3-agent SMF service goes into maintenance when it is restarted.

    Workaround: Restart the ipfilter service and clear the neutron-l3-agent.

    network# svcadm restart ipfilter:default
    network# svcadm clear neutron-l3-agent:default
  • The default gateway for the Network node is removed in certain setups.

    If the IP address of the Network node is derived from the external_network address space, and if you use the neutron router-gateway-clear command to remove the external_network from the provider_router, the default gateway for the Network node is deleted and the Network node is inaccessible.

    network# neutron router-gateway-clear router_UUID

    Workaround: Connect to the Network node through the console and add the default gateway again.

  • Nova sqlite database locks up when multiple instances are created concurrently.

    When a large number of instances (for example, 10 or more) are created concurrently, the nova list command stops working for a period of time with the following error message:

    $ nova list
    ERROR: The server has either erred or is incapable of performing the
    requested operation. (HTTP 500) (Request-ID:

    Horizon is also unable to find the instances.

    The cause of this problem is that the Nova sqlite database gets locked up. After some time, the database catches up, and nova list and Horizon function as expected.

    Workaround: Use the MySQL database instead of sqlite. See How to Configure the Compute Node.