13%
28.06.2011
0000 / 0000 2 512 10
07 AVAILABILITYZONE |- m1.xlarge 0000 / 0000 2 1024 20
08 AVAILABILITYZONE |- c1.xlarge 0000 / 0000 4 2048 20
Making Images
13%
28.11.2021
2
01 global:
02 scrape_interval: 15s
03 evaluation_interval: 15s
04
05 ########## ALERTING CONFIGURATION ##########
06
07 alerting:
08 alertmanagers:
09 - static_configs:
10 - targets:
11
13%
30.11.2025
06 I_T nexus information:
07 LUN information:
08 LUN: 0
09 Type: controller
10 SCSI ID: deadbeaf1:0
11 SCSI SN: beaf10
12 Size: 0
13
13%
14.03.2013
: 6
08 microcode : 0x60c
09 cpu MHz : 800.000
10 cache size : 6144 KB
11 physical id : 0
12 siblings : 2
13 core id : 0
14 cpu cores : 2
15 apicid
13%
07.01.2013
plugin for Amazon Simple Storage Service (Amazon S3)
20 - sftp plugin for SSH File Transfer Protocol
21 - ebs plugin for Elastic Block Storage
22 - local plugin for Local file system
23
13%
30.11.2025
.appengine.ext.webapp import template
07
08 class MyHandler(webapp.RequestHandler):
09 def get(self):
10 variable1 = "No"
11 variable2 = "Idea"
12
13 template_values = {
14 'firstname': variable1,
15
13%
07.06.2019
A common definition of a self-healing system is a set of servers that can detect a malfunction within its own operations and then repair any error(s) without outside intervention. "Repair
13%
21.08.2014
_wait_timeout": "30s",
08 "shutdown_command": "echo 'Done' | sudo -S shutdown -h now"
09 }],
10 "provisioners": [{
11 "type": "shell",
12 "inline": [
13 "sleep 30",
14 "sudo apt-get update",
15
13%
17.02.2015
service_description PING
11 check_command check_ping!100.0,20%!500.0,60%
12 }
13 define service{
14 use generic-service ; Name of service template to use
15
13%
30.11.2025
. In the test scenario, I defined a backup schedule with the following settings:
Schedule: weekly
Daily full backup: Monday – Friday 20:00
Daily incremental backup: Monday – Friday 08:00--18:00, 30
