[12:09] <gsamfira> Hello folks. Couple of questions.
[12:09] <gsamfira> any chance we can get win2019 tools in simplestreams for the latest juju release?
[12:10] <gsamfira> and the other question is: How would I go about updating the documentation for the manual provider to include Windows?
[12:26] <rick_h> gsamfira:  second one is easy, the docs are in the discourse "Docs" category and can leave comments on there that are picked up and such.
[12:26] <rick_h> gsamfira:  first one will have to look into.
[12:27] <gsamfira> rick_h: great! Will look in discourse. Need to send a few PRs before I update the docs. A few small fixes to the manual provider.
[12:28] <gsamfira> rick_h: for the second one, we built the tools locally, so not a huge blocker, but would rather use the ones in simplestreams.
[12:31] <rick_h> gsamfira:  yea totally. We're a bit understaffed today with the holiday but will look into it.
[12:31] <gsamfira> rick_h: no rush at all. Whenever you get around to it. Thanks for the info!
[22:54] <wallyworld> babbageclunk: bug 1790185 was from 2018, but i think we're still lacking zone constraint support?
[22:54] <mup> Bug #1790185: There is no way of specifiying on which cluster charm should be deployed vSphere <cpe-onsite> <vsphere-provider> <juju:Triaged> <https://launchpad.net/bugs/1790185>
[22:54] <wallyworld> could they use resource-groups?
[22:57] <wallyworld> babbageclunk: actually, there's discussion in #juju
[22:58] <babbageclunk> wallyworld: ok looking
[23:43] <wallyworld> kelvinliu: any chance of a review on a small PR to merge 2.7 into devel? https://github.com/juju/juju/pull/11434
[23:46] <kelvinliu> looking
[23:54] <kelvinliu> looking good to me if the ignore leader check change for upgrade-charm is an expected change wallyworld
[23:55] <wallyworld> kelvinliu: yeah, added it as a driveby
[23:55] <wallyworld> it was a bug in 2.8
[23:55] <kelvinliu> ic
[23:55] <wallyworld> it caused those leadership errors when upgrading
[23:55] <kelvinliu> ah right