Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Select an Edge Site MTN1 (or MTN2) by clicking on the radio button in the GUI table displayed in the Home page. These are the two default sites available in the Seed code.
  2. For the selected Edge site, select a Blueprint (Rover or Unicycle) from the drop-down menu.
  3. Click on Upload button (in the Blueprint column), this will open a pop-up dialog
  4. Provide the edge site-specific details such as:
    1. Host IP address
    2. Host user
    3. Host password.
    4. Click on Browse button, select the input file for Blueprint - Rover (Single-Node Cluster). 
      The input file is a property file that stores information in key-value format.  Sample input file used for ‘Rover’ deploy: 

      Info

      Copy and paste the below contents in to a file, and save it as rover.txt. Use this file for uploading as mentioned in step 4.d above.

      Verify the configuration details as applicable to your environment. For more details refer to Appendix - Edge Site Configuration


      Code Block
      languagetext
      titlerover.txt
      # Copyright 2018 AT&T Intellectual Property.  All other rights reserved.
      #
      # Licensed under the Apache License, Version 2.0 (the "License");
      # you may not use this file except in compliance with the License.
      # You may obtain a copy of the License at
      #
      #     http://www.apache.org/licenses/LICENSE-2.0
      #
      # Unless required by applicable law or agreed to in writing, software
      # distributed under the License is distributed on an "AS IS" BASIS,
      # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
      # See the License for the specific language governing permissions and
      # limitations under the License.
      
      # host name for server
      SRV_NAME=aknode42
      
      # out of band interface information for server (idrac/ilo/etc)
      SRV_OOB_IP=192.168.41.42
      SRV_OOB_USR=root
      SRV_OOB_PWD=calvin
      
      # server oem - Dell or HPE (case sensitive)
      SRV_OEM=Dell
      
      # name of network interface used during build when ipxe.efi is booted and when os is booted
      # ipxe numbers interfaces from 0-n in pci bus order. 
      # the netX value will depend on how many nics are in the server 
      # and which pci device number is assigned to the slot
      SRV_IPXE_INF=net4
      SRV_BLD_INF=enp94s0f0
      SRV_BOOT_DEVICE=sdg
      
      # ipxe script to use - based on the os version and kernel to install
      # valid options are script-hwe-16.04.5-amd64.ipxe or script-16.04.5-amd64.ipxe
      SRV_BLD_SCRIPT=script-hwe-16.04.5-amd64.ipxe
      
      # template xml file to set bios and raid configuration settings
      SRV_BIOS_TEMPLATE=dell_r740_g14_uefi_base.xml.template
      SRV_BOOT_TEMPLATE=dell_r740_g14_uefi_httpboot.xml.template
      SRV_HTTP_BOOT_DEV=NIC.Slot.7-1-1
      
      # tempalte to run to configure OS after first boot
      # current options are: firstboot.sh.template, firstboot-genesis.sh.template or firstboot-airship-iab.sh.template
      SRV_FIRSTBOOT_TEMPLATE=firstboot-airship-iab.sh.template
      
      # VLAN to use during build and for final network configuration
      SRV_VLAN=41
      
      # basic network information for dhcp config and final server network settings
      SRV_MTU=9000
      SRV_IP=192.168.2.42
      SRV_SUBNET=192.168.2.0
      SRV_NETMASK=255.255.255.0
      SRV_GATEWAY=192.168.2.200
      SRV_DNS=192.168.2.85
      SRV_DOMAIN=lab.akraino.org
      SRV_DNSSEARCH=lab.akraino.org
      SRV_NTP=ntp.ubuntu.org
      
      # root password for server being built
      SRV_PWD=akraino,d
      
      # network bond information
      SRV_BOND=bond0
      SRV_SLAVE1=enp94s0f0
      SRV_SLAVE2=enp94s0f1

...


5. Click on Submit. This will upload the input file and the site details into the portal.

...

  1. Navigate to the Akraino Blueprint > Add-Ons page via the left navigation menu.
  2. Select a deployed edge site on the Install ONAP page.
  3. Click on Upload button (in the sites column), this will open a pop-up dialog
  4. Click on Browse button, select the input file for ONAP (parameters.env file).  
    The input file is a property file that stores information in key=value format.  Sample input file used for ONAP: 

    parameters.env
    Info
    title

    Copy and paste the below contents in to a file, and save it as parameters.env. Use this file for uploading as mentioned in step 4 above.

    Verify the configuration details as applicable to your environment. For more details refer to Appendix - ONAP Configuration


    Code Block
    languagetext
    titleparameters.envbash
    # Parameters that will be populated by camunda engine
    parameters:
    
      public_net_name: public
    
      public_physical_net_provider_name: bond0
    
      provider_segmentation_id: 50
    
      public_physical_net_type: vlan
    
      public_subnet_name: public
    
      public_subnet_cidr: 172.24.8.0/24
    
      public_subnet_allocation_start: 172.24.8.221
    
      public_subnet_allocation_end: 172.24.8.225
    
      public_subnet_dns_nameserver: 8.8.8.8
    
      public_subnet_gateway_ip: 172.24.8.1
    
      flavor_name: m1.onap
    
      onap_vm_public_key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCWcbAk6SJxvYf4CM75JGWsQ38149Fhu4dUXUmnmASFWuvPJ6sCpoGyMPQdEMEt3wITCFGfS4gw6eQO39NUaS4JqWYjNN6sejernldwyqGwz42H/rn7CL0xhbCql9upWF+2bm5X46UgSwZBYcLxW0BrOh+0lxkON+2qOGZFbtEcOUeOVmRSJdBuxczyGD5i6zusITJ00scqfNTCyRLm8JiHlW9SY43iyj3Lq0cDxYQ97fKX2F+0D/JfnWPu/2v+HaJWDpfpNG/Mo/SVzNAwE997DMY1ZD9jJsoYPr8UWypQQJUMldn3P+ERaswNTXnGbmCnwRGlj7IANnmGCc7koi6t root@csoaiclab01-85
    
      http_proxy:
    
      https_proxy:
    
      no_proxy:
    
      keystone_admin_password: password
    
      onap_tenant_password: amsterdam
    
      onap_artifacts_http_repo:
    
    


  5. User will see the "file uploaded successfully" message in the sites column. Then, "Install ONAP" button gets enabled.
  6. Click "Install ONAP" to begin the installation.
  7. The ONAP status changes from ‘Not started’ to ‘In progress’ to ‘Complete’.
  8. ONAP VM will be created successfully after the job completes.  It may take several hours for ONAP to become operational.

...