πŸ‘ Fan πŸ‘ Networking πŸ‘ is a πŸ‘ game πŸ‘ changer

I've got something else for the .1 release - m5 instance types dropped last
week in AWS, preparing a pull request now

On Fri, Dec 8, 2017 at 6:30 AM Rick Harding <rick.hard...@canonical.com>
wrote:

> Hey, how did you know I was working on a plugin for that :P
>
> I just started poking at the problem of easier management of what version
> your controller and models are on and a helper to maas upgrade. I'll reach
> out for some testing once it's there.
>
> On Fri, Dec 8, 2017 at 7:22 AM Merlijn Sebrechts <
> merlijn.sebrec...@gmail.com> wrote:
>
>> Slightly related; is there a way to update _all_ models on a controller
>> with one command?
>>
>> 2017-12-08 10:14 GMT+01:00 Andrew Wilkins <andrew.wilk...@canonical.com>:
>>
>>> On Fri, Dec 8, 2017 at 6:59 AM Nicholas Skaggs <
>>> nicholas.ska...@canonical.com> wrote:
>>>
>>>> The Juju team are extremely pleased to announce the release of Juju
>>>> 2.3. Juju is now more versatile, more efficient, and more configurable than
>>>> ever.
>>>>
>>>> Cross Model Relations deliver a new way of organising your software
>>>> stack. Deploy a database in one model and connect it to an application
>>>> running another, even one running on a different controller, or even a
>>>> different cloud.
>>>>
>>>> For containers at scale, Juju now integrates Canonical's Fan overlay
>>>> network system. This allows containers to map network traffic to any other
>>>> container on the fan network without distributed databases, consensus
>>>> protocols, or any extra overhead.
>>>>
>>>> Juju's support for bundles has made it possible to quickly deploy
>>>> connected sets of applications for some time now, but no two use cases are
>>>> the same. That's why we have introduced the concept of an 'overlay' bundle
>>>> - now you can easily add your own configuration and tweaks to a bundle at
>>>> deploy time. See below for links to more information on this and other key
>>>> features.
>>>>
>>>
>>> Hi folks,
>>>
>>> Unfortunately a critical bug [0] has escaped to the field. This bug
>>> affects existing relations in upgraded models. Models created after
>>> upgrading, or with a fresh bootstrap, or where relations are created after
>>> upgrading, will not be affected.
>>>
>>> I would not recommend upgrading from 2.x. to 2.3.0. We will be working
>>> on a fix for 2.3.1, and I expect this issue will bring that release forward
>>> much sooner. If you have already upgraded and are affected, then you can
>>> fix it by adding a document to the "statuses" collection in Mongo, as
>>> described in the bug.
>>>
>>> Cheers,
>>> Andrew
>>>
>>> [0] https://bugs.launchpad.net/juju/+bug/1737107
>>>
>>>
>>>>
>>>>
>>>> ## How can I get it?
>>>>
>>>>
>>>> The best way to get your hands on this release of Juju is to install it
>>>> via snap packages (see https://snapcraft.io/for more info on snaps).
>>>>
>>>>
>>>>    snap install juju --classic
>>>>
>>>>
>>>> Other packages are available for a variety of platforms. Please see the
>>>> online documentation at
>>>> https://jujucharms.com/docs/2.3/reference-install <
>>>> https://jujucharms.com/docs/stable/reference-install>. Those
>>>> subscribed to a snap channel should be automatically upgraded. If you’re
>>>> using the ppa/homebrew, you should see an upgrade available.
>>>>
>>>>
>>>> For highlights of this release, please see the documentation at
>>>>
>>>> https://jujucharms.com/docs/2.3/whats-new. Further details are below.
>>>>
>>>>
>>>>
>>>> ## New
>>>>
>>>>
>>>> * Cross Model Relations:
>>>>
>>>>  - see https://jujucharms.com/docs/2.3/models-cmr
>>>>
>>>>
>>>> * Persistent Storage:
>>>>
>>>>  - see https://jujucharms.com/docs/2.3/charms-storage
>>>>
>>>>
>>>> * FAN:
>>>>
>>>>  - see https://jujucharms.com/docs/2.3/charms-fan
>>>>
>>>>
>>>> * Bundle deployments:
>>>>
>>>>  - Changed flags for deploying bundles to existing machines
>>>>
>>>>  - Bundle deploy flag --bundle-config replaced with --overlay
>>>>
>>>>  - Deploying bundles now supports --dry-run
>>>>
>>>>  - Deploying bundles can now target existing machines
>>>>
>>>>
>>>> * Update Application Series:
>>>>
>>>>  - see https://jujucharms.com/docs/2.3/howto-updateseries
>>>>
>>>>
>>>> * Parallelization of the Machine Provisioner:
>>>>
>>>> - Groups of machines will now be provisioned in parallel reducing
>>>> deployment time, especially on large bundles.
>>>>
>>>>
>>>> * open_port and close_port hook tools now support ICMP
>>>>
>>>> - The open_port and close_port hook tools now support opening firewall
>>>> access for ICMP. The syntax is:
>>>>
>>>> open_port icmp
>>>>
>>>>
>>>> * LXD Storage Provider:
>>>>
>>>>  - see https://jujucharms.com/docs/2.3/charms-storage#lxd-(lxd)
>>>>
>>>>
>>>> ## Fixes
>>>>
>>>>
>>>> * Listing of Juju models is more efficient and can now handle more
>>>> models gracefully
>>>>
>>>> * Leadership coordinations is no longer tied to local time which avoids
>>>> problems with clock skew and reduces overall load on the database
>>>>
>>>> * Models are now more reliably destroyed and several fixes to avoid
>>>> negative impacts while they are being removed
>>>>
>>>>
>>>> You can check the milestones for a detailed breakdown of the Juju bugs
>>>> we have fixed:
>>>>
>>>>
>>>> https://launchpad.net/juju/+milestone/2.3.0
>>>>
>>>> https://launchpad.net/juju/+milestone/2.3-rc2
>>>>
>>>> https://launchpad.net/juju/+milestone/2.3-rc1
>>>>
>>>> https://launchpad.net/juju/+milestone/2.3-beta3
>>>>
>>>> https://launchpad.net/juju/+milestone/2.3-beta2
>>>>
>>>> https://launchpad.net/juju/+milestone/2.3-beta1
>>>>
>>>>
>>>>
>>>> ## Known issues
>>>>
>>>> The issues are targeted to be addressed in the upcoming 2.3.1 release.
>>>>
>>>>
>>>> * Firewaller issues on vmware vsphere
>>>> https://bugs.launchpad.net/juju/+bug/1732665
>>>>
>>>>
>>>> * LXD broken on vmware
>>>> https://bugs.launchpad.net/juju/+bug/1733882
>>>>
>>>>
>>>> * Can't deploy bundle with map-machines=existing and subordinates
>>>> https://bugs.launchpad.net/juju/+bug/1736592
>>>>
>>>>
>>>> * load spike on controller following remove-application
>>>> https://bugs.launchpad.net/juju/+bug/1733708
>>>>
>>>>
>>>>
>>>> ## Feedback Appreciated!
>>>>
>>>>
>>>> We encourage everyone to let us know how you're using Juju.
>>>>
>>>>
>>>> Join us at regular Juju shows - subscribe to our Youtube channel
>>>> https://youtube.com/jujucharms
>>>>
>>>> Send us a message on Twitter using #jujucharms, join us at #juju on
>>>> freenode, and subscribe to the mailing list at j...@lists.ubuntu.com.
>>>>
>>>>
>>>> https://jujucharms.com/docs/2.3/contact-us <
>>>> https://jujucharms.com/docs/stable/contact-us>
>>>>
>>>>
>>>> ## More information
>>>>
>>>>
>>>> To learn more about Juju please visit https://jujucharms.com.
>>>> --
>>>> 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-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-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Reply via email to