Welcome to Community Edition

Nutanix Community Edition is a free version of Nutanix AOS, which powers the Nutanix enterprise platform. The Community Edition of AOS is designed for people interested in test driving its main features on their own test hardware and infrastructure. As stated in the end user license agreement, Community Edition is intended for internal business operations and non-production use only.

Before you begin, consider that the commercially-available Nutanix NX Series systems are tuned for performance. The enterprise-ready version of AOS is bundled as the engine driving our hyperconverged compute and storage platform. You should not expect to achieve comparable benchmark numbers. For example, the NX Series systems include 10 GbE network interfaces, high core count dual CPUs, large amounts of memory, and high performance enterprise-class solid-state drives (SSDs).

Even so, Community Edition performance will be sufficient for a number of VMs per node, given enough memory, CPU, and network resources.

Table: What’s In Community Edition
Hypervisor Acropolis hypervisor with virtualization management
Single pane of glass control Prism web console to manage the cluster
Command-line management Nutanix command line (nCLI)
Ability to add nodes to the cluster One, three, or four nodes can comprise a cluster
Ease of installation and use Install and boot the hypervisor and AOS environment from USB device

Support for and Learning More About Community Edition and Acropolis (AOS)

The most support for Community Edition is available through the Next Community Edition forum. Nutanix asks that you share your experiences and lessons learned with your fellow Community Edition users.

You can also visit the following pages for more information about Acropolis and the Nutanix architecture.

Recommended Community Edition Hardware

The following table shows our recommendations for hardware to use with Community Edition, based on hardware we have tested. However, like other Community Edition users, you might find that other hardware works as well as the recommended types. Please see these topics in the Community Edition Next Forum:

Table: System Configuration
Component Recommendation Notes
CPUs Intel CPUs with VT-x support. 4 core minimum; 2 cores dedicated to the Controller VM
System memory 16 GB minimum

One Controller VM per node with optional deduplication/compression features and additional memory for one or more user VMs

32 GB or greater recommended for AOS features such as deduplication,compression, or more user VMs
Network interface card (NIC) Intel-based NIC Some Community Edition users have reported success using Broadcom NICs.
Host bus adapter (HBA) Community Edition supports Advanced Host Controller Interface (AHCI) , or LSI controller with:

  • IT mode (Nutanix testing shows better performance than IR)
  • IR mode with pass-through
  • IR mode with RAID-0
Storage Devices, All Drives Maximum number of / drives per node is 4. Some Community Edition users have reported success using more than 4 drives.
Storage Devices, Cold Tier 500 GB or greater available

Maximum 18 TB (3 x 6 TB HDDs)

Hard drive (HDD) or Solid-state drive (SSD) for cold-tier storage
Storage Devices, Hot Tier Flash Single 200 GB SSD or greater
  • Place SSD(s) before HDDs (commonly Bay 0 or Bay 1). The first bay number varies depending on manufacturer labeling.
  • Community Edtion 2016.12.22 supports NVMe-based drives. These drives are not supported on previous Community Edition versions.
Boot device One 8 GB capacity device per node. It can be an external or internal device. Nutanix has successfully tested and used external USB drives and internal devices such as a SATA DOM. USB 3.0 media recommended.

Note: If you use a USB drive, do not remove the USB drive or device at any time during your use of Community Edition.
Firmware Consider updating the firmware for any devices or hardware you plan to use with Community Edition to the latest edition or edition recommended by the hardware vendor.
Table: Other Recommendations
Component Recommendation
Cluster size Community Edition allows you to install single-node, three-node, and four-node clusters.

Depending on your available hardware, Nutanix recommends a three-node cluster to exercise the features of Community Edition most effectively.

DHCP Server If you are using a DHCP server, ensure that static IP addresses are assigned for hypervisor hosts and Controller VMs.

Nutanix recommends that you not use dynamic IP addressing for hosts or Controller VMs.

Imaging software
  • : use the included dd utility
  • Mac OS X: use the included dd utility
  • Windows: ImageUSB from PassMark Software (freeware)

Community Edition Licensing Requirements

To use the Community Edition, Nutanix requires the following actions and access. If you fail to meet these requirements, access to your cluster will be blocked. The cluster remains operating but you will be unable to log on to it. Otherwise, there are no licensing file requirements as with the commercially-available Nutanix products.

Table: Licensing Requirements
Requirement Enforcement
Admin account password change from default When you first log on to the Prism web console with the admin account credentials, you must immediately change the admin user password from its default.
Nutanix Next account with log on credentials and the Community Edition role enabled After you first log on to the Prism web console and change the admin credentials, you are prompted to provide these credentials.
Outgoing ports 80 or 8443 opened through your firewall An automated feedback mechanism named Pulse that sends cluster alerts and usage statistics to Nutanix requires internet connectivity and port access.
Install any pending Community Edition updates Nutanix make updates available occasionally. When an upgrade is available, but not yet downloaded, you must upgrade within 30 calendar days. You must install the available upgrade immediately once you have downloaded it.

If you fail to meet these requirements, access to your cluster will be blocked. The cluster remains operating but you will be unable to log on to it.

Preparing to Install Community Edition

Before you begin

Before you install Community Edition:

  1. Ensure that you have a valid account and log on credentials for the Next Community Edition forum, and that the account has the Community Edition role associated with it.
  2. Download the Community Edition software at the Community Edition forum topic Nutanix Next Community Download Software. The latest release is usually in the most recent topic in the thread.
  3. Prepare the USB drive or other boot device with the downloaded image with your favorite imaging software.

    Tip: If you are using a Linux or Mac OS X environment, you can use the dd command to image the device:

    dd if=ce.img of=/dev/sdX

    where X is the USB drive letter.

    • [Linux only] To find the USB drive letter, check the output of this command:
      for i in /dev/sd?; do udevadm info --query=all --name=$i; done
    • (OS X only) List any storage devices:
      diskutil list
    • (OS X only) Show information about a specific device:
      diskutil info /dev/X

      where X is the USB drive.

    (OS X only) For improved performance when imaging, specify a block size of 1 MB. For example:dd if=ce.img of=/dev/rdisk2 bs=1m

What to do next

Have the following networking information ready for installation.

Caution: Nutanix recommends that you not use dynamic IP addressing for hosts or Controller VMs. If you are using a DHCP server, ensure that it is set to assign static IP addresses for hosts and Controller VMs.

Community Edition reserves IP addresses 192.168.5.0 through 192.168.5.254 for internal use. Nutanix recommends using an IP address in the network ranges 10.x.x.x or 172.x.x.x for the Host and Controller VM.

Table: Network Information Checklist
Host IP address

(for the Community Edition hypervisor host)

Host subnet mask
Host gateway
Controller VM IP address

(this becomes the virtual IP address that enables you to log in and manage the cluster through the Prism web console or an SSH terminal connection)

Controller VM subnet mask
Controller VM gateway

Installing Community Edition

Before you begin

Ensure you have prepared the USB drive or device and gathered your network information as described in Preparing to Install Community Edition.

Note: Do not remove the USB drive or device at any time during your use of Community Edition.
  1. Set the primary boot device to USB (or SATA DOM, if that’s the case) on your server (also known as the node) where you are going to install Community Edition.
  2. If you are using an external boot device, insert the imaged USB drive or device into the node and reboot the node.The node boots into the Nutanix Acropolis image.
  3. Log on with the user name of install. A password is not required.
  4. Select a keyboard layout by using the Up or Down arrow keys.
  5. Read the WARNING about how performance tests will be run on the discovered disks.
    • Press Tab to move to Proceed if you are OK with the I/O performance tests, which will erase any existing data on the disks.
    • Press Tab to move to Cancel if you need to back up existing data before installing Community Edition. This choice exits the installer.

      Figure: Example Installer Dialog

  6. If you selected Proceed, Community Edition prompts you for the network information you gathered for the Network Information Checklist in Preparing to Install Community Edition
  7. Type the IP address information and use the Tab or arrow keys to go to the next field.
  8. If you are creating a single-node cluster, press the spacebar to select Create single-node cluster?.
    Note: A single-node cluster is created with a redundancy factor of 1. You cannot extend an existing single-node cluster to a three- or four-node cluster, to automatically create a cluster with redundancy factor 2. To expand to a three- or four-node cluster when you have a single-node cluster, destroy the cluster first, then create the new cluster. See Destroying a Cluster.

    Type a DNS server IP address in the required DNS field.

  9. Read and scroll through the end-user license agreement, then go to the I accept the end user license agreement checkbox.
  10. Press the spacebar to select the checkbox, then move to Start and press Enter.The installation process displays status messages to the screen. When you see the Imaging process completed successfully message, it means that the process is complete and then the Controller VM begins starting up.
  11. Press Enter to return to the login prompt.
    Note: The login banner displays the Controller VM IP address.

What to do next

  1. Log in to the Community Edition host, then open a secure shell session to the Controller VM IP address.
  2. Configure a single-node or multi-node cluster.
  3. See Getting Started.

Creating a Cluster

Cluster Task/See This Topic
Creating a Single-Node Cluster
Creating and Configuring a Multi-Node Cluster (Web Browser Method)
Creating and Configuring a Multi-Node Cluster (Manual Method)
Destroying a Cluster

Creating a Single-Node Cluster

Before you begin

Note:

  • The login banner displays the Controller VM IP address.
  • Data resiliency is not applicable for single-node clusters; a single-node cluster does not provide resiliency or high availability features, as multi-node clusters do.
  • Do not remove the USB drive or device at any time during your use of Community Edition.
  • A single-node cluster is created with a redundancy factor of 1. You cannot extend an existing single-node cluster to a three- or four-node cluster, to automatically create a cluster with redundancy factor 2. To expand to a three- or four-node cluster when you have a single-node cluster, destroy the cluster first, then create the new cluster. See Destroying a Cluster.
Caution: If you created a single-node cluster during installation (that is, you selected the Create single-node cluster? checkbox) you do not need to perform this procedure. This topic is included for reference only.
  1. At the login prompt shown after installing Community Edition, log on to the Community Edition host. User name is root and password isnutanix/4u.
  2. Log on to the Controller VM through a secure shell session. User name is nutanix and password is nutanix/4u.For example: ssh [email protected]
  3. Create the single node cluster, where cvm_ip is the Controller VM’s IP address.
    [email protected]$ cluster -s cvm_ip -f create
    Note: As of version ce-2015.11.05-stable, you do not need to specify the -f option. The command is cluster -scvm_ipcreate.

    A series of messages displays, indicating that the cluster is being created and cluster services are starting. When the process is finished, a cluster created message is displayed and the prompt returns.

  4. Configure one or more DNS servers, then verify that the settings are in place.
    [email protected]$ ncli cluster add-to-name-servers servers="dns_server"

    Replace dns_server with the IP address of a single DNS server or with a comma-separated list of DNS server IP addresses.

    [email protected]$ ncli cluster get-name-servers

Creating and Configuring a Multi-Node Cluster (Web Browser Method)

Before you begin

  • Do not remove the USB drive or device at any time during your use of Community Edition.
  • If you are using Internet Explorer for Windows:
    Note: Internet Explorer requires protected mode to be disabled. Go to Tools > Internet Options > Security, clear the Enable Protected Mode check box, and restart the browser.
  • If IPv6 link-local is enabled on the subnet, use the web browser option. If it is not enabled, use the manual command line option as described in Creating and Configuring a Multi-Node Cluster (Manual Method)
  • A single-node cluster is created with a redundancy factor of 1. You cannot extend an existing single-node cluster to a three- or four-node cluster, to automatically create a cluster with redundancy factor 2. To expand to a three- or four-node cluster when you have a single-node cluster, destroy the cluster first, then create the new cluster. See Destroying a Cluster.
  1. Open a web browser and go to http://cvm_host_name:2100/cluster_init. to create the cluster.Replace cvm_host_name with the IPv6 service name of any Controller VM that will be added to the cluster. Following is an example URL to access the cluster creation page on a Controller VM:
    http://NTNX-12AM3K520060-A-CVM.local.:2100/cluster_init.html
  2. Complete the following fields.
    • Cluster Name. Type a meaningful value in this field. The maximum length is 75 characters. Allowed characters are uppercase and lowercase standard Latin letters (A-Z and a-z), decimal digits (0-9), dots (.), hyphens (-), and underscores (_).
    • (Optional)Cluster External IP. You can connect to the external cluster IP address with both the web console and Nutanix command line (nCLI). In the event that a Controller VM is rebooted or fails, the external cluster IP address will be relocated to another Controller VM in the cluster.
    • Cluster Max Redundancy Factor. Clear or set to 2 for three- and four-node clusters. By default, Nutanix clusters have redundancy factor 2, which means they can tolerate the failure of a single node or drive.
    • Network settings. Type any network component IP addresses that were not detected during installation.
    • NTP servers. Enter NTP servers that the Controller VMs can reach in the CVM NTP Servers field. If reachable NTP servers are not entered or if the time on the Controller VMs is ahead of the current time, cluster services may fail to start.
    • Discovered nodes. Select the check box next to each node that you want to add to the cluster. All unconfigured nodes on the current network are presented on this web page. If you will be configuring multiple clusters, be sure that you only select the nodes that should be part of the current cluster.
  3. Click Create.Wait until the Log Messages section of the page reports that the cluster has been successfully configured.Output similar to the following indicates successful cluster configuration.
    Configuring IP addresses on node 13SM71450003/A...
    Configuring IP addresses on node 13SM71450003/A...
    Configuring IP addresses on node 13SM71450003/A...
    Configuring IP addresses on node 13SM71450003/A...
    Configuring the Hypervisor DNS settings on node 13SM71450003/A...
    ....
    Initializing cluster...
    Cluster successfully initialized!
    Initializing the CVM DNS and NTP servers...
    Successfully updated the CVM NTP and DNS server list

    The cluster is started automatically after creation.

  4. You can log in to the Controller VM through an SSH session and check that the cluster started properly by issuing a cluster statuscommand. Each cluster service will show a status of UP if the cluster started successfully.

Creating and Configuring a Multi-Node Cluster (Manual Method)

Before you begin

  • Do not remove the USB drive or device at any time during your use of Community Edition.
  • If IPv6 link-local is enabled on the subnet, use the web browser option as described in Creating and Configuring a Multi-Node Cluster (Web Browser Method). If it is not enabled, use this manual command line option.
  • A single-node cluster is created with a redundancy factor of 1. You cannot extend an existing single-node cluster to a three- or four-node cluster, to automatically create a cluster with redundancy factor 2. To expand to a three- or four-node cluster when you have a single-node cluster, destroy the cluster first, then create the new cluster. See Destroying a Cluster.
Note: As described, this procedure is performed from the Community Edition hypervisor host. You can also perform it remotely by logging on to the Controller VM virtual IP address through a secure shell session. You specified this IP address as part of installation (Preparing to Install Community Edition).
  1. At the login prompt shown after installing Community Edition, log on to the Community Edition host. User name is root and password isnutanix/4u.
  2. Log on to the Controller VM through a secure shell session. User name is nutanix and password is nutanix/4u.For example: ssh [email protected]
  3. Create the cluster.
    [email protected]$ cluster -s cvm_ip_addrs create

    Replace cvm_ip_addrs with a comma-separated list of Controller VM IP addresses. Include all Controller VMs that will be part of the cluster. For example, if the new cluster should comprise four nodes, include all the IP addresses of all four Controller VMs

  4. Start the Nutanix cluster.
    [email protected]$ cluster start

    If the cluster starts properly, a series of messages is displayed for each node in the cluster, showing cluster services with a status of UP.

  5. Set cluster parameters.
    1. Define the name of the cluster.
      [email protected]$ ncli cluster edit-params new-name=cluster_name

      Replace cluster_name with a name for the cluster of your choice.

    2. Configure one or more DNS servers, then verify that the settings are in place.
      [email protected]$ ncli cluster add-to-name-servers servers="dns_server"

      Replace dns_server with the IP address of a single DNS server or with a comma-separated list of DNS server IP addresses.

      [email protected]$ ncli cluster get-name-servers
    3. Configure the NTP servers.
      [email protected]$ ncli cluster add-to-ntp-servers servers="ntp_server"

      Replace ntp_server with the IP address or host name of a single NTP server or a with a comma-separated list of NTP server IP addresses or host names.

    4. Configure an external IP address for the cluster.
      [email protected]$ ncli cluster set-external-ip-address \
       external-ip-address="cluster_ip_address"

      Replace cluster_ip_address with a virtual IP address for the cluster.

      This parameter is required for your Community Edition cluster.

Destroying a Cluster

Destroying a cluster resets all nodes in the cluster to the factory configuration. All cluster configuration and guest VM data is unrecoverable after destroying the cluster.

  1. Log into a Controller VM through SSH.
  2. Stop the cluster.
    [email protected]$ cluster stop

    Wait to proceed until output similar to the following is displayed for every Controller VM in the cluster.

    CVM: 172.16.8.191 Up, ZeusLeader
                                Zeus   UP   [3167, 3180, 3181, 3182, 3191, 3201]
                           Scavenger   UP   [3334, 3351, 3352, 3353]
                   ConnectionSplicer DOWN   []
                            Hyperint DOWN   []
                              Medusa DOWN   []
                  DynamicRingChanger DOWN   []
                              Pithos DOWN   []
                            Stargate DOWN   []
                             Cerebro DOWN   []
                             Chronos DOWN   []
                             Curator DOWN   []
                               Prism DOWN   []
                        AlertManager DOWN   []
                     StatsAggregator DOWN   []
                    SysStatCollector DOWN   []
  3. Destroy the cluster.
    Caution: Performing this operation deletes all cluster and guest VM data in the cluster.
    [email protected]$ cluster -f destroy

    You can now recreate your cluster.

Getting Started

Note: See also the Getting Started with Community Edition video.

Now that your cluster is created, you can:

Getting Started Task Information/See This Topic
(Optional) Configure your HTTP proxy server. Configuring Proxy Server Settings Before Logging Into the Web Console
Log on to the web console and explore this management interface to your cluster and its related components.
  • Logging Into the Web Console
  • The Web Console Guide at Nutanix documentation
Ensure that your outgoing network ports 80 or 8443 are open. Pulse is enabled by default after installation. You just need these ports open as part of your Community Edition licensing requirements.
Configure your storage by creating one storage pool (consisting of all physical disks in the cluster) and one container (a datastore consisting of all available storage capacity in the pool). Creating the Datastore: Storage Pool and Container
Create and manage virtual machines. Creating a VM By Using the Web Console
Check cluster health. The web console shows a summary of information about the cluster. For health details, click Home > Health. The Web Console Guidedescribes more in the Health Monitoring topic.
Install any pending Community Edition updates. As updates are made available in future, this Getting Started guide will describe how to install them.

Configuring Proxy Server Settings Before Logging Into the Web Console

If you are deploying Community Edition behind a proxy server, you need to use the Nutanix command line interface (nCLI) to configure a proxy server. This step helps ensure that Community Edition can validate your credentials.

  1. At the login prompt shown after installing Community Edition, log on to the Community Edition host. User name is root and password isnutanix/4u.
  2. Log on to the Controller VM through a secure shell session. User name is nutanix and password is nutanix/4u.For example: ssh [email protected]
  3. Create the HTTP/HTTPS proxy.
    [email protected]$ ncli http-proxy add name=proxy_name address=ip_addr username=user
            password=password port=8080 proxyTypes=http,https
    

    The port number can be the common ports 8080 or 8443, or whichever ports are open through your proxy server. Specify the proxy address as an IP address or domain name.

  4. Ensure that proxy was added successfully by displaying the proxy settings.
    [email protected]$ ncli http-proxy ls

    To update proxy settings, use the ncli http-proxy edit command with the same options above. To delete the proxy, use the ncli http-proxy delete command with the same options above.

Logging Into the Web Console

Before you begin

Behind a proxy server? See Configuring Proxy Server Settings Before Logging Into the Web Console first.

To log into the web console, do the following:

  1. Open a web browser and navigate to http://management_ip_addr. Replace management_ip_addr with the IP address of any Nutanix Controller VM in the cluster.The browser will redirect to the encrypted port (9440) and may display an SSL certificate warning. Acknowledge the warning and proceed to the site.
  2. First time logon: Do this step if this is the first time you have logged on to your Community Edition cluster.
    1. Log on with the default admin account user name and password of admin).
    2. When prompted, change the default admin password, then log on with the admin account user name and new password.
    3. Type your Nutanix Next Community account user name and password and press Enter or click the right arrow icon.

    Click +Create Account if you have not joined the Next Community. Community Edition checks to ensure that the Community Edition role associated with your account is enabled.

  3. After logging on for the first time: Log on with the admin account user name and new password.

Creating the Datastore: Storage Pool and Container

  1. Sign in to the Nutanix web console.
  2. In the Storage dashboard, click the Storage Pool button.The Create Storage Pool dialog box appears.
  3. Enter the storage pool parameters.
    1. Name: Enter a name for the storage pool.
    2. Capacity: Check the box to use the available unallocated capacity for this storage pool.
    3. When all the field entries are correct, click the Save button.
  4. In the Storage dashboard, click the Container button.The Create Container dialog box appears.

    Figure: Create Container

  5. Create the container.Do the following in the indicated fields:
    1. Name: Type the name default for the container.

      For Community Edition clusters, if you name the container anything other than default you will need to use the –container parameter with the VM management scripts.

    2. Storage Pool: Select the storage pool you created above from the drop-down list.The following field, Max Capacity, displays the amount of free space available in the selected storage pool.
      Note: Advanced Settings include the ability to set the replication factor. For single-node clusters, you might see the alert message Replication factor of oplog on container default is set to 1. Obviously, you cannot select a replication factor of 2, and, as a result, single-node clusters do not provide resiliency or high availability features, as multi-node clusters do.
    3. When all the field entries are correct, click the Save button.

Creating a VM By Using the Web Console

You can create a new virtual machine (VM) through the web console.

To create a VM, do the following:

  1. In the VM dashboard, click the Create VM button.The Create VM dialog box appears.

    Figure: Create VM Dialog Box

  2. Do the following in the indicated fields:
    1. Name: Enter a name for the VM.
    2. Compute: Enter the number of vCPUs to allocate to this VM.
    3. Memory: Enter the amount of memory (in MiBs) to allocate to this VM.
  3. To attach a disk to the VM, click the plus symbol to the right of the Disks field.The Add Disks dialog box appears.

    Figure: Add Disks Dialog Box

    Do the following in the indicated fields:

    1. Type: Select the type of storage device, DISK or CDROM, from the pull-down list.The following fields and options vary depending on whether you choose DISK or CDROM.
    2. Operation: Specify the device contents from the pull-down list.
      • Select Clone from Image to copy an existing system image onto the device.
      • Select Empty CDROM to create a blank CDROM device. (This option appears only when CDROM is selected in the previous field.) A CDROM device is needed when you intend to provide a system image from CDROM.
      • Select Allocate on Container to allocate space without specifying an image. (This option appears only when DISK is selected in the previous field.) Selecting this option means you are allocating space only. You will need to provide a system image later from a CDROM or other source.
    3. Bus Type: Select the bus type from the pull-down list. The choices are IDESCSI, or SATA.
    4. Path: Enter the path to the desired system image.This field appears only when Clone from Image is selected. It specifies the image to copy. Enter the path name as/container_name/iso_name.iso. For example to clone an image frommyos.iso in a container named crt1, enter/crt1/myos.iso. When a user types the container name (/container_name/), a list appears of the ISO files in that container (assuming one or more ISO files had previously been copied to that container).
    5. Container: Select the storage container to use from the pull-down list.This field appears only when Allocate on Container is selected. The list includes all containers created for this cluster.
    6. Size: Enter the disk size in GiBs.This field appears only when Allocate on Container is selected.
    7. When all the field entries are correct, click the Add button to attach the disk to the VM and return to the Create VM dialog box.
    8. Repeat this step to attach additional devices to the VM.
  4. To create a network interface for the VM, click the plus symbol to the right of the NIC field.The Create NIC dialog box appears.

    Figure: Create NIC Dialog Box

    Do the following in the indicated fields:

    1. VLAN ID: Select the target virtual LAN from the pull-down list.The list includes all defined networks.
    2. VLAN Details: This is a read-only field that displays the VLAN UUID.
    3. Network Address/Prefix: This is a read-only field that displays the network IP address and prefix.
    4. IP Address: Enter an IP address for the VLAN.This field appears only if the NIC is placed in a managed network. Entering an IP address in this field is optional when the network configuration provides an IP pool. If the field is left blank, the NIC will be assigned an IP address from the pool.
    5. When all the field entries are correct, click the Create button to create the network interface for the VM and return to the Create VMdialog box.
    6. Repeat this step to create additional network interfaces for the VM.
  5. When all the field entries are correct, click the Save button to create the VM and close the Create VM dialog box.The new VM appears in the VM table view

Running Community Edition On Demand

This topic describes how to use Nutanix Community Edition On-Demand with Ravello Systems, a cloud service provider.

What Is CE On Demand?

Nutanix is providing a VM template (known as a blueprint) that you can copy and run in your Ravello CSP account. The template is a single-node cluster with:

  • One Controller VM
  • Acropolis hypervisor (AHV)
  • Four (4) CPUs
  • 16 GB RAM
  • 1 TB disk storage (300 GB SSD/600 GB HDD/8 GB boot drive)

After you publish the application (as described here), you can log in to the Prism web console and get started.

What You’ll Need

To successfully use Community Edition, you will need:

  • Nutanix Next credentials (after initial login to the Prism web console as described here, you can create a Nutanix Next account)
  • Laptop or desktop with broadband or better Internet access.

    The user experience will depend on the quality of your connection.

  • Upgraded/paid cloud service provider account with Ravello Systems (where Nutanix is hosting the Community Edition VM). Ravello enables you to run CE on Web Services or Google Cloud – typical rates are about $1 USD per hour. Ravello accepts most major credit cards.

Browse to https://www.ravellosystems.com/ for more information about registering and creating a paid account.

Get a Copy of Community Edition

Video:This video describes how to get a copy of Community Edition.
  1. Do one of the following at https://www.ravellosystems.com/repo/blueprints/65209959.
    • Create an account with Ravello Systems, if you haven’t already.
    • Log in to your account at Ravello Systems
  2. Click Add to Library, then type a name for the CE copy. Nutanix recommends you keep the default file name Copy of filename.
  3. Agree to the terms of service and click Add.
    Note: You might have to log out, then log back in to perform the next step.
  4. Your login takes you to the Canvas tab. Select the copy, then click Copy to My Blueprints.
  5. Name the Blueprint copy and click Copy.Your copy is now located in your Library Blueprints.

Starting Community Edition On Demand

In this step, you’ll create an application from the copied template, then publish it to start it.

  1. Click Library Blueprints, then select your copy of Community Edition. Ravello places your copy on the Canvas.
  2. Click Create Application. You can keep the default name, add a description, then click Create.
  3. Click the Settings tab.
  4. Click Optimize for Performance to view pricing details.
  5. Click Publish to open the Publish Application dialog:
    1. Select Optimize for Performance. Nutanix recommends selecting this option.
    2. Select a time to automatically stop the application (if desired).
    3. Select Advanced Start All VMs Automatically to start the cluster.
    4. Click Publish.

  6. Click the Canvas tab.

Results

You should see an hourglass while the application is being published. It takes about 10 to 15 minutes to start. The hourglass then becomes a Play button to indicate CE has started. Click the Nutanix CE application icon and the status in the lower right displays VM is Started. You should be able to log in to the Prism web console in another 5 or so minutes.

Next Steps – Logging into the Prism Web Console

Click the Canvas tab and click the Nutanix CE application icon. On the right side of the canvas is information about the Nutanix CE application. Note: this picture has been altered to show all the information.

Important: After your VM has started, wait 5 minutes or so and do the following. Note that you can also stop or restart the Nutanix CE VM from the controls at the bottom
  1. Click the Canvas tab and click the Nutanix CE application icon.
  2. Under the VM is Started message in the lower right Summary, select NIC 1/1 from the External Access list. This NIC’s IP address shown in the IP field will become the managment IP address for the Prism web console as follows: https://IP_address:9440/
  3. Open a browser and browse to the Prism web console URL with your specific IP address: https://IP_address:9440/ [The “Oops – server error” message means the cluster has not started yet. Wait a few minutes more and refresh the browser page.]
  4. When the Nutanix CE cluster has started, the Prism web console is displayed and prompts for new admin user password. Create one, then you can log in as the user admin with your new password.
  5. After logging in, you are prompted for your Nutanix Next Community credentials. You can create an account from a link on this page if you haven’t already.
  6. After completing logon and validation, the Prism web console Home dashboard is displayed.

What to do next

More Resources: Nutanix_Community_Edition_Getting_Started

Print Friendly, PDF & Email

Comments

comments

Bài viết liên quan