blocks|key|1320564|text|您需要设置host_string，示例如下：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1320565|from+fabric.context_managers+import+settings+as+_settings

def+_get_hardware_node(virtualized):
++++return+"localhost"

def+mystuff(virtualized):
++++real_host+=+_get_hardware_node(virtualized)
++++with+_settings(
++++++++host_string=real_host):
++++++++run("echo+I+run+on+the+host+%25s+::+`hostname+-f`"+%25+(real_host,+))|code-block|syntax|javascript|1320566|entityMap^0|5|B|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

You need to set <code>host_string</code> an example would be:

<pre><code>from fabric.context_managers import settings as _settings

def _get_hardware_node(virtualized):
 return "localhost"

def mystuff(virtualized):
 real_host = _get_hardware_node(virtualized)
 with _settings(
 host_string=real_host):
 run("echo I run on the host %s :: `hostname -f`" % (real_host, ))
</code></pre>

blocks|key|1320652|text|您可以在执行子任务之前分配给env.hoststring。如果要在多个主机上迭代，则在循环中将此全局变量赋值。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1320653|不幸的是，对你我来说，fabric不是为这个用例而设计的。在http://github.com/bitprophet/fabric/blob/master/fabric/main.py上查看main函数，看看它是如何工作的。|1320654|entityMap|0|LINK|mutability|MUTABLE|url|http://github.com/bitprophet/fabric/blob/master/fabric/main.py^0|E|E|0|2N|4|U|1Q|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|H|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

You can assign to <code>env.hoststring</code> before executing a subtask. Assign to this global variable in a loop if you want to iterate over multiple hosts.

Unfortunately for you and me, fabric is not designed for this use case. Check out the <code>main</code> function at <a href="http://github.com/bitprophet/fabric/blob/master/fabric/main.py" rel="nofollow noreferrer">http://github.com/bitprophet/fabric/blob/master/fabric/main.py</a> to see how it works.

blocks|key|1105719|text|您需要在模块级别修改env.hosts，而不是在任务函数内。我也犯了同样的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1105720|from+fabric.api+import+*

def+_get_hosts():
++++hosts+=+[]
++++...+populate+'hosts'+list+...
++++return+hosts

env.hosts+=+_get_hosts()

def+your_task():
++++...+your+task+...|code-block|syntax|javascript|1105721|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You need to modify env.hosts at the module level, not within a task function. I made the same mistake.

<pre><code>from fabric.api import *

def _get_hosts():
 hosts = []
 ... populate 'hosts' list ...
 return hosts

env.hosts = _get_hosts()

def your_task():
 ... your task ...
</code></pre>

blocks|key|1105754|text|使用roledefs|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1105755|from+fabric.api+import+env,+run

env.roledefs+=+{
++++'test':+['localhost'],
++++'dev':+['user@dev.example.com'],
++++'staging':+['user@staging.example.com'],
++++'production':+['user@production.example.com']
}+

def+deploy():
++++run('echo+test')|code-block|syntax|javascript|1105756|选择具有-R的角色：|1105757|$+fab+-R+test+deploy
[localhost]+Executing+task+'deploy'
...|1105758|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.fabfile.org/en/latest/usage/execution.html#roles^0|2|8|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

Use <a href="http://docs.fabfile.org/en/latest/usage/execution.html#roles" rel="noreferrer">roledefs</a>

<pre><code>from fabric.api import env, run

env.roledefs = {
 'test': ['localhost'],
 'dev': ['user@dev.example.com'],
 'staging': ['user@staging.example.com'],
 'production': ['user@production.example.com']
} 

def deploy():
 run('echo test')
</code></pre>

Choose role with -R:

<pre><code>$ fab -R test deploy
[localhost] Executing task 'deploy'
...
</code></pre>

blocks|key|1320766|text|这是一个更简单的serverhorror's+answer版本|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1320767|from+fabric.api+import+settings

def+mystuff():
++++with+settings(host_string='192.0.2.78'):
++++++++run("hostname+-f")|code-block|syntax|javascript|1320768|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/2415868/116973^0|8|L|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Here's a simpler version of <a href="https://stackoverflow.com/a/2415868/116973">serverhorror's answer</a>:

<pre><code>from fabric.api import settings

def mystuff():
 with settings(host_string='192.0.2.78'):
 run("hostname -f")
</code></pre>

blocks|key|1105824|text|这很简单。只需初始化env.host_string变量，以下所有命令都将在此主机上执行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1105825|from+fabric.api+import+env,+run

env.host_string+=+'user@exmaple.com'

def+foo:
++++run("hostname+-f")|code-block|syntax|javascript|1105826|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

It's very simple. Just initialize the env.host_string variable and all of the following commands will be executed on this host.

<pre><code>from fabric.api import env, run

env.host_string = 'user@exmaple.com'

def foo:
 run("hostname -f")
</code></pre>

blocks|key|1320870|text|使用角色目前被认为是做这件事的“适当”和“正确”的方式，也是你“应该”做的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1320871|也就是说，如果您喜欢大多数您“喜欢”或“渴望”的是执行“扭曲的系统”或在飞行中切换目标系统的能力。|1320872|因此，仅用于娱乐目的(!)下面的例子说明了许多人可能认为有风险，但不知何故完全令人满意的策略，如下所示：|1320873|env.remote_hosts+++++++=+env.hosts+=+['10.0.1.6']
env.remote_user++++++++=+env.user+=+'bob'
env.remote_password++++=+env.password+=+'password1'
env.remote_host_string+=+env.host_string

env.local_hosts++++++++=+['127.0.0.1']
env.local_user+++++++++=+'mark'
env.local_password+++++=+'password2'

def+perform_sumersault():
++++env_local_host_string+=+env.host_string+=+env.local_user+%2B+'@'+%2B+env.local_hosts[0]
++++env.password+=+env.local_password
++++run("hostname+-f")
++++env.host_string+=+env.remote_host_string
++++env.remote_password+=+env.password
++++run("hostname+-f")|code-block|syntax|javascript|1320874|然后运行：|1320875|fab+perform_sumersault|1320876|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Using roles is currently considered to be the "proper" and "correct" way of doing this and is what you "should" do it.

That said, if you are like most of what you "would like" or "desire" is the ability to perform a "twisted syster" or switching target systems on the fly.

So for entertainment purposes only (!) the following example illustrates what many might consider to a risky, and yet somehow thoroughly satisfying, manoeuvre that goes something like this:

<pre><code>env.remote_hosts = env.hosts = ['10.0.1.6']
env.remote_user = env.user = 'bob'
env.remote_password = env.password = 'password1'
env.remote_host_string = env.host_string

env.local_hosts = ['127.0.0.1']
env.local_user = 'mark'
env.local_password = 'password2'

def perform_sumersault():
 env_local_host_string = env.host_string = env.local_user + '@' + env.local_hosts[0]
 env.password = env.local_password
 run("hostname -f")
 env.host_string = env.remote_host_string
 env.remote_password = env.password
 run("hostname -f")
</code></pre>

Then running:

<pre><code>fab perform_sumersault
</code></pre>

blocks|key|1320937|text|因此，为了设置主机，并让命令在所有主机上运行，您必须从以下命令开始：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1320938|def+PROD():
++++env.hosts+=+['10.0.0.1',+'10.0.0.2']

def+deploy(version='0.0'):
++++sudo('deploy+%25s'+%25+version)|code-block|syntax|javascript|1320939|一旦定义了这些，就可以在命令行上运行该命令：|1320940|fab+PROD+deploy:1.5|1320941|它将在PROD函数中列出的所有服务器上运行部署任务，因为它在运行任务之前设置了env.hosts。|1320942|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

So, in order to set the hosts, and have the commands run across all the hosts, you have to start with:

<pre><code>def PROD():
 env.hosts = ['10.0.0.1', '10.0.0.2']

def deploy(version='0.0'):
 sudo('deploy %s' % version)
</code></pre>

Once those are defined, then run the command on the command line:

<pre><code>fab PROD deploy:1.5
</code></pre>

What will run the deploy task across all of the servers listed in the PROD function, as it sets the env.hosts before running the task.

blocks|key|1105954|text|下面是支持fab+my_env_1+my_command使用的另一个"summersault“模式：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1105955|使用此模式，我们只需使用字典定义一次环境。env_factory根据ENVS的键名创建函数。我将ENVS放在自己的目录中，并将secrets.config.py文件从fabric代码中分离出来。|1105956|缺点是，正如编写的那样，添加@task装饰器将break+it。|1105957|注意:由于late+binding，我们在工厂中使用def+func(k=k):而不是def+func():。我们使用this+solution获取正在运行的模块，并对其进行修补以定义函数。|1105958|secrets.config.py|1105959|ENVS+=+{
++++'my_env_1':+{
++++++++'HOSTS':+[
++++++++++++'host_1',
++++++++++++'host_2',
++++++++],
++++++++'MY_OTHER_SETTING':+'value_1',
++++},
++++'my_env_2':+{
++++++++'HOSTS':+['host_3'],
++++++++'MY_OTHER_SETTING':+'value_2'
++++}
}|code-block|syntax|javascript|1105960|fabfile.py|1105961|import+sys
from+fabric.api+import+env
from+secrets+import+config


def+_set_env(env_name):
++++#+can+easily+customize+for+various+use+cases
++++selected_config+=+config.ENVS[env_name]
++++for+k,+v+in+selected_config.items():
++++++++setattr(env,+k,+v)


def+_env_factory(env_dict):
++++for+k+in+env_dict:
++++++++def+func(k=k):
++++++++++++_set_env(k)
++++++++setattr(sys.modules[__name__],+k,+func)


_env_factory(config.ENVS)

def+my_command():
++++#+do+work|1105962|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.fabfile.org/en/1.13/usage/tasks.html#task-decorator|1|https://stackoverflow.com/questions/3431676/creating-functions-in-a-loop/#answer-3431699|2|https://stackoverflow.com/questions/602846/how-can-i-access-the-current-executing-module-or-class-name-in-python/#answer-7810592^0|5|N|0|L|B|Y|4|1C|4|1R|H|0|E|5|N|8|0|0|Q|E|17|B|5|C|1|1N|D|2|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1B|8|@$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]|$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1K|8|@$9|1L|A|1M|B|C]]|D|@$9|1N|A|1O|1|1P]]|E|$]]|$1|J|3|K|5|6|7|1Q|8|@$9|1R|A|1S|B|C]|$9|1T|A|1U|B|C]]|D|@$9|1V|A|1W|1|1X]|$9|1Y|A|1Z|1|20]]|E|$]]|$1|L|3|M|5|6|7|21|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|22|8|@]|D|@]|E|$Q|R]]|$1|S|3|T|5|6|7|23|8|@]|D|@]|E|$]]|$1|U|3|V|5|P|7|24|8|@]|D|@]|E|$Q|R]]|$1|W|3|-4|5|6|7|25|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]|14|$5|Z|10|11|E|$12|15]]|16|$5|Z|10|11|E|$12|17]]]]

Here's another "summersault" pattern that enables the <code>fab my_env_1 my_command</code> usage:

With this pattern, we only have to define environments one time using a dictionary. <code>env_factory</code> creates functions based on the keynames of <code>ENVS</code>. I put <code>ENVS</code> in its own directory and file <code>secrets.config.py</code> to separate config from the fabric code.

The drawback is that, as written, adding the <code>@task</code> decorator will <a href="http://docs.fabfile.org/en/1.13/usage/tasks.html#task-decorator" rel="nofollow noreferrer">break it</a>.

Notes: We use <code>def func(k=k):</code> instead of <code>def func():</code> in the factory because of <a href="https://stackoverflow.com/questions/3431676/creating-functions-in-a-loop/#answer-3431699">late binding</a>. We get the running module with <a href="https://stackoverflow.com/questions/602846/how-can-i-access-the-current-executing-module-or-class-name-in-python/#answer-7810592">this solution</a> and patch it to define the function.

secrets.config.py

<pre><code>ENVS = {
 'my_env_1': {
 'HOSTS': [
 'host_1',
 'host_2',
 ],
 'MY_OTHER_SETTING': 'value_1',
 },
 'my_env_2': {
 'HOSTS': ['host_3'],
 'MY_OTHER_SETTING': 'value_2'
 }
}
</code></pre>

fabfile.py

<pre><code>import sys
from fabric.api import env
from secrets import config


def _set_env(env_name):
 # can easily customize for various use cases
 selected_config = config.ENVS[env_name]
 for k, v in selected_config.items():
 setattr(env, k, v)


def _env_factory(env_dict):
 for k in env_dict:
 def func(k=k):
 _set_env(k)
 setattr(sys.modules[__name__], k, func)


_env_factory(config.ENVS)

def my_command():
 # do work
</code></pre>

I want to use Fabric to deploy my web app code to development, staging and production servers. My fabfile:

<pre><code>def deploy_2_dev():
 deploy('dev')

def deploy_2_staging():
 deploy('staging')

def deploy_2_prod():
 deploy('prod')

def deploy(server):
 print 'env.hosts:', env.hosts
 env.hosts = [server]
 print 'env.hosts:', env.hosts
</code></pre>

Sample output:

<pre><code>host:folder user$ fab deploy_2_dev
env.hosts: []
env.hosts: ['dev']
No hosts found. Please specify (single) host string for connection:
</code></pre>

When I create a <code>set_hosts()</code> task as shown in the <a href="http://docs.fabfile.org/0.9.0/usage/execution.html#globally-via-env" rel="noreferrer">Fabric docs</a>, env.hosts is set properly. However, this is not a viable option, neither is a decorator. Passing hosts on the command line would ultimately result in some kind of shell script that calls the fabfile, I would prefer having one single tool do the job properly.

It says in the Fabric docs that 'env.hosts is simply a Python list object'. From my observations, this is simply not true.

Can anyone explain what is going on here ? How can I set the host to deploy to ?

How to set target hosts in Fabric file

服务器

Python

我想使用Fabric将我的web应用程序代码部署到开发、暂存和生产服务器。我的fabfile文件：def deploy_2_dev():  deploy('dev')def deploy_2_staging():  deploy('staging')def deploy_2_prod():  deploy('prod'...

问如何在Fabric文件中设置目标主机
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Fabric文件中设置目标主机EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Fabric文件中设置目标主机
EN