Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring Junos Space Virtual Appliances and Databases

    This section describes procedures that you need to perform to configure the Junos Space components.

    Configuring a Junos Space Cluster

    If you use a redundant Contrail Service Orchestration installation, you must configure a cluster for the Junos Space Virtual Appliances. You configure the cluster manually whether you provisioned the VMs with the provisioning tool or manually.

    To configure the Junos Space cluster:

    1. Log in to the Junos Space Network Management Web GUI.

      The default login credentials are:

      • Username—super
      • Password—juniper123

      The dashboard and the Password Expiry dialog box appear.

    2. Click Yes in the Password Expiry dialog box to change the default password.

      The Change User Settings dialog box appears.

    3. Specify a new password and click OK.

      The password is updated.

    4. Log out, then log in again with your new password.
    5. In the left navigation bar, select Administration > Fabric.

      The Administration > Fabric page appears.

    6. In the toolbar, click Add Node.

      The Add Node to fabric dialog box appears.

      1. For the Node Type field, select DB Node.
      2. Specify the hostname and IP address of the VMs for the primary and secondary Junos Space databases.
      3. For the primary database, specify the IP address of the VM for the primary Junos Space Virtual Appliance.
      4. Click Add.
    7. In the toolbar, click Add Node.

      The Add Node to fabric dialog box appears.

      1. For the Node Type field, select JBoss.
      2. Specify the hostname and IP address of the VM for the secondary Junos Space Virtual Appliance.
      3. Click Add.

        The Administration > Fabric page appears.

    8. Wait approximately 30 minutes for the nodes in the cluster to become active.

    Configuring MySQL for the Junos Space Databases

    When you provision the VMs manually, you must configure MySQL for the Junos Space databases for both non-redundant and redundant Contrail Service Orchestration installations. If you provision the VMs with the provisioning tool, you do not need to complete this procedure, because the tool takes care of the configuration.

    To configure MySQL for the Junos Space database:

    1. Using the credentials you specified when you provisioned the VMs, log in to the appropriate VM:
      • For a Junos Space cluster, log in to the VM for the primary Junos Space database.
      • For a standalone Junos Space Virtual Appliance, log in to the VM for the Junos Space Virtual Appliance.
    2. Open the file /var/chroot/mysql/etc/my.cnf with a text editor.
    3. in the [mysqld] section, add the following lines after the line
      performance_schema = off:
      bind-address = 0.0.0.0
      innodb_large_prefix=on
      innodb_file_format=barracuda
      innodb_file_per_table=true
      
    4. Save the file.
    5. Restart the MySQL database. For example:
      admin@space-db1:~/# /etc/init.d/mysql restart

      The MySQL database restarts.

    6. For a Junos Space cluster, repeat Steps 1 through 5 for the secondary MySQL database.

    Configuring MySQL to Communicate with the Contrail Service Orchestration Components

    You must complete this procedure for both non-redundant and redundant Contrail Service Orchestration installations, whether you provisioned the VMs manually or with the provisioning tool.

    To configure MySQL to communicate with the Contrail Service Orchestration components:

    1. Using the credentials you specified when you provisioned the VMs, log in to the appropriate VM:
      • For a redundant Contrail Service Orchestration installation, log in to the VM for the primary Junos Space database.
      • For a non-redundant Contrail Service Orchestration installation, log in to the VM for Junos Space.
    2. Configure access to MySQL through remote authentication. For example, if the MySQL remote authentication username is admin and the remote authentication password is secret123, type:
      admin@space1:~/# mysql -h localhost -uroot -pnetscreen -e "grant all on *.* to 'admin'@'%' identified by 'secret123'"
    3. Assign privileges for all MySQL operations to components with access to MySQL.
      admin@space1:~/# mysql -h localhost -uroot -pnetscreen -e "grant all privileges ON *.* to 'admin'@'%' WITH GRANT OPTION"

    Disabling the Firewall on the Junos Space Virtual Appliances

    If you provisioned the Junos Space VMs manually and not with the provisioning tool, you must disable the firewall on each Junos Space Virtual Appliance in the Cloud CPE Centralized Deployment Model. For information on this procedure, see the Junos Space Virtual Appliance documentation at https://www.juniper.net/techpubs/en_US/release-independent/junos-space/index.html.

    Installing the Patch for Third-Party VNFs

    You must install the Junos Space patch for third-party VNFs for both non-redundant and redundant Contrail Service Orchestration installations, whether you provisioned the VMs with the provisioning tool or manually.

    1. Copy the patch installer package file to the VM in which the primary Junos Space Virtual Appliance resides.
    2. Expand the patch installer package, which has a name specific to the release. For example, if the name of the installer package is patch-version.tar.gz:
      root@host:~/# tar xvf patch-version.tar.gz
    3. Access the directory that contains the installation files. For example:
      root@host:~/# cd patch-version
    4. Apply the patch.
      1. Run the patch.sh script and enter 1 at the prompt.
      2. Run the patch.sh script a second time and enter 2 at the prompt.
      3. Run the patch.sh script a third time and enter 3 at the prompt.

      For example:

      root@host:~/patch-version# ./patch.sh
      root@host:~/patch-version# 1
      root@host:~/patch-version# ./patch.sh
      root@host:~/patch-version# 2
      root@host:~/patch-version# ./patch.sh
      root@host:~/patch-version# 3

      This action installs the patch on both Junos Space Virtual Appliances and databases.

    Modified: 2016-06-01