• Topic
  • Discussion
  • ODS.VirtPayAsYouGoEBSBackedAMI(Last) -- DAVWikiAdmin? , 2017-06-29 07:34:24 Edit WebDAV System Administrator 2017-06-29 02:34:24

    Deploying the Virtuoso Pay As You Go (PAGO) EBS-backed EC2 AMI

    Introduction

    In addition to the Instance-backed EC2 AMI? that has been in existence since 2008, Virtuoso is now also available as an EBS-backed EC2 AMI based on your choice of License Model --

    • Bring You Own License, or BYOL?
    • Pay As You Go, or PAGO (documented here)

    With either License Model, you will be starting with a preconfigured Virtuoso instance. The fundamental benefits provided by this type of AMI include:

    • Virtuoso DBMS Server is preinstalled with basic tuning for the host operating system.
    • You can start and stop this Virtuoso instance without having to terminate its host AMI.
    • With the hourly model, you pay only for the time the AMI is used.

    Prerequisites

    • An Amazon Web Services (AWS) account.
    • Recently created AWS accounts will have been automatically signed up for the Amazon S3 and EC2 Web Service. If you created your AWS account a long time ago, you may now need to manually sign up for these services.
    • Ensure a AWS security group allowing access to ports 22 (SSH) and 80 (HTTP) is used.

    Instantiating & Using Virtuoso 7.2 PAGO Enterprise Edition via Web Interface

    1. Use one-click or aws-console (at https://console.aws.amazon.com/) launch options to start the Virtuoso Universal Server 7.2 (Enterprise-- Cloud PAGO Edition)

      EC2 instance launch dialog, PAGO

    First-time Setup & Usage Notes

    These steps are only necessary immediately after instantiating the AMI, when you start the Virtuoso Database for the first time. This section may subsequently be ignored, as it is not necessary after AMI reboots.

    1. ssh into your instantiated AMI using:

      ssh -i {secure-pem-file} ec2-user@{amazon-ec2-dns-name-or-ip-address}

    2. Start the Virtuoso DBMS Server against the DBpedia Database by issuing the command:

      sudo /etc/rc.d/init.d/virtuoso restart

    3. Retrieve the AMI instance-id from the AMI properties presented by the Amazon AWS console UI, or by executing the following in the Linux shell:

      curl http://169.254.169.254/latest/meta-data/instance-id

    4. Go to http://{amazon-ec2-ami-dns-name-or-ip-address}/conductor -- to change the default password of this instance.
    5. At the authentication challenge, log in as the dba user, with the AMI instance-id as the password.
    6. Change the password for the 'dba' user.

    Administering Virtuoso Instance via SSH

    All scripts for starting and stopping the Virtuoso instance are found in the following locations --

    • /etc/rc.d/init.d -- scripts that enable automatic database server instantiation at operating system (AMI) boot or reboot time
    • /opt/virtuoso -- scripts for starting and stopping the database server within a running operating system (AMI)

    OpenLink? License Manager

    • Start the License Manager:

      /etc/rc.d/init.d/oplmgr start

    • Stop the License Manager

      /etc/rc.d/init.d/oplmgr stop

    • Restart the License Manager

      /etc/rc.d/init.d/oplmgr restart

    Virtuoso the Server

    • Start the Virtuoso Server:

      /etc/rc.d/init.d/virtuoso start

    • Stop the Virtuoso Server:

      /etc/rc.d/init.d/virtuoso stop

    • Restart the Virtuoso Server:

      /etc/rc.d/init.d/virtuoso restart

    Virtuoso Database Instance Interaction

    1. Set the Virtuoso environment variables by running the command

      . /opt/virtuoso/virtuoso-enterprise.sh

    2. Run the Virtuoso "isql" command line tool to connect to the database. Note: your EC2 AMI's instance-id will be the dba user's password, until you change it.

      $ isql 1111 -U dba -P i-123abc321 Connected to OpenLink Virtuoso Driver: 07.10.3214 OpenLink Virtuoso ODBC Driver OpenLink Interactive SQL (Virtuoso), version 0.9849b. Type HELP; for help and EXIT; to exit. SQL>

    3. Run the "tables" command to obtain a list of tables in the default schema

      SQL> tables; Showing SQLTables of tables like 'NULL.NULL.NULL', tabletype/colname like 'NULL' TABLE_QUALIFIER TABLE_OWNER TABLE_NAME TABLE_TYPE REMARKS VARCHAR VARCHAR VARCHAR VARCHAR VARCHAR _______________________________________________________________________________ DB DBA ADMIN_SESSION SYSTEM TABLE NULL DB DBA ADM_OPT_ARRAY_TO_RS_PVIEW SYSTEM TABLE NULL DB DBA ADM_XML_VIEWS SYSTEM TABLE NULL . . . DB DBA SYS_SQL_INVERSE SYSTEM TABLE NULL DB DBA SYS_TRIGGERS SYSTEM TABLE NULL DB DBA SYS_VIEWS SYSTEM TABLE NULL 209 Rows. -- 1890 msec. SQL>

    4. You can stop the Virtuoso Database Server by running:

      virtuoso-stop.sh

    5. You can restart the Virtuoso Database Server by running:

      virtuoso-start.sh

    Performance Notes

    In regards to performance, please be aware of the following:

    1. We currently bundle a 10 Database Sessions and 4 CPU Affinity license with this AMI -- Database & CPU Affinity upgrade licenses are available as upgrade options.
    2. There are a range of AMIs choices covering system memory and CPU combination.

    Collectively, the factors above affect the performance of your DBpedia instance. Thus, use EC2 Instance Types with more memory and CPU cores for best performance.

    Note by default this AMI is configured to run on a m3.large EC2 Instance Type, thus if a larger EC2 Instance Type is chosen then the NumberOfBuffer and MaxDirtyBuffers parameters in the /opt/virtuoso/dbpedia/dbpedia.ini configuration file, should be increased to the available memory as detailed in the Virtuoso Performance Tuning Guide:

    EC2 Instance Type System RAM NumberOfBuffers? MaxDirtyBuffers?
    m3.large 7 GB 680000 500000
    r3.large 15 GB 1360000 1000000
    r3.xlarge 30.5 GB 2720000 2000000
    r3.2xlarge 61 GB 5450000 4000000

    and the Virtuoso server restarted as detailed above.

    Troubleshooting

    If you are unable to start your Virtuoso instance as described in the installation and usage steps above, please perform the following steps to get your instance running:

    1. cd to /opt/virtuoso
    2. execute: . ?./ ent*?.sh
    3. cd to /opt/virtuoso/database
    4. execute: virtuoso -c virtuoso -f

    If successful, you can retry the alternative options such as:

    • /etc/init.d/virtuoso restart
    • /etc/init.d/virtuoso start

    Related Items

    CategoryHowTo CategoryODS CategoryVirtuoso CategoryDocumentation CategoryEC2?