=== mup_ is now known as mup === mup_ is now known as mup === kelvinliu__ is now known as kelvinliu === kina___ is now known as kina__ === razorz_ is now known as razorz === mup_ is now known as mup === mup_ is now known as mup === mup_ is now known as mup [08:42] manadart: you around? [08:43] jam: I am. [08:43] In Oracle HO. [08:43] omw [09:14] https://github.com/juju/replicaset/pull/8 [09:15] manadart: ^^ [09:25] manadart: https://github.com/juju/juju/pull/8618 [12:12] Hi [12:13] I wrote a charm based on the docker layer - https://jujucharms.com/docs/1.24/authors-charm-with-docker [12:13] and I have an issue - it's not installing anything - juju.worker.uniter.operation runhook.go:116 skipped "install" hook (missing) [12:13] and it's copy paste from the article [12:13] can somebody help me with this [12:14] elmaciej: hmm, did you run charm build? normally that's because you edit the layer stuff but don't charm build or deploy the build charm (that generates the hooks) [12:14] well I did charm build ./mycharm [12:15] and then juju deploy ./mycharm --to kvm:0 [12:26] jam: https://github.com/juju/juju/pull/8619/files [12:27] Going to scan the current known intermittent failures. [12:36] manadart: one change definitely needed, and a discussion of 2 or 3 things to think about [12:40] rick_h_: this is my output : https://pastebin.com/0Bmgf0fM [12:40] rick_h_: should I add more things ? I just want to deploy a docker, no relations, no interfaces ... [12:52] jam: Implemented all of your suggestions; much nicer. Tests using that code pass repeatedly without the buffer, so it is gone. [12:54] elmaciej: ok and you deployed "/mnt/c/Users/devep/PycharmProjects/charms/aiakafka/builds/aiakafka" so that the built charm, with the install hook, is what gets run? [12:54] yes, I deployed this one using : juju deploy ./aiakafka [12:54] and it deploys but nothing is happening inside this charm [12:54] so thats weird [12:55] elmaciej: right, but it needs to be juju deploy ./builds/aiakafka [12:55] ohhhhh' [12:55] assuming you're terminal is at the directory you're righting the charm from [12:55] yep [12:55] ok, will try now [12:55] <3 [15:15] ello hml [15:17] ejat: hi [15:17] your work around works .. [15:17] ejat: good news, i tried it locallly, but confirmation is nice [15:17] but .... [15:17] later i got this : found 0 image metadata in default cloud images [15:18] do i need to configure the simplestream ? [15:18] ejat: yes you do [15:18] its a must ? [15:18] then bootstrap with --config swift_URL ? [15:19] ejat: for OpenStack yes - juju pulls the images from glance and needs to know how to find the ones you want to use [15:19] i did the simplestream [15:19] but its doesnt work for me :( [15:19] ejat: just a sec [15:20] ejat: did you follow the instructions here: https://jujucharms.com/docs/stable/howto-privatecloud [15:20] ejat: --config image-metadata-url=$SWIFT_URL [15:20] and you need a network defined as well for bootstrap [15:21] ejat: usually [15:23] https://paste.ubuntu.com/p/9DdRCcmVDR/ [15:28] ejat: try ‘wget http://172.15.1.99/swift/v1/simplestreams/images/streams/v1/index.json' [15:31] im having problem to add this endpoint [15:31] openstack endpoint create --region $REGION --publicurl $SWIFT_URL/simplestreams/images \ [15:31] --internalurl $SWIFT_URL/simplestreams/images product-streams [15:31] ejat: do you have admin permissions for the project in openstack? [15:31] yes [15:32] ejat: but you can’t create an endpoint yes? [15:32] parameter error [15:33] ejat: which parameter is causing the problem? [15:34] --region [15:34] https://paste.ubuntu.com/p/G8GBXxpX4G/ [15:35] and some of the parameter are differ from the documentation [15:35] there is no --internalurl [15:35] --publicurl [15:36] ejat: which version of the openstack client are you using? [15:36] 3.14.0-0ubuntu1 [15:38] ejat: while i figure this out, perhaps the client options have changed… you can specify a local path to the streams you created [15:39] ejat: use --metadata-source [15:40] --metadata-source=~/simplestream ? [15:41] using local works [15:42] thanks [15:42] ejat: k [15:43] ejat: which version of OpenStack are you using? [15:44] hml: queens [15:44] ejat: i see the problem in the doc - the instructions are for identity v2, not identity v3 [15:44] hml: i suspected that [15:44] ejat: https://docs.openstack.org/python-openstackclient/pike/cli/command-objects/endpoint.html#endpoint-create [15:45] i guess the everything need to be change toward v3 [15:46] btw, how to bootstrap the controller with public ip ? [15:46] include the config network ? [15:46] ejat: juju show-cloud --include-config [15:47] will show the openstack config options for bootstrap and models [15:47] you’ll need to define a network (private) and —use-floating-ip [15:47] —external-network if you wish [15:48] ok yeah [15:48] --use-floating-ip [15:50] ejat: can you test something for me please… to update the docs: see if ‘openstack endpoint create --region RegionOne product-streams public http://172.15.1.99/swift/v1/simplestreams/images' works [15:51] yeah [15:51] ejat: ty [15:51] https://paste.ubuntu.com/p/gJMrqQwMSp/ [15:51] you’ll need to do run again replacing public with internal - that should setup the endpoint for you [15:52] * ejat wondering is it only me using queens now :) [15:52] both work public n internal [15:53] how to use the --use-floating-ip ? [15:53] ejat: see if the wget line wokrs now please? [15:54] image-metadata-url works [15:54] after create public n internal endpoint [15:54] ejat: perfect [15:54] how to use the --use-floating-ip ? [15:56] --config image-metadata-url=xxxxx use-floating-ip [15:57] ejat: —config use-floating-ip=true --config image-metadata-url=xxxxx [15:57] owh [15:57] ejat: once you have nailed down what config items to bootstrap with - you can add them to the cloud config [15:58] ok [15:59] ejat: since you setup the product-streams endpoint - juju will find it automagically - so you can leave that off the bootstrap if you wish [15:59] noted [16:01] ejat: i bootstrap openstack with the following config: https://paste.ubuntu.com/p/FYPSRvfPJM/ - so i just have to do ‘juju boostrap serverstack-os tuesday’ for example [16:04] 00:02:30 DEBUG juju.provider.common bootstrap.go:564 connection attempt for 172.16.5.206 failed: ssh: connect to host 172.16.5.206 port 22: Connection timed out [16:04] okie my bad [16:04] its my network access [16:04] ejat: that happens a couple times [16:04] okay.. [16:05] you do see it a few times sometimes while the instance is coming up.. unless juju fails you can ignore it usually [16:08] ok thanks [16:09] ejat: i’m creating a pr to update the doc - thanks for your help there [16:09] u r most welcome .. thanks to u too :) [16:10] btw, will you be at vancouver next month ? [16:11] ejat: I will not, I’m not on the openstack team :-) I work on juju itself [16:11] owh .. [16:12] its quite a years i stop writing my 1st charm [16:12] * ejat now more being a user :) [16:13] * ejat assist @ contribute as much as i can ... [16:13] :-) [16:13] asked question , file bugs [16:13] * ejat missed UDS :) [16:13] thats where i met all the juju guru [16:14] guru @ ninja [16:15] ejat: there should be some at vancouver [16:15] yeah .. === rahul is now known as Guest57485 [16:41] hi === frankban is now known as frankban|afk [18:54] Hello just started working with JUJU for an openstack install can someone please tell me what the correct filesystem layout should be for the dashboard. [19:09] acNEt: what do you mean? [19:09] acNEt: `juju deploy openstack-dashboard` [19:11] acNEt: ^ try that and see what you get by default [19:15] I deployed the dashboard but I keep getting permissions issues. Is it supposed to be /var/lib/openstack-dashboard or /usr/share/openstack-dashboard? [19:54] acNEt: context? [19:54] to what you are trying to do