Sunday, 2017-08-13

*** schwicht has joined #openstack-helm00:09
*** schwicht has quit IRC00:13
*** leakypipes has quit IRC01:09
*** felipemonteiro has joined #openstack-helm03:04
openstackgerritPete Birley proposed openstack/openstack-helm master: WIP: Ironic Chart  https://review.openstack.org/49027103:25
*** gouthamr has joined #openstack-helm03:32
*** felipemonteiro has quit IRC04:24
openstackgerritPete Birley proposed openstack/openstack-helm master: WIP: Ironic Chart  https://review.openstack.org/49027104:44
*** gouthamr has quit IRC06:04
*** gouthamr has joined #openstack-helm06:06
*** gouthamr has quit IRC10:30
*** schwicht has joined #openstack-helm11:34
*** schwicht has quit IRC13:17
openstackgerritPete Birley proposed openstack/openstack-helm master: WIP: Ironic Chart  https://review.openstack.org/49027114:44
openstackgerritPete Birley proposed openstack/openstack-helm master: WIP: Ironic Chart  https://review.openstack.org/49027114:59
*** mattmceuen has quit IRC15:10
*** schwicht has joined #openstack-helm15:15
*** schwicht has quit IRC15:22
openstackgerritPete Birley proposed openstack/openstack-helm master: WIP: Ironic Chart  https://review.openstack.org/49027115:33
osh-chatbot<kubernaut> Hi, I've installed kubernetes on 5 metal servers with kubespray using kubernetes 1.6.7 and followed the guide here: http://openstack-helm.readthedocs.io/en/latest/install/multinode.html  All things went well till installing nova, I'm getting after running:  root@ubuntu-xenial:~/openstack-helm# helm install --namespace=openstack --name=nova local/nova   --set pod.replicas.api_metadata=2   --set pod.replicas.osapi=2   --set16:46
osh-chatbotpod.replicas.conductor=2   --set pod.replicas.consoleauth=2   --set pod.replicas.scheduler=2   --set pod.replicas.novncproxy=2  The following error:  Error: release nova failed: Service "metadata" is invalid: spec.clusterIP: Invalid value: "10.97.120.234": provided IP is not in the valid range16:46
osh-chatbot<mariusv> heya @kubernaut you’ll have to replace the IP in both nova and neutron charts with one from your own range  here is where the change has to happen in nova: https://github.com/openstack/openstack-helm/blob/master/nova/values.yaml#L115-L116 and here is for neutron: https://github.com/openstack/openstack-helm/blob/master/neutron/values.yaml#L506-L50716:52
osh-chatbot<kubernaut> @mariusv great, thx kindly16:54
osh-chatbot<mariusv> no worries man16:55
osh-chatbot<mariusv> don’t forget to update helm once you updated the values :slightly_smiling_face:16:55
v1k0d3nthis should be documented a little better.17:09
v1k0d3nsrwilkers can we document this one together?17:10
v1k0d3ni'm sort of wondering if this is what caught bryan_att a little bit as well. looks like it snuck in back in june, but the changes weren't documented with it.17:11
v1k0d3nmaybe alanmeadows  can give some direction on how to best automatically determine/assign this out, rather than have the static entry in place. at the very least it should be caught somewhere.17:12
osh-chatbot<kubernaut> changed the nova_metadata_ip to 10.0.0.0 and did a "helm repo update" and "helm update" but I'm getting the same error: Error: release nova failed: Service "metadata" is invalid: spec.clusterIP: Invalid value: "10.97.120.234": provided IP is not in the valid range17:14
v1k0d3n@kubernaut you could change it in values and then just rerun make.17:15
osh-chatbot<kubernaut> ahhhh, thanks!17:16
v1k0d3nor you can do a 'helm upgrade --set network. metadata.ip=<ip>' to update it as well.17:16
v1k0d3nthat's what i usually do...as it's a bit faster, more flexible for me :)17:16
osh-chatbot<mariusv> or that way :slightly_smiling_face: I prefer to just edit the file so I can keep my changes for the staging env :slightly_smiling_face:17:25
osh-chatbot<mariusv> also had no idea you can do that with helm17:26
*** gouthamr has joined #openstack-helm17:26
osh-chatbot<kubernaut> now I'm getting a time out: kubectl get svc --all-namespaces Error from server (ServerTimeout): the server cannot complete the requested operation at this time, try again later (get services)  Master restart?17:51
*** gouthamr has quit IRC18:06
osh-chatbot<mariusv> you were supposed to use a `/32` IP most likely you used a already used IP and borked your cluster…next time choose an IP which is not used18:09
osh-chatbot<v1k0d3n> @kubernaut can you make sure that Helm serve is running?18:31
osh-chatbot<v1k0d3n> @mariusv it's good to keep those values for sure. It can also be nice to automate via Helm using the --set override. I like both options, just for difference scenarios, I guess.18:33
osh-chatbot<mariusv> @v1k0d3n yeah, just haven’t knew you can pass them to helm via --set override. Thanks for that18:33
*** mattmceuen has joined #openstack-helm18:34
*** schwicht has joined #openstack-helm19:11
osh-chatbot<v1k0d3n> Absolutely! Try using the upgrade as well. That's a huge help. :D19:28
*** gouthamr has joined #openstack-helm19:38
*** gouthamr has quit IRC19:52
*** gouthamr has joined #openstack-helm20:55
*** gouthamr has quit IRC21:54
*** mattmceuen has quit IRC22:00
*** gouthamr has joined #openstack-helm22:14
openstackgerritPete Birley proposed openstack/openstack-helm master: WIP: Ironic Chart  https://review.openstack.org/49027122:26
*** schwicht has quit IRC23:56

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!