$ sips
sips 10.4.4 - scriptable image processing system.
This tool is used to query or modify raster image files and ColorSync ICC profiles.
Its functionality can also be used through the "Image Events" AppleScript suite.
Try 'sips --help' or 'sips --helpProperties' for help using this tool
$ find . -name "*.jpg" -exec sips -g pixelHeights -g pixelWidth {} \;
$ azure group create US westus --subscription MySubscription
info: Executing command group create
+ Getting resource group US
+ Creating resource group US
info: Created resource group US
data: Id: /subscriptions/MySubscription/resourceGroups/US
data: Name: US
data: Location: westus
data: Provisioning State: Succeeded
data: Tags: null
data:
info: group create command OK
$ azure network vnet create US USVirtualNetwork westus --subscription MySubscription
info: Executing command network vnet create
warn: Using default address prefix: 10.0.0.0/8
+ Looking up the virtual network "USVirtualNetwork"
+ Creating virtual network "USVirtualNetwork"
data: Id : /subscriptions/MySubscription/resourceGroups/US/providers/Microsoft.Network/virtualNetworks/USVirtualNetwork
data: Name : USVirtualNetwork
data: Type : Microsoft.Network/virtualNetworks
data: Location : westus
data: Provisioning state : Succeeded
data: Address prefixes:
data: 10.0.0.0/8
info: network vnet create command OK
$ azure network vnet subnet create US USVirtualNetwork default -a 10.1.0.0/16 --subscription MySubscription
info: Executing command network vnet subnet create
+ Looking up the virtual network "USVirtualNetwork"
+ Looking up the subnet "default"
+ Creating subnet "default"
data: Id : /subscriptions/MySubscription/resourceGroups/US/providers/Microsoft.Network/virtualNetworks/USVirtualNetwork/subnets/default
data: Name : default
data: Provisioning state : Succeeded
data: Address prefix : 10.1.0.0/16
info: network vnet subnet create command OK
$ azure storage account keys list myusstorageaccount --resource-group US --subscription MySubscription
info: Executing command storage account keys list
+ Getting storage account keys
data: Name Key Permissions
data: ---- -------------- -----------
data: key1 111111111111== Full
data: key2 222222222222== Full
info: storage account keys list command OK
$ AZURE_STORAGE_ACCOUNT=myusstorageaccount AZURE_STORAGE_ACCESS_KEY=111111111111== azure storage container create system
info: Executing command storage container create
+ Creating storage container system
+ Getting storage container information
data: {
data: name: 'system',
data: metadata: {},
data: etag: '"################"',
data: lastModified: 'Thu, 04 Aug 2016 12:01:14 GMT',
data: lease: { status: 'unlocked', state: 'available' },
data: requestId: '############################',
data: publicAccessLevel: 'Off'
data: }
info: storage container create command OK
$ AZURE_STORAGE_ACCOUNT=myusstorageaccount AZURE_STORAGE_ACCESS_KEY=111111111111== azure storage blob copy start https://sourceaccount.blob.core.windows.net/system/Microsoft.Compute/Images/vhds/my-vm-osDisk.12345-23456-34567-45678.vhd system -a sourceaccount -k sourceaccount_KEY
info: Executing command storage blob copy start
- Start copying blob https://sourceaccount.blob.core.windows.net/system/Microsoft.Compute/Images/vhds/my-vm-osDisk.12345-23456-34567-45678.vhd
data: Copy ID Status
data: ------------------------------------ -------
data: #################################### success
info: storage blob copy start command OK
$ AZURE_STORAGE_ACCOUNT=myusstorageaccount AZURE_STORAGE_ACCESS_KEY=111111111111== azure storage blob copy start https://sourceaccount.blob.core.windows.net/system/Microsoft.Compute/Images/vhds/my-vm-osDisk.12345-23456-34567-45678.vhd system
info: Executing command storage blob copy start
- Start copying blob https://sourceaccount.blob.core.windows.net/system/Microsoft.Compute/Images/vhds/my-vm-osDisk.12345-23456-34567-45678.vhd
data: Copy ID Status
data: ------------------------------------ -------
data: #################################### pending
info: storage blob copy start command OK
$ AZURE_STORAGE_ACCOUNT=myusstorageaccount AZURE_STORAGE_ACCESS_KEY=111111111111== azure storage blob show
info: Executing command storage blob show
Container name: system
Blob name: Microsoft.Compute/Images/vhds/my-vm-osDisk.12345-23456-34567-45678.vhd
+ Getting storage blob information
data: Property Value
data: ------------- ----------------------------------------------------------------------------------------------------
data: container system
data: name Microsoft.Compute/Images/vhds/my-vm-osDisk.12345-23456-34567-45678.vhd
data: blobType PageBlob
data: contentLength 1234567890
data: contentType application/octet-stream
data: contentMD5 ############==
info: storage blob show command OK
error: Deployment provisioning state was not successful
error: Source and destination storage accounts for disk my-vm-osDisk.12345-23456-34567-45678.vhd are different.
error: Deployment provisioning state was not successful
error: The resource operation completed with terminal provisioning state 'Failed'.
error: Disk image https://myusstorageaccount.blob.core.windows.net/system/Microsoft.Compute/Images/vhds/my-vm-osDisk.12345-23456-34567-45678.vhd is in Pending state. Please retry when image is ready.
$ azure network public-ip create US ip-my-server -l westus --subscription MySubscription
$ azure network nic create US nic-my-server -k default -m USVirtualNetwork -l westus --subscription MySubscription
$ azure network nic create US nic-my-server -k default -m USVirtualNetwork -l westus --subscription MySubscription -p ip-my-server
$ azure group deployment create US -f my-servier-template.json --subscription MySubscription -p '{"vmName":{"value":"my-server"},"networkInterfaceId":{"value":"/subscriptions/MySubscription/resourceGroups/US/providers/Microsoft.Network/networkInterfaces/nic-my-server"}}'
$ jq '' < MyImageName-old.json > old-formated.json
$ jq '' < MyImageName-Date.json > date-formated.json
$ vimdiff old-formated.json date-formated.json
$ mv old-formated.json MyImageName-Date-formated.json
$ azure group deployment create MyResource -f MyImageName-Date-formated.json --subscription MySubscription
$ sudo waagent -deprovision+user
移除 SSH 主機金鑰 (如果組態檔中的 Provisioning.RegenerateSshHostKeyPair 是 'y')
清除 /etc/resolv.conf 中的名稱伺服器設定
移除 /etc/shadow 中的 root 使用者密碼 (如果組態檔中的 Provisioning.DeleteRootPassword 是 'y')
移除快取的 DHCP 用戶端租用
將主機名稱重設為 localhost.localdomain
刪除最後佈建的使用者帳戶 (取自於 /var/lib/waagent) 和相關聯的資料。
$ azure config mode arm
info: Executing command config mode
info: New mode is arm
info: config mode command OK
// Shutdown a virtual machine in a resource group and release the compute resources
$ azure vm deallocate -g MyResource -n MyCurrentVM --subscription MySubscription
info: Executing command vm deallocate
+ Looking up the VM "MyCurrentVM"
+ Deallocating the virtual machine "MyCurrentVM"
info: vm deallocate command OK
// Set the state of a VM in a resource group to Generalized.
$ azure vm generalize MyResource MyCurrentVM --subscription MySubscription
info: Executing command vm generalize
+ Looking up the VM "MyCurrentVM"
+ Generalizing the virtual machine "MyCurrentVM"
info: vm generalize command OK
$ azure vm capture MyResource MyCurrentVM MyImageID -t MyImageID-base.json --subscription MySubscription
info: Executing command vm capture
+ Looking up the VM "MyCurrentVM"
+ Capturing the virtual machine "MyCurrentVM"
info: Saved template to file "MyImageID-base.json"
info: vm capture command OK
$ azure network public-ip create MyResource MyImageID-ip-1 -l westus --subscription MySubscription
info: Executing command network public-ip create
warn: Using default --idle-timeout 4
warn: Using default --allocation-method Dynamic
warn: Using default --ip-version IPv4
+ Looking up the public ip "MyImageID-ip-1"
+ Creating public ip address "MyImageID-ip-1"
data: Id : /subscriptions/MySubscription/resourceGroups/MyResource/providers/Microsoft.Network/publicIPAddresses/MyImageID-ip-1
data: Name : MyImageID-ip-1
data: Type : Microsoft.Network/publicIPAddresses
data: Location : westus
data: Provisioning state : Succeeded
data: Allocation method : Dynamic
data: IP version : IPv4
data: Idle timeout in minutes : 4
info: network public-ip create command OK
$ azure network nic create MyResource MyImageID-nic-1 -k default -m MyResource -p MyImageID-ip-1 -l westus --subscription MySubscription
info: Executing command network nic create
+ Looking up the network interface "MyImageID-nic-1"
+ Looking up the subnet "default"
+ Looking up the public ip "MyImageID-ip-1"
+ Creating network interface "MyImageID-nic-1"
data: Id : /subscriptions/MySubscription/resourceGroups/MyResource/providers/Microsoft.Network/networkInterfaces/MyImageID-nic-1
data: Name : MyImageID-nic-1
data: Type : Microsoft.Network/networkInterfaces
data: Location : westus
data: Provisioning state : Succeeded
data: Internal domain name suffix : #############.dx.internal.cloudapp.net
data: Enable IP forwarding : false
data: IP configurations:
data: Name : default-ip-config
data: Provisioning state : Succeeded
data: Private IP address : 10.0.0.6
data: Private IP version : IPv4
data: Private IP allocation method : Dynamic
data: Public IP address : /subscriptions/MySubscription/resourceGroups/MyResource/providers/Microsoft.Network/publicIPAddresses/MyImageID-ip-1
data: Subnet : /subscriptions/MySubscription/resourceGroups/MyResource/providers/Microsoft.Network/virtualNetworks/MyResource/subnets/default
data:
info: network nic create command OK
$ azure --version
0.10.2 (node: 4.2.4)
$ azure group deployment create MyResource -f MyImageID-base.json --subscription MySubscription
$ azure group deployment create MyResource -f MyImageID-base.json --subscription MySubscription -p '{"vmName":{"value":"MyVM"},"adminUserName":{"value":"ubuntu"},"adminPassword":{"value":"MyPassword"},"networkInterfaceId":{"value":"/subscriptions/MySubscription/resourceGroups/MyResource/providers/Microsoft.Network/networkInterfaces/MyImageID-nic-base"}}'
$ cat template.json | jq '.parameters'
{
"vmName": {
"type": "string"
},
"vmSize": {
"type": "string",
"defaultValue": "Standard_A1"
},
"adminUserName": {
"type": "string"
},
"adminPassword": {
"type": "securestring"
},
"networkInterfaceId": {
"type": "string"
}
}
$ cat template.json | jq '.resources[0].properties.osProfile'
{
"computerName": "[parameters('vmName')]",
"adminUsername": "[parameters('adminUsername')]",
"adminPassword": "[parameters('adminPassword')]"
}
$ cat template.json | jq '.parameters'
{
"vmName": {
"type": "string"
},
"vmSize": {
"type": "string",
"defaultValue": "Standard_A1"
},
"adminUserName": {
"type": "string"
},
"adminPassword": {
"type": "securestring",
"defaultValue": null
},
"networkInterfaceId": {
"type": "string"
},
"adminPublicKey": {
"type": "array"
},
"adminPublicKeyPath": {
"type": "string"
}
}
$ cat template.json | jq '.resources[0].properties.osProfile'
{
"computerName": "[parameters('vmName')]",
"adminUsername": "[parameters('adminUsername')]",
"adminPassword": "[parameters('adminPassword')]",
"linuxConfiguration": {
"disablePasswordAuthentication": true,
"ssh": {
"publicKeys": [
{
"path": "[parameters('adminPublicKeyPath')]",
"keyData": "[parameters('adminPublicKey')]"
}
]
}
}
}
$ azure group deployment create MyResource -f MyImageID-base.json --subscription MySubscription -p '{"adminPassword":{"value":""},"vmName":{"value":"MyVM"},"adminUserName":{"value":"ubuntu"},"adminPublicKey":{"value":"ssh-rsa ########"},"adminPublicKeyPath":{"value":"/home/ubuntu/.ssh/authorized_keys"},"networkInterfaceId":{"value":"/subscriptions/MySubscription/resourceGroups/MyResource/providers/Microsoft.Network/networkInterfaces/MyImageID-nic-base"}}'
New -> Virtual machine -> Create -> 基本設定後, 在第三步 Settings - Availability 項目中，可以指定 Availability Set。建置完後，緊接著建立 Load Balancer，建完後在其 Load Balancer -> Settings -> Backend pools -> Add a virtual machine -> Availability Set -> 挑選剛剛建立的 Availability Set（若 Set 裡沒機器，則會無法挑選！）-> 挑選裡頭的機器！
Load Balancer -> Settings -> Probes: 這就像 AWS Load Balancer 檢查某端口服務是否正常
Load Balancer -> Settings -> Load balancing rules: 正式把 requests 導向給後端機器群
Network security group -> Settings -> Inbound security rules (有需要可以在設定 Outbound security group)，例如預設有開通 22 port ，此時就只需再添加 80, 443 port如此一來，當 Load balancer 的 probes 檢驗通常順暢後，就可以對 load balancer 送資料試試了。