networking - Optimizing Ansible Transport\SSH for Unconventional Networks -

-

i'm wondering how optimise ansible work network radically different 1 use cases accelerate , default might not beneficial.

in scenario i'm not dealing virtual network, nor dealing servers. i'm dealing hundreds of embedded, rather unique network design, downside of faults in hosts or cabling on network may cause periodic connectivity changes neighbouring hosts.

this result in dropped or laggy ssh sessions on individual ssh conneciton, unfortunately cause ansible hang on particular hosts , timeout change alone doesn't seem make difference.

could provide information parameters best managing configuration changes , install updates on network drop outs may occur during session on or connected particular hosts, longer lived sessions may not beneficial. in particular advice on these areas in context use scenario

  1. ssh vs paramiko
  2. control persist, pipelining , timeout params
  3. accelerate or no?
  4. evaluating suitability number of specified forks run

if working in network connection might lost 'during' execution of play/task i'm not sure if (read: don't think) ansible saves context of execution recover such issues.

if network bad, should fix that.

assuming knew and: if network bad can't fix params of interest #2 , possibly #3 listed.

change #2 ensure ssh doesn't try reuse connections (doesn't persist). slow down playbook executions provide better stability.

change #3 if have transfer large files , you're using paramiko or ansible older 1.5.

for completeness: #1 kinda no-brainer, don't use paramiko unless have no choice. although list have choice in, practical purposes ansible expects use ssh there many disadvantages of using paramiko on ssh , 1 advantage, if donno advantage don't need it. :-)

even after these settings, if connection lost during execution of task ansible can't except show error message. thing deal these situations idempotency of plays/tasks. can run in loop until playbook runs , makes 0 changes.


Comments

Post a Comment

Popular posts from this blog

python - TypeError: start must be a integer -

-
i trying draw 5 turtles, getting typeerror on line 25. here code: import turtle wn = turtle.screen() redrose = turtle.turtle() color = input("what background color be?") fillcolor_f = input("what color of rose be?") redrose.hideturtle() redrose.speed(30) redrose.penup() redrose.left(180) redrose.forward(175) redrose.right(90) redrose.forward(30) redrose.right(90) redrose.pendown() def drawrose(red): redrose.color("pink") redrose.fillcolor(fillcolor_f) redrose.fill(true) in range(red): redrose.forward(i) redrose.right(49) in range(5): drawrose(redrose) redrose.penup() redrose.forward(350) redrose.right(144) redrose.pendown() redrose.fill(false) drawrose(50) wn.bgcolor(color) i trying draw 5 roses, produces errors. doing in interactivepython.org. you recursively calling drawrose wrong parameter. on line 23 ( for in range(red): ) expect red integer...
Read more

c# - DevExpress RepositoryItemComboBox BackColor property ignored -

-
i have following code almost works properly; private void cbstatus_drawitem(object sender, listboxdrawitemeventargs e) { string item = e.item string; if (item != null) { switch (item) { case "1": e.appearance.forecolor = color.green; e.appearance.backcolor = color.green; break; case "2": e.appearance.forecolor = color.orange; e.appearance.backcolor = color.orange; break; case "3": e.appearance.forecolor = color.red; e.appearance.backcolor = color.red; break; } } } when dropdown shown, items forecolor correct, backcolor remains whatever backcolor of theme is; i.e. if i've got set dark theme, backcolor dark, cells in gridview, rather being green/orange/red. i've tried setting e.appearance.options.usebackcolor trying set e....
Read more

django - Creating multiple model instances in DRF3 -

-
1) create multiple model instances 1 api call, asked here: how create multiple model instances django rest framework? tried solution named in link, no success. i trying upload multiple files in 1 api call. result: files uploaded (only once overwrote perform_create) 1 instance created (if send 2 files, latter created instance). my code: class fileuploadserializer(serializers.modelserializer): def __init__(self, *args, **kwargs): many = kwargs.pop('many', true) super(fileuploadserializer, self).__init__(many=many, *args, **kwargs) class meta: model = fileupload read_only_fields = ('created', 'datafile', 'owner') class fileuploadviewset(viewsets.modelviewset): queryset = fileupload.objects.all() serializer_class = fileuploadserializer parser_classes = (multipartparser, formparser, ) def perform_create(self, serializer): file_list = self.request.data.getlist('file') ...
Read more