Merge pull request #64 from oracle/release_2018-05-04

Releasing version 2.4.22

Author: viralmodi

CHANGELOG.rst

@@ -6,6 +6,31 @@ All notable changes to this project will be documented in this file.
 
 The format is based on `Keep a Changelog <http://keepachangelog.com/>`__.
 
+2.4.22 - 2018-05-03
+---------------------
+Added
+~~~~~~~~
+* Support for returning ``event-name`` in logs extracted from Audit Service. (``oci audit event list``)
+* Support for multiple hostnames per listener in Load Balancer Service. An example can be found on `Github <https://github.com/oracle/oci-cli/blob/master/scripts/create_load_balancer.sh>`_ (``oci lb hostname`` and ``oci lb listener create --hostname-names``)
+* Support for FastConnect service. New commands as mentioned below are added:
+
+	* ``oci network cross-connect-group``
+	* ``oci network cross-connect``
+	* ``oci network cross-connect-location``
+	* ``oci network cross-connect-port-speed-shape``
+	* ``oci network cross-connect-status``
+	* ``oci network fast-connect-provider-service``
+	* ``oci network virtual-circuit``
+	* ``oci network virtual-circuit-public-prefix``
+
+Fixed
+~~~~~~~~
+* Multiple OCI CLI installation issues as specified below:
+
+	* Corrected usage of ``--accept-all-defaults`` to prevent an infinite loop.
+	* An issue which causes failure of OCI CLI installations in non-default directories.
+	* An issue related to download of virtualenv package on windows instances.
+
 2.4.21 - 2018-04-19
 ---------------------
 Added

requirements.txt

@@ -12,7 +12,7 @@ Jinja2==2.9.6
 jmespath==0.9.3
 ndg-httpsclient==0.4.2
 mock==2.0.0
-oci==1.3.19
+oci==1.3.20
 packaging==16.8
 pluggy==0.4.0
 py==1.4.33

scripts/create_load_balancer.sh

@@ -55,6 +55,9 @@ function create_lb_with_all_options_as_individual_options() {
     # load balancer feature set by providing traffic routing flexibility.
     # More info about the feature can be found in scripts/create_load_balancer_example/path_route_sets_with_comments.json
     jsonlint -Sf scripts/create_load_balancer_example/path_route_sets_with_comments.json > scripts/create_load_balancer_example/path_route_sets.json
+    # Hostname are not mandatory parameter to load balancer create. They allow traffic to route to
+    # different backend sets by allowing multiple hostnames to map to a single listener in load balancer
+    jsonlint -Sf scripts/create_load_balancer_example/hostnames_with_comments.json > scripts/create_load_balancer_example/hostnames.json
 
     # Subnets are passed as a JSON array where each entry is a subnet OCID. For example:
     #
@@ -71,7 +74,15 @@ function create_lb_with_all_options_as_individual_options() {
     #   - The listener information (--listeners) may need the name of the certificate bundle specified in --certificates
     #
     # So you need to take that into account when preparing your files for input
-    CREATED_LB=$(oci lb load-balancer create -c $COMPARTMENT_ID --display-name exampleLb --shape-name $LB_SHAPE --subnet-ids file://scripts/create_load_balancer_example/subnets.json --certificates file://scripts/create_load_balancer_example/certificates.json --backend-sets file://scripts/create_load_balancer_example/backend_sets.json --listeners file://scripts/create_load_balancer_example/listeners.json --path-route-sets file://scripts/create_load_balancer_example/path_route_sets.json)
+    CREATED_LB=$(oci lb load-balancer create -c $COMPARTMENT_ID \
+                                            --display-name exampleLb \
+                                            --shape-name $LB_SHAPE \
+                                            --subnet-ids file://scripts/create_load_balancer_example/subnets.json \
+                                            --certificates file://scripts/create_load_balancer_example/certificates.json \
+                                            --backend-sets file://scripts/create_load_balancer_example/backend_sets.json \
+                                            --listeners file://scripts/create_load_balancer_example/listeners.json \
+                                            --path-route-sets file://scripts/create_load_balancer_example/path_route_sets.json \
+                                            --hostnames file://scripts/create_load_balancer_example/hostnames.json)
     WORK_REQUEST_ID=$(jq -r '."opc-work-request-id"' <<< "$CREATED_LB")
     echo "Create Load Balancer Work Request ID: $WORK_REQUEST_ID"
 
@@ -205,6 +216,16 @@ function create_lb_with_minimum_then_add_related_resources() {
         --wait-for-state SUCCEEDED \
         --max-wait-seconds 300
 
+    # We can create multiple hostnames here to eventually attach them to load balancer listener.
+    # Each hostname can correspond to an application served from your backend.
+    oci lb hostname create --load-balancer-id $LB_ID \
+        --hostname host1.name.com \
+        --name hostname1
+
+    oci lb hostname create --load-balancer-id $LB_ID \
+        --hostname host2.name.com \
+        --name hostname2
+
     # Now that we have our certificates, backend set and path route set, we can add a listener. We need to specify a backend set which exists (e.g. the one we made)
     #
     # The valid values for --protocol can be found via "oci lb protocol list"
@@ -218,6 +239,7 @@ function create_lb_with_minimum_then_add_related_resources() {
         --ssl-certificate-name my_cert_bundle \
         --ssl-verify-depth 3 \
         --ssl-verify-peer-certificate false \
+        --hostname-names '["hostname1", "hostname2"]' \
         --path-route-set-name PathRouteSetName
 
     # Print out information about the load balancer

scripts/create_load_balancer_example/create_load_balancer_all_complex_params_with_comments.json

@@ -49,12 +49,27 @@
             }
         }
     },
+    "hostnames": {
+        // The content here aligns with the example in the hostnames_with_comments.json file
+        "hostname1": {
+            "hostname": "host1.name.com",
+            "name": "hostname1"
+        },
+        "hostname2": {
+            "hostname": "host2.name.com",
+            "name": "hostname2"
+        }
+    },
     "listeners": {
         // The content here aligns with the example in the listeners_with_comments.json file
         "listenerName": {
             "defaultBackendSetName": "backendSetName",
+            "hostnameNames": [
+                "hostname1",
+                "hostname2"
+            ],
             "port": 8080,
-            "protocol": "HTTP"
+            "protocol": "HTTP",
             "pathRouteSetName": "PathRouteSetName"
         }
     },

scripts/create_load_balancer_example/hostnames_with_comments.json

@@ -0,0 +1,25 @@
+{
+  /*
+   * Each entry in this dictionary represents a virtual hostname. You can assign a virtual hostname
+   * to any listener you create for your load balancer. Each hostname can correspond to an
+   * application served from your backend. For more information on virtual hostnames, see
+   * https://docs.us-phoenix-1.oraclecloud.com/Content/Balance/Tasks/managingrequest.htm#vhost
+   */
+
+   // The key value below should be the name of the "hostname" resource.
+  "hostname1": {
+
+    // hostname is the URL associated with the listener and hence a backend set.
+    // Multiple hostnames, backed by DNS entries, can point to the same load balancer IP address.
+    // Once the request reaches the LB service the hostname in  used to identify the backendset
+    "hostname": "host1.name.com",
+
+    // The name attribute mentioned below is optional since we already mention the name of the resource as
+    // the key above.
+    "name": "hostname1"
+  },
+  "hostname2": {
+    "hostname": "host2.name.com",
+    "name": "hostname2"
+  }
+}

scripts/create_load_balancer_example/listeners_with_comments.json

@@ -15,6 +15,20 @@
         // --backend-sets option when doing a "oci lb load-balancer create")
         "defaultBackendSetName": "backendSetName",
 
+        // This should match the name of hostname group which has been/will be associated with a load balancer (e.g. via the
+        // --hostnames option when doing a "oci lb load-balancer create")
+        // You can assign one or more virtual hostnames to any listener you create for your load balancer.
+        // Each hostname can correspond to an application served from your backend.
+        "hostnameNames": [
+            "hostname1",
+            "hostname2"
+        ],
+
+        // This should match the name of a path route set which has been/will be associated with a load balancer (e.g. via the
+        // --path-route-sets option when doing a "oci lb load-balancer create")
+        // A path route set includes all path route strings and matching rules that define the data routing for a particular listener.
+        "pathRouteSetName": "PathRouteSetName",
+
         "port": 8080,
 
         // You can get valid protocol values by calling "oci lb protocol list"
@@ -24,7 +38,15 @@
     // as many times as necessary to add all the listeners you need
     /*
     , "mySecondListenerName": {
-        "defaultBackendSetName": "backendSetName",
+        "connectionConfiguration": {
+            "idleTimeout": 0
+        },
+        "defaultBackendSetName": "backendSetName2",
+        "hostnameNames": [
+            "hostname3",
+            "hostname4"
+        ],
+        "pathRouteSetName": "pathRouteSetName2",
         "port": 80,
         "protocol": "HTTP",
         "sslConfiguration": {

setup.py

@@ -30,7 +30,7 @@ def open_relative(*path):
 
 
 requires = [
-    'oci==1.3.19',
+    'oci==1.3.20',
     'arrow==0.10.0',
     'certifi',
     'click==6.7',