[Openstack] API endpoint naming in Keystone
I just now upgraded my test install (nova, keystone and glance) from Liberty to Mitaka. Immediately after the upgrade, every compute query in the openstack client or Horizon started returned a 404. I resolved this problem by changing all of my nova endpoints in Keystone that looked like this: http://labtestnet2001.codfw.wmnet:8774/v2/$(tenant_id)s so that they now look like this: http://labtestnet2001.codfw.wmnet:8774/v2 I can't find any online documentation to support this change. Every how-to guide includes the $(tenant_id)s component of the endpoint for nova, although other services (e.g. glance) seem not to recommend it. Can anyone help me understand what's going on here? Are the docs just out of date, or do I have some subtle breakage in my install that this is revealing? Thanks! -Andrew ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] [neutron] Integration SDN controller
Hi colleagues, I want to do the Neutron integration (liberation version) with an SDN Ryu controller. But so far I have not found much that could help me how to do this. Anyone here already made this integration? Do you know how to proceed? Please help me :) -- Thanks, ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] [neutron] Advice on replacing (non-openstack) existing IPv6 setup
Hi, I'm seeking some advice on replacing a libvirt/manual setup with an openstack/VM based one. Most of the work has been done and seems to work, however, the existing setup has working IPv6 on the host as well as the guests -- something that I have failed to achieve so far with the OpenStack replacement. My situation is a single host with a /64 subnet assigned. The guests and the host have been assigned an IP from the available /64 subnet. All traffic from the host and the guests needs to be routed upstream through fe80::1. Everything works as long as I don't set up any IPv6 at all. But when I set up the external interface (enp4s0) with an IPv6 address (no matter which one), the linux bridge receives "File exists" errors from RTNETLINK. Can anyone point me to configuration examples or installation documentation for the case I'm trying to configure? (Note that I have looked at this page: https://docs.openstack.org/mitaka/networking-guide/config-ipv6.html but the fact that it talks a lot about prefix delegation makes it very confusing, tbh...) Thanks in advance for any advice you can provide! -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in. ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[Openstack] [HEAT] order in attributes list
Hi colleagues, I have the following HOT configuration of a port: n1-wan: type: OS::Neutron::Port properties: fixed_ips: - { subnet: e-subnet1, ip_address: 51.x.x.x } - { subnet: e-subnet2, ip_address: 25.x.x.x } when I try to extract these values in template using {get_attr}, then, regardless of fixed_ips' order in port definition (either "subnet1, subnet2" or "subnet2, subnet1"), the value of { get_attr: [n1-wan, fixed_ips] } always give the following result: output_value: - ip_address: 25.x.x.x subnet_id: ... - ip_address: 51.x.x.x subnet_id: ... and, thus, { get_attr: [n1-wan, fixed_ips, 1, ip_address ] } gives me 51.x.x.x value. So, the question is - how the list of fixed_ips is ordered? Is there way to know for sure index of entry I'm interested in? Thank you. -- Volodymyr Litovka "Vision without Execution is Hallucination." -- Thomas Edison ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack