Solaris 11.2 OpenStack UAR Configuration Cookbook by Tim 2016-02-13آ  Solaris 11.2 OpenStack UAR...

download Solaris 11.2 OpenStack UAR Configuration Cookbook by Tim 2016-02-13آ  Solaris 11.2 OpenStack UAR Configuration

If you can't read please download the document

  • date post

    15-Aug-2020
  • Category

    Documents

  • view

    0
  • download

    0

Embed Size (px)

Transcript of Solaris 11.2 OpenStack UAR Configuration Cookbook by Tim 2016-02-13آ  Solaris 11.2 OpenStack UAR...

  • Solaris 11.2 OpenStack UAR Configuration Cookbook by Tim Wort

    This paper is a cookbook for configuring the Oracle Solaris 11.2 OpenStack Unified Archive. The Solaris 11.2 OpenStack Unified Archive is no longer available. If you have the UAR file the following documentation describes how to deploy the UAR.

    This paper assumes the installation and system configuration are complete.

    • Host name configured • Assigned IP address on local network (192.168.1.0/24) • DNS configured • Time, language, locale etc. • root and (optional) user configured

    After the system is installed you can open a web browser from a different system and log in to the Horizon Dashboard but some preparation is required to configure the environment to enable the creation of a Virtual Machine (VM).

    Note: The paper uses line continuations “\”, you can type the backslash as displayed in the paper followed by a newline (return) and complete the line at the secondary shell prompt or do not type the backslash, rather type the complete line and enter a return.

    Configuring the Oracle Solaris Elastic Virtual Switch (EVS):

    root@OSCloud:~# evsadm evsadm: could not open connection to controller: failed connecting to EVS controller

    A script is provided on the installed system in the /usr/demo/openstack directory. This python script can be used to configure EVS quickly. The script does the following:

    • Creates a EVS user • Creates ssh key pairs for the root, neutron, and evsuser users • Add the public keys for the users to the evsusers authorized_keys file • Logs in as each user to except the servers key • Creates a etherstub called l3stub0 (level 3 stub0) • Configures the EVS Controller properties for the etherstub and vlan type and vlans • Starts the Neutron Service

    root@OSCloud:# /usr/demo/openstack/configure_evs.py Generating public/private rsa key pair. Your identification has been saved in /var/user/evsuser/.ssh/id_rsa. Your public key has been saved in /var/user/evsuser/.ssh/id_rsa.pub. The key fingerprint is: 34:d4:fc:9c:63:7c:6b:a4:55:fd:db:9e:2e:66:8a:ca evsuser@OSCloud Generating public/private rsa key pair. Created directory '/var/lib/neutron/.ssh'. Your identification has been saved in /var/lib/neutron/.ssh/id_rsa. Your public key has been saved in /var/lib/neutron/.ssh/id_rsa.pub. The key fingerprint is: 79:d4:95:b3:19:d7:fc:8e:e4:8f:6f:e1:0a:ba:e1:2f neutron@OSCloud

    https://docs.oracle.com/cd/E36784_01/html/E54155/installuar.html#scrolltoc

  • Oracle Corporation SunOS 5.11 11.2 June 2014 Generating public/private rsa key pair. Created directory '/root/.ssh'. Your identification has been saved in /root/.ssh/id_rsa. Your public key has been saved in /root/.ssh/id_rsa.pub. The key fingerprint is: 79:13:4b:9c:dd:5b:1d:5b:70:c7:02:1f:ff:a3:52:8f root@OSCloud populating authorized_keys configuring EVS enabling Neutron

    The following shows the newly configured EVS information.

    root@OSCloud:~# evsadm show-prop PROPERTY PERM VALUE DEFAULT controller rw ssh://evsuser@localhost --

    root@OSCloud:~# evsadm show-controlprop PROPERTY PERM VALUE DEFAULT HOST l2-type rw vlan vlan -- uplink-port rw l3stub0 -- -- vlan-range rw 200-300 -- -- vlan-range-avail r- 200-300 -- -- vxlan-addr rw 0.0.0.0 0.0.0.0 -- vxlan-ipvers rw v4 v4 -- vxlan-mgroup rw 0.0.0.0 0.0.0.0 -- vxlan-range rw -- -- -- vxlan-range-avail r- -- -- –

    Environment variables

    A set of environment variables need to be configured to use the OpenStack commands, you may type these directly in your current shell instance or place them into a file and source the file or you can add them to the root users .profile file.

    In the example the variables are added to the .profile file.

    root@OSCloud:~# vi /root/.profile

    Added to the bottom of the file:

    export OS_USERNAME=neutron export OS_PASSWORD=neutron export OS_TENANT_NAME=service export OS_AUTH_URL=http://localhost:5000/v2.0

    Source the file.

    root@OSCloud:~# . /root/.profile

    Verify the results.

    root@OSCloud:~# env

  • HZ= LC_MONETARY= SHELL=/usr/bin/bash TERM=xterm LC_NUMERIC= OLDPWD=/etc/keystone LC_ALL= PAGER=/usr/bin/less -ins MAIL=/var/mail/root PATH=/usr/bin:/usr/sbin LC_MESSAGES= LC_COLLATE= PWD=/root OS_PASSWORD=neutron LANG= TZ=localtime OS_AUTH_URL=http://localhost:5000/v2.0 OS_USERNAME=neutron SHLVL=1 HOME=/root OS_TENANT_NAME=service LOGNAME=root LC_CTYPE= LC_TIME= _=/usr/bin/env

    Next the services are examined and all of the openstack services should be enabled and running.

    root@OSCloud:~# svcs | grep openstack online 3:34:46 svc:/application/openstack/swift/swift-account-reaper:default online 3:34:47 svc:/application/openstack/swift/swift-container-replicator:default online 3:34:47 svc:/application/openstack/swift/swift-object-server:default online 3:34:47 svc:/application/openstack/swift/swift-container-sync:default online 3:34:47 svc:/application/openstack/swift/swift-account-auditor:default online 3:34:47 svc:/application/openstack/swift/swift-container-updater:default online 3:34:47 svc:/application/openstack/swift/swift-container-server:default online 3:34:47 svc:/application/openstack/swift/swift-object-replicator:default online 3:34:47 svc:/application/openstack/swift/swift-object-auditor:default online 3:34:47 svc:/application/openstack/swift/swift-container-auditor:default online 3:34:47 svc:/application/openstack/swift/swift-proxy-server:default online 3:34:47 svc:/application/openstack/swift/swift-account-replicator:default online 3:34:48 svc:/application/openstack/nova/nova-objectstore:default online 3:34:48 svc:/application/openstack/swift/swift-object-updater:default online 3:34:48 svc:/application/openstack/swift/swift-object-expirer:default online 3:34:48 svc:/application/openstack/swift/swift-replicator-rsync:default online 3:34:48 svc:/application/openstack/glance/glance-scrubber:default online 3:34:48 svc:/application/openstack/swift/swift-account-server:default online 3:34:51 svc:/application/openstack/glance/glance-db:default online 3:34:52 svc:/application/openstack/cinder/cinder-db:default online 3:34:52 svc:/application/openstack/keystone:default online 3:34:53 svc:/application/openstack/nova/nova-api-osapi-compute:default online 3:34:53 svc:/application/openstack/nova/nova-api-ec2:default online 3:34:55 svc:/application/openstack/nova/nova-conductor:default online 3:34:56 svc:/application/openstack/glance/glance-api:default online 3:34:56 svc:/application/openstack/glance/glance-registry:default online 3:34:56 svc:/application/openstack/cinder/cinder-api:default online 3:34:57 svc:/application/openstack/cinder/cinder-scheduler:default online 3:34:58 svc:/application/openstack/cinder/cinder-volume:setup online 3:34:58 svc:/application/openstack/nova/nova-compute:default online 3:34:58 svc:/application/openstack/nova/nova-scheduler:default online 3:34:58 svc:/application/openstack/nova/nova-cert:default online 3:34:59 svc:/application/openstack/cinder/cinder-volume:default online 3:46:03 svc:/application/openstack/neutron/neutron-server:default online 3:46:04 svc:/application/openstack/neutron/neutron-dhcp-agent:default

    With the environment variables in place the keystone command can be uses to list the default tenants.

  • root@OSCloud:~# keystone tenant-list +----------------------------------+---------+---------+ | id | name | enabled | +----------------------------------+---------+---------+ | 1cb851c5711dee6cf28aa43d37129cc2 | demo | True | | 7461d4a9f5a64af9a01ae4e84e08c182 | service | True | +----------------------------------+---------+---------+

    Neutron Network Configuration

    Next an internal network is create to support the VM that will be created. This is a private network and is only accessible to the VMs created in this tenant. The red text above denotes the tenant ID that is used to populate the neutron net-create sub command. (INT is an arbitrary name selected for the network.)

    root@OSCloud:~# neutron net-create --provider:network_type=vlan \ --router:external=false --tenant-id 1cb851c5711dee6cf28aa43d37129cc2 INT Created a new network: +--------------------------+--------------------------------------+ | Field | Value | +--------------------------+--------------------------------------+ | admin_state_up | True | | id | 1c11255c-68ed-11e5-8e9c-11bccdfe43cd | | name | INT | | provider:network_type | vlan | | provider:segmentation_id | 200 | | router:external | False | | shared | False | | status | ACTIVE | | subnets | | | tenant_id