
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Connector to the Xen API
Installation of the npm package:
npm install --save xen-api
Tested with:
const { createClient } = require('xen-api')
const xapi = createClient({
url: 'https://xen1.company.net',
allowUnauthorized: false,
auth: {
user: 'root',
password: 'important secret password',
},
readOnly: false,
})
Options:
url
: address of a host in the pool we are trying to connect toallowUnauthorized
: whether to accept self-signed certificatesauth
: credentials used to sign in (can also be specified in the URL)readOnly = false
: if true, no methods with side-effects can be calledcallTimeout
: number of milliseconds after which a call is considered failed (can also be a map of timeouts by methods)httpProxy
: URL of the HTTP/HTTPS proxy used to reach the host, can include credentials// Force connection.
xapi.connect().catch(error => {
console.error(error)
})
// Watch objects.
xapi.objects.on('add', objects => {
console.log('new objects:', objects)
})
Note: all objects are frozen and cannot be altered!
Custom fields on objects (hidden − ie. non enumerable):
$type
: the type of the object (VM
, task
, …);$ref
: the (opaque) reference of the object;$id
: the identifier of this object (its UUID if any, otherwise its reference);$pool
: the pool object this object belongs to.Furthermore, any field containing a reference (or references if an
array) can be resolved by prepending the field name with a $
:
console.log(xapi.pool.$master.$resident_VMs[0].name_label)
// vm1
A CLI is provided to help exploration and discovery of the XAPI.
> xen-api xen1.company.net root
Password: ******
root@xen1.company.net> xapi.status
'connected'
root@xen1.company.net> xapi.pool.master
'OpaqueRef:ec7c5147-8aee-990f-c70b-0de916a8e993'
root@xen1.company.net> xapi.pool.$master.name_label
'xen1'
You can optionally prefix the address by a protocol: https://
(default) or http://
.
In case of error due to invalid or self-signed certificates you can use the --allow-unauthorized
flag (or --au
):
> xen-api --au xen1.company.net root
To ease searches, find()
and findAll()
functions are available:
root@xen1.company.net> findAll({ $type: 'VM' }).length
183
To get a record from the local cache:
root@xen1.company.net> vm = getObject('17ccab66-9cc0-90a4-71a5-95874f9ad5e0')
root@xen1.company.net> vm.name_label
'My VM'
root@xen1.company.net> vm.$ref
'OpaqueRef:9a533a13-64bf-4755-ad6a-9b0f67d686ca'
To call a XAPI method:
root@xen1.company.net> call('VM.start', 'OpaqueRef:9a533a13-64bf-4755-ad6a-9b0f67d686ca', false, false)
''
root@xen1.company.net> vm.$call('start', false, false)
''
To call a XAPI method
Contributions are very welcomed, either on the documentation or on the code.
You may:
FAQs
Connector to the Xen API
The npm package xen-api receives a total of 72 weekly downloads. As such, xen-api popularity was classified as not popular.
We found that xen-api demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 10 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.