Re: Juju 2.0-beta10 is here!

2016-06-24 Thread Marco Ceppi
On Fri, Jun 24, 2016 at 3:18 PM Curtis Hovey-Canonical 
wrote:

> A new development release of Juju, 2.0-beta10 is here!
>
> ## What's new?
>
> * Improved handling of LACP bonds
> * Continued usability enhancements
>   * Users can now use `juju relate` to add a relation between applications
>

This has got to be such a small change, but it goes a long way, love it!


>   * Additional `juju status` enhancements
> * Bundles requesting legacy ‘lxc’ type will automatically get new ‘lxd’
>   containers
>
> ## How do I get it?
>
> If you are running ubuntu, you can get it from the juju devel ppa:
>
> sudo apt-add-repository ppa:juju/devel
> sudo apt update; sudo apt install juju
>
> Windows, Centos, and OS X users can get a corresponding installer at:
>
> https://launchpad.net/juju-core/+milestone/2.0-beta10
>
> ## Feedback Appreciated!
>
> We encourage everyone to subscribe to the mailing list at
> j...@lists.ubuntu.com and join us at #juju on freenode.
> We would love to hear your feedback and about your usage of juju.
>
> ## Known issues
>
> * Juju GUI is not yet compatible with the API changes in 2.0-beta10
> * Juju deployer, and any tool using python-jujuclient are not yet
>   compatible with the API changes in recent betas.
>
> ## Anything else?
>
> You can read more information about what's in this release by viewing
> the release notes here:
>
> https://jujucharms.com/docs/devel/temp-release-notes
>
>
> --
> Curtis Hovey
> Canonical Cloud Development and Operations
> http://launchpad.net/~sinzui
>
> --
> 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


Juju 2.0-beta10 is here!

2016-06-24 Thread Curtis Hovey-Canonical
A new development release of Juju, 2.0-beta10 is here!

## What's new?

* Improved handling of LACP bonds
* Continued usability enhancements
  * Users can now use `juju relate` to add a relation between applications
  * Additional `juju status` enhancements
* Bundles requesting legacy ‘lxc’ type will automatically get new ‘lxd’
  containers

## How do I get it?

If you are running ubuntu, you can get it from the juju devel ppa:

sudo apt-add-repository ppa:juju/devel
sudo apt update; sudo apt install juju

Windows, Centos, and OS X users can get a corresponding installer at:

https://launchpad.net/juju-core/+milestone/2.0-beta10

## Feedback Appreciated!

We encourage everyone to subscribe to the mailing list at
j...@lists.ubuntu.com and join us at #juju on freenode.
We would love to hear your feedback and about your usage of juju.

## Known issues

* Juju GUI is not yet compatible with the API changes in 2.0-beta10
* Juju deployer, and any tool using python-jujuclient are not yet
  compatible with the API changes in recent betas.

## Anything else?

You can read more information about what's in this release by viewing
the release notes here:

https://jujucharms.com/docs/devel/temp-release-notes


-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev


Re: Cleansing Mongo data

2016-06-24 Thread Nate Finch
It seems as though we should be cleansing all the keys since we never
know what queries we might want to make in the future.

On Fri, Jun 24, 2016 at 12:04 PM Katherine Cox-Buday <
katherine.cox-bu...@canonical.com> wrote:

>
> As I have only just discovered the need to cleanse mongo data, I can't say
> for sure, but it looks like we may have been cleansing things in the parts
> of Juju that need it. William may know more.
>
> If not, I imagine a small upgrade step would make short work of any
> problems.
>
> roger peppe  writes:
>
> > This is useful, thanks.
> >
> > Note that's it's not necessary to cleanse *all* keys that go into Mongo,
> > just the ones that might be used in queries.
> >
> > But one thought... what about keys that already contain full-width
> > dollar and dot?
> >
> >   cheers,
> > rog.
> >
> > On 23 June 2016 at 21:09, Katherine Cox-Buday
> >  wrote:
> >> Hey all,
> >>
> >> William gave me a good review and it came up that I wasn't cleansing
> >> some of
> >> the data being placed in Mongo. I wasn't aware this had to be done,
> >> and
> >> after talking to a few other folks it became apparent that maybe not
> >> many
> >> people know we should be doing this.
> >>
> >> At any rate, William also pointed me to some existing code which did
> >> this.
> >> I've pulled it out into the mongo/utils package for general
> >> consumption. The
> >> comments do a pretty good job of elucidating why this is necessary.
> >>
> >> https://github.com/juju/juju/blob/master/mongo/utils/data_cleansing.go
> >>
> >> -
> >> Katherine
> >>
> >> --
> >> Juju-dev mailing list
> >> Juju-dev@lists.ubuntu.com
> >> Modify settings or unsubscribe at:
> >> https://lists.ubuntu.com/mailman/listinfo/juju-dev
> >>
>
> --
> Katherine
>
> --
> 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


Re: Cleansing Mongo data

2016-06-24 Thread Katherine Cox-Buday

As I have only just discovered the need to cleanse mongo data, I can't say for 
sure, but it looks like we may have been cleansing things in the parts of Juju 
that need it. William may know more.

If not, I imagine a small upgrade step would make short work of any problems.

roger peppe  writes:

> This is useful, thanks.
>
> Note that's it's not necessary to cleanse *all* keys that go into Mongo,
> just the ones that might be used in queries.
>
> But one thought... what about keys that already contain full-width
> dollar and dot?
>
>   cheers,
> rog.
>
> On 23 June 2016 at 21:09, Katherine Cox-Buday
>  wrote:
>> Hey all,
>>
>> William gave me a good review and it came up that I wasn't cleansing
>> some of
>> the data being placed in Mongo. I wasn't aware this had to be done,
>> and
>> after talking to a few other folks it became apparent that maybe not
>> many
>> people know we should be doing this.
>>
>> At any rate, William also pointed me to some existing code which did
>> this.
>> I've pulled it out into the mongo/utils package for general
>> consumption. The
>> comments do a pretty good job of elucidating why this is necessary.
>>
>> https://github.com/juju/juju/blob/master/mongo/utils/data_cleansing.go
>>
>> -
>> Katherine
>>
>> --
>> Juju-dev mailing list
>> Juju-dev@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>>

-- 
Katherine

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev


Re: Cleansing Mongo data

2016-06-24 Thread Katherine Cox-Buday

Thanks Menno, I'll get that docstring corrected!

I'm not sure it needs to be in its own package. I put it there because the 
taxonomy made sense in my head, and I get the impression that we have built up 
a lot of utility-like functions for Mongo over time, but YAGNI may apply here.

I don't plan on moving this over (mostly due to time constraints), but I would 
not be opposed if someone wanted to. It might be helpful to inventory other 
utility-like functionality first.

Menno Smits  writes:

> Thanks, this is really useful - especially when writing data into the
> database that comes sources that the code doing the writing doesn't
> have control over.
>
> Two little things:
>
> 1. The docstring for EscapeKeys still mentions statusDoc. 
> 2. Are you sure this needs to be in it's own package, especially one
> called "utils"? Given we already have the widely used
> github.com/juju/utils - as well as others with that name under
> juju/juju - this one is predestined to be aliased everywhere it's
> imported. Couldn't these escaping functions just live in their own
> file in github.com/juju/juju/mongo? Even when the import isn't
> aliased, the intent of "mongo.EscapeKeys(...)" is clearer than
> "utils.EscapeKeys(...)".
>
> - Menno
>
> On 24 June 2016 at 08:09, Katherine Cox-Buday
>  wrote:
>
> Hey all,
> 
> 
> William gave me a good review and it came up that I wasn't
> cleansing some of the data being placed in Mongo. I wasn't aware
> this had to be done, and after talking to a few other folks it
> became apparent that maybe not many people know we should be doing
> this.
> 
> 
> At any rate, William also pointed me to some existing code which
> did this. I've pulled it out into the mongo/utils package for
> general consumption. The comments do a pretty good job of
> elucidating why this is necessary.
> 
> 
> https://github.com/juju/juju/blob/master/mongo/utils/data_cleansing.go
>
> 
> 
> 
> -
> Katherine
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
> 
> 
>
>

-- 
Katherine

-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev