| === frankban|afk is now known as frankban | ||
| skay | where's upstream of django-layer-base? I forked it from somewhere and github isn't showing where I forked it from | 14:54 |
|---|---|---|
| rick_h | skay: hmm, I think that's bdx's work | 14:55 |
| skay | I can't even remember why I forked it | 14:55 |
| skay | someone's been giving me PRs and I want to point them to upstream | 14:55 |
| rick_h | bah, don't see it in his GH but might be under a different org so not sure. | 14:57 |
| skay | rick_h: I found one in omnivector | 14:58 |
| skay | is he part of that? | 14:58 |
| rick_h | yes! | 14:58 |
| rick_h | yea, I see the sentry stuff in that namespace he was working on | 14:58 |
| skay | rick_h: thanks! I contactd github to ask them to link up my repo as a fork | 15:02 |
| skay | bdx: I had a brainfart and merged a couple of requests from someone to my repo. I've asked the contributor to submit them to your repo. https://github.com/codersquid/layer-django-base/pulls?q=is%3Apr+is%3Aclosed | 15:06 |
| === frankban is now known as frankban|afk | ||
| === agprado is now known as agprado|afk | ||
| skay | bdx: ah, the vanishing fork solved. I forked an old repo of yours that no longer exists. someone from github got back to me to explain this. | 18:04 |
| === chat is now known as Guest35305 | ||
| catbus | Hi, is there a way to update the maas endpoint in the juju cloud settings? maas cloud is added then the endpoint is changed. | 19:15 |
| catbus | the 'update-cloud' seems to work with only public clouds. | 19:16 |
| freyes | catbus, you could update it manually in ~/.local/share/juju/clouds.yaml | 19:26 |
| catbus | I did. juju is still trying to reach the old maas endpoint. | 19:26 |
| catbus | freyes: ^^^ | 19:26 |
| catbus | juju show-cloud shows the new endpoint that I manually modified. juju destroy-controller --destroy-all-models throws the error that it can't reach maas at the old endpoint. | 19:28 |
| freyes | catbus, ah, an already deployed environment, that's stored in mongodb, you would need to edit the database manually | 19:28 |
| freyes | I don't know what the specific collection where that information is stored, sorry :\ | 19:28 |
| catbus | freyes: no problem. working on database directly is too much. Do you happen to know if I can kill the controller, remove the maas cloud setting in juju, and manually release the machines in this order? | 19:30 |
| freyes | catbus, yes you can, and if you update clouds.yaml first, I think the kill-controller will be able to reach maas to release the nodes | 19:31 |
| catbus | ok, will give it a try. | 19:31 |
| freyes | kill-controller makes the client (the one running in your laptop) talk to the cloud provider directly | 19:31 |
| catbus | freyes: kill-controller failed for the same error, not able to reach the old maas endpoint.. | 19:33 |
| catbus | ERROR getting controller environ: getting environ using bootstrap config from client store: Get http://<old endpoint> i/o timeout. So the config in the controller needs update. | 19:34 |
| freyes | catbus, try editing bootstrap-config.yaml | 19:34 |
| catbus | cool | 19:34 |
| catbus | I think it's working. I see 'will kill machines directly in 4m5s'. | 19:36 |
| catbus | freyes: the juju controller node is released successfully, but not the rest. it does say 'manual intervention may be necessary to ensure resources are released.' I will manually release them via maas. Thanks! | 19:42 |
| freyes | catbus, probably it couldn't get the list of nodes associated with that controller | 19:43 |
| freyes | catbus, yw ;) | 19:43 |
| hml | catbus: you can change the maas endpoints with juju add-cloud —replace… instead of editting the file though i’m not sure what happens with an exsiting controller | 19:45 |
| catbus | hml: oh, will try --replace next time. Didn't know it. I have killed the controller, so my guess is if I bootstrap again, it will use the new settings that I manually modified. | 19:46 |
| hml | yes | 19:47 |
| catbus | hml: shouldn't this fall in 'update-cloud'? | 19:47 |
| hml | update-clouds is for public cloud info. | 19:48 |
| hml | you had to do an add-cloud to setup the maas cloud… | 19:49 |
| hml | though it is a little weird to do an add-cloud to change it perhaps | 19:49 |
| catbus | hml: right, that's what I meant. The doc is clear that update-clouds is for public cloud only, but for maas, you have to use add-cloud --replace to update. | 19:50 |
| hml | catbus: i’m not clear on your question then, can you expand on it please? | 19:51 |
| catbus | hml: It's not a question. I just echoed what you said that though it is a little weird to do an add-cloud to change it perhaps. I know update-clouds is for public cloud only, clear from the juju doc. | 19:53 |
| hml | :-) | 19:53 |
| === lborda_ is now known as lborda_att_poc | ||
| === agprado_ is now known as agprado | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!