https://wiki.amahi.org/api.php?action=feedcontributions&feedformat=atom&user=Bigfoot65Amahi Wiki - User contributions [en]2026-04-19T10:17:03ZUser contributionsMediaWiki 1.34.2https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117826Infrastructure Virtualization Project2022-05-26T02:23:41Z<p>Bigfoot65: /* Configuration */</p>
<hr />
<div>{{WorkInProgress}}<br />
'''Last Update:''' May 22, 2022<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial (use LVM, but remove ''/home'' partition and redistribute space to ''/''). </li><br />
<li> [https://linuxconfig.org/rhel-8-configure-static-ip-address Set Static IP Address] and [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ configure Fully Qualified Domain Name], then reboot</li><br />
<li> Follow step 0 - 3 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 4, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace {set password} and ''eth0'' with appropriate values)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been developed to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117821Infrastructure Virtualization Project2022-05-23T01:54:32Z<p>Bigfoot65: /* Objective */</p>
<hr />
<div>{{WorkInProgress}}<br />
'''Last Update:''' May 22, 2022<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial (use LVM, but remove ''/home'' partition and redistribute space to ''/''). </li><br />
<li> [https://linuxconfig.org/rhel-8-configure-static-ip-address Set Static IP Address] and [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ configure Fully Qualified Domain Name], then reboot</li><br />
<li> Follow step 0 - 3 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 4, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace {set password} and ''eth0'' with appropriate values)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been developed to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117816Infrastructure Virtualization Project2022-05-23T01:53:01Z<p>Bigfoot65: /* Setup */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial (use LVM, but remove ''/home'' partition and redistribute space to ''/''). </li><br />
<li> [https://linuxconfig.org/rhel-8-configure-static-ip-address Set Static IP Address] and [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ configure Fully Qualified Domain Name], then reboot</li><br />
<li> Follow step 0 - 3 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 4, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace {set password} and ''eth0'' with appropriate values)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been developed to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117811Infrastructure Virtualization Project2022-05-23T01:49:46Z<p>Bigfoot65: /* Setup */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial (use LVM, but remove ''/home'' partition and redistribute space to ''/''). </li><br />
<li> [https://linuxconfig.org/rhel-8-configure-static-ip-address Set Static IP Address] and [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ configure Fully Qualified Domain Name], then reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace {set password} and ''eth0'' with appropriate values)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been developed to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117806Infrastructure Virtualization Project2022-05-23T01:49:19Z<p>Bigfoot65: /* Setup */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial (use LVM, but remove ''/home'' partition). </li><br />
<li> [https://linuxconfig.org/rhel-8-configure-static-ip-address Set Static IP Address] and [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ configure Fully Qualified Domain Name], then reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace {set password} and ''eth0'' with appropriate values)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been developed to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117801Infrastructure Virtualization Project2022-05-23T01:48:57Z<p>Bigfoot65: /* Setup */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial (use LVM, but remove /home partition). </li><br />
<li> [https://linuxconfig.org/rhel-8-configure-static-ip-address Set Static IP Address] and [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ configure Fully Qualified Domain Name], then reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace {set password} and ''eth0'' with appropriate values)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been developed to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117796Infrastructure Virtualization Project2022-05-23T01:48:36Z<p>Bigfoot65: /* Setup */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial (use LVM, but remove /home partition). </li><br />
<li> [https://linuxconfig.org/rhel-8-configure-static-ip-address Set Static IP Address] and [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ Configure Fully Qualified Domain Name], then reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace {set password} and ''eth0'' with appropriate values)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been developed to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117791Infrastructure Virtualization Project2022-05-23T01:46:39Z<p>Bigfoot65: /* Setup */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial (use LVM, but remove /home partition). </li><br />
<li> [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ Configure Fully Qualified Domain Name] and reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace {set password} and ''eth0'' with appropriate values)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been developed to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117786Infrastructure Virtualization Project2022-05-23T01:45:44Z<p>Bigfoot65: /* Configuration */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial. </li><br />
<li> [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ Configure Fully Qualified Domain Name] and reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace {set password} and ''eth0'' with appropriate values)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been developed to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117781Infrastructure Virtualization Project2022-05-22T14:47:04Z<p>Bigfoot65: /* Setup */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream (LVM Partitioning)<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream (Standard Partitioning)<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial. </li><br />
<li> [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ Configure Fully Qualified Domain Name] and reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace {set password} and ''eth0'' with appropriate values)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been developed to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117776Infrastructure Virtualization Project2022-05-22T14:45:48Z<p>Bigfoot65: /* Setup */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream (LVM Partitioning)<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream (Standard Partitioning)<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial. </li><br />
<li> [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ Configure Fully Qualified Domain Name] and reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace {set password} and ''eth0'' with appropriate values)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script automates the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117771Infrastructure Virtualization Project2022-05-22T14:44:34Z<p>Bigfoot65: /* Configuration */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream (LVM Partitioning)<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream (Standard Partitioning)<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial. </li><br />
<li> [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ Configure Fully Qualified Domain Name] and reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace ''eth0'' with appropriate interface)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script automates the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117766Infrastructure Virtualization Project2022-05-22T14:43:05Z<p>Bigfoot65: /* Setup */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial. </li><br />
<li> [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ Configure Fully Qualified Domain Name] and reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command: <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace ''eth0'' with appropriate interface)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script automates the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117761Infrastructure Virtualization Project2022-05-22T14:39:23Z<p>Bigfoot65: /* Setup */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Yoga):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS 8 Stream] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial. </li><br />
<li> [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ Configure Fully Qualified Domain Name] and reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command <code>packstack --allinone --provision-demo=n --cinder-volumes-size=100G --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-mappings=extnet:br-ex --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace ''eth0'' with appropriate interface)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Set Cinder Volumes to 100GB</li><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been created to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117756Infrastructure Virtualization Project2022-05-22T00:30:04Z<p>Bigfoot65: /* Configuration */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - EMPTY<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Ussuri):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial. </li><br />
<li> [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ Configure Fully Qualified Domain Name] and reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command <code>packstack --cinder-volumes-create=y --cinder-volumes-size=100G --provision-demo=n --os-heat-install=y --os-ceilometer-install=y --os-horizon-ssl=n --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace ''eth0'' with appropriate interface)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Set Cinder Volumes to 100GB</li><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been created to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117751Infrastructure Virtualization Project2022-05-21T23:05:03Z<p>Bigfoot65: /* Configuration */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 120GB SSD<br />
** 3 - 750GB (Backup)<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Ussuri):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial. </li><br />
<li> [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ Configure Fully Qualified Domain Name] and reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command <code>packstack --cinder-volumes-create=y --cinder-volumes-size=100G --provision-demo=n --os-heat-install=y --os-ceilometer-install=y --os-horizon-ssl=n --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace ''eth0'' with appropriate interface)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Set Cinder Volumes to 100GB</li><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been created to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117746Infrastructure Virtualization Project2022-05-21T23:04:34Z<p>Bigfoot65: /* Configuration */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB<br />
** 2 - 750GB (Backup)<br />
** 3 - 120GB SSD<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Ussuri):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial. </li><br />
<li> [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ Configure Fully Qualified Domain Name] and reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command <code>packstack --cinder-volumes-create=y --cinder-volumes-size=100G --provision-demo=n --os-heat-install=y --os-ceilometer-install=y --os-horizon-ssl=n --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace ''eth0'' with appropriate interface)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Set Cinder Volumes to 100GB</li><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been created to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Infrastructure_Virtualization_Project&diff=117741Infrastructure Virtualization Project2022-05-21T23:04:14Z<p>Bigfoot65: /* Configuration */</p>
<hr />
<div>{{WorkInProgress}}<br />
=Objective=<br />
This is a project to update and modernize the infrastructure that keeps the Amahi web sites and services running.<br />
<br />
The idea is to provide easier and more sustainable management of the infrastructure to leave more time for the team to devote to moving the project forward.<br />
<br />
'''NOTE:''' this project is not about running Amahi platform software on virtual servers, etc. For that there is a separate page on [[Virtualization]].<br />
<br />
=Goals=<br />
We have multiple goals:<br />
* Operate internal build machines in a reliable, efficient way, so that we have consistent and updated builds/releases<br />
* Consistent and recent backups making things recoverable<br />
* Execute some testing of Amahi apps more easily and efficiently<br />
* Test new features in an isolated manner<br />
<br />
=Configuration=<br />
'''Dell Server (F1DH):''' <br />
* Dual Xeon E5450 3.0 GHz Processors<br />
* Gigabit Network Interface<br />
* KVM Network Interface<br />
* RAID Controller<br />
<br><br />
'''Server #1 (CURRENT):'''<br />
* OpenStack release Wallaby<br />
* Operating System: CentOS 8 Stream<br />
* 24GB PC2-5300 RAM (4x2/8x2)<br />
* Quick Swap Drive Bays<br />
** 1 - 850GB (LVM)<br />
** 2 - EMPTY<br />
** 3 - 120GB SSD (Backup)<br />
** 4 - EMPTY<br />
<br><br />
'''Server #2 (BACKUP):'''<br />
* OpenStack release Yoga<br />
* Operating System: CentOS 8 Stream<br />
* 32GB PC2-5300 RAM (8x4)<br />
* Quick Swap Drive Bays<br />
** 1 - 1TB (LVM)<br />
** 2 - 750GB (Backup)<br />
** 3 - 120GB SSD<br />
** 4 - EMPTY<br />
<br />
=Setup=<br />
The following guidance is based on the latest release of OpenStack (Ussuri):<br />
<ul><br />
<li> Download [https://www.centos.org/download/ CentOS] minmal image and install following [https://linuxhint.com/install_centos8_netboot_iso/ Installing CentOS 8 using NetBoot ISO Image] tutorial. </li><br />
<li> [https://techjourney.net/how-to-set-change-hostname-fqdn-fully-qualified-domain-name-in-rhel-centos-7/ Configure Fully Qualified Domain Name] and reboot</li><br />
<li> Follow step 0 - 2 of the [https://www.rdoproject.org/install/packstack/ RDO Packstack Quickstart] for the OpenStack installation (ensure step 0 prerequisites are completed first).</li><br />
<li> At step 3, follow the [https://www.rdoproject.org/networking/neutron-with-existing-external-network/ Neutron with existing network guidance]:</li><br />
<ul><br />
<li> Use command <code>packstack --cinder-volumes-create=y --cinder-volumes-size=100G --provision-demo=n --os-heat-install=y --os-ceilometer-install=y --os-horizon-ssl=n --keystone-admin-passwd={set password} --os-neutron-ml2-mechanism-drivers=openvswitch --os-neutron-ml2-tenant-network-types=vxlan --os-neutron-ml2-type-drivers=vxlan,flat,vlan --os-neutron-l2-agent=openvswitch --os-neutron-ovs-bridge-interfaces=br-ex:eth0 --nova-libvirt-virt-type=kvm</code> (replace ''eth0'' with appropriate interface)</li><br />
<li> Skip down to ''Now, create the external network with Neutron.'' and follow guidance.</li><br />
<li> Next move to ''Then create a router and set its gateway using the external network...'' and follow remaining guidance.</li><br />
</ul><br />
<li> Set up the floating IP addresses to the external network.</li><br />
<li> Create flavors named ''amahi.small'' of 10GB and ''amahi.medium'' of 15GB.<br />
<li> Add the following rules to ''default'' Security Group (Ingress, IPv4, Remote IP 0.0.0.0):<br />
<ul><br />
<li> ICMP / Any</li><br />
<li> TCP / 22</li><br />
<li> TCP / 80</li><br />
<li> TCP / 3000</li><br />
<li> TCP / 443 (<i>Optional</i>)</li><br />
</ul><br />
<li> Set Cinder Volumes to 100GB</li><br />
<li> Add users and private keys for SSH login</li><br />
<li> Disable SSH password and root login</li><br />
<li> Add users to web UI access</li><br />
<li> Ensure OS updates applied and reboot</li><br />
<li> Create a single instance with floating IP</li><br />
<li> Verify all is working as expected.</li><br />
</ul><br />
<br />
<br />
<b>NOTE:</b> A terminal script has been created to automate the installation steps above for OpenStack after CentOS is installed.<br />
<br />
=Naming Convention=<br />
The following is recommended for standardization:<br />
* Instances: '''os-function''' (i.e. ''f24-bot'', ''f24-repo'', ''f24-dev'', etc)<br />
* Images: '''os-type''' (i.e. ''f24-cd'', ''f24-dvd'', etc)<br />
* Snapshot: '''os-function-ss#''' (i.e. ''f24-repo-ss1'', ''f24-bot-ss2'', etc)<br />
* Volumes: '''instance-vol''' (i.e. ''f24-repo-vol'', ''mirrormgr-vol'', ''dlmaster-vol'', etc)<br />
<br />
=Build Images=<br />
This will outline how to build OpenStack images using [https://www.proxmox.com/en/ Proxmox VE] (alternate method in development).<br />
* Log into Proxmox VE web UI<br />
* Create a VM or clone an existing one (<code><i>type</i>=qemu64</code>)<br />
** If creating a VM, install the OS<br />
** If using a clone, start the VM<br />
* Open a console window for the VM<br />
** Log in and as <code>root</code> do the following<br />
*** <code>dd if=/dev/zero of=/mytempfile bs=1M</code> (zero out any unused space)<br />
*** <code>rm -f /mytempfile</code><br />
** Shutdown VM<br />
** Log into Proxmox VE via SSH and execute the following from command line<br />
*** Navigate to <code>/dev/pve</code><br />
*** <code>qemu-img convert -O qcow2 original_image new_image.qcow2</code><br />
*** Copy <code>new_image.qcow2</code> to a safe location for uploading into OpenStack<br />
*** Delete the VM from Proxmox VE web UI<br />
* Use WinSCP or similar program to copy the <code>new_image.qcow2</code> to client machine<br />
* Upload into OpenStack via the web UI<br />
<br />
<br />
'''Reference:''' [https://gazelle.ihe.net/book/export/html/917 Transfer Proxmox VM]<br />
<br />
=Create Instance=<br />
This is a nice straightforward tutorial on [https://www.tecmint.com/create-deploy-and-launch-virtual-machines-in-openstack/ how to deploy and launch an instance (VM)].<br />
<br />
Also refer to [https://docs.openstack.org/mitaka/user-guide/cli_nova_launch_instance_using_ISO_image.html launch instance from ISO] for an alternate method.<br />
<br />
=Backup=<br />
'''Last Backup completed:'''<br />
* Instances - ''04 Jul 2021''<br />
* Volumes - ''04 Jul 2021''<br />
<br />
<br />
'''NOTES:'''<br />
* Back up scripts have been created to synchronize instances, volumes, and snapshots to a secondary drive on demand.<br />
* Minimal of monthly back ups be done in case of catastrophic failure.<br />
* See [https://github.com/Nexenture/openstack-instances-backups OpenStack Instance Backups] to automate via terminal script (some modification is needed).<br />
<br />
=Tips=<br />
==Command Line==<br />
[https://docs.openstack.org/python-openstackclient/ussuri/ OpenStack Command Line Guide]<br />
==Network Issues==<br />
If the DNS server is changed or networking appears inoperable, check the following to ensure the DNS is correct:<br />
* ''/etc/sysconfig/network-scripts/ifcfg-br-ex''<br />
* ''/etc/resolve.conf''<br />
<br />
<br />
Next restart neutron network services:<br />
<code><br />
:service neutron-server restart<br /><br />
:service neutron-dhcp-agent restart<br /><br />
:service neutron-l3-agent restart<br /><br />
:service neutron-metadata-agent restart<br /><br />
:service neutron-openvswitch-agent restart<br />
</code><br />
<br />
==Volume Issues==<br />
When a volume becomes detached and/or shows in error, the state can be reset:<br />
<code><br />
:source keystonerc_admin<br />
:cinder reset-state ''volume_id''<br />
</code><br />
or use web UI.<br />
<br />
Also refer to [https://bugs.amahi.org/issues/2051 Amahi Bug #2051].<br />
<br />
==Instance Issues==<br />
When an instance '''Status''' reflects an ''error'' state, reset it by:<br />
<code><br />
:source keystonerc_admin<br />
:nova reset-state --active INSTANCE_ID<br />
</code><br />
<br />
'''NOTE:''' Should the '''Power State''' reflect ''no state'' or blank, it can be corrected by doing the above step, then starting the instance.<br />
<br />
==Update/Reboot/Shutdown Process==<br />
Follow guidelines below to prevent corruption:<br />
* Shutdown/Disconnect<br />
** Stop all instances<br />
** Verify all instances stopped<br />
** Perform Update/Reboot/Shutdown<br />
<br><br />
* Once system Started/Rebooted:<br />
** Start all needed instances<br />
** Verify all instances are operational<br />
<br />
==Create Static IP for Instance==<br />
Setting a static IP for instances will ensure the internal IP address remains the same through it's life cycle. The floating IP address can be easily added afterwards.<br />
* As root user, execute <code>source keystonerc_admin</code><br />
* Use the following to reserve the IP address:<br />
<code><br />
:openstack port create --network private --fixed-ip subnet_id=private_subnet,ip_address=x.x.x.x static-ip-1<br />
</code><br />
* Create the instance and boot via command-line vs the web UI:<br />
<code><br />
:openstack server create --image IMAGE_NAME --flavor amahi.small --nic port-id=NETWORK_ID_FROM_ABOVE_COMMAND INSTANCE_NAME<br />
</code><br />
<br />
:'''NOTE:''' If image name has spaces, enclose it in double quotes.<br />
Ref: [https://ask.openstack.org/en/question/30690/add-multiple-specific-ips-to-instance/ Add Multiple Specific IPs to Instance]<br />
<br />
==Change Instance Flavor==<br />
As ''root'' user:<br />
<code><br />
:source keystonerc_admin<br />
</code><br />
See [https://docs.openstack.org/newton/user-guide/cli-change-the-size-of-your-server Change the size of your server] for command line guidance.<br />
<br />
==Fedora Cloud Base Images==<br />
See [https://alt.fedoraproject.org/cloud/ Fedora Cloud Base Images] for guidance.<br />
<br />
== Migration ==<br />
=== Images ===<br />
See [https://raymii.org/s/tutorials/Openstack_Glance_Image_Download.html OpenStack Glance Image Download Tutorial] for how to transfer images from one server to another.<br />
<br />
=== Snapshots ===<br />
See [https://community.cisco.com/t5/cloud-blogs/how-to-snapshot-an-openstack-nova-instance-boot-it-download/ba-p/3661228 Snapshot an OpenStack instance, boot it, and download] for how to transfer snapshots from one instance to another.<br />
<br />
=== Volumes ===<br />
See [http://blog.oddbit.com/2015/09/29/migrating-cinder-volumes-between-openstack-environments/ Migrating cinder volumes between OpenStack environments] for how to transfer volumes from one instance to another.<br />
<br />
==Fix Broken Web UI==<br />
Add the following line to ''/etc/httpd/conf.d/15-horizon_vhost.conf'':<br />
WSGIApplicationGroup %{GLOBAL}<br />
Then restart the web server<br />
<br />
Ref: [https://ask.openstack.org/en/question/91352/openstack-mitaka-can-not-access-dashboard/ OpenStack cannot access Dashboard]<br />
<br />
=Known Issues=<br />
Cannot use multiple SSH keys via Dashboard ([https://bugs.launchpad.net/nova/+bug/1499751 OpenStack Bug #1499751])<br />
<br></div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117736Amahi 122022-05-15T15:25:22Z<p>Bigfoot65: /* Fedora 36 */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 36 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 36===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/36/Server/x86_64/iso/Fedora-Server-netinst-x86_64-36-1.5.iso Fedora-Server-netinst-x86_64-36-1.5.iso]<br />
:&nbsp;(670 MB; SHA1 5126e9d4ed3fe043d914de69463dcdd93da16e5c)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/36/Server/x86_64/iso/Fedora-Server-dvd-x86_64-36-1.5.iso Fedora-Server-dvd-x86_64-36-1.5.iso]<br />
:&nbsp;(2.19 GB; SHA1 725e1d56d8bcb935f0398dfd430996bea528f46a)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f36.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2465 Amahi Bug # 2465]<br />
<br />
=To Do=<br />
* Create Amahi repo<br />
* Create apps (rename F35 to F36)<br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* Add to Amahi repo:<br />
** ''netatalk (native to Fedora 36)''<br />
** 'RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''><br />
** ''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''<br />
** ''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]<br />
* Test Minimal CD (Netinstall) method<br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* Create OpenStack instances:<br />
** Amahi Repo<br />
** Amahi Test<br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 35 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117731Amahi 122022-05-15T15:16:03Z<p>Bigfoot65: /* To Do */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 36 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 36===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/36/Server/x86_64/iso/Fedora-Server-netinst-x86_64-36-1.5.iso Fedora-Server-netinst-x86_64-36-1.5.iso]<br />
:&nbsp;(670 MB; SHA1 5126e9d4ed3fe043d914de69463dcdd93da16e5c)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/36/Server/x86_64/iso/Fedora-Server-dvd-x86_64-36-1.5.iso Fedora-Server-dvd-x86_64-36-1.5.iso]<br />
:&nbsp;(2.20 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f36.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2465 Amahi Bug # 2465]<br />
<br />
=To Do=<br />
* Create Amahi repo<br />
* Create apps (rename F35 to F36)<br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* Add to Amahi repo:<br />
** ''netatalk (native to Fedora 36)''<br />
** 'RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''><br />
** ''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''<br />
** ''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]<br />
* Test Minimal CD (Netinstall) method<br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* Create OpenStack instances:<br />
** Amahi Repo<br />
** Amahi Test<br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 35 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117726Amahi 122022-05-15T15:14:24Z<p>Bigfoot65: /* Amahi 12 */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 36 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 36===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/36/Server/x86_64/iso/Fedora-Server-netinst-x86_64-36-1.5.iso Fedora-Server-netinst-x86_64-36-1.5.iso]<br />
:&nbsp;(670 MB; SHA1 5126e9d4ed3fe043d914de69463dcdd93da16e5c)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/36/Server/x86_64/iso/Fedora-Server-dvd-x86_64-36-1.5.iso Fedora-Server-dvd-x86_64-36-1.5.iso]<br />
:&nbsp;(2.20 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f36.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2465 Amahi Bug # 2465]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* <s>Add to Amahi repo:</s><br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** <s>''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]</s><br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* <s>Create OpenStack instances:</s><br />
** <s>Amahi Repo</s><br />
** <s>Amahi Test</s><br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 35 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117721Amahi 122022-05-15T15:14:09Z<p>Bigfoot65: /* Fedora 35 */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 36 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 36===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/36/Server/x86_64/iso/Fedora-Server-netinst-x86_64-36-1.5.iso Fedora-Server-netinst-x86_64-36-1.5.iso]<br />
:&nbsp;(670 MB; SHA1 5126e9d4ed3fe043d914de69463dcdd93da16e5c)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/36/Server/x86_64/iso/Fedora-Server-dvd-x86_64-36-1.5.iso Fedora-Server-dvd-x86_64-36-1.5.iso]<br />
:&nbsp;(2.20 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2465 Amahi Bug # 2465]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* <s>Add to Amahi repo:</s><br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** <s>''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]</s><br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* <s>Create OpenStack instances:</s><br />
** <s>Amahi Repo</s><br />
** <s>Amahi Test</s><br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 35 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117716Amahi 122022-05-15T15:12:46Z<p>Bigfoot65: /* Objective */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 36 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 35===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-netinst-x86_64-35-1.2.iso Fedora-Server-netinst-x86_64-35-1.2.iso]<br />
:&nbsp;(646 MB; SHA1 71a67fd53ba8bb25318b14bffbf170654129ccee)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-dvd-x86_64-35-1.2.iso Fedora-Server-dvd-x86_64-35-1.2.iso]<br />
:&nbsp;(2.07 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2465 Amahi Bug # 2465]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* <s>Add to Amahi repo:</s><br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** <s>''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]</s><br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* <s>Create OpenStack instances:</s><br />
** <s>Amahi Repo</s><br />
** <s>Amahi Test</s><br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 35 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Main_Page&diff=117711Main Page2022-05-15T15:12:27Z<p>Bigfoot65: /* Roadmap & Development */</p>
<hr />
<div><br /><br />
This is the knowledge base wiki for Amahi the home server. Please add or edit any information in this Wiki that you feel is lacking, missing, or needs improvement.<br />
<br />
__TOC__<br />
<br />
* [[Intro|Introduction]] to the Amahi HDA, or Home Digital Assistant, "like a PDA, but for the home"<br />
* [http://docs.amahi.org/requirements.html Minimum Hardware Requirements]<br />
* [https://www.amahi.org/faq Frequently Asked Questions (FAQ)]<br />
* [[HDA Admin How To]]<br />
* [[HDA OS Migration Guide]]<br />
* [https://www.amahi.org/videos Amahi Video Tutorials]<br />
* [[Feedback|Community Feedback]]<br />
<br />
----<br />
'''NOTES:'''<br />
# Current stable release: [http://docs.amahi.org/amahi-11.html Amahi 11], Fedora 27'''.<br />
# Amahi one-click applications are typically updated for the latest stable release '''ONLY'''.<br />
# This wiki is built to provide support for the stable release primarily.<br />
# Registration in this wiki is subject to manual approval due to spam considerations.<br />
# '''Maintenance Support ONLY''' indicates all Amahi updates (i.e. platform, applications, etc) have been halted.<br />
----<br />
<br />
== Installation ==<br />
* [http://docs.amahi.org/amahi-11.html Fedora 27 / Amahi 11] (officially supported release)<br />
* Maintenance Support '''ONLY''':<br />
** Fedora 25 ([[Amahi 10 Install|New Install]] / [[Amahi 10 Upgrade|Amahi 9 to 10 Upgrade]])<br />
** Fedora 23 ([[Amahi 9 Install|New Install]] / [[Amahi 9 Upgrade|Amahi 8 to 9 Upgrade]])<br />
** Fedora 21 ([[Amahi 8 Install|New Install]] / [[Amahi 8 Upgrade|Amahi 7 to 8 Upgrade]] / [[Amahi 8 install via unsupported methods|Unsupported Install Methods]])<br />
** Fedora 19 ([[Express Disc]] / [https://wiki.amahi.org/index.php/Amahi_7_full_DVD Full DVD] / [[Fedora_19_USB_install|USB Install]])<br />
** [http://docs.amahi.org/ubuntu-12.html Ubuntu 12.04.x LTS]<br />
** [http://docs.amahi.org/fedora-14.html Fedora 14]<br />
*[[Amahi_Virtualized|Amahi Virtualized]] ('''NOT''' fully supported)<br />
<br />
== Troubleshooting ==<br />
Refer to the [[troubleshooting]] page for assistance.<br />
<br />
== Post-Installation ==<br />
<br />
*[[TerminalScripts|Terminal Scripts]]: Useful command line scripts.<br />
* [[Linux-hda_commands|Linux/HDA Commands]]: Commonly used commands for Linux and Amahi.<br />
*[[Storage and file sharing]]: Setup & manage users and shares and access between them.<br />
*Access Shares using [[Map_Shares_in_Windows|Windows (XP/Vista/7/8)]], [[SharingToMacOSX|Mac OS X]], and [[SharingToLinux|Linux]] systems.<br />
*[[Post-Install_Hardware_Changes | Post Install Hardware Changes]]: Steps for changing hardware on your Amahi server (i.e. mother board, network card, etc).<br />
* Adding additional hard drives to your HDA: Use the Amahi [https://www.amahi.org/apps/disk-wizard Disk Wizard] application for Amahi 8 or greater. The [[Adding a second hard drive to your HDA|manual guidance]] remains available for all other Amahi versions.<br />
<br />
=== Remote Access ===<br />
Accessing your HDA from anywhere on the network<br />
* [[VPN|Virtual Private Networking (VPN)]]: Access from '''outside''' your network.<br />
* [[Key-Based SSH Logins|Secure Shell (SSH)]]: Key-based access to your HDA.<br />
* [http://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing (VNC)]: Access from '''inside''' your network (e.g. if your HDA is "headless").<br />
** [[Install_VNC_server_on_Ubuntu_Server_12.04|Ubuntu]]<br />
** [[VNC|Fedora]]<br />
<br />
=== Greyhole ===<br />
Redundant Storage Pooling for your files<br />
<br />
*[[Greyhole|Greyhole]]: Overview of Greyhole.<br />
*[https://github.com/gboudreau/Greyhole/wiki Greyhole Wiki]: External Greyhole Wiki site.<br />
*[[Storage_pooling|Storage Pooling]]: Overview of what it is all about.<br />
*[https://www.amahi.org/apps/greyhole-log Greyhole Log]: Amahi application for your HDA that monitors Greyhole activity.<br />
*[[Mount_Shares_Locally|Mounting Shares Locally]]: How to mount shares locally on the HDA for managing data safely.<br />
*[[Greyhole_landing_zone|Greyhole landing zone (LZ)]]: Explained and how to work with it.<br />
*[[Greyhole_updating|Updating Greyhole]]: How to upgrade to the latest version of Greyhole.<br />
*[[Greyhole_moving_data_out_of_the_pool|Moving Data Out of Greyhole]]: Removing drives and data out of the storage pool.<br />
* [[Reconnect_existing_Greyhole_storage_pool|Reconnect Greyhole Storage Pool]]: How to add existing Greyhole data drives to a new installation.<br />
* [[Greyhole_UI_App_Transition_Guide|Greyhole UI Application Transition Guide]]: Move from manual Greyhole install to the [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application for Amahi 7 or greater.<br />
<br />
=== Networking ===<br />
Using your HDA to manage your home network<br />
* [http://en.wikipedia.org/wiki/Local_area_network Local Area Network (LAN)]: Internal networking<br />
** [[Networking - Static IPs|Set Static IP Address]]: How to assign static IPs to your network devices.<br />
** [[Turning_off_DHCP|Turning off DHCP Server]]: Shows how to turn off DHCP Server on your HDA.<br />
** [[Change IP Address|Change IP Address]]: Change IP address of your Amahi server, Network Gateway, and DHCP Server Range.<br />
** [[How to use two HDAs on the same network| Single Network Dual HDA Setup]]: Configure and use two HDAs on the same network.<br />
** [[Adding an HDA networked printer]]: Guide to set up a print server on your HDA.<br />
<br />
* [http://en.wikipedia.org/wiki/Wide_area_network Wide Area Network (WAN)]: External networking<br />
** [[Hosting a website | Hosting a web site]]: Display your own web site on the internet from your Amahi home server<br />
** [[Changing your DNS provider|Changing DNS provider]]: Change from [http://www.opendns.com/ OpenDNS] to your [http://en.wikipedia.org/wiki/Internet_service_provider Internet Service Provicer (ISP)] or other third party provider.<br />
** [[Configuring OpenDNS]]: Configure [http://www.opendns.com/ OpenDNS] to filter or block web sites.<br />
** [[Punching DNS Holes]]: How to assign IP addresses outside of your network for your home domain.<br />
<br />
== Additional Functionality == <br />
* [https://www.amahi.org/apps/ Apps Gallery]: The repo of Amahi one-click applications ('''NOTE:''' [https://www.amahi.org/faq#do-you-change-for-apps Convenience fees] may apply; log into Amahi website to purchase). <br />
* [http://www.amahi.org/plans PRO and NINJA plans]: Provided users with additional Amahi benefits for a small monthly fee.<br />
* [[Monit|Monit Web Interface]]: Amahi application to monitor and control status of your HDA services.<br />
* [[Webapps | Creating web apps]]: how to make your own web apps, with your code or other's code<br />
* [[Calendars]]: How to use the calendar server in the HDA, including Outlook and iCal sync.<br />
* [[Backups]]: How to backup/restore [[XPBackups|Windows XP]], [[VistaWindows7Backups|Windows Vista/7/8]], [[Sbackup|Ubuntu Linux]], and [[Backups#Mac_OS_X|Mac OS X]].<br />
* [[Database_Backup|Automatic Database Backup]]: Automated daily backup of HDA databases.<br />
* [http://en.wikipedia.org/wiki/RAID RAID]: Configuration guides for [[RAID 1]] and [[RAID 5]].<br />
* [[Require_Login|Password protect Applications]]: Provides password protect for your Amahi installed applications.<br />
<br />
== Community Tutorials ==<br />
Contributed by the Amahi user community<br />
<br />
* [[Ubuntu Tutorials|Ubuntu]]<br />
* [[Fedora Tutorials|Fedora]]<br />
* [http://wiki.amahi.org/index.php/Category:Apps Applications]<br />
<br />
== Roadmap & Development ==<br />
The [https://www.amahi.org/team core team] '''ONLY''' supports Ubuntu and Fedora development at this time. All others are being supported by the user community. <br /><br />
<br />
<u>'''ACTIVE:'''</u> Released or Development In Progress<br />
* [http://docs.amahi.org/amahi-11.html Fedora 27] (Current official release)<br />
* [[Amahi 12|Fedora 36]] (initial development)<br />
<br />
* Maintenance support <b>ONLY</b><br />
** [[Amahi 10|Fedora 25]]<br />
** [[Amahi 9|Fedora 23]]<br />
** [[Amahi 8|Fedora 21]]<br />
** [[Fedora_19|Fedora 19]]<br />
** [[Ubuntu|Ubuntu 12.04.x LTS]]<br />
** [[Fedora 14|Fedora 14]]<br />
<br /><br />
<u>'''INACTIVE:'''</u> Unsupported or Development Stopped<br />
* Fedora 15-18, 20, 22, 24, 26, 28-35<br />
* Ubuntu 12.10 or newer<br />
* CentOS [[CentOS|5]], [[Centos_6|6]], [[Centos_7|7]], or newer<br />
* [[Scientific_Linux|Scientific Linux 6.1]] or newer<br />
<br />
== Contribute ==<br />
How you can help<br />
<br />
* [[Translate Amahi]] to your language<br />
* [[How to Create a new Theme]]<br />
* Submit a [http://bugs.amahi.org Bug/Feature/Support] report<br />
* [[Contribute|Package]] or [[Tester program|Test apps]]<br />
* [http://www.flickr.com/photos/amahi/sets/72157606815797764/ Amahi Wallpapers]<br />
* [http://www.flickr.com/photos/amahi/sets/72157606828513620/ Amahi Banners]<br />
<br />
== Related Links ==<br />
* [[Developers]]: How to write HDA apps, questions, API suggestions, etc.<br />
* [[Credits]]: How are we doing all this? We have many OSS projects to thank!</div>Bigfoot65https://wiki.amahi.org/index.php?title=Main_Page&diff=117706Main Page2022-05-15T15:12:11Z<p>Bigfoot65: /* Roadmap & Development */</p>
<hr />
<div><br /><br />
This is the knowledge base wiki for Amahi the home server. Please add or edit any information in this Wiki that you feel is lacking, missing, or needs improvement.<br />
<br />
__TOC__<br />
<br />
* [[Intro|Introduction]] to the Amahi HDA, or Home Digital Assistant, "like a PDA, but for the home"<br />
* [http://docs.amahi.org/requirements.html Minimum Hardware Requirements]<br />
* [https://www.amahi.org/faq Frequently Asked Questions (FAQ)]<br />
* [[HDA Admin How To]]<br />
* [[HDA OS Migration Guide]]<br />
* [https://www.amahi.org/videos Amahi Video Tutorials]<br />
* [[Feedback|Community Feedback]]<br />
<br />
----<br />
'''NOTES:'''<br />
# Current stable release: [http://docs.amahi.org/amahi-11.html Amahi 11], Fedora 27'''.<br />
# Amahi one-click applications are typically updated for the latest stable release '''ONLY'''.<br />
# This wiki is built to provide support for the stable release primarily.<br />
# Registration in this wiki is subject to manual approval due to spam considerations.<br />
# '''Maintenance Support ONLY''' indicates all Amahi updates (i.e. platform, applications, etc) have been halted.<br />
----<br />
<br />
== Installation ==<br />
* [http://docs.amahi.org/amahi-11.html Fedora 27 / Amahi 11] (officially supported release)<br />
* Maintenance Support '''ONLY''':<br />
** Fedora 25 ([[Amahi 10 Install|New Install]] / [[Amahi 10 Upgrade|Amahi 9 to 10 Upgrade]])<br />
** Fedora 23 ([[Amahi 9 Install|New Install]] / [[Amahi 9 Upgrade|Amahi 8 to 9 Upgrade]])<br />
** Fedora 21 ([[Amahi 8 Install|New Install]] / [[Amahi 8 Upgrade|Amahi 7 to 8 Upgrade]] / [[Amahi 8 install via unsupported methods|Unsupported Install Methods]])<br />
** Fedora 19 ([[Express Disc]] / [https://wiki.amahi.org/index.php/Amahi_7_full_DVD Full DVD] / [[Fedora_19_USB_install|USB Install]])<br />
** [http://docs.amahi.org/ubuntu-12.html Ubuntu 12.04.x LTS]<br />
** [http://docs.amahi.org/fedora-14.html Fedora 14]<br />
*[[Amahi_Virtualized|Amahi Virtualized]] ('''NOT''' fully supported)<br />
<br />
== Troubleshooting ==<br />
Refer to the [[troubleshooting]] page for assistance.<br />
<br />
== Post-Installation ==<br />
<br />
*[[TerminalScripts|Terminal Scripts]]: Useful command line scripts.<br />
* [[Linux-hda_commands|Linux/HDA Commands]]: Commonly used commands for Linux and Amahi.<br />
*[[Storage and file sharing]]: Setup & manage users and shares and access between them.<br />
*Access Shares using [[Map_Shares_in_Windows|Windows (XP/Vista/7/8)]], [[SharingToMacOSX|Mac OS X]], and [[SharingToLinux|Linux]] systems.<br />
*[[Post-Install_Hardware_Changes | Post Install Hardware Changes]]: Steps for changing hardware on your Amahi server (i.e. mother board, network card, etc).<br />
* Adding additional hard drives to your HDA: Use the Amahi [https://www.amahi.org/apps/disk-wizard Disk Wizard] application for Amahi 8 or greater. The [[Adding a second hard drive to your HDA|manual guidance]] remains available for all other Amahi versions.<br />
<br />
=== Remote Access ===<br />
Accessing your HDA from anywhere on the network<br />
* [[VPN|Virtual Private Networking (VPN)]]: Access from '''outside''' your network.<br />
* [[Key-Based SSH Logins|Secure Shell (SSH)]]: Key-based access to your HDA.<br />
* [http://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing (VNC)]: Access from '''inside''' your network (e.g. if your HDA is "headless").<br />
** [[Install_VNC_server_on_Ubuntu_Server_12.04|Ubuntu]]<br />
** [[VNC|Fedora]]<br />
<br />
=== Greyhole ===<br />
Redundant Storage Pooling for your files<br />
<br />
*[[Greyhole|Greyhole]]: Overview of Greyhole.<br />
*[https://github.com/gboudreau/Greyhole/wiki Greyhole Wiki]: External Greyhole Wiki site.<br />
*[[Storage_pooling|Storage Pooling]]: Overview of what it is all about.<br />
*[https://www.amahi.org/apps/greyhole-log Greyhole Log]: Amahi application for your HDA that monitors Greyhole activity.<br />
*[[Mount_Shares_Locally|Mounting Shares Locally]]: How to mount shares locally on the HDA for managing data safely.<br />
*[[Greyhole_landing_zone|Greyhole landing zone (LZ)]]: Explained and how to work with it.<br />
*[[Greyhole_updating|Updating Greyhole]]: How to upgrade to the latest version of Greyhole.<br />
*[[Greyhole_moving_data_out_of_the_pool|Moving Data Out of Greyhole]]: Removing drives and data out of the storage pool.<br />
* [[Reconnect_existing_Greyhole_storage_pool|Reconnect Greyhole Storage Pool]]: How to add existing Greyhole data drives to a new installation.<br />
* [[Greyhole_UI_App_Transition_Guide|Greyhole UI Application Transition Guide]]: Move from manual Greyhole install to the [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application for Amahi 7 or greater.<br />
<br />
=== Networking ===<br />
Using your HDA to manage your home network<br />
* [http://en.wikipedia.org/wiki/Local_area_network Local Area Network (LAN)]: Internal networking<br />
** [[Networking - Static IPs|Set Static IP Address]]: How to assign static IPs to your network devices.<br />
** [[Turning_off_DHCP|Turning off DHCP Server]]: Shows how to turn off DHCP Server on your HDA.<br />
** [[Change IP Address|Change IP Address]]: Change IP address of your Amahi server, Network Gateway, and DHCP Server Range.<br />
** [[How to use two HDAs on the same network| Single Network Dual HDA Setup]]: Configure and use two HDAs on the same network.<br />
** [[Adding an HDA networked printer]]: Guide to set up a print server on your HDA.<br />
<br />
* [http://en.wikipedia.org/wiki/Wide_area_network Wide Area Network (WAN)]: External networking<br />
** [[Hosting a website | Hosting a web site]]: Display your own web site on the internet from your Amahi home server<br />
** [[Changing your DNS provider|Changing DNS provider]]: Change from [http://www.opendns.com/ OpenDNS] to your [http://en.wikipedia.org/wiki/Internet_service_provider Internet Service Provicer (ISP)] or other third party provider.<br />
** [[Configuring OpenDNS]]: Configure [http://www.opendns.com/ OpenDNS] to filter or block web sites.<br />
** [[Punching DNS Holes]]: How to assign IP addresses outside of your network for your home domain.<br />
<br />
== Additional Functionality == <br />
* [https://www.amahi.org/apps/ Apps Gallery]: The repo of Amahi one-click applications ('''NOTE:''' [https://www.amahi.org/faq#do-you-change-for-apps Convenience fees] may apply; log into Amahi website to purchase). <br />
* [http://www.amahi.org/plans PRO and NINJA plans]: Provided users with additional Amahi benefits for a small monthly fee.<br />
* [[Monit|Monit Web Interface]]: Amahi application to monitor and control status of your HDA services.<br />
* [[Webapps | Creating web apps]]: how to make your own web apps, with your code or other's code<br />
* [[Calendars]]: How to use the calendar server in the HDA, including Outlook and iCal sync.<br />
* [[Backups]]: How to backup/restore [[XPBackups|Windows XP]], [[VistaWindows7Backups|Windows Vista/7/8]], [[Sbackup|Ubuntu Linux]], and [[Backups#Mac_OS_X|Mac OS X]].<br />
* [[Database_Backup|Automatic Database Backup]]: Automated daily backup of HDA databases.<br />
* [http://en.wikipedia.org/wiki/RAID RAID]: Configuration guides for [[RAID 1]] and [[RAID 5]].<br />
* [[Require_Login|Password protect Applications]]: Provides password protect for your Amahi installed applications.<br />
<br />
== Community Tutorials ==<br />
Contributed by the Amahi user community<br />
<br />
* [[Ubuntu Tutorials|Ubuntu]]<br />
* [[Fedora Tutorials|Fedora]]<br />
* [http://wiki.amahi.org/index.php/Category:Apps Applications]<br />
<br />
== Roadmap & Development ==<br />
The [https://www.amahi.org/team core team] '''ONLY''' supports Ubuntu and Fedora development at this time. All others are being supported by the user community. <br /><br />
<br />
<u>'''ACTIVE:'''</u> Released or Development In Progress<br />
* [http://docs.amahi.org/amahi-11.html Fedora 27] (Current official release)<br />
* [[Amahi 12|Fedora 36]] (development)<br />
<br />
* Maintenance support <b>ONLY</b><br />
** [[Amahi 10|Fedora 25]]<br />
** [[Amahi 9|Fedora 23]]<br />
** [[Amahi 8|Fedora 21]]<br />
** [[Fedora_19|Fedora 19]]<br />
** [[Ubuntu|Ubuntu 12.04.x LTS]]<br />
** [[Fedora 14|Fedora 14]]<br />
<br /><br />
<u>'''INACTIVE:'''</u> Unsupported or Development Stopped<br />
* Fedora 15-18, 20, 22, 24, 26, 28-35<br />
* Ubuntu 12.10 or newer<br />
* CentOS [[CentOS|5]], [[Centos_6|6]], [[Centos_7|7]], or newer<br />
* [[Scientific_Linux|Scientific Linux 6.1]] or newer<br />
<br />
== Contribute ==<br />
How you can help<br />
<br />
* [[Translate Amahi]] to your language<br />
* [[How to Create a new Theme]]<br />
* Submit a [http://bugs.amahi.org Bug/Feature/Support] report<br />
* [[Contribute|Package]] or [[Tester program|Test apps]]<br />
* [http://www.flickr.com/photos/amahi/sets/72157606815797764/ Amahi Wallpapers]<br />
* [http://www.flickr.com/photos/amahi/sets/72157606828513620/ Amahi Banners]<br />
<br />
== Related Links ==<br />
* [[Developers]]: How to write HDA apps, questions, API suggestions, etc.<br />
* [[Credits]]: How are we doing all this? We have many OSS projects to thank!</div>Bigfoot65https://wiki.amahi.org/index.php?title=File:Cronkeep-ss.png&diff=117701File:Cronkeep-ss.png2022-05-07T18:44:36Z<p>Bigfoot65: </p>
<hr />
<div></div>Bigfoot65https://wiki.amahi.org/index.php?title=File:Cronkeep-logo.png&diff=117696File:Cronkeep-logo.png2022-05-07T18:36:51Z<p>Bigfoot65: </p>
<hr />
<div></div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117692Amahi 122022-04-24T16:44:02Z<p>Bigfoot65: /* Upgrade */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 35 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 35===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-netinst-x86_64-35-1.2.iso Fedora-Server-netinst-x86_64-35-1.2.iso]<br />
:&nbsp;(646 MB; SHA1 71a67fd53ba8bb25318b14bffbf170654129ccee)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-dvd-x86_64-35-1.2.iso Fedora-Server-dvd-x86_64-35-1.2.iso]<br />
:&nbsp;(2.07 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2465 Amahi Bug # 2465]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* <s>Add to Amahi repo:</s><br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** <s>''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]</s><br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* <s>Create OpenStack instances:</s><br />
** <s>Amahi Repo</s><br />
** <s>Amahi Test</s><br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 35 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=File:Statping-ng-ss.png&diff=117686File:Statping-ng-ss.png2021-12-18T18:53:40Z<p>Bigfoot65: </p>
<hr />
<div></div>Bigfoot65https://wiki.amahi.org/index.php?title=File:Statping-ng-logo.png&diff=117681File:Statping-ng-logo.png2021-12-18T18:53:08Z<p>Bigfoot65: </p>
<hr />
<div></div>Bigfoot65https://wiki.amahi.org/index.php?title=App_Ports&diff=117676App Ports2021-12-18T18:52:25Z<p>Bigfoot65: /* Web */</p>
<hr />
<div>Various services and applications utilize ports to communicate. The purpose of this page is to list those.<br />
<br />
'''Last Update:''' 10 Oct 2021<br />
<br />
== Web ==<br />
Most Amahi web applications operate on port 80. Below is a list of those that use a different port:<br />
<br />
{| class="wikitable"<br />
! Application<br />
! Port<br />
|-<br />
| [https://www.amahi.org/apps/cockpit Cockpit]<br />
| 9090<br />
|-<br />
| [https://www.amahi.org/apps/couchpotato CouchPotato]<br />
| 5050<br />
|-<br />
| [https://www.amahi.org/apps/deluge Deluge]<br />
| 8112<br />
|-<br />
| [https://www.amahi.org/apps/dlna DLNA]<br />
| 8200<br />
|-<br />
| [https://www.amahi.org/apps/emby Emby]<br />
| 8096<br />
|-<br />
| [https://www.amahi.org/apps/ghost Ghost]<br />
| 2368<br />
|-<br />
| [https://www.amahi.org/apps/glances-web Glances (Web)]<br />
| 61208<br />
|-<br />
| [https://www.amahi.org/apps/headphones Headphones]<br />
| 8181<br />
|-<br />
| [https://www.amahi.org/apps/home-assistant Home Assistant]<br />
| 8123<br />
|-<br />
| [https://www.amahi.org/apps/home-assistant-core Home Assistant Core]<br />
| 8123<br />
|-<br />
| [https://www.amahi.org/apps/htpc-manager HTPC Manager]<br />
| 8086<br />
|-<br />
| [https://www.amahi.org/apps/jenkins Jenkins]<br />
| 8080<br />
|-<br />
| [https://www.amahi.org/apps/lazy-librarian Lazy Librarian]<br />
| 5229<br />
|-<br />
| [https://www.amahi.org/apps/logitech-media-server Logitech Media Center]<br />
| 9000<br />
|-<br />
| [https://www.amahi.org/apps/maraschino Maraschino]<br />
| 8008<br />
|-<br />
| [https://www.amahi.org/apps/mediatomb MediaTomb]<br />
| 50500<br />
|-<br />
| [https://www.amahi.org/apps/minecraft-server Minecraft Server]<br />
| 62877<br />
|-<br />
| [https://www.amahi.org/apps/mldonkey MLDonkey]<br />
| 4080<br />
|-<br />
| [https://www.amahi.org/apps/monit-service-manager Monit Service Manager]<br />
| 2812<br />
|-<br />
| [https://www.amahi.org/apps/netdata Netdata]<br />
| 19999<br />
|-<br />
| [https://www.amahi.org/apps/node-red Node-RED]<br />
| 1880<br />
|-<br />
| [https://www.amahi.org/apps/nzbget NZBGet]<br />
| 6789<br />
|-<br />
| [https://www.amahi.org/apps/openremote OpenRemote]<br />
| 8080<br />
|-<br />
| [https://www.amahi.org/apps/openvpn-als OpenVPN ALS]<br />
| 4443<br />
|-<br />
| [https://www.amahi.org/apps/plex-media-server Plex Media Server]<br />
| 32400<br />
|-<br />
| [https://www.amahi.org/apps/pgadmin-4 pgAdmin 4]<br />
| 5050<br />
|-<br />
| [https://www.amahi.org/apps/pyload pyLoad]<br />
| 8000<br />
|-<br />
| [https://www.amahi.org/apps/qbittorrent Qbittorrent]<br />
| 8090<br />
|-<br />
| [https://www.amahi.org/apps/sabnzbd-plus SABnzbd Plus]<br />
| 25915<br />
|-<br />
| [https://www.amahi.org/apps/seafile Seafile]<br />
| 8088<br />
|-<br />
| [https://www.amahi.org/apps/shell-in-a-box Shell In A Box]<br />
| 4200<br />
|-<br />
| [https://www.amahi.org/apps/sick-beard Sick Beard]<br />
| 8081<br />
|-<br />
| [https://www.amahi.org/apps/sickchill SickChill]<br />
| 8081<br />
|-<br />
| [https://www.amahi.org/apps/sickgear SickGear]<br />
| 8081<br />
|-<br />
| [https://www.amahi.org/apps/sickrage SiCKRAGE]<br />
| 8082<br />
|-<br />
| [https://www.amahi.org/apps/sonarr Sonarr]<br />
| 8089<br />
|-<br />
| [https://www.amahi.org/apps/statping-ng Statping-ng]<br />
| 8182<br />
|-<br />
| [https://www.amahi.org/apps/subsonic Subsonic]<br />
| 4040<br />
|-<br />
| [https://www.amahi.org/apps/supersync SuperSync]<br />
| 5360<br />
|-<br />
| [https://www.amahi.org/apps/syncthing Syncthing]<br />
| 8384<br />
|-<br />
| [https://www.amahi.org/apps/tailon Tailon]<br />
| 5000<br />
|-<br />
| [https://www.amahi.org/apps/transmission Transmission]<br />
| 9091<br />
|-<br />
| [https://www.amahi.org/apps/urbackup-server UrBackup Server]<br />
| 55414<br />
|-<br />
| [https://www.amahi.org/apps/usermin Usermin]<br />
| 20000<br />
|-<br />
| [https://www.amahi.org/apps/watcher Watcher]<br />
| 9092<br />
|-<br />
| [https://www.amahi.org/apps/webmin Webmin]<br />
| 10000 / 10002<br />
|-<br />
| [https://www.amahi.org/apps/webshell WebShell]<br />
| 9022<br />
|-<br />
| [https://www.amahi.org/apps/xdm xdm]<br />
| 8085<br />
|-<br />
| [https://www.amahi.org/apps/znc ZNC]<br />
| 26244<br />
|}<br />
<br />
== Services ==<br />
{| class="wikitable"<br />
! Service<br />
! Port<br />
|-<br />
| [https://www.amahi.org/apps/cups CUPS]<br />
| 631<br />
|-<br />
| httpd (Apache)<br />
| 80<br />
|-<br />
| MariaDB (MySQL)<br />
| 3306<br />
|-<br />
| [https://www.amahi.org/apps/mosquitto-mqtt Mosquitto MQTT]<br />
| 1883<br />
|-<br />
| [https://www.amahi.org/apps/openvpn OpenVPN]<br />
| 1194<br />
|-<br />
| [https://www.amahi.org/apps/postgresql PostgreSQL]<br />
| 5432<br />
|-<br />
| Samba<br />
| 139/445<br />
|-<br />
| Secure Shell (SSH)<br />
| 22<br />
|-<br />
| VNC<br />
| 5904/6004<br />
|-<br />
| dnsmasq<br />
| 53<br />
|}<br />
<br />
== Docker ==<br />
Amahi Docker web applications operate on a different port other than 80 as listed below:<br />
<br />
{| class="wikitable"<br />
! Application<br />
! Port<br />
|-<br />
| [https://www.amahi.org/apps/adminer-docker Adminer (Docker)]<br />
| 8382<br />
|-<br />
| [https://www.amahi.org/apps/apache-guacamole-docker Apache Guacamole (Docker)]<br />
| 8188<br />
|-<br />
| [https://www.amahi.org/apps/drupal-docker Drupal (Docker)]<br />
| 8083<br />
|-<br />
| [https://www.amahi.org/apps/elkarbackup-docker ELKARbackup (Docker)]<br />
| 8010<br />
|-<br />
| [https://www.amahi.org/apps/emby-docker Emby (Docker)]<br />
| 8097<br />
|-<br />
| [https://www.amahi.org/apps/firefly-iii-docker Firefly III (Docker)]<br />
| 8484<br />
|-<br />
| [https://www.amahi.org/apps/freshrss-docker FreshRSS (Docker)]<br />
| 8017<br />
|-<br />
| [https://www.amahi.org/apps/ghost-docker Ghost (Docker)]<br />
| 8368<br />
|-<br />
| [https://www.amahi.org/apps/gibbon-docker Gibbon (Docker)]<br />
| 8899<br />
|-<br />
| [https://www.amahi.org/apps/gitea-docker Gitea (Docker)]<br />
| 3000<br />
|-<br />
| [https://www.amahi.org/apps/gogs-docker Gogs (Docker)]<br />
| 3100<br />
|-<br />
| [https://www.amahi.org/apps/home-assistant-docker Home Assistant (Docker)]<br />
| 8123<br />
|-<br />
| [https://www.amahi.org/apps/homebridge-docker Homebridge (Docker)]<br />
| 8581<br />
|-<br />
| [https://www.amahi.org/apps/keeweb-docker KeeWeb (Docker)]<br />
| 8432<br />
|-<br />
| [https://www.amahi.org/apps/lychee-docker Lychee (Docker)]<br />
| 8787<br />
|-<br />
| [https://www.amahi.org/apps/mediawiki-docker MediaWiki (Docker)]<br />
| 8184<br />
|-<br />
| [https://www.amahi.org/apps/netdata-docker Netdata (Docker)]<br />
| 19998<br />
|-<br />
| [https://www.amahi.org/apps/nexclipper-docker NexClipper (Docker)]<br />
| 10001<br />
|-<br />
| [https://www.amahi.org/apps/nextcloud-docker Nextcloud (Docker)]<br />
| 8181<br />
|-<br />
| [https://www.amahi.org/apps/node-red-docker Node-RED (Docker)]<br />
| 1880<br />
|-<br />
| [https://www.amahi.org/apps/nzbget-docker NZBGet (Docker)]<br />
| 6789<br />
|-<br />
| [https://www.amahi.org/apps/observium-ce-docker Observium CE (Docker)]<br />
| 8888<br />
|-<br />
| [https://www.amahi.org/apps/owncloud-docker ownCloud (Docker)]<br />
| 8282<br />
|-<br />
| [https://www.amahi.org/apps/pgadmin-4-docker pgAdmin 4 (Docker)]<br />
| 8488<br />
|-<br />
| [https://www.amahi.org/apps/phpmyadmin-docker PhpMyAdmin (Docker)]<br />
| 8383<br />
|-<br />
| [https://www.amahi.org/apps/phppgadmin-docker phpPgAdmin (Docker)]<br />
| 8284<br />
|-<br />
| [https://www.amahi.org/apps/php-server-monitor-docker PHP Server Monitor (Docker)]<br />
| 8286<br />
|-<br />
| [https://www.amahi.org/apps/plex-media-server-docker Plex Media Server (Docker)]<br />
| 32401<br />
|-<br />
| [https://www.amahi.org/apps/portainer-io-docker Portainer.io (Docker)]<br />
| 9000<br />
|-<br />
| [https://www.amahi.org/apps/qbittorrent-docker Qbittorrent (Docker)]<br />
| 8090<br />
|-<br />
| [https://www.amahi.org/apps/redmine-docker Redmine (Docker)]<br />
| 3010<br />
|-<br />
| [https://www.amahi.org/apps/sabnzbd-plus-docker SABnzbd Plus (Docker)]<br />
| 25916<br />
|-<br />
| [https://www.amahi.org/apps/seafile-docker Seafile (Docker)]<br />
| 8179<br />
|-<br />
| [https://www.amahi.org/apps/shaarli-docker Shaarli (Docker)]<br />
| 8015<br />
|-<br />
| [https://www.amahi.org/apps/shinobi-docker Shinobi (Docker)]<br />
| 8070<br />
|-<br />
| [https://www.amahi.org/apps/sickchill-docker SickChill (Docker)]<br />
| 8084<br />
|-<br />
| [https://www.amahi.org/apps/sickgear-docker SickGear (Docker)]<br />
| 8087<br />
|-<br />
| [https://www.amahi.org/apps/sonarr-docker Sonarr (Docker)]<br />
| 8988<br />
|-<br />
| [https://www.amahi.org/apps/syncthing-docker Syncthing (Docker)]<br />
| 8385<br />
|-<br />
| [https://www.amahi.org/apps/transmission-docker Transmission (Docker)]<br />
| 9091<br />
|-<br />
| [https://www.amahi.org/apps/universal-media-server-docker Universal Media Server (Docker)]<br />
| 9001<br />
|-<br />
| [https://www.amahi.org/apps/urbackup-server-docker UrBackup Server (Docker)]<br />
| 55414<br />
|-<br />
| [https://www.amahi.org/apps/wallabag-docker Wallabag (Docker)]<br />
|8289<br />
|-<br />
| [https://www.amahi.org/apps/watcher-docker Watcher (Docker)]<br />
| 9092<br />
|-<br />
| [https://www.amahi.org/apps/wordpress-docker WordPress (Docker)]<br />
| 8586<br />
|-<br />
| [https://www.amahi.org/apps/znc-docker ZNC (Docker)]<br />
| 26244<br />
|-<br />
| [https://www.amahi.org/apps/zoneminder-docker ZoneMinder (Docker)]<br />
| 8444<br />
|}<br />
<br />
{| class="wikitable"<br />
! Service<br />
! Port<br />
|-<br />
| [https://www.amahi.org/apps/mariadb-docker MariaDB (Docker)]<br />
| 6603<br />
|-<br />
| [https://www.amahi.org/apps/mosquitto-mqtt-docker Mosquito MQTT (Docker)]<br />
| 1883<br />
|-<br />
| [https://www.amahi.org/apps/postgresql-docker PostgreSQL (Docker)]<br />
| 2345<br />
|}<br />
<br />
== Snap ==<br />
Amahi Snap web applications operate on a different port other than 80 as listed below:<br />
<br />
{| class="wikitable"<br />
! Application<br />
! Port<br />
|-<br />
| [https://www.amahi.org/apps/home-assistant-snap Home Assistant (Snap)]<br />
| 8123<br />
|-<br />
| [https://www.amahi.org/apps/node-red-snap Node-RED (Snap)]<br />
| 1880<br />
|}<br />
<br />
{| class="wikitable"<br />
! Service<br />
! Port<br />
|-<br />
| [https://www.amahi.org/apps/mosquito-mqtt-snap Mosquito MQTT (Snap)]<br />
| 1883<br />
|}</div>Bigfoot65https://wiki.amahi.org/index.php?title=HDA_OS_Migration_Guide&diff=117671HDA OS Migration Guide2021-12-13T01:04:11Z<p>Bigfoot65: /* Backup Settings */</p>
<hr />
<div><p>The purpose of this tutorial is to provide a method for migrating Amahi HDA settings from one Amahi supported OS to another via a new install, such as:<br />
<br />
* [[Amahi 10|Fedora 25]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Amahi 9|Fedora 23]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Amahi 8|Fedora 21]] to [[Amahi 12|Fedora 27]]<br />
<br />
* [[Fedora 19]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Ubuntu|Ubuntu 12.04.x LTS]] to [[Amahi 11|Fedora 27]]<br />
<br /><br />
Currently there '''IS NOT''' an automated upgrade path for Ubuntu or a method for backing up current HDA settings for a reinstall. It is a manual process! However, we have provided a script to capture most of the settings you will need for a new Amahi HDA. We hope this will make it a more manageable task than it has been in the past.</p><br />
<br />
== Disclaimer ==<br />
<p>Please understand this is a guide to assist you in the migration. There is no guarantee this guidance will work for everyone. While every effort has been taken to accurately document the migration steps, use at your own risk.</p><br />
<br />
== Backup Settings ==<br />
<p>As with any other migration process, you will need to back up your HDA settings. In order to make the new system look and feel like your current one, there are certain components we need to capture.</p><br />
<br />
<p>To make this as painless as possible, a script is being provided. Once you run the script, it will record all the important information such as users, shares, apps installed, network, and Greyhole configuration (if installed), and other settings in a text file. You can then copy that file to a safe location for use once the new system is ready to be configured.</p><br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], do the following: <br />
* Navigate to the root directory:<br />
cd /root<br />
* Download script for appropriate Amahi version:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
:''u1204_hda_migration.sh'' script (sha1sum 0b65de7520a420b68f137601cdb479784538f762)<br />
wget <nowiki>"http://dl.amahi.org/u1204_hda_migration.sh.txt" -O u1204_hda_migration.sh</nowiki><br />
:<u>Fedora 19</u><br />
:''f19_hda_migration.sh'' script (sha1sum 777a27a4aa0f5192420585da0303f0b0defedd8d):<br />
wget <nowiki>"http://dl.amahi.org/f19_hda_migration.sh.txt" -O f19_hda_migration.sh</nowiki><br />
:<u>Fedora 21/23/25</u><br />
:''f21_hda_migration.sh'' script (sha1sum 5de37d8a18b9ea51a31c7964da9b7e41b74d34e7):<br />
wget <nowiki>"http://dl.amahi.org/f21_hda_migration.sh.txt" -O f21_hda_migration.sh</nowiki><br />
<br />
* Make it executable:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
chmod 755 u1204_hda_migration.sh<br />
:<u>Fedora 19</u><br />
chmod 755 f19_hda_migration.sh<br />
:<u>Fedora 21/23/25</u><br />
chmod 755 f21_hda_migration.sh<br />
<br />
* Run the script:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
./u1204_hda_migration.sh<br />
:<u>Fedora 19</u><br />
./f19_hda_migration.sh<br />
:<u>Fedora 21/23/25</u><br />
./f21_hda_migration.sh<br />
If all goes well, you will see a message similar to the one below:<br />
<pre><br />
HDA Settings Backup Complete!<br />
Filename : hda_production_migration.txt<br />
Directory: /root<br />
</pre><br />
Copy '''hda_production_migration.txt''' (hereon referred to as ''migration text'') to another machine and view the contents. Ensure all your settings were accurately captured before proceeding to the next section. <br />
<br />
You can also print the file to make it easy to follow along as you go through the migrations steps. See [[HDA_OS_Migration_Guide#Additional Tips|Additional Tips]] below for optional steps you may want to complete.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''IMPORTANT:''' You will need to document any manual configuration changes or apps installed from sources other than the [https://www.amahi.org/apps Amahi App Store].</div><br />
<br />
== Greyhole Cleanup ==<br />
If you are not currently using [https://wiki.amahi.org/index.php/Greyhole Greyhole], you can '''SKIP''' this section. <br />
<br />
Otherwise, [https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], begin with emptying the trash:<br />
greyhole -a<br />
Also recommend you run a <code>fsck</code> to ensure all files are in place:<br />
greyhole -f<br />
Monitor activity via the log file:<br />
tail -f /var/log/greyhole.log<br />
Once it's complete, you can prepare to shutdown your system<br />
<br />
== Shutdown Preparation ==<br />
Before powering '''OFF''' the HDA, you need to:<br />
# Turn '''OFF''' DHCP server on the HDA<br />
# Turn '''ON''' your [https://wiki.amahi.org/index.php/Turning_off_DHCP_in_your_router router DHCP/DNS server]<br />
# Power '''OFF''' any clients that aren't needed<br />
# [https://wiki.amahi.org/index.php/RenewIP Renew DHCP lease] for clients to remain '''ON'''<br />
# Verify all clients have connectivity via the router<br />
# Download new [http://docs.amahi.org Amahi install image]<br />
<br />
<br />
Once you have the media ready for install, it's time to power '''OFF''' your HDA.<br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], execute:<br />
:<pre>shutdown now -P</pre><br />
:or<br />
:you can select the '''Shutdown''' icon (the '''<span style="color:red">RED</span>''' one) from the HDA Dashboard ''Settings'' tab.<br />
<br />
Once the HDA is '''OFF''', disconnect all hard drives except the one for the OS. You don't need to remove them, just disconnect the power and drive cables.<br />
<br />
== New Installation ==<br />
To begin:<br />
* Power '''ON''' your HDA<br />
* Insert installation media (reboot if needed)<br />
* Follow the appropriate [http://docs.amahi.org Amahi installation instructions]<br />
* Once complete, '''DO NOT''' disable the router DHCP/DNS server yet.<br />
<br />
== Validate Success ==<br />
Once the install is complete, you need to validate the install was successful. Ensure everything is working correctly before proceeding to the next section.<br />
<br />
What you should check:<br />
* Does the HDA boot successfully and without errors<br />
* Can you connect to the Amahi Dashboard (<nowiki>http://hda</nowiki> or by IP Address)<br />
* Does the HDA have internet connectivity (try <code>yum list hda-platform</code>)<br />
<br />
<br />
If you have problems, refer to the [https://wiki.amahi.org/index.php/Network_troubleshooting Network Troubleshooting] guide in the wiki.<br />
<br />
Once everything appears to be working, you can now disable your [https://wiki.amahi.org/index.php/Turning_off_DHCP_in_your_router router DHCP/DNS server]. The Amahi HDA will become your DHCP/DNS server for the network. <br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You will need to [https://wiki.amahi.org/index.php/RenewIP renew the DHCP lease] on any client systems currently connected to the network.</div><br />
<br />
== Configure Drives ==<br />
If you do not have any additional drives to connect to your HDA, you can '''SKIP''' this section.<br />
<br />
Otherwise, you will need to:<br />
* Power '''OFF''' the HDA<br />
* Reconnect the power and drive cables<br />
* Power '''ON''' the HDA<br />
<br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], edit ''/etc/fstab'':<br />
vi /etc/fstab<br />
* Append entries the end of the file as noted in the '''fstab''' section of the ''migration text''. For example:<br />
:<pre>UUID=b7017251-cb54-438b-92a3-781537c565e6 /var/hda/files/drives/sdb ext4 defaults 1 2 noatime,data=writeback,nofail</pre><br />
* Ensure you '''DO NOT''' add any drive lines that contain ''/'', ''/boot'', or ''swap''. For example:<br />
:<pre>UUID=1ebbf241-528c-465e-889f-acc15400dd8c / ext4 defaults 1 1</pre><br />
* Create directories that correspond the the path in the drive lines. For example:<br />
:<pre>mkdir -p /var/hda/files/drives/sdb</pre><br />
:indicates a drive listed in ''/etc/fstab'' will be mounted at this location.<br />
<br />
Once you have all the drives added to ''/etc/fstab'' and the directories created, you can then mount the drives.<br />
mount -a<br />
If there are any errors, compare with the '''fstab''' section of the ''migration text''. '''DO NOT''' proceed to the next section until all drives are correctly mounted.<br />
<br />
To add additional drives to your HDA for Greyhole, please use the Amahi [https://www.amahi.org/apps/disk-wizard Disk Wizard] application which provides a Dashboard UI for this process. The [[Adding_a_second_hard_drive_to_your_HDA|adding a second hard drive]] from command-line documentation is also available.<br />
<br />
== Install Applications ==<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''WARNING:''' Some applications may not be ''LIVE'' for the new Amahi supported OS. Also the application version could be newer than you had installed on your previous HDA. As a result, the databases(s) and/or configuration files(s) may not be compatible.</div><br />
<br />
Refer to the '''INSTALLED APPS TAB''' section of the ''migration text'' to determine applications to install. Any [http://www.amahi.org/faq/if-i-pay-for-an-app-when-your-next-version-comes-out-do-i-have-to-pay-for-your-app-again previously purchased applications] from the [https://www.amahi.org/apps Amahi App Store] will be available for install.<br />
<br />
* As you proceed to install applications, compare the version you install with the version listed in the ''migration text''. That will give you an indication if a database or configuration file restore will be successful.<br />
<br />
* If you have any database(s) and configuration file(s) saved for applications, you can restore them in most cases. Database(s) can be restored via command line or using a MySQL application such as, [https://www.amahi.org/apps/adminer Adminer] or [https://www.amahi.org/apps/phpmyadmin phpMyAdmin].<br />
<br />
* Obviously you don't have to install all the applications you had on the previous system and you can choose to install new ones as well.<br />
<br />
:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You can now manually install any apps from sources other than the [https://www.amahi.org/apps Amahi App Store] if needed.</div><br />
<br />
== Migrate Settings ==<br />
We are now ready to being updating the new HDA with our previous HDA settings. Start by selecting ''Setup'' from the Amahi Dashboard main page (<nowiki>http://hda</nowiki>).<br />
<br />
<u>Users Tab</u><br />
:Create ''New users''. Refer to '''USERS TAB''' section in the ''migration text''.<br />
<br />
<u>Shares Tab</u><br />
:Choose the appropriate section and complete as noted.<br />
:*''Details'' section: Create ''Shares''. Refer to '''SHARES TAB''' section in the ''migration text''.<br />
:*''Settings'' section. Update ''Work Group Name'' if needed. Refer to '''SETTINGS''' under the '''SHARES TAB''' section in the ''migration text''.<br />
<br />
<u>Network Tab</u><br />
:Choose the appropriate section and complete as noted.<br />
:*''Fixed IPs'' section: Create ''Fixed IPs''. Refer to '''FIXED IP''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
:*''DNS Aliases'' section: Create ''DNS Aliases''. Refer to '''DNS ALIASES''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
:*''Settings'' section:<br />
::*Disable ''DHCP Server'' and/or ''DNS Server'' if needed. Refer to '''DHCP/DNS SERVER''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Lease Time'' if needed. Refer to '''DHCP Lease Time''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Change ''DNS Provider'' if needed. Refer to '''DNS PROVIDER''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Gateway'' if needed. Refer to '''GATEWAY''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Dynamic IP Range'' (Fedora 21/23<!--/25--> '''ONLY''') if needed. Refer to '''DYNAMIC IP RANGE''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
<br />
<u>Settings Tab</u><br />
:Enable ''Advanced Settings'' and/or ''Guest Dashboard''. Refer to '''SETTINGS TAB''' section in the ''migration text''.<br />
<br />
You should now have the majority of your settings restored. Double check to ensure you did not overlook anything before moving to the next section.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You can now make any manual configuration changes that are needed.</div><br />
<br />
== Setup Greyhole ==<br />
If you do not want to use [https://wiki.amahi.org/index.php/Greyhole Greyhole], you can '''SKIP''' this section. <br />
<br />
Otherwise, you have two options for installing Greyhole:<br />
<br />
<u>Manual</u><br /><br />
Follow the [[Amahi_Create_Manual_Greyhole_Setup|Manual configuration]] and [[Reconnect existing Greyhole storage pool]] guidance. Refer to '''greyhole.conf''' section in the ''migration text'' as needed.<br /><br />
<br />
or<br />
<br />
<u>Automated</u><br /><br />
Install the [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application. In the Amahi Dashboard, navigate to the '''Drive Pooling''' tab and choose:<br />
* '''Partitions''' section and select the appropriate ''Locations'' for the ''Pool''. Refer to '''greyhole.conf''' section (''storage_pool_directory'' line) in the ''migration text'' to verify the correct partitions are chosen. <br />
<br />
:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' If [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application was installed on your previous HDA, you should refer to '''DRIVE POOLING TAB''' section in the ''migration text'' rather than '''greyhole.conf''' section.</div><br />
* '''Shares''' section<br />
** Choose ''Storage Pool'' for the applicable ''Shares''. Refer to '''greyhole.conf''' (''num_copies'' line) section in the ''migration text'' to verify the correct ''Shares'' are chosen.<br />
** Select the appropriate ''Number Copies'' for ''Shares''. Refer to '''greyhole.conf''' section (''num_copies'' line) in the ''migration text'' to verify the correct ''Number Copies'' are chosen.<br />
<br />
::<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' If [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application was installed on your previous HDA, you should refer to '''SHARES TAB''' (''Disk Pool Copies'' column) section in the ''migration text'' to determine the appropriate setting.</div><br />
<br />
<u>Additional Settings</u><br /><br />
[https://wiki.amahi.org/index.php/Greyhole#Greyhole_Advanced_Options Greyhole Advanced Options] are configured in ''greyhole.yml'' file (''/var/hda/platform/html/config''). Compare the contents with the '''greyhole.yml''' section in the ''migration text'' for any differences. Make changes as needed.<br />
<br />
<u>Verify Operational</u><br /><br />
Before proceeding to the next section, verify Greyhole is working properly. This can be done by monitoring the log:<br />
tail -f /var/log/grehole.log<br />
If there is a problem, refer to [https://wiki.amahi.org/index.php/Greyhole_troubleshooting Greyhole Troubleshooting]. Don't forget to install [https://wiki.amahi.org/index.php/Mount_Shares_Locally Mount Shares Locally] service if needed.<br />
<br />
== Final Verification ==<br />
All the settings and configuration changes from your previous HDA should now be complete. Recommend you verify that everything is working as desired. Its best to check things over thoroughly now to prevent an unexpected surprise later.<br />
<br />
If something is not working as expected, double check ''migration text'' to ensure you didn't make any errors. Depending on the issue, you may need to refer to the [https://wiki.amahi.org/index.php/Troubleshooting Amahi Troubleshooting] guidance.<br />
<br />
Providing there are no problems, you should now have a fully functional up-to-date Amahi HDA.<br />
<br />
== Additional Tips ==<br />
Each HDA is unique as will be the migration to a different Amahi supported OS. There are additional steps you can accomplish to make the transition a bit smoother.<br />
<br />
Recommend backing up:<br />
* App database(s) and configuration file(s)<br />
* ''.bashrc'' and ''.vimrc'' files for each user<br />
* User added terminal scripts<br />
* Screen capture of dashboard tabs</div>Bigfoot65https://wiki.amahi.org/index.php?title=HDA_OS_Migration_Guide&diff=117666HDA OS Migration Guide2021-12-12T23:29:14Z<p>Bigfoot65: /* Backup Settings */</p>
<hr />
<div><p>The purpose of this tutorial is to provide a method for migrating Amahi HDA settings from one Amahi supported OS to another via a new install, such as:<br />
<br />
* [[Amahi 10|Fedora 25]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Amahi 9|Fedora 23]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Amahi 8|Fedora 21]] to [[Amahi 12|Fedora 27]]<br />
<br />
* [[Fedora 19]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Ubuntu|Ubuntu 12.04.x LTS]] to [[Amahi 11|Fedora 27]]<br />
<br /><br />
Currently there '''IS NOT''' an automated upgrade path for Ubuntu or a method for backing up current HDA settings for a reinstall. It is a manual process! However, we have provided a script to capture most of the settings you will need for a new Amahi HDA. We hope this will make it a more manageable task than it has been in the past.</p><br />
<br />
== Disclaimer ==<br />
<p>Please understand this is a guide to assist you in the migration. There is no guarantee this guidance will work for everyone. While every effort has been taken to accurately document the migration steps, use at your own risk.</p><br />
<br />
== Backup Settings ==<br />
<p>As with any other migration process, you will need to back up your HDA settings. In order to make the new system look and feel like your current one, there are certain components we need to capture.</p><br />
<br />
<p>To make this as painless as possible, a script is being provided. Once you run the script, it will record all the important information such as users, shares, apps installed, network, and Greyhole configuration (if installed), and other settings in a text file. You can then copy that file to a safe location for use once the new system is ready to be configured.</p><br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], do the following: <br />
* Navigate to the root directory:<br />
cd /root<br />
* Download script for appropriate Amahi version:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
:''u1204_hda_migration.sh'' script (sha1sum 0b65de7520a420b68f137601cdb479784538f762)<br />
wget <nowiki>"https://drive.google.com/uc?export=download&id=0B64TOKt5XksaeU1DNzM5TUlSbFk" -O u1204_hda_migration.sh</nowiki><br />
:<u>Fedora 19</u><br />
:''f19_hda_migration.sh'' script (sha1sum 777a27a4aa0f5192420585da0303f0b0defedd8d):<br />
wget <nowiki>"https://drive.google.com/file/d/1Ait2fBxqoQJcKfj-gzeurYT46v07jaT7" -O f19_hda_migration.sh</nowiki><br />
:<u>Fedora 21/23/25</u><br />
:''f21_hda_migration.sh'' script (sha1sum 5de37d8a18b9ea51a31c7964da9b7e41b74d34e7):<br />
wget <nowiki>"https://drive.google.com/file/d/19UgoU5wDdLO63Mh37478avV_Z98yx5rE" -O f21_hda_migration.sh</nowiki><br />
<br />
* Make it executable:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
chmod 755 u1204_hda_migration.sh<br />
:<u>Fedora 19</u><br />
chmod 755 f19_hda_migration.sh<br />
:<u>Fedora 21/23/25</u><br />
chmod 755 f21_hda_migration.sh<br />
<br />
* Run the script:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
./u1204_hda_migration.sh<br />
:<u>Fedora 19</u><br />
./f19_hda_migration.sh<br />
:<u>Fedora 21/23/25</u><br />
./f21_hda_migration.sh<br />
If all goes well, you will see a message similar to the one below:<br />
<pre><br />
HDA Settings Backup Complete!<br />
Filename : hda_production_migration.txt<br />
Directory: /root<br />
</pre><br />
Copy '''hda_production_migration.txt''' (hereon referred to as ''migration text'') to another machine and view the contents. Ensure all your settings were accurately captured before proceeding to the next section. <br />
<br />
You can also print the file to make it easy to follow along as you go through the migrations steps. See [[HDA_OS_Migration_Guide#Additional Tips|Additional Tips]] below for optional steps you may want to complete.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''IMPORTANT:''' You will need to document any manual configuration changes or apps installed from sources other than the [https://www.amahi.org/apps Amahi App Store].</div><br />
<br />
== Greyhole Cleanup ==<br />
If you are not currently using [https://wiki.amahi.org/index.php/Greyhole Greyhole], you can '''SKIP''' this section. <br />
<br />
Otherwise, [https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], begin with emptying the trash:<br />
greyhole -a<br />
Also recommend you run a <code>fsck</code> to ensure all files are in place:<br />
greyhole -f<br />
Monitor activity via the log file:<br />
tail -f /var/log/greyhole.log<br />
Once it's complete, you can prepare to shutdown your system<br />
<br />
== Shutdown Preparation ==<br />
Before powering '''OFF''' the HDA, you need to:<br />
# Turn '''OFF''' DHCP server on the HDA<br />
# Turn '''ON''' your [https://wiki.amahi.org/index.php/Turning_off_DHCP_in_your_router router DHCP/DNS server]<br />
# Power '''OFF''' any clients that aren't needed<br />
# [https://wiki.amahi.org/index.php/RenewIP Renew DHCP lease] for clients to remain '''ON'''<br />
# Verify all clients have connectivity via the router<br />
# Download new [http://docs.amahi.org Amahi install image]<br />
<br />
<br />
Once you have the media ready for install, it's time to power '''OFF''' your HDA.<br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], execute:<br />
:<pre>shutdown now -P</pre><br />
:or<br />
:you can select the '''Shutdown''' icon (the '''<span style="color:red">RED</span>''' one) from the HDA Dashboard ''Settings'' tab.<br />
<br />
Once the HDA is '''OFF''', disconnect all hard drives except the one for the OS. You don't need to remove them, just disconnect the power and drive cables.<br />
<br />
== New Installation ==<br />
To begin:<br />
* Power '''ON''' your HDA<br />
* Insert installation media (reboot if needed)<br />
* Follow the appropriate [http://docs.amahi.org Amahi installation instructions]<br />
* Once complete, '''DO NOT''' disable the router DHCP/DNS server yet.<br />
<br />
== Validate Success ==<br />
Once the install is complete, you need to validate the install was successful. Ensure everything is working correctly before proceeding to the next section.<br />
<br />
What you should check:<br />
* Does the HDA boot successfully and without errors<br />
* Can you connect to the Amahi Dashboard (<nowiki>http://hda</nowiki> or by IP Address)<br />
* Does the HDA have internet connectivity (try <code>yum list hda-platform</code>)<br />
<br />
<br />
If you have problems, refer to the [https://wiki.amahi.org/index.php/Network_troubleshooting Network Troubleshooting] guide in the wiki.<br />
<br />
Once everything appears to be working, you can now disable your [https://wiki.amahi.org/index.php/Turning_off_DHCP_in_your_router router DHCP/DNS server]. The Amahi HDA will become your DHCP/DNS server for the network. <br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You will need to [https://wiki.amahi.org/index.php/RenewIP renew the DHCP lease] on any client systems currently connected to the network.</div><br />
<br />
== Configure Drives ==<br />
If you do not have any additional drives to connect to your HDA, you can '''SKIP''' this section.<br />
<br />
Otherwise, you will need to:<br />
* Power '''OFF''' the HDA<br />
* Reconnect the power and drive cables<br />
* Power '''ON''' the HDA<br />
<br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], edit ''/etc/fstab'':<br />
vi /etc/fstab<br />
* Append entries the end of the file as noted in the '''fstab''' section of the ''migration text''. For example:<br />
:<pre>UUID=b7017251-cb54-438b-92a3-781537c565e6 /var/hda/files/drives/sdb ext4 defaults 1 2 noatime,data=writeback,nofail</pre><br />
* Ensure you '''DO NOT''' add any drive lines that contain ''/'', ''/boot'', or ''swap''. For example:<br />
:<pre>UUID=1ebbf241-528c-465e-889f-acc15400dd8c / ext4 defaults 1 1</pre><br />
* Create directories that correspond the the path in the drive lines. For example:<br />
:<pre>mkdir -p /var/hda/files/drives/sdb</pre><br />
:indicates a drive listed in ''/etc/fstab'' will be mounted at this location.<br />
<br />
Once you have all the drives added to ''/etc/fstab'' and the directories created, you can then mount the drives.<br />
mount -a<br />
If there are any errors, compare with the '''fstab''' section of the ''migration text''. '''DO NOT''' proceed to the next section until all drives are correctly mounted.<br />
<br />
To add additional drives to your HDA for Greyhole, please use the Amahi [https://www.amahi.org/apps/disk-wizard Disk Wizard] application which provides a Dashboard UI for this process. The [[Adding_a_second_hard_drive_to_your_HDA|adding a second hard drive]] from command-line documentation is also available.<br />
<br />
== Install Applications ==<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''WARNING:''' Some applications may not be ''LIVE'' for the new Amahi supported OS. Also the application version could be newer than you had installed on your previous HDA. As a result, the databases(s) and/or configuration files(s) may not be compatible.</div><br />
<br />
Refer to the '''INSTALLED APPS TAB''' section of the ''migration text'' to determine applications to install. Any [http://www.amahi.org/faq/if-i-pay-for-an-app-when-your-next-version-comes-out-do-i-have-to-pay-for-your-app-again previously purchased applications] from the [https://www.amahi.org/apps Amahi App Store] will be available for install.<br />
<br />
* As you proceed to install applications, compare the version you install with the version listed in the ''migration text''. That will give you an indication if a database or configuration file restore will be successful.<br />
<br />
* If you have any database(s) and configuration file(s) saved for applications, you can restore them in most cases. Database(s) can be restored via command line or using a MySQL application such as, [https://www.amahi.org/apps/adminer Adminer] or [https://www.amahi.org/apps/phpmyadmin phpMyAdmin].<br />
<br />
* Obviously you don't have to install all the applications you had on the previous system and you can choose to install new ones as well.<br />
<br />
:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You can now manually install any apps from sources other than the [https://www.amahi.org/apps Amahi App Store] if needed.</div><br />
<br />
== Migrate Settings ==<br />
We are now ready to being updating the new HDA with our previous HDA settings. Start by selecting ''Setup'' from the Amahi Dashboard main page (<nowiki>http://hda</nowiki>).<br />
<br />
<u>Users Tab</u><br />
:Create ''New users''. Refer to '''USERS TAB''' section in the ''migration text''.<br />
<br />
<u>Shares Tab</u><br />
:Choose the appropriate section and complete as noted.<br />
:*''Details'' section: Create ''Shares''. Refer to '''SHARES TAB''' section in the ''migration text''.<br />
:*''Settings'' section. Update ''Work Group Name'' if needed. Refer to '''SETTINGS''' under the '''SHARES TAB''' section in the ''migration text''.<br />
<br />
<u>Network Tab</u><br />
:Choose the appropriate section and complete as noted.<br />
:*''Fixed IPs'' section: Create ''Fixed IPs''. Refer to '''FIXED IP''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
:*''DNS Aliases'' section: Create ''DNS Aliases''. Refer to '''DNS ALIASES''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
:*''Settings'' section:<br />
::*Disable ''DHCP Server'' and/or ''DNS Server'' if needed. Refer to '''DHCP/DNS SERVER''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Lease Time'' if needed. Refer to '''DHCP Lease Time''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Change ''DNS Provider'' if needed. Refer to '''DNS PROVIDER''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Gateway'' if needed. Refer to '''GATEWAY''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Dynamic IP Range'' (Fedora 21/23<!--/25--> '''ONLY''') if needed. Refer to '''DYNAMIC IP RANGE''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
<br />
<u>Settings Tab</u><br />
:Enable ''Advanced Settings'' and/or ''Guest Dashboard''. Refer to '''SETTINGS TAB''' section in the ''migration text''.<br />
<br />
You should now have the majority of your settings restored. Double check to ensure you did not overlook anything before moving to the next section.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You can now make any manual configuration changes that are needed.</div><br />
<br />
== Setup Greyhole ==<br />
If you do not want to use [https://wiki.amahi.org/index.php/Greyhole Greyhole], you can '''SKIP''' this section. <br />
<br />
Otherwise, you have two options for installing Greyhole:<br />
<br />
<u>Manual</u><br /><br />
Follow the [[Amahi_Create_Manual_Greyhole_Setup|Manual configuration]] and [[Reconnect existing Greyhole storage pool]] guidance. Refer to '''greyhole.conf''' section in the ''migration text'' as needed.<br /><br />
<br />
or<br />
<br />
<u>Automated</u><br /><br />
Install the [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application. In the Amahi Dashboard, navigate to the '''Drive Pooling''' tab and choose:<br />
* '''Partitions''' section and select the appropriate ''Locations'' for the ''Pool''. Refer to '''greyhole.conf''' section (''storage_pool_directory'' line) in the ''migration text'' to verify the correct partitions are chosen. <br />
<br />
:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' If [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application was installed on your previous HDA, you should refer to '''DRIVE POOLING TAB''' section in the ''migration text'' rather than '''greyhole.conf''' section.</div><br />
* '''Shares''' section<br />
** Choose ''Storage Pool'' for the applicable ''Shares''. Refer to '''greyhole.conf''' (''num_copies'' line) section in the ''migration text'' to verify the correct ''Shares'' are chosen.<br />
** Select the appropriate ''Number Copies'' for ''Shares''. Refer to '''greyhole.conf''' section (''num_copies'' line) in the ''migration text'' to verify the correct ''Number Copies'' are chosen.<br />
<br />
::<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' If [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application was installed on your previous HDA, you should refer to '''SHARES TAB''' (''Disk Pool Copies'' column) section in the ''migration text'' to determine the appropriate setting.</div><br />
<br />
<u>Additional Settings</u><br /><br />
[https://wiki.amahi.org/index.php/Greyhole#Greyhole_Advanced_Options Greyhole Advanced Options] are configured in ''greyhole.yml'' file (''/var/hda/platform/html/config''). Compare the contents with the '''greyhole.yml''' section in the ''migration text'' for any differences. Make changes as needed.<br />
<br />
<u>Verify Operational</u><br /><br />
Before proceeding to the next section, verify Greyhole is working properly. This can be done by monitoring the log:<br />
tail -f /var/log/grehole.log<br />
If there is a problem, refer to [https://wiki.amahi.org/index.php/Greyhole_troubleshooting Greyhole Troubleshooting]. Don't forget to install [https://wiki.amahi.org/index.php/Mount_Shares_Locally Mount Shares Locally] service if needed.<br />
<br />
== Final Verification ==<br />
All the settings and configuration changes from your previous HDA should now be complete. Recommend you verify that everything is working as desired. Its best to check things over thoroughly now to prevent an unexpected surprise later.<br />
<br />
If something is not working as expected, double check ''migration text'' to ensure you didn't make any errors. Depending on the issue, you may need to refer to the [https://wiki.amahi.org/index.php/Troubleshooting Amahi Troubleshooting] guidance.<br />
<br />
Providing there are no problems, you should now have a fully functional up-to-date Amahi HDA.<br />
<br />
== Additional Tips ==<br />
Each HDA is unique as will be the migration to a different Amahi supported OS. There are additional steps you can accomplish to make the transition a bit smoother.<br />
<br />
Recommend backing up:<br />
* App database(s) and configuration file(s)<br />
* ''.bashrc'' and ''.vimrc'' files for each user<br />
* User added terminal scripts<br />
* Screen capture of dashboard tabs</div>Bigfoot65https://wiki.amahi.org/index.php?title=HDA_OS_Migration_Guide&diff=117661HDA OS Migration Guide2021-12-12T23:25:11Z<p>Bigfoot65: /* Backup Settings */</p>
<hr />
<div><p>The purpose of this tutorial is to provide a method for migrating Amahi HDA settings from one Amahi supported OS to another via a new install, such as:<br />
<br />
* [[Amahi 10|Fedora 25]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Amahi 9|Fedora 23]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Amahi 8|Fedora 21]] to [[Amahi 12|Fedora 27]]<br />
<br />
* [[Fedora 19]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Ubuntu|Ubuntu 12.04.x LTS]] to [[Amahi 11|Fedora 27]]<br />
<br /><br />
Currently there '''IS NOT''' an automated upgrade path for Ubuntu or a method for backing up current HDA settings for a reinstall. It is a manual process! However, we have provided a script to capture most of the settings you will need for a new Amahi HDA. We hope this will make it a more manageable task than it has been in the past.</p><br />
<br />
== Disclaimer ==<br />
<p>Please understand this is a guide to assist you in the migration. There is no guarantee this guidance will work for everyone. While every effort has been taken to accurately document the migration steps, use at your own risk.</p><br />
<br />
== Backup Settings ==<br />
<p>As with any other migration process, you will need to back up your HDA settings. In order to make the new system look and feel like your current one, there are certain components we need to capture.</p><br />
<br />
<p>To make this as painless as possible, a script is being provided. Once you run the script, it will record all the important information such as users, shares, apps installed, network, and Greyhole configuration (if installed), and other settings in a text file. You can then copy that file to a safe location for use once the new system is ready to be configured.</p><br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], do the following: <br />
* Navigate to the root directory:<br />
cd /root<br />
* Download script for appropriate Amahi version:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
:''u1204_hda_migration.sh'' script (sha1sum 0b65de7520a420b68f137601cdb479784538f762)<br />
wget <nowiki>"https://drive.google.com/uc?export=download&id=0B64TOKt5XksaeU1DNzM5TUlSbFk" -O u1204_hda_migration.sh</nowiki><br />
:<u>Fedora 19</u><br />
:''f19_hda_migration.sh'' script (sha1sum 777a27a4aa0f5192420585da0303f0b0defedd8d):<br />
wget <nowiki>"https://drive.google.com/file/d/1Ait2fBxqoQJcKfj-gzeurYT46v07jaT7" -O f19_hda_migration.sh</nowiki><br />
:<u>Fedora 21/23</u><br />
:''f21_hda_migration.sh'' script (sha1sum 5de37d8a18b9ea51a31c7964da9b7e41b74d34e7):<br />
wget <nowiki>"https://drive.google.com/file/d/19UgoU5wDdLO63Mh37478avV_Z98yx5rE" -O f21_hda_migration.sh</nowiki><br />
:<u>Fedora 25</u><br />
:''f25_hda_migration.sh'' script (sha1sum 5de37d8a18b9ea51a31c7964da9b7e41b74d34e7):<br />
wget <nowiki>"https://drive.google.com/file/d/1Gg1CxfudvDtZgxlCLDgMLdDGdFk-Lf01" -O f25_hda_migration.sh</nowiki><br />
<br />
* Make it executable:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
chmod 755 u1204_hda_migration.sh<br />
:<u>Fedora 19</u><br />
chmod 755 f19_hda_migration.sh<br />
:<u>Fedora 21/23</u><br />
chmod 755 f21_hda_migration.sh<br />
:<u>Fedora 25</u><br />
chmod 755 f25_hda_migration.sh<br />
* Run the script:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
./u1204_hda_migration.sh<br />
:<u>Fedora 19</u><br />
./f19_hda_migration.sh<br />
:<u>Fedora 21/23</u><br />
./f21_hda_migration.sh<br />
:<u>Fedora 25</u><br />
./f25_hda_migration.sh<br />
If all goes well, you will see a message similar to the one below:<br />
<pre><br />
HDA Settings Backup Complete!<br />
Filename : hda_production_migration.txt<br />
Directory: /root<br />
</pre><br />
Copy '''hda_production_migration.txt''' (hereon referred to as ''migration text'') to another machine and view the contents. Ensure all your settings were accurately captured before proceeding to the next section. <br />
<br />
You can also print the file to make it easy to follow along as you go through the migrations steps. See [[HDA_OS_Migration_Guide#Additional Tips|Additional Tips]] below for optional steps you may want to complete.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''IMPORTANT:''' You will need to document any manual configuration changes or apps installed from sources other than the [https://www.amahi.org/apps Amahi App Store].</div><br />
<br />
== Greyhole Cleanup ==<br />
If you are not currently using [https://wiki.amahi.org/index.php/Greyhole Greyhole], you can '''SKIP''' this section. <br />
<br />
Otherwise, [https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], begin with emptying the trash:<br />
greyhole -a<br />
Also recommend you run a <code>fsck</code> to ensure all files are in place:<br />
greyhole -f<br />
Monitor activity via the log file:<br />
tail -f /var/log/greyhole.log<br />
Once it's complete, you can prepare to shutdown your system<br />
<br />
== Shutdown Preparation ==<br />
Before powering '''OFF''' the HDA, you need to:<br />
# Turn '''OFF''' DHCP server on the HDA<br />
# Turn '''ON''' your [https://wiki.amahi.org/index.php/Turning_off_DHCP_in_your_router router DHCP/DNS server]<br />
# Power '''OFF''' any clients that aren't needed<br />
# [https://wiki.amahi.org/index.php/RenewIP Renew DHCP lease] for clients to remain '''ON'''<br />
# Verify all clients have connectivity via the router<br />
# Download new [http://docs.amahi.org Amahi install image]<br />
<br />
<br />
Once you have the media ready for install, it's time to power '''OFF''' your HDA.<br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], execute:<br />
:<pre>shutdown now -P</pre><br />
:or<br />
:you can select the '''Shutdown''' icon (the '''<span style="color:red">RED</span>''' one) from the HDA Dashboard ''Settings'' tab.<br />
<br />
Once the HDA is '''OFF''', disconnect all hard drives except the one for the OS. You don't need to remove them, just disconnect the power and drive cables.<br />
<br />
== New Installation ==<br />
To begin:<br />
* Power '''ON''' your HDA<br />
* Insert installation media (reboot if needed)<br />
* Follow the appropriate [http://docs.amahi.org Amahi installation instructions]<br />
* Once complete, '''DO NOT''' disable the router DHCP/DNS server yet.<br />
<br />
== Validate Success ==<br />
Once the install is complete, you need to validate the install was successful. Ensure everything is working correctly before proceeding to the next section.<br />
<br />
What you should check:<br />
* Does the HDA boot successfully and without errors<br />
* Can you connect to the Amahi Dashboard (<nowiki>http://hda</nowiki> or by IP Address)<br />
* Does the HDA have internet connectivity (try <code>yum list hda-platform</code>)<br />
<br />
<br />
If you have problems, refer to the [https://wiki.amahi.org/index.php/Network_troubleshooting Network Troubleshooting] guide in the wiki.<br />
<br />
Once everything appears to be working, you can now disable your [https://wiki.amahi.org/index.php/Turning_off_DHCP_in_your_router router DHCP/DNS server]. The Amahi HDA will become your DHCP/DNS server for the network. <br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You will need to [https://wiki.amahi.org/index.php/RenewIP renew the DHCP lease] on any client systems currently connected to the network.</div><br />
<br />
== Configure Drives ==<br />
If you do not have any additional drives to connect to your HDA, you can '''SKIP''' this section.<br />
<br />
Otherwise, you will need to:<br />
* Power '''OFF''' the HDA<br />
* Reconnect the power and drive cables<br />
* Power '''ON''' the HDA<br />
<br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], edit ''/etc/fstab'':<br />
vi /etc/fstab<br />
* Append entries the end of the file as noted in the '''fstab''' section of the ''migration text''. For example:<br />
:<pre>UUID=b7017251-cb54-438b-92a3-781537c565e6 /var/hda/files/drives/sdb ext4 defaults 1 2 noatime,data=writeback,nofail</pre><br />
* Ensure you '''DO NOT''' add any drive lines that contain ''/'', ''/boot'', or ''swap''. For example:<br />
:<pre>UUID=1ebbf241-528c-465e-889f-acc15400dd8c / ext4 defaults 1 1</pre><br />
* Create directories that correspond the the path in the drive lines. For example:<br />
:<pre>mkdir -p /var/hda/files/drives/sdb</pre><br />
:indicates a drive listed in ''/etc/fstab'' will be mounted at this location.<br />
<br />
Once you have all the drives added to ''/etc/fstab'' and the directories created, you can then mount the drives.<br />
mount -a<br />
If there are any errors, compare with the '''fstab''' section of the ''migration text''. '''DO NOT''' proceed to the next section until all drives are correctly mounted.<br />
<br />
To add additional drives to your HDA for Greyhole, please use the Amahi [https://www.amahi.org/apps/disk-wizard Disk Wizard] application which provides a Dashboard UI for this process. The [[Adding_a_second_hard_drive_to_your_HDA|adding a second hard drive]] from command-line documentation is also available.<br />
<br />
== Install Applications ==<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''WARNING:''' Some applications may not be ''LIVE'' for the new Amahi supported OS. Also the application version could be newer than you had installed on your previous HDA. As a result, the databases(s) and/or configuration files(s) may not be compatible.</div><br />
<br />
Refer to the '''INSTALLED APPS TAB''' section of the ''migration text'' to determine applications to install. Any [http://www.amahi.org/faq/if-i-pay-for-an-app-when-your-next-version-comes-out-do-i-have-to-pay-for-your-app-again previously purchased applications] from the [https://www.amahi.org/apps Amahi App Store] will be available for install.<br />
<br />
* As you proceed to install applications, compare the version you install with the version listed in the ''migration text''. That will give you an indication if a database or configuration file restore will be successful.<br />
<br />
* If you have any database(s) and configuration file(s) saved for applications, you can restore them in most cases. Database(s) can be restored via command line or using a MySQL application such as, [https://www.amahi.org/apps/adminer Adminer] or [https://www.amahi.org/apps/phpmyadmin phpMyAdmin].<br />
<br />
* Obviously you don't have to install all the applications you had on the previous system and you can choose to install new ones as well.<br />
<br />
:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You can now manually install any apps from sources other than the [https://www.amahi.org/apps Amahi App Store] if needed.</div><br />
<br />
== Migrate Settings ==<br />
We are now ready to being updating the new HDA with our previous HDA settings. Start by selecting ''Setup'' from the Amahi Dashboard main page (<nowiki>http://hda</nowiki>).<br />
<br />
<u>Users Tab</u><br />
:Create ''New users''. Refer to '''USERS TAB''' section in the ''migration text''.<br />
<br />
<u>Shares Tab</u><br />
:Choose the appropriate section and complete as noted.<br />
:*''Details'' section: Create ''Shares''. Refer to '''SHARES TAB''' section in the ''migration text''.<br />
:*''Settings'' section. Update ''Work Group Name'' if needed. Refer to '''SETTINGS''' under the '''SHARES TAB''' section in the ''migration text''.<br />
<br />
<u>Network Tab</u><br />
:Choose the appropriate section and complete as noted.<br />
:*''Fixed IPs'' section: Create ''Fixed IPs''. Refer to '''FIXED IP''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
:*''DNS Aliases'' section: Create ''DNS Aliases''. Refer to '''DNS ALIASES''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
:*''Settings'' section:<br />
::*Disable ''DHCP Server'' and/or ''DNS Server'' if needed. Refer to '''DHCP/DNS SERVER''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Lease Time'' if needed. Refer to '''DHCP Lease Time''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Change ''DNS Provider'' if needed. Refer to '''DNS PROVIDER''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Gateway'' if needed. Refer to '''GATEWAY''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Dynamic IP Range'' (Fedora 21/23<!--/25--> '''ONLY''') if needed. Refer to '''DYNAMIC IP RANGE''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
<br />
<u>Settings Tab</u><br />
:Enable ''Advanced Settings'' and/or ''Guest Dashboard''. Refer to '''SETTINGS TAB''' section in the ''migration text''.<br />
<br />
You should now have the majority of your settings restored. Double check to ensure you did not overlook anything before moving to the next section.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You can now make any manual configuration changes that are needed.</div><br />
<br />
== Setup Greyhole ==<br />
If you do not want to use [https://wiki.amahi.org/index.php/Greyhole Greyhole], you can '''SKIP''' this section. <br />
<br />
Otherwise, you have two options for installing Greyhole:<br />
<br />
<u>Manual</u><br /><br />
Follow the [[Amahi_Create_Manual_Greyhole_Setup|Manual configuration]] and [[Reconnect existing Greyhole storage pool]] guidance. Refer to '''greyhole.conf''' section in the ''migration text'' as needed.<br /><br />
<br />
or<br />
<br />
<u>Automated</u><br /><br />
Install the [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application. In the Amahi Dashboard, navigate to the '''Drive Pooling''' tab and choose:<br />
* '''Partitions''' section and select the appropriate ''Locations'' for the ''Pool''. Refer to '''greyhole.conf''' section (''storage_pool_directory'' line) in the ''migration text'' to verify the correct partitions are chosen. <br />
<br />
:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' If [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application was installed on your previous HDA, you should refer to '''DRIVE POOLING TAB''' section in the ''migration text'' rather than '''greyhole.conf''' section.</div><br />
* '''Shares''' section<br />
** Choose ''Storage Pool'' for the applicable ''Shares''. Refer to '''greyhole.conf''' (''num_copies'' line) section in the ''migration text'' to verify the correct ''Shares'' are chosen.<br />
** Select the appropriate ''Number Copies'' for ''Shares''. Refer to '''greyhole.conf''' section (''num_copies'' line) in the ''migration text'' to verify the correct ''Number Copies'' are chosen.<br />
<br />
::<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' If [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application was installed on your previous HDA, you should refer to '''SHARES TAB''' (''Disk Pool Copies'' column) section in the ''migration text'' to determine the appropriate setting.</div><br />
<br />
<u>Additional Settings</u><br /><br />
[https://wiki.amahi.org/index.php/Greyhole#Greyhole_Advanced_Options Greyhole Advanced Options] are configured in ''greyhole.yml'' file (''/var/hda/platform/html/config''). Compare the contents with the '''greyhole.yml''' section in the ''migration text'' for any differences. Make changes as needed.<br />
<br />
<u>Verify Operational</u><br /><br />
Before proceeding to the next section, verify Greyhole is working properly. This can be done by monitoring the log:<br />
tail -f /var/log/grehole.log<br />
If there is a problem, refer to [https://wiki.amahi.org/index.php/Greyhole_troubleshooting Greyhole Troubleshooting]. Don't forget to install [https://wiki.amahi.org/index.php/Mount_Shares_Locally Mount Shares Locally] service if needed.<br />
<br />
== Final Verification ==<br />
All the settings and configuration changes from your previous HDA should now be complete. Recommend you verify that everything is working as desired. Its best to check things over thoroughly now to prevent an unexpected surprise later.<br />
<br />
If something is not working as expected, double check ''migration text'' to ensure you didn't make any errors. Depending on the issue, you may need to refer to the [https://wiki.amahi.org/index.php/Troubleshooting Amahi Troubleshooting] guidance.<br />
<br />
Providing there are no problems, you should now have a fully functional up-to-date Amahi HDA.<br />
<br />
== Additional Tips ==<br />
Each HDA is unique as will be the migration to a different Amahi supported OS. There are additional steps you can accomplish to make the transition a bit smoother.<br />
<br />
Recommend backing up:<br />
* App database(s) and configuration file(s)<br />
* ''.bashrc'' and ''.vimrc'' files for each user<br />
* User added terminal scripts<br />
* Screen capture of dashboard tabs</div>Bigfoot65https://wiki.amahi.org/index.php?title=HDA_OS_Migration_Guide&diff=117656HDA OS Migration Guide2021-12-12T23:23:57Z<p>Bigfoot65: /* Backup Settings */</p>
<hr />
<div><p>The purpose of this tutorial is to provide a method for migrating Amahi HDA settings from one Amahi supported OS to another via a new install, such as:<br />
<br />
* [[Amahi 10|Fedora 25]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Amahi 9|Fedora 23]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Amahi 8|Fedora 21]] to [[Amahi 12|Fedora 27]]<br />
<br />
* [[Fedora 19]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Ubuntu|Ubuntu 12.04.x LTS]] to [[Amahi 11|Fedora 27]]<br />
<br /><br />
Currently there '''IS NOT''' an automated upgrade path for Ubuntu or a method for backing up current HDA settings for a reinstall. It is a manual process! However, we have provided a script to capture most of the settings you will need for a new Amahi HDA. We hope this will make it a more manageable task than it has been in the past.</p><br />
<br />
== Disclaimer ==<br />
<p>Please understand this is a guide to assist you in the migration. There is no guarantee this guidance will work for everyone. While every effort has been taken to accurately document the migration steps, use at your own risk.</p><br />
<br />
== Backup Settings ==<br />
<p>As with any other migration process, you will need to back up your HDA settings. In order to make the new system look and feel like your current one, there are certain components we need to capture.</p><br />
<br />
<p>To make this as painless as possible, a script is being provided. Once you run the script, it will record all the important information such as users, shares, apps installed, network, and Greyhole configuration (if installed), and other settings in a text file. You can then copy that file to a safe location for use once the new system is ready to be configured.</p><br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], do the following: <br />
* Navigate to the root directory:<br />
cd /root<br />
* Download script for appropriate Amahi version:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
:''u1204_hda_migration.sh'' script (sha1sum 0b65de7520a420b68f137601cdb479784538f762)<br />
wget <nowiki>"https://drive.google.com/uc?export=download&id=0B64TOKt5XksaeU1DNzM5TUlSbFk" -O u1204_hda_migration.sh</nowiki><br />
:<u>Fedora 19</u><br />
:''f19_hda_migration.sh'' script (sha1sum 777a27a4aa0f5192420585da0303f0b0defedd8d):<br />
wget <nowiki>"https://drive.google.com/file/d/1Ait2fBxqoQJcKfj-gzeurYT46v07jaT7" -O f19_hda_migration.sh</nowiki><br />
:<u>Fedora 21/23</u><br />
:''f21_hda_migration.sh'' script (sha1sum 5de37d8a18b9ea51a31c7964da9b7e41b74d34e7):<br />
wget <nowiki>"https://drive.google.com/file/d/19UgoU5wDdLO63Mh37478avV_Z98yx5rE" -O f21_hda_migration.sh</nowiki><br />
:<u>Fedora 25</u><br />
:''f25_hda_migration.sh'' script (sha1sum 5de37d8a18b9ea51a31c7964da9b7e41b74d34e7):<br />
wget <nowiki>"https://drive.google.com/file/d/1Gg1CxfudvDtZgxlCLDgMLdDGdFk-Lf01" -O f25_hda_migration.sh</nowiki><br />
<br />
* Make it executable:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
chmod 755 u1204_hda_migration.sh<br />
:<u>Fedora 19</u><br />
chmod 755 f19_hda_migration.sh<br />
:<u>Fedora 21/23</u><br />
chmod 755 f21_hda_migration.sh<br />
:<u>Fedora 25</u><br />
chmod 755 f25_hda_migration.sh<br />
* Run the script:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
./u1204_hda_migration.sh<br />
:<u>Fedora 19</u><br />
./f19_hda_migration.sh<br />
:<u>Fedora 21/23/25/27</u><br />
./f21_hda_migration.sh<br />
If all goes well, you will see a message similar to the one below:<br />
<pre><br />
HDA Settings Backup Complete!<br />
Filename : hda_production_migration.txt<br />
Directory: /root<br />
</pre><br />
Copy '''hda_production_migration.txt''' (hereon referred to as ''migration text'') to another machine and view the contents. Ensure all your settings were accurately captured before proceeding to the next section. <br />
<br />
You can also print the file to make it easy to follow along as you go through the migrations steps. See [[HDA_OS_Migration_Guide#Additional Tips|Additional Tips]] below for optional steps you may want to complete.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''IMPORTANT:''' You will need to document any manual configuration changes or apps installed from sources other than the [https://www.amahi.org/apps Amahi App Store].</div><br />
<br />
== Greyhole Cleanup ==<br />
If you are not currently using [https://wiki.amahi.org/index.php/Greyhole Greyhole], you can '''SKIP''' this section. <br />
<br />
Otherwise, [https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], begin with emptying the trash:<br />
greyhole -a<br />
Also recommend you run a <code>fsck</code> to ensure all files are in place:<br />
greyhole -f<br />
Monitor activity via the log file:<br />
tail -f /var/log/greyhole.log<br />
Once it's complete, you can prepare to shutdown your system<br />
<br />
== Shutdown Preparation ==<br />
Before powering '''OFF''' the HDA, you need to:<br />
# Turn '''OFF''' DHCP server on the HDA<br />
# Turn '''ON''' your [https://wiki.amahi.org/index.php/Turning_off_DHCP_in_your_router router DHCP/DNS server]<br />
# Power '''OFF''' any clients that aren't needed<br />
# [https://wiki.amahi.org/index.php/RenewIP Renew DHCP lease] for clients to remain '''ON'''<br />
# Verify all clients have connectivity via the router<br />
# Download new [http://docs.amahi.org Amahi install image]<br />
<br />
<br />
Once you have the media ready for install, it's time to power '''OFF''' your HDA.<br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], execute:<br />
:<pre>shutdown now -P</pre><br />
:or<br />
:you can select the '''Shutdown''' icon (the '''<span style="color:red">RED</span>''' one) from the HDA Dashboard ''Settings'' tab.<br />
<br />
Once the HDA is '''OFF''', disconnect all hard drives except the one for the OS. You don't need to remove them, just disconnect the power and drive cables.<br />
<br />
== New Installation ==<br />
To begin:<br />
* Power '''ON''' your HDA<br />
* Insert installation media (reboot if needed)<br />
* Follow the appropriate [http://docs.amahi.org Amahi installation instructions]<br />
* Once complete, '''DO NOT''' disable the router DHCP/DNS server yet.<br />
<br />
== Validate Success ==<br />
Once the install is complete, you need to validate the install was successful. Ensure everything is working correctly before proceeding to the next section.<br />
<br />
What you should check:<br />
* Does the HDA boot successfully and without errors<br />
* Can you connect to the Amahi Dashboard (<nowiki>http://hda</nowiki> or by IP Address)<br />
* Does the HDA have internet connectivity (try <code>yum list hda-platform</code>)<br />
<br />
<br />
If you have problems, refer to the [https://wiki.amahi.org/index.php/Network_troubleshooting Network Troubleshooting] guide in the wiki.<br />
<br />
Once everything appears to be working, you can now disable your [https://wiki.amahi.org/index.php/Turning_off_DHCP_in_your_router router DHCP/DNS server]. The Amahi HDA will become your DHCP/DNS server for the network. <br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You will need to [https://wiki.amahi.org/index.php/RenewIP renew the DHCP lease] on any client systems currently connected to the network.</div><br />
<br />
== Configure Drives ==<br />
If you do not have any additional drives to connect to your HDA, you can '''SKIP''' this section.<br />
<br />
Otherwise, you will need to:<br />
* Power '''OFF''' the HDA<br />
* Reconnect the power and drive cables<br />
* Power '''ON''' the HDA<br />
<br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], edit ''/etc/fstab'':<br />
vi /etc/fstab<br />
* Append entries the end of the file as noted in the '''fstab''' section of the ''migration text''. For example:<br />
:<pre>UUID=b7017251-cb54-438b-92a3-781537c565e6 /var/hda/files/drives/sdb ext4 defaults 1 2 noatime,data=writeback,nofail</pre><br />
* Ensure you '''DO NOT''' add any drive lines that contain ''/'', ''/boot'', or ''swap''. For example:<br />
:<pre>UUID=1ebbf241-528c-465e-889f-acc15400dd8c / ext4 defaults 1 1</pre><br />
* Create directories that correspond the the path in the drive lines. For example:<br />
:<pre>mkdir -p /var/hda/files/drives/sdb</pre><br />
:indicates a drive listed in ''/etc/fstab'' will be mounted at this location.<br />
<br />
Once you have all the drives added to ''/etc/fstab'' and the directories created, you can then mount the drives.<br />
mount -a<br />
If there are any errors, compare with the '''fstab''' section of the ''migration text''. '''DO NOT''' proceed to the next section until all drives are correctly mounted.<br />
<br />
To add additional drives to your HDA for Greyhole, please use the Amahi [https://www.amahi.org/apps/disk-wizard Disk Wizard] application which provides a Dashboard UI for this process. The [[Adding_a_second_hard_drive_to_your_HDA|adding a second hard drive]] from command-line documentation is also available.<br />
<br />
== Install Applications ==<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''WARNING:''' Some applications may not be ''LIVE'' for the new Amahi supported OS. Also the application version could be newer than you had installed on your previous HDA. As a result, the databases(s) and/or configuration files(s) may not be compatible.</div><br />
<br />
Refer to the '''INSTALLED APPS TAB''' section of the ''migration text'' to determine applications to install. Any [http://www.amahi.org/faq/if-i-pay-for-an-app-when-your-next-version-comes-out-do-i-have-to-pay-for-your-app-again previously purchased applications] from the [https://www.amahi.org/apps Amahi App Store] will be available for install.<br />
<br />
* As you proceed to install applications, compare the version you install with the version listed in the ''migration text''. That will give you an indication if a database or configuration file restore will be successful.<br />
<br />
* If you have any database(s) and configuration file(s) saved for applications, you can restore them in most cases. Database(s) can be restored via command line or using a MySQL application such as, [https://www.amahi.org/apps/adminer Adminer] or [https://www.amahi.org/apps/phpmyadmin phpMyAdmin].<br />
<br />
* Obviously you don't have to install all the applications you had on the previous system and you can choose to install new ones as well.<br />
<br />
:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You can now manually install any apps from sources other than the [https://www.amahi.org/apps Amahi App Store] if needed.</div><br />
<br />
== Migrate Settings ==<br />
We are now ready to being updating the new HDA with our previous HDA settings. Start by selecting ''Setup'' from the Amahi Dashboard main page (<nowiki>http://hda</nowiki>).<br />
<br />
<u>Users Tab</u><br />
:Create ''New users''. Refer to '''USERS TAB''' section in the ''migration text''.<br />
<br />
<u>Shares Tab</u><br />
:Choose the appropriate section and complete as noted.<br />
:*''Details'' section: Create ''Shares''. Refer to '''SHARES TAB''' section in the ''migration text''.<br />
:*''Settings'' section. Update ''Work Group Name'' if needed. Refer to '''SETTINGS''' under the '''SHARES TAB''' section in the ''migration text''.<br />
<br />
<u>Network Tab</u><br />
:Choose the appropriate section and complete as noted.<br />
:*''Fixed IPs'' section: Create ''Fixed IPs''. Refer to '''FIXED IP''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
:*''DNS Aliases'' section: Create ''DNS Aliases''. Refer to '''DNS ALIASES''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
:*''Settings'' section:<br />
::*Disable ''DHCP Server'' and/or ''DNS Server'' if needed. Refer to '''DHCP/DNS SERVER''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Lease Time'' if needed. Refer to '''DHCP Lease Time''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Change ''DNS Provider'' if needed. Refer to '''DNS PROVIDER''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Gateway'' if needed. Refer to '''GATEWAY''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Dynamic IP Range'' (Fedora 21/23<!--/25--> '''ONLY''') if needed. Refer to '''DYNAMIC IP RANGE''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
<br />
<u>Settings Tab</u><br />
:Enable ''Advanced Settings'' and/or ''Guest Dashboard''. Refer to '''SETTINGS TAB''' section in the ''migration text''.<br />
<br />
You should now have the majority of your settings restored. Double check to ensure you did not overlook anything before moving to the next section.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You can now make any manual configuration changes that are needed.</div><br />
<br />
== Setup Greyhole ==<br />
If you do not want to use [https://wiki.amahi.org/index.php/Greyhole Greyhole], you can '''SKIP''' this section. <br />
<br />
Otherwise, you have two options for installing Greyhole:<br />
<br />
<u>Manual</u><br /><br />
Follow the [[Amahi_Create_Manual_Greyhole_Setup|Manual configuration]] and [[Reconnect existing Greyhole storage pool]] guidance. Refer to '''greyhole.conf''' section in the ''migration text'' as needed.<br /><br />
<br />
or<br />
<br />
<u>Automated</u><br /><br />
Install the [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application. In the Amahi Dashboard, navigate to the '''Drive Pooling''' tab and choose:<br />
* '''Partitions''' section and select the appropriate ''Locations'' for the ''Pool''. Refer to '''greyhole.conf''' section (''storage_pool_directory'' line) in the ''migration text'' to verify the correct partitions are chosen. <br />
<br />
:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' If [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application was installed on your previous HDA, you should refer to '''DRIVE POOLING TAB''' section in the ''migration text'' rather than '''greyhole.conf''' section.</div><br />
* '''Shares''' section<br />
** Choose ''Storage Pool'' for the applicable ''Shares''. Refer to '''greyhole.conf''' (''num_copies'' line) section in the ''migration text'' to verify the correct ''Shares'' are chosen.<br />
** Select the appropriate ''Number Copies'' for ''Shares''. Refer to '''greyhole.conf''' section (''num_copies'' line) in the ''migration text'' to verify the correct ''Number Copies'' are chosen.<br />
<br />
::<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' If [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application was installed on your previous HDA, you should refer to '''SHARES TAB''' (''Disk Pool Copies'' column) section in the ''migration text'' to determine the appropriate setting.</div><br />
<br />
<u>Additional Settings</u><br /><br />
[https://wiki.amahi.org/index.php/Greyhole#Greyhole_Advanced_Options Greyhole Advanced Options] are configured in ''greyhole.yml'' file (''/var/hda/platform/html/config''). Compare the contents with the '''greyhole.yml''' section in the ''migration text'' for any differences. Make changes as needed.<br />
<br />
<u>Verify Operational</u><br /><br />
Before proceeding to the next section, verify Greyhole is working properly. This can be done by monitoring the log:<br />
tail -f /var/log/grehole.log<br />
If there is a problem, refer to [https://wiki.amahi.org/index.php/Greyhole_troubleshooting Greyhole Troubleshooting]. Don't forget to install [https://wiki.amahi.org/index.php/Mount_Shares_Locally Mount Shares Locally] service if needed.<br />
<br />
== Final Verification ==<br />
All the settings and configuration changes from your previous HDA should now be complete. Recommend you verify that everything is working as desired. Its best to check things over thoroughly now to prevent an unexpected surprise later.<br />
<br />
If something is not working as expected, double check ''migration text'' to ensure you didn't make any errors. Depending on the issue, you may need to refer to the [https://wiki.amahi.org/index.php/Troubleshooting Amahi Troubleshooting] guidance.<br />
<br />
Providing there are no problems, you should now have a fully functional up-to-date Amahi HDA.<br />
<br />
== Additional Tips ==<br />
Each HDA is unique as will be the migration to a different Amahi supported OS. There are additional steps you can accomplish to make the transition a bit smoother.<br />
<br />
Recommend backing up:<br />
* App database(s) and configuration file(s)<br />
* ''.bashrc'' and ''.vimrc'' files for each user<br />
* User added terminal scripts<br />
* Screen capture of dashboard tabs</div>Bigfoot65https://wiki.amahi.org/index.php?title=HDA_OS_Migration_Guide&diff=117651HDA OS Migration Guide2021-12-12T23:22:46Z<p>Bigfoot65: /* Backup Settings */</p>
<hr />
<div><p>The purpose of this tutorial is to provide a method for migrating Amahi HDA settings from one Amahi supported OS to another via a new install, such as:<br />
<br />
* [[Amahi 10|Fedora 25]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Amahi 9|Fedora 23]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Amahi 8|Fedora 21]] to [[Amahi 12|Fedora 27]]<br />
<br />
* [[Fedora 19]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Ubuntu|Ubuntu 12.04.x LTS]] to [[Amahi 11|Fedora 27]]<br />
<br /><br />
Currently there '''IS NOT''' an automated upgrade path for Ubuntu or a method for backing up current HDA settings for a reinstall. It is a manual process! However, we have provided a script to capture most of the settings you will need for a new Amahi HDA. We hope this will make it a more manageable task than it has been in the past.</p><br />
<br />
== Disclaimer ==<br />
<p>Please understand this is a guide to assist you in the migration. There is no guarantee this guidance will work for everyone. While every effort has been taken to accurately document the migration steps, use at your own risk.</p><br />
<br />
== Backup Settings ==<br />
<p>As with any other migration process, you will need to back up your HDA settings. In order to make the new system look and feel like your current one, there are certain components we need to capture.</p><br />
<br />
<p>To make this as painless as possible, a script is being provided. Once you run the script, it will record all the important information such as users, shares, apps installed, network, and Greyhole configuration (if installed), and other settings in a text file. You can then copy that file to a safe location for use once the new system is ready to be configured.</p><br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], do the following: <br />
* Navigate to the root directory:<br />
cd /root<br />
* Download script for appropriate Amahi version:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
:''u1204_hda_migration.sh'' script (sha1sum 0b65de7520a420b68f137601cdb479784538f762)<br />
wget <nowiki>"https://drive.google.com/uc?export=download&id=0B64TOKt5XksaeU1DNzM5TUlSbFk" -O u1204_hda_migration.sh</nowiki><br />
:<u>Fedora 19</u><br />
:''f19_hda_migration.sh'' script (sha1sum 777a27a4aa0f5192420585da0303f0b0defedd8d):<br />
wget <nowiki>"https://drive.google.com/file/d/1Ait2fBxqoQJcKfj-gzeurYT46v07jaT7" -O f19_hda_migration.sh</nowiki><br />
:<u>Fedora 21/23</u><br />
:''f21_hda_migration.sh'' script (sha1sum 5de37d8a18b9ea51a31c7964da9b7e41b74d34e7):<br />
wget <nowiki>"https://drive.google.com/file/d/19UgoU5wDdLO63Mh37478avV_Z98yx5rE" -O f21_hda_migration.sh</nowiki><br />
:<u>Fedora 25</u><br />
:''f25_hda_migration.sh'' script (sha1sum 5de37d8a18b9ea51a31c7964da9b7e41b74d34e7):<br />
wget <nowiki>"https://drive.google.com/file/d/1Gg1CxfudvDtZgxlCLDgMLdDGdFk-Lf01" -O f25_hda_migration.sh</nowiki><br />
<br />
* Make it executable:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
chmod 755 u1204_hda_migration.sh<br />
:<u>Fedora 19</u><br />
chmod 755 f19_hda_migration.sh<br />
:<u>Fedora 21/23/25</u><br />
chmod 755 f21_hda_migration.sh<br />
* Run the script:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
./u1204_hda_migration.sh<br />
:<u>Fedora 19</u><br />
./f19_hda_migration.sh<br />
:<u>Fedora 21/23/25/27</u><br />
./f21_hda_migration.sh<br />
If all goes well, you will see a message similar to the one below:<br />
<pre><br />
HDA Settings Backup Complete!<br />
Filename : hda_production_migration.txt<br />
Directory: /root<br />
</pre><br />
Copy '''hda_production_migration.txt''' (hereon referred to as ''migration text'') to another machine and view the contents. Ensure all your settings were accurately captured before proceeding to the next section. <br />
<br />
You can also print the file to make it easy to follow along as you go through the migrations steps. See [[HDA_OS_Migration_Guide#Additional Tips|Additional Tips]] below for optional steps you may want to complete.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''IMPORTANT:''' You will need to document any manual configuration changes or apps installed from sources other than the [https://www.amahi.org/apps Amahi App Store].</div><br />
<br />
== Greyhole Cleanup ==<br />
If you are not currently using [https://wiki.amahi.org/index.php/Greyhole Greyhole], you can '''SKIP''' this section. <br />
<br />
Otherwise, [https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], begin with emptying the trash:<br />
greyhole -a<br />
Also recommend you run a <code>fsck</code> to ensure all files are in place:<br />
greyhole -f<br />
Monitor activity via the log file:<br />
tail -f /var/log/greyhole.log<br />
Once it's complete, you can prepare to shutdown your system<br />
<br />
== Shutdown Preparation ==<br />
Before powering '''OFF''' the HDA, you need to:<br />
# Turn '''OFF''' DHCP server on the HDA<br />
# Turn '''ON''' your [https://wiki.amahi.org/index.php/Turning_off_DHCP_in_your_router router DHCP/DNS server]<br />
# Power '''OFF''' any clients that aren't needed<br />
# [https://wiki.amahi.org/index.php/RenewIP Renew DHCP lease] for clients to remain '''ON'''<br />
# Verify all clients have connectivity via the router<br />
# Download new [http://docs.amahi.org Amahi install image]<br />
<br />
<br />
Once you have the media ready for install, it's time to power '''OFF''' your HDA.<br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], execute:<br />
:<pre>shutdown now -P</pre><br />
:or<br />
:you can select the '''Shutdown''' icon (the '''<span style="color:red">RED</span>''' one) from the HDA Dashboard ''Settings'' tab.<br />
<br />
Once the HDA is '''OFF''', disconnect all hard drives except the one for the OS. You don't need to remove them, just disconnect the power and drive cables.<br />
<br />
== New Installation ==<br />
To begin:<br />
* Power '''ON''' your HDA<br />
* Insert installation media (reboot if needed)<br />
* Follow the appropriate [http://docs.amahi.org Amahi installation instructions]<br />
* Once complete, '''DO NOT''' disable the router DHCP/DNS server yet.<br />
<br />
== Validate Success ==<br />
Once the install is complete, you need to validate the install was successful. Ensure everything is working correctly before proceeding to the next section.<br />
<br />
What you should check:<br />
* Does the HDA boot successfully and without errors<br />
* Can you connect to the Amahi Dashboard (<nowiki>http://hda</nowiki> or by IP Address)<br />
* Does the HDA have internet connectivity (try <code>yum list hda-platform</code>)<br />
<br />
<br />
If you have problems, refer to the [https://wiki.amahi.org/index.php/Network_troubleshooting Network Troubleshooting] guide in the wiki.<br />
<br />
Once everything appears to be working, you can now disable your [https://wiki.amahi.org/index.php/Turning_off_DHCP_in_your_router router DHCP/DNS server]. The Amahi HDA will become your DHCP/DNS server for the network. <br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You will need to [https://wiki.amahi.org/index.php/RenewIP renew the DHCP lease] on any client systems currently connected to the network.</div><br />
<br />
== Configure Drives ==<br />
If you do not have any additional drives to connect to your HDA, you can '''SKIP''' this section.<br />
<br />
Otherwise, you will need to:<br />
* Power '''OFF''' the HDA<br />
* Reconnect the power and drive cables<br />
* Power '''ON''' the HDA<br />
<br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], edit ''/etc/fstab'':<br />
vi /etc/fstab<br />
* Append entries the end of the file as noted in the '''fstab''' section of the ''migration text''. For example:<br />
:<pre>UUID=b7017251-cb54-438b-92a3-781537c565e6 /var/hda/files/drives/sdb ext4 defaults 1 2 noatime,data=writeback,nofail</pre><br />
* Ensure you '''DO NOT''' add any drive lines that contain ''/'', ''/boot'', or ''swap''. For example:<br />
:<pre>UUID=1ebbf241-528c-465e-889f-acc15400dd8c / ext4 defaults 1 1</pre><br />
* Create directories that correspond the the path in the drive lines. For example:<br />
:<pre>mkdir -p /var/hda/files/drives/sdb</pre><br />
:indicates a drive listed in ''/etc/fstab'' will be mounted at this location.<br />
<br />
Once you have all the drives added to ''/etc/fstab'' and the directories created, you can then mount the drives.<br />
mount -a<br />
If there are any errors, compare with the '''fstab''' section of the ''migration text''. '''DO NOT''' proceed to the next section until all drives are correctly mounted.<br />
<br />
To add additional drives to your HDA for Greyhole, please use the Amahi [https://www.amahi.org/apps/disk-wizard Disk Wizard] application which provides a Dashboard UI for this process. The [[Adding_a_second_hard_drive_to_your_HDA|adding a second hard drive]] from command-line documentation is also available.<br />
<br />
== Install Applications ==<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''WARNING:''' Some applications may not be ''LIVE'' for the new Amahi supported OS. Also the application version could be newer than you had installed on your previous HDA. As a result, the databases(s) and/or configuration files(s) may not be compatible.</div><br />
<br />
Refer to the '''INSTALLED APPS TAB''' section of the ''migration text'' to determine applications to install. Any [http://www.amahi.org/faq/if-i-pay-for-an-app-when-your-next-version-comes-out-do-i-have-to-pay-for-your-app-again previously purchased applications] from the [https://www.amahi.org/apps Amahi App Store] will be available for install.<br />
<br />
* As you proceed to install applications, compare the version you install with the version listed in the ''migration text''. That will give you an indication if a database or configuration file restore will be successful.<br />
<br />
* If you have any database(s) and configuration file(s) saved for applications, you can restore them in most cases. Database(s) can be restored via command line or using a MySQL application such as, [https://www.amahi.org/apps/adminer Adminer] or [https://www.amahi.org/apps/phpmyadmin phpMyAdmin].<br />
<br />
* Obviously you don't have to install all the applications you had on the previous system and you can choose to install new ones as well.<br />
<br />
:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You can now manually install any apps from sources other than the [https://www.amahi.org/apps Amahi App Store] if needed.</div><br />
<br />
== Migrate Settings ==<br />
We are now ready to being updating the new HDA with our previous HDA settings. Start by selecting ''Setup'' from the Amahi Dashboard main page (<nowiki>http://hda</nowiki>).<br />
<br />
<u>Users Tab</u><br />
:Create ''New users''. Refer to '''USERS TAB''' section in the ''migration text''.<br />
<br />
<u>Shares Tab</u><br />
:Choose the appropriate section and complete as noted.<br />
:*''Details'' section: Create ''Shares''. Refer to '''SHARES TAB''' section in the ''migration text''.<br />
:*''Settings'' section. Update ''Work Group Name'' if needed. Refer to '''SETTINGS''' under the '''SHARES TAB''' section in the ''migration text''.<br />
<br />
<u>Network Tab</u><br />
:Choose the appropriate section and complete as noted.<br />
:*''Fixed IPs'' section: Create ''Fixed IPs''. Refer to '''FIXED IP''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
:*''DNS Aliases'' section: Create ''DNS Aliases''. Refer to '''DNS ALIASES''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
:*''Settings'' section:<br />
::*Disable ''DHCP Server'' and/or ''DNS Server'' if needed. Refer to '''DHCP/DNS SERVER''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Lease Time'' if needed. Refer to '''DHCP Lease Time''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Change ''DNS Provider'' if needed. Refer to '''DNS PROVIDER''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Gateway'' if needed. Refer to '''GATEWAY''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Dynamic IP Range'' (Fedora 21/23<!--/25--> '''ONLY''') if needed. Refer to '''DYNAMIC IP RANGE''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
<br />
<u>Settings Tab</u><br />
:Enable ''Advanced Settings'' and/or ''Guest Dashboard''. Refer to '''SETTINGS TAB''' section in the ''migration text''.<br />
<br />
You should now have the majority of your settings restored. Double check to ensure you did not overlook anything before moving to the next section.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You can now make any manual configuration changes that are needed.</div><br />
<br />
== Setup Greyhole ==<br />
If you do not want to use [https://wiki.amahi.org/index.php/Greyhole Greyhole], you can '''SKIP''' this section. <br />
<br />
Otherwise, you have two options for installing Greyhole:<br />
<br />
<u>Manual</u><br /><br />
Follow the [[Amahi_Create_Manual_Greyhole_Setup|Manual configuration]] and [[Reconnect existing Greyhole storage pool]] guidance. Refer to '''greyhole.conf''' section in the ''migration text'' as needed.<br /><br />
<br />
or<br />
<br />
<u>Automated</u><br /><br />
Install the [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application. In the Amahi Dashboard, navigate to the '''Drive Pooling''' tab and choose:<br />
* '''Partitions''' section and select the appropriate ''Locations'' for the ''Pool''. Refer to '''greyhole.conf''' section (''storage_pool_directory'' line) in the ''migration text'' to verify the correct partitions are chosen. <br />
<br />
:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' If [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application was installed on your previous HDA, you should refer to '''DRIVE POOLING TAB''' section in the ''migration text'' rather than '''greyhole.conf''' section.</div><br />
* '''Shares''' section<br />
** Choose ''Storage Pool'' for the applicable ''Shares''. Refer to '''greyhole.conf''' (''num_copies'' line) section in the ''migration text'' to verify the correct ''Shares'' are chosen.<br />
** Select the appropriate ''Number Copies'' for ''Shares''. Refer to '''greyhole.conf''' section (''num_copies'' line) in the ''migration text'' to verify the correct ''Number Copies'' are chosen.<br />
<br />
::<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' If [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application was installed on your previous HDA, you should refer to '''SHARES TAB''' (''Disk Pool Copies'' column) section in the ''migration text'' to determine the appropriate setting.</div><br />
<br />
<u>Additional Settings</u><br /><br />
[https://wiki.amahi.org/index.php/Greyhole#Greyhole_Advanced_Options Greyhole Advanced Options] are configured in ''greyhole.yml'' file (''/var/hda/platform/html/config''). Compare the contents with the '''greyhole.yml''' section in the ''migration text'' for any differences. Make changes as needed.<br />
<br />
<u>Verify Operational</u><br /><br />
Before proceeding to the next section, verify Greyhole is working properly. This can be done by monitoring the log:<br />
tail -f /var/log/grehole.log<br />
If there is a problem, refer to [https://wiki.amahi.org/index.php/Greyhole_troubleshooting Greyhole Troubleshooting]. Don't forget to install [https://wiki.amahi.org/index.php/Mount_Shares_Locally Mount Shares Locally] service if needed.<br />
<br />
== Final Verification ==<br />
All the settings and configuration changes from your previous HDA should now be complete. Recommend you verify that everything is working as desired. Its best to check things over thoroughly now to prevent an unexpected surprise later.<br />
<br />
If something is not working as expected, double check ''migration text'' to ensure you didn't make any errors. Depending on the issue, you may need to refer to the [https://wiki.amahi.org/index.php/Troubleshooting Amahi Troubleshooting] guidance.<br />
<br />
Providing there are no problems, you should now have a fully functional up-to-date Amahi HDA.<br />
<br />
== Additional Tips ==<br />
Each HDA is unique as will be the migration to a different Amahi supported OS. There are additional steps you can accomplish to make the transition a bit smoother.<br />
<br />
Recommend backing up:<br />
* App database(s) and configuration file(s)<br />
* ''.bashrc'' and ''.vimrc'' files for each user<br />
* User added terminal scripts<br />
* Screen capture of dashboard tabs</div>Bigfoot65https://wiki.amahi.org/index.php?title=HDA_OS_Migration_Guide&diff=117646HDA OS Migration Guide2021-12-12T23:22:25Z<p>Bigfoot65: /* Backup Settings */</p>
<hr />
<div><p>The purpose of this tutorial is to provide a method for migrating Amahi HDA settings from one Amahi supported OS to another via a new install, such as:<br />
<br />
* [[Amahi 10|Fedora 25]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Amahi 9|Fedora 23]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Amahi 8|Fedora 21]] to [[Amahi 12|Fedora 27]]<br />
<br />
* [[Fedora 19]] to [[Amahi 11|Fedora 27]]<br />
<br />
* [[Ubuntu|Ubuntu 12.04.x LTS]] to [[Amahi 11|Fedora 27]]<br />
<br /><br />
Currently there '''IS NOT''' an automated upgrade path for Ubuntu or a method for backing up current HDA settings for a reinstall. It is a manual process! However, we have provided a script to capture most of the settings you will need for a new Amahi HDA. We hope this will make it a more manageable task than it has been in the past.</p><br />
<br />
== Disclaimer ==<br />
<p>Please understand this is a guide to assist you in the migration. There is no guarantee this guidance will work for everyone. While every effort has been taken to accurately document the migration steps, use at your own risk.</p><br />
<br />
== Backup Settings ==<br />
<p>As with any other migration process, you will need to back up your HDA settings. In order to make the new system look and feel like your current one, there are certain components we need to capture.</p><br />
<br />
<p>To make this as painless as possible, a script is being provided. Once you run the script, it will record all the important information such as users, shares, apps installed, network, and Greyhole configuration (if installed), and other settings in a text file. You can then copy that file to a safe location for use once the new system is ready to be configured.</p><br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], do the following: <br />
* Navigate to the root directory:<br />
cd /root<br />
* Download script for appropriate Amahi version:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
:''u1204_hda_migration.sh'' script (sha1sum 0b65de7520a420b68f137601cdb479784538f762)<br />
wget <nowiki>"https://drive.google.com/uc?export=download&id=0B64TOKt5XksaeU1DNzM5TUlSbFk" -O u1204_hda_migration.sh</nowiki><br />
:<u>Fedora 19</u><br />
:''f19_hda_migration.sh'' script (sha1sum 777a27a4aa0f5192420585da0303f0b0defedd8d):<br />
wget <nowiki>"https://drive.google.com/file/d/1Ait2fBxqoQJcKfj-gzeurYT46v07jaT7" -O f19_hda_migration.sh</nowiki><br />
:<u>Fedora 21/23</u><br />
:''f21_hda_migration.sh'' script (sha1sum 5de37d8a18b9ea51a31c7964da9b7e41b74d34e7):<br />
wget <nowiki>"https://drive.google.com/file/d/19UgoU5wDdLO63Mh37478avV_Z98yx5rE" -O f21_hda_migration.sh</nowiki><br />
:<u>Fedora 25</u><br />
:''f25_hda_migration.sh'' script (sha1sum 5de37d8a18b9ea51a31c7964da9b7e41b74d34e7):<br />
wget <nowiki>"https://drive.google.com/file/d/1Gg1CxfudvDtZgxlCLDgMLdDGdFk-Lf01/view?usp=sharing" -O f25_hda_migration.sh</nowiki><br />
<br />
* Make it executable:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
chmod 755 u1204_hda_migration.sh<br />
:<u>Fedora 19</u><br />
chmod 755 f19_hda_migration.sh<br />
:<u>Fedora 21/23/25</u><br />
chmod 755 f21_hda_migration.sh<br />
* Run the script:<br />
:<br />
:<u>Ubuntu 12.04.x</u><br />
./u1204_hda_migration.sh<br />
:<u>Fedora 19</u><br />
./f19_hda_migration.sh<br />
:<u>Fedora 21/23/25/27</u><br />
./f21_hda_migration.sh<br />
If all goes well, you will see a message similar to the one below:<br />
<pre><br />
HDA Settings Backup Complete!<br />
Filename : hda_production_migration.txt<br />
Directory: /root<br />
</pre><br />
Copy '''hda_production_migration.txt''' (hereon referred to as ''migration text'') to another machine and view the contents. Ensure all your settings were accurately captured before proceeding to the next section. <br />
<br />
You can also print the file to make it easy to follow along as you go through the migrations steps. See [[HDA_OS_Migration_Guide#Additional Tips|Additional Tips]] below for optional steps you may want to complete.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''IMPORTANT:''' You will need to document any manual configuration changes or apps installed from sources other than the [https://www.amahi.org/apps Amahi App Store].</div><br />
<br />
== Greyhole Cleanup ==<br />
If you are not currently using [https://wiki.amahi.org/index.php/Greyhole Greyhole], you can '''SKIP''' this section. <br />
<br />
Otherwise, [https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], begin with emptying the trash:<br />
greyhole -a<br />
Also recommend you run a <code>fsck</code> to ensure all files are in place:<br />
greyhole -f<br />
Monitor activity via the log file:<br />
tail -f /var/log/greyhole.log<br />
Once it's complete, you can prepare to shutdown your system<br />
<br />
== Shutdown Preparation ==<br />
Before powering '''OFF''' the HDA, you need to:<br />
# Turn '''OFF''' DHCP server on the HDA<br />
# Turn '''ON''' your [https://wiki.amahi.org/index.php/Turning_off_DHCP_in_your_router router DHCP/DNS server]<br />
# Power '''OFF''' any clients that aren't needed<br />
# [https://wiki.amahi.org/index.php/RenewIP Renew DHCP lease] for clients to remain '''ON'''<br />
# Verify all clients have connectivity via the router<br />
# Download new [http://docs.amahi.org Amahi install image]<br />
<br />
<br />
Once you have the media ready for install, it's time to power '''OFF''' your HDA.<br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], execute:<br />
:<pre>shutdown now -P</pre><br />
:or<br />
:you can select the '''Shutdown''' icon (the '''<span style="color:red">RED</span>''' one) from the HDA Dashboard ''Settings'' tab.<br />
<br />
Once the HDA is '''OFF''', disconnect all hard drives except the one for the OS. You don't need to remove them, just disconnect the power and drive cables.<br />
<br />
== New Installation ==<br />
To begin:<br />
* Power '''ON''' your HDA<br />
* Insert installation media (reboot if needed)<br />
* Follow the appropriate [http://docs.amahi.org Amahi installation instructions]<br />
* Once complete, '''DO NOT''' disable the router DHCP/DNS server yet.<br />
<br />
== Validate Success ==<br />
Once the install is complete, you need to validate the install was successful. Ensure everything is working correctly before proceeding to the next section.<br />
<br />
What you should check:<br />
* Does the HDA boot successfully and without errors<br />
* Can you connect to the Amahi Dashboard (<nowiki>http://hda</nowiki> or by IP Address)<br />
* Does the HDA have internet connectivity (try <code>yum list hda-platform</code>)<br />
<br />
<br />
If you have problems, refer to the [https://wiki.amahi.org/index.php/Network_troubleshooting Network Troubleshooting] guide in the wiki.<br />
<br />
Once everything appears to be working, you can now disable your [https://wiki.amahi.org/index.php/Turning_off_DHCP_in_your_router router DHCP/DNS server]. The Amahi HDA will become your DHCP/DNS server for the network. <br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You will need to [https://wiki.amahi.org/index.php/RenewIP renew the DHCP lease] on any client systems currently connected to the network.</div><br />
<br />
== Configure Drives ==<br />
If you do not have any additional drives to connect to your HDA, you can '''SKIP''' this section.<br />
<br />
Otherwise, you will need to:<br />
* Power '''OFF''' the HDA<br />
* Reconnect the power and drive cables<br />
* Power '''ON''' the HDA<br />
<br />
<br />
[https://wiki.amahi.org/index.php/Open_Terminal_as_root As root user], edit ''/etc/fstab'':<br />
vi /etc/fstab<br />
* Append entries the end of the file as noted in the '''fstab''' section of the ''migration text''. For example:<br />
:<pre>UUID=b7017251-cb54-438b-92a3-781537c565e6 /var/hda/files/drives/sdb ext4 defaults 1 2 noatime,data=writeback,nofail</pre><br />
* Ensure you '''DO NOT''' add any drive lines that contain ''/'', ''/boot'', or ''swap''. For example:<br />
:<pre>UUID=1ebbf241-528c-465e-889f-acc15400dd8c / ext4 defaults 1 1</pre><br />
* Create directories that correspond the the path in the drive lines. For example:<br />
:<pre>mkdir -p /var/hda/files/drives/sdb</pre><br />
:indicates a drive listed in ''/etc/fstab'' will be mounted at this location.<br />
<br />
Once you have all the drives added to ''/etc/fstab'' and the directories created, you can then mount the drives.<br />
mount -a<br />
If there are any errors, compare with the '''fstab''' section of the ''migration text''. '''DO NOT''' proceed to the next section until all drives are correctly mounted.<br />
<br />
To add additional drives to your HDA for Greyhole, please use the Amahi [https://www.amahi.org/apps/disk-wizard Disk Wizard] application which provides a Dashboard UI for this process. The [[Adding_a_second_hard_drive_to_your_HDA|adding a second hard drive]] from command-line documentation is also available.<br />
<br />
== Install Applications ==<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''WARNING:''' Some applications may not be ''LIVE'' for the new Amahi supported OS. Also the application version could be newer than you had installed on your previous HDA. As a result, the databases(s) and/or configuration files(s) may not be compatible.</div><br />
<br />
Refer to the '''INSTALLED APPS TAB''' section of the ''migration text'' to determine applications to install. Any [http://www.amahi.org/faq/if-i-pay-for-an-app-when-your-next-version-comes-out-do-i-have-to-pay-for-your-app-again previously purchased applications] from the [https://www.amahi.org/apps Amahi App Store] will be available for install.<br />
<br />
* As you proceed to install applications, compare the version you install with the version listed in the ''migration text''. That will give you an indication if a database or configuration file restore will be successful.<br />
<br />
* If you have any database(s) and configuration file(s) saved for applications, you can restore them in most cases. Database(s) can be restored via command line or using a MySQL application such as, [https://www.amahi.org/apps/adminer Adminer] or [https://www.amahi.org/apps/phpmyadmin phpMyAdmin].<br />
<br />
* Obviously you don't have to install all the applications you had on the previous system and you can choose to install new ones as well.<br />
<br />
:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You can now manually install any apps from sources other than the [https://www.amahi.org/apps Amahi App Store] if needed.</div><br />
<br />
== Migrate Settings ==<br />
We are now ready to being updating the new HDA with our previous HDA settings. Start by selecting ''Setup'' from the Amahi Dashboard main page (<nowiki>http://hda</nowiki>).<br />
<br />
<u>Users Tab</u><br />
:Create ''New users''. Refer to '''USERS TAB''' section in the ''migration text''.<br />
<br />
<u>Shares Tab</u><br />
:Choose the appropriate section and complete as noted.<br />
:*''Details'' section: Create ''Shares''. Refer to '''SHARES TAB''' section in the ''migration text''.<br />
:*''Settings'' section. Update ''Work Group Name'' if needed. Refer to '''SETTINGS''' under the '''SHARES TAB''' section in the ''migration text''.<br />
<br />
<u>Network Tab</u><br />
:Choose the appropriate section and complete as noted.<br />
:*''Fixed IPs'' section: Create ''Fixed IPs''. Refer to '''FIXED IP''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
:*''DNS Aliases'' section: Create ''DNS Aliases''. Refer to '''DNS ALIASES''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
:*''Settings'' section:<br />
::*Disable ''DHCP Server'' and/or ''DNS Server'' if needed. Refer to '''DHCP/DNS SERVER''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Lease Time'' if needed. Refer to '''DHCP Lease Time''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Change ''DNS Provider'' if needed. Refer to '''DNS PROVIDER''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Gateway'' if needed. Refer to '''GATEWAY''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
::*Update ''Dynamic IP Range'' (Fedora 21/23<!--/25--> '''ONLY''') if needed. Refer to '''DYNAMIC IP RANGE''' under the '''NETWORK TAB''' section in the ''migration text''.<br />
<br />
<u>Settings Tab</u><br />
:Enable ''Advanced Settings'' and/or ''Guest Dashboard''. Refer to '''SETTINGS TAB''' section in the ''migration text''.<br />
<br />
You should now have the majority of your settings restored. Double check to ensure you did not overlook anything before moving to the next section.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' You can now make any manual configuration changes that are needed.</div><br />
<br />
== Setup Greyhole ==<br />
If you do not want to use [https://wiki.amahi.org/index.php/Greyhole Greyhole], you can '''SKIP''' this section. <br />
<br />
Otherwise, you have two options for installing Greyhole:<br />
<br />
<u>Manual</u><br /><br />
Follow the [[Amahi_Create_Manual_Greyhole_Setup|Manual configuration]] and [[Reconnect existing Greyhole storage pool]] guidance. Refer to '''greyhole.conf''' section in the ''migration text'' as needed.<br /><br />
<br />
or<br />
<br />
<u>Automated</u><br /><br />
Install the [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application. In the Amahi Dashboard, navigate to the '''Drive Pooling''' tab and choose:<br />
* '''Partitions''' section and select the appropriate ''Locations'' for the ''Pool''. Refer to '''greyhole.conf''' section (''storage_pool_directory'' line) in the ''migration text'' to verify the correct partitions are chosen. <br />
<br />
:<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' If [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application was installed on your previous HDA, you should refer to '''DRIVE POOLING TAB''' section in the ''migration text'' rather than '''greyhole.conf''' section.</div><br />
* '''Shares''' section<br />
** Choose ''Storage Pool'' for the applicable ''Shares''. Refer to '''greyhole.conf''' (''num_copies'' line) section in the ''migration text'' to verify the correct ''Shares'' are chosen.<br />
** Select the appropriate ''Number Copies'' for ''Shares''. Refer to '''greyhole.conf''' section (''num_copies'' line) in the ''migration text'' to verify the correct ''Number Copies'' are chosen.<br />
<br />
::<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px;">'''NOTE:''' If [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application was installed on your previous HDA, you should refer to '''SHARES TAB''' (''Disk Pool Copies'' column) section in the ''migration text'' to determine the appropriate setting.</div><br />
<br />
<u>Additional Settings</u><br /><br />
[https://wiki.amahi.org/index.php/Greyhole#Greyhole_Advanced_Options Greyhole Advanced Options] are configured in ''greyhole.yml'' file (''/var/hda/platform/html/config''). Compare the contents with the '''greyhole.yml''' section in the ''migration text'' for any differences. Make changes as needed.<br />
<br />
<u>Verify Operational</u><br /><br />
Before proceeding to the next section, verify Greyhole is working properly. This can be done by monitoring the log:<br />
tail -f /var/log/grehole.log<br />
If there is a problem, refer to [https://wiki.amahi.org/index.php/Greyhole_troubleshooting Greyhole Troubleshooting]. Don't forget to install [https://wiki.amahi.org/index.php/Mount_Shares_Locally Mount Shares Locally] service if needed.<br />
<br />
== Final Verification ==<br />
All the settings and configuration changes from your previous HDA should now be complete. Recommend you verify that everything is working as desired. Its best to check things over thoroughly now to prevent an unexpected surprise later.<br />
<br />
If something is not working as expected, double check ''migration text'' to ensure you didn't make any errors. Depending on the issue, you may need to refer to the [https://wiki.amahi.org/index.php/Troubleshooting Amahi Troubleshooting] guidance.<br />
<br />
Providing there are no problems, you should now have a fully functional up-to-date Amahi HDA.<br />
<br />
== Additional Tips ==<br />
Each HDA is unique as will be the migration to a different Amahi supported OS. There are additional steps you can accomplish to make the transition a bit smoother.<br />
<br />
Recommend backing up:<br />
* App database(s) and configuration file(s)<br />
* ''.bashrc'' and ''.vimrc'' files for each user<br />
* User added terminal scripts<br />
* Screen capture of dashboard tabs</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117641Amahi 122021-11-25T03:28:54Z<p>Bigfoot65: /* To Do */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 35 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 35===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-netinst-x86_64-35-1.2.iso Fedora-Server-netinst-x86_64-35-1.2.iso]<br />
:&nbsp;(646 MB; SHA1 71a67fd53ba8bb25318b14bffbf170654129ccee)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-dvd-x86_64-35-1.2.iso Fedora-Server-dvd-x86_64-35-1.2.iso]<br />
:&nbsp;(2.07 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2441 Amahi Bug # 2441]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* <s>Add to Amahi repo:</s><br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** <s>''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]</s><br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* <s>Create OpenStack instances:</s><br />
** <s>Amahi Repo</s><br />
** <s>Amahi Test</s><br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 35 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Fedora_27_Server_DVD_Install&diff=117636Fedora 27 Server DVD Install2021-11-17T23:28:27Z<p>Bigfoot65: /* Install Amahi 11 */</p>
<hr />
<div>= Install Fedora 27 =<br />
This is only recommended for cases where the Minimal CD Install does not work well (e.g. if your hardware needs extra drivers).<br />
<br />
* Download the Fedora 27 Server DVD for 64 bit (2.3 GB), preferably using torrents<br />
** Torrent - [https://torrent.fedoraproject.org/torrents/Fedora-Server-dvd-x86_64-27.torrent Fedora-Server-dvd-x86_64-27.torrent] <br />
** HTTP - [https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/27/Server/x86_64/iso/Fedora-Server-dvd-x86_64-27-1.6.iso Fedora-Server-dvd-x86_64-27-1.6.iso] <br />
** Checksum:<br />
*** <code>MD5 f148145afbccebe532dc710362352052</code><br />
*** <code>SHA1 d3a671de536b969811df2874330a0ee652938ed2</code><br />
<br />
* Burn the ISO to DVD (or [[USB Install|USB]]), insert the media into your server, and reboot the system.<br />
<br />
* These instructions below will guide you through the Fedora 27 Server DVD installation with screen shots and commentary. If you are not an advanced Linux user and know what you are doing, recommend you '''DO NOT''' deviate from the guidance. Click '''[<Screenshot>]''' to show/hide the image.<br />
<br />
== Boot Screen ==<br />
<ul><br />
<li>Select ''Install Fedora 27''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:Fedora27-boot-screen.png|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
== Language Selection ==<br />
<ul><br />
<li>Choose desired language and select ''Continue''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS1.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
== Installation Summary ==<br />
<ul><br />
<li>Change the '''KEYBOARD''' or '''TIME & DATE''' to match your locale if needed.</li><br />
<li> Verify '''NETWORK & HOST NAME''' indicates ''connected''. Don't make any changes unless needed.</li> <br />
<li>Once complete, next choose ''INSTALLATION DESTINATION''. This is where you will select the disk drive to use.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27DVD_SS2.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
== Disk Drive Setup ==<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''WARNING:''' Amahi staff doesn't recommend using the default ''LVM'' partition scheme. Doing so will dedicate most of the drive space in the system to the ''/home'' partition. Amahi does not utilize this space, limiting storage for file shares and web applications. For best results and maximum storage, use the ''Standard'' partition scheme.</div><br />
<br />
<ul><br />
<li>Choose the disk drive you want to use for the Fedora installation. If you have more than one disk drive connected, '''DO NOT''' select them at this time. You will notice a ''check mark'' on the disk drive selected. Select ''Custom'' and then choose ''Done''.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS3A.PNG|600px]] <br />
</div><br></li><br />
<br />
<li>Should you have existing partitions on the disk drive you will be using for the Fedora 27 installation, they will have to be removed.</li><br />
<ul><br />
<li> You should see the existing partition about half way down the screen.</li><br />
<li>Choose it to expand and display the existing partitions for deletion. Select the first partition in the list followed by the minus (-) sign.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS3C.PNG|600px]] <br />
</div></li><br />
<li> When prompted ''Are you sure you want to delete all the data on ...?'', choose ''Delete It''.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS3D.PNG|400px]] <br />
</div></li><br />
<li> Repeat the previous two steps until all the existing partitions on the disk drive are gone.</li><br />
</ul><br />
<br />
<li>Ensure the ''New mount points will use the following partitioning scheme:'' is changed to reflect '''Standard partition'''. Then select ''Click here to create them automatically''.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS3E.PNG|600px]] <br />
</div><br></li><br />
<br />
<li>The disk drive partition should look similar to this setup. For most users, the default partitioning scheme used will suffice. However, you can manually change it using the hard drive partition scheme documentation as a guide. Once complete, choose ''Done''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS3F.PNG|600px]] <br />
</div><br></li><br />
<br />
<li>You will now see '''SUMMARY OF CHANGES''' to the disk drive. Choose ''Accept Changes''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS3G.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
==Software Selection==<br />
<ul><br />
<li>Next on the '''INSTALLATION SUMMARY''', select ''SOFTWARE SELECTION''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27DVD_SS5.PNG|600px]] <br />
</div><br></li><br />
<br />
<li>Ensure ''Fedora Server Edition'' is selected and then choose ''Done''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27DVD_SS4B.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
== Begin Installation ==<br />
<ul><br />
<li>Back to the '''INSTALLATION SUMMARY''' and ready to begin installation. Select ''Begin Installation''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27DVD_SS5.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
== Initial User Creation ==<br />
<ul><br />
<li>Installation has begun and we need to create the initial user. '''DO NOT''' set the root password.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS6A.PNG|600px]] <br />
</div><br></li><br />
<br />
<li>You '''MUST''' create the initial user and password (This will be your HDA Login, also called the First Admin User). Ensure you select ''Make this user administrator'' check box. Once complete, choose ''Done''. Note that a weak password may require you to select ''Done'' twice.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS6B.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
== Installation Progress ==<br />
<ul><br />
<li>Now all of the configuration steps are complete. Sit back and watch the progress.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27DVD_SS7.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
== Installation Complete ==<br />
<ul><br />
<li>Installation is complete. Choose ''Reboot'' and remove the installation media.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS8.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
= Install Amahi 11 =<br />
<br />
Next, we will install Amahi 11 proper on top of Fedora 27.<br />
<ul><br />
<li>When you reboot you will see a black screen with no graphics and a "localhost login" text prompt. Login into that that console directly with the user and password you created in the Fedora 27 installation. (You can also use SSH to login remotely from a client if you know how)<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:A11_DVD_SS1.PNG|600px]] <br />
</div><br><br><br />
<br />
:'''NOTE:''' Passwords do not echo characters on the screen.<br />
<br />
<li>You need to obtain an install code (denoted YOUR-INSTALL-CODE below) from the [https://www.amahi.org/users Amahi control panel] after configuring a profile for the system you are installing, with '''proper network configuration''' for your network.<br><br><br />
<br />
<li>From text console or using SSH (logged in with the user created in the Fedora 27 installation), become ''root'' for the Amahi installation. When prompted for a password, it's your user password you set in the Fedora 27 install.<br /><br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left"><br />
sudo su -<br />
</div><br />
<br />
<li>After that, type these three separate commands (one per line, waiting for each to complete as signified by the command prompt before entering the next command) in the console:<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left"><br />
<nowiki>rpm -Uvh http://f27.amahi.org/noarch/hda-release-11.0.0-1.noarch.rpm</nowiki><br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE<br />
</div><br />
</ul><br />
What this does is installs the Amahi F27 repo, gets the mariadb base packages to avoid dependency conflicts, and installs base Amahi packages (that part should install several packages).<br />
<br />
If there are no errors, install Amahi (replace ''YOUR-INSTALL-CODE'' above with install code you got when creating a profile at [https://www.amahi.org/users your Amahi control panel]).<br />
<br />
If all goes well, it should tell you to reboot. Go ahead and reboot!<br />
<br />
Once it comes back from the reboot, you should have a fully functional home server using the IP address you set up in your network!<br />
<br />
Next you need to transition your network to use it!<br />
<br />
= Transitioning to your Amahi server =<br />
<br />
Once installed, you will want to transition your network to using your Amahi server. Here are some of the things you should know:<br />
<br />
<ul><br />
<li>Your server will boot with the static IP you pre-configured in the Amahi control panel</li><br />
<li>This is a headless server, therefore it will boot to a text console. There is no desktop user interface. '''Installing the Desktop (e.g. GNOME) interface will break DNS/DHCP and make the HDA as an unsuitable network server''' [[Amahi_8_Troubleshooting#Virtualization_Stack_Breaks_DNS.2FDHCP_Server|(details)]]</li><br />
<li>It's strongly recommended you follow the [[transition to Amahi]] HDA guide to get your network fully working properly</li><br />
<li>You can verify if the dashboard is available by accessing it from any client using the IP address of your server '''<nowiki>http://IPADDRESS/</nowiki>''' or '''<nowiki>http://hda/</nowiki>''' (in most Windows clients this works even without DNS from your HDA)</li><br />
<li>The first time you access the dashboard, you will need to log in with user name and password you created above in the [[Fedora_27_Server_DVD_Install#Initial_User_Creation|Initial user creation]] step.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:A11-SS1.PNG|250px]] <br />
</div><br></li><br />
<li>Once you reach your dashboard, recommend you configure your HDA [[Setup|settings]], [[Storage_and_file_sharing|create/manage shares]], [[Adding_a_second_hard_drive_to_your_HDA|add more storage space]], install apps, etc.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:A11-SS2.PNG|400px]] <br />
</div><br></li><br />
<li>Optionally refer to [[Greyhole#Amahi_7.2F8|Greyhole]] to install/configure storage pooling. [[RAID]] guidance is also available for advanced users.</li><br />
</ul><br />
<br />
<br />
Go back to [[Amahi_11_Install|Amahi 11 Install]] page.</div>Bigfoot65https://wiki.amahi.org/index.php?title=Fedora_27_Server_CD_Install&diff=117631Fedora 27 Server CD Install2021-11-17T23:27:56Z<p>Bigfoot65: /* Install Amahi 11 */</p>
<hr />
<div>__TOC__<br />
<br />
= Install Fedora 27=<br />
This is the recommended install method.<br />
<br />
* [https://archives.fedoraproject.org/pub/archive/fedora/linux/releases/27/Server/x86_64/iso/Fedora-Server-netinst-x86_64-27-1.6.iso Fedora-Server-netinst-x86_64-27-1.6.iso] (511MB)<br />
* Checksum:<br />
** <code>MD5 958e27d78109c8c083fb6a0d4485e8e7</code><br />
** <code>SHA1 e9223711ba270c2c90dd644c9b95545af062be1a</code><br />
<br />
* Burn the ISO to CD/DVD (or [[USB Install|USB]]), insert the media into your server, and reboot the system.<br />
<br />
* These instructions below will guide you through the Fedora 27 Netinstall CD installation with screen shots and commentary. If you are not an advanced Linux user and know what you are doing, recommend you '''DO NOT''' deviate from the guidance. Click '''[<Screenshot>]''' to show/hide the image.<br />
<br />
==Boot Screen==<br />
<ul><br />
<li>Select ''Install Fedora 27''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:Fedora27-boot-screen.png|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
==Language Selection==<br />
<ul><br />
<li>Choose desired language and select ''Continue''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS1.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
==Installation Summary==<br />
<ul><br />
<li>The '''INSTALLATION SUMMARY''' screen will appear. It may take a few minutes to finish ''Checking software dependencies''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS2A.PNG|600px]] <br />
</div><br></li><br />
<br />
<li>Change the '''KEYBOARD''' or '''TIME & DATE''' to match your locale if needed.</li><br />
<li> Verify '''NETWORK & HOST NAME''' indicates ''connected''. Don't make any changes unless you are sure of what you are doing.</li> <br />
<br />
<li>Once complete, next choose ''INSTALLATION DESTINATION''. This is where you will select the disk drive to use.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS2B.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
==Disk Drive Setup==<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #FFB6C1; margin: 3px 3px 1em 3px;">'''WARNING:''' Amahi staff doesn't recommend using the default ''LVM'' partition scheme. Doing so will dedicate most of the drive space in the system to the ''/home'' partition. Amahi does not utilize this space, limiting storage for file shares and web applications. For best results and maximum storage, use the ''Standard'' partition scheme.</div><br />
<br />
<ul><br />
<li>Choose the disk drive you want to use for the Fedora installation. If you have more than one disk drive connected, '''DO NOT''' select them at this time. You will notice a ''check mark'' on the disk drive selected. Select ''Custom'' and then choose ''Done''.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS3A.PNG|600px]] <br />
</div><br></li><br />
<br />
<li>Should you have existing partitions on the disk drive you will be using for the Fedora 27 installation, they will have to be removed.</li><br />
<ul><br />
<li> You should see the existing partition about half way down the screen.</li><br />
<li>Choose it to expand and display the existing partitions for deletion. Select the first partition in the list followed by the minus (-) sign.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS3C.PNG|600px]] <br />
</div></li><br />
<li> When prompted ''Are you sure you want to delete all the data on ...?'', choose ''Delete It''.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS3D.PNG|400px]] <br />
</div></li><br />
<li> Repeat the previous two steps until all the existing partitions on the disk drive are gone.</li><br />
</ul><br />
<br />
<li>Ensure the ''New mount points will use the following partitioning scheme:'' is changed to reflect '''Standard partition'''. Then select ''Click here to create them automatically''.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS3E.PNG|600px]] <br />
</div><br></li><br />
<br />
<li>The disk drive partition should look similar to this setup. For most users, the default partitioning scheme used will suffice. However, you can manually change it using the hard drive partition scheme documentation as a guide. Once complete, choose ''Done''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS3F.PNG|600px]] <br />
</div><br></li><br />
<br />
<li>You will now see '''SUMMARY OF CHANGES''' to the disk drive. Choose ''Accept Changes''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS3G.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
==Software Selection==<br />
<ul><br />
<li>Next on the '''INSTALLATION SUMMARY''', select ''SOFTWARE SELECTION''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS4A.PNG|600px]] <br />
</div><br></li><br />
<br />
<li>Select ''Minimal Install'' and then choose ''Done''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS4B.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
==Begin Installation==<br />
<ul><br />
<li>Back to the '''INSTALLATION SUMMARY''' and ready to begin installation. Select ''Begin Installation''<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS5.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
==Initial User Creation==<br />
<ul><br />
<li>Installation has begun and we need to create the initial user. '''DO NOT''' set the root password.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS6A.PNG|600px]] <br />
</div><br></li><br />
<br />
<li>You '''MUST''' create the initial user and password (This will be your HDA Login, also called the First Admin User). Ensure you select ''Make this user administrator'' check box. Once complete, choose ''Done''. Note that a weak password may require you to select ''Done'' twice.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD_SS6B.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
==Installation Progress==<br />
<ul><br />
<li>Now all of the configuration steps are complete. Sit back and watch the progress.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD SS7.PNG|600px]] <br />
</div><br></li><br />
</ul><br />
<br />
==Installation Complete==<br />
<ul><br />
<li>Installation is complete. Choose ''Reboot'' and remove the installation media.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:F27CD SS8.PNG|600px]] <br />
</div><br></li></ul><br />
<br />
= Install Amahi 11 =<br />
<br />
Next, we will install Amahi 11 proper on top of Fedora 27.<br />
<ul><br />
<li>When you reboot you will see a black screen with no graphics and a "localhost login" text prompt. Login into that that console directly with the user and password you created in the Fedora 27 installation. (You can also use SSH to login remotely from a client if you know how)<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:A11_SS1.PNG|450px]] <br />
</div><br><br><br />
<br />
:'''NOTE:''' Passwords do not echo characters on the screen.<br />
<br />
<li>You need to obtain an install code (denoted YOUR-INSTALL-CODE below) from the [https://www.amahi.org/users Amahi control panel] after configuring a profile for the system you are installing, with '''proper network configuration''' for your network.<br><br><br />
<br />
<li>From text console or using SSH (logged in with the user created in the Fedora 27 installation), become ''root'' for the Amahi installation. When prompted for a password, it's your user password you set in the Fedora 27 install.<br /><br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left"><br />
sudo su -<br />
</div><br />
<br />
<li>After that, type these three separate commands (one per line, waiting for each to complete as signified by the command prompt before entering the next command) in the console.<br />
<br />
<div style="border: 1px solid #A3B1BF; padding: .5em 1em; color: #000; background-color: #E6F2FF; margin: 3px 3px 1em 3px; text-align: left"><br />
<nowiki>rpm -Uvh http://f27.amahi.org/noarch/hda-release-11.0.0-1.noarch.rpm</nowiki><br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE<br />
</div><br />
</ul><br />
What this does is installs the Amahi F27 repo, gets the mariadb base packages to avoid dependency conflicts, and installs base Amahi packages (that part should install several packages).<br />
<br />
If there are no errors, install Amahi (replace ''YOUR-INSTALL-CODE'' above with install code you got when creating a profile at [https://www.amahi.org/users your Amahi control panel]).<br />
<br />
If all goes well, it should tell you to reboot. Go ahead and reboot!<br />
<br />
Once reboot is complete, you should have a fully functional home server using the IP address you set up in your network!<br />
<br />
Next you need to transition your network to use it!<br />
<br />
= Transitioning to your Amahi server =<br />
<br />
Once installed, you will want to transition your network to using your Amahi server. Here are some of the things you should know:<br />
<br />
<ul><br />
<li>Your server will boot with the static IP you pre-configured in the Amahi control panel</li><br />
<li>This is a headless server, therefore it will boot to a text console. There is no desktop user interface. '''Installing the Desktop (e.g. GNOME) interface will break DNS/DHCP and make the HDA as an unsuitable network server''' [[Amahi_8_Troubleshooting#Virtualization_Stack_Breaks_DNS.2FDHCP_Server|(details)]]</li><br />
<li>It's strongly recommended you follow the [[transition to Amahi]] HDA guide to get your network fully working properly</li><br />
<li>You can verify if the dashboard is available by accessing it from any client using the IP address of your server '''<nowiki>http://IPADDRESS/</nowiki>''' or '''<nowiki>http://hda/</nowiki>''' (in most Windows clients this works even without DNS from your HDA)</li><br />
<li>The first time you access the dashboard, you will need to log in with user name and password you created above in the [[Fedora_27_Server_CD_Install#Initial_User_Creation|Initial user creation]] step.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:A11-SS1.PNG|250px]] <br />
</div><br></li><br />
<li>Once you reach your dashboard, recommend you configure your HDA [[Setup|settings]], [[Storage_and_file_sharing|create/manage shares]], [[Adding_a_second_hard_drive_to_your_HDA|add more storage space]], install apps, etc.<br />
<div class="mw-collapsible mw-collapsed" data-collapsetext="{{int:Screenshot}}" style="width:400px"><br />
[[file:A11-SS2.PNG|400px]] <br />
</div><br></li><br />
<li>Optionally refer to [[Greyhole#Amahi_7.2F8|Greyhole]] to install/configure storage pooling. [[RAID]] guidance is also available for advanced users.</li><br />
</ul><br />
<br />
<br />
Go back to [[Amahi_11_Install|Amahi 11 Install]] page.</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117626Amahi 122021-11-12T02:04:27Z<p>Bigfoot65: /* To Do */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 35 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 35===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-netinst-x86_64-35-1.2.iso Fedora-Server-netinst-x86_64-35-1.2.iso]<br />
:&nbsp;(646 MB; SHA1 71a67fd53ba8bb25318b14bffbf170654129ccee)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-dvd-x86_64-35-1.2.iso Fedora-Server-dvd-x86_64-35-1.2.iso]<br />
:&nbsp;(2.07 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2441 Amahi Bug # 2441]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* Add to Amahi repo:<br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** <s>''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]</s><br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* <s>Create OpenStack instances:</s><br />
** <s>Amahi Repo</s><br />
** <s>Amahi Test</s><br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 35 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117621Amahi 122021-11-07T17:01:04Z<p>Bigfoot65: /* To Do */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 35 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 35===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-netinst-x86_64-35-1.2.iso Fedora-Server-netinst-x86_64-35-1.2.iso]<br />
:&nbsp;(646 MB; SHA1 71a67fd53ba8bb25318b14bffbf170654129ccee)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-dvd-x86_64-35-1.2.iso Fedora-Server-dvd-x86_64-35-1.2.iso]<br />
:&nbsp;(2.07 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2441 Amahi Bug # 2441]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* Add to Amahi repo:<br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** <s>''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]</s><br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* Create OpenStack instances:<br />
** <s>Amahi Repo</s><br />
** <s>Amahi Test</s><br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 35 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117616Amahi 122021-11-07T16:58:54Z<p>Bigfoot65: /* To Do */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 35 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 35===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-netinst-x86_64-35-1.2.iso Fedora-Server-netinst-x86_64-35-1.2.iso]<br />
:&nbsp;(646 MB; SHA1 71a67fd53ba8bb25318b14bffbf170654129ccee)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-dvd-x86_64-35-1.2.iso Fedora-Server-dvd-x86_64-35-1.2.iso]<br />
:&nbsp;(2.07 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2441 Amahi Bug # 2441]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* Add to Amahi repo:<br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** <s>''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** ''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]<br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* Create OpenStack instances:<br />
** <s>Amahi Repo</s><br />
** <s>Amahi Test</s><br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 35 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Main_Page&diff=117611Main Page2021-11-07T02:26:42Z<p>Bigfoot65: /* Roadmap & Development */</p>
<hr />
<div><br /><br />
This is the knowledge base wiki for Amahi the home server. Please add or edit any information in this Wiki that you feel is lacking, missing, or needs improvement.<br />
<br />
__TOC__<br />
<br />
* [[Intro|Introduction]] to the Amahi HDA, or Home Digital Assistant, "like a PDA, but for the home"<br />
* [http://docs.amahi.org/requirements.html Minimum Hardware Requirements]<br />
* [https://www.amahi.org/faq Frequently Asked Questions (FAQ)]<br />
* [[HDA Admin How To]]<br />
* [[HDA OS Migration Guide]]<br />
* [https://www.amahi.org/videos Amahi Video Tutorials]<br />
* [[Feedback|Community Feedback]]<br />
<br />
----<br />
'''NOTES:'''<br />
# Current stable release: [http://docs.amahi.org/amahi-11.html Amahi 11], Fedora 27'''.<br />
# Amahi one-click applications are typically updated for the latest stable release '''ONLY'''.<br />
# This wiki is built to provide support for the stable release primarily.<br />
# Registration in this wiki is subject to manual approval due to spam considerations.<br />
# '''Maintenance Support ONLY''' indicates all Amahi updates (i.e. platform, applications, etc) have been halted.<br />
----<br />
<br />
== Installation ==<br />
* [http://docs.amahi.org/amahi-11.html Fedora 27 / Amahi 11] (officially supported release)<br />
* Maintenance Support '''ONLY''':<br />
** Fedora 25 ([[Amahi 10 Install|New Install]] / [[Amahi 10 Upgrade|Amahi 9 to 10 Upgrade]])<br />
** Fedora 23 ([[Amahi 9 Install|New Install]] / [[Amahi 9 Upgrade|Amahi 8 to 9 Upgrade]])<br />
** Fedora 21 ([[Amahi 8 Install|New Install]] / [[Amahi 8 Upgrade|Amahi 7 to 8 Upgrade]] / [[Amahi 8 install via unsupported methods|Unsupported Install Methods]])<br />
** Fedora 19 ([[Express Disc]] / [https://wiki.amahi.org/index.php/Amahi_7_full_DVD Full DVD] / [[Fedora_19_USB_install|USB Install]])<br />
** [http://docs.amahi.org/ubuntu-12.html Ubuntu 12.04.x LTS]<br />
** [http://docs.amahi.org/fedora-14.html Fedora 14]<br />
*[[Amahi_Virtualized|Amahi Virtualized]] ('''NOT''' fully supported)<br />
<br />
== Troubleshooting ==<br />
Refer to the [[troubleshooting]] page for assistance.<br />
<br />
== Post-Installation ==<br />
<br />
*[[TerminalScripts|Terminal Scripts]]: Useful command line scripts.<br />
* [[Linux-hda_commands|Linux/HDA Commands]]: Commonly used commands for Linux and Amahi.<br />
*[[Storage and file sharing]]: Setup & manage users and shares and access between them.<br />
*Access Shares using [[Map_Shares_in_Windows|Windows (XP/Vista/7/8)]], [[SharingToMacOSX|Mac OS X]], and [[SharingToLinux|Linux]] systems.<br />
*[[Post-Install_Hardware_Changes | Post Install Hardware Changes]]: Steps for changing hardware on your Amahi server (i.e. mother board, network card, etc).<br />
* Adding additional hard drives to your HDA: Use the Amahi [https://www.amahi.org/apps/disk-wizard Disk Wizard] application for Amahi 8 or greater. The [[Adding a second hard drive to your HDA|manual guidance]] remains available for all other Amahi versions.<br />
<br />
=== Remote Access ===<br />
Accessing your HDA from anywhere on the network<br />
* [[VPN|Virtual Private Networking (VPN)]]: Access from '''outside''' your network.<br />
* [[Key-Based SSH Logins|Secure Shell (SSH)]]: Key-based access to your HDA.<br />
* [http://en.wikipedia.org/wiki/Virtual_Network_Computing Virtual Network Computing (VNC)]: Access from '''inside''' your network (e.g. if your HDA is "headless").<br />
** [[Install_VNC_server_on_Ubuntu_Server_12.04|Ubuntu]]<br />
** [[VNC|Fedora]]<br />
<br />
=== Greyhole ===<br />
Redundant Storage Pooling for your files<br />
<br />
*[[Greyhole|Greyhole]]: Overview of Greyhole.<br />
*[https://github.com/gboudreau/Greyhole/wiki Greyhole Wiki]: External Greyhole Wiki site.<br />
*[[Storage_pooling|Storage Pooling]]: Overview of what it is all about.<br />
*[https://www.amahi.org/apps/greyhole-log Greyhole Log]: Amahi application for your HDA that monitors Greyhole activity.<br />
*[[Mount_Shares_Locally|Mounting Shares Locally]]: How to mount shares locally on the HDA for managing data safely.<br />
*[[Greyhole_landing_zone|Greyhole landing zone (LZ)]]: Explained and how to work with it.<br />
*[[Greyhole_updating|Updating Greyhole]]: How to upgrade to the latest version of Greyhole.<br />
*[[Greyhole_moving_data_out_of_the_pool|Moving Data Out of Greyhole]]: Removing drives and data out of the storage pool.<br />
* [[Reconnect_existing_Greyhole_storage_pool|Reconnect Greyhole Storage Pool]]: How to add existing Greyhole data drives to a new installation.<br />
* [[Greyhole_UI_App_Transition_Guide|Greyhole UI Application Transition Guide]]: Move from manual Greyhole install to the [https://www.amahi.org/apps/greyhole-ui Greyhole UI] application for Amahi 7 or greater.<br />
<br />
=== Networking ===<br />
Using your HDA to manage your home network<br />
* [http://en.wikipedia.org/wiki/Local_area_network Local Area Network (LAN)]: Internal networking<br />
** [[Networking - Static IPs|Set Static IP Address]]: How to assign static IPs to your network devices.<br />
** [[Turning_off_DHCP|Turning off DHCP Server]]: Shows how to turn off DHCP Server on your HDA.<br />
** [[Change IP Address|Change IP Address]]: Change IP address of your Amahi server, Network Gateway, and DHCP Server Range.<br />
** [[How to use two HDAs on the same network| Single Network Dual HDA Setup]]: Configure and use two HDAs on the same network.<br />
** [[Adding an HDA networked printer]]: Guide to set up a print server on your HDA.<br />
<br />
* [http://en.wikipedia.org/wiki/Wide_area_network Wide Area Network (WAN)]: External networking<br />
** [[Hosting a website | Hosting a web site]]: Display your own web site on the internet from your Amahi home server<br />
** [[Changing your DNS provider|Changing DNS provider]]: Change from [http://www.opendns.com/ OpenDNS] to your [http://en.wikipedia.org/wiki/Internet_service_provider Internet Service Provicer (ISP)] or other third party provider.<br />
** [[Configuring OpenDNS]]: Configure [http://www.opendns.com/ OpenDNS] to filter or block web sites.<br />
** [[Punching DNS Holes]]: How to assign IP addresses outside of your network for your home domain.<br />
<br />
== Additional Functionality == <br />
* [https://www.amahi.org/apps/ Apps Gallery]: The repo of Amahi one-click applications ('''NOTE:''' [https://www.amahi.org/faq#do-you-change-for-apps Convenience fees] may apply; log into Amahi website to purchase). <br />
* [http://www.amahi.org/plans PRO and NINJA plans]: Provided users with additional Amahi benefits for a small monthly fee.<br />
* [[Monit|Monit Web Interface]]: Amahi application to monitor and control status of your HDA services.<br />
* [[Webapps | Creating web apps]]: how to make your own web apps, with your code or other's code<br />
* [[Calendars]]: How to use the calendar server in the HDA, including Outlook and iCal sync.<br />
* [[Backups]]: How to backup/restore [[XPBackups|Windows XP]], [[VistaWindows7Backups|Windows Vista/7/8]], [[Sbackup|Ubuntu Linux]], and [[Backups#Mac_OS_X|Mac OS X]].<br />
* [[Database_Backup|Automatic Database Backup]]: Automated daily backup of HDA databases.<br />
* [http://en.wikipedia.org/wiki/RAID RAID]: Configuration guides for [[RAID 1]] and [[RAID 5]].<br />
* [[Require_Login|Password protect Applications]]: Provides password protect for your Amahi installed applications.<br />
<br />
== Community Tutorials ==<br />
Contributed by the Amahi user community<br />
<br />
* [[Ubuntu Tutorials|Ubuntu]]<br />
* [[Fedora Tutorials|Fedora]]<br />
* [http://wiki.amahi.org/index.php/Category:Apps Applications]<br />
<br />
== Roadmap & Development ==<br />
The [https://www.amahi.org/team core team] '''ONLY''' supports Ubuntu and Fedora development at this time. All others are being supported by the user community. <br /><br />
<br />
<u>'''ACTIVE:'''</u> Released or Development In Progress<br />
* [http://docs.amahi.org/amahi-11.html Fedora 27] (Current official release)<br />
* [[Amahi 12|Fedora 35]] (development)<br />
<br />
* Maintenance support <b>ONLY</b><br />
** [[Amahi 10|Fedora 25]]<br />
** [[Amahi 9|Fedora 23]]<br />
** [[Amahi 8|Fedora 21]]<br />
** [[Fedora_19|Fedora 19]]<br />
** [[Ubuntu|Ubuntu 12.04.x LTS]]<br />
** [[Fedora 14|Fedora 14]]<br />
<br /><br />
<u>'''INACTIVE:'''</u> Unsupported or Development Stopped<br />
* Fedora 15-18, 20, 22, 24, 26, 28-34<br />
* Ubuntu 12.10 or newer<br />
* CentOS [[CentOS|5]], [[Centos_6|6]], [[Centos_7|7]], or newer<br />
* [[Scientific_Linux|Scientific Linux 6.1]] or newer<br />
<br />
== Contribute ==<br />
How you can help<br />
<br />
* [[Translate Amahi]] to your language<br />
* [[How to Create a new Theme]]<br />
* Submit a [http://bugs.amahi.org Bug/Feature/Support] report<br />
* [[Contribute|Package]] or [[Tester program|Test apps]]<br />
* [http://www.flickr.com/photos/amahi/sets/72157606815797764/ Amahi Wallpapers]<br />
* [http://www.flickr.com/photos/amahi/sets/72157606828513620/ Amahi Banners]<br />
<br />
== Related Links ==<br />
* [[Developers]]: How to write HDA apps, questions, API suggestions, etc.<br />
* [[Credits]]: How are we doing all this? We have many OSS projects to thank!</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117606Amahi 122021-11-07T02:25:32Z<p>Bigfoot65: /* To Do */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 35 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 35===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-netinst-x86_64-35-1.2.iso Fedora-Server-netinst-x86_64-35-1.2.iso]<br />
:&nbsp;(646 MB; SHA1 71a67fd53ba8bb25318b14bffbf170654129ccee)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-dvd-x86_64-35-1.2.iso Fedora-Server-dvd-x86_64-35-1.2.iso]<br />
:&nbsp;(2.07 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2441 Amahi Bug # 2441]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* Add to Amahi repo:<br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** ''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''<br />
** ''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''<br />
** ''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]<br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* Create OpenStack instances:<br />
** <s>Amahi Repo</s><br />
** <s>Amahi Test</s><br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 35 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117601Amahi 122021-11-07T02:21:54Z<p>Bigfoot65: /* Development Bugs */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 35 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 35===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-netinst-x86_64-35-1.2.iso Fedora-Server-netinst-x86_64-35-1.2.iso]<br />
:&nbsp;(646 MB; SHA1 71a67fd53ba8bb25318b14bffbf170654129ccee)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-dvd-x86_64-35-1.2.iso Fedora-Server-dvd-x86_64-35-1.2.iso]<br />
:&nbsp;(2.07 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2441 Amahi Bug # 2441]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* Add to Amahi repo:<br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** ''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''<br />
** ''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''<br />
** ''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]<br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* Create OpenStack instances:<br />
** <s>Amahi Repo</s><br />
** Amahi 12 Test<br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 35 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117596Amahi 122021-11-07T02:21:27Z<p>Bigfoot65: /* Objective */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 35 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 35===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-netinst-x86_64-35-1.2.iso Fedora-Server-netinst-x86_64-35-1.2.iso]<br />
:&nbsp;(646 MB; SHA1 71a67fd53ba8bb25318b14bffbf170654129ccee)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-dvd-x86_64-35-1.2.iso Fedora-Server-dvd-x86_64-35-1.2.iso]<br />
:&nbsp;(2.07 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2441 Amahi Bug # 2441]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* Add to Amahi repo:<br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** ''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''<br />
** ''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''<br />
** ''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]<br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* Create OpenStack instances:<br />
** <s>Amahi Repo</s><br />
** Amahi 12 Test<br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 34 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117591Amahi 122021-11-07T02:19:28Z<p>Bigfoot65: /* To Do */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 34 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 35===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-netinst-x86_64-35-1.2.iso Fedora-Server-netinst-x86_64-35-1.2.iso]<br />
:&nbsp;(646 MB; SHA1 71a67fd53ba8bb25318b14bffbf170654129ccee)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-dvd-x86_64-35-1.2.iso Fedora-Server-dvd-x86_64-35-1.2.iso]<br />
:&nbsp;(2.07 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2441 Amahi Bug # 2441]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* Add to Amahi repo:<br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** ''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''<br />
** ''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''<br />
** ''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]<br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* Create OpenStack instances:<br />
** <s>Amahi Repo</s><br />
** Amahi 12 Test<br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 34 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117586Amahi 122021-11-07T02:18:49Z<p>Bigfoot65: /* To Do */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 34 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 35===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-netinst-x86_64-35-1.2.iso Fedora-Server-netinst-x86_64-35-1.2.iso]<br />
:&nbsp;(646 MB; SHA1 71a67fd53ba8bb25318b14bffbf170654129ccee)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-dvd-x86_64-35-1.2.iso Fedora-Server-dvd-x86_64-35-1.2.iso]<br />
:&nbsp;(2.07 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2441 Amahi Bug # 2441]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F34 to F35)</s><br />
* Test Apps<br />
* Build Amahi-specific RPMs:<br />
** ''amahi-anywhere''<br />
** ''amahi-sync''<br />
** ''amahi-plex''<br />
** ''amahi-greyhole''<br />
* <s>Add to Amahi repo:</s><br />
** <s>''netatalk (native to Fedora 35)''</s><br />
** ''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''<br />
** ''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''<br />
** ''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]<br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 35)?<br />
* Custom Fedora 35 CD (Amahi 12 Express)?<br />
* Create OpenStack instances:<br />
** <s>Amahi Repo</s><br />
** Amahi 12 Test<br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 34 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65https://wiki.amahi.org/index.php?title=Amahi_12&diff=117581Amahi 122021-11-07T02:14:26Z<p>Bigfoot65: /* Amahi 12 */</p>
<hr />
<div>{{MessageBox|<br />
backgroundcolor = #ffaaaa|<br />
image =Warning.png|<br />
heading =WARNING|<br />
message = This is beta software. We intend to make it automatically upgrade to the official Amahi 12 release. If you install, please report your results in the forums at https://forums.amahi.org<br />
<br />
See [http://docs.amahi.org Amahi Docs] for the officially supported version, Amahi 11 on Fedora 27.}}<br />
<br />
=Objective=<br />
Develop and test installation of Amahi 12, based on Fedora 34 for the next Amahi release.<br />
<br />
=New Install=<br />
==Download==<br />
===Fedora 35===<br />
* Minimal CD (Netinstall) - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-netinst-x86_64-35-1.2.iso Fedora-Server-netinst-x86_64-35-1.2.iso]<br />
:&nbsp;(646 MB; SHA1 71a67fd53ba8bb25318b14bffbf170654129ccee)<br />
* Full DVD - [https://download.fedoraproject.org/pub/fedora/linux/releases/35/Server/x86_64/iso/Fedora-Server-dvd-x86_64-35-1.2.iso Fedora-Server-dvd-x86_64-35-1.2.iso]<br />
:&nbsp;(2.07 GB; SHA1 e672291c28055313dfdcf535f5e39e5bff576062)<br />
<br />
===Amahi 12===<br />
As <code>root</code> user, execute the following:<br />
<br />
<pre>rpm -Uvh http://f35.amahi.org/noarch/hda-release-12.0.0-1.noarch.rpm<br />
dnf -y install hda-ctl<br />
hda-install -i YOUR-INSTALL-CODE</pre><br />
<br />
=Upgrade=<br />
Refer to [https://bugs.amahi.org/issues/2441 Amahi Bug # 2441]<br />
<br />
=To Do=<br />
* <s>Create Amahi repo</s><br />
* <s>Create apps (rename F33 to F34)</s><br />
* Test Apps<br />
* <s>Build Amahi-specific RPMs:</s><br />
** <s>''amahi-anywhere''</s><br />
** <s>''amahi-sync''</s><br />
** <s>''amahi-plex''</s><br />
** <s>''amahi-greyhole''</s><br />
* <s>Add to Amahi repo:</s><br />
** <s>''netatalk (native to Fedora 34)''</s><br />
** <s>''RPM Fusion Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])'' </s><br />
** <s>''RPM Fusion Non-Free ([https://bugs.amahi.org/issues/2461 Amahi Bug #2461])''</s><br />
** <s>''HandBrake-cli'' [needed for [https://www.amahi.org/apps/videos5 Videos5]; ''HandBrake'' native to [https://www.amahi.org/apps/rpm-fusion-free-repo RPM Fusion (Free) Repo]]</s><br />
* <s>Test Minimal CD (Netinstall) method</s><br />
* Test Full DVD method<br />
* Build apps testbot<br />
* Test upgrade (27 to 34)?<br />
* Custom Fedora 34 CD (Amahi 12 Express)?<br />
* Create OpenStack instances:<br />
** <s>Amahi Repo</s><br />
** Amahi 12 Test<br />
<br />
=Recommended Changes=<br />
==New Features==<br />
* App Install Failure Link ([https://bugs.amahi.org/issues/1918 Bug #1918])<br />
* Option to add to Samba Global settings ([https://bugs.amahi.org/issues/1341 Bug #1341])<br />
* Log view in Dashboard App/Server Tab ([https://bugs.amahi.org/issues/2108 Bug #2108])<br />
* Capability to rename server (Samba) to something other than \\HDA ([https://bugs.amahi.org/issues/1898 Bug #1898])<br />
* Add access control for all users in the system ([https://bugs.amahi.org/issues/2099 Bug #2099])<br />
* Simple setup for remote access of Web Apps ([https://bugs.amahi.org/issues/1859 Bug #1859])<br />
* IPv6 support ([https://bugs.amahi.org/issues/1122 Bug #1122])<br />
* Multiple install of web apps ([https://bugs.amahi.org/issues/1939 Bug #1939])<br />
* Using wildcard DNS aliases ([https://bugs.amahi.org/issues/1721 Bug #1721])<br />
* Inform user of app upgrade via dashboard ([https://bugs.amahi.org/issues/1512 Bug #1512])<br />
* Add 7 Zip Archiver ([https://bugs.amahi.org/issues/1934 Bug #1934])<br />
* Wake-on-LAN capability ([https://bugs.amahi.org/issues/2253 Bug #2253])<br />
* Run PHP 5 apps in a container ([https://bugs.amahi.org/issues/2250 Bug #2250])<br />
<br />
==Bug Fixes==<br />
* <s>Clean up hda-install ([https://bugs.amahi.org/issues/2122 Bug #2122])</s><br />
* Webapps and dns aliases get stuck after a bad app install ([https://bugs.amahi.org/issues/1586 Bug #1586])<br />
* Samba Config Errors ([https://bugs.amahi.org/issues/2408 Bug #2408])<br />
* DNS bug block website plex.tv if Fixed IP host name is "TV" Reproducable with other domains ([https://bugs.amahi.org/issues/1896 Bug #1896])<br />
* Deleting user does not delete their home directory ([https://bugs.amahi.org/issues/1844 Bug #1844])<br />
* HDA File Search ([https://bugs.amahi.org/issues/1786 Bug #1786])<br />
* Access control not working if proxypass is used ([https://bugs.amahi.org/issues/2015 Bug #2015])<br />
* Dashboard Gateway Doesn't Change HDA Network Settings ([https://bugs.amahi.org/issues/2285 Bug #2285])<br />
* <s>Remove Dashboard News Feed ([https://bugs.amahi.org/issues/2459 Bug #2459])</s><br />
<br />
=Development Bugs=<br />
* Amahi 12 Testing ([https://bugs.amahi.org/issues/2424 Amahi Bug #2424])<br />
* <s>SSH public key auth broken with Fedora 34 ([https://bugs.amahi.org/issues/2440 Amahi Bug #2440])</s><br />
* Amahi 12 with fedora 34 and platform 11.9 ([https://bugs.amahi.org/issues/2458 Amahi Bug #2458])</div>Bigfoot65