Dane, I’ve heard Yolanda has done good work on making disk image builder build fedora atomic properly consistently. This may work better than the current image building tools available with atomic if you need to roll your own. Might try pinging her on irc for advice if you get jammed up here. Might consider consulting tango as well as I handed off my knowledge in this area to him first and he has distributed to the rest of the Magnum core reviewer team. I’m not sure if tango and Yolanda have synced on this – recommend checking with them.
Seems important to have a working atomic image for both Mitaka and Newton. Regards -steve From: "Dane Leblanc (leblancd)" <lebla...@cisco.com> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Thursday, September 8, 2016 at 2:18 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [magnum] Fedora Atomic image that supports kubernetes external load balancer (for stable/mitaka) Does anyone have a pointer to a Fedora Atomic image that works with stable/mitaka Magnum, and supports the kubernetes external load balancer feature [1]? I’m trying to test the kubernetes external load balancer feature with stable/mitaka Magnum. However, when I try to bring up a load-balanced service, I’m seeing these errors in the kube-controller-manager logs: E0907 16:26:54.375286 1 servicecontroller.go:173] Failed to process service delta. Retrying: failed to create external load balancer for service default/nginx-service: SubnetID is required I verified that I have the subnet-id field set in the [LoadBalancer] section in /etc/sysconfig/kube_openstack_config. I’ve tried this using the following Fedora Atomic images from [2]: fedora-21-atomic-5.qcow2 fedora-21-atomic-6.qcow2 fedora-atomic-latest.qcow2 According to the Magnum external load balancer blueprint [3], there were 3 patches in kubernetes that are required to get the OpenStack provider plugin to work in kubernetes: https://github.com/GoogleCloudPlatform/kubernetes/pull/12203 https://github.com/GoogleCloudPlatform/kubernetes/pull/12262 https://github.com/GoogleCloudPlatform/kubernetes/pull/12288 The first of these patches, “Pass SubnetID to vips.Create()”, is apparently necessary to fix the “SubnetID is required” error shown above. According to the Magnum external load balancer blueprint [3], the fedora-21-atomic-6 image should include the above 3 fixes: “Our work-around is to use our own custom Kubernetes build (version 1.0.4 + 3 fixes) until the fixes are released. This is in image fedora-21-atomic-6.qcow2” However, I’m still seeing the “SubnetID is required” errors with this image downloaded from [2]. Here are the kube versions I’m seeing with this image: [minion@k8-64n4bna2v6-0-ffukgho7n7tf-kube-master-fif5b6pivdmy sysconfig]$ rpm -qa | grep kube kubernetes-node-1.2.0-0.15.alpha6.gitf0cd09a.fc23.x86_64 kubernetes-1.2.0-0.15.alpha6.gitf0cd09a.fc23.x86_64 kubernetes-client-1.2.0-0.15.alpha6.gitf0cd09a.fc23.x86_64 kubernetes-master-1.2.0-0.15.alpha6.gitf0cd09a.fc23.x86_64 [minion@k8-64n4bna2v6-0-ffukgho7n7tf-kube-master-fif5b6pivdmy sysconfig]$ Does anyone have a pointer to a Fedora Atomic image that contains the 3 kubernetes fixes listed earlier (and works with stable/mitaka)? Thanks! -Dane [1] http://kubernetes.io/docs/user-guide/services/#type-loadbalancer [2] https://fedorapeople.org/groups/magnum/ [3] https://blueprints.launchpad.net/magnum/+spec/external-lb
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
