installation-powershell-core-and-powercli-10-on-debian-or-ubuntu

Some of you know that already, but the latest PowerCLI 10 release works very nice with PowerShell Core that can be installed on Linux.

That is an amazing step forward to simplify reporting and automation without the requirement of a running Microsoft Windows system – means, no license questions and flexible ways of distribution.

Let´s directly get into it and start with a Debian system.

Installation PowerShell Core

To install the PowerShell Core you should visit the main project site and download the corresponding linux package. For this blog post I have a Debian 8 system, but you can just download the project that fits your system.

Download PowerShell Core

Visit https://github.com/PowerShell/PowerShell and download the file or just use wget:

wget https://github.com/PowerShell/PowerShell/releases/download/v6.0.2/powershell_6.0.2-1.debian.8_amd64.deb

# Install the debian package

sudo dpkg -i powershell_6.0.2-1.debian.8_amd64.deb

If you haven´t already installed some less common packages, you´ll end up with an installation error that some packages are missing:

Installation Error PowerShell Core

Luckily installing the dependent packages is absolutely straightforward:

sudo apt-get -f install

After apt-get installed all the missing packages, you can run the dpkg -i powershell*.deb command again and all should work fine.

pwsh to start PowerShell Core

You can start the PowerShell using the command pwsh

get-host shows you the current version of the installed PowerShell Core.

Installation PowerCLI 10

The PowerCLI project website can be found here: https://code.vmware.com/tool/vmware-powercli/10.0.0

To install the PowerCLI 10, you just need to open the PowerShell with the pwsh command and run a install-module:

# either for the system – you need higher permissions of course

Install-Module -Name VMware.PowerCLI

# or for the current logged in user

Install-Module -Name VMware.PowerCLI -Scope CurrentUser

The installation takes a while and you need to agree to trust the PSGallery modules, as PowerCLI is one of them.

Many customers run VMware vCenter with self-signed or even invalid certificates, therefore if you´re one of them make sure to run the following PowerCLI Configuration command before connecting to any vCenter server:

Set-PowerCLIConfiguration -InvalidCertificateAction Ignore

PowerCLI 10 linux

First commands

That was already it, PowerShell Core and PowerCLI 10 are installed and we can connect to a VMware vCenter or ESXi host.

Connect to a vCenter:

Connect-VIServer vcenter.dns.name -user -pass

vCenter connection PowerCLI

Get-VM shows the virtual machines, Get-VMHost the ESXi hosts managed by vCenter. There are so many cmdlets and possibilities now – just amazing.

Exceptions:

The PowerShell is extremely tolerant when it comes to syntax and shortcuts. On a Linux system that can be annoying, especially if you´re not familiar with Linux vs. PowerShell commands.

As a rule of thumb – make sure not to use any system commands that are also PowerShell shortcuts, i. e. sort-object instead of sort.

If you don´t use sort-object, the linux sort command will be used by the PowerShell and you typically run into issues. Use the full cmdlet names and no alias and you will be on the safe side.

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.