Re: GUI Props

[Uros Jovanovic]

Happy to hear you like the new features in the release, James. You're
right, current account page is just a start and we're excited about the
things that are yet to come. SSH keys handling is on that list for sure.

Thank you and the rest of the community for providing feedback and feature
requests to fit your use cases, it's the combined effort that makes the
development of UI bits a true joy.

Cheers from the JAAS team.

On Tue, May 23, 2017 at 7:03 AM, James Beedy  wrote:

> The latest Juju GUI release is a huge step in the right direction! Amongst
> the great improvements, the account page is really the start to something
> great! Massive props and many thanks to all who have put in hard work and
> long hours to bring the GUI to where it is today.
>
> Looking forward, I'm wondering if the account page would be a good place
> to manage ssh keys too?
>
> Either way, nice work here!
>
>
>
> --
> 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: PROPOSAL: stop recording 'executing update-status hook'

[Uros Jovanovic]

+1

On Fri, May 19, 2017 at 4:13 AM, Tim Penhey 
wrote:

> Hi folks,
>
> Currently juju will update the status of any hook execution for any unit
> to show that it is busy doing things. This was all well and good until we
> do things based on time.
>
> Every five minutes (or so) each unit will have the update-status hook
> executed to allow the unit to set or update the workload status based on
> what is currently going on with that unit.
>
> Since all hook executions are stored, this means that the show-status-log
> will show the unit jumping from executing update-status to ready and back
> every five minutes.
>
> The proposal is to special case the update-status hook and show in status
> (or the status-log) that the hook is being executed. debug-log will
> continue to show the hook executing if you are looking.
>
> This will reduce noise in the status-log, simplify some of our code around
> dealing with status-log, and reduce load on controllers looking after
> hundreds or thousands of units.
>
> Is anyone opposed to this change?
>
> Tim
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/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: Juju 2.2-alpha and conjure-up, are here!

[Uros Jovanovic]

Please note, that the experience with "juju login jaas" in 2.2-Alpha1 is
still quite broken. The login command will add jaas controller to the
controllers.yaml, so the next time you'd like to use it, you'll have to do
"juju switch jaas" instead of "juju login jaas".  We'll improve the
experience by the next release.

PS: In case you've already registered JAAS controller, please unregister it
and run "juju login jaas" again.

On Thu, Mar 16, 2017 at 10:19 PM, Curtis Hovey-Canonical <
cur...@canonical.com> wrote:

> A new release of Juju, 2.2-alpha1, and conjure-up, are here!
>
>
> ## What's new in 2.2-alpha1
>
> - juju login
>
>
> ### juju login
>
> Juju login command now accepts the name of the public controller as a
> parameter.
>
> juju login jaas
>
> This would add the jaas public controller to the list of the controllers
> you can use, it will also get cached in the controllers.yaml. Public
> controllers use external identity providers. JAAS uses Ubuntu SSO as an
> external provider, so in order to use this controller, you have to
> register at Ubuntu SSO. In order to get access to the JAAS public
> controller, please register through jujucharms.com or using this URL
> https://jujucharms.com/login
>
> The previous version of the command accepted the user name as a
> parameter. In order to login as a local user, pass the -u option.
>
> juju login -u bob
>
> Note that this release includes only the initial implementation of the
> juju login command changes. Polishing and improved UX will come with
> following releases.
>
>
> ## Resolved Issues
>
> Check the milestones for a detailed breakdown of Juju and conjure-up
> bugs corrected.
>
> https://github.com/conjure-up/conjure-up/milestone/20?closed=1
> https://launchpad.net/juju/+milestone/2.2-alpha1
>
>
> ## How do I get it?
>
> If you are running Ubuntu, you can get Juju from the juju stable ppa:
>
>sudo add-apt-repository ppa:juju/devel; sudo apt-get update
>
>sudo apt-get install juju
>
> Or install Juju from the snap store:
>
>snap install juju --classic --beta
>
> Install conjure-up from the snap store:
>
>snap install conjure-up --classic --edge
>
> If you are on Trusty, you'll need to run a few extra commands:
>
>sudo apt-get install snapd
>sudo groupadd lxd && sudo usermod -a -G lxd $USER
>sudo reboot
>
> Now you can install snaps, including conjure-up, as normal:
>
>snap install conjure-up --classic --edge
>
> Windows, CentOS, and MacOS users can get a corresponding Juju
> installer at:
>
>https://launchpad.net/juju/+milestone/2.2-alpha1
>
>
> ## Feedback Appreciated!
>
> We encourage everyone to let us know how you're using Juju. 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.
>
>
> ## More information
>
> To learn more about these great technologies please visit
> https://jujucharms.com and http://conjure-up.io.
>
>
> --
> 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

Re: charm store series enablement/timing (unrecognized series "zesty")

[Uros Jovanovic]

This should be resolved now.

On Sat, Dec 3, 2016 at 5:20 PM, Ryan Beisner 
wrote:

> Hi All,
>
> Do we have an eta for zesty series recognition in the charm store?  It
> looks like it is already committed in master, so I imagine it's just a
> matter of the store release schedule.
>
> OpenStack Charm CI consumes cs: artifacts for our charm dev and test, and
> all of the official OpenStack charms are multi-series.  That means that the
> presence of zesty series metadata effectively halts our dev/test and CI for
> all series.  We are seeing:
>
> unrecognized series "zesty" in metadata
> https://github.com/juju/charmstore/issues/695
>
>
> To unblock devs in the mean time, I've raised reviews to remove zesty
> series metadata from the affected charm repos.
>
> I think it's pretty important for the charm store to get ahead of this by
> always enabling the next dev series as soon as that series opens for
> development.  And, we'll look before we leap on each cycle.
>
> Cheers & thanks,
>
> Ryan
>
> --
> 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: juju devel 2.0-beta4 is released

[Uros Jovanovic]

Great news, kudos all!

Please note that although the example states "juju upgrade-gui 2.1.1" we've
replaced 2.1.1 version with 2.1.2, which is also the default one that get's
installed.

Have fun.


On Fri, Apr 15, 2016 at 6:38 AM, Curtis Hovey-Canonical <
cur...@canonical.com> wrote:

> # juju 2.0-beta4
>
> A new development release of Juju, juju 2.0-beta4, is now available.
> This release replaces version 2.0-beta3.
>
>
> ## Getting Juju
>
> Juju 2.0-beta4 is available for Xenial and backported to earlier
> series in the following PPA:
>
> https://launchpad.net/~juju/+archive/devel
>
> Windows, Centos, and OS X users will find installers at:
>
> https://launchpad.net/juju-core/+milestone/2.0-beta4
>
> Upgrading to this development releases is not supported.
>
>
> ## The complete release notes available on the Web
>
> The release notes for Juju 2.0-beta4 are very long. They are too large
> to post to a list. The complete release notes are published at
>
> https://jujucharms.com/docs/devel/temp-release-notes
>
>
> ## Getting started with Juju 2.0
>
> Juju 2.0 allows you to get started creating models without modifying any
> definition files. Just provide your credentials and go! (Note: to
> fully understand the new bootstrap experience please see the "New
> Bootstrap and Cloud Management Experience" section below)
>
> * LXD provider (requires lxd 2.0.0~rc9 or later):
>   The LXD provider requires no credentials, so you can create a
>   controller by just specifying its name:
>
> juju bootstrap  lxd
>
> Note that the lxdbr0 bridge needs to be properly configured for the lxd
> provider to work, for details see:
> http://insights.ubuntu.com/2016/04/07/lxd-networking-lxdbr0-explained/
>
> * Public Clouds:
>   Known public clouds can be listed with juju list-clouds:
>
> juju list-clouds
>
> CLOUD  TYPEREGIONS
> awsec2 us-east-1, us-west-1, us-west-2, ...
> aws-china  ec2 cn-north-1
> aws-govec2 us-gov-west-1
> azure  azure   japanwest, centralindia, eastus2,
> ...
> azure-chinaazure   chinaeast, chinanorth
> cloudsigma cloudsigma  mia, sjc, wdc, zrh, hnl
> google gce us-east1, us-central1, ...
> joyent joyent  us-east-1, us-east-2, us-east-3, …
> lxdlxd
> maas   maas
> manual manual
> rackspace  rackspace   LON, SYD, HKG, DFW, ORD, IAD
>
> Add your credentials using either:
>
> juju add-credential 
> or
> juju add-credential  -f creds.yaml
> or
> juju autoload-credentials
>
> When specifying just the cloud, juju add-credential will allow a new
> credential to be added interactively. You will be prompted type the
> required credential attributes. Example:
>
> juju add-credential maas
>   credential name: hmaas
>   replace existing credential? [y/N]: y
>   auth-type: oauth1
>   maas-oauth:
> credentials added for cloud maas
>
> The new credentials.yaml file at: ~/.local/share/juju/credentials.yaml
>
> The autoload tool will search for existing credentials for AWS,
> OpenStack/Rackspace, and Google clouds. You will then be prompted for
> which ones you'd like to save.
>
> If you have an existing credential.yaml file, you can also import a
> named credential, eg for MAAS
>
> cat credentials.yaml
>
>   credentials:
>  maas:
>my-credentials:
>  auth-type: oauth1
>  maas-oauth: 
>
> or, for AWS
>
> cat credentials.yaml
>
>   credentials:
> aws:
>   default-credential: my-credentials
>   my-credentials:
> auth-type: access-key
> access-key: 
> secret-key: 
>
> Bootstrap using your default credentials:
>
>  juju bootstrap  [/region]
>
> Examples:
>
>  juju bootstrap aws-controller aws
>
>  juju bootstrap mass-controller maas/192.168.0.1
>
> In the MAAS example above, you specify the host address of the MAAS
> controller. So to use Juju on MAAS out of the box, you set up a
> credentials file (either interactively, or based on the example above)
> and then bootstrap. This avoids the need for any cloud configuration.
> But it's also possible to set up a named MAAS cloud definition as
> explained later.
>
> More details on the new bootstrap experience, including defining private
> clouds can be found in the New Bootstrap and Cloud Management Experience
> section.
>
>
> ## What's New in Beta4
>
> * Mongo 3.2 is now used when bootstrapping on Xenial hosts
> * address-allocation feature flag no longer supported in MAAS provider
> * prefer-ipv6 setting is now ignored in all providers
> * MAAS 1.9+ provisioned LXD containers now have a bridge per NIC
> * Accurate address selection based on spaces (in MAAS)
> * extra-bindings support for charms metadata
> *