Re: [Openstack-operators] Newton consoleauth HA tokens
Chris, Good to see that you finally got the issue resolved! One more thing, the [default] should be [DEFAULT] I believe. Best regards George Paraskevas On 25 January 2017 at 03:21, Chris Apsey wrote: > Saverio, > > Here is my pertinent config data: > > [default] > memcached_servers = 10.10.6.240:11211 > > [cache] > enablde = True <<< I just noticed this > as I copied into the email. > memcache_servers = 10.10.6.240:11211 > backend = oslo_cache.memcache_pool > > [keystone_authtoken] > memcached_servers = 10.10.6.240:11211 > > > See above - I just noticed my config typo as I was getting ready to send > this. Changing it to 'enabled' seems to have solved the issue. Spelling > counts. This is a working config for anyone else who runs into the same > problems. Be sure to specify the backend under [cache], as the default is > null. > > > Thanks for the assist! > > Chris > > --- > v/r > > Chris Apsey > bitskr...@bitskrieg.net > https://www.bitskrieg.net > > On 2017-01-24 11:36, Saverio Proto wrote: > >> Did you try to restart memcached after chaning the configuration to HA ? >> >> there are two sections where you can configure, memcached_servers >> [DEFAULT] >> [keystone_authtoken] >> >> how your config looks like ? >> >> Saverio >> >> >> 2017-01-24 6:48 GMT+01:00 Chris Apsey : >> >>> All, >>> >>> I attempted to deploy the nova service in HA, but when users attempt to >>> connect via the console, it doesn't work about 30% of the time and they >>> get >>> the 1006 error. The nova-consoleauth service is reporting their token as >>> invalid. I am running memcached, and have tried referencing it using >>> both >>> the legacy memcached_servers directive and in the new [cache] >>> configuration >>> section. No dice. If I disable the nova-consoleauth service on one of >>> the >>> nodes, everything works fine. I see lots of bug reports floating around >>> about this, but I can't quite get the solutions I have found reliably >>> working. I'm on Ubuntu 16.04 LTS+Newton from UCA. >>> >>> Ideas? >>> >>> -- >>> v/r >>> >>> Chris Apsey >>> bitskr...@bitskrieg.net >>> https://www.bitskrieg.net >>> >>> ___ >>> OpenStack-operators mailing list >>> OpenStack-operators@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>> >> > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Newton consoleauth HA tokens
Hello, You should also define memcached servers in the default Nova section I believe. Try that. Best regards George On Tue, 24 Jan 2017, 07:48 Chris Apsey, wrote: > All, > > I attempted to deploy the nova service in HA, but when users attempt to > connect via the console, it doesn't work about 30% of the time and they > get the 1006 error. The nova-consoleauth service is reporting their > token as invalid. I am running memcached, and have tried referencing it > using both the legacy memcached_servers directive and in the new [cache] > configuration section. No dice. If I disable the nova-consoleauth > service on one of the nodes, everything works fine. I see lots of bug > reports floating around about this, but I can't quite get the solutions > I have found reliably working. I'm on Ubuntu 16.04 LTS+Newton from UCA. > > Ideas? > > -- > v/r > > Chris Apsey > bitskr...@bitskrieg.net > https://www.bitskrieg.net > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] neutron flat network on existing bridge fails
Hello, With Linux bridge, I believe you should use physical _interface_mappings =provider:br224 Beat regards George On Tue, 16 Aug 2016, 16:48 Paul Dekkers, wrote: > Hi, > > I'm using Ubuntu 16.04.1 with it's Mitaka release, and neutron flat > networking with linuxbridge+ml2: > > I'd like to attach my flat neutron network to an existing linuxbridge on > my system. This fails with an error like: > > 2016-08-16 15:07:00.711 7982 DEBUG > neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent > [req-720266dc-fe8d-47c4-a7df-19fee7a8d679 - - - - -] Skip adding device > tapf99013c6-6b to br224. It is owned by compute:nova and thus added > elsewhere. _add_tap_interface > > /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py:473 > > with the result that the tap interface is added to a newly created > bridge instead of the existing (br224) bridge. > > I've set > bridge_mappings = provider:br224 > in /etc/neutron/plugins/ml2/linuxbridge_agent.ini > > (because if I use > physical_interface_mappings = provider:vlan224 > the vlan224 interface is actually detached from the original bridge) > > I've created the bridge via /etc/network/interfaces: > > auto br224 > iface br224 inet manual > bridge_ports vlan224 > > auto vlan224 > iface vlan224 inet manual > vlan_raw_device eno1 > > Reason for doing this is that I'd like to attach an lxc container to > this bridge (and only when neutron needs it the "brqf709c220-fd" (with > for me an unpredictable name) is setup, so I can't use that), and/or > like to have the machine itself use an interface on this network. (This > is also my reason for using flat networking, and not vlan.) > > I've created the neutron networks with > > neutron net-create default --shared --provider:physical_network provider > --provider:network_type flat > > (I would repeat this with a different physical_network name if I need > more VLANs, instead of using the --provider:segmentation_id.) > > Instance networking works when I let nova/neutron create the bridge > interfaces. > > Any idea why neutron refuses to use the bridge_mappings and why it > creates a new interface? > > Regards, > Paul > > P.S. To me it feels like this is what people would need when setting up > a small single-network setup (both for instances and OpenStack), but > most examples use multiple networks anyway. > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] [puppet] Can we install OpenStack components using puppet but through source?
Hello, I believe you can do so with openstack-ansible, its a set of ansible playbooks that orchestrate openstack from source using wheels. I think there you can select different branches for selected components. If this is what you want https://github.com/openstack/openstack-ansible Thanks George. On Fri, 13 Nov 2015, 09:07 Okan bhan wrote: > Hi Guys, > > I'm trying installing OpenStack using puppet modules. I'm able to setup > all-in-one installation for liberty release. > > This works fine but I was hoping, if there is a way I can install services > (say keystone) from source code. Essentially I was hoping if I can use > puppet to setup a developer workstation. > > Thanks > Alok Kumar > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Need help with adding instance with fixed ip in external network with out using private and floating ip.
Hello again, that's great! As for the method you mentioned i haven't tried it but i will just to see what happens. Thanks again George On 31 October 2015 at 15:29, Geo Varghese wrote: > Hi George, > > I just tried your method and it seems working perfectly :) > > Thanks for your valuable inputs. > > On Sat, Oct 31, 2015 at 6:42 PM, Geo Varghese wrote: > >> Hi George, >> >> Thanks for the update. Yes, you are right that is the exact requirement. >> >> "assign ip from that network directly to the instance with out the use of >> a private net and floating ip over nat" >> >> I got a update about external network like this from list. Thats why i >> tried it like that. >> >> == >> A Neutron router can also be attached to the same network so that >> instances in non-routable tenant networks can obtain floating IPs from the >> same 'public' network. At one time non-admin users were not allowed to >> attach VMs to 'external' networks but I believe that restriction was >> removed around Kilo or so. >> >> Yes, as long as the network is marked as both 'shared' and external, a >> tenant can attach VMs and router gateway interfaces directly to it. >> == >> >> According to your inputs, the above method is not correct right? >> >> >> And about the method of adding bridge to compute node, do we need to add >> following options? >> >> bridgemapping in ml2 conf >> enable_distributed_routing to true >> >> Thanks again for your time. >> >> >> On Sat, Oct 31, 2015 at 2:20 PM, George Paraskevas >> wrote: >> >>> Hello there, >>> >>> From what I understand you want to assign ip from that network directly >>> to the instance with out the use of a private net and floating ip over nat. >>> Now you need to correct some things and you will be quite there. First when >>> you create an external network then that network can only work though >>> floating ip. So instead create the same net but don't mark it as external. >>> Also you need that bridge on compute nodes because the VM nic will bind >>> directly to it. So don't configure l3 agent just configure ml mapping for >>> that network. I hope you can under stand and I also hope I understood you. >>> Thanks >>> George >>> >>> On Sat, 31 Oct 2015, 08:43 Geo Varghese wrote: >>> >>>> Hi Team, >>>> >>>> I need help with adding instance with fixed ip in external network with >>>> out using private and floating ip. >>>> >>>> I have tested it using following steps >>>> >>>> 1) Created a new nic - eth4 for new external network(192.168.122.0/24) >>>> in controller. >>>> >>>> 2) Created a bridge - br-ex2 and added eth4 as port to bridge. >>>> >>>> 3) Mapped this bridge in ml2 conf and restarted l3 agent and neutron >>>> plugin >>>> >>>> 4) Then added shared external network Ext2 in openstack. Then added >>>> subnet as 192.168.122.0/24 >>>> >>>> 5) Added it to the router- router2 as interface with a IP - >>>> 192.168.122.99. Network topology shows the interface is active with this >>>> IP. Ping to this ip is also working from other machines. >>>> >>>> Later created VM in this network, but it failed with following error in >>>> nova-compute log. >>>> >>>> = >>>> Unable to mount image >>>> /var/lib/nova/instances/903a6630-941c-4fd0-948f-85522fa20979/disk with >>>> error libguestfs installed but not usable (/usr/bin/supermin-helper exited >>>> with error status 1. >>>> == >>>> >>>> Please check attached screen shot of network topology. >>>> >>>> Please help me with your inputs. >>>> >>>> -- >>>> -- >>>> Regards, >>>> Geo Varghese >>>> ___ >>>> OpenStack-operators mailing list >>>> OpenStack-operators@lists.openstack.org >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>>> >>> >> >> >> -- >> -- >> Regards, >> Geo Varghese >> > > > > -- > -- > Regards, > Geo Varghese > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Need help with adding instance with fixed ip in external network with out using private and floating ip.
Hello there, >From what I understand you want to assign ip from that network directly to the instance with out the use of a private net and floating ip over nat. Now you need to correct some things and you will be quite there. First when you create an external network then that network can only work though floating ip. So instead create the same net but don't mark it as external. Also you need that bridge on compute nodes because the VM nic will bind directly to it. So don't configure l3 agent just configure ml mapping for that network. I hope you can under stand and I also hope I understood you. Thanks George On Sat, 31 Oct 2015, 08:43 Geo Varghese wrote: > Hi Team, > > I need help with adding instance with fixed ip in external network with > out using private and floating ip. > > I have tested it using following steps > > 1) Created a new nic - eth4 for new external network(192.168.122.0/24) in > controller. > > 2) Created a bridge - br-ex2 and added eth4 as port to bridge. > > 3) Mapped this bridge in ml2 conf and restarted l3 agent and neutron plugin > > 4) Then added shared external network Ext2 in openstack. Then added subnet > as 192.168.122.0/24 > > 5) Added it to the router- router2 as interface with a IP - > 192.168.122.99. Network topology shows the interface is active with this > IP. Ping to this ip is also working from other machines. > > Later created VM in this network, but it failed with following error in > nova-compute log. > > = > Unable to mount image > /var/lib/nova/instances/903a6630-941c-4fd0-948f-85522fa20979/disk with > error libguestfs installed but not usable (/usr/bin/supermin-helper exited > with error status 1. > == > > Please check attached screen shot of network topology. > > Please help me with your inputs. > > -- > -- > Regards, > Geo Varghese > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] about network configuration
Hello, Why dhcp; configure it manual. Also what kind of network setup do you have; does your network have a gateway on management subnet; George. On Thu, Sep 10, 2015, 17:31 applyhhj wrote: > Hi Everyone, > >I am new to openstack. When following the Install Guidance(kilo > version) for Ubuntu, I was unable to correctly configure the network. I > followed the Guidance and set up 1 controller node, 1 network node and 3 > computing nodes. All configuration is almost the same as the Guidance. > However, if I set the gateway of management interface in network node to > 10.0.0.1 and change external interface to “dhcp” mode, which is required by > my external network environment, then I cannot ping other nodes from > network nodes. So I comment the gateway configuration and everything works > fine. But only network node can access to external network, other nodes are > not able to ping outside website. It will throw “unknown host” error. Can > anyone help me with this problem please? Thank you very much!! > > > 2015-09-10 > -- > applyhhj > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
