11%
02.06.2020
-to-end machine learning platform initially developed by the Google Brain team for internal Google use. The free and open source software library, released under Apache License 2.0 in 2015, allows a wide range
11%
07.06.2019
-p ${CASC_JENKINS_CONFIG} && mkdir -p ${JENKINS_HOME}/plugins && adduser -h ${JENKINS_HOME} -u ${UID} -s /bin/bash -D ${JENKINS_USER} && chown -R ${UID} ${JENKINS_HOME} ${CASC_JENKINS_CONFIG}
20
21
11%
02.02.2021
, such as a self-service portal for resetting user passwords or for additional authorization requests. A single sign-on based on modern protocols such as OpenID Connect or Security Assertion Markup Language 2.0
11%
11.10.2016
straightforward. If a processor was operating at a fixed frequency of 2.0GHz, CPU utilization was the percentage of time the processor spent doing work. (Not doing work is idle
time.) For 50% utilization
11%
11.10.2016
with the message:
10.0.0.1 - - [21/Dec/2015:05:46:30 -0500] "GET /tile-399.jpg HTTP/2.0" 200 846 "https://10.0.0.31/" ...
Figure 2: A blue lightning bolt icon
11%
28.11.2022
variant will do; it does not have to come from the official Microsoft Store [6]. Alternatively, the attacker can create their own Linux derivative for WSL with known threats and tools.
The command
PS
11%
08.07.2013
-party cloud technologies with the help of its Delta Cloud API.
After all, CloudForms 1.1, DeltaCloud 1.0, Storage Server 2.0, JBoss Middleware, and Enterprise Virtualization 3.1 form the foundation
11%
02.08.2021
-{{ openstack_release }}
cirros_deploy_image_upstream_url: https://share/ironic-ubuntu-osism-20.04.qcow2
dhcp_pool_start: 192.168.21.200
dhcp_pool_end: 192.168.21.250
dnsmasq_router: 192.168.21.254
domain: osism
11%
27.09.2021
in an automated process; the neutral inventory file gcp_hosts,
[gcp]
34.71.6.79 vmname=one privateip=10.128.0.20 purpose=database
34.66.26.41 vmname=two privateip=10.128.0.21 purpose=webserver
is also available
11%
26.03.2025
pods and schedules them in turn as resources that are released by the preceding completed pods. I'll demonstrate this by submitting (as simultaneously as possible) 20 two-CPU pods to the test cluster
