diff --git a/ci/vale/dictionary.txt b/ci/vale/dictionary.txt index d321b05f28c..52c36b5684f 100644 --- a/ci/vale/dictionary.txt +++ b/ci/vale/dictionary.txt @@ -888,6 +888,8 @@ ossec ostemplate osx otomen +outputter +outputters overcommit overwatch ovpn @@ -985,6 +987,7 @@ psql psudo psycop2 pty +pubkey publickey puppetd puppetmaster @@ -1178,6 +1181,7 @@ sparklines spectre speedtest spf1 +spm spork sql sqlplus diff --git a/docs/applications/configuration-management/salt-command-line-reference/index.md b/docs/applications/configuration-management/salt-command-line-reference/index.md new file mode 100644 index 00000000000..4fd3e6560ab --- /dev/null +++ b/docs/applications/configuration-management/salt-command-line-reference/index.md @@ -0,0 +1,299 @@ +--- +author: + name: Linode Community + email: docs@linode.com +description: 'A reference for the SaltStack command line interface.' +keywords: ['salt','saltstack','cli','command line','reference'] +license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' +published: 2018-10-03 +modified: 2018-10-03 +modified_by: + name: Linode +title: "SaltStack Command Line Reference" +contributor: + name: "Andy Stevens" + link: "https://github.com/andystevensname" +external_resources: +- '[SaltStack Command Line Documentation](https://docs.saltstack.com/en/latest/ref/cli/index.html)' +- '[Linode Cloud Module](https://docs.saltstack.com/en/latest/ref/clouds/all/salt.cloud.clouds.linode.html)' +--- + +[SaltStack](https://github.com/saltstack/salt) is a powerful configuration management tool. The following is a quick-reference guide for Salt's command line interface (CLI). + +## salt + +Used to issue commands to minions in parallel. `salt` allows you to both control and query minions. + +|Option|Description|Example| +|------|-----------|-------| +|`--version`|Get the current version of Salt.|`salt --version`| +|`-h`, `--help`|Display Salt commands and help text.|`salt -h`| +|`-c`, `--config-dir`|Change the Salt configuration directory. The default is `/etc/salt`.|`salt -c /home/salt/conf test.ping`| +|`-s`, `--static`|Only return data after all minions have returned.|`salt --static`| +|`--async`|Instead of waiting for a job on a minion or minions, print the job ID and the job completion.|`salt '*' pkg.install apache2 --async`| +|`--subset`|Execute commands on a random subset of minions.|`salt '*' telegram.post_message message="Hello random 3!" --subset 3`| +|`-v`, `--verbose`|Print extra data, such as the job ID.|`salt 'minion1' user.add steve --verbose`| +|`--hide-timeout`|Only print minions that can be reached.|`salt '*' test.ping --hide-timeout`| +|`-b`, `--batch-size`|Execute on a batch or percentage of minions.|`salt '*' test.ping --batch-size 25%`| +|`-a`, `--auth`|Use an external authentication medium. You will be prompted for credentials. Options are `auto`, `keystone`, `ldap`, and `pam`. Can be used with `-T`.|`salt -a pam '*' status.meminfo`| +|`-T`, `--make-token`|Used with `-a`. Creates an authentication token in the active user's home directory that has a default 12 hour expiration time. Token expiration time is set in the Salt master config file.|`salt -T -a pam '*' status.cpuinfo`| +|`--return`|Used to select an alternative returner. Options are `carbon`, `cassandra`, `couchbase`, `couchdb`, `elasticsearch`, `etcd`, `hipchat`, `local`, `local_cache`, `memcache`, `mongo`, `mysql`, `odbc`, `postgres`, `redis`, `sentry`, `slack`, `sms`, `smtp`, `sqlite3`, `syslog`, and `xmpp`.|`salt '*' status.all_status --return mongo`| +|`-d`, `--doc`, `--documentation`|Return all available documentation for a module function, or all functions if one is not provided.|`salt 'minion3' service.available -d`| +|`-l`, `--log-level`|Change console log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`salt 'minion2' state.apply -l info`| +|`--log-file`|Change the log file path. Defaults to `/var/log/salt/master`|`salt '*' test.ping --log-file /home/salt/log`| +|`--log-file-level`|Change the logging level of the log file. Same options as `--log-level`|`salt '*' test.ping --log-level all`| +|`-E`, `--pcre`|Target expression will be interpreted as a Perl Compatible Regular Expression (PCRE) rather than a shell glob.|`salt -E 'minion[0-9]' service.reload apache2`| +|`-L`, `--list`|Target expression will be interpreted as a comma-delimited list.|`salt -L 'minion1,minion2' service.show sshd`| +|`-G`, `--grain`|Target expression in the form of a glob expression matches a Salt grain. <grain value>:<glob expression>.|`salt -G 'os:Ubuntu' service.available mysql`| +|`--grain-pcre`|Target expression in the form of a Perl Compatible Regular Expression matches values returned by Salt grains on the minion.<grain value>:<regular expression>|`salt --grain-pcre 'os:Arch' service.restart apache2`| +|`-I`, `--pillar`| Use pillar values instead of shell globs to identify targets.|`salt -I 'role:production' test.echo 'playback'`| +|`--out`| Choose an alternative outputter to display returned data. Available outputters are: `grains`, `highstate`, `json`, `key`, `overstatestage`, `pprint`, `raw`, `txt`, `yaml`. Note: when using `--out json` you will probably want to also use `--static`.| `salt '*' test.version --out json --static`| + + +## salt-call + +Runs module functions on a minion instead of the master. It is used to run a standalone minion. + +|Option|Description|Example| +|------|-----------|-------| +|`--version`|Get the current version of Salt.|`salt-call --version`| +|`-h`, `--help`|Display Salt commands and help text.|`salt-call -h`| +|`-c`, `--config-dir`|Change the Salt configuration directory. The default is `/etc/salt`.|`salt-call -c /home/salt/conf test.ping`| +|`-g`, `--grains`|Get the information generated by the Salt grains.|`salt-call --grains`| +|`-m`, `--module-dirs`|Select an additional modules directory. You can provide this option multiple times for multiple directories.|`salt-call -m /home/salt/modules1 -m /home/salt/modules2`| +|`-d`, `--doc`, `--documentation`|Return all available documentation for module function, or all functions if one is not provided.|`salt-call system.get_system_time -d`| +|`--master`|Choose which master to use. The minion must be authenticated with the master. If the master is omitted, the first master in the minion config will be used.|`salt-call --master master1`| +|`--return`|Used to select an alternative returner. Options are `carbon`, `cassandra`, `couchbase`, `couchdb`, `elasticsearch`, `etcd`, `hipchat`, `local`, `local_cache`, `memcache`, `mongo`, `mysql`, `odbc`, `postgres`, `redis`, `sentry`, `slack`, `sms`, `smtp`, `sqlite3`, `syslog`, and `xmpp`.|`salt-call --return mongo status.all_status`| +|`--local`|Run Salt as if there was no master running.|`salt-call --local system.get_system_time`| +|`--file-root`|Set a directory as the base file directory.|`salt-call --file-root /home/salt`| +|`--pillar-root`|Set a directory as the base pillar directory.|`salt-call --file-root /home/salt/pillar`| +|`-l`, `--log-level`|Change console log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`salt-call -l all test.exception 'oh no!'`| +|`--log-file`|Change log file path. Defaults to `/var/log/salt/minion`.|`salt-call --logfile /home/salt/log/minion test.exception 'oh no!'`| +|`--log-file-level`|Change logfile log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`salt-call --log-file-level all test.exception 'oh no!'`| +|`--out`| Choose an alternative outputter to display returned data. Available outputters are: `grains`, `highstate`, `json`, `key`, `overstatestage`, `pprint`, `raw`, `txt`, `yaml`.| `salt-call test.version --out json`| + +## salt-cloud + +Used to provision virtual machines on public clouds with Salt. + +|Option|Description|Example| +|------|-----------|-------| +|`--version`|Get the current version of Salt.|`salt-cloud --version`| +|`-h`, `--help`|Display Salt commands and help text.|`salt-cloud -h`| +|`-c`, `--config-dir`|Change the Salt configuration directory. The default is `/etc/salt`.|`salt-cloud -c /home/salt/conf`| +|`-a`, `--action`|Perform a cloud provider specific action. Requires an instance.|`salt-cloud -a reboot testlinode`| +|`-f`, `--function`|Perform a cloud provider specific function that does not apply to an instance. Requires a provider.|`salt-cloud -f clone my-linode-config linode_id=1234567 datacenter_id=2 plan_id=5`| +|`-p`, `--profile`|Choose a profile from which to build cloud VMs.|`salt-cloud -p linode-1024 mynewlinode`| +|`-m`, `--map`|Choose a map file from which to create your VMs. If a VM exists it will be skipped.|`salt-cloud -m /path/to/map`| +|`-H`, `--hard`|Used when creating VMs with a map file. If set, will destroy all VMs not listed in the map file.|`salt-cloud -m /path/to/map -H`| +|`-d`, `--destroy`|Destroy the named VMs. Can be used with `-m` to provide a map of VMs to destroy.|`salt-cloud -m /path/to/map -d`| +|`-P`, `--parallel`|Build VMs in parallel.|`salt-cloud -P -p linode-profile newlinode1 newlinode2`| +|`-u`, `--update-boostrap`|Update salt-bootstrap.|`salt-cloud -u`| +|`-y`, `--assume-yes`|Answer yes to all questions.|`salt-cloud -y -d linode1 linode2`| +|`-k`, `-keep-tmp`|Do not remove /tmp files.|`salt-cloud -k -m /path/to/map`| +|`--show-deploy-args`|Include deployment arguments in the return data.|`salt-cloud --show-deploy-args -m /path/to/map`| +|`--script-args`|Arguments to be passed to the bootstrap script when deploying.|`salt-cloud -m /path/to/map --script-args '-h'`| +|`-Q`, `--query`|Query nodes running on configured cloud providers.|`salt-cloud -Q`| +|`-F`, `--full-query`|Query VMs and print all available information. Can be used with -m to provide a map.|`salt-cloud -F`| +|`-S`, `--select-query`|Query VMs and print selected information. Can be used with -m to provide a map.|`salt-cloud -S`| +|`--list-providers`|Display a list of configured providers.|`salt-cloud --list-providers`| +|`--list-profiles`|Display a list of configured profiles. Supply a cloud provider, such as `linode`, or pass `all` to view all configured profiles.|`salt-cloud --list-profiles linode`| +|`--list-locations`|Display a list of available locations. Supply a cloud provider, such as `linode`, or pass `all` to view all location for configured profiles.|`salt-cloud --list-locations linode`| +|`--list-images`|Display a list of available images. Supply a cloud provider, such as `linode`, or pass `all` to view all images for configured profiles.|`salt-cloud --list-images linode`| +|`--list-sizes`|Display a list of available sizes. Supply a cloud provider, such as `linode`, or pass `all` to view all sizes for configured profiles.|`salt-cloud --list-sizes linode`| +|`--out`| Choose an alternative outputter to display returned data. Available outputters are: `grains`, `highstate`, `json`, `key`, `overstatestage`, `pprint`, `raw`, `txt`, `yaml`.| `salt-call test.version --out json`| + + +## salt-cp + +Used to copy files from the master to all Salt minions that match a specific target expression. + +|Option|Description|Example| +|------|-----------|-------| +|`--version`|Get the current version of Salt.|`salt-cp --version`| +|`-h`, `--help`|Display Salt commands and help text.|`salt-cp -h`| +|`-c`, `--config-dir`|Change the Salt configuration directory. The default is `/etc/salt`.|`salt-cp '*' -c /home/salt/conf /file/to/copy /destination`| +|`-t`, `--timeout`|The amount of seconds to wait for replies from minions. The default is 5 seconds.|`salt-cp '*' -t 25 /file/to/copy /destination`| +|`-l`, `--log-level`|Change console log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`salt-cp '*' -l all /file/to/copy /destination`| +|`--log-file`|Change log file path. Defaults to `/var/log/salt/master`.|`salt-cp '*' --logfile /home/salt/log/minion /file/to/copy /destination`| +|`--log-file-level`|Change logfile log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`salt-cp '*' --log-file-level all /file/to/copy /destination`| +|`-E`, `--pcre`|Target expression will be interpreted as a Perl Compatible Regular Expression (PCRE) rather than a shell glob.|`salt-cp -E 'minion[0-9]' /file/to/copy /destination`| +|`-L`, `--list`| Target expression will be interpreted as a comma-delimited list.|`salt -L 'minion1,minion2' /file/to/copy /destination`| +|`-G`, `--grain`|Target expression matches a Salt grain. <grain value>:<glob expression>.|`salt -G 'os:Ubuntu' /file/to/copy /destination`| +|`--grain-pcre`|Target expression in the form of a Perl Compatible Regular Expression matches values returned by Salt grains on the minion.<grain value>:<regular expression>|`salt-cp --grain-pcre 'os:Arch' /file/to/copy /destination`| +|`-C`, `--chunked`|Use chunked mode to copy files. Supports large files, recursive directories copying and compression.|`salt-cp -C /some/large/file /destination`| +|`-n`, `--no-compression`|Disable gzip in chunked mode.|`salt-cp -C -n /some/large/file /destination`| + +## salt-key + +Used to manage the Salt server public keys. + +|Option|Description|Example| +|------|-----------|-------| +|`--version`|Get the current version of Salt.|`salt-key --version`| +|`-h`, `--help`|Display Salt commands and help text.|`salt-key -h`| +|`-c`, `--config-dir`|Change the Salt configuration directory. The default is `/etc/salt`.|`salt-key -c /home/salt/conf`| +|`-u`, `--user`|Supply a user to run salt-key.|`salt-key --user steven`| +|`-q`, `--quiet`|Suppress output|`salt-key -q`| +|`-y`, `--yes`|Answer yes to all questions. Default is `False`.|`salt-key -y True`| +|`--rotate-aes-key`|Setting to `False` prevents the key session from being refreshed when keys are deleted or rejected. Default is `True`.|`salt-key --rotate-aes-key False`| +|`--log-file`|Change log file path. Defaults to `/var/log/salt/minion`.|`salt-key --logfile /home/salt/log/minion -D`| +|`--log-file-level`|Change logfile log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`salt-key --log-file-level all --accept '*'`| +|`-l`, `--list`|List public keys. `pre`, `un`, and `unaccepted` will list unaccepted/unsigned keys. `acc` or `accepted` will list accepted/signed keys. `rej` or `rejected` will list rejected keys. `all` will list all keys.|`salt-key -l all`| +|`-a`, `--accept`|Accept a public key. Globs are supported.|`salt-key --accept 'minion*'`| +|`-A`, `--accept-all`|Accept all pending keys.|`salt-key -A`| +|`-r`, `--reject`|Reject a specific key. Globs are supported.|`salt-key -r 'minion*'`| +|`-R`, `--reject-all`|Reject all pending keys.|`salt-key -R`| +|`--include-all`|Include non-pending keys when accepting and rejecting.|`salt-key -r 'minion*' --include-all`| +|`-p`, `--print`|Print a public key.|`salt-key --print 'minion1'`| +|`-d`, `--delete`|Delete a public key. Globs are supported.|`salt-key -d 'minion*'`| +|`-D`, `--delete-all`|Delete all public keys.|`salt-key --delete-all -y`| +|`-f`, `--finger`|Print a key's fingerprint.|`salt-key --finger 'minion1'`| +|`-F`, `--finger-all`|Print all keys' fingerprints.|`salt-key --F`| +|`--gen-keys`|Set a name to generate a key-pair.|`salt-key --gen-keys newminion`| +|`--gen-keys-dir`|Choose where to save newly generated key-pairs. Only works with `--gen-keys`.|`salt-key --gen-keys newminion --gen-keys-dir /home/salt/keypairs`| +|`--keysize`|Set the keysize for a generated key. Must be a value of 2048 or higher. Only works with `--gen-keys`.|`salt-key --gen-keys newminion --keysize 4096`| +|`--gen-signature`|Create a signature for the master's public key named master_pubkey_signature. This requires a new-signing-keypair which can be created with the `--auto-create` option.|`salt-key --gen-signature --auto-create`| +|`--priv`|The private-key file with which to create a signature.|`salt-key --priv key.pem`| +|`--signature-path`|The file path for the new signature.|`salt-key --gen-signature --auto-create --signature-path /path/to/signature`| +|`--pub`|The public-key file with which to create a signature.|`salt-key --gen-signature key.pub`| +|`--auto-create`|Auto-create a signing key-pair.|`salt-key --gen-signature --auto-create`| + +## salt-master + +A daemon used to control Salt minions. + +|Option|Description|Example| +|------|-----------|-------| +|`--version`|Get the current version of Salt.|`salt-master --version`| +|`-h`, `--help`|Display Salt commands and help text.|`salt-master -h`| +|`-c`, `--config-dir`|Change the Salt configuration directory. The default is `/etc/salt`.|`salt-master -c /home/salt/conf`| +|`-u`, `--user`|Supply a user to run salt-master.|`salt-master --user steven`| +|`-d`, `--daemon`|Run salt-master as daemon.|`salt-master -d`| +|`--pid-file`|Specify the file path of the pidfile. Default is `/var/run/salt-master.pid`|`salt-master --pid-file /path/to/new/pid`| +|`-l`, `--log-level`|Change console log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`salt-master -l info`| +|`--log-file`|Change the log file path. Defaults to `/var/log/salt/master`|`salt-master --log-file /home/salt/log`| +|`--log-file-level`|Change the logging level of the log file. Same options as `--log-level`|`salt-master --log-level all`| + +## salt-minion + +A daemon that is controlled by a Salt master. + +|Option|Description|Example| +|------|-----------|-------| +|`--version`|Get the current version of Salt.|`salt-minion --version`| +|`-h`, `--help`|Display Salt commands and help text.|`salt-minion -h`| +|`-c`, `--config-dir`|Change the Salt configuration directory. The default is `/etc/salt`.|`salt-minion -c /home/salt/conf`| +|`-u`, `--user`|Supply a user to run salt-minion.|`salt-minion --user steven`| +|`-d`, `--daemon`|Run salt-minion as daemon.|`salt-minion -d`| +|`--pid-file`|Specify the file path of the pidfile. Default is `/var/run/salt-minion.pid`|`salt-minion --pid-file /path/to/new/pid`| +|`-l`, `--log-level`|Change console log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`salt-master -l info`| +|`--log-file`|Change the log file path. Defaults to `/var/log/salt/minion`|`salt-minion --log-file /home/salt/log`| +|`--log-file-level`|Change the logging level of the log file. Same options as `--log-level`|`salt-minion --log-level all`| + +## salt-run + +Runs a Salt runner on a Salt master. + +|Option|Description|Example| +|------|-----------|-------| +|`--version`|Get the current version of Salt.|`salt-run --version`| +|`-h`, `--help`|Display Salt commands and help text.|`salt-run -h`| +|`-c`, `--config-dir`|Change the Salt configuration directory. The default is `/etc/salt`.|`salt-run -c /home/salt/conf foo.bar`| +|`-t`, `--timeout`|The amount of seconds to wait for replies from minions. The default is 5 seconds.|`salt-run -t 25 foo.bar`| +|`-d`, `--doc`, `--documentation`|Return all available documentation for a module or runner.|`salt-run foo.bar -d`| +|`-l`, `--log-level`|Change console log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`salt-run -l info foo.bar`| +|`--log-file`|Change the log file path. Defaults to `/var/log/salt/master`|`salt-minion --log-file /home/salt/log foo.bar`| +|`--log-file-level`|Change the logging level of the log file. Same options as `--log-level`|`salt-minion --log-level all foo.bar`| + +## salt-ssh + +Use SSH transport to execute salt routines. + +|Option|Description|Example| +|------|-----------|-------| +|`--version`|Get the current version of Salt.|`salt-ssh --version`| +|`-h`, `--help`|Display Salt commands and help text.|`salt-ssh -h`| +|`-c`, `--config-dir`|Change the Salt configuration directory. The default is `/etc/salt`.|`salt-ssh '*' -c /home/salt/conf test.ping`| +|`-r`, `--raw`, `--raw-shell`|Run a raw shell command.|`salt-ssh '*' -r echo 'test'`| +|`--roster`|Choose which roster system to use. The default is the flat file roster.|`salt-ssh '192.168.0.0/16' --roster scan pkg.install apache2`| +|`--roster-file`|Change the roster file directory. The default is the same directory as the master config file.|`salt-ssh 'minion1' --roster-file /path/to/roster test.ping`| +|`--refresh`, `--refresh-cache`|Use to force refresh the target's data in the master side cache before the auto refresh timeframe has been reached.|`salt-ssh 'minion1' --refresh-cache status.diskstats`| +|`--max-procs`|The number of minions to communicate with concurrently. In general, more connections mean faster communication. Default is 25.|`salt-ssh '*' --max-procs 50 test.ping`| +|`-v`, `--verbose`|Display job ID.|`salt-ssh '*' -v test.ping`| +|`-s`, `--static`|Return minion data as a grouping.|`salt-ssh '*' -s status.meminfo`| +|`-w`, `--wipe`|Remove Salt files when the job is done.|`salt-ssh '*' -w state.apply`| +|`-W`. `--rand-thin-dir`|Deploys to a random temp directory and cleans the directory when done.|`salt-ssh '*' -W state.apply`| +|`--python2-bin`|File path to a python2 binary which has Salt installed.|`salt-ssh '*' --python2-bin /file/to/bin test.ping`| +|`--python3-bin`|File path to a python3 binary which has Salt installed.|`salt-ssh '*' --python3-bin /file/to/bin test.ping`| +|`--jid`|Supply a job ID instead of generating one.|`salt-ssh '*' -v --jid 00000000000000000000 test.ping`| +|`--priv`|Supply which SSH private key to use for authentication.|`salt-ssh '*' --priv /path/to/privkey status.netstats`| +|`-i`, `--ignore-host-keys`|Disable StrictHostKeyChecking, which suppresses asking for connection approval.|`salt-ssh '*' -i pkg.install mysql-client`| +|`--no-host-keys`|Ignores SSH host keys. Useful if an error persists with `--ignore-host-keys`.|`salt-ssh '*' -i --no-host-keys pkg.install cowsay`| +|`--user`|Supply the user to authenticate with.|`salt-ssh '*' --user steven -r cowsay 'hello!'`| +|`--passwd`|Supply the password to authenticate with.|`salt-ssh 'minion2' --passwd p455w0rd system.reboot`| +|`--askpass`|Request a password prompt.|`salt-ssh 'minion1' --askpass sys.doc`| +|`--key-deploy`|Deploy the authorized SSH key to all minions.|`salt-ssh '*' --key-deploy --passwd test.ping`| +|`--sudo`|Run command with elevated privileges.|`salt-ssh '*' -r --sudo somecommand`| +|`--scan-ports`|A comma-separated list of ports to scan in the scan roster.|`salt-ssh '192.168.0.0/16' --roster scan --scan-ports 22,23 test.ping`| +|`--scan-timeout`|Timeout for scan roster.|`salt-ssh '192.168.0.0/16' --roster scan --scan-timeout 100 test.ping`| +|`-l`, `--log-level`|Change console log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`salt-ssh -l info test.ping`| +|`--log-file`|Change the log file path. Defaults to `/var/log/salt/ssh`|`salt-ssh --log-file /home/salt/log test.ping`| +|`--log-file-level`|Change the logging level of the log file. Same options as `--log-level`|`salt-ssh --log-level all test.ping`| +|`-E`, `--pcre`|Target expression will be interpreted as a Perl Compatible Regular Expression (PCRE) rather than a shell glob.|`salt-ssh -E 'minion[0-9]' service.reload apache2`| +|`--out`| Choose an alternative outputter to display returned data. Available outputters are: `grains`, `highstate`, `json`, `key`, `overstatestage`, `pprint`, `raw`, `txt`, `yaml`.| `salt-ssh '*' test.version --out json`| + +## salt-syndic + +A minion set up on a master that allows for passing commands in from a higher master. + +|Option|Description|Example| +|------|-----------|-------| +|`--version`|Get the current version of Salt.|`salt-syndic --version`| +|`-h`, `--help`|Display Salt commands and help text.|`salt-syndic -h`| +|`-c`, `--config-dir`|Change the Salt configuration directory. The default is `/etc/salt`.|`salt-syndic -c /home/salt/conf`| +|`-u`, `--user`|Supply a user to run salt-syndic.|`salt-syndic --user steven`| +|`-d`, `--daemon`|Run salt-syndic as daemon.|`salt-syndic -d`| +|`--pid-file`|Specify the file path of the pidfile. Default is `/var/run/salt-syndic.pid`|`salt-syndic --pid-file /path/to/new/pid`| +|`-l`, `--log-level`|Change console log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`salt-syndic -l info`| +|`--log-file`|Change the log file path. Defaults to `/var/log/salt/master`|`salt-syndic --log-file /home/salt/log`| +|`--log-file-level`|Change the logging level of the log file. Same options as `--log-level`|`salt-syndic --log-level all`| + +## spm + +Salt Package Manager + +|Option|Description|Example| +|------|-----------|-------| +|`-y`, `--yes`|Answer yes to all questions.|`spm remove -y apache`| +|`-f`, `--force`|Force `spm` to perform an action it would normally refuse to perform.|| +|`-l`, `--log-level`|Change console log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`spm -l info install apache`| +|`--log-file`|Change the log file path. Defaults to `/var/log/salt/spm`|`spm --log-file /home/salt/log install mysql`| +|`--log-file-level`|Change the logging level of the log file. Same options as `--log-level`|`spm --log-level all remove nginx`| + +|Command|Description|Example| +|-------|-----------|-------| +|`update_repo`|Update locally configured repository metadata.|`spm update_repo`| +|`install`|Install a package by name from a configured SPM repository.|`spm install nginx`| +|`remove`|Remove a package.|`spm remove apache`| +|`info`|Get an installed package's information.|`spm info mysql`| +|`files`|List an installed package's files.|`spm files mongodb`| +|`local`|Perform a command on a local package, not a package in a repository or an installed package. Does not work with `remove`.|`spm local install /path/to/package`| +|`build`|Build a package.|`spm build /path/to/package`| +|`create_repo`|Scan a directory for a valid SPM package and build an SPM-METADATA file in that directory.|`spm create_rep /path/to/package`| + +## salt-api + +Used to start the Salt API + +|Option|Description|Example| +|------|-----------|-------| +|`--version`|Get the current version of Salt.|`salt-api --version`| +|`-h`, `--help`|Display Salt commands and help text.|`salt-api -h`| +|`-c`, `--config-dir`|Change the Salt configuration directory. The default is `/etc/salt`.|`salt-api -c /home/salt/conf`| +|`-u`, `--user`|Supply a user to run salt-api.|`salt-api --user steven`| +|`-d`, `--daemon`|Run salt-api as daemon.|`salt-api -d`| +|`--pid-file`|Specify the file path of the pidfile. Default is `/var/run/salt-api.pid`|`salt-api --pid-file /path/to/new/pid`| +|`-l`, `--log-level`|Change console log level. Defaults to `warning`. Available options are `all`, `garbage`, `trace`, `debug`, `info`, `warning`, `error`, and `quiet`.|`salt-api -l info`| +|`--log-file`|Change the log file path. Defaults to `/var/log/salt/api`|`salt-api --log-file /home/salt/log`| +|`--log-file-level`|Change the logging level of the log file. Same options as `--log-level`|`salt-api --log-level all`| \ No newline at end of file diff --git a/docs/email/postfix/configure-postfix-to-send-mail-using-gmail-and-google-apps-on-debian-or-ubuntu/index.md b/docs/email/postfix/configure-postfix-to-send-mail-using-gmail-and-google-apps-on-debian-or-ubuntu/index.md index 140d76f5cde..3478e84e748 100644 --- a/docs/email/postfix/configure-postfix-to-send-mail-using-gmail-and-google-apps-on-debian-or-ubuntu/index.md +++ b/docs/email/postfix/configure-postfix-to-send-mail-using-gmail-and-google-apps-on-debian-or-ubuntu/index.md @@ -5,9 +5,9 @@ author: description: 'Install and configure Postfix on Debian and Ubuntu to send email through Gmail and Google Apps.' keywords: ["Postfix", " Ubuntu", " Debian", " SMTP", " Gmail"] license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' -modified: 2017-09-05 +modified: 2018-09-27 modified_by: - name: Edward Angert + name: Linode published: 2016-12-13 title: Configure Postfix to Send Mail Using Gmail and Google Apps on Debian or Ubuntu --- @@ -84,6 +84,9 @@ Usernames and passwords are stored in `sasl_passwd` in the `/etc/postfix/sasl/` {{< /file >}} + {{< note >}} +The SMTP server address configuration `smtp.gmail.com` supports message submission over port 587 ([StartTLS](https://en.wikipedia.org/wiki/Opportunistic_TLS)) and port 465 ([SSL](https://en.wikipedia.org/wiki/Transport_Layer_Security)). Whichever protocol you choose, be sure the port number is the same in `/etc/postfix/sasl/sasl\\_passwd` and `/etc/postfix/main.cf` files. See Google's [G Suite Administrator Help](https://support.google.com/a/answer/176600?hl=en) for more information. +{{< /note >}} 2. Create the hash db file for Postfix by running the `postmap` command: @@ -104,7 +107,7 @@ To restrict access to these files, change their permissions so that only the **r In this section, you will configure the `/etc/postfix/main.cf` file to use Gmail's SMTP server. -1. Find and modify `relayhost` in `/etc/postfix/main.cf` to match the following example: +1. Find and modify `relayhost` in `/etc/postfix/main.cf` to match the following example. Be sure the port number matches what you specified in `/etc/postfix/sasl/sasl\\_passwd` above. {{< file "/etc/postfix/main.cf" >}} relayhost = [smtp.gmail.com]:587 diff --git a/docs/getting-started/index.md b/docs/getting-started/index.md index dbe4e62577a..38c6557de4e 100644 --- a/docs/getting-started/index.md +++ b/docs/getting-started/index.md @@ -142,12 +142,12 @@ Once you have the IP address and an SSH client, you can log in via SSH. The foll 1. Enter the following into your terminal window or application. Replace the example IP address with your Linode's IP address: - ssh root@123.456.78.90 + ssh root@198.51.100.4 2. If this is the first time connecting to your Linode, you'll see the authenticity warning below. This is because your SSH client has never encountered the server's key fingerprint before. Type `yes` and press **Enter** to continue connecting. {{< output >}} -The authenticity of host '123.456.78.90 (123.456.78.90)' can't be established. +The authenticity of host '198.51.100.4 (198.51.100.4)' can't be established. RSA key fingerprint is 11:eb:57:f3:a5:c3:e0:77:47:c4:15:3a:3c:df:6c:d2. Are you sure you want to continue connecting (yes/no)? {{< /output >}} @@ -155,13 +155,13 @@ Are you sure you want to continue connecting (yes/no)? After you enter `yes`, the client confirms the addition: {{< output >}} -Warning: Permanently added '123.456.78.90' (RSA) to the list of known hosts. +Warning: Permanently added '198.51.100.4' (RSA) to the list of known hosts. {{< /output >}} 3. The login prompt appears for you to enter the password you created for the `root` user above. {{< output >}} -root@123.456.78.90's password: +root@198.51.100.4's password: {{< /output >}} 4. The SSH client initiates the connection. When the connection is completed the following prompt appears: @@ -178,7 +178,7 @@ To reconnect via SSH, revoke the key for that IP address. For Linux and Mac OS X: - ssh-keygen -R 123.45.67.89 + ssh-keygen -R 198.51.100.4 For Windows, PuTTY users must remove the old host IP addresses manually. PuTTY's known hosts are in the registry entry: diff --git a/docs/networking/dns/update-dns-at-common-name-server-authorities/index.md b/docs/networking/dns/update-dns-at-common-name-server-authorities/index.md new file mode 100644 index 00000000000..08a7b9bf83b --- /dev/null +++ b/docs/networking/dns/update-dns-at-common-name-server-authorities/index.md @@ -0,0 +1,29 @@ +--- +author: + name: Nathan Melehan + email: docs@linode.com +description: "Shortguide list of support documentation for updating DNS records at common name server authorities" +license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' +keywords: ["nameserver", "authoritative nameserver", "DNS", "DNS Manager"] +modified: 2018-09-27 +modified_by: + name: Nathan Melehan +title: "Update DNS Records at Common Name Server Authorities" +published: 2018-09-27 +headless: true +--- + +{{< disclosure-note "Updating DNS records at common nameserver authorities" >}} +The following support documents describe how to update DNS records at common nameserver authorities: + +- [CloudFlare](https://support.cloudflare.com/hc/en-us/articles/200168686-What-do-I-do-if-I-changed-my-server-IP-address-or-hosting-provider-) +- [GoDaddy](https://www.godaddy.com/help/manage-dns-zone-files-680) +- [DreamHost](https://help.dreamhost.com/hc/en-us/articles/215414867-How-do-I-add-custom-DNS-records) +- [Gandi](https://doc.gandi.net/en/dns/zone) +- [1&1](https://www.1and1.com/help/domains/configuring-your-ip-address/connecting-a-domain-to-a-static-ip-address/) +- [Network Solutions](http://www.networksolutions.com/support/how-to-manage-advanced-dns-records/) +- [Bluehost](https://my.bluehost.com/hosting/help/559) +- [HostGator](https://support.hostgator.com/articles/manage-dns-records-with-hostgatorenom) +- [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/319/2237/how-can-i-set-up-an-a-address-record-for-my-domain) +- [Hover](https://help.hover.com/hc/en-us/articles/217282457-How-to-Edit-DNS-records-A-AAAA-CNAME-MX-TXT-SRV-) +{{< /disclosure-note >}} \ No newline at end of file diff --git a/docs/platform/block-storage/how-to-use-block-storage-with-your-linode/index.md b/docs/platform/block-storage/how-to-use-block-storage-with-your-linode/index.md index fdc2c84e1e7..7308baedcf7 100644 --- a/docs/platform/block-storage/how-to-use-block-storage-with-your-linode/index.md +++ b/docs/platform/block-storage/how-to-use-block-storage-with-your-linode/index.md @@ -18,7 +18,7 @@ cloud_manager_link: platform/block-storage/how-to-use-block-storage-with-your-li Linode’s Block Storage service allows you to attach additional storage volumes to your Linode. A single volume can range from 10 GiB to 10,000 GiB in size and costs $0.10/GiB per month. They can be partitioned however you like and can accommodate any filesystem type you choose. Up to eight volumes can be attached to a single Linode, be it new or already existing, so you do not need to recreate your server to add a Block Storage Volume. -The Block Storage service is currently available in the Dallas, Fremont, Frankfurt, London, Newark, and Singapore data centers. +The Block Storage service is currently available in the Dallas, Fremont, Frankfurt, London, Newark, Singapore, and Tokyo 2 data centers. {{< caution >}} - Linode's backup services do not cover Block Storage Volumes. You must execute [your own backups](/docs/security/backups/backing-up-your-data/) for this data. diff --git a/docs/platform/disk-images/resizing-a-linode/resizing-a-linode-small.png b/docs/platform/disk-images/resizing-a-linode/resizing-a-linode-small.png index 296887c2060..ce389355ddd 100644 Binary files a/docs/platform/disk-images/resizing-a-linode/resizing-a-linode-small.png and b/docs/platform/disk-images/resizing-a-linode/resizing-a-linode-small.png differ diff --git a/docs/platform/disk-images/resizing-a-linode/resizing-a-linode.png b/docs/platform/disk-images/resizing-a-linode/resizing-a-linode.png index c984ec22779..ce389355ddd 100644 Binary files a/docs/platform/disk-images/resizing-a-linode/resizing-a-linode.png and b/docs/platform/disk-images/resizing-a-linode/resizing-a-linode.png differ diff --git a/docs/platform/manager/dns-manager-new-manager/index.md b/docs/platform/manager/dns-manager-new-manager/index.md index 7a55a41083b..31023c851e4 100644 --- a/docs/platform/manager/dns-manager-new-manager/index.md +++ b/docs/platform/manager/dns-manager-new-manager/index.md @@ -16,7 +16,7 @@ hiddenguide: true -The *Domains* section of the Linode Manger is a comprehensive DNS management interface that allows you to add DNS records for all of your domain names. This guide covers the use of the Domains section and basic domain zone setup. For an introduction to DNS in general, see our [Introduction to DNS Records](/docs/networking/dns/dns-records-an-introduction/) guide. +The *Domains* section of the Linode Manager is a comprehensive DNS management interface that allows you to add DNS records for all of your domain names. This guide covers the use of the Domains section and basic domain zone setup. For an introduction to DNS in general, see our [Introduction to DNS Records](/docs/networking/dns/dns-records-an-introduction/) guide. ## Getting Started diff --git a/docs/platform/manager/dns-manager/index.md b/docs/platform/manager/dns-manager/index.md index 3a039ee62f0..1c09055bd66 100644 --- a/docs/platform/manager/dns-manager/index.md +++ b/docs/platform/manager/dns-manager/index.md @@ -105,7 +105,7 @@ In order for Linode's DNS servers to function as slaves, your DNS master server 2a01:7e00::a {{< /note >}} -If you selected the option to have the DNS Manager insert basic DNS records, those records will be visible, as shown above. If you elected to keep the zone empty, you can start adding DNS records now. Skip to the [Adding DNS Records](/docs/networking/dns/dns-manager-overview/#add-records) section for instructions. +If you selected the option to have the DNS Manager insert basic DNS records, those records will be visible, as shown above. If you elected to keep the zone empty, you can start adding DNS records now. ### Add Records diff --git a/docs/platform/migrate-to-linode/best-practices-when-migrating-to-linode/index.md b/docs/platform/migrate-to-linode/best-practices-when-migrating-to-linode/index.md index 6c8adbbd5ac..f26b75c9314 100644 --- a/docs/platform/migrate-to-linode/best-practices-when-migrating-to-linode/index.md +++ b/docs/platform/migrate-to-linode/best-practices-when-migrating-to-linode/index.md @@ -116,19 +116,7 @@ To direct your visitors to your Linode, associate your domain with [your new Lin If you'd like to continue with your current nameservers, update all of the DNS records that are assigned to your old host's IP address to use your new Linode's IP. Contact your nameserver authority for instructions on how to update your DNS records. -{{< disclosure-note "Updating DNS records at common nameserver authorities" >}} -The following support documents describe how to update DNS records at common nameserver authorities: - -- [GoDaddy](https://www.godaddy.com/help/manage-dns-zone-files-680) -- [DreamHost](https://help.dreamhost.com/hc/en-us/articles/215414867-How-do-I-add-custom-DNS-records) -- [Gandi](https://doc.gandi.net/en/dns/zone) -- [1&1](https://www.1and1.com/help/domains/configuring-your-ip-address/connecting-a-domain-to-a-static-ip-address/) -- [Network Solutions](http://www.networksolutions.com/support/how-to-manage-advanced-dns-records/) -- [Bluehost](https://my.bluehost.com/hosting/help/559) -- [HostGator](https://support.hostgator.com/articles/manage-dns-records-with-hostgatorenom) -- [Namecheap](https://www.namecheap.com/support/knowledgebase/article.aspx/319/2237/how-can-i-set-up-an-a-address-record-for-my-domain) -- [Hover](https://help.hover.com/hc/en-us/articles/217282457-How-to-Edit-DNS-records-A-AAAA-CNAME-MX-TXT-SRV-) -{{< /disclosure-note >}} +{{< content "update-dns-at-common-name-server-authorities" >}} After DNS propagation has finished, [set reverse DNS](/docs/networking/dns/configure-your-linode-for-reverse-dns/) for your domain. This is especially important if you are running a mail server. diff --git a/docs/platform/tokyo2-migration/index.md b/docs/platform/tokyo2-migration/index.md new file mode 100644 index 00000000000..1c49c4dd21b --- /dev/null +++ b/docs/platform/tokyo2-migration/index.md @@ -0,0 +1,129 @@ +--- +author: + name: Linode + email: docs@linode.com +description: Linode is retiring our Tokyo 1 data center, and this guide shows how to migrate to our new Tokyo 2 location. +keywords: ["tokyo 1", "tokyo 2", "migrate", "migration", "migrating", "data center"] +license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)' +modified: 2018-09-27 +modified_by: + name: Linode +published: 2018-09-27 +title: Migrating from Tokyo 1 to Tokyo 2 +hiddenguide: true +--- + +In November 2016, Linode [announced and opened](https://blog.linode.com/2016/11/21/new-linode-datacenter-tokyo-2/) the Tokyo 2 data center. This is the second facility operated by Linode in the Tokyo region. Linode is now making preparations to retire the original Tokyo 1 facility. All Linodes hosted in this data center will be migrated to Tokyo 2. This guide is written to prepare customers for this migration and to make migrating easier. + +## Benefits of Tokyo 2 + +The Tokyo 2 data center provides access to features that are not available in Tokyo 1. These features are: + +- The [Block Storage Service](https://www.linode.com/blockstorage) (available starting Q3 2018). +- The [newest Linode plans](https://blog.linode.com/2018/05/17/updated-linode-plans-new-larger-linodes/). +- Future features on Linode's product roadmap. + +## When will My Linodes be Migrated? + +You will receive a support ticket from Linode that lists the scheduled dates and times for the migration of your Tokyo 1 Linodes. This ticket will be sent to you at least three months in advance of the start of your first migration. + +Different Linodes will be scheduled to migrate on different dates and times. The support ticket you receive will list the migration schedule for all of your Tokyo 1 Linodes. **Linode will not be able to adjust this schedule of migrations.** + +You are able to move your servers to Tokyo 2 before the scheduled migration dates. We recommend that all customers move their servers early. Moving early will help you better control the uptime of your services. + +{{< note >}} +You will receive a credit on your account equal to three months of service for each of your Tokyo 1 Linodes. This credit will cover the cost of creating new servers in Tokyo 2 if you choose to [clone your Linodes](#option-2-clone-your-linodes). +{{< /note >}} + +## What are My Options for Migrating? + +There are three different options for moving your servers to the Tokyo 2 data center. The first two of these methods can be followed before the scheduled migration deadlines for your Linodes. + +Regardless of which option you choose, **all of your Tokyo 1 Linodes' IP addresses will change** when moving to the new location. This includes all public and private IPv4 addresses, as well as public and link-local IPv6 addresses. + +Later sections in this guide describe how to update your [network interface configuration](#update-your-network-configuration) and [DNS records](#update-dns-records) to use the new IPs. + +{{< note >}} +If your Tokyo 1 Linode is enrolled in the [Linode Backup Service](https://www.linode.com/backups), it will remain enrolled in the service after the migration. However, the saved backups and snapshots that have been created for your Linode prior to the migration **will not move** to the new Tokyo 2 facility. Instead, your Linode will start creating new scheduled backups after it is migrated to the Tokyo 2 date center (according to its [backup schedule](/docs/platform/disk-images/linode-backup-service/#schedule-backups)). +{{}} + +### Option 1: Migrate Early + +When you receive the support ticket which lists your migration times, you will also see a new banner appear in the dashboard of each of your Tokyo 1 Linodes. This banner will give you the option to initiate an early migration of your Linode to Tokyo 2. + +Clicking on the banner will take you to a new page which shows the estimated duration for the migration. This page will let you initiate the migration. + +The following sequence executes when you start the migration: + +1. If your Linode is running, your Linode is gracefully powered down. + +1. At the same time, your Linode will be assigned new IP addresses. You will be able to view these new IPs from the [Remote Access tab](/docs/platform/manager/remote-access/) of your Linode's dashboard. + +1. The migration of your Linode is started immediately after the shutdown completes. + +1. If the Linode was running before the migration started, it will be automatically booted after the migration completes. If the Linode was not running, it will remain offline after the migration. + +You will be able to monitor the progress of your Linode's migration from its dashboard. While waiting on the migration to complete, [update your DNS records](#update-dns-records) to use your new IP addresses. DNS changes can take time to propagate, so we recommend doing this quickly after the migration is initiated. + +When the migration finishes, you may need to update your Linode's [network configuration](#update-your-network-configuration) to use the new IPs. + + +### Option 2: Clone your Linodes + +Because migrating a Linode will power it down during the migration, your Linode's services will be offline during that time. In addition, if you run a cluster of multiple Linodes for a service, then migrating one or more of them may cause problems for the cluster. + +To avoid these issues, you can instead create new Linodes in Tokyo 2 and then **clone** your Tokyo 1 Linode's disks to them. Performing a clone will create exact copies of your disks on the new Linode. + +{{< note >}} +You can perform a clone of a Linode when it is running. However, this can sometimes result in filesystem inconsistencies on the target Linode (your source Linode will never be negatively affected, even if the clone fails). You may need to power your source Linode down to perform a successful clone. +{{< /note >}} + +Cloning your Linodes offers these benefits: + +- You will be able to set up your new Linodes in Tokyo 2 and verify that they run normally before you remove your Tokyo 1 Linodes. + +- When you have verified that your Tokyo 2 Linodes work, you can update your DNS records. Updating your DNS records will gracefully direct your users to your new servers without downtime. + +To clone a Linode, follow these steps: + +1. Create a new Linode in Tokyo 2. Make sure that you [select a plan](https://www.linode.com/pricing) that has as much disk space as the size of your disks on your source Tokyo 1 Linode. + +1. Follow the [cloning guide](/docs/platform/disk-images/clone-your-linode/) to complete the clone operation. When following these steps, enable all of the configuration profile options for your Linode. + +After you have created your new Linode and completed the clone, you may need to update your new Linode's [network configuration](#update-your-network-configuration). After making sure that your new Tokyo 2 servers all work as expected, [update your DNS records](#update-dns-records). + +{{< note >}} +If you clone your Tokyo 1 Linodes to Tokyo 2, your Tokyo 1 Linodes will remain running and active on your account by default. To prevent double-billing, [remove](/docs/platform/billing-and-support/billing-and-payments/#removing-services) the original Tokyo 1 Linodes after you have finished your clones. The three-month credit that will be applied to your account will cover the costs for your extra servers during this transition period. This credit will not cover future costs if you do not delete your Tokyo 1 Linodes. +{{< /note >}} + +### Option 3: Migrate when Scheduled + +If you do not choose to migrate or clone early, Linode will automatically start your migrations at the time listed in your support ticket. + +{{< caution >}} +If Linode initiates your migration when it is scheduled, **your Linode will not be powered on automatically when the migration finishes**. Your Linode is not powered on in order to minimize potential security issues that could result from booting under a new IP assignment. +{{< /caution >}} + +After the scheduled migration completes, you can log into the Linode's dashboard and power it on. You may need to update your new Linode's [network configuration](#update-your-network-configuration). Then, [update your DNS records](#update-dns-records). You can also choose to update your DNS records as soon as the migration starts. + +## Update your Network Configuration + +In order for your new IP address assignment to work, your Linux deployment's network interface configuration needs to use the new IPs. If Linode's [Network Helper](/docs/platform/network-helper/) tool is enabled for your configuration profile, your network interface should automatically adopt the new IPs without any extra action needed from you. + +If Network Helper is not enabled, but you use DHCP for your network assignments, then your networking should also work automatically. + +If you do not use Network Helper or DHCP, then you will need to update your static interface configuration files. Follow the [Linux Static IP Configuration](/docs/networking/linux-static-ip-configuration/) guide to enter your new IP addresses. Your new IPs are listed in the [Remote Access tab](/docs/platform/manager/remote-access/) of your Linode's dashboard. These new IPs will only appear **after you start its migration** (if you choose to migrate instead of cloning). + +You may also need to update the configuration of your applications if they explicitly bind to your public or private IP addresses. Review Linode's [web server](/docs/web-servers/) and [application](/docs/applications/) guides for more information on this topic. + +## Update DNS Records + +To direct your users to your new Tokyo 2 servers' IPs, you need to update your DNS records to use the new IPs. If you are using Linode's DNS Manager, follow the DNS Manager guide to [update your records](/docs/platform/manager/dns-manager/#edit-records). + +If you use a different DNS provider, you will need to visit that provider's website to update your records. + +{{< content "update-dns-at-common-name-server-authorities" >}} + +## Contact Linode Support + +If you have any issues when migrating or cloning to Tokyo 2, or if you have any questions about this process, please [contact Linode Support](/docs/platform/billing-and-support/support/#contacting-linode-support). Technical questions about your Linux deployment's configuration are often outside the scope of support. For any out-of-scope issues, we also recommend searching and asking technical questions in the [Linode Community Site](/community/questions/). \ No newline at end of file diff --git a/docs/web-servers/nginx/deploy-django-applications-using-uwsgi-and-nginx-on-ubuntu-14-04/index.md b/docs/web-servers/nginx/deploy-django-applications-using-uwsgi-and-nginx-on-ubuntu-14-04/index.md index 28810d24081..062b0005b9e 100644 --- a/docs/web-servers/nginx/deploy-django-applications-using-uwsgi-and-nginx-on-ubuntu-14-04/index.md +++ b/docs/web-servers/nginx/deploy-django-applications-using-uwsgi-and-nginx-on-ubuntu-14-04/index.md @@ -13,6 +13,7 @@ title: 'Deploy Django Applications Using uWSGI and Nginx on Ubuntu 14.04' contributor: name: Sergey Pariev link: https://twitter.com/spariev +deprecated: True aliases: ['websites/nginx/deploy-a-django-application-using-uwsgi-and-nginx-on-ubuntu-14-04/','websites/nginx/deploy-django-applications-using-uwsgi-and-nginx-on-ubuntu-14-04/'] external_resources: - '[Writing your first Django app Tutorial](https://docs.djangoproject.com/en/dev/intro/tutorial01/#intro-tutorial01)'