Leo's Notes - User contributions [en]

CloudStack

2022-10-26T17:26:24Z

136.159.16.240: systemctl enable --now enables a service and starts it simultaneously, reducing the need to run multiple commands

Apache CloudStack is open-source cloud computing software. It is used to deploy a infrastructure as a service (IaaS) platform on virtualization technologies such as KVM, VMware, and Xen. This is similar to OpenStack but is significantly simpler to setup and manage (albeit with less features).

This page contains my notes on setting up and using CloudStack 4.15. I am by no means a CloudStack expert so take my notes here with a huge grain of salt and feel free to make corrections.

==Installation==
This installation is based on CloudStack 4.15 using CentOS 8. The setup described below uses KVM and Open vSwitch. I'm basing the design decisions and approach from the installation guide at [http://docs.cloudstack.apache.org/en/latest/quickinstallationguide/qig.html#management-server-installation http://docs.cloudstack.apache.org/en/latest/quickinstallationguide/qig.html]

===Overview===
I will have 1 management node and a few bare metal nodes. All nodes will have the same processor (Intel something) and memory (24GB).

Each node will have the same network configuration based on OpenVSwitch. There will be only 1 ethernet connection per node with various VLANs trunked to each node. The VLANs are:
{| class="wikitable"
!Network
!Vlan
!Network subnet
|-
|Management
|11, untagged
|172.19.0.0/20
|-
|Storage
|3205
|172.22.0.0/24
|-
|Guest
|100 - 200
|n/a
|-
|Public
|2
|136.159.1.0/24
|}
The network configs for the 4 nodes I'll be using are listed below. There is also a NFS server used for primary storage. The reason for the weird IPs is because this was set up on an existing network.
{| class="wikitable"
!Node
!Networks
|-
|management
|Management: 172.19.12.141/20
Storage: 172.22.0.241/24
|-
|baremetal1
|Management: 172.19.12.142/20
Storage: 172.22.0.242/24
|-
|baremetal2
|Management: 172.19.12.143/20
Storage: 172.22.0.243/24
|-
|baremetal3
|Management: 172.19.12.144/20
Storage: 172.22.0.244/24
|-
|netapp1
|Storage: 172.22.0.19/24
|}

===Switch config===
For completeness, here's the configuration of the HP Procurve switch that the nodes are connected to. The switch should have all the guest VLANs defined and tagged.
{{Highlight
| code = config

# Guest VLANs
vlan 100 name guest100
vlan 101 name guest101
...
vlan 200 name guest 200
interface 1-8 tagged vlan 100-200

# Public, management, storage VLANs
vlan 2 name public
vlan 11 name management
vlan 3205 name storage
interface 1-8 untagged vlan 11
interface 1-8 tagged vlan 2,3205
| lang = terminal
}}

===Node setup===
Each node will be set up with the following sub-steps.

====CloudStack Repos====
Install CloudStack repos.{{Highlight
| code = # cat > /etc/yum.repos.d/cloudstack.repo <<EOF
[cloudstack]
name=cloudstack
baseurl=http://download.cloudstack.org/centos/8/4.15/
enabled=1
gpgcheck=0
EOF
| lang = terminal
}}

====Install base packages====
Install all other dependencies.{{Highlight
| code = # yum -y install epel-release
# yum -y install bridge-utils net-tools
| lang = terminal
}}Install OpenVSwitch from CentOS Extras:
{{Highlight
| code = # yum -y install \
http://mirror.centos.org/centos/8/extras/x86_64/os/Packages/centos-release-nfv-openvswitch-1-3.el8.noarch.rpm \
http://mirror.centos.org/centos/8/extras/x86_64/os/Packages/centos-release-nfv-common-1-3.el8.noarch.rpm
| lang = terminal
}}

====Disable SELinux====
The system should have SELinux disabled. Use <code>setenforce</code> and edit the selinux config:{{Highlight
| code = # setenforce 0
# vi /etc/selinux/config
## disable selinux
| lang = terminal
}}

====Disable firewalld====
{{Highlight
| code = # systemctl stop firewalld
# systemctl disable firewalld
| lang = terminal
}}

====Configure Open vSwitch====
{{Highlight
| code = # echo "blacklist bridge" >> /etc/modprobe.d/local-blacklist.conf
# echo "install bridge /bin/false" >> /etc/modprobe.d/local-dontload.conf

# systemctl enable --now openvswitch
| lang = terminal
}}
We will be using network-scripts to configure the Open vSwitch bridges later. I removed NetworkManager but retained network-scripts to ensure NetworkManager doesn't interfere with my network setup. The install guide leaves NetworkManager around.

I create a 'shared' bridge that's tied to the network interface called <code>nic0</code>. This was done to make it easier to change the bridge setup during my testing but this could be simplified. Each of the physical networks I later set up in CloudStack are its own individual bridge to make it obvious how VMs get connected to the network.
{{Highlight
| code = # ovs-vsctl add-br nic0
# ovs-vsctl add-port nic0 enp4s0f0 tag=11 vlan_mode=native-untagged
# ovs-vsctl set port nic0 trunks=2,11,40-49,3205

# ovs-vsctl add-br management0 nic0 11
# ovs-vsctl add-br cloudbr0 nic0 2
# ovs-vsctl add-br cloudbr1 nic0 100
# ovs-vsctl add-br storage0 nic0 3205
| lang = terminal
}}The node's management IP address needs to be removed from the primary network interface and then assigned on the management0 interface. If you're doing this to a node remotely, this might interrupt your connection.
{{Highlight
| code = # ip addr del 172.19.12.141/20 dev enp4s0f0
# ip addr add 172.19.12.141/20 dev management0
# ip route add default via 172.19.0.3
# ip addr add 172.22.0.241/24 dev storage0

# ip link set management0 up
# ip link set storage0 up
| lang = terminal
}}

====Network configuration====
Once the Open vSwitch bridges are set up, configure the interfaces as follows:
{| class="wikitable"
!Network Interface
!Role
!Configuration
|-
|enp4s0f0
|primary NIC in the host
|up on boot; no IP
|-
|nic0
|network OVS switch that connects to the other bridges to the NIC
|up on boot; no IP
|-
|cloudbr0
|public traffic.
|up on boot; no IP
|-
|cloudbr1
|guest traffic
|up on boot; no IP
|-
|management0
|management traffic
|up on boot; assigned with management IP
|-
|storage0
|storage traffic
|up on boot; assigned with storage network IP
|-
|cloud0
|link local traffic
|up on boot; assigned 169.254.0.1/16
|}Network configs are applied using network-scripts. The idea here is to have the network interfaces be configured when the system boots automatically. For interfaces that require a static IP address, I used the following network-scripts file. Adjust the device name and IP address as required.
{{Highlight
| code = # cat <<EOF > /etc/sysconfig/network-scripts/ifcfg-cloudbr0
DEVICE=cloudbr0
TYPE=Bridge
ONBOOT=yes
BOOTPROTO=static
IPV6INIT=no
IPV6_AUTOCONF=no
DELAY=5
IPADDR=172.16.10.2
GATEWAY=172.16.10.1
NETMASK=255.255.255.0
DNS1=8.8.8.8
DNS2=8.8.4.4
USERCTL=no
NM_CONTROLLED=no
EOF
| lang = terminal
}}For devices that don't require a static IP:
{{Highlight
| code = cat <<EOF > ifcfg-cloudbr0
DEVICE=cloudbr0
TYPE=OVSBridge
DEVICETYPE=ovs
ONBOOT=yes
BOOTPROTO=none
HOTPLUG=no
NM_CONTROLLED=no
EOF
| lang = text
}}Once configured, verify that your node comes up with the proper network settings on a reboot.

===Management node setup===
On the management node, set up the network configs and the CloudStack management packages.

====Setup Storage====
If you intend to use the management server as the primary and secondary storage, you will need to set up a NFS server. If you intend to use an external NFS server as the primary storage, you can skip this step.{{Highlight
| code = # mkdir -p /export/primary /export/secondary
# yum -y install nfs-utils
# cat > /etc/exports <<EOF
/export/secondary *(rw,async,no_root_squash,no_subtree_check)
/export/primary *(rw,async,no_root_squash,no_subtree_check)
EOF
# systemctl enable --now nfs-server
| lang = terminal
}}

====CloudStack management services====
Install MySQL. MariaDB isn't supported and the installation fails with it.
{{Highlight
| code = # rpm -ivh http://repo.mysql.com/mysql80-community-release-el8.rpm
# yum -y install mysql-server
# yum -y install mysql-connector-python

## edit /etc/my.cnf to have the following lines.
cat >> /etc/my.cnf <<EOF
[mysqld]
innodb_rollback_on_timeout=1
innodb_lock_wait_timeout=600
max_connections=350
log-bin=mysql-bin
binlog-format = 'ROW'
EOF

# systemctl enable --now mysqld
| lang = terminal
}}
Setup CloudStack.{{Highlight
| code = # yum -y install cloudstack-management

# cloudstack-setup-databases cloud:password@localhost --deploy-as=root
# cloudstack-setup-management
# systemctl enable --now cloudstack-management
| lang = terminal
}}After starting <code>cloudstack-management</code> for the firs time, it might take from 2-10 minutes for the database to set up completely. During this time, the web interface won't be responsive. In the mean time, you will need to seed the system VM images to the secondary storage. If you are using an external NFS server for your secondary storage, adjust the mount point in the following command accordingly.
{{Highlight
| code = ## Seed the systemvm into secondary storage
# /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt -m /export/secondary -u https://download.cloudstack.org/systemvm/4.15/systemvmtemplate-4.15.1-kvm.qcow2.bz2 -h kvm -F
| lang = terminal
}}
We will continue the setup process via the web interface after setting up a bare metal node.

===Bare metal node setup===
You should set up at least one bare metal node which will be used to set up your first zone and pod.

On a bare metal node, set up everything outlined in the [[CloudStack#Node setup|Node setup]] section above. The node should have the CloudStack repos, Open vSwitch, SElinux/firewalld, and the networking configured. The agent node must have virtualization enabled on the CPU and KVM should be installed. You should be able to find <code>/dev/kvm</code> on the system.

====CloudStack Agent====
To set up the node, install the <code>cloudstack-agent</code> package.

{{Highlight
| code = # yum -y install cloudstack-agent
| lang = terminal
}}

Configure <code>qemu</code> and <code>libvirtd</code>.{{Highlight
| code = ## edit /etc/libvirt/qemu.conf
vnc_listen=0.0.0.0

## edit /etc/libvirt/libvirtd.conf
listen_tls = 0
listen_tcp = 1
tcp_port = "16509"
auth_tcp = "none"
mdns_adv = 0
| lang = terminal
}}The CloudStack install guide instructs you to edit the libvirtd arguments to <code>--listen</code>, but this will prevent libvirtd from starting using systemd. Instead, you should skip this step entirely because the CloudStack agent will configure this for you when you add the node to a zone.
{{Highlight
| code = ## The install guide suggests editing /etc/sysconfig/libvirtd to use the listen flag.
## However, this only works if you're not using systemd or using the libvirtd-tcp socket.
## I skipped this step since the agent will configure this later on.
LIBVIRTD_ARGS="--listen"
| lang = terminal
}}Start the CloudStack agent. The CloudStack agent should also automatically bring up libvirtd (it's a service dependency).

====Allow sudo access====
Ensure that <code>/etc/sudoers</code> does not require TTY. In the older documentation, CloudStack requires that the 'cloud' user be able to sudo with the addition of <code>Defaults:cloud !requiretty</code>. However, looking at the installation on the CentOS 8 box, the agent actually runs as root, so perhaps root needs to be able to sudo?

===Setting up your first zone===
At this point in the process, you should have at least one bare metal host and your management node should be up and running and it should be serving the CloudStack web UI at http://cloudstack:8080/client. Login using the default <code>admin</code> / <code>password</code> credentials.

You will be greeted with a setup wizard. I have had no luck with this and it's better to ignore it. Instead, navigate to Infrastructure -> zones and manually set up your first zone.
{| class="wikitable"
!Description
!Screenshot
|-
|There are 3 types of zones that you can create:

#'''Basic zone''' - All guest VMs are placed on a single shared flat network. There is no isolation or security policies in place to prevent guest VMs from seeing each other.
#'''Advanced zone''' - Guest VMs can be placed in one or more VLAN based networks. Guest networks can either be isolated or L2. Isolated networks (depending on the chosen network offering) comes with a virtual router (VR) which offers NAT/SNAT and firewall services and uses one or more public IP addresses. L2 networks are similar but doesn't have a virtual router but instead requires these services to be offered externally. Tenants can also create something called a virtual private cloud (VPC). A VPC is like a regular isolated guest network but with additional features. A VPC allows the user to:
##Create multiple subnets (called tiers) which can route with each other
##Network traffic between tiers can be controlled through Network ACLs
##One or more public IPs can be associated to a VPC.
##Like an isolated guest network, all subnets can be NATed out through a single public IP
##You can create a private gateway (and therefore static routes) within a VPC
##You can create a VPN connection to a VPC
#'''Advanced zone with security groups''' - Guest VMs are placed on a shared network that is publicly routable. There is no concept of a 'public' network because the guest network should also be public. As a result, there is no ability to create any other kind of guest networks or VPCs. The only benefit here is the ability to define security groups per-VM (which is implemented via IPTables on the bare metal host). Because enabling security groups in a zone will restrict that zone from being able to create isolated guest networks or VPCs, the security group feature only appears useful in an environment where guests only need to connect to the internet.

Be aware of each type's limitations before continuing.

We will be creating an advanced network zone.
|[[File:CloudStack - New Zone 1.png|left|thumb]]
|-
|We will add the DNS resolvers for the zone and specify the hypervisor type (KVM).
Empty the guest CIDR since we're going to allow users to specify their own.
|[[File:CloudStack - New Zone 2.png|left|thumb]]
|-
|When using the advanced zone, you need to specify the physical networks for the management, storage, and public networks.
These should correspond to the physical network devices on the hypervisor. Recall that in the previous step where we set up the Open vSwitch bridges, we created the following bridges for each role:

*management - management0
*storage - storage0
*public - cloudbr0
*guest - cloudbr1
|<gallery>
File:CloudStack - New Zone 3.png
File:CloudStack - New Zone 3a.png
</gallery>
|-
|Specify the public network. The addresses defined here populates the 'Public IP' pool.

All isolated guest networks and all VPCs will use one of the addresses defined in this pool for the SNAT/NAT. The addresses specified here should therefore be accessible from the internet.
|[[File:CloudStack - New Zone 4.png|left|thumb]]
|-
|Create a new pod.

The pod network here should cover your management network subnet. The reserved IP addresses here will be used by system VMs that require access to the management network.
|[[File:CloudStack - New Zone 5.png|left|thumb]]
|-
|Specify the guest network VLAN range.

Because we're using VLAN as an isolation method, this range specifies what VLANs the guest networks will use over the guest physical network.
|[[File:CloudStack - New Zone 6.png|left|thumb]]
|-
|Specify the storage network.

The reserved start/end IPs will be used by system VMs that require access to the primary storage.

If you are assigning static IPs on your bare metal hosts, ensure that the reserved addresses don't overlap with the IP range specified here (because I had CloudStack assign a VM with the same IP as a bare metal host)
|[[File:CloudStack - New Zone 7.png|left|thumb]]
|-
|Specify a cluster name.
|[[File:CloudStack - New Zone 8.png|left|thumb]]
|-
|Add your first bare metal host.
You must add one host now and can add additional ones later.
|[[File:CloudStack - New Zone 9.png|left|thumb]]
|-
|Specify your primary storage.
The server should be accessible from the storage network.
|[[File:CloudStack - New Zone 10.png|left|thumb]]
|-
|Specify your secondary storage.

You need to have at least one NFS secondary storage that has been seeded with the system VM template.

Secondary storage pools should be accessible from the management network ('''confirm'''?)
|[[File:CloudStack - New Zone 11.png|left|thumb]]
|-
|Launch the zone.
This step might take a few minutes. If all goes well, you can then enable the zone shortly after. If you run into any problems, check the logs on the management node at /var/log/cloudstack/management.
|[[File:CloudStack - New Zone 12.png|left|thumb]]
|}
Once your zone has been enabled, it should automatically start a Console Proxy VM and secondary storage VM. You can find this under Infrastructure -> System VMs. If for some reason the System VMs are not starting, check that your systemvm template is available in your secondary storage and that the cloud0 bridge on each host is up. You should be able to ping the link local IP address (the 169.254.x.x address) from the hypervisor.

Once the two system VMs are running, verify that you're able to create new guest networks or VPCs. These networks should create a virtual router.

==Configuration==

===Service offerings===

====Deployment planner====
There are a few deployment techniques that can be used. These are set within a compute offering and cannot be changed after it's been created ('''really?''' can we change it via API?). The options are:
{| class="wikitable"
!Deployment planner
!Description
|-
|First fit
|Placed on the first host that has sufficient capacity
|-
|User dispersing
|Evenly distributes VMs by account across clusters
|-
|User concentrated
|Opposite of the above.
|-
|Implicit dedication
|requires or prefers (depending on planner mode) a dedicated host
|-
|Bare metal
|requires a bare metal host
|}
More information from [https://docs.cloudstack.apache.org/en/4.15.2.0/adminguide/service_offerings.html#compute-and-disk-service-offerings CloudStack's documentation on Compute and Disk Service Offerings].

===Enable SAML2 authentication===
Enable the SAML2 plugin by setting <code>saml2.enabled=true</code> under Global Settings.

Set up SAML authentication by specifying the following settings:
{| class="wikitable"
!Setting
!Description
!Example value
|-
|saml2.default.idpid
|The URL of the identity provider. This is likely obtained from the metadata URL and set by the SAML2 plugin every time CloudStack starts.
|<nowiki>https://sts.windows.net/c609a0ec-xxx-xxx-xxx-xxxxxxxxxxxx/</nowiki>
|-
|saml2.idp.metadata.url
|The metadata XML URL
|<nowiki>https://login.microsoftonline.com/609a0ec-xxx-xxx-xxx-xxxxxxxxxxxx/federationmetadata/2007-06/federationmetadata.xml?appid=c5b8df24-xxx-xxx-xxx-xxxxxxxxxxxx</nowiki>
|-
|saml2.sp.id
|The identifier string for this application
|cloudstack-test.my-organization.tld
|-
|saml2.redirect.url
|The redirect URL using your cloudstack domain.
|<nowiki>https://cloudstack-test.my-organization.tld/client</nowiki>
|-
|saml2.user.attribute
|The attribute to use as the username.
If you're not sure what's available, look at the management logs after a login attempt.
|For Azure AD, use the email address attribute: <nowiki>http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress</nowiki>
|}
Restart the management server. To allow a user access, create the user and enable SSO. The user's username must match the value that's obtained from the saml2.user.attribute field.

====Bugs====

=====SAML Request being rejected by Azure AD=====
If you are using Azure AD, you may have issues authenticating because the SAML request ID that's generated might begin with a number. When this happens, you will get an error similar to: <code>AADSTS7500529: The value '692rv91k6dgmdas33vr3b2keahr4lqjv' is not a valid SAML ID. The ID must not begin with a number.</code>. For more information, see: https://github.com/apache/cloudstack/issues/5548

=====Users cannot login via SSO=====
Users that will be using SAML for authentication will need to have their CloudStack accounts created with SSO enabled. There seems to be a bug with the CloudStack web UI where a user's SAML IdPID isn't settable (it gets set to a '0'). A work-around would be to create and authorize users via CloudMonkey.

The steps on adding a new user are:

#Create the user: <code>create user firstname=First lastname=User email=user1@ucalgary.ca username=user1@ucalgary.ca account=RCS state=enabled password=asdf</code>
#Find the user's ID: <code>list users domainid=<tab> filter=username,id</code>
#Authorize the user: <code>authorize samlsso enable=true entityid=<nowiki>https://sts.windows.net/c609a0ec-xxx-xxx-xxx-xxxxxxxxxxxx/</nowiki> userid=user-id</code>
#Verify that the user is enabled for SSO: <code>list samlauthorization filter=userid,idpid,status</code>

When authorizing a user, the entityid must be the URL of the identity provider. The end slash is also mandatory.

===Enable SSL===
A few things to note about enabling SSL:

*If you added hosts via IP address, enabling SSL would likely break the management-to-client connection. You might need to re-add the host so that the certificates all match up.
* On CloudStack 4.16, the button to upload a new certificate in the SSL dialog box does not work. This is fixed in 4.16.1.

==== Preparing your SSL certificates ====
First, generate a private key and certificate signing request and then obtain your SSL certificate from a certificate authority. For a typical CloudStack installation, you should obtain SSL certificates for both your management server as well as your console proxy.
{{Highlight
| code = # openssl genrsa -out server.key 4096
# openssl req -new -sha256 \
-key server.key \
-subj "/C=CA/ST=Alberta/O=Steamr/CN=cloudstack-test.example.com" \
-reqexts SAN \
-extensions SAN \
-config <(cat /etc/pki/tls/openssl.cnf <(printf "[SAN]\nsubjectAltName=DNS:cloudstack-test-console.example.com")) \
-out server.csr
## With the server.csr file, upload it to your Certificate Authority to obtained a signed certificate.
| lang = terminal
}}
Your certificate authority should have given you your signed certificate as well as the root and any other intermediate certificates in a X.509 (.crt) format. If you need to self sign this certificate signing request, do the following:{{Highlight
| code = ## Run the following only if you want to self sign your certificate
## Make your root CA
# openssl genrsa -des3 -out rootCA.key 4096
# openssl req -x509 -new -subj "/C=CA/ST=Alberta/O=Steamr/CN=example.com" -nodes -key rootCA.key -sha256 -days 1024 -out rootCA.crt

## Sign the certificate
# openssl x509 -req -in server.csr -CA rootCA.crt -CAkey rootCA.key -CAcreateserial -out server.crt -days 500 -sha256

## Check the certificate
# openssl x509 -in server.crt -text -noout
| lang = terminal
}}Next, you need to convert your certificate into a PKCS12 format and your private key into a PKCS8 format. This is the only format that works with the CloudStack management server. We place the PKCS12 keystore file at <code>/etc/cloudstack/management/ssl_keystore.pkcs12</code>.
{{Highlight
| code = ## Combine Files
# cat server.key server.crt intermediate.crt root.crt > combined.crt

## Create keystore
## You may use 'password' as the password
# openssl pkcs12 -in combined.crt -export -out combined.pkcs12

## Import keystore
## Provide the same password above. Eg. 'password'
# keytool -importkeystore -srckeystore combined.pkcs12 -srcstoretype PKCS12 -destkeystore /etc/cloudstack/management/ssl_keystore.pkcs12 -deststoretype pkcs12

## Convert the private key into PKCS8 format
## Provide the same password above. Eg. 'password'
# openssl pkcs8 -topk8 -in server.key -out server.pkcs8.encrypted.key
# openssl pkcs8 -in server.pkcs8.encrypted.key -out server.pkcs8.key
| lang = terminal
}}

==== Upload SSL certificates ====
You can upload SSL certificates to CloudStack under Infrastructure -> Summary and then clicking on the 'SSL Certificates" button. Provide the root certificate authority, the certificate, the private key (in PKCS8 format), and the domain that the certificate applies to. Wildcard domains should be specified as <code>*.example.com</code>.

Alternatively, you may use the CloudMonkey tool to upload certificates using the file parameter passing feature like so:

{{Highlight
| code = # cmk upload customcertificate domainsuffix=cloudstack.steamr.com id=1 name=root certificate=@root.crt
# cmk upload customcertificate domainsuffix=cloudstack.steamr.com id=2 name=intermediate1 certificate=@intermediate.crt
# cmk upload customcertificate domainsuffix=cloudstack.steamr.com id=3 privatekey=@server.pkcs8.key certificate=@domain.crt
| lang = terminal
}}

==== Enabling HTTPS ====
Next, you will need to enable HTTPS on both the management console and console proxy.

Note that you may enable the HTTPS setting only after at least one certificate has been uploaded. If the server has no certificates, the option is ignored.

===== Enable HTTPS on the management console =====
The management console can be configured by editing <code>/etc/cloudstack/management/server.properties</code> with the following lines. Set the keystore password to the same password you used above to import it.
{{Highlight
| code = https.enable=true
https.port=8443
https.keystore=/etc/cloudstack/management/ssl_keystore.pkcs12
https.keystore.password=password
| lang = text
}}Restart the management server for this to apply.
{{Info
| title = Why port 8443?
| message = Because CloudStack runs under a non-root account, it can only bind to high port (> 1024) numbers.

You can still have CloudStack visible on port 443 if you use a [[IPTables#Mapping incoming traffic to a different internal port|IPTables rule]].
}}
Confirm that you are able to reach your management console via HTTPS.

==== Enable HTTPS on the console proxy ====
If you enable SSL on the management console, you will also need to enable SSL for the console proxies for the VNC web sockets to work properly. If your management console certificate (from the previous sections) contain a Subject Alternative Name (SAN) or is a wildcard certificate that includes your console proxy's DNS name, SSL for the console proxy should be working. If your certificates do not include the console proxy's DNS name, you will need to obtain another SSL certificate and add it to the SSL keystore and upload it to CloudStack using the same instructions above.

== Tasks ==
===Re-add existing KVM bare metal host===
Once a host has been added to CloudStack, the CloudStack agent will have generated some public/private keys and configured itself to talk to the management node. If you need to remove and re-add a host, you will need to clean up the agent before re-adding it back to CloudStack again. Based on my experience, I had to do the following:

#Before removing the host from CloudStack, drain it of all VMs. <code>virsh list</code> should be empty. If not and you've removed the host from the management server already, manually kill each VM with <code>virsh destroy</code>.
#<code>systemctl stop cloudstack-agent</code>
#<code>rm -rf /etc/cloudstack/agent/cloud*</code>
#unmount any primary storages with <code>umount /mnt/*</code> and clean up with <code>rmdir /mnt/*</code>
#<code>systemctl stop libvirtd</code>
#<code>rm -rf /var/lib/libvirt/qemu</code>
#You may need to edit <code>/etc/sysconfig/libvirtd</code> to not use the listen flag. This might prevent libvirtd (and subsequently cloudstack-agent) from starting.
#Edit <code>/etc/cloudstack/agent/agent.properties</code> and remove the keystore passphrase, any UUIDs and GUIDs, cluster/pod/zone, and the host.
#Restart with <code>systemctl start cloudstack-agent</code> (libvirt should come up automatically as it's a dependency). Ensure that it comes up OK.

You may then re-add the host back to CloudStack.

===Building RPMs===
To build the RPM packages from scratch, you'll need to install a bunch of dependencies and then run the build script. For more information, see:

*<nowiki>https://docs.cloudstack.apache.org/en/4.15.2.0/installguide/building_from_source.html#building-rpms-from-source</nowiki>
{{Highlight
| code = # yum groupinstall "Development Tools"
# yum install java-11-openjdk-devel genisoimage mysql mysql-server createrepo
# yum install epel-release

# curl -sL https://rpm.nodesource.com/setup_12.x {{!}} sudo bash -
# yum install nodejs

# cat <<EOF > /etc/yum.repos.d/mysql.repo
[mysql-community]
name=MySQL Community connectors
baseurl=http://repo.mysql.com/yum/mysql-connectors-community/el/$releasever/$basearch/
gpgkey=http://repo.mysql.com/RPM-GPG-KEY-mysql
enabled=1
gpgcheck=1
EOF
# yum -y install mysql-connector-python

enable powertools

# yum install jpackage-utils maven

# git clone https://github.com/apache/cloudstack.git
# cd cloudstack
# git checkout 4.15

# cd packaging
# sh package.sh --distribution centos8
| lang = terminal
}}

=== Rebuilding UI ===
To rebuild the CloudStack management console UI (such as to test a new feature or bug fix), do the following:

# On a server with npm installed, clone the CloudStack git repo and checkout the branch with the UI fix/feature
# Navigate to <code>cloudstack/ui/</code>
# Run <code>npm install</code>
# Run <code>npm run build</code>
# Copy the <code>dist/</code> directory to <code>/usr/share/cloudstack-management/webapp/</code>

Reload the console page. Ensure that the vue app isn't cached.

===Usage server===
Install <code>cloudstack-usage</code>. Start it and restart the management server. Set <code>enable.usage.server=true</code> in global settings.

The usage data will be stored in the usage database on your management server. Metrics are gathered daily and can be viewed through Cloud Monkey. There is no option to view this data in the management console.

The collected data is coarse in nature, but it should be sufficient enough for you to determine an account or VM's resource utilization over a time period of a day or more and should be good enough to implement a rough billing / showback amount.

===Adding some Linux templates===
You can add the "Generic Cloud" qcow2 disk images as a system template to CloudStack.

Because these cloud images uses cloud-init, you will need to provide some custom userdata when deploying these images. Userdata will only work when the VM is deployed on a network that offers the "User Data" service offering. If you can't use userdata or if you want the VMs to come up with a specific root password, you can use [[virt-customize]] to set the root password on the qcow2 file.
{| class="wikitable"
!Distro
!Type
!URL
|-
|Rocky Linux 8.4
|CentOS 8
|https://download.rockylinux.org/pub/rocky/8.4/images/Rocky-8-GenericCloud-8.4-20210620.0.x86_64.qcow2
|-
|CentOS 8.4
|CentOS 8
|https://cloud.centos.org/centos/8/x86_64/images/CentOS-8-GenericCloud-8.4.2105-20210603.0.x86_64.qcow2
|-
|Fedora 34
|Fedora Linux (64 bit)
|https://download.fedoraproject.org/pub/fedora/linux/releases/34/Cloud/x86_64/images/Fedora-Cloud-Base-34-1.2.x86_64.qcow2
|-
|Ubuntu Server 21.04
|
|http://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64.img
You need to convert img to qcow with qemu-img:

<code>qemu-img create -F qcow2 -b cloudimg-amd64.img -f qcow2 cloudimg-adm64.qcow2 10G</code>
|}
Here's an example of a cloud-init configuration which you would put in the userdata field when deploying a VM:
{{Highlight
| code = #cloud-config
hostname: vm01
manage_etc_hosts: true
users:
- name: vmadm
sudo: ALL=(ALL) NOPASSWD:ALL
groups: users, admin
home: /home/vmadm
shell: /bin/bash
lock_passwd: false
ssh_pwauth: true
disable_root: false
chpasswd:
list: {{!}}
vmadm:vmadm
expire: false
| lang = text
}}

=== Importing a VMware Virtual Machine ===
To import a VMware virtual machine:

# Copy the virtual machine's .vmdk disk file to a CloudStack node
# Convert the .vmdk into a .qcow format using the qemu-img convert command. Eg. <code>qemu-img convert -f linux.vmdk -O linux.qcow2</code>
# Run the file command on the qcow disk and make a note of its size (in bytes).
# Create a new virtual machine in CloudStack. Use an ISO and not a template. Set the size of the VM's ROOT disk to match the disk size noted from the previous step.
# Start and stop the VM to ensure the virtual disk is created. Make a note of the virtual disk's ID.
# Copy the converted qcow disk over the existing virtual disk image in the primary storage.
# Restart the VM in CloudStack.

Some things to note with this process:

* The disk subsystem might differ between KVM and VMware. As a result, you may need to [[Rebuilding the initial ramdisk|rebuild the initrd file]] so that it has the necessary drivers to boot properly.

=== Increasing the management console's timeout ===
The default timeout is 30 minutes. You may adjust the number of minutes in the <code>session.timeout</code> value stored in <code>/etc/cloudstack/management/server.properties</code>.
{{Highlight
| code = session.timeout=60
| lang = xml
}}
Restart the cloudstack-management service to apply.

=== Upgrade CloudStack ===
To upgrade CloudStack to the next major release, you should first update the management server, then secondly the agents, and lastly, check if you need to upgrade any system VMs or virtual routers. Ideally, you should have the same CloudStack version across the entire cluster to avoid any weird issues due to mismatched versions. If you do have mismatched versions, you might find yourself being unable to start a virtual router properly because the virtual router version is higher than the underlying CloudStack agent doing the orchestration.

==== Updating the management server ====
Here are the general steps to upgrade the management server.

# Make sure you back up your CloudStack database before you begin. This is necessary if you wish to rollback the update because new versions typically also require a database migration which cannot be reverted easily and older CloudStack versions will refuse to start with an updated database.
# Stop the management server: <code>systemctl stop cloudstack-management</code>
# Apply the update: <code>yum -y update cloudstack\*</code>
# Manually unmount any CloudStack mounts. I had to do when I upgraded from 4.16 to 4.17 since it prevented CloudStack from starting: <code>umount /var/cloudstack/mnt/*</code>
# Ensure that the appropriate system VM template exists. This is a problem if you built a custom RPM package and didn't include it. If it's missing, download the appropriate version from http://download.cloudstack.org/systemvm. <code>ls -al /usr/share/cloudstack-management/templates/systemvm/</code>.
# Restart the management server: <code>systemctl start cloudstack-management</code>,
# Watch the CloudStack logs for any issues preventing a startup: <code>tail -f /var/log/cloud/management/*log</code>

==== Updating the CloudStack agents ====
Updating the agent is straight forward and shouldn't require you to drain VMs from the node.

# Stop CloudStack agent: <code>systemctl stop cloudstack-agent</code>
# Update the CloudStack agent: <code>yum -y update cloudstack-agent</code>
# Restart the CloudStack agent: <code>systemctl restart cloudstack-agent</code>

==== Updating the system VMs ====
Check your list of virtual routers under Infrastructure -> Virtual routers. Update any VMs that are marked with 'requires upgrade'. Do so by selecting the VM and clicking on the 'upgrade router to use newer template' button.

If the virtual router doesn't start up properly after performing an upgrade, make sure that the VM is running on a node with an appropriate CloudStack agent version. Virtual routers that land on a node with an older version of the agent won't start properly.

==== Other upgrade notes ====
Things to watch out for:

* Don't upgrade CloudStack packages on a server until you stop the CloudStack services. For some reason, I've had issues in the past where something with Java gets corrupted if you try to do an upgrade while the java processes are still running. This then results in some odd class loader issue which results in the service being unable to start after the upgrade.
* System VM template: I upgraded the CloudStack management server to 4.16.1 using a custom compiled RPM package. However, the management server didn't start and inspecting the logs show that it was expecting a system VM template at <code>/usr/share/cloudstack-management/templates/systemvm/systemvmtemplate-4.16.1-kvm.qcow2.bz2</code>. This is easily fixed by downloading the template and restarting the management server. <code>wget <nowiki>http://download.cloudstack.org/systemvm/4.16/systemvmtemplate-4.16.1-kvm.qcow2.bz2</nowiki> -O /usr/share/cloudstack-management/templates/systemvm/systemvmtemplate-4.16.1-kvm.qcow2.bz2</code>

=== Traefik ===

==== Using Traefik for SSL termination ====
With the console proxy served using SSL, we could put a reverse proxy in front of both the management UI and the console proxy service VMs with a valid certificate. This allows us to 'mask' the self-signed certificate with Traefik's ability to request for a proper certificate from Let's Encrypt.

In my test version of CloudStack, I've set up Traefik with the following configs. I updated the console proxy to use a dynamic URL by setting <code>consoleproxy.url.domain</code> to something like <code>*.cloudstack-test.example.com</code>. CloudStack's console proxy service will translate the <code>*</code> by the system VM's IP address (Eg. 10.1.1.1 becomes 10-1-1-1). We'll tell Traefik to reverse proxy these domains for both HTTPS and WSS on ports 443 and 8080 respectively. My dynamic traefik configs to make this happen looks like the following:{{Highlight
| code = http:
serversTransports:
ignorecert:
insecureSkipVerify: true

routers:
cloudstack:
rule: Host(`cloudstack-test.example.com`)
service: cloudstack-poc
entrypoints:
- http
middlewares:
- https-redirect

cloudstack-https:
rule: Host(`cloudstack-test.example.com`)
service: cloudstack-poc
entrypoints:
- https
tls:
certresolver: letsencrypt

cloudstack-pub-ip-136-159-1-100:
rule: Host(`136-159-1-1.cloudstack-test.example.com`)
service: 136-159-1-100
entrypoints:
- https
tls:
certresolver: letsencrypt

cloudstack-pub-ip-136-159-1-100-ws:
rule: Host(`136-159-1-1.cloudstack-test.example.com`)
service: 136-159-1-100-ws
entrypoints:
- httpws
tls:
certresolver: letsencrypt

services:
cloudstack-poc:
loadBalancer:
servers:
- url: "http://172.19.12.141:8080"

136-159-1-100:
loadBalancer:
servers:
- url: "https://136.159.1.100"
serversTransport: ignorecert

136-159-1-100-ws:
loadBalancer:
servers:
- url: "https://136.159.1.100:8080"
serversTransport: ignorecert

middlewares:
https-redirect:
redirectscheme:
scheme: https
| lang = yaml
}}And the following traefik configs:
{{Highlight
| code = entryPoints:
http:
address: ":80"
https:
address: ":443"
httpws:
address: ":8080"

certificatesResolvers:
letsencrypt:
acme:
email: user@example.com
storage: "/config/acme.json"
httpChallenge:
entryPoint: http
| lang = yaml
}}

=== Change guest VM CPU flags ===
The default CPU flags that guest VMs sees are set to qemu64 compatible features. The qemu64 feature set covers a very small subset of the available features that modern CPUs have which makes the guest VM be compatible to nearly all available CPUs at the cost of reduced features. The feature flags in qemu64 are: <code>fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pse36 clflush mmx fxsr sse sse2 ht syscall nx lm rep_good nopl xtopology cpuid tsc_known_freq pni cx16 x2apic hypervisor lahf_lm cpuid_fault pti</code>

For virtualized workloads that require additional feature sets, you can edit the CloudStack agent to use a different guest CPU mode. Select one of:

* '''custom''': This is the default and it defaults to the x86_qemu64 feature set defined in <code>/usr/share/libvirt/cpu_map/x86_qemu64.xml</code>. You may select a different CPU map by specifying <code>guest.cpu.model</code>.
* '''host-model''': Uses a CPU model compatible with your host. Most feature flags are available.
* '''host-passthrough''': Use CPU passthrough; feature flags match exactly. Migrations only work with matching CPUs and may still fail when using this mode.

For CloudStack clusters with identical CPUs, it's recommended to use host-model. I've tried using host-passthrough on matching hosts using a Intel Xeon Silver 4316 and migrations sometimes fail and the VM requires a reset to be brought back up.

For more information, see: http://docs.cloudstack.apache.org/en/4.15.0.0/installguide/hypervisor/kvm.html#install-and-configure-the-agent

To change the CPU mode, you simply need to add the appropriate line into the agent properties file and restart the agent:
{{Highlight
| code = ## Matching host model
# echo "guest.cpu.mode=host-model" >> /etc/cloudstack/agent/agent.properties
# systemctl restart cloudstack-agent.service

## Passthrough
# echo "guest.cpu.mode=host-passthrough" >> /etc/cloudstack/agent/agent.properties
# systemctl restart cloudstack-agent.service
| lang = terminal
}}

=== Using Open vSwitch and DPDK ===
Getting DPDK working with Open vSwitch is relatively straight forward. You need to install the DPDK packages, configure the kernel to use hugepages and IO passthrough, enable the vfio driver on your network interfaces for DPDK support, reconfigure Open vSwitch to use the DPDK device, and enable DPDK on the CloudStack agent.

There are some existing resources that might help.

*https://www.shapeblue.com/openvswitch-with-dpdk-support-on-cloudstack/
* https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/ovs-dpdk_end_to_end_troubleshooting_guide/configure_and_test_lacp_bonding_with_open_vswitch_dpdk

Install DPDK tools:

{{Highlight
| code = # yum -y install dpdk dpdk-tools
| lang = terminal
}}

Reconfigure your kernel by editing <code>/etc/default/grub</code>. Add the following. Adjust the <code>isolcpus</code> depending on your CPUs available. I assigned 4 cores out of 80 vCPUs. I am also using 16 1GB huge pages. Adjust this according to how much memory your system has (and probably what performance you're seeing){{Highlight
| code = # vi /etc/default/grub
## default_hugepagesz=1GB hugepagesz=1G hugepages=16 iommu=pt intel_iommu=on isolcpus=1-19,21-39,41-59,61-79 intel_pstate=disable nosoftlockup

# grub2-mkconfig -o /boot/grub2/grub.cfg
| lang = terminal
}}You can also configure huge pages by sysctl (optional if you set it in the kernel cmdline){{Highlight
| code = # echo 'vm.nr_hugepages=16' > /etc/sysctl.d/hugepages.conf
# sysctl -w vm.nr_hugepages=16
| lang = terminal
}}Load the <code>vfio-pci</code> kernel module on boot
{{Highlight
| code = # echo vfio-pci > /etc/modules-load.d/vfio-pci.conf
| lang = terminal
}}
Reboot the machine. When it comes back, verify that you have hugepages and vfio-pci loaded, and that IOMMU is working.
{{Highlight
| code = # cat /proc/cmdline {{!}} grep iommu=pt
# cat /proc/cmdline {{!}} grep intel_iommu=on
# dmesg {{!}} grep -e DMAR -e IOMMU
# grep HugePages_ /proc/meminfo
# lsmod {{!}} grep vfio-pci
| lang = terminal
}}
Set the network interfaces you wish to use DPDK on to the vfio-pci driver. This is done using the <code>dpdk-devbind.py</code> script that's provided by the DPDK tools package.{{Highlight
| code = # modprobe vfio-pci
# dpdk-devbind.py --bind=vfio-pci ens2f0
# dpdk-devbind.py --bind=vfio-pci ens2f1
## Verify
# dpdk-devbind.py --status

Network devices using DPDK-compatible driver
============================================
0000:31:00.0 'Ethernet Controller X710 for 10GBASE-T 15ff' drv=vfio-pci unused=i40e
0000:31:00.1 'Ethernet Controller X710 for 10GBASE-T 15ff' drv=vfio-pci unused=i40e
| lang = terminal
}}Enable DPDK on Open vSwitch. pmd-cpu-mask defines what cores are used for data path packet processing. The dpdk-lcore-mask defines cores that non-datapath OVS-DPDK threads such as handler and revalidator threads run. These two masks should not overlap. For more information on these parameters, see: https://developers.redhat.com/blog/2017/06/28/ovs-dpdk-parameters-dealing-with-multi-numa<nowiki/>.{{Highlight
| code =
# ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
# ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-lcore-mask=0x00000001
# ovs-vsctl --no-wait set Open_vSwitch . other_config:pmd-cpu-mask=0x17c0017c
# ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem="1024"

## Verify
# ovs-vsctl get Open_vSwitch . dpdk_initialized
# ovs-vsctl get Open_vSwitch . dpdk_version
| lang = terminal
}}If Open vSwitch is already configured to use these interfaces by name, you will just need to change the interface type to dpdk and set its PCI address.
{{Highlight
| code = # ovs-vsctl set interface ens2f0 type=dpdk
# ovs-vsctl set interface ens2f0 options:dpdk-devargs=0000:31:00.0
# ovs-vsctl set interface ens2f1 type=dpdk
# ovs-vsctl set interface ens2f1 options:dpdk-devargs=0000:31:00.1
| lang = terminal
}}
The bridge that these interfaces are connected to must also have its datapath_type updated:
{{Highlight
| code = # ovs-vsctl set bridge nic0 datapath_type=netdev
| lang = terminal
}}
Restart Open vSwitch for these to apply properly and confirm that it's working
{{Highlight
| code = # systemctl restart openvswitch
# ovs-vsctl show
...
Port bond0
Interface ens2f1
type: dpdk
options: {dpdk-devargs="0000:31:00.1"}
Interface ens2f0
type: dpdk
options: {dpdk-devargs="0000:31:00.0"}
| lang = terminal
}}
Update the CloudStack agent so that this host has the DPDK capability. Edit <code>/etc/cloudstack/agent/agent.properties</code>. Note that the keyword is <code>openvswitch.dpdk.enabled</code> (enabled ending with -ed). The example from ShapeBlue's blog post is wrong.{{Highlight
| code = network.bridge.type=openvswitch
libvirt.vif.driver=com.cloud.hypervisor.kvm.resource.OvsVifDriver
openvswitch.dpdk.enabled=true
openvswitch.dpdk.ovs.path=/var/run/openvswitch/
| lang = text
}}Restart the CloudStack agent for this capability to be visible by the management server. You should be able to call <code>list hosts filter=capabilities,name</code> and have the host list dpdk as a capability. Eg:
{{Highlight
| code = (localcloud) 🐱 > list hosts filter=capabilities,name
count = 22
host:
+-------------------+----------+
{{!}} CAPABILITIES {{!}} NAME {{!}}
+-------------------+----------+
{{!}} hvm,snapshot,dpdk {{!}} cs9 {{!}}
{{!}} hvm,snapshot,dpdk {{!}} cs10 {{!}}
{{!}} hvm,snapshot,dpdk {{!}} cs11 {{!}}
| lang = terminal
}}
If you don't see this, double check your agent configs and restart it again.

For VMs to take advantage of DPDK, you must either set extraconfig on the virtual machine or create a new compute service offering. Extraconfig might get overwritten whenever the VM is updated, so it's not a reliable solution. Extraconfig is a URL encoded config and you cannot use single quotes in it or else you will break the VM deployment. Eg:
{{Highlight
| code = (localcloud) 🐱 > update virtualmachine extraconfig=dpdk-hugepages:%0A%3CmemoryBacking%3E%0A%20%20%20%3Chugepages%3E%0A%20%20%20%20%3C/hugepages%3E%0A%3C/memoryBacking%3E%0A%0Adpdk-numa:%0A%3Ccpu%20mode=%22host-passthrough%22%3E%0A%20%20%20%3Cnuma%3E%0A%20%20%20%20%20%20%20%3Ccell%20id=%220%22%20cpus=%220%22%20memory=%229437184%22%20unit=%22KiB%22%20memAccess=%22shared%22/%3E%0A%20%20%20%3C/numa%3E%0A%3C/cpu%3E%0A%0Adpdk-interface-queue:%0A%3Cdriver%20name=%22vhost%22%20queues=%22128%22/%3E id=af64cc80-a4e4-4c17-9c7d-c34ed234dc6a
virtualmachine = map[account:RCS affinitygroup:[] cpunumber:2 cpuspeed:1000 cpuused:5.88% created:2022-05-03T13:16:02-0600 details:map[Message.ReservedCapacityFreed.Flag:false dpdk-hugepages:a extraconfig-dpdk-hugepages:<memoryBacking>
| lang = terminal
}}

==== Troubleshooting ====
{{Highlight
| code = 2022-05-05T22:35:28.312Z{{!}}281704{{!}}netdev_dpdk{{!}}INFO{{!}}vHost Device '/var/run/openvswitch/csdpdk-1' connection has been destroyed
2022-05-05T22:35:28.312Z{{!}}281705{{!}}netdev_dpdk{{!}}INFO{{!}}vHost Device '/var/run/openvswitch/csdpdk-1' connection has been destroyed
2022-05-05T22:35:28.313Z{{!}}281706{{!}}netdev_dpdk{{!}}INFO{{!}}vHost Device '/var/run/openvswitch/csdpdk-1' connection has been destroyed
2022-05-05T22:35:28.313Z{{!}}281707{{!}}netdev_dpdk{{!}}INFO{{!}}vHost Device '/var/run/openvswitch/csdpdk-1' connection has been destroyed
2022-05-05T22:35:28.313Z{{!}}281708{{!}}netdev_dpdk{{!}}INFO{{!}}vHost Device '/var/run/openvswitch/csdpdk-1' connection has been destroyed
| lang = text
}}
Check the agent logs for issues from qemu. I had defined an invalid property which prevented the VM from starting.
{{Highlight
| code = [root@cs10 agent]# grep qemu agent.log
org.libvirt.LibvirtException: internal error: process exited while connecting to monitor: 2022-05-05T22:35:52.060450Z qemu-kvm: -netdev vhost-user,chardev=charnet0,queues=256,id=hostnet0: you are asking more queues than supported: 128
2022-05-05T22:35:52.060633Z qemu-kvm: -netdev vhost-user,chardev=charnet0,queues=256,id=hostnet0: you are asking more queues than supported: 128
2022-05-05T22:35:52.060817Z qemu-kvm: -netdev vhost-user,chardev=charnet0,queues=256,id=hostnet0: you are asking more queues than supported: 128
| lang = terminal
}}

==Tools==

===CloudMonkey===
Get started:

*Download from: https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.1.0
*Documentation at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+cloudmonkey+CLI

When you first run CloudMonkey, you will need to set the CloudStack instance URL and credentials and then run sync.
{{Highlight
| code = $ cmk
> set url http://172.19.12.141:8080/client/api
> set username admin
> set password password
> sync
| lang = terminal
}}
The settings are then saved to <code>~/.cmk/config</code>.

The sync command fetches all the available API calls that your account can use. Once that is done, you can then use tab completion while in the CloudMonkey CLI.

====Cheat sheet====
{| class="wikitable"
!What
!Command
|-
|Change output format
|<code><nowiki>set display table|json</nowiki></code>
|-
|Create compute offering
|<code>create serviceoffering name=rcs.c2 displaytext=Medium cpunumber=2 cpuspeed=750 memory=2048 storagetype=shared provisioningtype=thin offerha=false limitcpuuse=false isvolatile=false issystem=false deploymentplanner=UserDispersingPlanner cachemode=none customized=false</code>
|-
|Add a new host
|<code>add host clusterid=XX podid=XX zoneid=XX hypervisor=KVM password=**** username=root url=<nowiki>http://bm01</nowiki></code>
|}

====Automate zone deployments====
There is an example script on how to automate a basic zone deployment at: https://github.com/apache/cloudstack-cloudmonkey/wiki/Usage

=== Terraform ===
The Terraform CloudStack provide works for the most part. However, for CloudStack 4.16, you'll need to recompile it from scratch because the distributed binaries don't work properly (resulting in deployments hanging indefinitely). To build the Terraform provider, I will use Docker:

{{Highlight
| code = # git clone https://github.com/apache/cloudstack-terraform-provider.git
# cd cloudstack-terraform-provide
# git clone https://github.com/tetra12/cloudstack-go.git
# cat <<EOF >> go.mod
replace github.com/apache/cloudstack-go/v2 => ./cloudstack-go
exclude github.com/apache/cloudstack-go/v2 v2.11.0
EOF
# docker run --rm -ti -v /home/me/cloudstack-terraform-provider/:/build golang bash
> cd /build
> go build
| lang = terminal
}}

Copy the resulting binary to your terraform plugins path. Because I ran terraform init, it placed it in my terraform directory under <code>.terraform/providers/registry.terraform.io/cloudstack/cloudstack/0.4.0/linux_amd64/terraform-provider-cloudstack_v0.4.0</code>. Edit the metadata file in the same directory as the provider executable and remove the file hash so that terraform runs the provider.

See also: [[Terraform#CloudStack]]

=== Packer ===
The Packer CloudStack provider also works for the most part, but is limited in that it cannot enter keyboard inputs. Any OS deployments will require some sort of manual inputs or require that the ISO media you use is completely automated. I also had to compile the provider manually since the default plugin that's fetched by packer doesn't quite work due to API changes.

See also: [[Packer#CloudStack]]

==Troubleshooting==
When you run into issues, check the logs in <code>/var/log/cloudstack/</code>. There's typically a stacktrace which gets generated whenever you encounter an error.

===Can't create shared network in a advanced zone using Open vSwitch===
Whenever I try creating a shared network in an advanced zone that is using OVS, the step fails with: "Unable to convert network offering with specified id to network profile".

Stack trace shows that the [https://github.com/apache/cloudstack/blob/bf6266188c89a5487383f216333ae10e878d2c10/plugins/network-elements/ovs/src/main/java/com/cloud/network/guru/OvsGuestNetworkGuru.java#L99 OVS guest network guru] isn't able at designing the network because the zone isn't capable of handling this network offering.

{{Highlight
| code = 2021-09-28 16:36:26,416 DEBUG [c.c.a.ApiServer] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) CIDRs from which account 'Acct[76a1585d-1bf6-11ec-a3c5-8f3e88f01ab1-admin]' is allowed to perform API calls: 0.0.0.0/0,::/0
2021-09-28 16:36:26,439 DEBUG [c.c.u.AccountManagerImpl] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) Access granted to Acct[76a1585d-1bf6-11ec-a3c5-8f3e88f01ab1-admin] to [Network Offering [7-Guest-DefaultSharedNetworkOffering] by AffinityGroupAccessChecker
2021-09-28 16:36:26,517 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) Refusing to design this network, the physical isolation type is not BCF_SEGMENT
2021-09-28 16:36:26,521 DEBUG [o.a.c.n.c.m.ContrailGuru] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) Refusing to design this network
2021-09-28 16:36:26,524 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) Refusing to design this network
2021-09-28 16:36:26,527 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) Refusing to design this network
2021-09-28 16:36:26,530 DEBUG [c.c.n.g.OvsGuestNetworkGuru] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) Refusing to design this network
2021-09-28 16:36:26,536 DEBUG [c.c.n.g.DirectNetworkGuru] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) GRE: VLAN
2021-09-28 16:36:26,536 DEBUG [c.c.n.g.DirectNetworkGuru] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) GRE: VXLAN
2021-09-28 16:36:26,536 INFO [c.c.n.g.DirectNetworkGuru] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) Refusing to design this network
2021-09-28 16:36:26,539 INFO [c.c.n.g.DirectNetworkGuru] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) Refusing to design this network
2021-09-28 16:36:26,543 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) SSP not configured to be active
2021-09-28 16:36:26,546 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) Refusing to design this network
2021-09-28 16:36:26,549 DEBUG [o.a.c.e.o.NetworkOrchestrator] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) Releasing lock for Acct[76a0531f-1bf6-11ec-a3c5-8f3e88f01ab1-system]
2021-09-28 16:36:26,624 DEBUG [c.c.u.d.T.Transaction] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) Rolling back the transaction: Time = 172 Name = qtp1816147548-400; called by -TransactionLegacy.rollback:888-TransactionLegacy.removeUpTo:831-TransactionLegacy.close:655-Transaction.execute:38-Transaction.execute:47-NetworkOrches
trator.createGuestNetwork:2572-NetworkOrchestrator.createGuestNetwork:2327-NetworkServiceImpl$4.doInTransaction:1502-NetworkServiceImpl$4.doInTransaction:1450-Transaction.execute:40-NetworkServiceImpl.commitNetwork:1450-NetworkServiceImpl.createGuestNetwork:1366
2021-09-28 16:36:26,667 ERROR [c.c.a.ApiServer] (qtp1816147548-400:ctx-291672d1 ctx-3f19296a) (logid:83c45c2a) unhandled exception executing api command: [Ljava.lang.String;@69a8823d
com.cloud.utils.exception.CloudRuntimeException: Unable to convert network offering with specified id to network profile
at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator.setupNetwork(NetworkOrchestrator.java:739)
at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2634)
at org.apache.cloudstack.engine.orchestration.NetworkOrchestrator$10.doInTransaction(NetworkOrchestrator.java:2572)
at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:50)
at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
at com.cloud.utils.db.Transaction.execute(Transaction.java:47)
...
| lang = text
}}

====Possible answer====
The guest network was set up with GRE isolation. This however isn't supported with KVM as the hypervisor (see [https://events.static.linuxfound.org/sites/events/files/slides/CloudStack%20Collab%20Hypervisor.pdf this presentation]). After re-creating the zone with the guest physical network set up with just VLAN isolation, I was able to create a regular shared guest network that all tenants within the zone can see and use.

To make the shared network SNAT out, I created another shared network offering that also has SourceNat and StaticNat.
{{Highlight
| code = $ cmk list serviceofferings issystem=true name='System Offering For Software Router'
$ cmk create networkoffering \
name=SharedNetworkOfferingWithSourceNatService displaytext="Shared Network Offering with Source NAT Service" traffictype=GUEST guestiptype=shared conservemode=true specifyvlan=true specifyipranges=true \
serviceofferingid=307b14d8-afd1-43ea-948c-ffe882cd5926 \
supportedservices=Dhcp,Dns,Firewall,SourceNat,StaticNat,PortForwarding \
serviceProviderList[0].service=Dhcp serviceProviderList[0].provider=VirtualRouter \
serviceProviderList[1].service=Dns serviceProviderList[1].provider=VirtualRouter \
serviceProviderList[2].service=Firewall serviceProviderList[2].provider=VirtualRouter \
serviceProviderList[3].service=SourceNat serviceProviderList[3].provider=VirtualRouter \
serviceProviderList[4].service=StaticNat serviceProviderList[4].provider=VirtualRouter \
serviceProviderList[5].service=PortForwarding serviceProviderList[5].provider=VirtualRouter \
servicecapabilitylist[0].service=SourceNat servicecapabilitylist[0].capabilitytype=SupportedSourceNatTypes servicecapabilitylist[0].capabilityvalue=peraccount
| lang = terminal
}}
Using this network offering, I was able to create a shared network in the advanced networking zone that has a NAT service which is visible to all accounts. The only issue with this approach is that there isn't a way to create a port forwarding for a specific VM because the account that owns this network is 'system'.

==Open-ended questions==
===Compute offerings with 'unlimited' CPU cycles?===
Compute offerings require a MHz value assigned. Why is this? Can we just assign a VM entire cores?

- If you read the docs, CPU (in MHz) only has an effect if CPU cap is selected. In all other cases, the value here is something akin to 'cpu shares'.

- if you put in a huge number like 9999, deployment would fail though.

===How to implement showback?===
Is there a way to implement showback based on resources consumed by account?

===Monitoring resources?===
Is there a way to monitor resource usage by account, node? Any good way to push VMs into a CMDB like ServiceNow?

===NetApp integration?===
Is it possible to do guest VM snapshots by leveraging NetApp?

===Backups?===
The only backup plugins that are available are 'dummy' which does nothing and 'veeam' which only supports VMware + Veeam. If you're using KVM, there doesn't seem to be any way to easily backup/restore VMs.<br />

<br />
{{Navbox Linux}}
[[Category:Linux]]
[[Category:LinuxUtilities]]

LXR Guide

2018-05-04T17:21:54Z

136.159.16.240: /* Prerequisites */

LXR, shortened for Linux Cross-Reference, is a perl web application that lets you read different versions of the Linux kernel source code with the added benefit of quickly searching the source and having static values and functions cross-referenced with each other.

== Step by Step Guide ==
The installation of LXRng are detailed in this guide for a CentOS 7 server. We will be using:
* LXRng
* PostgreSQL (as a fulltext index)
* Apache 2.4 / mod_perl

=== Prerequisites ===
On a clean install of CentOS 7, install the following dependencies. A few Perl modules must be installed outside of yum and I recommend using cpanm.

{{highlight|lang=terminal|code=
# yum install postgresql postgresql-server \
perl-App-cpanminus \
xapian-core xapian-core-devel \
perl-DBI perl-DBD-Pg \
perl-Term-ProgressBar \
perl-Pod-POM \
perl-CGI \
perl-HTML-Template \
perl-XML-Parser \
perl-XML-NamespaceSupport \
perl-XML-LibXML \
perl-XML-SAX-Base \
perl-Image-Xbm \
perl-Image-Base \
perl-Template-Toolkit \
perl-Linux-Pid \
perl-BSD-Resource \
make gcc gcc-c++ \
ctags \
httpd \
mod_perl mod_ssl \
git \
screen
}}

lxr expects it as {{code|ctag}} as {{code|ctags-exuberant}}.

{{highlight|lang=terminal|code=
# ln -s /usr/bin/ctags /usr/bin/ctags-exuberant
}}

Install the missing dependencies through cpanm:

{{highlight|lang=terminal|code=
# cpanm Search::Xapian
# cpanm Test::More
# cpanm Devel::Size
}}

Pull the lxrng source into {{code|/var/www}}. Apache will own everything since the web server will need to run the web application.

{{highlight|lang=terminal|code=
# cd /var/www
# chgrp apache .
# sudo -u apache git clone git://lxr.linux.no/git/lxrng.git
}}

If this repository is down, a copy is also available at https://git.steamr.com/leo/lxrng.git

=== Setting up PostgreSQL ===

With PostgreSQL installed, set it up with a lxrng database. You may want to set up permissions as well, but I will be using the root account.

{{highlight|lang=terminal|code=
# postgresql-setup initdb
# systemctl start postgresql
# systemctl enable postgresql
}}

By default, Postgres should be configured to use system accounts for authentication. Since we will have the Apache web server running as {{code|apache}}, we will create a Postgres account named {{code|apache}} that should have access to the lxrng database.

{{highlight|lang=terminal|code=
# su postgres
$ createuser -d apache
}}

=== LXRng Setup ===
The {{code|lxrng.conf}} configuration file located at {{code|/var/www/lxrng/lxrng.conf}} should contain the following:

{{highlight|lang=text|code=
# -*- mode: perl -*-
# Configuration file
#
#

use LXRng::Index::PgBatch;
use LXRng::Repo::Git;
use LXRng::Search::Xapian;

my $gitrepo = LXRng::Repo::Git
->new('/var/www/lxrng/repos/linux-2.6/.git',
release_re => qr/^v[^-]*$/,
author_timestamp => 0);

my $index = LXRng::Index::PgBatch->new(db_spec => 'dbname=lxrng;port=5432',
db_user => "apache", db_pass => "",
# table_prefix => 'lxr'
);
my $search = LXRng::Search::Xapian->new('/var/www/lxrng/text-db/linux-2.6');

return {
'linux' => {
'repository' => $gitrepo,
'index' => $index,
'search' => $search,

'base_url' => 'http://lxr.cpsc.ucalgary.ca/',
# Must be writable by httpd user:
'cache' => '/var/www/lxrng/cache',

'fs_charset' => 'iso-8859-1',
# Tried successively
'content_charset' => ['utf-8', 'iso-8859-1'],

'languages' => ['C', 'GnuAsm', 'Kconfig'],
#'ctags_flags' => ["-I\@$LXRng::ROOT/lxr-ctags-quirks"],
'ver_list' => [$gitrepo->allversions],

'ver_default' => 'v4.9',

'include_maps' =>
[
[qr{{!}}^arch/(.*?)/{{!}}, qr{{!}}^asm/(.*){{!}},
sub { "include/asm-$_[0]/$_[1]" }],
[qr{{!}}^include/asm-(.*?)/{{!}}, qr{{!}}^asm/(.*){{!}},
sub { "include/asm-$_[0]/$_[1]" }],
[qr{{!}}^{{!}}, qr{{!}}^asm/(.*){{!}},
sub { map { "include/asm-$_/$_[0]" }
qw(i386 alpha arm ia64 m68k mips mips64),
qw(ppc s390 sh sparc sparc64 x86_64) }],
[qr{{!}}^{{!}}, qr{{!}}(.*){{!}},
sub { "include/$_[0]" }],
],
},
};

}}

There are a few important values which you may want to change:
* {{code|$gitrepo}} defines where the source code (as a git repo) will be placed. In our case, {{code|/var/www/lxrng/repos}} should contain a directory called {{code|linux-2.6/.git}} containing the git repository.
* {{code|$search}} defines where the text index should reside
* {{code|base_url}} is the URL of the web application
* {{code|cache}} is the cache directory used by lxr.

Create these directories, and ensure they are readable and writable by apache:
{{highlight|lang=terminal|code=
# cd /var/www/lxrng
# mkdir repos
# mkdir -p text-db/linux-2.6
# mkdir cache
# chmod 777 cache
}}

=== Fetch the Kernel Source ===
Get the source code either via git or from an existing tarball.

{{highlight|lang=terminal|code=
# cd /var/www/lxrng/repos
# git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

## or for the newest post-2.6 kernels:
# git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
}}

Start the indexing process:

{{highlight|lang=terminal|code=
# cd /var/www/lxrng/
# sudo -u apache sh
$ ./lxr-db-admin linux --init
$ ./lxr-genxref linux
## Or alternatively, run it in screen: screen -d -m ./lxr-genxref linux
## and then view progress by running screen -r
}}

=== Setting up Apache ===

{{highlight|lang=terminal|code=
# cd /export/lxrng
# cp apache2-site.conf-dist-mod_perl /etc/httpd/conf.d/lxrng.conf
# sed -i "s/@@LXRROOT@@/\/export\/lxrng/g" /etc/httpd/conf.d/lxrng.conf
# sed -i "s/@@LXRURL@@/lxr/g" /etc/httpd/conf.d/lxrng.conf
# sed -i "s/^[$^#$]*/# /" /etc/httpd/conf.d/welcome.conf
# /etc/init.d/httpd start
# chkconfig httpd on --level 345
}}

== Updating Kernel Source ==
{{highlight|lang=terminal|code=
# cd repos
# git pull git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git master
}}

Then, rerun the xref to update.
{{highlight|lang=terminal|code=
$ ./lxr-genxref linux
}}

[[Category:Linux]]

[[Category:Guides]]

Systemd

2018-04-04T21:32:24Z

136.159.16.240: /* Limiting Log Sizes */

== Journal ==
Systemd keeps tracks of service logs.

=== Clearing Journal ===

Clear all the entries by running:

{{highlight|lang=terminal|code=
# journalctl --vacuum-time=1seconds
}}

Or

{{highlight|lang=terminal|code=
# journalctl --vacuum-size=1M
}}

=== Limiting Log Sizes ===

Edit {{code|/etc/systemd/journald.conf}} and define a value for {{code|SystemMaxUse}}. Eg. {{code|1=SystemMaxUse=100M}}.

== Creating a Service ==
Suppose you have a program that you want started when the system boots. To have systemd start the program as a service, create a new service file in {{code|/etc/systemd/system}} containing something like:

{{highlight|lang=terminal|code=
# cat /etc/systemd/system/mag-read.service
[Unit]
Description=Mag card reader

[Install]
WantedBy=multi-user.target

[Service]
ExecStart=/root/scripts/mag.sh
Restart=always
}}

This service file will execute {{code|mag.sh}} which will start a process that sits and waits for input from a mag-strip card reader and will automatically restart it if it stops.

Once the file has been created, reload systemd and enable the service:
{{highlight|lang=terminal|code=
# systemctl daemon-reload # Reloads the service files so systemd is aware of the new one
# systemctl enable mag-read
}}

== SystemV-like Init Scripts ==

If you have custom packages that make use of the old SystemV startup scripts, you can use the following files to make use of such scripts.

In {{code|/usr/lib/systemd/system/startup.service}}

{{highlight|lang=text|code=
[Unit]
Description=Custom SystemV-like Startup
After=network.target
ConditionFileIsExecutable=/usr/local/sbin/custom-startup-initd

[Service]
Type=oneshot
ExecStart=/usr/local/sbin/custom-startup-initd
TimeoutSec=0
StandardOutput=tty
RemainAfterExit=yes
SysVStartPriority=99

[Install]
WantedBy=multi-user.target
}}

A few things of interest.
* The {{code|ConditionFileIsExecutable}} will only run the script if it's executable. It basically does a {{code|test -x}} on the file before this continues.
* {{code|RemainAfterExit}} will cause systemd to show the service as active even after the script has finished execution.

In {{code|/usr/local/sbin/custom-startup-initd}}:
{{highlight|lang=terminal|code=
#!/bin/sh
StartupDir="/usr/local/boot/startup"

# Run all scripts starting with 'S'
for i in `ls $StartupDir/S*` ; do
ScriptName=`basename $i`
sh $StartupDir/$ScriptName
done

# Success exit code.
exit 0
}}

Make the directory:
{{highlight|lang=terminal|code=
# mkdir -p /usr/local/boot/startup/
}}

Then place your scripts in the startup directory starting with the letter 'S'.

Enable the new service by running:
{{highlight|lang=terminal|code=
# systemctl enable startup
# systemctl start startup
}}

Verify this:
{{highlight|lang=terminal|code=
# systemctl status startup.service
}}

[[Category:Linux]]

{{Navbox Linux}}

Systemd

2018-04-04T21:32:02Z

136.159.16.240: /* Journal */

== Journal ==
Systemd keeps tracks of service logs.

=== Clearing Journal ===

Clear all the entries by running:

{{highlight|lang=terminal|code=
# journalctl --vacuum-time=1seconds
}}

Or

{{highlight|lang=terminal|code=
# journalctl --vacuum-size=1M
}}

=== Limiting Log Sizes ===

Edit {{code|/etc/systemd/journald.conf}} and define a value for {{code|SystemMaxUse}}. Eg. {{code|SystemMaxUse=100M}}.

== Creating a Service ==
Suppose you have a program that you want started when the system boots. To have systemd start the program as a service, create a new service file in {{code|/etc/systemd/system}} containing something like:

{{highlight|lang=terminal|code=
# cat /etc/systemd/system/mag-read.service
[Unit]
Description=Mag card reader

[Install]
WantedBy=multi-user.target

[Service]
ExecStart=/root/scripts/mag.sh
Restart=always
}}

This service file will execute {{code|mag.sh}} which will start a process that sits and waits for input from a mag-strip card reader and will automatically restart it if it stops.

Once the file has been created, reload systemd and enable the service:
{{highlight|lang=terminal|code=
# systemctl daemon-reload # Reloads the service files so systemd is aware of the new one
# systemctl enable mag-read
}}

== SystemV-like Init Scripts ==

If you have custom packages that make use of the old SystemV startup scripts, you can use the following files to make use of such scripts.

In {{code|/usr/lib/systemd/system/startup.service}}

{{highlight|lang=text|code=
[Unit]
Description=Custom SystemV-like Startup
After=network.target
ConditionFileIsExecutable=/usr/local/sbin/custom-startup-initd

[Service]
Type=oneshot
ExecStart=/usr/local/sbin/custom-startup-initd
TimeoutSec=0
StandardOutput=tty
RemainAfterExit=yes
SysVStartPriority=99

[Install]
WantedBy=multi-user.target
}}

A few things of interest.
* The {{code|ConditionFileIsExecutable}} will only run the script if it's executable. It basically does a {{code|test -x}} on the file before this continues.
* {{code|RemainAfterExit}} will cause systemd to show the service as active even after the script has finished execution.

In {{code|/usr/local/sbin/custom-startup-initd}}:
{{highlight|lang=terminal|code=
#!/bin/sh
StartupDir="/usr/local/boot/startup"

# Run all scripts starting with 'S'
for i in `ls $StartupDir/S*` ; do
ScriptName=`basename $i`
sh $StartupDir/$ScriptName
done

# Success exit code.
exit 0
}}

Make the directory:
{{highlight|lang=terminal|code=
# mkdir -p /usr/local/boot/startup/
}}

Then place your scripts in the startup directory starting with the letter 'S'.

Enable the new service by running:
{{highlight|lang=terminal|code=
# systemctl enable startup
# systemctl start startup
}}

Verify this:
{{highlight|lang=terminal|code=
# systemctl status startup.service
}}

[[Category:Linux]]

{{Navbox Linux}}

Pacman

2018-04-03T16:41:40Z

136.159.16.240: /* Introduction */

Pacman is the package manager for arch linux.

== Introduction ==

Configuration files are stored in /etc/pacman
=== Updating Databases ===

Similar to a {{code|yum clean all ; yum update}} you can update the repository information by running:
pacman -Syy

=== Searching ===
Search for a package
pacman -Ss packageName

=== Installing ===
pacman -S packageName groupName

=== Updating System ===
pacman -Syu

=== Removing a Package ===
pacman -R packageName

With dependencies
pacman -Rsc packageName

=== Searching for whatprovides ===
Install the pkgfile utilitiy
pacman -S pkgfile

Update the repo:
pkgfile --update

Then to search:
pkgfile -s lspci
core/pciutils

=== Searching Package Ownership ===
When given a path (eg. /usr/bin/startx), you can find which package provided the file by using:

pacman -Qo /usr/bin/startx

This is similar to RPM's {{code|rpm -qf /usr/bin/startx}}.

[[Category:Linux]]
[[Category:PackageManagement]]
{{Navbox Linux}}

Raspberry Pi

2017-02-27T23:39:21Z

136.159.16.240: /* Arch Linux */

== Setup ==
=== Arch Linux ===
Download ArchLinux's Raspberry Pi tarball.
* Raspberry Pi: http://archlinuxarm.org/os/ArchLinuxARM-rpi-latest.tar.gz
* Raspberry Pi 2: http://archlinuxarm.org/os/ArchLinuxARM-rpi-2-latest.tar.gz

Setup the SD card to contain two partitions using fdisk:
# 100MB (W95 FAT32 (LBA))
# Rest: OS / Data

{{highlight|lang=terminal|code=
# fdisk /dev/sdcard
## Set up the SD card partitions
## Commands are: o, n, p, [enter], +100M, t, c, n, p, 2, [enter], [enter], w
# mkfs.vfat /dev/sdcard1
# mkfs.ext4 /dev/sdcard2
# cd /mnt
# mkdir root root/boot
# mount /dev/sdcard2 root
# mount /dev/sdcard1 root/boot
# tar -xpf ArchLinuxARM-rpi-latest.tar.gz -C root
# umount root/boot root
}}

Once the SD card is prepared, insert it to the Pi and power it on. Log in to ArchLinux using the default user {{code|alarm}} using password {{code|alarm}}. The default root password is {{code|root}}.

For more information and to see the latest images see:
* http://archlinuxarm.org/platforms/armv6/raspberry-pi
* http://archlinuxarm.org/platforms/armv7/broadcom/raspberry-pi-2

== Configuration ==
=== Wifi ===
See [[Wifi]].

== Miscellaneous ==
=== Control Status LEDs ===
The Raspberry Pi 2 LEDs are driven by the kernel's led-GPIO drivers. This allows for the LEDs to be controlled by software rather than hardware as is the case with the older first generation Pi's. The two LEDs on the Raspberry Pi 2 are the green status light (led0) and the red power light (led1).

To see the available triggers that are in use and available for a particular LED:
{{highlight|lang=terminal|code=
# cat /sys/class/leds/led1/trigger
none usb-gadget usb-host [mmc0] timer oneshot heartbeat backlight gpio cpu0 cpu1 cpu2 cpu3 default-on transient flash torch input
}}

The active trigger is in {{code|[ ]}} and can be changed by writing to the file. For example, to turn off the LED entirely:
{{highlight|lang=terminal|code=
# echo none > /sys/class/leds/led1/trigger
# cat /sys/class/leds/led1/trigger
[none] usb-gadget usb-host mmc0 timer oneshot heartbeat backlight gpio cpu0 cpu1 cpu2 cpu3 default-on transient flash torch input
}}

You may also edit the {{code|config.txt}} file to change the behavior on startup.
{{highlight|lang=text|code=
# Disable the ACT LED.
dtparam=act_led_trigger=none
dtparam=act_led_activelow=off

# Disable the PWR LED.
dtparam=pwr_led_trigger=none
dtparam=pwr_led_activelow=off
}}

See Also: http://www.armadeus.com/wiki/index.php?title=GPIO_LEDS

=== Mounting {{code|/var/log}} as tmpfs ===

Append to the {{code|/etc/fstab}} with the following line.
tmpfs /var/log tmpfs nodev,nosuid,mode=0755,size=50m 0 0

This will mount {{code|/var/log}} as a 50MB ramdisk. If your system is using {{code|systemd}}, this will break {{code|systemd-journald}}. To fix it, you will need to [[Systemd|create a startup script]] after the mount has completed that creates the {{code|journald}}'s directory in {{code|/var/log/journal/}}.

Reboot the Pi for the changes to take affect, or run {{code|mount -a}} which will mount the ramdisk to /var/log immediately, though you'll need to restart any services that has handles to any files there.

Why would you want to do this? To limit the amount of writes that is made to the SD card to prevent premature wearing.

=== UART Serial ===
By default, ArchLinux on the Raspberry Pi will start a getty on the UART serial port. To make use of the port, you will have to disable the getty first.

Edit {{code|/boot/cmdline.txt}} and remove all instances of {{code|ttyAMA0}}. Mine ended up looking like:
{{highlight|lang=text|code=
root=/dev/mmcblk0p2 rw rootwait console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 elevator=noop
}}

Then, run: {{highlight|lang=terminal|code=
systemctl disable serial-getty@ttyAMA0.service
}}

Reboot.

If everything is working, you should be able to talk with {{code|/dev/ttyAMA0}}.

{{highlight|lang=terminal|code=
# stty < /dev/ttyAMA0
speed 9600 baud; line = 0;
kill = ^H; min = 100; time = 2;
-icrnl -imaxbel
-opost -onlcr
-isig -icanon -echo

# cat /dev/ttyAMA0 &
# echo hello > /dev/ttyAMA0
}}

[[Category:Linux]]

Raspberry Pi

2017-02-27T23:36:49Z

136.159.16.240: /* Setup */

== Setup ==
=== Arch Linux ===
Setup the SD card to contain two partitions using fdisk:
# 100MB (W95 FAT32 (LBA))
# Data

Download ArchLinux's Raspberry Pi tarball.
* Raspberry Pi: http://archlinuxarm.org/os/ArchLinuxARM-rpi-latest.tar.gz
* Raspberry Pi 2: http://archlinuxarm.org/os/ArchLinuxARM-rpi-2-latest.tar.gz

{{highlight|lang=terminal|code=
# fdisk /dev/sdcard
## Set up the SD card partitions
## Commands are: o, n, p, [enter], +100M, t, c, n, p, 2, [enter], [enter], w
# mkfs.vfat /dev/sdcard1
# mkfs.ext4 /dev/sdcard2
# cd /mnt
# mkdir root root/boot
# mount /dev/sdcard2 root
# mount /dev/sdcard1 root/boot
# tar -xpf ArchLinuxARM-rpi-latest.tar.gz -C root
# umount root/boot root
}}

For more information and to see the latest images see:
* http://archlinuxarm.org/platforms/armv6/raspberry-pi
* http://archlinuxarm.org/platforms/armv7/broadcom/raspberry-pi-2

== Configuration ==
=== Wifi ===
See [[Wifi]].

== Miscellaneous ==
=== Control Status LEDs ===
The Raspberry Pi 2 LEDs are driven by the kernel's led-GPIO drivers. This allows for the LEDs to be controlled by software rather than hardware as is the case with the older first generation Pi's. The two LEDs on the Raspberry Pi 2 are the green status light (led0) and the red power light (led1).

To see the available triggers that are in use and available for a particular LED:
{{highlight|lang=terminal|code=
# cat /sys/class/leds/led1/trigger
none usb-gadget usb-host [mmc0] timer oneshot heartbeat backlight gpio cpu0 cpu1 cpu2 cpu3 default-on transient flash torch input
}}

The active trigger is in {{code|[ ]}} and can be changed by writing to the file. For example, to turn off the LED entirely:
{{highlight|lang=terminal|code=
# echo none > /sys/class/leds/led1/trigger
# cat /sys/class/leds/led1/trigger
[none] usb-gadget usb-host mmc0 timer oneshot heartbeat backlight gpio cpu0 cpu1 cpu2 cpu3 default-on transient flash torch input
}}

You may also edit the {{code|config.txt}} file to change the behavior on startup.
{{highlight|lang=text|code=
# Disable the ACT LED.
dtparam=act_led_trigger=none
dtparam=act_led_activelow=off

# Disable the PWR LED.
dtparam=pwr_led_trigger=none
dtparam=pwr_led_activelow=off
}}

See Also: http://www.armadeus.com/wiki/index.php?title=GPIO_LEDS

=== Mounting {{code|/var/log}} as tmpfs ===

Append to the {{code|/etc/fstab}} with the following line.
tmpfs /var/log tmpfs nodev,nosuid,mode=0755,size=50m 0 0

This will mount {{code|/var/log}} as a 50MB ramdisk. If your system is using {{code|systemd}}, this will break {{code|systemd-journald}}. To fix it, you will need to [[Systemd|create a startup script]] after the mount has completed that creates the {{code|journald}}'s directory in {{code|/var/log/journal/}}.

Reboot the Pi for the changes to take affect, or run {{code|mount -a}} which will mount the ramdisk to /var/log immediately, though you'll need to restart any services that has handles to any files there.

Why would you want to do this? To limit the amount of writes that is made to the SD card to prevent premature wearing.

=== UART Serial ===
By default, ArchLinux on the Raspberry Pi will start a getty on the UART serial port. To make use of the port, you will have to disable the getty first.

Edit {{code|/boot/cmdline.txt}} and remove all instances of {{code|ttyAMA0}}. Mine ended up looking like:
{{highlight|lang=text|code=
root=/dev/mmcblk0p2 rw rootwait console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 elevator=noop
}}

Then, run: {{highlight|lang=terminal|code=
systemctl disable serial-getty@ttyAMA0.service
}}

Reboot.

If everything is working, you should be able to talk with {{code|/dev/ttyAMA0}}.

{{highlight|lang=terminal|code=
# stty < /dev/ttyAMA0
speed 9600 baud; line = 0;
kill = ^H; min = 100; time = 2;
-icrnl -imaxbel
-opost -onlcr
-isig -icanon -echo

# cat /dev/ttyAMA0 &
# echo hello > /dev/ttyAMA0
}}

[[Category:Linux]]

VMware ESXi

2017-02-17T20:00:32Z

136.159.16.240: /* Updating */

== Updating ==
=== 6.0 to 6.5 ===
Download the offline depot package and apply the update:
{{highlight|lang=terminal|code=
# esxcli software profile update -p ESXi-6.5.0-4564106-standard -d /vmfs/volumes/vol/VMware-ESXi-6.5.0-4564106-depot.zip
}}

This package requires a subscription. If you're using the free license, either get the evaluation or install the update by booting with the ISO image.

=== 5.5 to 6.0 ===
To update a ESXi install from 5.5 to 6.0, download the ESXi 6.0 offline bundle and upload it to a datastore on the server.

Log in via SSH and execute
{{highlight|lang=terminal|code=
# esxcli software vib update -d /vmfs/volumes/datastore1/ESXi600-201504001.zip
}}

Then reboot to apply the changes.

See Also:
* http://www.vladan.fr/patch-esxi-5-5-to-esxi-6-0/

== Troubleshooting ==
=== IOMMU Hangs ===
If your ESXi server hangs while "Initializing IOV", disable IOMMU by appending 'noIOMMU' to the kernel immediately after the new kernel boots by hitting Shift-O (letter O, not zero)

To make the changes persistent, add it to the boot arguments in <code>/bootbank/boot.cfg</code>

See Also:
* https://communities.vmware.com/message/2354177

VMware ESXi

2017-02-17T19:37:24Z

136.159.16.240: /* Updating */

== Updating ==
=== 6.0 to 6.5 ===

{{highlight|lang=terminal|code=
# esxcli software profile update -p ESXi-6.5.0-4564106-standard -d VMware-ESXi-6.5.0-4564106-depot.zip
}}

=== 5.5 to 6.0 ===
To update a ESXi install from 5.5 to 6.0, download the ESXi 6.0 offline bundle and upload it to a datastore on the server.

Log in via SSH and execute
{{highlight|lang=terminal|code=
# esxcli software vib update -d /vmfs/volumes/datastore1/ESXi600-201504001.zip
}}

Then reboot to apply the changes.

See Also:
* http://www.vladan.fr/patch-esxi-5-5-to-esxi-6-0/

== Troubleshooting ==
=== IOMMU Hangs ===
If your ESXi server hangs while "Initializing IOV", disable IOMMU by appending 'noIOMMU' to the kernel immediately after the new kernel boots by hitting Shift-O (letter O, not zero)

To make the changes persistent, add it to the boot arguments in <code>/bootbank/boot.cfg</code>

See Also:
* https://communities.vmware.com/message/2354177

Ruby on Rails under cPanel

2017-02-15T23:53:42Z

136.159.16.240: /* Troubleshooting */

This guide will get a modern Ruby on Rails application working on a cPanel account without using cPanel's outdated ruby support.

== Overview ==
To get a Ruby on Rails application running, we'll need to get a recent version of ruby installed.

cPanel officially supports ruby version {{code|1.8.7}} and rails version {{code|2.3.18}}. This guide will install ruby {{code|2.2.0}} and rails {{code|4.2.5}} using RVM.

== Setup ==
Install [[Ruby|Ruby using RVM]].

As root, install all the prerequsites.
{{highlight|lang=terminal|code=
# yum install gcc-c++ patch readline readline-devel zlib zlib-devel libyaml-devel libffi-devel openssl-devel make bzip2 autoconf automake libtool bison iconv-devel sqlite-devel
}}

As the user running the website, install ruby and rails.
{{highlight|lang=terminal|code=
# curl -L get.rvm.io {{!}} bash -s stable --ruby
# rvm install 2.2.0
# source ~/.rvm/scripts/rvm
# gem install rails
}}

At this point, you should have ruby and rails installed under your {{code|~/.rvm}} directory.
{{highlight|lang=terminal|code=
# which ruby
/home/net/.rvm/rubies/ruby-2.0.0-p643/bin/ruby
# which rails
/home/net/.rvm/gems/ruby-2.0.0-p643/bin/rails
# ruby --version
ruby 2.0.0p643 (2015-02-25 revision 49749) [x86_64-linux]
# rails --version
Rails 4.2.5
}}

You may need to install additional gems depending on the rails application you're trying to run.
{{highlight|lang=terminal|code=
# cd $rails_application
# bundle install
}}

If everything went smoothly, you should now be able to start the rails application.
{{highlight|lang=terminal|code=
# cd $rails_application
# rails s
}}

Ensure that your login profile sources the rvm script, or that your paths are set so that running ruby or rails runs the proper binary. If you want to invoke ruby in a shell script, you might need to adjust the {{code|PATH}} environment variable like so:

{{highlight|lang=bash|code=
export PATH=/home/fnet/.rvm/gems/ruby-2.0.0-p643/bin:/home/net/.rvm/gems/ruby-2.0.0-p643@global/bin:/home/net/.rvm/rubies/ruby-2.0.0-p643/bin:/home/net/.rvm/bin:$PATH
export GEM_PATH=/home/net/.rvm/gems/ruby-2.0.0-p643:/home/net/.rvm/gems/ruby-2.0.0-p643@global
export GEM_HOME=/home/net/.rvm/gems/ruby-2.0.0-p643
export RUBY_VERSION=ruby-2.0.0-p643
}}

== Website Rewrite ==
Your rails application should be running on a high port such as {{code|3000}}. In order for your main domain to serve the rails application on port {{code|80}}, you will need to create a {{code|.htaccess}} file with the following contents.

{{highlight|lang=text|code=
RewriteEngine on
RewriteRule ^(.*)$ http://127.0.0.1:3000/$1 [P,L]
}}

If you wish to serve the application in a sub directory, change the {{code|RewriteRule}} accordingly. Eg: To serve the site from {{code|/rails}}:

{{highlight|lang=text|code=
RewriteEngine on
RewriteRule ^rails\/(.*)$ http://127.0.0.1:3000/$1 [P,L]
}}

== Starting the Application Automatically ==
A quick and dirty solution is to make use of a cronjob to start the website automatically in case the server goes down.

Create a script with the following:
{{highlight|lang=bash|code=
#!/bin/bash

ps ux {{!}} grep -v grep {{!}} grep -q ruby {{!}}{{!}} screen -S railsapp -dm rails s
}}

Set the script to execute every minute.

== Troubleshooting ==
=== Installing Rails Hangs ===
When installing rails on version {{code|2.2.3}} of ruby, gem will hang on the line {{code|installing ri documentation for rail}}. Ruby will use up 100% of the CPU while doing nothing. The same thing happens when running {{code|gems install rails --no-ri --no-rdoc}}.

This was fixed by using an older version of ruby ({{code|2.0}} worked for me}}.

=== No route matches [GET] "/index.html.var" ===
When using Apache 2.4 and the solution above, you may get an error on the main page:

No route matches [GET] "/index.html.var"

This was fixed by adding this line to the {{code|.htaccess}} file:

DirectoryIndex disabled

[[Category:Coding]]
[[Category:Linux]]

PHP

2016-11-04T20:25:31Z

136.159.16.240: /* Installation */

PHP is a server-side scripting library.

== Installation ==

The instructions here will compile the latest version of PHP as an apache module for a prepackaged apache installation under a RedHat based system (such as CentOS, Fedora, ScientificLinux). The steps below will make use of {{code|apxs2}} from the {{code|http-tools}} package. If you wish to install PHP with suPHP, see [[suPHP]].

{{highlight|lang=terminal|code=
## Install rpmforge repo
# wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm
# rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt
# rpm -K rpmforge-release-0.5.2-2.el6.rf.*.rpm
# rpm -i rpmforge-release-0.5.2-2.el6.rf.*.rpm

## Install all prerequisites.
# yum -y install make autoconf g++ gcc-c++ libtermcap-devel libgcc-c++ libtool gcc libpng-devel libjpeg-devel libxml1-devel libxml2-devel curl curl-devel libmcrypt libmcrypt-devel libtool-ltdl-devel libxml2.x86_64 libxml2-devel.x86_64 curl-devel.x86_64 openssl-devel httpd-devel

# Compile PHP
# Go to the PHP source directory, then run:
# ./configure --with-apxs2 --with-config-file-path=/etc --with-gd --enable-shmop --enable-ftp --enable-sockets --enable-exif --enable-zip --enable-sysvsem --enable-sysvsem --enable-sysvshm --with-jpeg-dir --with-png-dir --enable-mbstring --enable-embedded-mysqli=shared --with-curl --with-mcrypt --with-mysql --with-mysqli --with-openssl --with-zlib --with-pdo-mysql --with-libdir=lib64
}}

Add {{code|1=--with-libdir=lib64}} if you need to reference 64bit libraries. By default, configure will only search in /usr/lib rather than /usr/lib64.

Run <code>make</code> and <code>make install</code>. If you had enabled apache apxs2 above, then it should have enabled the PHP module in apache automatically in {{/etc/httpd/conf/httpd.conf}}. If that failed for whatever reason, you could create an included config at {{code|/etc/httpd/conf.d/php.conf}} with the following contents:

{{highlight|lang=apache|code=
#
# PHP is an HTML-embedded scripting language which attempts to make it
# easy for developers to write dynamically generated webpages.
#
<IfModule prefork.c>
LoadModule php5_module modules/libphp5.so
# Of if you use PHP 7, use: LoadModule php7_module modules/libphp7.so
</IfModule>
<IfModule worker.c>
LoadModule php5_module modules/libphp5-zts.so
</IfModule>

# Cause the PHP interpreter to handle files with a .php extension.

AddHandler php5-script .php
AddType text/html .php

#
# Add index.php to the list of files that will be served as directory
# indexes.
#
DirectoryIndex index.php

#
# Uncomment the following line to allow PHP to pretty-print .phps
# files as PHP source code:
#
AddType application/x-httpd-php-source .phps

}}

=== Troubleshooting ===

==== PDOException : could not find driver ====
You need to have the pdo driver installed. In my case, I was trying to use the pdo-mysql connector which wasn't compiled with PHP. To fix this, install the PDO driver or compile it manually with:
{{highlight|lang=text|code=
--with-pdo-<driver>
}}
In my case, I needed mysql:
{{highlight|lang=text|code=
--with-pdo-mysql
}}

==== UTF-8 to hex ====
There is basically NO good way.

* http://www.tokyomuslim.com/2008/01/php-convert-utf-8-to-hex-codepoint-values-unicode-hexidecimal/
* http://hsivonen.iki.fi/php-utf8/

==== Error Reporting ====
{{highlight|lang=php|code=
// Turn off all error reporting
error_reporting(0);

// Report simple running errors
error_reporting(E_ERROR {{!}} E_WARNING {{!}} E_PARSE);

// Reporting E_NOTICE can be good too (to report uninitialized
// variables or catch variable name misspellings ...)
error_reporting(E_ERROR {{!}} E_WARNING {{!}} E_PARSE {{!}} E_NOTICE);

// Report all errors except E_NOTICE
// This is the default value set in php.ini
error_reporting(E_ALL ^ E_NOTICE);

// Report all PHP errors (see changelog)
error_reporting(E_ALL);

// Report all PHP errors
error_reporting(-1);

// Same as error_reporting(E_ALL);
ini_set('error_reporting', E_ALL);
}}

[[Category:Linux]]
[[Category:Code]]

Udev Rules

2016-11-04T16:37:41Z

136.159.16.240: /* Creating New udev rules */

<code>udev</code> is a device manager for the Linux kernel and handles device nodes in <code>/dev</code>. Rules can be defined which governs how these device nodes are created and what attributes are set.

== Creating New <code>udev</code> rules ==

Place new rules in <code>/etc/udev/rules.d</code>. The filename should be numbered.

If you are attempting to write a rule for a specific device, you should plug the device to your computer now and determine what the device path is. You must then list out all the udev properties of the device using the <code>udevadm</code> command.

To see attributes of a device, run:
{{code|1=udevadm info --attribute-walk --name=/dev/ttyUSB0}}

For example, to create a udev rule for a USB Webcam at <code>/etc/video0</code>:
<syntaxhighlight lang="text">
# udevadm info -a -p `udevadm info -q path -n /dev/video0`

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

looking at device '/devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0/video4linux/video0':
KERNEL=="video0"
SUBSYSTEM=="video4linux"
DRIVER==""
ATTR{debug}=="0"
ATTR{index}=="0"

looking at parent device '/devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3:1.0':
KERNELS=="1-1.3:1.0"
SUBSYSTEMS=="usb"
DRIVERS=="uvcvideo"
ATTRS{bInterfaceClass}=="0e"
ATTRS{iad_bFunctionClass}=="0e"
ATTRS{iad_bFirstInterface}=="00"
ATTRS{bInterfaceSubClass}=="01"
ATTRS{bInterfaceProtocol}=="00"
ATTRS{bNumEndpoints}=="01"
ATTRS{iad_bFunctionSubClass}=="03"
ATTRS{iad_bFunctionProtocol}=="00"
ATTRS{supports_autosuspend}=="1"
ATTRS{iad_bInterfaceCount}=="02"
ATTRS{bAlternateSetting}==" 0"
ATTRS{bInterfaceNumber}=="00"

looking at parent device '/devices/platform/bcm2708_usb/usb1/1-1/1-1.3':
KERNELS=="1-1.3"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="02"
ATTRS{bDeviceProtocol}=="01"
ATTRS{devpath}=="1.3"
ATTRS{idVendor}=="045e"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 4"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="6"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="500mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0100"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="38"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Microsoft"
ATTRS{removable}=="removable"
ATTRS{idProduct}=="0761"
ATTRS{bDeviceClass}=="ef"

looking at parent device '/devices/platform/bcm2708_usb/usb1/1-1':
KERNELS=="1-1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="02"
ATTRS{devpath}=="1"
ATTRS{idVendor}=="0424"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="2"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="2mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="3"
ATTRS{bcdDevice}=="0200"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="80"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="9512"
ATTRS{bDeviceClass}=="09"

looking at parent device '/devices/platform/bcm2708_usb/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="01"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="1"
ATTRS{bcdDevice}=="0318"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="bcm2708_usb"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="26"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.18.9-3-ARCH dwc_otg_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="DWC OTG Controller"

looking at parent device '/devices/platform/bcm2708_usb':
KERNELS=="bcm2708_usb"
SUBSYSTEMS=="platform"
DRIVERS=="dwc_otg"
ATTRS{hnp}=="HstNegScs = 0x0"
ATTRS{srp}=="SesReqScs = 0x1"
ATTRS{regvalue}=="invalid offset"
ATTRS{hsic_connect}=="HSIC Connect = 0x1"
ATTRS{guid}=="GUID = 0x2708a000"
ATTRS{mode}=="Mode = 0x1"
ATTRS{srpcapable}=="SRPCapable = 0x1"
ATTRS{regdump}=="Register Dump"
ATTRS{gpvndctl}=="GPVNDCTL = 0x00000000"
ATTRS{ggpio}=="GGPIO = 0x00000000"
ATTRS{hprt0}=="HPRT0 = 0x00001005"
ATTRS{wr_reg_test}=="Time to write GNPTXFSIZ reg 10000000 times: 670 msecs (67 jiffies)"
ATTRS{driver_override}=="(null)"
ATTRS{hcd_frrem}=="HCD Dump Frame Remaining"
ATTRS{mode_ch_tim_en}=="Mode Change Ready Timer Enable = 0x0"
ATTRS{gnptxfsiz}=="GNPTXFSIZ = 0x01000306"
ATTRS{remote_wakeup}=="Remote Wakeup Sig = 0 Enabled = 0 LPM Remote Wakeup = 0"
ATTRS{busconnected}=="Bus Connected = 0x1"
ATTRS{hcddump}=="HCD Dump"
ATTRS{gotgctl}=="GOTGCTL = 0x001c0001"
ATTRS{spramdump}=="SPRAM Dump"
ATTRS{grxfsiz}=="GRXFSIZ = 0x00000306"
ATTRS{gsnpsid}=="GSNPSID = 0x4f54280a"
ATTRS{gusbcfg}=="GUSBCFG = 0x00001700"
ATTRS{hptxfsiz}=="HPTXFSIZ = 0x02000406"
ATTRS{devspeed}=="Device Speed = 0x0"
ATTRS{fr_interval}=="Frame Interval = 0x1d4c"
ATTRS{rem_wakeup_pwrdn}==""
ATTRS{bussuspend}=="Bus Suspend = 0x0"
ATTRS{buspower}=="Bus Power = 0x1"
ATTRS{hnpcapable}=="HNPCapable = 0x1"
ATTRS{rd_reg_test}=="Time to read GNPTXFSIZ reg 10000000 times: 1510 msecs (151 jiffies)"
ATTRS{enumspeed}=="Device Enumeration Speed = 0x1"
ATTRS{inv_sel_hsic}=="Invert Select HSIC = 0x0"
ATTRS{regoffset}=="0xffffffff"

looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""
</syntaxhighlight>

In the udev rules file, match all attributes that uniquely identify the device you're targetting. In the example above, using the <code>SUBSYSTEM</code>, <code>ATTRS{idVendor}</code>, and <code>ATTRS{idProduct}</code> would be sufficient. Eg:
SUBSYSTEM=="video4linux", ATTRS{idVendor}=="045e"

In the second half of the line, you may define values for this device. If the webcam needs to be world read and writable, assign <code>0666</code> to <code>MODE</code> like so:
SUBSYSTEM=="video4linux", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="0761", MODE="0666"

Restart the udev daemon and check the logs for any errors. If the rules are correct, replugging the device should have have the affects defined in the rules.

== See Also ==
* http://hackaday.com/2009/09/18/how-to-write-udev-rules/

[[Category:Linux]]
{{Navbox Linux}}

Git

2016-01-19T19:42:47Z

136.159.16.240: /* Reverting Changes */

== Quick Use Guide ==
As someone who used SVN for the last decade, switching over to git was slightly confusing since the terminology is different. Hopefully, this usage guide will help.

=== Committing Files ===
A commit is like a snapshot and allows you to save the current state of the repository. Unlike in SVN where files are manually included/excluded when a commit is made, git allows files to be staged or unstaged prior to the commit being created. Staged files will always be added to the next commit made.

Typically, you will want to stage all files for commit which can be done by running:
{{Highlight|lang=bash|code=
git add -A .
}}

Run {{code|git status}} to see all files that are staged as well as any changed but unstaged files.
{{Highlight|lang=bash|code=
git status
}}

To commit all the staged files with a message:
{{Highlight|lang=bash|code=
git commit -m 'message'
}}

=== Reverting Changes ===
To revert all changes in the current repository, use:
{{highlight|lang=terminal|code=
## Fetch latest from remote
# git fetch --all
## Reset all changes fetched previously.
# git reset --hard HEAD
}}

To revert a specific file from a specific revision, use {{code|git checkout}}.
{{highlight|lang=terminal|code=
# git checkout <revision> <filename>
}}

=== Remote Origins ===
Git allows you to push/pull changes from other remote git repositories. Remote repositories can be in another path or hosted somewhere on the internet.

To see your repository's remotes:
{{Highlight|lang=bash|code=
git remote -v
}}

To add a new remote:
{{Highlight|lang=bash|code=
git remote add origin git@gitlab-blah:user/repo.git
}

To remove a remote:
{{Highlight|lang=bash|code=
git remote rm origin
}}

If your remote uses SSH, you will most likely need to configure SSH in order to make use of SSH key based authentication. You can read more about this at [[SSH Configuration File]], but the basic idea is to create a SSH configuration file at <code>~/.ssh/config</code> defining the remote's host.

<syntaxhighlight lang="text">
Host gitlab-remote
User git
HostName git.example.com
IdentityFile ~/.ssh/gitlab-remote
</syntaxhighlight>

==== Pushing / Pulling ====
After making a new change in your repository, you may want to push your changes out to other repositories. Do so by running:
{{Highlight|lang=bash|code=
git push
}}

You may also specify a specific remote and branch as well. Eg: {{code|git push remote-name branch-name}}.

Conversely, to retrieve changes from another repository, run
{{Highlight|lang=bash|code=
git pull
}}

[[Category:Linux]]

Ipset

2016-01-19T00:06:32Z

136.159.16.240: Created page with "You can use {{code|ipset}} to mass block a list of IP addresses with IPTables efficiently. == Usage & Configuration == Install the {{code|ipset}} package. In order to bloc..."

You can use {{code|ipset}} to mass block a list of IP addresses with IPTables efficiently.

== Usage & Configuration ==
Install the {{code|ipset}} package.

In order to block a list of IP addresses, create a new set hashed by the IP address that will contain all the banned IP addresses.
{{highlight|lang=terminal|code=
# ipset create banlist hash:ip hashsize 4096
# ipset list
Name: banlist
Type: hash:ip
Header: family inet hashsize 4096 maxelem 65536
Size in memory: 65656
References: 1
Members:
}}

Use the {{code|ipset add}} command to add IP addresses to the set.
{{highlight|lang=terminal|code=
# ipset add banlist 1.2.3.4
# ipset add banlist 1.2.3.4
ipset v6.11: Element cannot be added to the set: it's already added
}}

Duplicates will generate a warning. You can make {{code|ipset}} silently ignore duplicates this by passing the {{code|-exist}} flag.
{{highlight|lang=terminal|code=
# ipset -exist add banlist 1.2.3.4
}}

IPs can be removed by using the {{code|ipset remove}} command or wiped completely using the {{code|ipset flush}} command.

=== Integrating with IPTables ===
To make use of a {{code|ipset}} set created above, create a new IPTables rule that uses the {{code|set}} module. Eg:

{{highlight|lang=terminal|code=
$IPT -t mangle -N banned_ip_check
$IPT -t mangle -A banned_ip_check -m set --match-set banlist src -j banned_ip
$IPT -t mangle -A PREROUTING -j banned_ip_check
}}

In this case, we match source IP addresses to the {{code|ipset}} set named 'banlist'.

== See Also ==
* http://daemonkeeper.net/781/mass-blocking-ip-addresses-with-ipset/

[[Category:Linux]]

Gnome

2016-01-12T18:16:56Z

136.159.16.240: /* Screensaver Timeout */

== GSettings ==
The {{code|gsettings}} utility provides a way to get to GSettings which is more or less like a Windows registry containing key value pairs.

GSetting values are different for each user. To modify or view values for a different user, launch a dbus session as the user via {{code|sudo}}:
{{highlight|lang=terminal|code=
# sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively
}}

== Screensaver Timeout ==
The amount of idle time before the screensaver starts is set using:

{{highlight|lang=text|code=
# gsettings get org.gnome.desktop.session idle-delay
uint32 60
# gsettings set org.gnome.desktop.session idle-delay 3600
}}

The amount of time before the screen is locked is set:

{{highlight|lang=text|code=
## Instantly locks when the screensaver starts
# gsettings set org.gnome.desktop.screensaver lock-delay 0
## Or a delay in seconds. Eg: 1 minute
# gsettings set org.gnome.desktop.screensaver lock-delay 60
}}

== See Also ==
* http://blog.tordeu.com/?p=292
* http://superuser.com/questions/727120/make-gnome-screen-lock-after-1-hour-not-15-minutes

[[Category:Linux]]

VMware ESXi

2015-08-28T21:19:47Z

136.159.16.240:

== Updating ==
To update a ESXi install from 5.5 to 6.0, download the ESXi 6.0 offline bundle and upload it to a datastore on the server.

Log in via SSH and execute
esxcli software vib update -d /vmfs/volumes/datastore1/ESXi600-201504001.zip

Then reboot to apply the changes.

See Also:
* http://www.vladan.fr/patch-esxi-5-5-to-esxi-6-0/

== Troubleshooting ==
=== IOMMU Hangs ===
If your ESXi server hangs while "Initializing IOV", disable IOMMU by appending 'noIOMMU' to the kernel immediately after the new kernel boots by hitting Shift-O (letter O, not zero)

To make the changes persistent, add it to the boot arguments in <code>/bootbank/boot.cfg</code>

See Also:
* https://communities.vmware.com/message/2354177

VMware ESXi

2015-08-28T21:18:54Z

136.159.16.240:

== Updating ==
To update a ESXi install from 5.5 to 6.0, download the ESXi 6.0 offline bundle and upload it to a datastore on the server.

Log in via SSH and execute
esxcli software vib update -d /vmfs/volumes/datastore1/ESXi600-201504001.zip

Then reboot to apply the changes.

== Troubleshooting ==
=== IOMMU Hangs ===
If your ESXi server hangs while "Initializing IOV", disable IOMMU by appending 'noIOMMU' to the kernel immediately after the new kernel boots by hitting Shift-O (letter O, not zero)

To make the changes persistent, add it to the boot arguments in <code>/bootbank/boot.cfg</code>

See Also:
* https://communities.vmware.com/message/2354177

VMware ESXi

2015-08-28T21:18:17Z

136.159.16.240: Created page with " == Updating == To update a ESXi install from 5.5 to 6.0, download the ESXi 6.0 offline bundle and upload it to a datastore on the server. Log in via SSH and execute esxcli..."

== Updating ==
To update a ESXi install from 5.5 to 6.0, download the ESXi 6.0 offline bundle and upload it to a datastore on the server.

Log in via SSH and execute
esxcli software vib update -d /vmfs/volumes/datastore1/ESXi600-201504001.zip

Then reboot to apply the changes.

== Troubleshooting ==
=== IOMMU Hangs ===
If your ESXi server hangs while "Initializing IOV", disable IOMMU by appending 'noiommu' to the kernel immediately after the new kernel boots by hitting Shift-O (letter O, not zero)

To make the changes persistent, add it to the boot arguments in <code>/bootbank/boot.cfg</code>

Converting VMware ESXi Disk

2015-07-23T20:29:53Z

136.159.16.240: Created page with " Convert the disks to the ESXi format using: vmkfstools -i Workstation.vmdk Esxi.vmdk"

Convert the disks to the ESXi format using:
vmkfstools -i Workstation.vmdk Esxi.vmdk

Benchmark for APM X-Gene

2015-06-29T16:33:29Z

136.159.16.240:

{{Benchmark
| hardware = APM X-Gene
| cpu = APM X-Gene
| memory = 16 GB DDR3 EEC
| disk = 1x500 GB SATA
| os = Fedora 22 aarch64
| type = server
| score = 708.7
| raw =
========================================================================
BYTE UNIX Benchmarks (Version 5.1.3)

System: localhost.localdomain: GNU/Linux
OS: GNU/Linux -- 4.0.4-303.fc22.aarch64 -- #1 SMP Mon Jun 1 13:16:58 UTC 2015
Machine: aarch64 (aarch64)
Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8")
16:59:07 up 16 min, 2 users, load average: 0.09, 0.09, 0.07; runlevel 3

------------------------------------------------------------------------
Benchmark Run: Thu Jun 18 2015 16:59:07 - 17:27:03
0 CPUs in system; running 1 parallel copy of tests

Dhrystone 2 using register variables 17729811.6 lps (10.0 s, 7 samples)
Double-Precision Whetstone 2115.3 MWIPS (9.6 s, 7 samples)
Execl Throughput 2416.0 lps (29.9 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 394596.4 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 109161.3 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 1069966.8 KBps (30.0 s, 2 samples)
Pipe Throughput 792063.6 lps (10.0 s, 7 samples)
Pipe-based Context Switching 152173.7 lps (10.0 s, 7 samples)
Process Creation 5261.0 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 2384.2 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 426.0 lpm (60.1 s, 2 samples)
System Call Overhead 1497371.3 lps (10.0 s, 7 samples)

System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 17729811.6 1519.3
Double-Precision Whetstone 55.0 2115.3 384.6
Execl Throughput 43.0 2416.0 561.9
File Copy 1024 bufsize 2000 maxblocks 3960.0 394596.4 996.5
File Copy 256 bufsize 500 maxblocks 1655.0 109161.3 659.6
File Copy 4096 bufsize 8000 maxblocks 5800.0 1069966.8 1844.8
Pipe Throughput 12440.0 792063.6 636.7
Pipe-based Context Switching 4000.0 152173.7 380.4
Process Creation 126.0 5261.0 417.5
Shell Scripts (1 concurrent) 42.4 2384.2 562.3
Shell Scripts (8 concurrent) 6.0 426.0 709.9
System Call Overhead 15000.0 1497371.3 998.2
========
System Benchmarks Index Score 708.7
}}

The following benchmark was done on the original linux kernel that the box came with.
{{Benchmark
| hardware = APM X-Gene
| cpu = APM X-Gene
| memory = 16 GB DDR3 EEC
| disk = 1x500 GB SATA
| os = Fedora 22 aarch64
| type = server
| score = 926.9 / 3402.7
| raw =
========================================================================
BYTE UNIX Benchmarks (Version 5.1.3)

System: csa.cpsc.ucalgary.ca: GNU/Linux
OS: GNU/Linux -- 3.12.0-mustang_sw_1.12.09-beta -- #1 SMP Thu Jun 12 10:27:15 PDT 2014
Machine: aarch64 (aarch64)
Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8")
CPU 0: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 1: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 2: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 3: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 4: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 5: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 6: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 7: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

17:28:54 up 27 min, 3 users, load average: 1.39, 0.87, 0.61; runlevel 3

------------------------------------------------------------------------
Benchmark Run: Fri Jun 26 2015 17:28:54 - 17:56:56
8 CPUs in system; running 1 parallel copy of tests

Dhrystone 2 using register variables 17763947.5 lps (10.0 s, 7 samples)
Double-Precision Whetstone 2114.7 MWIPS (9.6 s, 7 samples)
Execl Throughput 2459.8 lps (29.9 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 468331.1 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 130247.8 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 1151363.8 KBps (30.0 s, 2 samples)
Pipe Throughput 1067484.4 lps (10.0 s, 7 samples)
Pipe-based Context Switching 192167.1 lps (10.0 s, 7 samples)
Process Creation 7660.0 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 4207.7 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 1634.0 lpm (60.0 s, 2 samples)
System Call Overhead 1438914.1 lps (10.0 s, 7 samples)

System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 17763947.5 1522.2
Double-Precision Whetstone 55.0 2114.7 384.5
Execl Throughput 43.0 2459.8 572.0
File Copy 1024 bufsize 2000 maxblocks 3960.0 468331.1 1182.7
File Copy 256 bufsize 500 maxblocks 1655.0 130247.8 787.0
File Copy 4096 bufsize 8000 maxblocks 5800.0 1151363.8 1985.1
Pipe Throughput 12440.0 1067484.4 858.1
Pipe-based Context Switching 4000.0 192167.1 480.4
Process Creation 126.0 7660.0 607.9
Shell Scripts (1 concurrent) 42.4 4207.7 992.4
Shell Scripts (8 concurrent) 6.0 1634.0 2723.3
System Call Overhead 15000.0 1438914.1 959.3
========
System Benchmarks Index Score 926.9

------------------------------------------------------------------------
Benchmark Run: Fri Jun 26 2015 17:56:56 - 18:25:05
8 CPUs in system; running 8 parallel copies of tests

Dhrystone 2 using register variables 141540380.6 lps (10.0 s, 7 samples)
Double-Precision Whetstone 16919.0 MWIPS (9.6 s, 7 samples)
Execl Throughput 13012.0 lps (29.8 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 579580.8 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 155434.8 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 1673229.9 KBps (30.0 s, 2 samples)
Pipe Throughput 8441190.9 lps (10.0 s, 7 samples)
Pipe-based Context Switching 1463165.9 lps (10.0 s, 7 samples)
Process Creation 32854.4 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 16740.8 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 2477.4 lpm (60.1 s, 2 samples)
System Call Overhead 7650246.7 lps (10.0 s, 7 samples)

System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 141540380.6 12128.6
Double-Precision Whetstone 55.0 16919.0 3076.2
Execl Throughput 43.0 13012.0 3026.1
File Copy 1024 bufsize 2000 maxblocks 3960.0 579580.8 1463.6
File Copy 256 bufsize 500 maxblocks 1655.0 155434.8 939.2
File Copy 4096 bufsize 8000 maxblocks 5800.0 1673229.9 2884.9
Pipe Throughput 12440.0 8441190.9 6785.5
Pipe-based Context Switching 4000.0 1463165.9 3657.9
Process Creation 126.0 32854.4 2607.5
Shell Scripts (1 concurrent) 42.4 16740.8 3948.3
Shell Scripts (8 concurrent) 6.0 2477.4 4128.9
System Call Overhead 15000.0 7650246.7 5100.2
========
System Benchmarks Index Score 3402.7
}}

== Other Information ==
This test was done only one one CPU.

<syntaxhighlight lang="text">

[root@localhost UnixBench]# free -m
total used free shared buff/cache available
Mem: 16257 180 15195 4 881 15951
Swap: 8191 0 8191
</syntaxhighlight>

Benchmark for APM X-Gene

2015-06-29T16:32:58Z

136.159.16.240:

{{Benchmark
| hardware = APM X-Gene
| cpu = APM SOC
| memory = 16 GB DDR3 EEC
| disk = 1x500 GB SATA
| os = Fedora 22 aarch64
| type = server
| score = 708.7
| raw =
========================================================================
BYTE UNIX Benchmarks (Version 5.1.3)

System: localhost.localdomain: GNU/Linux
OS: GNU/Linux -- 4.0.4-303.fc22.aarch64 -- #1 SMP Mon Jun 1 13:16:58 UTC 2015
Machine: aarch64 (aarch64)
Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8")
16:59:07 up 16 min, 2 users, load average: 0.09, 0.09, 0.07; runlevel 3

------------------------------------------------------------------------
Benchmark Run: Thu Jun 18 2015 16:59:07 - 17:27:03
0 CPUs in system; running 1 parallel copy of tests

Dhrystone 2 using register variables 17729811.6 lps (10.0 s, 7 samples)
Double-Precision Whetstone 2115.3 MWIPS (9.6 s, 7 samples)
Execl Throughput 2416.0 lps (29.9 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 394596.4 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 109161.3 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 1069966.8 KBps (30.0 s, 2 samples)
Pipe Throughput 792063.6 lps (10.0 s, 7 samples)
Pipe-based Context Switching 152173.7 lps (10.0 s, 7 samples)
Process Creation 5261.0 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 2384.2 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 426.0 lpm (60.1 s, 2 samples)
System Call Overhead 1497371.3 lps (10.0 s, 7 samples)

System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 17729811.6 1519.3
Double-Precision Whetstone 55.0 2115.3 384.6
Execl Throughput 43.0 2416.0 561.9
File Copy 1024 bufsize 2000 maxblocks 3960.0 394596.4 996.5
File Copy 256 bufsize 500 maxblocks 1655.0 109161.3 659.6
File Copy 4096 bufsize 8000 maxblocks 5800.0 1069966.8 1844.8
Pipe Throughput 12440.0 792063.6 636.7
Pipe-based Context Switching 4000.0 152173.7 380.4
Process Creation 126.0 5261.0 417.5
Shell Scripts (1 concurrent) 42.4 2384.2 562.3
Shell Scripts (8 concurrent) 6.0 426.0 709.9
System Call Overhead 15000.0 1497371.3 998.2
========
System Benchmarks Index Score 708.7
}}

The following benchmark was done on the original linux kernel that the box came with.
{{Benchmark
| hardware = APM X-Gene
| cpu = APM SOC
| memory = 16 GB DDR3 EEC
| disk = 1x500 GB SATA
| os = Fedora 22 aarch64
| type = server
| score = 926.9 / 3402.7
| raw =
========================================================================
BYTE UNIX Benchmarks (Version 5.1.3)

System: csa.cpsc.ucalgary.ca: GNU/Linux
OS: GNU/Linux -- 3.12.0-mustang_sw_1.12.09-beta -- #1 SMP Thu Jun 12 10:27:15 PDT 2014
Machine: aarch64 (aarch64)
Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8")
CPU 0: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 1: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 2: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 3: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 4: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 5: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 6: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

CPU 7: APM X-Gene Mustang board @ 2.40GHz (0.0 bogomips)

17:28:54 up 27 min, 3 users, load average: 1.39, 0.87, 0.61; runlevel 3

------------------------------------------------------------------------
Benchmark Run: Fri Jun 26 2015 17:28:54 - 17:56:56
8 CPUs in system; running 1 parallel copy of tests

Dhrystone 2 using register variables 17763947.5 lps (10.0 s, 7 samples)
Double-Precision Whetstone 2114.7 MWIPS (9.6 s, 7 samples)
Execl Throughput 2459.8 lps (29.9 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 468331.1 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 130247.8 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 1151363.8 KBps (30.0 s, 2 samples)
Pipe Throughput 1067484.4 lps (10.0 s, 7 samples)
Pipe-based Context Switching 192167.1 lps (10.0 s, 7 samples)
Process Creation 7660.0 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 4207.7 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 1634.0 lpm (60.0 s, 2 samples)
System Call Overhead 1438914.1 lps (10.0 s, 7 samples)

System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 17763947.5 1522.2
Double-Precision Whetstone 55.0 2114.7 384.5
Execl Throughput 43.0 2459.8 572.0
File Copy 1024 bufsize 2000 maxblocks 3960.0 468331.1 1182.7
File Copy 256 bufsize 500 maxblocks 1655.0 130247.8 787.0
File Copy 4096 bufsize 8000 maxblocks 5800.0 1151363.8 1985.1
Pipe Throughput 12440.0 1067484.4 858.1
Pipe-based Context Switching 4000.0 192167.1 480.4
Process Creation 126.0 7660.0 607.9
Shell Scripts (1 concurrent) 42.4 4207.7 992.4
Shell Scripts (8 concurrent) 6.0 1634.0 2723.3
System Call Overhead 15000.0 1438914.1 959.3
========
System Benchmarks Index Score 926.9

------------------------------------------------------------------------
Benchmark Run: Fri Jun 26 2015 17:56:56 - 18:25:05
8 CPUs in system; running 8 parallel copies of tests

Dhrystone 2 using register variables 141540380.6 lps (10.0 s, 7 samples)
Double-Precision Whetstone 16919.0 MWIPS (9.6 s, 7 samples)
Execl Throughput 13012.0 lps (29.8 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 579580.8 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 155434.8 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 1673229.9 KBps (30.0 s, 2 samples)
Pipe Throughput 8441190.9 lps (10.0 s, 7 samples)
Pipe-based Context Switching 1463165.9 lps (10.0 s, 7 samples)
Process Creation 32854.4 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 16740.8 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 2477.4 lpm (60.1 s, 2 samples)
System Call Overhead 7650246.7 lps (10.0 s, 7 samples)

System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 141540380.6 12128.6
Double-Precision Whetstone 55.0 16919.0 3076.2
Execl Throughput 43.0 13012.0 3026.1
File Copy 1024 bufsize 2000 maxblocks 3960.0 579580.8 1463.6
File Copy 256 bufsize 500 maxblocks 1655.0 155434.8 939.2
File Copy 4096 bufsize 8000 maxblocks 5800.0 1673229.9 2884.9
Pipe Throughput 12440.0 8441190.9 6785.5
Pipe-based Context Switching 4000.0 1463165.9 3657.9
Process Creation 126.0 32854.4 2607.5
Shell Scripts (1 concurrent) 42.4 16740.8 3948.3
Shell Scripts (8 concurrent) 6.0 2477.4 4128.9
System Call Overhead 15000.0 7650246.7 5100.2
========
System Benchmarks Index Score 3402.7
}}

== Other Information ==
This test was done only one one CPU.

<syntaxhighlight lang="text">

[root@localhost UnixBench]# free -m
total used free shared buff/cache available
Mem: 16257 180 15195 4 881 15951
Swap: 8191 0 8191
</syntaxhighlight>

Benchmark for APM X-Gene

2015-06-18T23:31:00Z

136.159.16.240: Created page with "{{Benchmark | hardware = APM X-Gene | cpu = APM SOC | memory = 16 GB DDR3 EEC | disk = 1x500 GB SATA | os = Fedora 22 aarch64 | type =..."

APM X-C1 (Mustang)

2015-06-18T20:58:17Z

136.159.16.240: /* Updating UEFI from U-Boot */

<syntaxhighlight lang="text">

U-Boot 2013.04-mustang_sw_1.12.09-beta (Jun 12 2014 - 10:48:45)

CPU0: APM ARM 64-bit Potenza Rev A3 2400MHz PCP 2400MHz
32 KB ICACHE, 32 KB DCACHE
SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz
Boot from SPI-NOR
Board: Mustang - AppliedMicro APM883208-xNA24SPT Reference Board
I2C: ready
DRAM: ECC 16 GiB @ 1600MHz
SF: Detected N25Q256 with page size 256 Bytes, total 32 MiB
MMC: X-Gene SD/SDIO/eMMC: 0
PCIE0: (RC) link down
In: serial
Out: serial
Err: serial
CPUs: 11111111
Net: eth0

</syntaxhighlight>

<syntaxhighlight lang="text">

Mustang# printenv
addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:off panic=1
addmisc=setenv bootargs ${bootargs} earlyprintk=uart8250-32bit,0x1c020000 debug maxcpus=${num_cores} swiotlb=65536
addtty=setenv bootargs ${bootargs} console=ttyS0,${baudrate}
baudrate=115200
bootcmd=run sata_self
bootdelay=5
bootfile=uImage
dnsip=10.66.18.10
enet=8
enet_mode=x:n
eth1addr=00:01:73:02:21:35
eth2addr=00:01:73:02:21:36
eth3addr=00:01:73:02:21:37
ethact=eth0
ethaddr=00:01:73:02:21:34
fdt_addr_f=0x1000000
fdt_addr_r=0x4003000000
fdt_file=apm-mustang.dtb
fdt_size=7285
flash_nfs=run nfsargs addip addtty addmisc; bootm ${kern_addr_f}
flash_self=run ramargs addip addtty addmisc; bootm ${kern_addr_f} ${ramdisk_addr_f} ${fdt_addr_f}
fw_addr_r=0x4003800000
gatewayip=10.66.19.1
hostname=dhcp-10-66-19-173
initrd_high=0x43e0000000
ipaddr=10.66.19.173
kern_addr_f=0x100000
kern_addr_r=0x4002000000
kern_size=a9a050
kernel_addr_r=0x4002000000
load=tftp ${uboot_addr_r} ${user_dir}/${u-boot}
load_fdt=tftp ${fdt_addr_r} ${user_dir}/${fdt_file}
load_kern=tftp ${kern_addr_r} ${user_dir}/${bootfile}
load_ramdisk=tftp ${ramdisk_addr_r} ${user_dir}/${ramdisk_file}
loadaddr=0x100000000
media_addr_r=0x4001000000
media_img=mustang_media.img
mgmt_enet=e
mslim_bootfile=uImage-mslim
mslim_fdt_addr_r=0x43f0600000
mslim_fdt_file=mslim-mustang.dtb
mslim_kern_addr_r=0x43f1000000
mslim_net_self=run net_load_mslim; startmslim
mslim_ramdisk_addr_r=0x43f2000000
mslim_ramdisk_file=uRamdisk-mslim
mslim_sd_self=run sd_load_mslim; startmslim
mslim_uboot_addr_r=0x43f0000000
mslim_uboot_file=u-boot-mslim.bin
mslim_user_dir=mslim
net_load_mslim=run nload_mslim_uboot nload_mslim_kern nload_mslim_ramdisk nload_mslim_fdt
net_nfs=run load_kern load_fdt; run nfsargs addip addtty addmisc; bootm ${kern_addr_r} - ${fdt_addr_r}
net_sata=run load_kern load_fdt; run sataargs addip addtty addmisc; bootm ${kern_addr_r} - ${fdt_addr_r}
net_self=run net_self_load; run ramargs addip addtty addmisc; bootm ${kern_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}
net_self_load=run load_kern load_ramdisk load_fdt
netdev=eth0
netmask=255.255.255.0
nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath}
nload_mslim_fdt=tftp ${mslim_fdt_addr_r} ${mslim_user_dir}/${mslim_fdt_file}
nload_mslim_kern=tftp ${mslim_kern_addr_r} ${mslim_user_dir}/${mslim_bootfile}
nload_mslim_ramdisk=tftp ${mslim_ramdisk_addr_r} ${mslim_user_dir}/${mslim_ramdisk_file}
nload_mslim_uboot=tftp ${mslim_uboot_addr_r} ${mslim_user_dir}/${mslim_uboot_file}
num_cores=8
pcie_gen=3:3:3:3:3
pcie_mode=RP:NA:NA:NA:NA
pcie_reset=y:n:n:n:n
pxefile_addr_r=0x4001000000
ram_nfs=run nfsargs addip addtty addmisc; bootm ${kern_addr_r} - ${fdt_addr_r}
ram_self=run ramargs addip addtty addmisc; bootm ${kern_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}
ramargs=setenv bootargs root=/dev/ram rw
ramdisk_addr_f=0x1100000
ramdisk_addr_r=0x4004000000
ramdisk_file=uRamdisk_basic
ramdisk_size=344abe
rgmii_phyid=3
rootpath=/opt/nfsrootfs/arm64/release
sata=0x3c
sata_enet=e:e:n:n
sata_load_fdt=ext4load scsi 0:1 0x4003000000 apm-mustang.dtb
sata_load_kern=ext4load scsi 0:1 0x4002000000 uImage
sata_self=scsi init; run sata_load_kern sata_load_fdt; run sataargs addip addtty addmisc; bootm 0x4002000000 - 0x4003000000
sataargs=setenv bootargs root=/dev/sda1 rw
script_addr_r=0x4004000000
sd_load_mslim=mmc dev 0; run sdload_mslim_uboot sdload_mslim_kern sdload_mslim_ramdisk sdload_mslim_fdt
sd_self=mmc dev 0; ext2load mmc 0 ${kern_addr_r} ${bootfile}; ext2load mmc 0 ${fdt_addr_r} ${fdt_file}; ext2load mmc 0 ${ramdisk_addr_r} ${ramdisk_file}; run ram_self
sdload_mslim_fdt=ext2load mmc 0 ${mslim_fdt_addr_r} ${mslim_fdt_file}
sdload_mslim_kern=ext2load mmc 0 ${mslim_kern_addr_r} ${mslim_bootfile}
sdload_mslim_ramdisk=ext2load mmc 0 ${mslim_ramdisk_addr_r} ${mslim_ramdisk_file}
sdload_mslim_uboot=ext2load mmc 0 ${mslim_uboot_addr_r} ${mslim_uboot_file}
sdphy=1
serverip=10.66.19.133
sgmii_phyid=4:5::
spi_fdt_upd=run load_fdt; setenv fdt_size ${filesize}; save; run update_fdt
spi_fw_img=mustang_slimpro_ext_spi.bin
spi_fw_load=tftp ${fw_addr_r} ${user_dir}/${spi_fw_img}
spi_fw_upd=run spi_fw_load;run spi_fw_update
spi_fw_update=bmc stop; i2c dev 1; eeprom write ${fw_addr_r} 0x0 ${filesize}
spi_kern_upd=run load_kern; setenv kern_size ${filesize}; save; run update_kern
spi_load=tftp ${media_addr_r} ${user_dir}/${media_img}
spi_ramdisk_upd=run load_ramdisk; setenv ramdisk_size ${filesize}; save; run update_ramdisk
spi_self=sf probe 0; sf read ${kern_addr_r} ${kern_addr_f} ${kern_size}; sf read ${fdt_addr_r} ${fdt_addr_f} ${fdt_size}; sf read ${ramdisk_addr_r} ${ramdisk_addr_f} ${ramdisk_size}; run ram_self
spi_upd=run spi_load;run spi_update
spi_update=sf probe 0; sf erase 0x0 ${filesize}; sf write ${media_addr_r} 0x0 ${filesize}
stderr=serial
stdin=serial
stdout=serial
u-boot=u-boot.bin
uboot_addr_f=0x8100000000
uboot_addr_r=0x4001000000
uboot_size=0x80000
upd=run load; setenv uboot_size ${filesize};run update
updall=run spi_kern_upd; run spi_ramdisk_upd; run spi_fdt_upd
update=protect off ${uboot_addr_f} +${uboot_size}; erase ${uboot_addr_f} +${uboot_size}; cp.b ${uboot_addr_r} ${uboot_addr_f} ${uboot_size}
update_fdt=sf probe 0; sf erase ${fdt_addr_f} ${filesize}; sf write ${fdt_addr_r} ${fdt_addr_f} ${filesize}
update_kern=sf probe 0; sf erase ${kern_addr_f} ${filesize}; sf write ${kern_addr_r} ${kern_addr_f} ${filesize}
update_ramdisk=sf probe 0; sf erase ${ramdisk_addr_f} ${filesize}; sf write ${ramdisk_addr_r} ${ramdisk_addr_f} ${filesize}
user_dir=/1.12.09-Beta/BUILDS/potenza
xgmii_phyid=:

Environment size: 5832/32764 bytes

</syntaxhighlight>

<syntaxhighlight lang="text">

POWERED BY:

X X GGGG
X X G G
X X G EEEEE N NNNN EEEEE
X ####### G GGG E E NN N E E
X X G G EEEEEEE N N EEEEEEE
X X G G E N N E
X X GGGGG EEEEE N N EEEEE (TM)

Welcome to Applied Micro X-Gene 64-bit ARM Server Platform

Applied Micro Linux 3.12.0-mustang_sw_1.12.09-beta (aarch64) (ttyS0)
dhcp-10-66-19-173 login: root
Password:
[root@dhcp-10-66-19-173 ~]# cat /proc/cpuinfo
Processor : AArch64 Processor rev 0 (aarch64)
processor : 0
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 1
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 2
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 3
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 4
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 5
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 6
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 7
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

Features : fp asimd
CPU implementer : 0x50
CPU architecture: AArch64
CPU variant : 0x0
CPU part : 0x000
CPU revision : 0

Hardware : APM X-Gene Mustang board

</syntaxhighlight>

== Updating UEFI from U-Boot ==
https://fedoraproject.org/wiki/Architectures/AArch64/Hardware/Mustang?rd=Architectures/ARM/AArch64/Mustang

<syntaxhighlight lang="text">

U-Boot 2013.04-mustang_sw_1.12.09-beta (Jun 12 2014 - 10:48:45)

CPU0: APM ARM 64-bit Potenza Rev A3 2400MHz PCP 2400MHz
32 KB ICACHE, 32 KB DCACHE
SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz
Boot from SPI-NOR
Board: Mustang - AppliedMicro APM883208-xNA24SPT Reference Board
I2C: ready
DRAM: ECC 16 GiB @ 1600MHz
SF: Detected N25Q256 with page size 256 Bytes, total 32 MiB
MMC: X-Gene SD/SDIO/eMMC: 0
PCIE0: (RC) link down
In: serial
Out: serial
Err: serial
CPUs: 11111111
Net: eth0
Hit any key to stop autoboot: 0
Mustang#
Mustang#
Mustang#
Mustang#
Mustang#
Mustang# setenv rh_sd_tiano_sec_ubt fatload mmc 0:1 0x1d000000 /mustang/mustang_tianocore_sec_ubt.fd
Mustang# setenv rh_sd_tiano_ubt fatload mmc 0:1 0x4002000000 /mustang/mustang_tianocore_ubt.fd
Mustang# setenv rh_run_tiano_ubt go 0x1d000000
Mustang# setenv bootcmd run rh_sd_tiano_ubt rh_sd_tiano_sec_ubt rh_run_tiano_ubt
Mustang# saveenv
Saving Environment to SPI Flash...
SF: Detected N25Q256 with page size 256 Bytes, total 32 MiB
.Erasing SPI flash.....SF: STMicro: Successfully erased 262144 bytes @ 0xc0000
Writing to SPI flash.......done
Mustang# reset
resetting ...
cold reset ...▒

U-Boot 2013.04-mustang_sw_1.12.09-beta (Jun 12 2014 - 10:48:45)

CPU0: APM ARM 64-bit Potenza Rev A3 2400MHz PCP 2400MHz
32 KB ICACHE, 32 KB DCACHE
SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz
Boot from SPI-NOR
Board: Mustang - AppliedMicro APM883208-xNA24SPT Reference Board
I2C: ready
DRAM: ECC 16 GiB @ 1600MHz
SF: Detected N25Q256 with page size 256 Bytes, total 32 MiB
MMC: X-Gene SD/SDIO/eMMC: 0
PCIE0: (RC) link down
In: serial
Out: serial
Err: serial
CPUs: 11111111
Net: eth0
Hit any key to stop autoboot: 0
Mustang# printenv bootcmd
bootcmd=run rh_sd_tiano_ubt rh_sd_tiano_sec_ubt rh_run_tiano_ubt
Mustang# printenv rh_
## Error: "rh_" not defined
Mustang# printenv rh_sd_tiano_ubt
rh_sd_tiano_ubt=fatload mmc 0:1 0x4002000000 /mustang/mustang_tianocore_ubt.fd
Mustang# reset
resetting ...
cold reset ...▒

U-Boot 2013.04-mustang_sw_1.12.09-beta (Jun 12 2014 - 10:48:45)

CPU0: APM ARM 64-bit Potenza Rev A3 2400MHz PCP 2400MHz
32 KB ICACHE, 32 KB DCACHE
SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz
Boot from SPI-NOR
Board: Mustang - AppliedMicro APM883208-xNA24SPT Reference Board
I2C: ready
DRAM: ECC 16 GiB @ 1600MHz
SF: Detected N25Q256 with page size 256 Bytes, total 32 MiB
MMC: X-Gene SD/SDIO/eMMC: 0
PCIE0: (RC) link down
In: serial
Out: serial
Err: serial
CPUs: 11111111
Net: eth0
Hit any key to stop autoboot: 0
Mustang# run rh_sd_tiano_ubt rh_sd_tiano_sec_ubt rh_run_tiano_ubt
reading /mustang/mustang_tianocore_ubt.fd
1835008 bytes read in 1426 ms (1.2 MiB/s)
reading /mustang/mustang_tianocore_sec_ubt.fd
262144 bytes read in 1295 ms (197.3 KiB/s)
## Starting application at 0x1D000000 ...
X-Gene Mustang Board
Boot firmware (version 1.1.0 built at 12:03:43 on Mar 23 2015)
PROGRESS CODE: V3020003 I0
PROGRESS CODE: V3020002 I0
PROGRESS CODE: V3020003 I0
PROGRESS CODE: V3020002 I0
PROGRESS CODE: V3020003 I0
PROGRESS CODE: V3020002 I0
PROGRESS CODE: V3020003 I0
PROGRESS CODE: V3021001 I0
TianoCore 1.1.0 UEFI 2.4.0 Mar 23 2015 12:03:18
CPU: APM ARM 64-bit Potenza Rev A3 2400MHz PCP 2400MHz
32 KB ICACHE, 32 KB DCACHE
SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz
Board: X-Gene Mustang Board
Slimpro FW:
Ver: 2.1
The default boot selection will start in 1 second
Attempting PXE boot on MAC: 00:11:22:33:44:55
..Attempting PXE boot on MAC: 00:11:22:33:44:55
.

</syntaxhighlight>

<syntaxhighlight lang="text">
TianoCore 1.1.0 UEFI 2.4.0 Mar 23 2015 12:03:18
CPU: APM ARM 64-bit Potenza Rev A3 2400MHz PCP 2400MHz
32 KB ICACHE, 32 KB DCACHE
SOC 2000MHz IOBAXI 400MHz AXI 250MHz AHB 200MHz GFC 125MHz
Board: X-Gene Mustang Board
Slimpro FW:
Ver: 2.1
The default boot selection will start in 4 seconds
[1] Shell
[2] Boot Manager
[3] Reboot
[4] Shutdown
Start:
</syntaxhighlight>
Hit 1 for the shell

<syntaxhighlight lang="text">
UEFI Interactive Shell v2.0
EDK II
UEFI v2.40 (X-Gene Mustang Board EFI Mar 23 2015 12:04:07, 0x00000000)
Mapping table
FS0: Alias(s):HD13b:;BLK5:
VenHw(B225ED30-6DFD-43A9-BF6B-5753358F2F70)/HD(1,MBR,0x000F06A6,0x800,0x400000)
BLK3: Alias(s):
VenHw(6C9CEEF0-A406-11E3-A5E2-0800200C9A66)
BLK2: Alias(s):
VenHw(02118005-9DA7-443A-92D5-781F022AEDBB)
BLK6: Alias(s):
VenHw(F40A3869-92C4-4275-8501-4491A1A20C19)
BLK4: Alias(s):
VenHw(B225ED30-6DFD-43A9-BF6B-5753358F2F70)
BLK0: Alias(s):
PciRoot(0x6)/Pci(0x0,0x0)/Sata(0x0,0x0,0x0)
BLK1: Alias(s):
PciRoot(0x6)/Pci(0x0,0x0)/Sata(0x0,0x0,0x0)/HD(1,MBR,0xC63EB28B,0x800,0x3A385830)

</syntaxhighlight>

APM X-C1 (Mustang)

2015-06-18T20:16:18Z

136.159.16.240:

APM X-C1 (Mustang)

2015-06-17T23:33:20Z

136.159.16.240:

APM X-C1 (Mustang)

2015-06-17T23:28:29Z

136.159.16.240:

APM X-C1 (Mustang)

2015-06-17T23:26:20Z

136.159.16.240: Created page with " <syntaxhighlight lang="text"> POWERED BY: X X GGGG X X G G X X G EEEEE N NNNN EEEEE..."

<syntaxhighlight lang="text">

POWERED BY:

X X GGGG
X X G G
X X G EEEEE N NNNN EEEEE
X ####### G GGG E E NN N E E
X X G G EEEEEEE N N EEEEEEE
X X G G E N N E
X X GGGGG EEEEE N N EEEEE (TM)

Welcome to Applied Micro X-Gene 64-bit ARM Server Platform

Applied Micro Linux 3.12.0-mustang_sw_1.12.09-beta (aarch64) (ttyS0)
dhcp-10-66-19-173 login: root
Password:
[root@dhcp-10-66-19-173 ~]# cat /proc/cpuinfo
Processor : AArch64 Processor rev 0 (aarch64)
processor : 0
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 1
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 2
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 3
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 4
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 5
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 6
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

processor : 7
model name : APM X-Gene Mustang board @ 2.40GHz
cpu MHz : 2400.00
fpu : yes

Features : fp asimd
CPU implementer : 0x50
CPU architecture: AArch64
CPU variant : 0x0
CPU part : 0x000
CPU revision : 0

Hardware : APM X-Gene Mustang board

</syntaxhighlight>

Git

2015-06-04T19:21:23Z

136.159.16.240: Created page with " == Quick Use Guide == === Adding/Removing remote origin === git remote add origin git@gitlab-blah:user/repo.git git remote remove origin To use public key authentication w..."

== Quick Use Guide ==
=== Adding/Removing remote origin ===
git remote add origin git@gitlab-blah:user/repo.git
git remote remove origin

To use public key authentication with SSH, you must configure it inside <code>~/.ssh/config</code> instead of passing the key as you would with SSH (ie: <code>ssh -i ~/.ssh/privkey</code>) like so:

<syntaxhighlight lang="text">
Host gitlab-blah
HostName gitlab.cpsc.ucalgary.ca
User git
IdentityFile ~/.ssh/gitlab-leo
</syntaxhighlight>

=== Pushing to remote origin ===
git push origin '''branch'''
Where branch can be the master.

=== Committing Files ===
Ensure all files you want to commit are staged. To add all files:
git add -A .

See the status with:
git status

To commit:
git commit -m 'message'

=== Reverting Changes ===
To revert any changes in the current repository, use (???)
git reset

[[Category:Linux]]

Main Page

2015-05-20T16:54:18Z

136.159.16.240:

[[Special:Search|Search]] | [[Special:Upload|Upload]] | [[Special:Version|Version]]

== Linux ==
{{Navbox Linux}}

== Benchmarks ==
{{Navbox Benchmarks}}

== Others ==
Categories
* [[:Category:C-Sharp|C#]]
* [[:Category:FreeBSD|FreeBSD]]
* [[:Category:Solaris|Solaris]]
* [[:Category:VMWare ESXi|VMWare ESXi]]
* [[:Category:TipsnTricks|Tips & Tricks]]
* [[:Category:Services|Services]]
* [[:Category:Code|Code]]
* [[:Category:Guides|Guides]]
* [[:Category:Todo|Todo]]

Topics
* [[Cheat Sheet]]
* [[Troubleshoot]]
* [[ZFS]]
* [[BSD Jails]]
* [[Dying SSD]]
* [[Cobbler]]
* [[Salt]]
* [[Cdist]]
* [[Mail Server]]
* [[tcsh]]
* [[Elevator]]

Personal
* [[Recipes]]
* [[Shopping List]]

Other Sites
* [http://iplocation.truevue.org/ IP Lookup]

* http://sipb.mit.edu/doc/safe-shell/
* http://blog.kihltech.com/
* http://tech.superhappykittymeow.com/
* http://info.michael-simons.eu
* http://crashmag.net
* http://mywiki.wooledge.org/BashFAQ
* http://www.iptables.info/en/structure-of-iptables.html

Pirate Drops
* fredkodongo.ananke.feralhosting.com/index.html/
** ~200mbit. Some games and TV
* abdullah.stack.seedhost.eu/abdullah/downloads/?C=M;O=A
* ukuthemba.seedstuff.ca/?C=M;O=A
* dl.eveilmusical.ovh/Complete/?C=M;O=A
* beckwreck.hermes.feralhosting.com/links/deluge_data/

To find more, search:
inurl:feralhosting.com intitle:"Index of"
inurl:seedhost.eu intitle:"Index of"

* https://herbertmusoke.com

Not updated:
* instance.hypnos.feralhosting.com/data
** random stuff
* djoendi.co.vu/dunlud/
** games
* ks3352402.kimsufi.com/dl
* https://lsd-25.ru/uploads

* hxxp://ks3352402.kimsufi.com/dl/ ~70mbit, some movies, some tv, french
* hxxp://box.bob.sh/ misc stuff
* hxxp://blogs.hatrix.fr/download HD TV, french
* hxxp://87.252.164.6/Mof/ low quality TV
* hxxp://nivaldia.fr/torrent/Complete/Cloud%20Atlas/ - french stuff. tvs and movies.
* hxxp://metaldiamond.tk/private/Jeux/ some games, french stuff.

* dl.imontou.ch
** Alles auf Deutsch: TV, Movies, Games

* hxxp://xcloud.thib0704.net/thib/downloads some games, tv, movies
* hxxp://home.alexsoft-bg.com:8080/download/ misc

php fcgi
* http://blog.giantchipmunk.com/2011/01/setting-up-php-with-fastcgi-and-suexec.html

ACL

2015-04-30T18:49:57Z

136.159.16.240:

== Linux ==

To get ACL permissions

<syntaxhighlight lang="bash" line start="1" enclose="div">
getfacl
</syntaxhighlight>

To set ACL permissions for a user:
<syntaxhighlight lang="bash" line start="1" enclose="div">
setfacl -m user:<user>:<perms> <path>

# eg:
setfacl -m user:leo:wrx /home/leo

# To do this recursively, pass the <code>-R</code> flag.
setfacl -mR user:leo:wrx /home/leo
</syntaxhighlight>

To remove ACL permissions for a user:
<syntaxhighlight lang="bash" line start="1" enclose="div">
setfacl -x user:leo /home/leo
</syntaxhighlight>

To clone ACL permissions from fileA to fileB:
<syntaxhighlight lang="bash" line start="1" enclose="div">
getfacl fileA | setfacl -bnM - fileB
</syntaxhighlight>

[[Category:Linux]]

Cisco

2015-04-13T18:05:09Z

136.159.16.240: Created page with " == Show Switchport == sola# '''config''' Enter configuration commands, one per line. End with CNTL/Z. sola(config)# '''interface ethernet 3/28''' sola(config-if)# '''sho..."

== Show Switchport ==
sola# '''config'''
Enter configuration commands, one per line. End with CNTL/Z.
sola(config)# '''interface ethernet 3/28'''
sola(config-if)# '''show interface ethernet 3/28 switchport'''
Name: Ethernet3/28
Switchport: Enabled
Switchport Monitor: Not enabled
Operational Mode: trunk
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Trunking VLANs Enabled: 1-12,14-3967,4048-4093
Administrative private-vlan primary host-association: none
Administrative private-vlan secondary host-association: none
Administrative private-vlan primary mapping: none
Administrative private-vlan secondary mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none

Getting Hardware UUID

2015-04-09T17:10:47Z

136.159.16.240: /* Linux / FreeBSD */

== Windows ==

You may get the UUID value from PowerShell.
get-wmiobject Win32_ComputerSystemProduct | Select-Object -ExpandProperty UUID

[[Category:Windows]]

== Linux / FreeBSD ==

Use the dmidecode utility to get the UUID
dmidecode -s system-uuid

You may need to install dmidecode since it usually isn't bundled with the base OS. On FreeBSD, it's available in ports at <code>/usr/ports/sysutils/dmidecode</code>.

[[Category:Linux]]
[[Category:FreeBSD]]

== VMWare ESXi ==

To get the UUID of the physical machine that your ESXi server is running on, login via SSH and run:

esxcfg-info |grep -i uuid

You will see a bunch of UUIDs, most of which pertain to disks/volumes. What you are looking for is:

|----System UUID..............................................5178962d-2fcf-df50-536d-000423d9985a

[[Category:VMWare ESXi]]

{{Navbox Linux}}

Awk

2015-04-08T19:06:35Z

136.159.16.240:

== Counting Lines Until Match ==

To print the number of lines before a match is found:
awk 'BEGIN { n = 0 } /PATTERN/ { print n; next } { n++ }'

Eg: Suppose I have a file with the contents:
leo
spoon
cake
fork

To find the number of lines up until 'cake', do:
cat list.txt | awk 'BEGIN { n = 0 } /cake/ { print n; next } { n++ }'

== Convert Number as Bytes to Human Readable Value ==
I wanted to sort size in reverse order, but in order to do that properly, the value from du needs to be in kilobytes. I also didn't want to run this through du again just to get the human readable value. So, I did this:

<syntaxhighlight lang="bash" line start="1" enclose="div">
du -s ./*/ ./*/*/ ./*/*/*/ \
| sort -rn \
| awk 'BEGIN { \
split("KB MB GB TB PB", type) \
} \
{ \
y = 0; \
x = $1; \
for (i = 4; y < 1 ; i--) \
y = x / (2 ** (10 * i)); \
print y type[i+2]" "$2 \
}'
</syntaxhighlight>

If you want to count using bytes instead of kilobytes, just add K to the split function and replace i=4 with i=5.

== Convert <code>ps</code> Elapsed Time to Seconds ==
To convert the elapsed time (in [http://pubs.opengroup.org/onlinepubs/009696799/utilities/ps.html POSIX locale] formatted as <code>[[dd-]hh:]mm:ss</code>) to seconds using awk:

<syntaxhighlight lang="bash">
Elapsed=`ps -p $Pid -o etime=`
Elapsed=`echo $Elapsed | tr - : | tr : ' '`
Seconds=`echo $Elapsed | awk '
NF == 2 { print ($1 * 60) + $2 }
NF == 3 { print ((($1 * 60) + $2) * 60) + $3 }
NF == 4 { print ((((($1 * 24) + $2) * 60) + $3) * 60) + $4 }
{}'`
echo $Seconds
</syntaxhighlight>

For example, a process running for <code>66-00:12:58</code> has been running for 5703178 seconds. The Awk command will match how many columns were found and then do the proper calculation.

== Get a Text Section ==
To grab a specific section from a .spec file (where sections begin with <code>%</code>):

<syntaxhighlight lang="bash">

if [ $# -ne 2 ] ; then
echo "Usage: $0 file.spec section"
exit
fi

Section="$2"

cat $1 | awk -v Section="$Section" '
BEGIN {
InSection=false
}
/^%.*/ {
if ($0 ~ Section) {
InSection=1
} else {
InSection=0
}

next
}
{
if (InSection) {
print $0
}
}

</syntaxhighlight>

[[Category:Linux]]
[[Category:TipsnTricks]]
[[Category:LinuxUtilities]]
{{Navbox Linux}}

Bash Scripting

2015-04-08T19:05:05Z

136.159.16.240: /* Indent */

== Common Functions ==
Here are some common functions I use in my scripts.

=== Prompt ===
You can prompt the user for an yes or no answer using this function. An optional default values are accepted as the second argument.

Example Usage:
<syntaxhighlight lang="bash">
if prompt "Is this okay?" Y ; then
echo "It's Okay!"
fi
if ! prompt "Is this okay?" N ; then
echo "It's not okay!"
fi
</syntaxhighlight>

Function:
<syntaxhighlight lang="bash">
function prompt() {
# credit: http://djm.me/ask
while true; do
if [ "${2:-}" = "Y" ]; then
prompt="Y/n"
default=Y
elif [ "${2:-}" = "N" ]; then
prompt="y/N"
default=N
else
prompt="y/n"
default=
fi

# Ask the question
read -p "$1 [$prompt] " REPLY

# Default?
if [ -z "$REPLY" ]; then
REPLY=$default
fi

# Check if the reply is valid
case "$REPLY" in
Y*|y*) return 0 ;;
N*|n*) return 1 ;;
esac
done
}
</syntaxhighlight>

=== die ===
Similar to the <code>die</code> command in PHP which prints out a message before stopping execution.

Function:
<syntaxhighlight lang="bash">
function die {
echo $@
exit
}
</syntaxhighlight>

The caveat is that exit will kill the current shell - if running in a subshell, this will terminate the subshell and not the parent shell. To get around this, you may need to kill the parent PID instead.

=== Indent ===
Indents text piped to the function.

Function:
<syntaxhighlight lang="bash">
function Indent {
Prepend="\t"

if [ $# -eq 1 ] ; then
Indent=$1

while [ $Indent -ge 0 ] ; do
Prepend="\t$Prepend"
Indent=$(($Indent - 1))
done
fi

IFS='' # To preserve any existing spacing.
while read i ; do echo -e "${Prepend}$i" ; done
}
</syntaxhighlight>

Usage:
<syntaxhighlight lang="bash">
echo "test" | Indent
test
echo "test" | Indent 2
test
</syntaxhighlight>

== Extracting / Parsing Filenames ==
Use the <code>basename</code> to extract filenames from a path and and <code>dirname</code> to extract the path of a filename.

Eg:
dirname /etc/hosts
/etc

basename /etc/hosts
hosts

To extract only the extension or the filename without the extension, use bash's string matching:
Filename=$(basename /etc/resolv.conf)
Ext="${Filename##*.}"
Name="${Filename%.*}"

== Arithmetic Operations ==
Do integer arithmetic operations on variables within double brackets. For example:
Value=1
ValuePlusOne=$((Value + 1))
ValueTimes12=$((Value * 12))

The operators that are supported are:
+ - / * %
Bitwise operators also work:
^ (XOR) | (OR) & (AND)

== Control Blocks ==
=== Switch ===
<syntaxhighlight lang="bash">
read -p "What do you want to do?: " Option

case "$Option" in
"K")
install_new_kernel
die "Complete!"
;;
"H")
usage
;;
*)
die "Stopping installation."
;;
esac
</syntaxhighlight>

== Snippets ==
=== Get First IP Address ===
ip a | /bin/grep inet | grep -v inet6 | tail -n+2 | head -n 1 | awk '{print $2}' | cut -d'/' -f1

[[Category:Linux]]
{{Navbox Linux}}

Bash Scripting

2015-04-08T18:56:53Z

136.159.16.240: /* Common Functions */

== Common Functions ==
Here are some common functions I use in my scripts.

=== Prompt ===
You can prompt the user for an yes or no answer using this function. An optional default values are accepted as the second argument.

Example Usage:
<syntaxhighlight lang="bash">
if prompt "Is this okay?" Y ; then
echo "It's Okay!"
fi
if ! prompt "Is this okay?" N ; then
echo "It's not okay!"
fi
</syntaxhighlight>

Function:
<syntaxhighlight lang="bash">
function prompt() {
# credit: http://djm.me/ask
while true; do
if [ "${2:-}" = "Y" ]; then
prompt="Y/n"
default=Y
elif [ "${2:-}" = "N" ]; then
prompt="y/N"
default=N
else
prompt="y/n"
default=
fi

# Ask the question
read -p "$1 [$prompt] " REPLY

# Default?
if [ -z "$REPLY" ]; then
REPLY=$default
fi

# Check if the reply is valid
case "$REPLY" in
Y*|y*) return 0 ;;
N*|n*) return 1 ;;
esac
done
}
</syntaxhighlight>

=== die ===
Similar to the <code>die</code> command in PHP which prints out a message before stopping execution.

Function:
<syntaxhighlight lang="bash">
function die {
echo $@
exit
}
</syntaxhighlight>

The caveat is that exit will kill the current shell - if running in a subshell, this will terminate the subshell and not the parent shell. To get around this, you may need to kill the parent PID instead.

=== Indent ===
Indents text piped to the function.

Function:
<syntaxhighlight lang="bash">
function Indent {
Prepend="\t"

if [ $# -eq 1 ] ; then
Indent=$1

while [ $Indent -ge 0 ] ; do
Prepend="\t$Prepend"
Indent=$(($Indent - 1))
done
fi

while read i ; do echo -e "${Prepend}$i" ; done
}
</syntaxhighlight>

Usage:
<syntaxhighlight lang="bash">
echo "test" | Indent
test
echo "test" | Indent 2
test
</syntaxhighlight>

== Extracting / Parsing Filenames ==
Use the <code>basename</code> to extract filenames from a path and and <code>dirname</code> to extract the path of a filename.

Eg:
dirname /etc/hosts
/etc

basename /etc/hosts
hosts

To extract only the extension or the filename without the extension, use bash's string matching:
Filename=$(basename /etc/resolv.conf)
Ext="${Filename##*.}"
Name="${Filename%.*}"

== Arithmetic Operations ==
Do integer arithmetic operations on variables within double brackets. For example:
Value=1
ValuePlusOne=$((Value + 1))
ValueTimes12=$((Value * 12))

The operators that are supported are:
+ - / * %
Bitwise operators also work:
^ (XOR) | (OR) & (AND)

== Control Blocks ==
=== Switch ===
<syntaxhighlight lang="bash">
read -p "What do you want to do?: " Option

case "$Option" in
"K")
install_new_kernel
die "Complete!"
;;
"H")
usage
;;
*)
die "Stopping installation."
;;
esac
</syntaxhighlight>

== Snippets ==
=== Get First IP Address ===
ip a | /bin/grep inet | grep -v inet6 | tail -n+2 | head -n 1 | awk '{print $2}' | cut -d'/' -f1

[[Category:Linux]]
{{Navbox Linux}}

Arch Linux

2015-04-06T21:27:59Z

136.159.16.240: /* Installation */

== PXE ==
If you already have a PXE server, create a new entry that boots their iPXE kernel:
cd /tftpboot/images/ArchLinux/
wget https://releng.archlinux.org/pxeboot/ipxe.lkrn

The default config (or the config your computer boots off of) should contain:
<syntaxhighlight lang="text">
LABEL ArchLinux
MENU LABEL ArchLinux
kernel /images/ArchLinux/ipxe.lkrn
</syntaxhighlight>

You can customize the kernel to automate installs.

== Installation ==
The PXE rom that you can download from ArchLinux's website points iPXE to fetch PXE data from a remote HTTP server, http://releng.archlinux.org/pxeboot/boot/cfg/. The PXE configs will then boot the live image from one of the many available mirrors that is selected in the boot menu.

=== Remastering ===
'''Side Note''': You may alter the [[iPXE]] script to use a different server by recompiling the iPXE kernel and automate the install process by appending to the airoot customize script.

pacman -S archiso
cp -r /usr/share/archiso/configs/releng /root
# edit relang/airootfs/root/custom*
./build.sh -v

mkarchiso -w work/x86_64 -C work/pacman.conf -D arch init
arch-chroot work/x86_64/airootfs mkinitcpio -c /etc/mkinitcpio-archiso.conf -k /boot/vmlinuz-linux -g /boot/archiso.img
mksquashfs work/airootfs.img work/iso/arch/x86_64/airootfs.sfs -noappend -comp xz -no-progress

=== Steps ===
After booting into the live image, you need to:
# Read the install.txt file
# Create a file system
# Mount the file system to /mnt
# Run <code>pacstrap /mnt/base</code>
# Generate fstab <code>genfstab -p /mnt >> /mnt/etc/fstab</code>
# Chroot into the new system <code>arch-chroot /mnt</code>
# Set the hostname <code>echo "hostname" >> /etc/hostname</code>
# Set the timezone <code>ln -sf /usr/share/zoneinfo/America/Edmonton /etc/localtime</code>
# Locales
#* Comment out any locales you want in <code>/etc/locale.gen</code>
#* Run <code>locale-gen</code>
# Set the default locale <code>echo LANG=\"en_US.UTF-8\" > /etc/locale.conf</code>
# Set up networking configs ??
# Console font <code>/etc/vconsole.conf</code>
#* echo KEYMAP=\"us\" > /etc/vconsole.conf
#* echo FONT=\"latarcyrheb-sun16\" >> /etc/vconsole.conf
# Rebuild ram disk <code>mkinitcpio -p linux</code>
# Set the root password <code>passwd</code>
# Install a bootloader
#* pacman -Sy grub
#* <code>grub-install --target=i386-pc --recheck /dev/sda</code>
#* <code>grub-mkconfig -o /boot/grub/grub.cfg</code>

Reboot and hope it works.

=== Networking ===
You may use systemd to configure the network
/etc/systemd/network
Create a file named <code>wired.network</code> with:
<syntaxhighlight lang="text">
[Match]
Name=eno1

[Network]
DHCP=v4
</syntaxhighlight>

You may need to get a list of all network interfaces using:
networkctl list | tail -n+2 | head -n+2 | grep -v loopback | awk '{print $2}'

== Package List ==
gnome-desktop nvidia-304xx-libgl
lightdm lightdm-gtk-greeter

qt

dmidecode

accountsservices

salt-zmq

== Mirroring ==
rsync -rtlH --delete-after --exclude='*i686*' --delay-updates --copy-links --safe-links --max-delete=1000 --progress rsync://mirror.csclub.uwaterloo.ca/archlinux/community .

* https://www.archlinux.org/mirrors/status/

Syslog

2015-04-06T19:59:10Z

136.159.16.240:

== Configuration ==

<syntaxhighlight lang="text">
# Log all kernel messages to the console.
# Logging much else clutters up the screen.
#kern.* /dev/console

# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none /var/log/messages

# The authpriv file has restricted access.
authpriv.* /var/log/secure

# Log all the mail messages in one place.
mail.* -/var/log/maillog

# Log cron stuff
cron.* /var/log/cron

# Everybody gets emergency messages
*.emerg *

# Save news errors of level crit and higher in a special file.
uucp,news.crit /var/log/spooler

# Save boot messages also to boot.log
local7.* /var/log/boot.log

# Log to the logstash server
*.* @@logstash.cs.ucalgary.ca:5544

# Log to the old loghost server
*.* @loghost

</syntaxhighlight>

== Troubleshooting ==

<syntaxhighlight lang="text">
[root@leo-archer log]# systemctl start rsyslog
A dependency job for rsyslog.service failed. See 'journalctl -xe' for details.

journalctl -xe

-- The result is failed.
Apr 06 13:55:27 leo-archer systemd[1]: Dependency failed for System Logging Service.
-- Subject: Unit rsyslog.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rsyslog.service has failed.
--

systemctl enable rsyslog
systemctl start rsyslog

</syntaxhighlight>

[[Category:Linux]]

Syslog

2015-04-06T19:57:53Z

136.159.16.240: Created page with " <syntaxhighlight lang="text"> [root@leo-archer log]# systemctl start rsyslog A dependency job for rsyslog.service failed. See 'journalctl -xe' for details. journalctl -xe -..."

<syntaxhighlight lang="text">
[root@leo-archer log]# systemctl start rsyslog
A dependency job for rsyslog.service failed. See 'journalctl -xe' for details.

journalctl -xe

-- The result is failed.
Apr 06 13:55:27 leo-archer systemd[1]: Dependency failed for System Logging Service.
-- Subject: Unit rsyslog.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rsyslog.service has failed.
--

systemctl enable rsyslog
systemctl start rsyslog

</syntaxhighlight>

[[Category:Linux]]

Arch Linux

2015-04-06T17:32:02Z

136.159.16.240:

== PXE ==
If you already have a PXE server, create a new entry that boots their iPXE kernel:
cd /tftpboot/images/ArchLinux/
wget https://releng.archlinux.org/pxeboot/ipxe.lkrn

The default config (or the config your computer boots off of) should contain:
<syntaxhighlight lang="text">
LABEL ArchLinux
MENU LABEL ArchLinux
kernel /images/ArchLinux/ipxe.lkrn
</syntaxhighlight>

You can customize the kernel to automate installs.

== Installation ==
The PXE rom that you can download from ArchLinux's website points iPXE to fetch PXE data from a remote HTTP server, http://releng.archlinux.org/pxeboot/boot/cfg/. The PXE configs will then boot the live image from one of the many available mirrors that is selected in the boot menu.

=== Remastering ===
'''Side Note''': You may alter the [[iPXE]] script to use a different server by recompiling the iPXE kernel and automate the install process by appending to the airoot customize script.

pacman -S archiso
cp -r /usr/share/archiso/configs/releng /root
# edit relang/airootfs/root/custom*
./build.sh -v

mkarchiso -w work/x86_64 -C work/pacman.conf -D arch init
arch-chroot work/x86_64/airootfs mkinitcpio -c /etc/mkinitcpio-archiso.conf -k /boot/vmlinuz-linux -g /boot/archiso.img
mksquashfs work/airootfs.img work/iso/arch/x86_64/airootfs.sfs -noappend -comp xz -no-progress

=== Steps ===
After booting into the live image, you need to:
# Read the install.txt file
# Create a file system
# Mount the file system to /mnt
# Run <code>pacstrap /mnt/base</code>
# Generate fstab <code>genfstab -p /mnt >> /mnt/etc/fstab</code>
# Chroot into the new system <code>arch-chroot /mnt</code>
# Set the hostname <code>echo "hostname" >> /etc/hostname</code>
# Set the timezone <code>ln -sf /usr/share/zoneinfo/America/Edmonton /etc/localtime</code>
# Locales
#* Comment out any locales you want in <code>/etc/locale.gen</code>
#* Run <code>locale-gen</code>
# Set the default locale <code>echo LANG=\"en_US.UTF-8\" > /etc/locale.conf</code>
# Set up networking configs ??
# Console font <code>/etc/vconsole.conf</code>
#* echo KEYMAP=\"us\" > /etc/vconsole.conf
#* echo FONT=\"latarcyrheb-sun16\" >> /etc/vconsole.conf
# Rebuild ram disk <code>mkinitcpio -p linux</code>
# Set the root password <code>passwd</code>
# Install a bootloader
#* pacman -Sy grub
#* <code>grub-install --target=i386-pc --recheck /dev/sda</code>
#* <code>grub-mkconfig -o /boot/grub/grub.cfg</code>

Reboot and hope it works.

== Package List ==
gnome-desktop nvidia-304xx-libgl
lightdm lightdm-gtk-greeter

qt

dmidecode

accountsservices

salt-zmq

== Mirroring ==
rsync -rtlH --delete-after --exclude='*i686*' --delay-updates --copy-links --safe-links --max-delete=1000 --progress rsync://mirror.csclub.uwaterloo.ca/archlinux/community .

* https://www.archlinux.org/mirrors/status/

Pacman

2015-04-06T17:29:49Z

136.159.16.240:

Pacman is the package manager for arch linux.

== Introduction ==

Configuration files are stored in /etc/pacman
=== Updating Databases ===

Similar to a <code>yum clean all ; yum update</code> you can update the repository information by running:
pacman -Syy

=== Searching ===
Search for a package
pacman -Ss packageName

=== Installing ===
pacman -S packageName groupName

=== Updating System ===
pacman -Syu

[[Category:Linux]]
[[Category:PackageManagement]]
{{Navbox Linux}}

Bash Scripting

2015-03-31T18:09:50Z

136.159.16.240: Created page with " == Extracting / Parsing Filenames == Use the <code>basename</code> to extract filenames from a path and and <code>dirname</code> to extract the path of a filename. Eg: dirn..."

== Extracting / Parsing Filenames ==
Use the <code>basename</code> to extract filenames from a path and and <code>dirname</code> to extract the path of a filename.

Eg:
dirname /etc/hosts
/etc

basename /etc/hosts
hosts

To extract only the extension or the filename without the extension, use bash's string matching:
Filename=$(basename /etc/resolv.conf)
Ext="${Filename##*.}"
Name="${Filename%.*}"

== Arithmetic Operations ==
Do integer arithmetic operations on variables within double brackets. For example:
Value=1
ValuePlusOne=$((Value + 1))
ValueTimes12=$((Value * 12))

The operators that are supported are:
+ - / * %
Bitwise operators also work:
^ (XOR) | (OR) & (AND)

[[Category:Linux]]
{{Navbox Linux}}

Self Signed SSL Certificates

2015-03-30T16:28:40Z

136.159.16.240:

__NOTOC__
Self-signed SSL certificates can be used to set up a temporary or personal SSL web server. It may be useful in cases where you don't want to spend money for security or if you distrust all certificate authorities

To quickly generate a self-signed certificate, enter a domain name below and follow the instructions:
<htmlet nocache="yes">selfsignedssl-js</htmlet>

Run the following commands on a *NIX machine with OpenSSL installed:
<htmlet nocache="yes">selfsignedssl-cmd</htmlet>

To configure apache to use the newly created key and SSL certificate, create a new <code>VirtualHost</code> with the configuration below:
<htmlet nocache="yes">selfsignedssl-apache</htmlet>

=== Explaination ===

== Renewing an Expired Self Signed Certificate ==
You can check the status of a certificate using:
openssl x509 -in cert.crt -text -noout

If it has expired, you can 'renew' it by first regenerating a certificate signing request (CSR):
openssl x509 -x509toreq -in expired_certificate.crt -out new_csr.csr -signkey domain_private.key

Then signing the CSR with the private key to produce a new certificate:
openssl x509 -req -days 3650 -in new_csr.csr -signkey domain_private.key -out new_certificate.crt

Replace the expired certificate with the new certificate and reload any services that are using the certificate for it to be applied.

== Trusting Your Self Signed SSL Certificates ==
The key and certificate generated with the steps above will not be signed by a trusted certificate authority and therefore cannot be verified by your browser, resulting in a security warning.

== Other Notes ==

Note: Ensure that all keys are not readable to others. chmod 700 the ssl directory and chmod 600 all the keys.

openssl req -new -x509 -key www.example.com.key -out www.example.com.cert -days 3650 -subj /CN=www.example.com

== See Also ==
* [[OpenSSL]]
* https://www.sslshopper.com/article-most-common-openssl-commands.html

Self Signed SSL Certificates

2015-03-30T16:28:14Z

136.159.16.240:

Self Signed SSL Certificates

2015-03-30T16:27:53Z

136.159.16.240:

Self-signed SSL certificates can be used to set up a temporary or personal SSL web server. It may be useful in cases where you don't want to spend money for security or if you distrust all certificate authorities

To quickly generate a self-signed certificate, enter a domain name below and follow the instructions:
<htmlet nocache="yes">selfsignedssl-js</htmlet>

Run the following commands on a *NIX machine with OpenSSL installed:
<htmlet nocache="yes">selfsignedssl-cmd</htmlet>

To configure apache to use the newly created key and SSL certificate, create a new <code>VirtualHost</code> with the configuration below:
<htmlet nocache="yes">selfsignedssl-apache</htmlet>

=== Explaination ===

== Renewing an Expired Self Signed Certificate ==
You can check the status of a certificate using:
openssl x509 -in cert.crt -text -noout

If it has expired, you can 'renew' it by first regenerating a certificate signing request (CSR):
openssl x509 -x509toreq -in expired_certificate.crt -out new_csr.csr -signkey domain_private.key

Then signing the CSR with the private key to produce a new certificate:
openssl x509 -req -days 3650 -in new_csr.csr -signkey domain_private.key -out new_certificate.crt

Replace the expired certificate with the new certificate and reload any services that are using the certificate for it to be applied.

== Trusting Your Self Signed SSL Certificates ==
The key and certificate generated with the steps above will not be signed by a trusted certificate authority and therefore cannot be verified by your browser, resulting in a security warning.

== Other Notes ==

Note: Ensure that all keys are not readable to others. chmod 700 the ssl directory and chmod 600 all the keys.

openssl req -new -x509 -key www.example.com.key -out www.example.com.cert -days 3650 -subj /CN=www.example.com

Sed

2015-03-23T19:15:07Z

136.159.16.240:

== Modifying a File Directly ==

Using the above tips, you can modify a file directly by using the <code>-i</code> parameter, with the filename as the second argument:
sed -i "search" /path/to/file

== Simple search / replace ==
Global search and replace:
sed 's/<search>/<replace>/g'

To replace only the first match:
sed '0,/<search>/s//<replace>/'

== Remove HTML tags ==

sed -e 's/<[^>]*>//g' <file>

== Remove File Extensions ==

sed 's/$.*$\..*/\1/'

eg:
echo "house.txt" | sed 's/$.*$\..*/\1/' # returns 'house'

== Delete Matching Line ==

sed '/someline/d'

== Inserting a Line Before/After a Match ==

Use: <code>0,/<regex>/s//<replacement text where \0 is the found line>/</code>
# Add a password line before the first title entry in the grub.conf file.
sed -i "0,/^title/s//password --encrypted $Password\n\n\0/" $GrubConfig

To append after, just put \0 before your replacement text.

== Grap Specific Section using Regex ==
To grab a specific section of a string, for instance '3' in 'Server time offset: 3':
echo 'Server time offset: 3' | sed -n -e 's/.*: $[0-9]*$/\1/p'

This can also be done with grep, though it isn't regex:
echo 'Server time offset: 3' | /bin/grep -ohE '[0-9]*'

[[Category:Linux]]
[[Category:TipsnTricks]]
[[Category:Code]]

Awk

2015-03-23T18:00:58Z

136.159.16.240: /* Convert ps Elapsed Time to Seconds */

Awk

2015-03-23T17:57:59Z

136.159.16.240:

== Counting Lines Until Match ==

To print the number of lines before a match is found:
awk 'BEGIN { n = 0 } /PATTERN/ { print n; next } { n++ }'

Eg: Suppose I have a file with the contents:
leo
spoon
cake
fork

To find the number of lines up until 'cake', do:
cat list.txt | awk 'BEGIN { n = 0 } /cake/ { print n; next } { n++ }'

== Convert Number as Bytes to Human Readable Value ==
I wanted to sort size in reverse order, but in order to do that properly, the value from du needs to be in kilobytes. I also didn't want to run this through du again just to get the human readable value. So, I did this:

<syntaxhighlight lang="bash" line start="1" enclose="div">
du -s ./*/ ./*/*/ ./*/*/*/ \
| sort -rn \
| awk 'BEGIN { \
split("KB MB GB TB PB", type) \
} \
{ \
y = 0; \
x = $1; \
for (i = 4; y < 1 ; i--) \
y = x / (2 ** (10 * i)); \
print y type[i+2]" "$2 \
}'
</syntaxhighlight>

If you want to count using bytes instead of kilobytes, just add K to the split function and replace i=4 with i=5.

== Convert <code>ps</code> Elapsed Time to Seconds ==
To convert the elapsed time (in [[http://pubs.opengroup.org/onlinepubs/009696799/utilities/ps.html|POSIX locale]] formatted as <code>[[dd-]hh:]mm:ss</code>) to seconds using awk:

<syntaxhighlight lang="bash">
Elapsed=`ps -p $Pid -o etime=`
Elapsed=`echo $Elapsed | tr - : | tr : ' '`
Seconds=`echo $Elapsed | awk '
NF == 2 { print ($1 * 60) + $2 }
NF == 3 { print ((($1 * 60) + $2) * 60) + $3 }
NF == 4 { print ((((($1 * 24) + $2) * 60) + $3) * 60) + $4 }
{}'`
echo $Seconds
</syntaxhighlight>

[[Category:Linux]]
[[Category:TipsnTricks]]

Awk

2015-03-23T17:56:52Z

136.159.16.240:

Vnstat

2015-03-23T17:00:47Z

136.159.16.240:

== Installation ==
The following steps should work for CentOS/ScientificLinux/RHEL.

<syntaxhighlight lang="bash" line start="1" enclose="div">
wget http://humdi.net/vnstat/vnstat-1.11.tar.gz
tar -xzf vnstat-1.11.tar.gz
cd vnstat-1.11
make
make install
vnstat --testkernel
/bin/cp examples/init.d/centos/vnstat /etc/init.d/vnstat
chkconfig --levels 234 --add vnstat
vnstat -u -i eth0
/etc/init.d/vnstat start
</syntaxhighlight>

== Usage ==
You do not need to interface with vnstat directly since vnstat will create a cronjob in <code>/etc/cron.d/vnstat</code> which will run <code>/usr/sbin/vnstat.cron</code> as nobody every 5 minutes.

However, you may need to fix or initialize the database.

=== Initializing Database ===
To initialize a database for a specific device:
vnstat -u -i $NetInterface

=== Force Update ===
sudo -u /usr/sbin/vnstat.cron --force

[[Category:Guides]]
[[Category:Linux]]

IPv6

2015-03-19T21:36:51Z

136.159.16.240: Created page with " To disable IPv6 # sysctl net.ipv6.conf.all.disable_ipv6=1 # sysctl net.ipv6.conf.default.disable_ipv6=1 # sysctl net.ipv6.conf.lo.disable_ipv6=1 Category:Linux"

To disable IPv6
# sysctl net.ipv6.conf.all.disable_ipv6=1
# sysctl net.ipv6.conf.default.disable_ipv6=1
# sysctl net.ipv6.conf.lo.disable_ipv6=1

[[Category:Linux]]