Re: Openstack User Feedback

Touched base on IRC out of band with this, just circling back here as well to confirm that we're working to reproduce and advise. Thanks again, Ryan On Wed, Apr 4, 2018 at 11:04 AM, James Beedy wrote: > forgot one: https://bugs.launchpad.net/charms.ceph/+bug/1761230 > >

Re: Juju Openstack - Blocked

Great! Thanks for confirming. I'm happy to have helped de-obfuscate the situation. I may or may not have caused that same little flavor overrun "once" - cannot confirm. ;-) Cheers, Ryan On Mon, Feb 19, 2018 at 4:42 PM, James Beedy wrote: > I wanted to chime back in

Re: Juju Openstack - Blocked

Great! Thanks for confirming. I'm happy to have helped de-obfuscate the situation. I may or may not have caused that same little flavor overrun "once" - cannot confirm. ;-) Cheers, Ryan On Mon, Feb 19, 2018 at 4:42 PM, James Beedy wrote: > I wanted to chime back in

Re: Trouble adding IPv6 to installed Keystone charm.

Hi Ken, It is possible that you've hit a bug. But to know for sure, can you tell us the output of this command on the unit?: ip addr show eth0 Also feel free to raise a bug [1] with further details and/or chat on freenode IRC, the #openstack-charms channel. [1]

Re: Proposing Alex Kavanagh for ~charmers

Strong +1 here. On Wed, Apr 26, 2017 at 12:45 PM, Konstantinos Tsakalozos < kos.tsakalo...@canonical.com> wrote: > +1 from me too! > > On Wed, Apr 26, 2017 at 5:07 PM, Tom Barber wrote: > >> Unofficial +1 from the other half of Norwich... >> >> On Wed, Apr 26, 2017 at 3:06

Re: Goodbye Opsworks

Nice work, bdx :) On Fri, Mar 31, 2017 at 8:06 PM, James Beedy wrote: > The day has finally come for me to turn down the last of our Opsworks > instances for our PRM application. This marks the completion of one of many > Opsworks -> Juju conversion projects I've taken on.

Re: Goodbye Opsworks

Nice work, bdx :) On Fri, Mar 31, 2017 at 8:06 PM, James Beedy wrote: > The day has finally come for me to turn down the last of our Opsworks > instances for our PRM application. This marks the completion of one of many > Opsworks -> Juju conversion projects I've taken on.

Re: Can't push to my own team

Hi Tom, On a rare occasion, I've had to use a slightly larger hammer than logout/login, which is to remove (or rename) the following files: ~/.go-cookies ~/.local/share/juju/store-usso-token That should force a fresh re-auth. Cheers, Ryan On Mon, Feb 6, 2017 at 5:38 PM, Tom Barber

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

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

Re: How to reproduce the same build output binaries?

As far as I know, there is no notion of a stable Layer or a stable Interface. That makes it difficult to carry any layered charm as "stable," and quite awkward to cherry-pick and backport fixes to stable charms which depend on Layers and Interfaces. As you mention, you could synthesize stability

Re: Zuul Charm

ie. Project repos would be born, developed and maintained here. :-) https://github.com/openstack?query=charm On Wed, Nov 2, 2016 at 12:28 PM, Ryan Beisner <ryan.beis...@canonical.com> wrote: > As Zuul is an OpenStack project, I'd like to see this developed in line > with the oth

Re: Zuul Charm

ie. Project repos would be born, developed and maintained here. :-) https://github.com/openstack?query=charm On Wed, Nov 2, 2016 at 12:28 PM, Ryan Beisner <ryan.beis...@canonical.com> wrote: > As Zuul is an OpenStack project, I'd like to see this developed in line > with the oth

Re: Zuul Charm

As Zuul is an OpenStack project, I'd like to see this developed in line with the other OpenStack Charms. I would be happy to help light the path along the way to ensure that all efforts are as efficient as possible, and that the resultant layer(s), interface(s) and charm(s) can leverage the

Re: [ANN] Updated Python Juju Client

idated, focused, well built Object > Oriented Python library. > +1000 :-) > Marco > > On Tue, Nov 1, 2016, 4:25 PM Ryan Beisner <ryan.beis...@canonical.com> > wrote: > >> This is good stuff. I think keeping it focused on Juju 2.0 and later, >> completely free o

Re: [ANN] Updated Python Juju Client

idated, focused, well built Object > Oriented Python library. > +1000 :-) > Marco > > On Tue, Nov 1, 2016, 4:25 PM Ryan Beisner <ryan.beis...@canonical.com> > wrote: > >> This is good stuff. I think keeping it focused on Juju 2.0 and later, >> completely free o

Re: [ANN] Updated Python Juju Client

This is good stuff. I think keeping it focused on Juju 2.0 and later, completely free of legacy shims, is a good thing. I'd love to be using this natively instead of the collective stack of [Amulet + Juju-deployer + python-jujuclient], and plan to take it for a spin. Cheers, Ryan On Tue, Nov

Re: [ANN] Updated Python Juju Client

This is good stuff. I think keeping it focused on Juju 2.0 and later, completely free of legacy shims, is a good thing. I'd love to be using this natively instead of the collective stack of [Amulet + Juju-deployer + python-jujuclient], and plan to take it for a spin. Cheers, Ryan On Tue, Nov

Re: lxd hook failed change-config

Hi All - we need a LP bug for this, please. The gerrit review will need to have its commit message updated with the lp bug info so that CI can do bug management on it. Then, once it lands in the charm's master, we can cherry-pick it for a stable backport to the stable charm. Thanks, Ryan On

Re: Feedback wanted: Changes to the Ubuntu Charm

On Thu, Sep 22, 2016 at 8:47 AM, Cory Johns wrote: > For clarity, I'd just like to note that https://jujucharms.com/ubuntu/8 > is the candidate revision, and you can deploy this on 1.25.6 (without > --channel support) by being specific about the revision number: >

Re: Specify lxd container bridge

Where can I get fresh RC builds? On Mon, Sep 19, 2016 at 1:52 PM, Corey Bryant wrote: > I just wanted to follow up on this thread to say I tested with a > pre-release of juju rc1 and it fixed up the issues I was hitting. > > On Sat, Sep 17, 2016 at 9:04 AM, Dimiter

Re: Feedback wanted: Changes to the Ubuntu Charm

i/ubuntu/1 > > I'll have the repo fixed tomorrow. > > > Marco > > On Fri, Sep 16, 2016, 1:36 PM Ryan Beisner <ryan.beis...@canonical.com> > wrote: > >> Was there a merge proposal or pull request for these changes in the >> charm's upstream repo? If

Re: LXD instances fail to start

In one case yesterday, with a full openstack-on-lxd deployed and in use, I quickly hit the too-many-open-files issue. I raised fs.inotify.max_user_instances on the host to 50 which unblocked me for a while. I ended up raising both to 99 and have had smooth sailing since. Currently, the

Re: LXD instances fail to start

In one case yesterday, with a full openstack-on-lxd deployed and in use, I quickly hit the too-many-open-files issue. I raised fs.inotify.max_user_instances on the host to 50 which unblocked me for a while. I ended up raising both to 99 and have had smooth sailing since. Currently, the

Re: Feedback wanted: Changes to the Ubuntu Charm

Is there a merge proposal or pull request for the changes? I'd like to validate with 1.25.6 as the current stable release, but --channel isn't a thing there. I tried to `charm pull ubuntu --channel candidate` but received: ERROR cannot get archive: unauthorized: access denied. Thanks, Ryan

Re: Migration of jenkins-charm to upstream repo

Hi All, With the Jenkins (master) charm moved into upstream [1], we need to do some cleanup on the old code/bug spaces [2]. My thought is that we should triage and move any valid LP bugs over to the upstream issue tracker [3] and retire the old code repo [4] to avoid confusion in development

Re: Followup on 16.07 OpenStack charm release

On Tue, Aug 2, 2016 at 12:32 PM, Daniel Bidwell wrote: > Can I install OpenStack Mitaka on 16.04 with juju-1.25.6 and maas- > 1.9.3? Yes. :) A basic example is available at: https://jujucharms.com/u/openstack-charmers/openstack-base > Does this support using lxd

Re: Question for cosmetic and understandability of breadcrumbs in github

On Fri, Jun 17, 2016 at 2:10 AM, Jay Wren wrote: > If it helps, the charm set command supports arbitrary key values to be > stored in extra-info in the charm store. > > e.g. > > $ charm set cs:~evarlast/trusty/parse-server-0 layer-x=rev1 layer-y=rev2 > > Then this will be

Re: Question for cosmetic and understandability of breadcrumbs in github

Git tagging is certainly helpful to developers, so a big +1 to that for git-based projects. I think there is also a definite need to tie a specific charm store charm revision to its exact place and "time" of origin. Charms which are pushed into the charm store (and the deployed charms) are a bit

Re: Integration with OpenStack app catalog

Hi Merlijn, That's a great question. It is something that we've followed. Take note that the headline in the OpenStack Apps Catalog is: *"The OpenStack Application Catalog will help you make applications available on your cloud."* But, I think it should more accurately state: *"The OpenStack

Re: Introducing a Daily PPA for Juju

Absolutely <3 this. On Thu, May 12, 2016 at 3:36 PM, Nicholas Skaggs < nicholas.ska...@canonical.com> wrote: > Whether you want to track Juju development more closely, or simply like > living on the edge, there is a new ppa available for you. Dubbed the Juju > Daily ppa[1], it] contains the

Re: keystone deploy issue

bundle from the store doesn't work. Brand new install. > > Do I need to do something on my end differently or just wait for it to get > fixed ? > > Thanks! > On Apr 19, 2016 9:19 PM, "Ryan Beisner" <ryan.beis...@canonical.com> > wrote: > >> Hi Ed, >&g

Re: keystone deploy issue

for Trusty-Liberty or Wily-Liberty. Cheers, -- Ryan Beisner QA Engineer, Ubuntu OpenStack Engineering, Canonical, Ltd. irc:beisner gh/gerrit:ryan-beisner lp:~1chb1n On Tue, Apr 19, 2016 at 8:02 PM, ed bond <celpa.f...@gmail.com> wrote: > Anyone know why I might be getting this charm issue:

Re: New feature for charmers - min-juju-version

On Wed, Mar 30, 2016 at 1:30 AM, Martin Packman < martin.pack...@canonical.com> wrote: > On 23/03/2016, Ryan Beisner <ryan.beis...@canonical.com> wrote: > > > > To summarize: > > If we do nothing with regard to juju 1.25.x or the various tools, and if > a &g

Re: New feature for charmers - min-juju-version

On Wed, Mar 23, 2016 at 1:03 PM, roger peppe wrote: > On 23 March 2016 at 15:06, David Ames wrote: > > On 03/21/2016 06:54 PM, Stuart Bishop wrote: > >> > >> On 22 March 2016 at 11:42, Rick Harding > >> wrote: >

Re: New feature for charmers - min-juju-version

re for >> 1.25 is interesting and we'll have to see if clients passed enough info in >> the past to be able to do that intelligently. >> >> >> >> On Mon, Mar 21, 2016 at 10:06 AM Ryan Beisner <ryan.beis...@canonical.com> >> wrote: >> >&g

Re: Proposal: Charm testing for 2.0

on! -- Ryan Beisner QA Engineer, Ubuntu OpenStack Engineering, Canonical, Ltd. irc:beisner gh/gerrit:ryan-beisner lp:~1chb1n On Wed, Mar 16, 2016 at 7:52 PM, Marco Ceppi <marco.ce...@canonical.com> wrote: > Hello everyone! > > This is an email I've been meaning to write for a

Re: Proposal: Charm testing for 2.0

On Thu, Mar 17, 2016 at 8:38 AM, Marco Ceppi <marco.ce...@canonical.com> wrote: > On Thu, Mar 17, 2016 at 12:39 AM Ryan Beisner <ryan.beis...@canonical.com> > wrote: > >> Good evening, >> >> I really like the notion of a bundle possessing functional tests as

Re: charmers + openstack-charmers application

, 2016 at 10:14 AM, Ryan Beisner <ryan.beis...@canonical.com > > wrote: > >> Happy Friday, charmers! >> >> Please consider my application for membership to ~charmers and an >> ~openstack-charmers. >> >> Over the past two years, I've contributed to each o

charmers + openstack-charmers application

rticipated in remote and in-person customer demos of our tool sets and charms, and have given UOS and Charmer Summit demos and talks. I've made a point over the past year or so to chip in on AskUbuntu, generally with OpenStack-specific questions. I am: - https://github.com/ryan-beisne

"Evolution of a Charm" presentation from the Charmer Summit

ck in various environments and use cases. Thanks again to those who attended and participated. Cheers! -- Ryan Beisner QA Engineer, Ubuntu OpenStack Engineering, Canonical, Ltd. irc:beisner lp:~1chb1n -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lis

Re: How should we change default config values in charms?

Actually: the example bundle I listed is moot. It uses the percona-cluster charm. And it's pinned to a specific charm revision like a good little bundle. On Thu, Aug 13, 2015 at 10:57 AM, Ryan Beisner ryan.beis...@canonical.com wrote: Greetings, I'm all for sensible defaults

Re: How should we change default config values in charms?

Greetings, I'm all for sensible defaults and eliminating or mitigating paper cut risk. Those are all good things. I do think we need to take a hard look at the potential impact of a default charm config option value change, any time that is considered. My main concern is that, in changing a

Re: juju devel 1.22-beta4 is available for testing.

Ditto, also seeing that. On Fri, Feb 27, 2015 at 11:16 AM, Jason Hobbs jason.ho...@canonical.com wrote: Hi Curtis, On 02/26/2015 01:47 PM, Curtis Hovey-Canonical wrote: juju-core 1.22-beta4 Development releases use the 'devel' simple-streams. You must configure the 'agent-stream'

Re: Makefile target names

- something_else That file allows customization of much of bundletesters policy. -Ben On Wed, Jan 21, 2015 at 9:05 AM, Ryan Beisner ryan.beis...@canonical.com wrote: Greetings, I'd like to invite discussion on Makefile target names. I've seen a few different takes on Makefile target naming

Re: Makefile target names

Same here, the OpenStack charms have charm proof in the lint target. I expect it would be run twice in that case. On Thu, Jan 22, 2015 at 10:36 AM, Simon Davy bloodearn...@gmail.com wrote: On 22 January 2015 at 16:29, David Britton david.brit...@canonical.com wrote: On Thu, Jan 22, 2015 at

Makefile target names

to succeed in Juju QA / CI. Input and advice are much appreciated! Many thanks, Ryan Beisner -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju