Getting Started with

Community Edition
Community Edition CE 2.0
February 16, 2024
Contents

Welcome to Nutanix Community Edition................................................. 3

Support for and Learning More About Community Edition and

Acropolis (AOS)...................................................................................4

Recommended Community Edition Hardware......................................... 5

Community Edition Licensing Requirements...............................................................................7

Release Notes........................................................................................ 8

Preparing to Install Community Edition...................................................9

Installing Community Edition................................................................ 11

Creating a Cluster................................................................................ 13
Manually Creating a Single-Node Cluster................................................................................. 13
Creating and Configuring a Multi-Node Cluster Manually..........................................................14

Destroying a Cluster............................................................................. 16

Getting Started..................................................................................... 17
Configuring Proxy Server Settings Before Logging into the Web Console................................. 17
Logging into the Web Console..................................................................................................18
Creating the Datastore: Storage Pool and Container................................................................ 18
Creating a VM by Using the Web Console(AHV)....................................................................... 18
Deploying and using Prism Central.......................................................................................... 18

Troubleshooting.................................................................................... 19
Recovering From SSD Failure (CE)........................................................................................... 19
Recovering From CVM Error (CE)............................................................................................. 19

Copyright..............................................................................................20
WELCOME TO NUTANIX COMMUNITY
EDITION
Nutanix Community Edition is a free version of Nutanix AOS, which powers the Nutanix Enterprise Cloud
Platform. The Community Edition of AOS is designed for people interested in test driving AOS main
features on their own test hardware and infrastructure. As stated in the 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 is sufficient for a few VMs per node, given enough memory,
CPU, and network resources.

Table 1: What is in Community Edition

Hypervisor AHV with virtualization management.

Single pane of glass control Prism web console to manage the cluster.

Command-line management Nutanix command line (nCLI).Acropolis command

line (aCLI) for AHV.

Ability to add nodes to the cluster One, three, or four nodes can comprise a cluster.

Ease of installation and use Install AOS and AHV from the USB flash drive and
bootup from the local drive.

Community Edition | Welcome to Nutanix Community Edition | 3

SUPPORT FOR AND LEARNING MORE
ABOUT COMMUNITY EDITION AND
ACROPOLIS (AOS)
Most of the 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.

• Connect with other Community Edition users and download the Community Edition software at Nutanix
Next Community Edition Forum.
• Access Nutanix Hybrid Cloud Fundamentals course for NCA (Nutanix Certified Associate) certification.
• View videos about Community Edition at Nutanix nu.school YouTube channel - Getting Started with
Community Edition.
• Get more details about AOS, AHV, and other Nutanix features in the Nutanix documentation.
• Try Nutanix solutions within minutes, with no hardware, no setup, and no cost for 4 hours at Test Drive.

Community Edition | Support for and Learning More About Community Edition and Acropolis (AOS) | 4
RECOMMENDED COMMUNITY EDITION
HARDWARE
The following table shows our hardware recommendations to use with Community Edition. However, like
other Community Edition users, other hardware works as well as the recommended types.

Table 2: System Configuration

Component Recommendation Notes

CPUs Intel CPUs with Sandy Bridge 4 core minimum; 2 cores

micro architecture or later dedicated to the Controller VM.
generations (VT-x and AVX are
supported) and AMD CPUs with
Zen micro architecture or later
generations.

System memory 20 GB minimum 32 GB or greater is recommended

for AOS features such as
One Controller VM per node
deduplication, compression, or
with optional deduplication/
more user VMs.
compression features and more
memory for one or more user
VMs.

Network interface card (NIC) Intel: 1GbE(e1000e), 2.5GbE(igc) Other NICs compatible with the
commercial version of AHV are
Realtek: 1GbE and 2.5GbE potentially available.
(r8169)

Host bus adapter (HBA) Community Edition supports Some Community Edition users
the Advanced Host Controller have reported success using
Interface (AHCI) SATA, or LSI NVMe drives.
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 A maximum number of SSD/HDD Some Community Edition users
drives per node is 4. have reported success using
more than 4 drives.

Storage devices, Cold Tier 500 GB or greater available Hard disk drive (HDD) or solid-
state drive (SSD) for cold-tier
Maximum 18 TB (3 x 6 TB HDDs)
storage

Storage devices, Hot Tier Flash Single 200 GB SSD or greater

Community Edition | Recommended Community Edition Hardware | 5

Component Recommendation Notes

Hypervisor Boot Device
One 32 GB capacity device per
node. It can be an external (such
as USB flash drive) or internal
device (such as SATA DOM, M.2
SSD or SATA SSD/HDD).
Nutanix has successfully tested
and used external USB drives
and internal devices such as a
SATA DOM with AHV. Drives with
high I/O speed and reliability are
recommended.

Note: Nutanix
recommends to use USB
3.0 drives or higher to avoid
hypervisor imaging timed
out issues.

Firmware Before installing Community

Edition on that device, consider
updating the firmware for any
devices or hardware that you plan
to use with the Community Edition
to the latest edition or edition
recommended by the hardware
vendor.

Table 3: Other Recommendations and Requirements

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 effectively.

Note: If a cluster is configured as a single-

node cluster, it cannot be expanded. To expand
to a three- or four-node cluster, destroy the
single-node cluster first, then create a new
cluster.

Imaging software If you load the Community Edition installer ISO

directly with the Virtual Drive feature of IPMI on your
host instead of a USB drive, imaging software is not
needed.

• Linux: use the included dd utility

• Mac OS X: use the included dd utility
• Windows: use Rufus, an open-source USB drive
imaging software.

Community Edition | Recommended Community Edition Hardware | 6

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 sign in to it. Otherwise, there are no licensing file requirements as with the commercially available
Nutanix products.

Table 4: Licensing Requirements

Requirement Enforcement

Admin account password change from default
Login with a Nutanix NEXT account with valid
Community Edition privileges (a.k.a. Community
Edition role).
When you first sign in to the Prism web console
with the admin account credentials, you must
immediately change the default admin user
password.
After changing the admin account credentials, you
will be prompted to provide the NEXT credentials
for the first login to the Prism web console. Your
NEXT credentials are the same as your My Nutanix
account.
To get the Community Edition role for your
NEXT credential, refer to the Community Edition
registration page.

Outgoing TCP ports 80 or 8443 opened through An automated feedback mechanism named Pulse
your firewall that sends cluster alerts and usage statistics to
Nutanix requires Internet connectivity and port
access.

Community Edition | Recommended Community Edition Hardware | 7

RELEASE NOTES
This Community Edition release notes list the known issues in CE2.0 release:

Known Issues in CE version 2.0

• Language setting or region change fails with an error -"Saving user language preference failed".
Workaround:

• Sign in to Prism Element

• Go to admin (on the top-right corner), select Update Profile
• Fill the First Name, Last Name and Email address.
• Change the language, and click Save.
• Sign out from Prism Element, and re-login.
• Missing DNS and NTP settings for an automatic cluster creation on a low performing host. This may
cause authentication failure for first-time login to the Nutanix Next Community.
Workaround:

• Add the NTP and name server details manually with nCLI.
For more information, see Command reference documentation.

Community Edition | Release Notes | 8

PREPARING TO INSTALL COMMUNITY
EDITION
Before you begin
Ensure that you have a valid account and sign in credentials for the Next Community Edition forum, and
that the account has the Community Edition role associated with it.

Procedure

1. Select the Download Community Edition widget at Nutanix Next Community Edition Discussion Forum.
The latest release is usually in the most recent topic in the thread.

2. Download the ISO from the Installer ISO URL provided.

Ensure that you copy the Md5 code provided for the ISO file.

3. Prepare the USB drive with the imaging software.

Note: This step is not needed if you load the Community Edition installer ISO directly with the Virtual
Drive feature of IPMI on your host instead of a USB flash drive.

Tip: The capacity of the USB flash drive must be greater than the size of the Installer ISO file.
phoenix-ce2.0-XXX-x86_64.iso (with XXX as the auto generated AOS release) is about 5.5 GB, so we
recommend using the USB flash drive with 8GB or greater capacity.

Note: [Windows only] Download Rufus executable, and image your USB drive.
Tip: In the UI of Rufus, you can choose the partition scheme and Target system as Partition
scheme: MBR, Target system: BIOS or UEFI or Partition scheme: GPT, Target system:
UEFI (non CSM). Set it to match the BIOS/UEFI of the host on which you will install
Community Edition.

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

Community Edition | Preparing to Install Community Edition | 9

What to do next
Have the following networking information ready for installation.

Note: Community Edition reserves IP addresses 192.168.5.0 through 192.168.5.254 for internal networking.
Since the same address range cannot be used, the host (hypervisor) and the Controller VM, must be
connected to a network with a different subnet other than 192.168.5.0.

Caution: All Host and Controller VMs in the same cluster must be on the same subnet.

• Host IP address (for the Community Edition hypervisor host)

• Controller VM IP address (This value becomes the virtual IP address that enables you to log on and
manage the cluster through the Prism web console or an SSH terminal connection)
• Subnet mask
• Gateway

Community Edition | Preparing to Install Community Edition | 10

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 on page 9.

Note: You can also see the Getting Started with Community Edition video.

Procedure

1. Insert the imaged USB drive or plug-in the ISO on the virtual drive in the node.

2. Boot the node with setting the boot device to the imaged USB drive or virtual drive in the node (you
may change the boot device priority on the BIOS/UEFI configuration screen or select it on the one-
time boot device selection screen during the boot sequence).

Figure 1: Example of the Nutanix Community Edition Installer Dialog

3. Select Hypervisor to be either AHV or ESXi.

Caution: ESXi is not officially supported.

Use the Tab or arrow keys to go to the next field.

4. Select the disks to be used for hypervisor boot, CVM boot, and data. Default has been selected. Scroll
to a disk that you want to change and press ‘h’ for hypervisor boot, ‘c’ CVM boot, and ‘d’ for data.
‘I’ is selected for the Community Edition Installer USB flash drive by default and cannot be changed
(when using the Virtual Drive instead of the USB flash drive, it is not displayed).

Note: If you select a USB device for the hypervisor boot, upgrading the hypervisor using Life
Cycle Manager (LCM) is not supported and causes the hypervisor to become unavailable. Nutanix
recommends using a non-USB device for the hypervisor boot. However, hardware limitations at your
site might not permit this.

Community Edition | Installing Community Edition | 11

5. Type the host and CVM IP address information that you gathered for the Network Information
Checklist in Preparing to Install Community Edition. Use the Tab or arrow keys to go to the next field.

6. 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 redundancy factor 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 on page 16.

7. Make sure the settings that you have entered are correct, then move to Next Page and press Enter.

8. Read and scroll through the license agreement, then go to the I accept the end user license
agreement checkbox.

9. Press the spacebar to select the checkbox, then move to Start and press Enter.
The installation process displays status messages on the screen.

10. Once imaging is complete, you will be prompted to plug out the Community Edition Installer media.
After plugging out the Community Edition Installer media, then type 'Y' and press Enter.
The host will restart now and complete the installation process.

11. After the host restarts, the initial configuration of CVM is automatically performed. The initialization
process takes about 10 minutes (depending on host performance) to complete after host startup.

Note: [Realtek NICs Only]: The kernel module "realtek" on which the Realtek r8169 driver depends
on, is not included in initramfs by default. So AHV cannot recognize the Realtek NICs and the firstboot
process of AHV fails. You need to add the "realtek" module to initramfs manually, and retry the firstboot
process with the following procedure.

• Login to the console of host with root user.

• Rebuild the initramfs adding the "realtek" module. dracut -f --add-drivers
realtek /boot/initramfs-$(uname -r).img

• Remove the flag of firstboot_fail. rm /root/.firstboot_fail

• Add the flag of firstboot. touch /root/.firstboot
• Reboot the node. reboot

What to do next

Note: If a single-node cluster creation is selected in step 7, then the cluster creation will start automatically
after the restart. Wait for about 15 minutes (depending on the host performance), to access the Prism web
console.

1. Log on 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 on page 17.

Community Edition | Installing Community Edition | 12

CREATING A CLUSTER
Cluster Task/See this Topic

Manually Creating a Single-Node Cluster on page 13

Creating and Configuring a Multi-Node Cluster Manually on page 14

Destroying a Cluster on page 16

Manually Creating a Single-Node Cluster

Before you begin

Note:

• Data resiliency is not applicable for single-node clusters; a Community Edition single-node
cluster does not provide resiliency or High Availability features, as multi-node clusters do.
• A Community Edition single-node cluster is created with redundancy factor 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 on page 16.

Caution: If you created a single-node cluster during installation (that is, when you selected the Create
single-node cluster? checkbox for AHV) you do not need to perform this procedure. This topic is included
for reference only.

Procedure

1. At the sign-in prompt shown after completion of the Community Edition installation, you can sign in to
the AHV through the local console and a secure shell session. The user name is root and the password
is nutanix/4u.

2. In a secure shell session, sign in to the Controller VM with the IP address specified during installation.
The username is nutanix and the password is nutanix/4u.
You can also access CVM from the hypervisor shell through the host internal network using the CVM
internal IP (192.168.5.2).

3. Create the single node cluster, where cvm_ip is the Controller VM IP address.
nutanix@cvm$ cluster -s cvm_ip --redundancy_factor=1 create
A series of messages displays, indicating that the cluster is being created and cluster services are
starting. When the process is finished, a message for the cluster creation is displayed and the prompt
returns.

4. Start the Nutanix cluster.

nutanix@cvm$ cluster start
If the cluster starts properly, a series of messages are displayed for each node in the cluster, showing
cluster services with a status of UP.

Community Edition | Creating a Cluster | 13

 5. Set cluster parameters.

a. Define the name of the cluster.

nutanix@cvm$ ncli cluster edit-params new-name=cluster_name
Replace cluster_name with a name for the cluster of your choice.
b. Configure an external IP address for the cluster.
nutanix@cvm$ 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.

Creating and Configuring a Multi-Node Cluster Manually

Before you begin

• A single-node cluster is created with redundancy factor 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-node or four-node cluster when you have a single-node cluster, destroy the cluster
first, then create a new cluster. See Destroying a Cluster on page 16.

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. This
CVM virtual IP is the IP address we specified as part of the Community Edition installation (Preparing to
Install Community Edition on page 9).

Procedure

1. The sign-in prompt is shown after installation is completed, you can sign in to the AHV through the local
console and a secure shell session. The user name is root and the password is nutanix/4u.

2. In a secure shell session, sign in to the Controller VM with the IP address specified during installation.
User name is nutanix and password is nutanix/4u.
You can also access CVM from the hypervisor shell through the host internal network using the CVM
internal IP (192.168.5.2).

3. Create the cluster.

nutanix@cvm$ cluster -s cvm_ip_addrs create
Replace cvm_ip_addrs with a comma-separated list of Controller VM IP addresses. Include all the
Controller VMs that will be part of the cluster. For example, if the new cluster comprises four nodes,
include all the IP addresses of all four Controller VMs.

4. Start the Nutanix cluster.

nutanix@cvm$ cluster start
If the cluster starts properly, a series of messages are displayed for each node in the cluster, showing
cluster services with a status of UP.

Community Edition | Creating a Cluster | 14

5. Set cluster parameters.

a. Define the name of the cluster.

nutanix@cvm$ ncli cluster edit-params new-name=cluster_name
Replace cluster_name with a name for the cluster of your choice.
b. Configure a virtual IP address for the cluster.
nutanix@cvm$ 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 is a required parameter
for your Community Edition cluster.
c. Add address to the list of name servers.
nutanix@cvm$ ncli cluster add-to-name-servers servers=DNS_server_ip_address
Replace DNS_server_ip_address with a DNS server IP address that is reachable from the CVM.
d. Add address to the list of NTP servers.
nutanix@cvm$ ncli cluster add-to-ntp-servers servers=NTP_server_ip_address
Replace NTP_server_ip_address with an NTP server IP address that is reachable from the CVM.

Community Edition | Creating a Cluster | 15

DESTROYING A CLUSTER
About this task
Destroying a cluster resets all nodes in the cluster to the factory configuration. All cluster configuration and
guest VM data are unrecoverable after destroying the cluster.

Procedure

1. Shut down all the guest VMs.

2. Sign in to the Controller VM through SSH.

3. Stop the cluster.

nutanix@cvm$ cluster stop

4. Enter "I agree" for the prompt to proceed.

Wait to proceed until output similar to the following screen 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 []

5. Destroy the cluster.

Caution: Performing this operation deletes all cluster and guest VM data in the cluster.

nutanix@cvm$ cluster destroy

Note: If cluster services are not DOWN, you cannot destroy the cluster. Other cluster issues also prevent
destroying a cluster. Connect with other Community Edition users at Nutanix Next Community Edition
Forum if you encounter issues while destroying a cluster.

6. Enter "Y" for the prompt to confirm destroying the cluster.

You can now recreate your cluster.

Community Edition | Destroying a Cluster | 16

GETTING STARTED
Now, that your cluster is created, you can:

Getting Started Task Information/See this Topic

Configure your HTTP proxy server (optional) . Configuring Proxy Server Settings Before Logging
into the Web Console on page 17

Log on to the web console and explore this

management interface to your cluster and its related • Logging into the Web Console on page 18
components. • The Web Console Guide at Nutanix
documentation

Ensure that your outgoing network ports 80 or 8443 Pulse is enabled by default after installation. You
are open. need these ports open as part of your Community
Edition licensing requirements.

Configure your storage by creating one storage pool Creating the Datastore: Storage Pool and Container
(consisting of all physical disks in the cluster) and on page 18
one container (a datastore consisting of all available
storage capacity in the pool).

Create and manage virtual machines. Creating a VM by Using the Web Console(AHV) on
page 18

Check cluster health. The web console shows a summary of information

about the cluster. For health details, click Home >
Health. The Web Console Guide describes 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
About this task
If you are deploying Community Edition behind a proxy server, you must use the Nutanix command-line
interface (nCLI) to configure a proxy server. This step helps ensure that Community Edition can validate
your credentials.

Procedure

1. In a secure shell session, sign in to the Controller VM with the IP address specified during installation.
The username is nutanix and the password is nutanix/4u.
You can also access CVM from the hypervisor shell through the host internal network using the CVM
internal IP (192.168.5.2).

2. Create the HTTP/HTTPS proxy.

nutanix@cvm$ ncli http-proxy add name=proxy_name address=ip_addr username=user
password=password port=8080 proxy-types=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.

Community Edition | Getting Started | 17

 3. Ensure that the proxy is added successfully by displaying the proxy settings.
nutanix@cvm$ ncli http-proxy ls
To update proxy settings, use the ncli http-proxy edit command with the same options as above. To
delete the proxy, use the ncli http-proxy remove command with the same options as above.

Logging into the Web Console

Before you begin
Behind a proxy server? See Configuring Proxy Server Settings Before Logging into the Web Console on
page 17 first.

About this task

To sign in to the web console, do the following:

Procedure

1. Open a web browser and browse to http://management_ip_addr. Replace management_ip_addr with

the IP address of any Nutanix Controller VM in the cluster.
The browser is redirected to the encrypted port (9440) and displays an SSL certificate warning.
Acknowledge the warning and proceed to the site.

2. First-time sign in: Do this step if you have logged on to your Community Edition cluster for the first time.

a. Sign in with the default admin account with user name as admin and password as Nutanix/4u.
b. When prompted, change the default admin password, then sign in 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. To enable the
Community Edition role, register at Nutanix Website.

Creating the Datastore: Storage Pool and Container

For detailed information on Storage pool and containers, visit Storage Management page.

Creating a VM by Using the Web Console(AHV)

For detailed information on VM creation using web console, visit Virtual Machine Management page.

Deploying and using Prism Central

Nutanix CE 2.0 is compatible with the commercial version of Prism Central. Starter Tier features of the
Prism Central are available for free, and advanced features are available on a trial basis. For more
information about Prism Central, visit Prism Central Guide.

Community Edition | Getting Started | 18

TROUBLESHOOTING
Recovering From SSD Failure (CE)
For more details on recovery from the SSD failure, visit Single SSD repair script KB article.

Recovering From CVM Error (CE)

For more details on recovery from the CVM error, visit Troubleshooting CVM Down KB article.

Community Edition | Troubleshooting | 19

COPYRIGHT
Copyright 2024 Nutanix, Inc.
Nutanix, Inc.
1740 Technology Drive, Suite 150
San Jose, CA 95110
All rights reserved. This product is protected by U.S. and international copyright and intellectual property
laws. Nutanix and the Nutanix logo are registered trademarks of Nutanix, Inc. in the United States and/or
other jurisdictions. All other brand and product names mentioned herein are for identification purposes only
and may be trademarks of their respective holders.

Community Edition | Copyright | 20