Provided by: bitcoind_0.3.24~dfsg-1_i386 NAMESYNOPSISDESCRIPTIONOPTIONS-conf=-gen-gen=0-min-datadir=-proxy=-addnode=-connect=-paytxfee=-server-daemon-testnet-rpcuser=-rpcpassword=-rpcport=-rpcallowip=-rpcconnect=-rpcssl=1-rpcsslcertificatchainfile=-rpcsslprivatekeyfile=-rpcsslciphers=COMMANDSbackupwallet 'destination'getaccount 'bitcoinaddress'setaccount 'bitcoinaddress' ['account']getaccountaddress 'account'getaddressesbyaccount 'account'getbalance 'account'getblockcountgetblocknumbergetconnectioncountgetdifficultygetgeneratesetgenerate 'generate' ['genproclimit']gethashespersecgetinfogetnewaddress 'account'getreceivedbyaccount 'account' ['minconf=1']getreceivedbyaddress 'bitcoinaddress' ['minconf=1']gettransaction 'txid'getwork 'data'help 'command'listaccounts ['minconf=1']listreceivedbyaccount ['minconf=1'] ['includeempty=false']listreceivedbyaddress ['minconf=1'] ['includeempty=false']listtransactions 'account' ['count=10']move <'fromaccount'> <'toaccount'> <'amount'> ['minconf=1'] ['comment']sendfrom*<'account'><'bitcoinaddress'><'amount'>['minconf=1']['comment'] ['comment-to']sendtoaddress 'bitcoinaddress' 'amount' ['comment'] ['comment-to']stopvalidateaddress 'bitcoinaddress'SEE ALSO bitcoin.conf(5) > for the Debian system (but may be used by others).

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 3 or any later version published by the Free Software Foundation.On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL.Powered by the Ubuntu Manpage Repository generator maintained by Dustin Kirkland © 2010 Canonical Ltd.Ubuntu and Canonical are registered trademarks of Canonical Ltd.[Edit 2017-04-20] A careful reader informed me (thanks for that HN user puzzle) that it is no longer required to run in privileged mode to access the GPUs in K8s.I therefore removed a note that previously stated this requirement, and am in the process of updating my Helm charts to remove it as well from there.Over the last 4 months I have blogged 4 times about the enablement of GPUs in Kubernetes.Each time I did so, I spent several days building and destroying clusters until it was just right, making the experience as fluid as possible for adventurous readers.

It was not the easiest task as the environments were different (cloud, bare metal), the hardware was different (g2.xlarge have old K20s, p2 instances have K80s, I had 1060GTX at home but on consumer grade Intel NUC…).As a result, I also spent several hours supporting people to set up clusters.Usually with success, but I must admit some environments have been challenging.Thankfully the team at Canonical in charge of developing the Canonical Distribution of Kubernetes have productized GPU integration and made it so easy to use that it would just be a shame not to talk about it.And as of course happiness never comes alone, I was lucky enough to be allocated 3 brand new, production grade Pascal P5000 by our nVidia friends.I could have installed these in my playful rig to replace the 1060GTX boards.But this would have showed little gratitude for the exceptional gift I received from nVidia.Instead, I decided to go for a full blown “production grade” bare metal cluster, which will allow me to replicate most of the environments customers and partners have.

I chose to go for 3x Dell T630 servers, which can be GPU enabled and are very capable machines.I received them a couple of week ago, and… Please don’t mind the cables, I don’t have a rack…There we are!Ready for some awesomeness?If you remember the other posts, the sequence was: Overall, on top of the Kubernetes installation, with all the scripting in the world, no less than 30 to 45min were lost to perform the specific maintenance for GPU enablement.litecoin pool rateIt is better than having no GPUs, but it is often too much for the operators of the clusters who want an instant solution.texas holdem bitcoin pokerI am happy to say that the requests of the community have been heard loud and clear.bitcoin barcode

As of Kubernetes 1.6.1, and the matching GA release of the Canonical Distribution of Kubernetes, the new experience is : Yes, you read that correctly.Single command deployment of GPU-enabled Kubernetes Cluster Since 1.6.1, the charms will now: You don’t believe me?Watch me… For the following, you’ll need: and for the files, cloning the repo: Deploying in the cloud is trivial.bitcoin ticker gbpOnce Juju is installed and your credentials are added, I was able to capture the moment where it is installing CUDA so you can see it… When it’s done: That’s it, you can see the K80 from the p2.xlarge instance.bitcoin brute forcerI didn’t do anything about it, it was completely automated.litecoin windows minerThis is Kubernetes on GPU steroids.

Obviously there is a little more to do on Bare Metal, and I will refer you to my previous posts to understand how to set MAAS up & running.This assumes it is already working.Adding the T630 to MAAS is a breeze.If you don’t change the default iDRAC username password (root/calvin), the only thing you have to do it connect them to a network (a specific VLAN for management is preferred of course), set the IP address, and add to MAAS with an IPMI Power type.Adding the nodes into MAASThen commission the nodes as you would with any other.This time, you won’t need to press the power button like I had to with the NUC cluster: MAAS will trigger via the IPMI card directly, request a PXE boot, and register the node, all fully automagically.Once that is done, tag them “gpu” to make sure to recognize them.Details about the T630 in MAAS Wait for a few minutes… You will see at some point that the charm is now installing CUDA drivers.At the end, That’s it, my 2 cards are in there: 1060GTX and P5000.

Again, no user interaction.How awesome is this?Note that the interesting aspects are not only that it automated the GPU enablement, but also that the bundle files (the yaml content) are essentially the same, but for the machine constraints we set.If you follow me you know I’ve been playing with Tensorflow, so that would be a use case, but I actually wanted to get some raw fun with them!One of my readers mentioned bitcoin mining once, so I decided to go for it.I made a quick and dirty Helm Chart for an Ethereum Miner, along with a simple rig monitoring system called ethmon.This chart will let you configure how many nodes, and how many GPU per node you want to use.Then you can also tweak the miner.For now, it only works in ETH only mode.Don’t forget to create a values.yaml file to By default, you’ll get the 3 worker nodes, with 2 GPUs (this is to work on my rig at home) KubeUI with the miners deployed Monitoring interface (ethmon)You can also track it here with nice graphs.