ThirdParty

Differences between revisions 7 and 8
⇤ ← Revision 7 as of 2015-02-20 13:03:18 →
Size: 5050
Editor: b153d7bc
Comment:
← Revision 8 as of 2015-02-20 15:56:33 → ⇥
Size: 7446
Editor: b153d7bc
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
=== Installing Salt on the master and on all minions ===

In order to do it, do:		 === Installing Saltstack ===

In order to do it, do the following on all machines you want to have controlled by saltstack as in the master node:
Line 12: Line 12:
# pip install pycrypto
# git clone https://github.com/saltstack/salt.git
# cd salt
# sudo python setup.py install
}}}
    # pip install pycrypto
   # git clone https://github.com/saltstack/salt.git
   # cd salt
   # sudo python setup.py install
}}}


== Start daemons ==

Once you have saltstack installed on all machines, you need to start the daemons.

For the minions, you need to specify which is the master node. The easier way to do it is configuring the hostname 'salt' point to the node IP, as for example:

{{{
# echo '10.1.1.4 salt' >> /etc/hosts
}}}

Then, you are able to start running the daemons. On the master node, you should run '''# salt-master''' or use the ''salt.master.service'' systemctl service. For minions, you should call '''# salt-minion''', or, again, the proper '''salt.minion.service'' service.

Examples:

=== On master ===

Start the server with the following command:

{{{
salt-master
}}}

Or, preferably using the daemon services, as the following line for ''systemd':

{{{
systemctl enable salt-master.service
}}}

=== On Minions ===

For every minion you have, start the salt daemon with:

{{{
salt-minion
}}}

Or, preferably using the daemon services, as the following line for ''systemd':

{{{
systemctl enable salt-minion.service
}}}

== Accept the minions keys in the master ==

When the minion connects to the master node, it provides a key that needs to be accepted by the master. In order to see the keys that are pending approval, go to the master node and use the command '''# salt-key -L''', and to approve then, use the '''# salt-key -A'''.

After approval, you are going to see something like this, where ubuntu1404 and ubuntu140402 are my current minions.

{{{
 sudo salt-key -L
Accepted Keys:
  ubuntu1404
  ubuntu140402
Denied Keys:
Unaccepted Keys:
Rejected Keys:
}}}

This example shows that my both minions have the keys accepted.

After that, you can check to see if the connection is fine with your minion, using the following command:


{{{
# salt '*' test.ping
ubuntu1404:
    True
ubuntu140402:
    True
}}}

In this case, means that both minions are reachable and you go proceed and start using salt.

One of the example, is capturing the MAC address for the eth0 interface on all minions:

{{{
sudo salt '*' network.hw_addr eth0
ubuntu1404:
    4c:45:42:45:01:01
ubuntu140402:
    4c:45:42:45:01:09
}}}

Or, restarting all the minions at once:

{{{
sudo salt '*' system.reboot
ubuntu140402:
    
ubuntu1404:
}}}

Third Party applications for Ubuntu on POWER

Saltstack

Installing Saltstack

In order to do it, do the following on all machines you want to have controlled by saltstack as in the master node: 

   # sudo apt-get install python-m2crypto  python-yaml python-m2crypto  python-zmq python-msgpack python-jinja2 python-dev python-pip git
   # pip install pycrypto
   # git clone https://github.com/saltstack/salt.git
   # cd salt
   # sudo python setup.py  install

== Start daemons ==

Once you have saltstack installed on all machines, you need to start the daemons.

For the minions, you need to specify which is the master node. The easier way to do it is configuring the hostname 'salt' point to the node IP, as for example: 

# echo '10.1.1.4        salt' >> /etc/hosts

Then, you are able to start running the daemons. On the master node, you should run # salt-master or use the salt.master.service systemctl service. For minions, you should call # salt-minion, or, again, the proper salt.minion.service service.

Examples:

On master

Start the server with the following command: 

salt-master

Or, preferably using the daemon services, as the following line for systemd': 

systemctl enable salt-master.service

On Minions

For every minion you have, start the salt daemon with: 

salt-minion

Or, preferably using the daemon services, as the following line for systemd': 

systemctl enable salt-minion.service

Accept the minions keys in the master

When the minion connects to the master node, it provides a key that needs to be accepted by the master. In order to see the keys that are pending approval, go to the master node and use the command # salt-key -L, and to approve then, use the # salt-key -A.

After approval, you are going to see something like this, where ubuntu1404 and ubuntu140402 are my current minions. 

 sudo salt-key -L
Accepted Keys:
  ubuntu1404
  ubuntu140402
Denied Keys:
Unaccepted Keys:
Rejected Keys:

This example shows that my both minions have the keys accepted.

After that, you can check to see if the connection is fine with your minion, using the following command: 

# salt '*' test.ping
ubuntu1404:
    True
ubuntu140402:
    True

In this case, means that both minions are reachable and you go proceed and start using salt.

One of the example, is capturing the MAC address for the eth0 interface on all minions: 

sudo salt '*' network.hw_addr eth0
ubuntu1404:
    4c:45:42:45:01:01
ubuntu140402:
    4c:45:42:45:01:09

Or, restarting all the minions at once: 

sudo salt '*' system.reboot
ubuntu140402:
    
ubuntu1404:

Advance Toolchain

The Advance Toolchain is a set of development tools, i.e. compiler, libraries, debugger and profiling tools, that help developers take leading edge advantage of IBM's latest POWER hardware features.

The following steps will guide you on the installation process of the Advance Toolchain. Detailed information is available in the Advance Toolchain documentation.

Firstly, import the Advance Toolchain GPG key by running: 

wget ftp://ftp.unicamp.br/pub/linuxpatch/toolchain/at/ubuntu/dists/precise/6976a827.gpg.key
sudo apt-key add 6976a827.gpg.key

Note: In the following steps, replace atX.X by the desired version, e.g. at8.0.

Native installation (on POWER)

Add the following line to /etc/apt/sources.list: 

deb ftp://ftp.unicamp.br/pub/linuxpatch/toolchain/at/ubuntu trusty atX.X

Then, install the packages by running: 

sudo aptitude install advance-toolchain-atX.X-runtime \
                      advance-toolchain-atX.X-devel \
                      advance-toolchain-atX.X-perf \
                      advance-toolchain-atX.X-mcore-libs

Cross compiler installation (on Intel)

The Advance Toolchain supports cross compilation from Intel processors and generating binaries for POWER processors.

Add the following line to /etc/apt/sources.list in your Intel-compatible computer: 

deb [arch=i386] ftp://ftp.unicamp.br/pub/linuxpatch/toolchain/at/ubuntu trusty atX.X

Then, install the packages by running: 

sudo aptitude install advance-toolchain-atX.X-cross-ppc64 advance-toolchain-atX.X-cross-ppc64le

For more information on how to use the Advance Toolchain cross compiler visit this page.

IBM SDK for PowerLinux

The IBM Software Development Kit for Linux on Power (SDK) is a free, Eclipse-based Integrated Development Environment (IDE). The SDK integrates C/C++ source development with the Advance Toolchain, Post-Link Optimization, and classic Linux performance analysis tools, including Oprofile, Perf and Valgrind. It is available as two different packages, providing you with three different development modes:

  • The IBM SDK for PowerLinux server development package allows you to use the IBM SDK for PowerLinux, which integrates the Eclipse integrated development environment (IDE), directly on the Power Systems server.

  • With the IBM SDK for PowerLinux client for remote development package, you can start the IBM SDK for PowerLinux x86_64 client, including the Eclipse IDE, on a workstation. You can then connect to a remote Power Systems server that has the IBM SDK for PowerLinux server agent installed to build, execute, debug, and analyze programs.

  • With the client for remote development package and cross-compiler feature, you can develop and build your application locally using the IBM Advance Toolchain for PowerLinux cross compiler.

To install IBM SDK for PowerLinux on Ubuntu, follow the instructions available at Download and Installation.

IBM Java

http://www.ibm.com/developerworks/java/jdk/linux/tested.html

Adding IBM Java Apt Repository

IBM Java is currently located into the Canonical partner archive and can be installed through the apt tool.

The partner repository is usually already into the file /etc/apt/sources.list, although disabled (commented). In order to enable it, one should uncomment or, in case it is not in the repositories list, add it to /etc/apt/sources.list. 

   1 deb http://archive.canonical.com/ubuntu utopic partner
   2 deb-src http://archive.canonical.com/ubuntu utopic partner

Then retrieve the updated package lists: 

   1 sudo apt-get update

Finally install it, via apt-get install. For the jdk: 

   1 sudo apt-get install ibm-java71-jdk

Or jre: 

   1 sudo apt-get install ibm-java71-jre

ppc64el/ThirdParty (last edited 2018-05-08 19:09:28 by rogerioalves25)