Differences

This shows you the differences between two versions of the page.

--- juju-manual [2016/12/07 16:22]
sgiulitti
+++ juju-manual [2016/12/08 21:52]
@@ Line 1: / Line 1: @@
-Hi guys, I will help you step by step to manually provision a windows machine. :-)
-====== Introduction ======
-Not long ago, manual provisioning in Juju was possible for linux machines. This feature is quite handy if you want to mange by yourself the cloud or you are providing for your services you own hosted cloud.
-===== For this example we are are using this: =====
-       State Machine   : xenial ubuntu   | 10.10.10.101)
-       Windows Machine : windows 2012 r2 | 10.10.10.102)
-==== So without further ado let's start the hacking process ====
-----
- ====== Step 1 ======
- '' This step will be entirly on the controller. Seting up the environ for manual compiling, instaling build scripts, make the process more automated''
-   Pop up a bash terminal windows in your controller(juju client machine) and execute din commands in order.
-<code bash>
-go get -v -u https://github.com/hoenirvili/juju/...
-go get -v launchpad.net/godeps
-cd $GOPATH/src/github.com/juju/juju
-git checkout enable-windows-provisioner
-godeps -t -u dependencies.tsv
-</code>
-I will supply here a link to the gist where you could download the build script in order to make the process more simpler.
-[[https://gist.github.com/hoenirvili/3c8f858a3865f3b31a3ee19c58ab2688]]
-Download all scripts in some location ,make them executable and point the path into $PATH env.
-For example(in my order of things).
-<code bash>
-SCRIPT_PATH = ~/Documents/scripts/
-mkdir -p $SCRIPT_PATH
-cd $SCRIPT_PATH
-https://gist.github.com/3c8f858a3865f3b31a3ee19c58ab2688.git
-mv 3c8f858a3865f3b31a3ee19c58ab2688/* $SCRIPT_PATH
-rmdir 3c8f858a3865f3b31a3ee19c58ab2688
-chmod u+x *
-# I usualy do this in my .profile in my $HOME directory. But you can run the line straight in the
-# shell, be careful when you close the bash session you will lose all variables saved, so put
-# it somewhere, where scripts will always load when you open a shell.(example .bashrc)
-export $PATH:$HOME/Documents/scripts
-</code>
-=== Now you can build the project doing running this command. Read the above Note first before executing this command. ===
-<code bash>  makejuju.sh enable-windows-provisioner  </code>
-In the **uploadtools.sh** file make sure on the last line, the path is pointing to the files where the http server has acces to serve them, mine for example is **/var/html/** (default on **ubuntu** systems).
-To make sure. You cand execute this commands in order.
-<code bash>
-mkdir -p /var/html/toolsdir
-chown -R $USER:$USER /var/html/*
-</code>
-We need to do this because the state machine will access the metadata and download the fresh jujud binary based on a specific series.
-====== Step 2 ======
-''This setup will show how to create and manage a WinRM(windows remote manager) listeners, how to setup a  CA cert for secure interactions with the WinRM protocol.''
-First ,we need check if the windows machine has enabled all WinRM listeners. It's important because, in the provisioning process, the juju client directly communicate, using this protocol in order to fully provision the machine.
-===== This is how would look if both listeners are enabled  =====
-{{:winrm_display_listeners.png?nolink|}}
-If not you will need to do the steps above.
-Open PowerShell console(on the windows machine) and type the following command to enable PowerShell remoting and the WinRM http listner:
-<code powershell>
-Enable-PSRemoting -Force
-Set-ExecutionPolicy RemoteSigned
-winrm quickconfig
-</code>
-{{:winrmquickconfig.png?nolink|}}
-To enable HTTPS listener you must first create a your own self signed CA cert using openssl or makecert.
-This guide will use openssl.
-=== Download OpenSSL for Windows. ===
-[[http://slproweb.com/products/Win32OpenSSL.html]]
-Package Win32/64 OpenSSL vx.x.x Light is more than enough for generating SSL certificate.
-To add Server Authentication to EKU open openssl.cfg and add extendedKeyUsage setting under v3_ca section:
-<code>
-[ v3_ca ]
-extendedKeyUsage = serverAuth
-subjectAltName = IP:192.168.100.102
-</code>
-<code powershell>
-set OPENSSL_CONF=C:\OpenSSL-Win64\bin\openssl.cfg
-cd C:\Users\Administrator
-C:\OpenSSL-Win64\bin\openssl.exe req -x509 -nodes -days 9999 -newkey rsa:2048 -keyout winrmcacert.key -out winrmcacert.cer -subj "/CN=maas-win2k12r2"
-C:\OpenSSL-Win64\bin\openssl.exe pkcs12 -export -out winrmcacert.pfx -inkey winrmcacert.key -in winrmcacert.cer -name "maas-win2k12r2" -passout pass:
-Import-PfxCertificate -FilePath .\winrmcacert.pfx -CertStoreLocation Cert:\LocalMachine\My
-Import-PfxCertificate -FilePath .\winrmcacert.pfx -CertStoreLocation Cert:\LocalMachine\Root
-winrm create winrm/config/Listener?Address=*+Transport=HTTPS '@{Hostname="maas-win2k12r2";CertificateThumbprint="THUMBPRINT"}'
-</code>
-=== Note: ===
-Don't forget to add those **'** around the **@{}**.
-=== Now this should look like in the first powershell screenshot ===
-=== I can't stress enough this to make sure we can reach the listeners please add execute this lines.===
-<code powershell>
-netsh advfirewall firewall add rule name="Windows Remote Management (HTTPS-In)" dir=in action=allow protocol=TCP localport=5986
-winrm set winrm/config/service '@{AllowUnencrypted="true"}' # this will let us use the http listener with password auth
-</code>
-=== Now we should make the cert in pem format and copy just pem formated cert over the ubuntu machine ===
-<code powershell>
-C:\OpenSSL-Win64\bin\openssl.exe x509 -inform DER -in C:\Users\Administrator\cert -out outcert.pem -text
-cat outcert.pem
-</code>
-Copy the that starts with -----BEGIN CERTIFICATE----- and ends with -----END CERTIFICATE-----
-====== Step 3 ======
-You need to copy the newly **CA sever cert** on the controller(juju client) in a specific x509 config folder where juju will look on.
-You need to store the file with a specific name of **winrmcacert.crt**
-Please make sure that the CA cert is in pem format.
-<code bash>
-mkdir -p $HOME/.local/share/juju/x509
-# make here a quick copy of the CA cert because if something is broken juju will delete the x509 dir and regenerate all the client certs but not the CA.
-cp winrmcacert.crt $HOME/.local/share/juju/
-# in order to generate the client certs by juju you must hit the command
-juju status
-# now move the cacert into x509
-cp winrmcacert.crt $HOME/.local/share/juju/x509
-# If you have some custom client cert please rename them into winrmclientkey.pem and winrmclientcert.crt and move them into $HOME/.local/share/juju/x509
-# if you list the dirs you should have something like this.
-tree x509/
-x509/
-├── winrmcacert.crt
-├── winrmclientcert.crt
-└── winrmclientkey.pem
-</code>
-====== Step 4 ======
-( manual provisioning )
-We need to make a new environmnet frist. (juju bootstrap)
-<code bash>
-juju bootstrap manual/10.10.10.101 mymanual --debug --config agent-metadata-url=http://10.10.10.10/toolsdir/tools --config agent-stream=devel
-</code>
-{{:bootstrapconfigmanual.png?nolink|}}
-If you hit juju status we should have an environment set and ready.
-<code bash>
-juju status
-</code>
-{{:jujustatus.png?nolink|}}
-Now for the grand finale.
-<code bash>
-juju add-machine --debug winrm:Administrator@10.10.10.101
-</code>
-{{:winrmaddmachine.png?nolink|}}
-======= More helpfull commands ======
-<code powershell>
-$host = $env:COMPUTERNAME
-$Cert = New-SelfSignedCertificate -CertstoreLocation Cert:\LocalMachine\My -DnsName $host
-Export-Certificate -Cert $Cert -FilePath C:\Users\Administrator\cert
-Import-Certificate -Filepath "C:\Users\Administrator\cert" -CertStoreLocation "Cert:\LocalMachine\Root"
-Enable-PSRemoting -SkipNetworkProfileCheck -Force
-New-Item -Path WSMan:\LocalHost\Listener -Transport HTTPS -Address * -CertificateThumbPrint $Cert.Thumbprint –Force
-New-NetFirewallRule -DisplayName "Windows Remote Management (HTTPS-In)" -Name "Windows Remote Management (HTTPS-In)" -Profile Any -LocalPort 5986 -Protocol TCP
-Add-Content $Env:SystemRoot\system32\drivers\etc\hosts "192.168.100.102 $host"
-# now you must reboot the windows machine.
-</code>

Cloudbase Solutions Wiki

User Tools

Site Tools

Differences

Page Tools