Help – My Machine is Locked Down and I Can’t Install the IBM Cloud CLI Tool (Part2)!

IN MY LAST POST, I talked about how the ‘ibmcloud’ CLI tool is useful for development but that I had encountered a number of clients where they had not been able to install it because of an enterprise-wide lockdown on their machines, which meant they could not install any software. To this end, I created a Public Image Template of a simple Linux server, which such users can use to create a new VM in the IBM Cloud, to which they can ssh and use the CLI tool, as well as Docker.

Well, what about other tools? A typical user needs a number of tools to be really productive, so how about creating a Public Image Template that does just that? So that’s what I’ve done.

This time, the virtual machine is based on Windows Server 2016 and has the following installed:

  • The ibmcloud CLI
  • Anaconda (a Python environment)
  • js
  • Jupyter
  • Git
  • Atom

Rather than logging in with ssh, you can then Remote Desktop into the server, to use a graphical interface.

Using this Public Image Template is again, pretty simple; follow these steps:

  1. Log into your IBM Cloud account
  2. In the top left corner, click the ‘hamburger’ icon and select ‘Infrastructure’ from the drop-down menu (you can shortcut this step by just hitting control.bluemix.net)
  3. Click Devices -> Manage -> Images from the left-hand menu
  4. This will show your Image Templates. Where it says ‘Private Images’, select ‘Public Images’ from the drop-down
  5. Look for a template called Windows-Cloud-Developer-Server. Note, this page does not have a simple ‘search’ function, so it may be easier to order the templates by ‘Create Date’ (click on the heading) – the template was created on ‘2018-10-12’.
  6. Click on ‘Actions’ and select one of the ‘Order’ options. This will open an order form.
  7. Select the data centre where you would like the VM to reside. Normally, this would be the one closest to your physical location, or closest to your IBM Cloud deployment if they are different.
  8. Then pick a Flavour option. Remember that this is running Windows Server, so you may need a little more RAM. I tended to choose a Balanced instance with 2 vCPUs and 4GB RAM.
  9. Scroll to the bottom and click ‘Add to Order’
  10. This takes you to the ‘Check Out’ screen. Under the Advanced System Configuration settings, provide a hostname for your virtual server and a domain.
  11. Click the two check boxes to acknowledge T&Cs and License terms, then click Submit Order. At this point, your machine will start provisioning.
  12. Go back to your list of devices (click Devices -> Device List from the left-hand menu). You will see your machine is provisioning (denoted by a ‘clock face’ icon beside it.
  13. When the machine is provisioned, you will see a Public IP address (as well as a Private one) beside its name. Click on the name of the server.
  14. Log into the Windows server using Remote Desktop (or similar). The host is the public IP address.
  15. Provide the username and password for the user. The user is devuser and default password is devUSERPASSWORD! (case sensitive)

NOTE It is strongly recommended that you change the devuser password on your image, particularly if it persists for some time, since EVERY server created using this template will have this password as a default.

  1. You are now good to go! You can use the ibmcloud cli from a command prompt and if you click ‘Start’ you’ll find the other apps.

What does the image include?

The image includes the developer tools listed above. You can add more tools if you wish. Note that the image DOES NOT include any anti-virus software and the Windows Firewall is not activated.

Other Considerations

  1. Think about how long your Virtual Machine might be needed for. Could you save money by provisioning a new machine each time you need it (note it can take up to 20 minutes) or by using Transient Virtual Servers?
  2. If you need to lock down access to the VM, consider using Security Groups and restricting access to a set IP address range, for example.

More help

As before, you can find a full list of IBM Cloud CLI commands here

Cheers,

James

Advertisements

One thought on “Help – My Machine is Locked Down and I Can’t Install the IBM Cloud CLI Tool (Part2)!

  1. Pingback: Help – My Machine is Locked Down and I Can’t Install the IBM Cloud CLI Tool! | The IBM Cloud Digest

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.