/srv/irclogs.ubuntu.com/2017/01/23/#juju-dev.txt

axwnurfet: ok, cool. at the moment, the ubuntu user is hard-coded throughout the codebase. I think it would be difficult to change that now, so your provider would need to create the ubuntu user00:00
axwnurfet: will your provider not rely on cloud-init?00:00
nurfetI see. no my provider does not support cloud-init at the moment00:01
axwnurfet: I have to go, will be back in an hour or so if you still have questions. otherwise thumper or wallyworld may be able to assist00:05
nurfetaxw: thanks00:10
thumperwell... fuck00:49
perrito666Good morning to you too thumper01:20
thumpero/01:20
rediris it morning already01:21
perrito666Not for me I just found funny the first thing I read from01:21
perrito666Thumper01:21
redirI'm gonna give up soon01:21
redirfor the day.01:21
perrito666Ahhggg i hate phone kb01:21
thumper:)01:22
perrito666I was just passing by01:22
redirnow I can't deploy because the maas can't see resolve simplestreams host.01:22
* redir eods02:09
redirlooks like it is still having trouble fetching the image from simplestreams02:10
thumperwallyworld: https://github.com/juju/juju/pull/685403:13
wallyworldyou want a review? ok03:14
thumperplease03:15
wallyworldthumper: +1, jeez why is arm so sloooooow03:16
thumperreasons03:16
veeberswallyworld: Is there an easy way to grab what series a controller is running? Or will it be the ol' "juju ssh lsb-release..."?03:53
wallyworldit might be in status, can't recall ottomh03:53
veeberswallyworld: ack I'll poke. Cheers03:56
veebersah it totally is03:57
wallyworldaxw: i'm having an issue with some azure unit tests. but maybe i should also validate the approach i'm using. did you have time for a HO?05:14
axwwallyworld: just finishing my lunch, in a short while05:15
wallyworldok05:15
axwwallyworld: ready, see you in 1:105:21
wallyworldaxw: here's the WIP  https://github.com/juju/juju/compare/develop...wallyworld:azure-ingress-rules?expand=105:21
axwwallyworld: should be fine. limit is 80 characters: https://docs.microsoft.com/en-us/azure/guidance/guidance-naming-conventions05:46
wallyworldgreat ty05:47
wallyworldi have tests passing now, just need t add some more05:47
wallyworldaxw: that PR is now up. much of it is cleanup https://github.com/juju/juju/pull/685506:10
axwwallyworld: OK, will look shortly06:10
wallyworldno rush ty06:10
axwwallyworld: what are the rules for grouping ingress rules, if any? as it is, there's no guarantee that IngressRules is going to return the rules with the same grouping as they were opened06:38
axwwallyworld: e.g. I might open port range 1000-2000, and later 2000-3000; then IngressRules will report them as one06:39
axwoh wait06:39
axwnever mind...06:39
wallyworldaxw: i am sure i read somewhere in our code that we do not allow overlapping ort ranges06:39
wallyworldi think if we do need to cater for that sort of thing, it needs to be done in the firewaller worker06:40
axwwallyworld: 2001-3000 then. what I mean is this: I could open 1000-2000 for 192.168.0.1/24, and then later 192.168.0.2/24. the azure implementation of IngressRules turns that into one IngressRule. is that the expection of the interface? does it *matter* that they're combined?06:42
axw(or not combined)06:42
axwwallyworld: if it matters, it should be specified on the interface method06:42
axwif not, then I'm wondering why we bother06:42
axwparticularly in the provider. if the firewaller cares about grouping them, it should do it - relieve the providers of the burden06:43
wallyworldaxw: the idea was that we OpenPorts() with an ingress rule that is has grouped CIDRs for a given port range, so we should mirror thaton the way back out when IngressRules() is called06:49
axwwallyworld: I understand. but what about when they're *not* grouped on the way in?06:49
axwwhy favour the one over the other?06:49
wallyworldthe network.IngressRule struct contains a slice of CIDRs, so we try and stick to that where possible06:50
wallyworldotherwise why bother having a slice of CIDrs in the IngressRule06:50
axwwallyworld: it makes sense coming in, as an optimisation06:50
axwwallyworld: on the way out, I don't think it matters at all06:51
axwwallyworld: at least not at the provider level06:51
wallyworldi guess i also see it as an optimisation on the way out06:51
wallyworldbut it can be changed if we think that's what needs to be done06:51
axwwallyworld: an optimisation for what?06:51
wallyworldthe caller06:51
wallyworldwho would otherwise need to do the grouping06:52
axwwallyworld: my point is this: either the caller needs to do the grouping, the provider needs to, or neither needs to; please document or remove06:53
axw(if the caller *needs* them grouped, and the provider doesn't do it, then it's breaking its contract. that contract needs to be specified, so people don't write dodgy providers)06:54
wallyworldi 'll add some doc the the IngressRules() interface method. we can see how it all plays out then when the firewaller is refactored to use this new stuff properly. we can always change the providers not to group if that turns out to be best06:55
axwwallyworld: I'm just going to give it a quick test, looks good tho07:13
wallyworldty07:13
wallyworldaxw: eating dinner soon, but thanks for review, will fix issues. let me know if any testing shows any issues07:30
axwwallyworld: sure, I'll let you know either way. still waiting on bootstrap...07:30
wallyworldazure is fast :-/07:31
axwwallyworld: QA OK07:46
wallyworldawesome, ty07:54
=== frankban|afk is now known as frankban
perrito666Morning09:42
hoenirGood morning comrades !10:31
frankbanaxw: ping11:20
=== frankban is now known as frankban|afk
perrito666morning again12:43
=== frankban|afk is now known as frankban
frankbanperrito666: do you know anything about the azure provider?13:33
rick_hfrankban: what's up?13:33
perrito666frankban: very little sadly, the person to as is axw, but shoot the question, we might sort it out13:41
frankbanperrito666: ok thanks13:45
frankbanperrito666: I'll send an email13:45
perrito666frankban: k13:51
mbruzekrick_h: Who works on packaging the juju bits that are installed on the deployed VMs?14:09
rick_hmbruzek: the juju agents? they're pulled directly from streams so not really a package?14:12
perrito666mbruzek: you are experiencing problems with agents?14:13
mbruzekrick_h: I was running a security tool and found jujud was not owned by a user on the deployed system. This set off a security issue, I filed a bug, but want to follow up with someone about it.14:13
mbruzekhttps://bugs.launchpad.net/juju-core/+bug/165854914:13
rick_hmbruzek: ah, yea saw that bug.14:13
mbruzekok14:13
rick_hmbruzek: not sure there's any "one" person on that.14:13
mbruzekI can be the "one" just point me at the code that does that.14:14
rick_hmbruzek: hmm, so I'd imagine that's done during the agent install process as part of the agent setup bits https://github.com/juju/juju/blob/staging/agent/agent.go14:17
rick_hmbruzek: but yea, might need to get someone like perrito666 or core folks to help sanity check where the agents are installed from/setup.14:17
perrito666mbruzek: rick_h I am not sure where the exact code is but typically its a tar.gz downloaded from our streams14:17
rick_hmbruzek: wallyworld is probably the best 'expert' on the whole agent setup bits14:17
perrito666the user on them must be the one fro jenkins on the machine that builds them14:17
perrito666so a chown is in order14:18
rick_hperrito666: right, but this is when the jujud is unpacked on the managed machine it needs to be chown there14:18
rick_hperrito666: at least that's how I read the bug14:18
perrito666rick_h: agreed14:18
perrito666I find it a bit odd that juju does not have its own user14:18
rick_hperrito666: hmm isn't it root?14:18
mbruzekThe other files in that directory were symbolic links to something else. This was the only file not owed by root and not a symbolic link.14:19
mbruzekiirc14:19
perrito666rick_h: yeah I would prefer us to be owned by a juju user14:19
perrito666mbruzek: looking for the relevant code14:20
mbruzekThanks perrito66614:20
mbruzekperrito666: I have to relocate, if you find anything please leave it in the bug I opened and I can take action on it. I am happy to help on this issue, just need a hint on where to look and/or get started.14:22
perrito666so ideally this should be done inside agent/tools/toolsdir.go -> UpackTools14:22
mbruzekOk14:23
mbruzekwriting that down now14:23
perrito666mbruzek: ping me when you are back14:23
perrito666:) ill have more info for you14:23
perrito666happy relocation14:23
mbruzekbrb14:23
mbruzekperrito666: back14:55
perrito666mbruzek: hi, I was saying "so ideally this should be done inside agent/tools/toolsdir.go -> UpackTools"14:56
mbruzekperrito666: I will take a look and propose a fix14:57
perrito666buut, that is only called by upgrades so cloud-init most likely has some repeated code doing that14:57
perrito666mbruzek: looking for the relevant part15:00
perrito666brb lunch15:38
redirmorning16:09
perrito666redir: hello :D16:09
redir:)16:09
alexisbmorning redir, perrito66616:30
perrito666alexisb: morning16:30
rediralexisb: 0/16:36
=== frankban is now known as frankban|afk
perrito666k, EOD until standup20:22

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!