Re: Weekly Development Summary
On Fri, Jul 21, 2017 at 10:01 AM Anastasia Macmood < anastasia.macm...@canonical.com> wrote: > Hi > > A quick update on what keeps us, Juju team, busy... > > This week the team has been busy with an important task of improving > developer experience in addition to improving the product. > > Of course, we have continued highly desired work on persistent storage > with this week's focus on storage import [1] as well non-destructive > storage removal [2] aspects. This effort also led to identifying > improvements in model destruction that are now under way. > > We have made considerable progress in improving actions' footprint with > work that prunes action results periodically [3]. > > As usual, with a week that follows a new release of Juju, we have > provided support to our existing users upgrading to a newer release. > > In addition, to excite and expedite developer experience, the team has > put in place an improved merge job! Now developers can with greater ease > track running tests when merging code. > > This week, the team has also worked on increasing functional coverage > for persistent storage, relations as well as model migration. > > Last but not least, in a "call for arms", we are working on enabling > users to specify primary network on VSphere overwriting the default VM > network specified in OVF files shipped with Ubuntu images [4]. The > nature of VSphere deployments, and the variety of networking > combinations that are useful in the production environments, means that > we need a hand from Juju community to verify our current approach. If > you are interested in the ability to specify network in your VSphere, > try the patch [5] linked in the bug and reach out to us with your feedback! > I've just managed to track down a vCenter suitable for testing, but it only has standard switches, and they're in use so can't be changed. I tested with a distributed vswitch/portgroup with a disabled NIC (just to see that the code would work). It would be great if someone could test with a working distributed vswitch/porgroup. I don't think we need to block releasing the fix on that, though. Cheers, Andrew Quick links: > Work pending: https://github.com/juju/juju/pulls > Recent commits: https://github.com/juju/juju/commits/develop > > Sincerely Yours, > > Anastasia > > [1] https://github.com/juju/juju/pull/7653 > > [2] https://github.com/juju/juju/pull/7648 and > https://github.com/juju/juju/pull/7649 > > [3] https://github.com/juju/juju/pull/7645 > > [4] https://bugs.launchpad.net/juju/+bug/1619812 > > [5] https://github.com/juju/juju/pull/7660 > > > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Weekly Development Summary
Hi A quick update on what keeps us, Juju team, busy... This week the team has been busy with an important task of improving developer experience in addition to improving the product. Of course, we have continued highly desired work on persistent storage with this week's focus on storage import [1] as well non-destructive storage removal [2] aspects. This effort also led to identifying improvements in model destruction that are now under way. We have made considerable progress in improving actions' footprint with work that prunes action results periodically [3]. As usual, with a week that follows a new release of Juju, we have provided support to our existing users upgrading to a newer release. In addition, to excite and expedite developer experience, the team has put in place an improved merge job! Now developers can with greater ease track running tests when merging code. This week, the team has also worked on increasing functional coverage for persistent storage, relations as well as model migration. Last but not least, in a "call for arms", we are working on enabling users to specify primary network on VSphere overwriting the default VM network specified in OVF files shipped with Ubuntu images [4]. The nature of VSphere deployments, and the variety of networking combinations that are useful in the production environments, means that we need a hand from Juju community to verify our current approach. If you are interested in the ability to specify network in your VSphere, try the patch [5] linked in the bug and reach out to us with your feedback! Quick links: Work pending: https://github.com/juju/juju/pulls Recent commits: https://github.com/juju/juju/commits/develop Sincerely Yours, Anastasia [1] https://github.com/juju/juju/pull/7653 [2] https://github.com/juju/juju/pull/7648 and https://github.com/juju/juju/pull/7649 [3] https://github.com/juju/juju/pull/7645 [4] https://bugs.launchpad.net/juju/+bug/1619812 [5] https://github.com/juju/juju/pull/7660 -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: testing the future of juju with snaps
And one of these days I'll learn how email works and reply to the right email. Apologies for the noise. On Thu, Jul 20, 2017 at 11:40 AM Rick Hardingwrote: > I've added the image and editing back in the paragraphs and such that > didn't copy over. Can you please play editor and tweak it for any insights > consistency and such please before it goes live? > > Thanks! > > On Thu, Jul 20, 2017 at 11:17 AM Rick Harding > wrote: > >> In light of recent calls for testing out upcoming 2.3 work [1][2] I >> wanted to make sure folks were aware of how easy it can be to get a hold of >> a really recent build of trunk and test things out, look into how you can >> use it, and provide feedback. >> >> http://mitechie.com/blog/2017/7/20/testing-the-future-of-juju-with-snaps >> >> >> 1: >> http://mitechie.com/blog/2017/7/7/call-for-testing-shared-services-with-juju >> 2: https://awilkins.id.au/post/juju-2.3-storage/ >> > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: testing the future of juju with snaps
I've added the image and editing back in the paragraphs and such that didn't copy over. Can you please play editor and tweak it for any insights consistency and such please before it goes live? Thanks! On Thu, Jul 20, 2017 at 11:17 AM Rick Hardingwrote: > In light of recent calls for testing out upcoming 2.3 work [1][2] I wanted > to make sure folks were aware of how easy it can be to get a hold of a > really recent build of trunk and test things out, look into how you can use > it, and provide feedback. > > http://mitechie.com/blog/2017/7/20/testing-the-future-of-juju-with-snaps > > > 1: > http://mitechie.com/blog/2017/7/7/call-for-testing-shared-services-with-juju > 2: https://awilkins.id.au/post/juju-2.3-storage/ > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
testing the future of juju with snaps
In light of recent calls for testing out upcoming 2.3 work [1][2] I wanted to make sure folks were aware of how easy it can be to get a hold of a really recent build of trunk and test things out, look into how you can use it, and provide feedback. http://mitechie.com/blog/2017/7/20/testing-the-future-of-juju-with-snaps 1: http://mitechie.com/blog/2017/7/7/call-for-testing-shared-services-with-juju 2: https://awilkins.id.au/post/juju-2.3-storage/ -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: How to set state in @hook code block?
I'm pretty sure hooks execute in the parent directory. So if you have charm/ hooks/ db-relation-changed myfiles/ test.yaml you need to open("hooks/myfiles/test.yaml") John =:-> On Jul 20, 2017 04:58, "fengxia"wrote: > Hi Juju, > > I think I read at some point in the official document that you can't set > state from hook. > > However, this is what I'm trying to achieve: in @hook('config-changed'), I > will pass in a file path as a config value. Files are part of the charm so > they are installed in /var/lib/juju/agents/unit-mycharm/myfiles/ on the > unit node. But when @hook('config-changed') is triggered, my code to > "open('/path/file')" actually complains "file not found". This makes me > wonder that hook is not visible of the charm directory? > > So I'm thinking this can be worked around if I set_state("mystate") from > hook. But doing so didn't trigger @when("mystate"). > > What's the right way to do this then? > > -- > Feng xia > Engineer > Lenovo USA > > Phone: 5088011794 > fx...@lenovo.com > > Lenovo.com > Twitter | Facebook | Instagram | Blogs | Forums > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm > an/listinfo/juju > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju