[11:45] <SimonKLB> kwmonroe: very late response, but no, it was against aws
[11:46] <SimonKLB> kwmonroe: it's solved though, i updated the bundletester issue thread about my issue
[13:48] <SimonKLB> any jujucharms.com admins here? need help with a broken login due to updated user on launchpad
[14:02] <Neepu> Hey. I'm looking into backing up a OpenStack system, that is built with nova-lxd-containers (All-in-one Ubuntu OpenStack) are there any documentation to help with that? I'm assuming that backup is slightly different than usual due to the use of containers.
[14:04] <tvansteenburgh> SimonKLB: rick_h can probably point you in the right direction
[14:05] <tvansteenburgh> Neepu: beisner or jamespage might know
[14:08] <beisner_> hi Neepu - the all-on-one openstack scenario is a handy dev/test/demo scenario, but it isn't recommended for production use cases.  openstack is a cloud, and clouds are meant to be distributed.  as such, we've not explored or documented a backup routine for that use case.
[14:09] <Neepu> hi beisner_ ty for the answer, if i were to backup such a system, do you have a suggestion? it is not meant to be used in a production environment.
[14:10] <beisner_> Neepu - there are a number of things that could be done.  when you say back up, are you talking about backing up the backing storage for running instances, or backing up the control and data plane of the cloud itself, or both?
[14:12] <Neepu> I haven't really settled on that yet, as i'm not too familiar with LXD containers yet. But the requirements i'm dealing with is that, it should be easy to restore again. The most important feature would be to backup the guestOSes, but i think there already is a feature for that.
[14:16] <Neepu> yep "nova backup", which probly backups inside the nova container.
[14:19] <beisner_> An OpenStack cloud as-a-whole isn't really something that's meant to be backed up and restored, as one might do with a traditional application.  It's a stack of independent applications and api services, each of which have certain needs.  The process for doing that at the application level, regardless of the substrate, would be the same as is documented in the upstream openstack docs.
[14:19] <beisner_> The process for doing that on a machine (container) level, is not documented or tested for use against an entire openstack cloud, but if this is a dev/test environment, it'd be interesting to see if lxd snapshots are helpful.
[14:24] <Neepu> I see, i think i'd be good with lxd snapshot to extract the backup
[14:25] <Neepu> I'm not too familiar with Juju's approach to OpenStack, but would snapshoting all LXD containers and start them let me run a functional OpenStack cloud?
[14:28] <beisner_> Neepu - i don't believe that is tested.  the recommended approach to OpenStack Charms delivered via Juju is to use an HA topology, where api services are disposable, etc.
[14:29] <beisner_> ie.  so when a machine dies, it's ok, there are 2 other machines that take the load while a repair/replacement is made.
[14:29] <beisner_> that's the "cloudier" way to address this.
[14:29] <Neepu> i see
[14:30] <Neepu> cheers for the answers, i'll head off now :-)
[14:31] <beisner_> Neepu - yw, happy to help.  see you around & best to ya!
[15:26] <beisner_> hi vds - belated pong:  invalid region "" seems to be meaningful there.  have you set the region in your juju cloud config?  here's an example of what we do in CI:  https://github.com/openstack-charmers/charm-test-infra/blob/master/juju-configs/clouds.yaml#L27
[15:27] <vds> beisner_: hi! :) how do I get the value for region from Openstack?
[15:29] <beisner_> hi vds - it'd be the value set at deploy time (on nova-cloud-controller).  if one wasn't specified, it'll use the default: https://github.com/openstack/charm-nova-cloud-controller/blob/master/config.yaml#L125
[15:29] <beisner_> RegionOne
[15:30] <vds> beisner_: thanks
[15:30] <beisner_> cheers vds :) yw
[15:33] <kjackal> 243667
[15:34] <rick_h> mhilton: we're helping SimonKLB here
[15:34] <rick_h> SimonKLB: broke the system!
[15:36] <mhilton> hi SimonKLB could you please try logging in on the staging system https://staging.jujucharms.com/ This should help resolve the login problems on jujucharms.com itself.
[16:18] <Budgie^Smore> o/ juju world
[16:49] <lazyPower> heya Budgie^Smore
[17:30] <Budgie^Smore> what's happening today?
[17:34] <lazyPower> Not much for me :)
[18:37] <SimonKLB> mhilton: confirmed working :) thaanks
[19:40] <mhilton> SimonKLB, thanks for that. unfortunately I don't have access to our production system to update that myself, but it is in the queue for the people that do, it's fairly simple so should be done reasonably quickly.
[19:49] <SimonKLB> mhilton: no worries, thanks for looking into it