Surpress pylint warning
Remove unused var
Better variable naming
Unusued var
Docstring
Docstrings. Formatting.
fixing whitespacing bug in debian_ip template
Changed naming for estates and lane names to not be the same as the key role but to be derived from the role
based on the application kind
the raet role is the same as the minion id in salt

so  minion with id 'alpha' has a raet role of 'alpha'
the minion primary estate name is produced by appending '_' and the application kind
the application kinds are ['master', 'minion', 'syndic', 'call']
If the application kind is 'minion' then
Then the primary minion estate name is  'alpha_minion'
The lanename for the manor lane is also 'alpha_minion'

On a master the estate name is master role with the application kind appended
so if the master id = 'master' = raet role and the application kind is 'minion'
 then the primary estate name is
'master_master'

The lanename for the manor lane on a master is special
this is because salt cloud uses of the raet_channel do not yet have opts associated with them
so there is no way to extract the id or the application kind.
As a result the lanename for the master manor lane is always 'master'
This imposes a constraint that there only be one master on a given directory structure that
is the sock_dir must be unique per master else there will be collisions with the manor lane
of multiple master on the same host.

The estate name must be globally unique for a given raet Road
This convention allows multiple Estares to share the same role as long as they are
of unique application kinds.
The primary use case is to support salt_caller as an independent estate and not use the
minion primary estate to communicate with the master
added application kind to RoadStack setup and then commented it out because errors
Fix lint errors
Merge pull request #16369 from terminalmage/cli-example-formatting

Fix formatting of CLI examples in cloud exec module
Issue #16384: avoid lspci warnings on OpenVZ containers

I did not dare to shuffle things around in the huge _virtual() method.
Instead, logging gets postponed, and upon detection of 'virtual:openvzve',
failures for lspci and dmidecode get discarded
create new file if not already present
Merge pull request #16362 from cro/20141003_mergefwd

Merge forward from 2014.7 was messy
updated masterless documentation to clarify the need to disable (or not run) the salt-minion daemon, otherwise the minion will attempt to connect to a master
Merge branch 'develop' of https://github.com/gracinet/salt into gracinet-develop
Merge branch 'gracinet-develop' into develop
Replace backslash-quote with raw string formatting
Issue #16384: avoid lspci warnings on OpenVZ containers

I did not dare to shuffle things around in the huge _virtual() method.
Instead, logging gets postponed, and upon detection of 'virtual:openvzve',
failures for lspci and dmidecode get discarded
Replace backslash-quote with raw string formatting