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

    Installing and Configuring the Cloud CPE Centralized Deployment Model

    Customizing the Configuration File for the Cloud CPE Centralized Deployment Model Installation

    The Cloud CPE Centralized Deployment Model installer uses a configuration file, which you must customize for your network. After you customize the configuration file, you run the installer to deploy and configure the software on the servers and VMs. An example configuration file is located in the server_manager directory of the installer and has the name csp_topology_example.conf. The configuration file is in YAML format.

    To customize the configuration file:

    1. Log in as root to the installer VM.
    2. Access the directory that contains the example configuration file. For example, if the name of the installer is cspVersion:
      root@host:~/# cd cspVersion/server_manager
    3. Make a copy of the example configuration file and name it csp_topology.conf
      root@host:~/cspVersion/server_manager# cp csp_topology_example.conf csp_topology.conf
    4. Open the file csp_topology.conf with a text editor.
    5. In the [SPACE] section, specify the following values for the Junos Space Virtual Appliance.
      • ip—IP address for the virtual appliance
      • user—Username for logging in to the virtual appliance
      • password—Password for logging in to the virtual appliance
    6. In the [MYSQL] section, specify the following values for the Junos Space database.
      • ip—IP address for the VM for the database
      • user—Username for logging in to the database
      • password—Password for logging in to the database
    7. In the [TARGETS] section, specify the following values for the network on which the Cloud CPE Centralized Deployment Model resides.
      • gateway—IP address of the gateway router
      • cidr—Range of IP addresses on the network
      • domain—Domain for the Cloud CPE Centralized Deployment Model
      • dns_servers—Comma-separated list of DNS name servers, including DNS servers specific to your network.
      • timezone—Time zone of the host, in the format specified in the Internet Assigned Numbers Authority (IANA) Time Zone Database. The default is the time zone of the installer VM.
      • ntp_servers—Comma-separated list of Network Time Protocol (NTP) servers. For networks within firewalls, specify NTP servers specific to your network.
      • servers—Comma-separated list of hostnames of the following components:
        • Server on which you install Contrail OpenStack
        • The following VMs on the Contrail Service Orchestration node:
          • VM that contains Network Service Orchestrator and other components.
          • VM that contains Custom Contrail.
          • VM that contains Network Service Designer and other components.
          • VM that contains the primary instance of Service and Infrastructure Monitor.
          • VM that contains the secondary instance of Service and Infrastructure Monitor.
          • VM that contains the controller and the load balancer for Service and Infrastructure Monitor.
    8. Specify the following BGP parameters for the MX Series router.
      • external_bgp—IP address of the BGP peer
      • router_asn—Autonomous system number used for the BGP peer
    9. Using the keystone settings that you configured for Contrail OpenStack, specify the following settings:

      Note: You can view the keystone settings on the Contrail Configure and Control Node in the files /etc/contrail/keystonerc and /etc/contrail/openstackrc.

      • keystone_password—OpenStack keystone password
      • keystone_tenant—OpenStack keystone tenant
      • keystone_username—OpenStack keystone username
      • service_token—OpenStack keystone service token
    10. Specify the following configuration values for the servers and VMs that you specified in Step 7.
      • [hostname]—Name of the machine
      • management_address—IP address of the Ethernet management (primary) interface
      • management_interface—Name of the Ethernet management interface, typically eth0
      • management_mac—MAC address for the host
      • data_net_address—IP address of the interface used to transmit data on a physical server
      • data_interface—Name of the Ethernet interface used to transmit data on a physical server
      • data_mac—MAC address for the interface used to transmit data on a physical server
      • gateway—IP address of the gateway for the host. If you do not specify a value, the value defaults to the gateway defined in the [TARGETS] section
      • hostname—Hostname of the machine.

        Caution: If you do not configure DNS for your network, specify the IP address of the machine in the hostname field. Otherwise, the Cloud CPE Centralized Deployment Model may not work correctly.

      • username—Username for logging in to the machine
      • password—Password for logging in to the machine
      • Roles—Components installed on the machine:
        • contrail—Server on which you install Contrail OpenStack
        • custom_contrail—Contrail software to support Identity and Access Manager component
        • iam—Identity and Access Manager
        • loadbalancer—Load-balancing software, which balances the volume of traffic for software components that offer redundancy
        • naas—Network as a Service, an application that manages internal event messages
        • nsd—Network Service Designer
        • nso—Network Service Orchestrator
        • sim—Icinga server software
        • sim_client—Icinga client software, which resides on the same machine as any component monitored by Service and Infrastructure Monitor
        • sim_primary—Primary instance of Server and Infrastructure Monitor, which works with the secondary instance to provide redundancy
        • sim_secondary—Secondary instance of Server and Infrastructure Monitor, which works with the primary instance to provide redundancy
        • tssm—Cloud CPE Tenant, Site and Service Manager
        • vnfm—VNF Manager
    11. (Optional) If you want to reimage the Ubuntu operating system on the Contrail Cloud Platform server with the Ubuntu version included in the installer, specify values In the [ccp-host] section for the following Intelligent Platform Management Interface (IPMI) parameters:

      Caution: Do not specify IPMI parameters for VMs. Doing so may prevent the Cloud CPE Centralized Deployment Model from working.

      • ipmi_address—IP address for IPMI.
      • ipmi_username—Username for IPMI operations.
      • ipmi_password—Password for IPMI operations.
      • ipmi_type = ipmilan—Type of Intelligent Platform Management Interface (IPMI). The Cloud CPE Centralized Deployment Model supports IPMI over LAN (ipmilan) and Integrated Lights-Out (ilo). The default is ipmilan.
    12. Save the file.

    The following example shows a customized configuration file:

    
    [DEPLOY_OPTIONS]
    
    [SPACE]
    ip = 192.0.2.55
    user = admin
    password = passw0rd
    
    [MYSQL]
    ip = 192.0.2.65
    admin_user = admin
    admin_password = passw0rd
    
    [TARGETS]
    gateway = 192.0.2.1
    cidr = 192.0.2.0/24
    
    domain = location.example.net
    dns_servers = $next_server, 8.8.8.8
    timezone = UTC
    ntp_servers = ntp.example.net, ntp.ubuntu.com
    servers = ccp-host, c-c-vm, nsd-vm, nso-vm, sim1-vm, sim2-vm, simcontroller-vm
    
    external_bgp = 192.0.2.60
    router_asn = 64512
    
    keystone_password = contrail123
    keystone_tenant = admin
    keystone_username = admin
    service_token = 229537
      
    [ccp-host]
    management_address = 192.0.2.10/24
    management_interface = eth0
    management_mac = 00:25:90:C8:11:86
    data_net_address = 192.0.2.12/24
    data_interface = eth1
    data_mac = 00:25:90:C8:11:88
    gateway = 192.0.2.1
    hostname = ccp-host
    username = root
    password = passw0rd
    ipmi_address = 192.0.2.25
    ipmi_username = ADMIN
    ipmi_password = ADMIN
    ipmitype = ilo
    roles = contrail, sim_client
    
    [c-c-vm]
    management_address = 192.168.1.3/24
    hostname = c-c-vm
    username = root
    password = passw0rd
    roles = custom_contrail
    
    [nso-vm]
    management_address = 192.168.1.4/24
    hostname = nso-vm
    username = root
    password = passw0rd
    roles = naas, nso, vnfm, tssm, iam, sim_client 
    
    [nsd-vm]
    management_address = 192.168.1.5/24
    hostname = nsd-vm
    username = root
    password = passw0rd
    roles = nsd, sim-client
    
    [sim1-vm]
    management_address = 192.168.1.6/24
    hostname = sim1-vm
    username = root
    password = passw0rd
    roles = sim_primary
    
    [sim2-vm]
    management_address = 192.168.1.7/24
    hostname = sim2-vm
    username = root
    password = passw0rd
    roles = sim_secondary
    
    [simcontroller-vm]
    management_address = 192.168.1.8/24
    hostname = simcontroller-vm
    username = root
    password = passw0rd
    roles = loadbalancer, sim

    Deploying the Cloud CPE Centralized Deployment Model

    After you have completed all previous installation tasks, you can run the installer from the installer host. To deploy the Cloud CPE Centralized Deployment Model:

    1. Log in to the installer VM as root.
    2. Access the directory for the installer, which has a name specific to the release. For example, if the name of the installer directory is cspVersion:
      root@host:~/# cd /~/cspVersion/
    3. Run the installer.
      root@host:~/cspVersion/# ./install_csp_solution.sh

      The installation begins and you see status messages about the installation.

    4. During installation, view the log file csp_deploy.log to observe detailed messages about the installation of the components.
      root@host:~/cspVersion/# cd logs
      root@host:/cspVersion/logs# tailf csp_deploy.log

      In the same directory, you can also view the log file csp_console.log

    5. When you see that the deployment is complete, run the verification script. For example:
      root@host:~/# cd /~/cspVersion/
      root@host:~/cspVersion# ./verify_csp_solution.sh

      If the deployment script installs all components successfully, the verification script returns confirmation that the components are running correctly.

      The verification script returns error messages if:

      • The deployment script was not able to install one or more of the software components.
      • One or more software components has not started.
      • The software components are not connected correctly.
      • The software components are not exchanging tokens correctly.

    Modified: 2016-02-01