For features that were introduced to OpenStack core components in this version, refer to the following release notes and optionally its preceding version:
For a list of issues with the current Juno release, see the version's corresponding Readme file in My Oracle Support.
The following Oracle Solaris functionalities are provided in OpenStack Juno:
Console support for VM instances, where each instance's console can be accessed from a browser based on a user's request.
For Horizon, Apache 2.4 is used by default if it is available on the system. Thus, httpd.conf fragments for both TLS and HTTP are included in the Apache 2.4's samples-conf.d directory.
For Neutron, complete IPv6 support for tenant networks as well as support for source NAT (SNAT).
By default, SNAT is enabled on the gateway interface of a Neutron router. To disable this feature, run neutron router-gateway-set --disable-snat command.
Additionally in Neutron, the following are supported in Juno:
Metadata Services
Flat (untagged) Layer-2 Network Type
New Neutron Subcommands
For more details on these Neutron features, see What's New in Solaris OpenStack Juno Neutron.
An added SMF service is introduced to correspond with an upgrade service in Swift 2.2.2 which reconciles objects in Swift containers after recovery from a network partition.
Support for OpenStack and EC2-compatible metadata services.
Beginning from the Oracle Solaris 11.3 SRU 2 release, the following features were added that are related to Cinder
Use of Remote SAN Storage
Aside from operating on locally managed ZFS volumes, with the support for Paramiko, Cinder can also provision these ZFS volumes on remote Solaris nodes as SAN storage using the iSCSI or Fiber Channel protocol. Remote systems can be orchestrated by configuring them into multiple storage back ends.
Support for Volume Backup and Restore Operations
The Cinder backup SMF service is now enabled in Oracle Solaris. Therefore, unattached volumes can be backed up and restored between configured back ends. Currently, Swift is the only supported back end.
Support for Cinder Volume Migration
Cinder takes advantage of ZFS operations to migrate Cinder volumes. ZFS send and receive processes enable the migration of volumes between different configured Cinder back ends. If the migration destination resides on the same zpool as the source, then a ZFS rename operation is used. Currently, cinder volume migration support is limited to a single system.
Beginning from the Oracle Solaris 11.3 SRU 6 release, the following features related to Nova are added:
Live Migration
You can start live migration by using the Horizon service's dashboard or the nova command. The scheduler selects the target host of the migration from among participating nodes. These nodes must have each other's public SSH keys. See Migrating and Evacuating VM Instances.
Encryption ensures that a live migration operation is secure. Through a parameter in the /etc/nova.conf file, you can manually select the encryption to use or you can let the process select a suitable encryption.
Support for Instance Evacuation
The nova evacuate functionality. In the event of host failure or services becoming disabled on the host, the instance can be safely moved to a different node and recovered from that node. Note that support for evacuation is available only if the root devices are on shared storage. Furthermore, evacuation is supported only for kernel zones, not non-global zones.
Resizing VM Instances
Resizing VM instances to new flavors is supported. For a VM instance you can increase or decrease the number of CPUs and the amount of memory available. Additionally, you can also increase the size of the root volume available to an instance. However, reducing the size of root volumes is not currently supported.