24%
05.02.2019
of Listing 1, schemaVersion: "2.0.0" reveals that the test descriptions that follow use the 2.0.0 schema. Without this information, the tool immediately denies service.
Under globalEnvVars (lines 3-7; note
24%
06.10.2019
).
Figure 1: NSGs are used to bundle resources and define and control network traffic.
Creating NSGs
You can define up to 100 NSGs per Azure subscription, with Azure Support increasing the limit to 200
24%
14.09.2021
$(find /sys/devices/system/cpu -regex ".*cpu[0-9]+/topology/thread_siblings_list") | sort -n | uniq
0,32
1,33
2,34
3,35
4,36
5,37
6,38
7,39
8,40
9,41
10,42
11,43
12,44
13,45
14,46
15,47
16,48
17,49
18,50
19,51
20,52
21,53
22,54
23,55
24,56
25
24%
01.04.2014
bootstrapping of its own local cloud, which does not require access to a public cloud provider and thus imposes very few requirements.
The Cloudify tarball is a heavyweight at 160MB, but the user initially only
24%
30.01.2024
the performance limit. The network in particular has seen major innovations in recent years, including the now widely available 400Gb Ethernet, which has quickly passed the buck back to storage devices
24%
05.12.2016
. The holdingdisk section (lines 22 to 26) specifies the key data for such a holding disk. In Listing 1, Amanda is allowed to cache data in the /amanda/holding directory, where it can use a maximum of 50MB space; any
24%
28.11.2021
, a backup occupies only about 400MB, but including server daemons and developer tools can quickly expand this file to several gigabytes.
Integrating Server Daemons
If you need to expand the development
24%
07.10.2014
and the other on all IPv6 IP addresses.
Listing 1
Checking Open Ports
chris@DebianBox:~# lsof -i :22
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sshd 3328 root 3r IPv4 33323 0t0 TCP *:ssh
24%
16.10.2012
bytes:215392635 (215.3 MB) TX bytes:1759757 (1.7 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK
24%
21.08.2012
=/vnfs
The VNFS grew a little bit in size from the ganglia additions to 72.3MB, which is still pretty small.
Now I can boot the compute node. Once it comes up (check this by ssh
ing to the node as a user
