Perl 6 - the future is here, just unevenly distributed

IRC log for #salt, 2016-07-30

| Channels | #salt index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:05 amcorreia joined #salt
00:05 ageorgop joined #salt
00:11 woodtablet left #salt
00:13 flowstate joined #salt
00:13 nmadhok joined #salt
00:14 sagerdearia joined #salt
00:30 ageorgop joined #salt
00:31 pipps joined #salt
00:34 GreatSnoopy joined #salt
00:49 Guest80605 joined #salt
00:58 teryx510 joined #salt
01:05 edrocks joined #salt
01:07 Nahual joined #salt
01:09 nmadhok joined #salt
01:13 blue_ joined #salt
01:13 sagerdearia joined #salt
01:15 flowstate joined #salt
01:18 iceyao joined #salt
01:21 mpanetta joined #salt
01:23 catpigger joined #salt
01:31 fracklen joined #salt
01:38 antpa joined #salt
01:51 timoguin joined #salt
01:52 nmadhok joined #salt
02:12 gableroux joined #salt
02:13 flowstate joined #salt
02:19 ALLmightySPIFF joined #salt
02:20 Xopher joined #salt
02:21 mpanetta joined #salt
02:28 Brijesh1 joined #salt
02:29 Andrew joined #salt
02:35 raspy_ joined #salt
02:35 raspy_ hi
02:44 bastiand1 joined #salt
02:47 Brijesh1 joined #salt
02:58 raspy_ is there a way to set an ec2 node into a specific availability zone? I want to set one node in us-west-1a and the other in us-west-1b
02:58 hemebond raspy_: In the profile.
02:58 hemebond Oh wait.
02:58 hemebond The provider defines the zone.
02:59 hemebond And the profile references the provider.
02:59 hemebond So you'd have to create a provider config for each zone.
02:59 hemebond That's according to my basic salt-cloud ec2 test config; I haven't read the docs recently.
03:00 raspy_ yeah i tried to set zone: us-west-1b but it didnt create the host there
03:01 raspy_ provider config ok
03:02 hemebond Is it something to do with the access key used in the provider?
03:02 hemebond Do you have to have a different key per zone?
03:02 hemebond In ec2 I mean. Does ec2 require a different key per zone?
03:03 pwhack joined #salt
03:04 raspy_ hemebond: http://pastebin.com/5q3sbNpT
03:05 raspy_ good question
03:05 raspy_ thats my provider config
03:07 pwhack Q: map files allow attaching grains to a minion when using salt-cloud. is there a way to assign grains in the salt-cloud command without a map file? for example:   salt-cloud -p dev-linux 28498.dev grains={'roles':['tomcat','jdk'], 'jdk_ver':'8'}
03:07 hemebond raspy_: Did you check https://docs.saltstack.com/en/latest/topics/cloud/aws.html
03:07 hemebond There are provider parameters "location" and "availability_zone".
03:10 raspy_ hemebond: hmmm yeah i tried but didnt seem to get the host to 1b
03:11 raspy_ ill keep pokin around, thx hemebond
03:11 timoguin joined #salt
03:12 hemebond raspy_: Which version of salt-cloud are you using?
03:13 flowstate joined #salt
03:13 hemebond raspy_: Your provider config doesn't have the availability_zone parameter.
03:13 hemebond According to your paste that is.
03:14 raspy_ hmmmm yeah that could be it let me try
03:34 PerilousApricot joined #salt
03:38 writtenoff joined #salt
03:40 antpa joined #salt
03:45 west575_ joined #salt
03:46 vilitux joined #salt
03:57 Brijesh1 joined #salt
04:07 votz left #salt
04:13 flowstate joined #salt
04:13 hasues joined #salt
04:13 hasues left #salt
04:21 Sokel joined #salt
04:23 keldwud joined #salt
04:25 syndikate joined #salt
04:26 Sokel I have a for loop in a state of mine for users. {% for name, user in pillar.get('users', {}).items() %} -- Let's say I wanted to override this so it didn't loop through the 20+ users in the pillar. What would be the right way to do so? I've tried: salt 'server' state.sls linux.users pillar='{users: tom}' for example, but I'm met with this: https://paste.fedoraproject.org/397513/85275414/
04:31 fracklen joined #salt
04:34 hasues joined #salt
04:39 hemebond Sokel: Your 'users' has to be a dict.
04:39 hemebond e.g., users: {}
04:40 hemebond or {users: {'Tommy Boy': 'tom'}}
04:40 hemebond I don't know what your pillar is like or what 'user' ends up containing.
04:40 keldwud joined #salt
04:40 subsignal joined #salt
04:46 Sokel hemebond: I see. Example of my pillar is like this (removing sensitive info): https://paste.fedoraproject.org/397517/69853940/
04:47 hemebond Sokel: Right, so you need to provide all that in the command.
04:48 hemebond pillar='{users: { tom: {fullname: 'Tom N', ... }}}'
04:51 Sokel So I can't just somehow pick one of my 20 users in the pillar then?
04:51 hemebond You can, but you have to include all the data.
04:52 hemebond You can't just provide a "reference" to the data.
04:55 babilen You could, however, implement support for that explicitly (if override_user is defined → pillar.get('users:' ~ override_user) .... )
04:55 hemebond Or use a separate list to define which accounts get looped through.
04:56 babilen Ah, I like that a lot more :)
04:56 hemebond Still requires rewriting the state though.
05:00 mpanetta_ joined #salt
05:04 POJO joined #salt
05:04 \ask joined #salt
05:13 flowstate joined #salt
05:14 hasues joined #salt
05:17 hasues left #salt
05:21 DEger joined #salt
05:21 DEger joined #salt
05:41 Brijesh1 joined #salt
05:41 Brijesh1 joined #salt
05:42 antpa joined #salt
05:50 Brijesh1 joined #salt
05:50 DEger joined #salt
06:13 flowstate joined #salt
06:15 lucas_ai joined #salt
06:30 lucas_ai joined #salt
06:32 syndikate joined #salt
06:37 fracklen joined #salt
06:44 subsignal joined #salt
06:50 syndikate joined #salt
06:51 PerilousApricot joined #salt
06:55 antpa joined #salt
07:06 ageorgop joined #salt
07:12 flowstate joined #salt
07:14 Miouge joined #salt
07:31 antpa joined #salt
07:34 rbjorklin joined #salt
07:39 antpa joined #salt
07:40 ribx joined #salt
07:41 Miouge joined #salt
07:52 Brijesh1 joined #salt
07:56 Miouge joined #salt
08:02 iceyao joined #salt
08:07 antpa joined #salt
08:08 antpa joined #salt
08:11 antpa joined #salt
08:11 mpanetta joined #salt
08:14 flowstate joined #salt
08:14 ivanjaros joined #salt
08:24 fredvd joined #salt
08:26 antpa joined #salt
08:28 antpa joined #salt
08:28 POJO joined #salt
08:32 antpa joined #salt
08:37 antpa joined #salt
08:43 lero joined #salt
08:50 jtang joined #salt
08:56 Miouge joined #salt
09:01 mpanetta joined #salt
09:03 DEger joined #salt
09:09 edrocks joined #salt
09:12 rbjorklin joined #salt
09:12 lovecraftian joined #salt
09:29 stooj joined #salt
09:30 ribx joined #salt
09:41 blueelvis joined #salt
09:41 lero joined #salt
10:01 GreatSnoopy joined #salt
10:05 antpa joined #salt
10:12 antpa joined #salt
10:20 mpanetta joined #salt
10:36 Miouge joined #salt
10:58 morissette joined #salt
11:04 mpanetta joined #salt
11:44 DEger joined #salt
12:19 iceyao joined #salt
12:22 amcorreia joined #salt
12:53 Trauma joined #salt
13:01 ivanjaros joined #salt
13:06 edrocks joined #salt
13:11 ZachLanich joined #salt
13:13 ZachLanich hemebond: Can you explain the reasoning behind targeting a minion in this command?: salt myminion cloud.profile ec2-centos64-x64 my-new-instance - Docs explain what it is, but no reason for doing so: https://docs.saltstack.com/en/stage/topics/cloud/salt.html#state-module (a ways down under "Profile")
13:14 cyborg-one joined #salt
13:15 ZachLanich Or anyone: ^
13:19 ninjada joined #salt
13:28 s_kunk joined #salt
13:35 nonades joined #salt
13:37 PerilousApricot joined #salt
13:39 antpa joined #salt
13:50 Brijesh1 joined #salt
13:55 Brijesh1 joined #salt
13:58 hoonetorg joined #salt
14:00 PerilousApricot joined #salt
14:10 sagerdearia joined #salt
14:13 sagerdearia joined #salt
14:20 Miouge joined #salt
14:35 PerilousApricot joined #salt
14:59 alinuxninja joined #salt
15:06 cyborg-one joined #salt
15:11 POJO joined #salt
15:13 nonades left #salt
15:20 ninjada joined #salt
15:42 nmadhok joined #salt
15:46 DEger joined #salt
15:52 ivanjaros joined #salt
15:58 vodik joined #salt
16:00 Ashald joined #salt
16:12 Ashald joined #salt
16:17 Ashald joined #salt
16:38 edrocks joined #salt
17:08 mohae joined #salt
17:09 Jimlad joined #salt
17:10 jenastar joined #salt
17:18 timoguin joined #salt
17:25 ldelossa joined #salt
17:40 Garo_ joined #salt
17:40 iggy because salt commands run on minions
17:51 nmadhok joined #salt
17:56 Perilous_ joined #salt
18:02 Tyrm joined #salt
18:16 tpaul joined #salt
18:18 Miouge joined #salt
18:19 POJO_ joined #salt
18:23 blueelvis joined #salt
18:26 ivanjaros joined #salt
18:27 blueelvis joined #salt
18:35 Jimlad joined #salt
18:38 JPT joined #salt
18:39 west575 joined #salt
18:43 PerilousApricot joined #salt
18:47 jenastar joined #salt
18:49 jenastar joined #salt
18:52 anotherZero joined #salt
19:01 west575 joined #salt
19:05 west575 joined #salt
19:16 ageorgop joined #salt
19:17 Miouge joined #salt
19:25 sagerdearia joined #salt
19:30 Fiber^ joined #salt
19:46 cyborg-one joined #salt
19:56 ageorgop joined #salt
19:58 west575 joined #salt
20:03 my10c quick one : if someone can help : {% set random_min = salt['random.rand_int']("start=0 end=59") %}
20:04 my10c this dpes not work: the question is : how do i pass more then 1 arg to a salt call in jinja?
20:04 my10c my goal it to do : random/5 in a crontab
20:04 babilen {% set random_min = salt['random.rand_int'](start=0, end=59) %}
20:05 babilen Or just: {% set random_min = salt['random.rand_int'](0, 59) %}
20:06 my10c without the 's
20:07 my10c let me try: i ll ask a new future to be able todo random/x : without changing the value once set :)
20:07 babilen Sorry, I don't quite follow
20:08 my10c currently random will not change the value once set : right ?
20:08 my10c my solution is buggy : since it will change the value every time the state is run
20:09 babilen True
20:09 babilen You could write it to a grain on the host and retrieve it from there
20:09 babilen grains.setval
20:09 my10c that was my next solution
20:09 my10c but since the state is onlt run twice / month : its ok
20:10 babilen Or just: https://xkcd.com/221/
20:10 my10c hahaha : yeah know that one
20:10 my10c gotta have xkcd 3 time/week for sure!
20:11 babilen If you want it to stay the same once chosen you have to save it somewhere. Grains are suitable for this and would allow for a simple implementation
20:13 my10c i know : wrote tons of grains :) already have an other solution : where the grains returns the host seq
20:13 my10c so web11 will return 11
20:13 Linuturk joined #salt
20:13 my10c so just matter to use same grain to add a seq%60  :-)
20:14 babilen That isn't really random, but I guess that all you care about is that your minions don't run the same job at the same time
20:14 my10c ack
20:15 babilen Well, sounds like a suitable solution then.
20:15 my10c :-)
20:15 teryx510 joined #salt
20:15 my10c my question above was how to pass arg to module : to is just do not use the 's not "s
20:15 my10c the only thing i hadn't try : stupid!
20:16 babilen It's not stupid, it simply is due to the fact you didn't quite realise that statements within {% .... %} follow the same syntactical rules as Python code
20:17 my10c now i know :)
20:17 babilen You know that now and it will be easy to write correct statements in the future
20:17 babilen :)
20:17 my10c wrote tons pf python for years : jinja less then 2 years
20:18 my10c one of the main reason i moved from puppet to salt wss python...
20:18 my10c again thanks!
20:18 my10c back to work
20:20 babilen have fun
20:22 my10c thanks
20:23 DEger joined #salt
20:28 CTaylor_ joined #salt
20:34 west575 joined #salt
20:39 west575 joined #salt
20:40 edrocks joined #salt
20:47 west575 joined #salt
20:52 POJO joined #salt
20:52 west575_ joined #salt
20:53 catpig joined #salt
20:55 justanot1eruser joined #salt
21:01 POJO_ joined #salt
21:02 DEger joined #salt
21:14 Pulp joined #salt
21:28 PerilousApricot joined #salt
21:34 sagerdearia joined #salt
21:44 my10c deos anyone know teh url to send feature ? i have the code tested too ...
21:46 west575 joined #salt
21:58 my10c nevermind submited #35083
22:05 barmaley joined #salt
22:12 nmadhok joined #salt
22:17 Shirkdog joined #salt
22:19 kiorky joined #salt
22:28 timoguin joined #salt
22:37 justanotheruser joined #salt
22:49 ashmckenzie joined #salt
23:01 Tyrm joined #salt
23:06 lovecraftian joined #salt
23:12 jenastar joined #salt
23:12 fredvd joined #salt
23:14 Tyrm joined #salt
23:15 robawt interesting issue
23:16 robawt i can see AMI ids for the ec2 driver of salt-cloud, but when i query against salt-cloud -f show_image it can't see them
23:16 robawt am i missing something/
23:25 Tyrm joined #salt
23:28 cyborg-one joined #salt
23:39 thejrose1984 joined #salt
23:43 PerilousApricot joined #salt
23:47 Jimlad joined #salt
23:48 bigdong joined #salt
23:51 teryx510 joined #salt
23:54 whitenoise joined #salt
23:58 theblazehen joined #salt

| Channels | #salt index | Today | | Search | Google Search | Plain-Text | summary