Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
Hi Martinx, Could you please share your .conf files showing how we can have both Linux Bridges and OpenvSwitch configurations? Thank you a lot. Em qui, 21 de abr de 2016 às 17:30, Paras pradhan escreveu: > Thanks Martinx > > On Thu, Apr 21, 2016 at 2:50 PM, Martinx - ジェームズ < > thiagocmarti...@gmail.com> wrote: > >> I just manage to make OpenStack Mitaka to work with both Linux Bridges, >> and OpenvSwitch... >> >> Everything is work on both "All in One" and multi-node environments. >> >> Very soon, I'll post instructions about how to use the Ansible automation >> that I am developing to play with this... >> >> Then, you guys will be able to deploy it, on a spare box (or VMs), and >> then, compare with failing deployemnts... >> >> Cheers! >> >> On 21 April 2016 at 16:44, Paras pradhan wrote: >> >>> The neutron section was missing from nova.conf and now the instances >>> work but having issues with metadata server. instances boot but no network >>> access. >>> Thanks >>> Paras. >>> >>> On Thu, Apr 21, 2016 at 9:58 AM, Martinx - ジェームズ < >>> thiagocmarti...@gmail.com> wrote: >>> My nova.conf is this one: https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_cmpt/templates/mitaka/nova.conf However, I'm facing connectivity problems when with OpenvSwitch deployments, investigating it now... On 21 April 2016 at 11:04, Paras pradhan wrote: > Yes . I did. here is my nova.conf. Can you share yours? > http://paste.openstack.org/show/494988/ > > On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block wrote: > >> Okay, did you restart the respective services on all nodes after the >> changes in your config files? If the same error still occurs then you >> might >> haven't found all occurrences of the option auth_plugin, did you replace >> it >> in all config files? I'm just guessing here... >> >> >> >> Zitat von Paras pradhan : >> >> No I still have that error. Other than that I don't see any other >>> errors. >>> >>> On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block wrote: >>> >>> So I guess the mentioned error should be resolved? Does it work now? Zitat von Paras pradhan : Yes I I have it set up in nova.conf and neutron.conf > > On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block > wrote: > > And did you change it to auth_type instead of auth_plugin? Also > you should > >> make sure that this option is in the correct section of your >> config file, >> for example >> >> [keystone_authtoken] >> ... >> auth_type = password >> >> or >> >> [neutron] >> ... >> auth_type = password >> >> >> Regards, >> Eugen >> >> >> Zitat von Paras pradhan : >> >> Hi Eugen, >> >> >>> Thanks. Log says its an error. Here is the full log. >>> http://pastebin.com/K1f4pJhB >>> >>> -Paras. >>> >>> On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block >>> wrote: >>> >>> Hi Paras, >>> >>> the option auth_plugin is deprecated (from nova.conf): ---cut here--- # Authentication type to load (unknown value) # Deprecated group/name - [DEFAULT]/auth_plugin auth_type = password ---cut here--- But as far as I can tell, you should only get a warning, not an error, I've seen some of these warnings in my logs, but it works (I work with openSUSE). To get Mitaka working at all I simply tried to set the same options as in my working Liberty configs, and then I searched for deprecation warnings and additional options mentioned in the Mitaka guide. Hope this helps! Regards, Eugen Zitat von Paras pradhan : Can somebody share the nova.conf and neutron.conf from working mitaka? I am also following the same guide and ran into a problem. > > 2016-04-18 16:51:07.982 2447 ERROR > nova.api.openstack.extensions > NoSuchOptError: no such option in group neutron: auth_plugin > > Not sure what did I do wrong. It was while launching an > instance. > > > Thanks > > Paras. > > On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood < >>
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
Thanks Martinx On Thu, Apr 21, 2016 at 2:50 PM, Martinx - ジェームズ wrote: > I just manage to make OpenStack Mitaka to work with both Linux Bridges, > and OpenvSwitch... > > Everything is work on both "All in One" and multi-node environments. > > Very soon, I'll post instructions about how to use the Ansible automation > that I am developing to play with this... > > Then, you guys will be able to deploy it, on a spare box (or VMs), and > then, compare with failing deployemnts... > > Cheers! > > On 21 April 2016 at 16:44, Paras pradhan wrote: > >> The neutron section was missing from nova.conf and now the instances work >> but having issues with metadata server. instances boot but no network >> access. >> Thanks >> Paras. >> >> On Thu, Apr 21, 2016 at 9:58 AM, Martinx - ジェームズ < >> thiagocmarti...@gmail.com> wrote: >> >>> My nova.conf is this one: >>> >>> >>> https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_cmpt/templates/mitaka/nova.conf >>> >>> However, I'm facing connectivity problems when with OpenvSwitch >>> deployments, investigating it now... >>> >>> On 21 April 2016 at 11:04, Paras pradhan wrote: >>> Yes . I did. here is my nova.conf. Can you share yours? http://paste.openstack.org/show/494988/ On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block wrote: > Okay, did you restart the respective services on all nodes after the > changes in your config files? If the same error still occurs then you > might > haven't found all occurrences of the option auth_plugin, did you replace > it > in all config files? I'm just guessing here... > > > > Zitat von Paras pradhan : > > No I still have that error. Other than that I don't see any other >> errors. >> >> On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block wrote: >> >> So I guess the mentioned error should be resolved? Does it work now? >>> >>> >>> >>> Zitat von Paras pradhan : >>> >>> Yes I I have it set up in nova.conf and neutron.conf >>> On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block wrote: And did you change it to auth_type instead of auth_plugin? Also you should > make sure that this option is in the correct section of your > config file, > for example > > [keystone_authtoken] > ... > auth_type = password > > or > > [neutron] > ... > auth_type = password > > > Regards, > Eugen > > > Zitat von Paras pradhan : > > Hi Eugen, > > >> Thanks. Log says its an error. Here is the full log. >> http://pastebin.com/K1f4pJhB >> >> -Paras. >> >> On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block >> wrote: >> >> Hi Paras, >> >> >>> the option auth_plugin is deprecated (from nova.conf): >>> >>> ---cut here--- >>> # Authentication type to load (unknown value) >>> # Deprecated group/name - [DEFAULT]/auth_plugin >>> auth_type = password >>> ---cut here--- >>> >>> But as far as I can tell, you should only get a warning, not an >>> error, >>> I've seen some of these warnings in my logs, but it works (I >>> work with >>> openSUSE). To get Mitaka working at all I simply tried to set >>> the same >>> options as in my working Liberty configs, and then I searched for >>> deprecation warnings and additional options mentioned in the >>> Mitaka >>> guide. >>> >>> Hope this helps! >>> >>> Regards, >>> Eugen >>> >>> >>> Zitat von Paras pradhan : >>> >>> >>> Can somebody share the nova.conf and neutron.conf from working >>> mitaka? >>> I >>> am >>> >>> also following the same guide and ran into a problem. >>> 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions NoSuchOptError: no such option in group neutron: auth_plugin Not sure what did I do wrong. It was while launching an instance. Thanks Paras. On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood < nasir.mahm...@gmail.com > wrote: Martinx, glad to see that you are able to dig into the typo issue. I > remember, I > had to completely re-re-clean install my virtual setup of > OpenStack > for a > POC back in 2015 , just because I have had miss-configured my > neutron.
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
The neutron section was missing from nova.conf and now the instances work but having issues with metadata server. instances boot but no network access. Thanks Paras. On Thu, Apr 21, 2016 at 9:58 AM, Martinx - ジェームズ wrote: > My nova.conf is this one: > > > https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_cmpt/templates/mitaka/nova.conf > > However, I'm facing connectivity problems when with OpenvSwitch > deployments, investigating it now... > > On 21 April 2016 at 11:04, Paras pradhan wrote: > >> Yes . I did. here is my nova.conf. Can you share yours? >> http://paste.openstack.org/show/494988/ >> >> On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block wrote: >> >>> Okay, did you restart the respective services on all nodes after the >>> changes in your config files? If the same error still occurs then you might >>> haven't found all occurrences of the option auth_plugin, did you replace it >>> in all config files? I'm just guessing here... >>> >>> >>> >>> Zitat von Paras pradhan : >>> >>> No I still have that error. Other than that I don't see any other errors. On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block wrote: So I guess the mentioned error should be resolved? Does it work now? > > > > Zitat von Paras pradhan : > > Yes I I have it set up in nova.conf and neutron.conf > >> >> On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block wrote: >> >> And did you change it to auth_type instead of auth_plugin? Also you >> should >> >>> make sure that this option is in the correct section of your config >>> file, >>> for example >>> >>> [keystone_authtoken] >>> ... >>> auth_type = password >>> >>> or >>> >>> [neutron] >>> ... >>> auth_type = password >>> >>> >>> Regards, >>> Eugen >>> >>> >>> Zitat von Paras pradhan : >>> >>> Hi Eugen, >>> >>> Thanks. Log says its an error. Here is the full log. http://pastebin.com/K1f4pJhB -Paras. On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block wrote: Hi Paras, > the option auth_plugin is deprecated (from nova.conf): > > ---cut here--- > # Authentication type to load (unknown value) > # Deprecated group/name - [DEFAULT]/auth_plugin > auth_type = password > ---cut here--- > > But as far as I can tell, you should only get a warning, not an > error, > I've seen some of these warnings in my logs, but it works (I work > with > openSUSE). To get Mitaka working at all I simply tried to set the > same > options as in my working Liberty configs, and then I searched for > deprecation warnings and additional options mentioned in the Mitaka > guide. > > Hope this helps! > > Regards, > Eugen > > > Zitat von Paras pradhan : > > > Can somebody share the nova.conf and neutron.conf from working > mitaka? > I > am > > also following the same guide and ran into a problem. > >> >> 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions >> NoSuchOptError: no such option in group neutron: auth_plugin >> >> Not sure what did I do wrong. It was while launching an instance. >> >> >> Thanks >> >> Paras. >> >> On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood < >> nasir.mahm...@gmail.com >> > >> wrote: >> >> Martinx, >> >> >> glad to see that you are able to dig into the typo issue. I >>> remember, I >>> had to completely re-re-clean install my virtual setup of >>> OpenStack >>> for a >>> POC back in 2015 , just because I have had miss-configured my >>> neutron.conf's mysql DB connector information. >>> >>> Cheers! >>> >>> >>> Regards, >>> Nasir Mahmood >>> >>> On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ < >>> thiagocmarti...@gmail.com> wrote: >>> >>> FIXED!! I knew it was a typo somewhere! LOL >>> >>> >>> https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 Thank you guys! Sorry about the buzz on TWO mail lists... At least, now we know that Nova silent fail on its start up, if somethings aren't configured according... And there is no verification steps to test the communication between Nova and Neutron. Mitaka is working no
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
I just manage to make OpenStack Mitaka to work with both Linux Bridges, and OpenvSwitch... Everything is work on both "All in One" and multi-node environments. Very soon, I'll post instructions about how to use the Ansible automation that I am developing to play with this... Then, you guys will be able to deploy it, on a spare box (or VMs), and then, compare with failing deployemnts... Cheers! On 21 April 2016 at 16:44, Paras pradhan wrote: > The neutron section was missing from nova.conf and now the instances work > but having issues with metadata server. instances boot but no network > access. > Thanks > Paras. > > On Thu, Apr 21, 2016 at 9:58 AM, Martinx - ジェームズ < > thiagocmarti...@gmail.com> wrote: > >> My nova.conf is this one: >> >> >> https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_cmpt/templates/mitaka/nova.conf >> >> However, I'm facing connectivity problems when with OpenvSwitch >> deployments, investigating it now... >> >> On 21 April 2016 at 11:04, Paras pradhan wrote: >> >>> Yes . I did. here is my nova.conf. Can you share yours? >>> http://paste.openstack.org/show/494988/ >>> >>> On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block wrote: >>> Okay, did you restart the respective services on all nodes after the changes in your config files? If the same error still occurs then you might haven't found all occurrences of the option auth_plugin, did you replace it in all config files? I'm just guessing here... Zitat von Paras pradhan : No I still have that error. Other than that I don't see any other > errors. > > On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block wrote: > > So I guess the mentioned error should be resolved? Does it work now? >> >> >> >> Zitat von Paras pradhan : >> >> Yes I I have it set up in nova.conf and neutron.conf >> >>> >>> On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block wrote: >>> >>> And did you change it to auth_type instead of auth_plugin? Also you >>> should >>> make sure that this option is in the correct section of your config file, for example [keystone_authtoken] ... auth_type = password or [neutron] ... auth_type = password Regards, Eugen Zitat von Paras pradhan : Hi Eugen, > Thanks. Log says its an error. Here is the full log. > http://pastebin.com/K1f4pJhB > > -Paras. > > On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block > wrote: > > Hi Paras, > > >> the option auth_plugin is deprecated (from nova.conf): >> >> ---cut here--- >> # Authentication type to load (unknown value) >> # Deprecated group/name - [DEFAULT]/auth_plugin >> auth_type = password >> ---cut here--- >> >> But as far as I can tell, you should only get a warning, not an >> error, >> I've seen some of these warnings in my logs, but it works (I work >> with >> openSUSE). To get Mitaka working at all I simply tried to set the >> same >> options as in my working Liberty configs, and then I searched for >> deprecation warnings and additional options mentioned in the >> Mitaka >> guide. >> >> Hope this helps! >> >> Regards, >> Eugen >> >> >> Zitat von Paras pradhan : >> >> >> Can somebody share the nova.conf and neutron.conf from working >> mitaka? >> I >> am >> >> also following the same guide and ran into a problem. >> >>> >>> 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions >>> NoSuchOptError: no such option in group neutron: auth_plugin >>> >>> Not sure what did I do wrong. It was while launching an instance. >>> >>> >>> Thanks >>> >>> Paras. >>> >>> On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood < >>> nasir.mahm...@gmail.com >>> > >>> wrote: >>> >>> Martinx, >>> >>> >>> glad to see that you are able to dig into the typo issue. I remember, I had to completely re-re-clean install my virtual setup of OpenStack for a POC back in 2015 , just because I have had miss-configured my neutron.conf's mysql DB connector information. Cheers! Regards, Nasir Mahmood On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ < thiagocmarti...@gmail.com> wrote: >
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
My nova.conf is this one: https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_cmpt/templates/mitaka/nova.conf However, I'm facing connectivity problems when with OpenvSwitch deployments, investigating it now... On 21 April 2016 at 11:04, Paras pradhan wrote: > Yes . I did. here is my nova.conf. Can you share yours? > http://paste.openstack.org/show/494988/ > > On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block wrote: > >> Okay, did you restart the respective services on all nodes after the >> changes in your config files? If the same error still occurs then you might >> haven't found all occurrences of the option auth_plugin, did you replace it >> in all config files? I'm just guessing here... >> >> >> >> Zitat von Paras pradhan : >> >> No I still have that error. Other than that I don't see any other errors. >>> >>> On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block wrote: >>> >>> So I guess the mentioned error should be resolved? Does it work now? Zitat von Paras pradhan : Yes I I have it set up in nova.conf and neutron.conf > > On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block wrote: > > And did you change it to auth_type instead of auth_plugin? Also you > should > >> make sure that this option is in the correct section of your config >> file, >> for example >> >> [keystone_authtoken] >> ... >> auth_type = password >> >> or >> >> [neutron] >> ... >> auth_type = password >> >> >> Regards, >> Eugen >> >> >> Zitat von Paras pradhan : >> >> Hi Eugen, >> >> >>> Thanks. Log says its an error. Here is the full log. >>> http://pastebin.com/K1f4pJhB >>> >>> -Paras. >>> >>> On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block wrote: >>> >>> Hi Paras, >>> >>> the option auth_plugin is deprecated (from nova.conf): ---cut here--- # Authentication type to load (unknown value) # Deprecated group/name - [DEFAULT]/auth_plugin auth_type = password ---cut here--- But as far as I can tell, you should only get a warning, not an error, I've seen some of these warnings in my logs, but it works (I work with openSUSE). To get Mitaka working at all I simply tried to set the same options as in my working Liberty configs, and then I searched for deprecation warnings and additional options mentioned in the Mitaka guide. Hope this helps! Regards, Eugen Zitat von Paras pradhan : Can somebody share the nova.conf and neutron.conf from working mitaka? I am also following the same guide and ran into a problem. > > 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions > NoSuchOptError: no such option in group neutron: auth_plugin > > Not sure what did I do wrong. It was while launching an instance. > > > Thanks > > Paras. > > On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood < > nasir.mahm...@gmail.com > > > wrote: > > Martinx, > > > glad to see that you are able to dig into the typo issue. I >> remember, I >> had to completely re-re-clean install my virtual setup of >> OpenStack >> for a >> POC back in 2015 , just because I have had miss-configured my >> neutron.conf's mysql DB connector information. >> >> Cheers! >> >> >> Regards, >> Nasir Mahmood >> >> On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ < >> thiagocmarti...@gmail.com> wrote: >> >> FIXED!! I knew it was a typo somewhere! LOL >> >> >> >>> >>> >>> >>> >>> https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 >>> >>> Thank you guys! >>> >>> Sorry about the buzz on TWO mail lists... >>> >>> At least, now we know that Nova silent fail on its start up, if >>> somethings aren't configured according... And there is no >>> verification >>> steps to test the communication between Nova and Neutron. >>> >>> Mitaka is working now on Xenial! YAY!! >>> >>> I'm about to commit changes to enable OpenvSwitch with DPDK and >>> multi-node deployments, fully automated! >>> >>> Cheers! >>> Thiago >>> >>> On 17 April 2016 at 21:26, Martinx - ジェームズ < >>> thiagocmarti...@gmail.com >>> > >>> wrote: >>> >>> On 17 April 2016 at 17
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
Yes . I did. here is my nova.conf. Can you share yours? http://paste.openstack.org/show/494988/ On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block wrote: > Okay, did you restart the respective services on all nodes after the > changes in your config files? If the same error still occurs then you might > haven't found all occurrences of the option auth_plugin, did you replace it > in all config files? I'm just guessing here... > > > > Zitat von Paras pradhan : > > No I still have that error. Other than that I don't see any other errors. >> >> On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block wrote: >> >> So I guess the mentioned error should be resolved? Does it work now? >>> >>> >>> >>> Zitat von Paras pradhan : >>> >>> Yes I I have it set up in nova.conf and neutron.conf >>> On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block wrote: And did you change it to auth_type instead of auth_plugin? Also you should > make sure that this option is in the correct section of your config > file, > for example > > [keystone_authtoken] > ... > auth_type = password > > or > > [neutron] > ... > auth_type = password > > > Regards, > Eugen > > > Zitat von Paras pradhan : > > Hi Eugen, > > >> Thanks. Log says its an error. Here is the full log. >> http://pastebin.com/K1f4pJhB >> >> -Paras. >> >> On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block wrote: >> >> Hi Paras, >> >> >>> the option auth_plugin is deprecated (from nova.conf): >>> >>> ---cut here--- >>> # Authentication type to load (unknown value) >>> # Deprecated group/name - [DEFAULT]/auth_plugin >>> auth_type = password >>> ---cut here--- >>> >>> But as far as I can tell, you should only get a warning, not an >>> error, >>> I've seen some of these warnings in my logs, but it works (I work >>> with >>> openSUSE). To get Mitaka working at all I simply tried to set the >>> same >>> options as in my working Liberty configs, and then I searched for >>> deprecation warnings and additional options mentioned in the Mitaka >>> guide. >>> >>> Hope this helps! >>> >>> Regards, >>> Eugen >>> >>> >>> Zitat von Paras pradhan : >>> >>> >>> Can somebody share the nova.conf and neutron.conf from working >>> mitaka? >>> I >>> am >>> >>> also following the same guide and ran into a problem. >>> 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions NoSuchOptError: no such option in group neutron: auth_plugin Not sure what did I do wrong. It was while launching an instance. Thanks Paras. On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood < nasir.mahm...@gmail.com > wrote: Martinx, glad to see that you are able to dig into the typo issue. I > remember, I > had to completely re-re-clean install my virtual setup of OpenStack > for a > POC back in 2015 , just because I have had miss-configured my > neutron.conf's mysql DB connector information. > > Cheers! > > > Regards, > Nasir Mahmood > > On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ < > thiagocmarti...@gmail.com> wrote: > > FIXED!! I knew it was a typo somewhere! LOL > > > >> >> >> >> >> https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 >> >> Thank you guys! >> >> Sorry about the buzz on TWO mail lists... >> >> At least, now we know that Nova silent fail on its start up, if >> somethings aren't configured according... And there is no >> verification >> steps to test the communication between Nova and Neutron. >> >> Mitaka is working now on Xenial! YAY!! >> >> I'm about to commit changes to enable OpenvSwitch with DPDK and >> multi-node deployments, fully automated! >> >> Cheers! >> Thiago >> >> On 17 April 2016 at 21:26, Martinx - ジェームズ < >> thiagocmarti...@gmail.com >> > >> wrote: >> >> On 17 April 2016 at 17:39, Martinx - ジェームズ < >> thiagocmarti...@gmail.com >> > >> >> wrote: >> >>> >>> Guys, >>> >>> >>> I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the following document: http://docs.openstack.org/mitaka/install-guide-ubuntu Yes, I know, the above document is for installing Mitaka on
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
Okay, did you restart the respective services on all nodes after the changes in your config files? If the same error still occurs then you might haven't found all occurrences of the option auth_plugin, did you replace it in all config files? I'm just guessing here... Zitat von Paras pradhan : No I still have that error. Other than that I don't see any other errors. On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block wrote: So I guess the mentioned error should be resolved? Does it work now? Zitat von Paras pradhan : Yes I I have it set up in nova.conf and neutron.conf On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block wrote: And did you change it to auth_type instead of auth_plugin? Also you should make sure that this option is in the correct section of your config file, for example [keystone_authtoken] ... auth_type = password or [neutron] ... auth_type = password Regards, Eugen Zitat von Paras pradhan : Hi Eugen, Thanks. Log says its an error. Here is the full log. http://pastebin.com/K1f4pJhB -Paras. On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block wrote: Hi Paras, the option auth_plugin is deprecated (from nova.conf): ---cut here--- # Authentication type to load (unknown value) # Deprecated group/name - [DEFAULT]/auth_plugin auth_type = password ---cut here--- But as far as I can tell, you should only get a warning, not an error, I've seen some of these warnings in my logs, but it works (I work with openSUSE). To get Mitaka working at all I simply tried to set the same options as in my working Liberty configs, and then I searched for deprecation warnings and additional options mentioned in the Mitaka guide. Hope this helps! Regards, Eugen Zitat von Paras pradhan : Can somebody share the nova.conf and neutron.conf from working mitaka? I am also following the same guide and ran into a problem. 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions NoSuchOptError: no such option in group neutron: auth_plugin Not sure what did I do wrong. It was while launching an instance. Thanks Paras. On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood < nasir.mahm...@gmail.com > wrote: Martinx, glad to see that you are able to dig into the typo issue. I remember, I had to completely re-re-clean install my virtual setup of OpenStack for a POC back in 2015 , just because I have had miss-configured my neutron.conf's mysql DB connector information. Cheers! Regards, Nasir Mahmood On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ < thiagocmarti...@gmail.com> wrote: FIXED!! I knew it was a typo somewhere! LOL https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 Thank you guys! Sorry about the buzz on TWO mail lists... At least, now we know that Nova silent fail on its start up, if somethings aren't configured according... And there is no verification steps to test the communication between Nova and Neutron. Mitaka is working now on Xenial! YAY!! I'm about to commit changes to enable OpenvSwitch with DPDK and multi-node deployments, fully automated! Cheers! Thiago On 17 April 2016 at 21:26, Martinx - ジェームズ < thiagocmarti...@gmail.com > wrote: On 17 April 2016 at 17:39, Martinx - ジェームズ < thiagocmarti...@gmail.com > wrote: Guys, I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the following document: http://docs.openstack.org/mitaka/install-guide-ubuntu Yes, I know, the above document is for installing Mitaka on top of Ubuntu 14.04 but, from what I understand, the only difference is that on Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, since Mitaka is the default on Xenial, so, I can follow that document, right? =) At first, OpenStack installation goes okay, without any errors, all services comes up, etc... However, it is not possible to launch an Instance. *** Errors on launching the Instance: - Right after launching it: https://paste.ubuntu.com/15902503/ - Spawning it, after Glance finishes the download, similar error a second time: https://paste.ubuntu.com/15902556/ What am I missing? Apparently, Nova is not authorized to talk with Neutron but, I am following the docs (maybe it is just a typo somewhere?)... Also, I have an Ansible automation to deploy it, so, it is less error prone. And however can help me, will see how I am deploying it. I see no error on Admin Dashboard, all services are up. NOTE: My Ansible playbooks is in a sense, " docs.openstack.org/mitaka/install-guide-ubuntu fully automated", it is very close to it, step-by-step. How can I debug this? I mean, how can I try to do, what Nova is doing (its connection with Neutron), to make sure that the settings are in place correctly? Here is how I am installing Mitaka on Xenial: --- 1- Install Ubuntu 16.04 server 64-bit on bare-metal; * Configure your /etc/hostname and /etc/hosts. DETAILS: https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md 2- Clone the automation: cd ~
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
So I guess the mentioned error should be resolved? Does it work now? Zitat von Paras pradhan : Yes I I have it set up in nova.conf and neutron.conf On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block wrote: And did you change it to auth_type instead of auth_plugin? Also you should make sure that this option is in the correct section of your config file, for example [keystone_authtoken] ... auth_type = password or [neutron] ... auth_type = password Regards, Eugen Zitat von Paras pradhan : Hi Eugen, Thanks. Log says its an error. Here is the full log. http://pastebin.com/K1f4pJhB -Paras. On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block wrote: Hi Paras, the option auth_plugin is deprecated (from nova.conf): ---cut here--- # Authentication type to load (unknown value) # Deprecated group/name - [DEFAULT]/auth_plugin auth_type = password ---cut here--- But as far as I can tell, you should only get a warning, not an error, I've seen some of these warnings in my logs, but it works (I work with openSUSE). To get Mitaka working at all I simply tried to set the same options as in my working Liberty configs, and then I searched for deprecation warnings and additional options mentioned in the Mitaka guide. Hope this helps! Regards, Eugen Zitat von Paras pradhan : Can somebody share the nova.conf and neutron.conf from working mitaka? I am also following the same guide and ran into a problem. 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions NoSuchOptError: no such option in group neutron: auth_plugin Not sure what did I do wrong. It was while launching an instance. Thanks Paras. On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood wrote: Martinx, glad to see that you are able to dig into the typo issue. I remember, I had to completely re-re-clean install my virtual setup of OpenStack for a POC back in 2015 , just because I have had miss-configured my neutron.conf's mysql DB connector information. Cheers! Regards, Nasir Mahmood On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ < thiagocmarti...@gmail.com> wrote: FIXED!! I knew it was a typo somewhere! LOL https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 Thank you guys! Sorry about the buzz on TWO mail lists... At least, now we know that Nova silent fail on its start up, if somethings aren't configured according... And there is no verification steps to test the communication between Nova and Neutron. Mitaka is working now on Xenial! YAY!! I'm about to commit changes to enable OpenvSwitch with DPDK and multi-node deployments, fully automated! Cheers! Thiago On 17 April 2016 at 21:26, Martinx - ジェームズ wrote: On 17 April 2016 at 17:39, Martinx - ジェームズ wrote: Guys, I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the following document: http://docs.openstack.org/mitaka/install-guide-ubuntu Yes, I know, the above document is for installing Mitaka on top of Ubuntu 14.04 but, from what I understand, the only difference is that on Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, since Mitaka is the default on Xenial, so, I can follow that document, right? =) At first, OpenStack installation goes okay, without any errors, all services comes up, etc... However, it is not possible to launch an Instance. *** Errors on launching the Instance: - Right after launching it: https://paste.ubuntu.com/15902503/ - Spawning it, after Glance finishes the download, similar error a second time: https://paste.ubuntu.com/15902556/ What am I missing? Apparently, Nova is not authorized to talk with Neutron but, I am following the docs (maybe it is just a typo somewhere?)... Also, I have an Ansible automation to deploy it, so, it is less error prone. And however can help me, will see how I am deploying it. I see no error on Admin Dashboard, all services are up. NOTE: My Ansible playbooks is in a sense, " docs.openstack.org/mitaka/install-guide-ubuntu fully automated", it is very close to it, step-by-step. How can I debug this? I mean, how can I try to do, what Nova is doing (its connection with Neutron), to make sure that the settings are in place correctly? Here is how I am installing Mitaka on Xenial: --- 1- Install Ubuntu 16.04 server 64-bit on bare-metal; * Configure your /etc/hostname and /etc/hosts. DETAILS: https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md 2- Clone the automation: cd ~ git clone https://github.com/tmartinx/svauto.git 3- Run the automation to install OpenStack (all-in-one) cd ~/svauto ./os-deploy.sh --br-mode=LBR --use-dummies --base-os=ubuntu16 --base-os-upgrade=yes --openstack-release=mitaka --openstack-installation --dry-run ansible-playbook -c local site-openstack.yml --extra-vars "openstack_installation=yes" --- NOTE: If you don't use "--dry-run" option, Ansible will be executed automatically by "os-deploy.sh". I am sharing the Ansible playbooks, because
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
No I still have that error. Other than that I don't see any other errors. On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block wrote: > So I guess the mentioned error should be resolved? Does it work now? > > > > Zitat von Paras pradhan : > > Yes I I have it set up in nova.conf and neutron.conf >> >> On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block wrote: >> >> And did you change it to auth_type instead of auth_plugin? Also you should >>> make sure that this option is in the correct section of your config file, >>> for example >>> >>> [keystone_authtoken] >>> ... >>> auth_type = password >>> >>> or >>> >>> [neutron] >>> ... >>> auth_type = password >>> >>> >>> Regards, >>> Eugen >>> >>> >>> Zitat von Paras pradhan : >>> >>> Hi Eugen, >>> Thanks. Log says its an error. Here is the full log. http://pastebin.com/K1f4pJhB -Paras. On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block wrote: Hi Paras, > > the option auth_plugin is deprecated (from nova.conf): > > ---cut here--- > # Authentication type to load (unknown value) > # Deprecated group/name - [DEFAULT]/auth_plugin > auth_type = password > ---cut here--- > > But as far as I can tell, you should only get a warning, not an error, > I've seen some of these warnings in my logs, but it works (I work with > openSUSE). To get Mitaka working at all I simply tried to set the same > options as in my working Liberty configs, and then I searched for > deprecation warnings and additional options mentioned in the Mitaka > guide. > > Hope this helps! > > Regards, > Eugen > > > Zitat von Paras pradhan : > > > Can somebody share the nova.conf and neutron.conf from working mitaka? > I > am > > also following the same guide and ran into a problem. >> >> 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions >> NoSuchOptError: no such option in group neutron: auth_plugin >> >> Not sure what did I do wrong. It was while launching an instance. >> >> >> Thanks >> >> Paras. >> >> On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood < >> nasir.mahm...@gmail.com >> > >> wrote: >> >> Martinx, >> >> >>> glad to see that you are able to dig into the typo issue. I >>> remember, I >>> had to completely re-re-clean install my virtual setup of OpenStack >>> for a >>> POC back in 2015 , just because I have had miss-configured my >>> neutron.conf's mysql DB connector information. >>> >>> Cheers! >>> >>> >>> Regards, >>> Nasir Mahmood >>> >>> On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ < >>> thiagocmarti...@gmail.com> wrote: >>> >>> FIXED!! I knew it was a typo somewhere! LOL >>> >>> https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 Thank you guys! Sorry about the buzz on TWO mail lists... At least, now we know that Nova silent fail on its start up, if somethings aren't configured according... And there is no verification steps to test the communication between Nova and Neutron. Mitaka is working now on Xenial! YAY!! I'm about to commit changes to enable OpenvSwitch with DPDK and multi-node deployments, fully automated! Cheers! Thiago On 17 April 2016 at 21:26, Martinx - ジェームズ < thiagocmarti...@gmail.com > wrote: On 17 April 2016 at 17:39, Martinx - ジェームズ < thiagocmarti...@gmail.com > wrote: > > Guys, > > >> I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using >> the >> following document: >> >> http://docs.openstack.org/mitaka/install-guide-ubuntu >> >> Yes, I know, the above document is for installing Mitaka on top >> of >> Ubuntu 14.04 but, from what I understand, the only difference is >> that >> on >> Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, >> since >> Mitaka is the default on Xenial, so, I can follow that document, >> right? >> =) >> >> At first, OpenStack installation goes okay, without any errors, >> all >> services comes up, etc... However, it is not possible to launch an >> Instance. >> >> *** Errors on launching the Instance: >> >> - Right after launching it: >> >> https://paste.ubuntu.com/15902503/ >> >> - Spawning it, after Glance finishes the download, similar error >> a >> second time: >> >> https://past
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
And did you change it to auth_type instead of auth_plugin? Also you should make sure that this option is in the correct section of your config file, for example [keystone_authtoken] ... auth_type = password or [neutron] ... auth_type = password Regards, Eugen Zitat von Paras pradhan : Hi Eugen, Thanks. Log says its an error. Here is the full log. http://pastebin.com/K1f4pJhB -Paras. On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block wrote: Hi Paras, the option auth_plugin is deprecated (from nova.conf): ---cut here--- # Authentication type to load (unknown value) # Deprecated group/name - [DEFAULT]/auth_plugin auth_type = password ---cut here--- But as far as I can tell, you should only get a warning, not an error, I've seen some of these warnings in my logs, but it works (I work with openSUSE). To get Mitaka working at all I simply tried to set the same options as in my working Liberty configs, and then I searched for deprecation warnings and additional options mentioned in the Mitaka guide. Hope this helps! Regards, Eugen Zitat von Paras pradhan : Can somebody share the nova.conf and neutron.conf from working mitaka? I am also following the same guide and ran into a problem. 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions NoSuchOptError: no such option in group neutron: auth_plugin Not sure what did I do wrong. It was while launching an instance. Thanks Paras. On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood wrote: Martinx, glad to see that you are able to dig into the typo issue. I remember, I had to completely re-re-clean install my virtual setup of OpenStack for a POC back in 2015 , just because I have had miss-configured my neutron.conf's mysql DB connector information. Cheers! Regards, Nasir Mahmood On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ < thiagocmarti...@gmail.com> wrote: FIXED!! I knew it was a typo somewhere! LOL https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 Thank you guys! Sorry about the buzz on TWO mail lists... At least, now we know that Nova silent fail on its start up, if somethings aren't configured according... And there is no verification steps to test the communication between Nova and Neutron. Mitaka is working now on Xenial! YAY!! I'm about to commit changes to enable OpenvSwitch with DPDK and multi-node deployments, fully automated! Cheers! Thiago On 17 April 2016 at 21:26, Martinx - ジェームズ wrote: On 17 April 2016 at 17:39, Martinx - ジェームズ wrote: Guys, I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the following document: http://docs.openstack.org/mitaka/install-guide-ubuntu Yes, I know, the above document is for installing Mitaka on top of Ubuntu 14.04 but, from what I understand, the only difference is that on Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, since Mitaka is the default on Xenial, so, I can follow that document, right? =) At first, OpenStack installation goes okay, without any errors, all services comes up, etc... However, it is not possible to launch an Instance. *** Errors on launching the Instance: - Right after launching it: https://paste.ubuntu.com/15902503/ - Spawning it, after Glance finishes the download, similar error a second time: https://paste.ubuntu.com/15902556/ What am I missing? Apparently, Nova is not authorized to talk with Neutron but, I am following the docs (maybe it is just a typo somewhere?)... Also, I have an Ansible automation to deploy it, so, it is less error prone. And however can help me, will see how I am deploying it. I see no error on Admin Dashboard, all services are up. NOTE: My Ansible playbooks is in a sense, " docs.openstack.org/mitaka/install-guide-ubuntu fully automated", it is very close to it, step-by-step. How can I debug this? I mean, how can I try to do, what Nova is doing (its connection with Neutron), to make sure that the settings are in place correctly? Here is how I am installing Mitaka on Xenial: --- 1- Install Ubuntu 16.04 server 64-bit on bare-metal; * Configure your /etc/hostname and /etc/hosts. DETAILS: https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md 2- Clone the automation: cd ~ git clone https://github.com/tmartinx/svauto.git 3- Run the automation to install OpenStack (all-in-one) cd ~/svauto ./os-deploy.sh --br-mode=LBR --use-dummies --base-os=ubuntu16 --base-os-upgrade=yes --openstack-release=mitaka --openstack-installation --dry-run ansible-playbook -c local site-openstack.yml --extra-vars "openstack_installation=yes" --- NOTE: If you don't use "--dry-run" option, Ansible will be executed automatically by "os-deploy.sh". I am sharing the Ansible playbooks, because it will be easier to see what I am doing. About the relevant configuration blocks, I believe that I have it properly configured (I followed Mitaka docs), like this: * neutron.conf: - https://github.com/tm
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
Yes I I have it set up in nova.conf and neutron.conf On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block wrote: > And did you change it to auth_type instead of auth_plugin? Also you should > make sure that this option is in the correct section of your config file, > for example > > [keystone_authtoken] > ... > auth_type = password > > or > > [neutron] > ... > auth_type = password > > > Regards, > Eugen > > > Zitat von Paras pradhan : > > Hi Eugen, >> >> Thanks. Log says its an error. Here is the full log. >> http://pastebin.com/K1f4pJhB >> >> -Paras. >> >> On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block wrote: >> >> Hi Paras, >>> >>> the option auth_plugin is deprecated (from nova.conf): >>> >>> ---cut here--- >>> # Authentication type to load (unknown value) >>> # Deprecated group/name - [DEFAULT]/auth_plugin >>> auth_type = password >>> ---cut here--- >>> >>> But as far as I can tell, you should only get a warning, not an error, >>> I've seen some of these warnings in my logs, but it works (I work with >>> openSUSE). To get Mitaka working at all I simply tried to set the same >>> options as in my working Liberty configs, and then I searched for >>> deprecation warnings and additional options mentioned in the Mitaka >>> guide. >>> >>> Hope this helps! >>> >>> Regards, >>> Eugen >>> >>> >>> Zitat von Paras pradhan : >>> >>> >>> Can somebody share the nova.conf and neutron.conf from working mitaka? I >>> am >>> also following the same guide and ran into a problem. 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions NoSuchOptError: no such option in group neutron: auth_plugin Not sure what did I do wrong. It was while launching an instance. Thanks Paras. On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood >>> > wrote: Martinx, > > glad to see that you are able to dig into the typo issue. I remember, I > had to completely re-re-clean install my virtual setup of OpenStack > for a > POC back in 2015 , just because I have had miss-configured my > neutron.conf's mysql DB connector information. > > Cheers! > > > Regards, > Nasir Mahmood > > On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ < > thiagocmarti...@gmail.com> wrote: > > FIXED!! I knew it was a typo somewhere! LOL > >> >> >> >> >> https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 >> >> Thank you guys! >> >> Sorry about the buzz on TWO mail lists... >> >> At least, now we know that Nova silent fail on its start up, if >> somethings aren't configured according... And there is no verification >> steps to test the communication between Nova and Neutron. >> >> Mitaka is working now on Xenial! YAY!! >> >> I'm about to commit changes to enable OpenvSwitch with DPDK and >> multi-node deployments, fully automated! >> >> Cheers! >> Thiago >> >> On 17 April 2016 at 21:26, Martinx - ジェームズ > > >> wrote: >> >> On 17 April 2016 at 17:39, Martinx - ジェームズ > > >> >>> wrote: >>> >>> Guys, >>> I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the following document: http://docs.openstack.org/mitaka/install-guide-ubuntu Yes, I know, the above document is for installing Mitaka on top of Ubuntu 14.04 but, from what I understand, the only difference is that on Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, since Mitaka is the default on Xenial, so, I can follow that document, right? =) At first, OpenStack installation goes okay, without any errors, all services comes up, etc... However, it is not possible to launch an Instance. *** Errors on launching the Instance: - Right after launching it: https://paste.ubuntu.com/15902503/ - Spawning it, after Glance finishes the download, similar error a second time: https://paste.ubuntu.com/15902556/ What am I missing? Apparently, Nova is not authorized to talk with Neutron but, I am following the docs (maybe it is just a typo somewhere?)... Also, I have an Ansible automation to deploy it, so, it is less error prone. And however can help me, will see how I am deploying it. I see no error on Admin Dashboard, all services are up. NOTE: My Ansible playbooks is in a sense, " docs.openstack.org/mitaka/install-guide-ubuntu fully automated", it is very close to it, step-by-step. How can I debug this? I mean, how can I try to do, what Nova is doing
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
Hi Eugen, Thanks. Log says its an error. Here is the full log. http://pastebin.com/K1f4pJhB -Paras. On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block wrote: > Hi Paras, > > the option auth_plugin is deprecated (from nova.conf): > > ---cut here--- > # Authentication type to load (unknown value) > # Deprecated group/name - [DEFAULT]/auth_plugin > auth_type = password > ---cut here--- > > But as far as I can tell, you should only get a warning, not an error, > I've seen some of these warnings in my logs, but it works (I work with > openSUSE). To get Mitaka working at all I simply tried to set the same > options as in my working Liberty configs, and then I searched for > deprecation warnings and additional options mentioned in the Mitaka guide. > > Hope this helps! > > Regards, > Eugen > > > Zitat von Paras pradhan : > > > Can somebody share the nova.conf and neutron.conf from working mitaka? I am >> also following the same guide and ran into a problem. >> >> 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions >> NoSuchOptError: no such option in group neutron: auth_plugin >> >> Not sure what did I do wrong. It was while launching an instance. >> >> >> Thanks >> >> Paras. >> >> On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood >> wrote: >> >> Martinx, >>> >>> glad to see that you are able to dig into the typo issue. I remember, I >>> had to completely re-re-clean install my virtual setup of OpenStack for a >>> POC back in 2015 , just because I have had miss-configured my >>> neutron.conf's mysql DB connector information. >>> >>> Cheers! >>> >>> >>> Regards, >>> Nasir Mahmood >>> >>> On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ < >>> thiagocmarti...@gmail.com> wrote: >>> >>> FIXED!! I knew it was a typo somewhere! LOL https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 Thank you guys! Sorry about the buzz on TWO mail lists... At least, now we know that Nova silent fail on its start up, if somethings aren't configured according... And there is no verification steps to test the communication between Nova and Neutron. Mitaka is working now on Xenial! YAY!! I'm about to commit changes to enable OpenvSwitch with DPDK and multi-node deployments, fully automated! Cheers! Thiago On 17 April 2016 at 21:26, Martinx - ジェームズ wrote: On 17 April 2016 at 17:39, Martinx - ジェームズ > wrote: > > Guys, >> >> I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the >> following document: >> >> http://docs.openstack.org/mitaka/install-guide-ubuntu >> >> Yes, I know, the above document is for installing Mitaka on top of >> Ubuntu 14.04 but, from what I understand, the only difference is that >> on >> Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, since >> Mitaka is the default on Xenial, so, I can follow that document, >> right? >> =) >> >> At first, OpenStack installation goes okay, without any errors, all >> services comes up, etc... However, it is not possible to launch an >> Instance. >> >> *** Errors on launching the Instance: >> >> - Right after launching it: >> >> https://paste.ubuntu.com/15902503/ >> >> - Spawning it, after Glance finishes the download, similar error a >> second time: >> >> https://paste.ubuntu.com/15902556/ >> >> What am I missing? >> >> Apparently, Nova is not authorized to talk with Neutron but, I am >> following the docs (maybe it is just a typo somewhere?)... >> >> Also, I have an Ansible automation to deploy it, so, it is less error >> prone. And however can help me, will see how I am deploying it. >> >> I see no error on Admin Dashboard, all services are up. >> >> NOTE: My Ansible playbooks is in a sense, " >> docs.openstack.org/mitaka/install-guide-ubuntu fully automated", it >> is >> very close to it, step-by-step. >> >> How can I debug this? I mean, how can I try to do, what Nova is doing >> (its connection with Neutron), to make sure that the settings are in >> place >> correctly? >> >> Here is how I am installing Mitaka on Xenial: >> >> --- >> 1- Install Ubuntu 16.04 server 64-bit on bare-metal; >> >>* Configure your /etc/hostname and /etc/hosts. >> >>DETAILS: >> https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md >> >> >> 2- Clone the automation: >> >> cd ~ >> git clone https://github.com/tmartinx/svauto.git >> >> >> 3- Run the automation to install OpenStack (all-in-one) >> >> cd ~/svauto >> >>./os-deploy.sh --br-mode=LBR --use-dummies --base-os=ubuntu16 >> --base-os-upgrade=yes --openstack-release=mitaka >> --openstack-installation >> --dr
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
Hi Paras, the option auth_plugin is deprecated (from nova.conf): ---cut here--- # Authentication type to load (unknown value) # Deprecated group/name - [DEFAULT]/auth_plugin auth_type = password ---cut here--- But as far as I can tell, you should only get a warning, not an error, I've seen some of these warnings in my logs, but it works (I work with openSUSE). To get Mitaka working at all I simply tried to set the same options as in my working Liberty configs, and then I searched for deprecation warnings and additional options mentioned in the Mitaka guide. Hope this helps! Regards, Eugen Zitat von Paras pradhan : Can somebody share the nova.conf and neutron.conf from working mitaka? I am also following the same guide and ran into a problem. 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions NoSuchOptError: no such option in group neutron: auth_plugin Not sure what did I do wrong. It was while launching an instance. Thanks Paras. On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood wrote: Martinx, glad to see that you are able to dig into the typo issue. I remember, I had to completely re-re-clean install my virtual setup of OpenStack for a POC back in 2015 , just because I have had miss-configured my neutron.conf's mysql DB connector information. Cheers! Regards, Nasir Mahmood On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ < thiagocmarti...@gmail.com> wrote: FIXED!! I knew it was a typo somewhere! LOL https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 Thank you guys! Sorry about the buzz on TWO mail lists... At least, now we know that Nova silent fail on its start up, if somethings aren't configured according... And there is no verification steps to test the communication between Nova and Neutron. Mitaka is working now on Xenial! YAY!! I'm about to commit changes to enable OpenvSwitch with DPDK and multi-node deployments, fully automated! Cheers! Thiago On 17 April 2016 at 21:26, Martinx - ジェームズ wrote: On 17 April 2016 at 17:39, Martinx - ジェームズ wrote: Guys, I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the following document: http://docs.openstack.org/mitaka/install-guide-ubuntu Yes, I know, the above document is for installing Mitaka on top of Ubuntu 14.04 but, from what I understand, the only difference is that on Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, since Mitaka is the default on Xenial, so, I can follow that document, right? =) At first, OpenStack installation goes okay, without any errors, all services comes up, etc... However, it is not possible to launch an Instance. *** Errors on launching the Instance: - Right after launching it: https://paste.ubuntu.com/15902503/ - Spawning it, after Glance finishes the download, similar error a second time: https://paste.ubuntu.com/15902556/ What am I missing? Apparently, Nova is not authorized to talk with Neutron but, I am following the docs (maybe it is just a typo somewhere?)... Also, I have an Ansible automation to deploy it, so, it is less error prone. And however can help me, will see how I am deploying it. I see no error on Admin Dashboard, all services are up. NOTE: My Ansible playbooks is in a sense, " docs.openstack.org/mitaka/install-guide-ubuntu fully automated", it is very close to it, step-by-step. How can I debug this? I mean, how can I try to do, what Nova is doing (its connection with Neutron), to make sure that the settings are in place correctly? Here is how I am installing Mitaka on Xenial: --- 1- Install Ubuntu 16.04 server 64-bit on bare-metal; * Configure your /etc/hostname and /etc/hosts. DETAILS: https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md 2- Clone the automation: cd ~ git clone https://github.com/tmartinx/svauto.git 3- Run the automation to install OpenStack (all-in-one) cd ~/svauto ./os-deploy.sh --br-mode=LBR --use-dummies --base-os=ubuntu16 --base-os-upgrade=yes --openstack-release=mitaka --openstack-installation --dry-run ansible-playbook -c local site-openstack.yml --extra-vars "openstack_installation=yes" --- NOTE: If you don't use "--dry-run" option, Ansible will be executed automatically by "os-deploy.sh". I am sharing the Ansible playbooks, because it will be easier to see what I am doing. About the relevant configuration blocks, I believe that I have it properly configured (I followed Mitaka docs), like this: * neutron.conf: - https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_neutron_aio/templates/mitaka/neutron.conf - * nova.conf: - https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_aio/templates/mitaka/nova.conf - I already installed OpenStack many, many, many times, since Havana release, I'm confident that I am doing it right but, of course, maybe I did something wrong this time... =P I appreciate any help! Thanks! Thiago Hey guys, I a
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
Can somebody share the nova.conf and neutron.conf from working mitaka? I am also following the same guide and ran into a problem. 2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions NoSuchOptError: no such option in group neutron: auth_plugin Not sure what did I do wrong. It was while launching an instance. Thanks Paras. On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood wrote: > Martinx, > > glad to see that you are able to dig into the typo issue. I remember, I > had to completely re-re-clean install my virtual setup of OpenStack for a > POC back in 2015 , just because I have had miss-configured my > neutron.conf's mysql DB connector information. > > Cheers! > > > Regards, > Nasir Mahmood > > On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ < > thiagocmarti...@gmail.com> wrote: > >> FIXED!! I knew it was a typo somewhere! LOL >> >> >> https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 >> >> Thank you guys! >> >> Sorry about the buzz on TWO mail lists... >> >> At least, now we know that Nova silent fail on its start up, if >> somethings aren't configured according... And there is no verification >> steps to test the communication between Nova and Neutron. >> >> Mitaka is working now on Xenial! YAY!! >> >> I'm about to commit changes to enable OpenvSwitch with DPDK and >> multi-node deployments, fully automated! >> >> Cheers! >> Thiago >> >> On 17 April 2016 at 21:26, Martinx - ジェームズ >> wrote: >> >>> On 17 April 2016 at 17:39, Martinx - ジェームズ >>> wrote: >>> Guys, I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the following document: http://docs.openstack.org/mitaka/install-guide-ubuntu Yes, I know, the above document is for installing Mitaka on top of Ubuntu 14.04 but, from what I understand, the only difference is that on Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, since Mitaka is the default on Xenial, so, I can follow that document, right? =) At first, OpenStack installation goes okay, without any errors, all services comes up, etc... However, it is not possible to launch an Instance. *** Errors on launching the Instance: - Right after launching it: https://paste.ubuntu.com/15902503/ - Spawning it, after Glance finishes the download, similar error a second time: https://paste.ubuntu.com/15902556/ What am I missing? Apparently, Nova is not authorized to talk with Neutron but, I am following the docs (maybe it is just a typo somewhere?)... Also, I have an Ansible automation to deploy it, so, it is less error prone. And however can help me, will see how I am deploying it. I see no error on Admin Dashboard, all services are up. NOTE: My Ansible playbooks is in a sense, " docs.openstack.org/mitaka/install-guide-ubuntu fully automated", it is very close to it, step-by-step. How can I debug this? I mean, how can I try to do, what Nova is doing (its connection with Neutron), to make sure that the settings are in place correctly? Here is how I am installing Mitaka on Xenial: --- 1- Install Ubuntu 16.04 server 64-bit on bare-metal; * Configure your /etc/hostname and /etc/hosts. DETAILS: https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md 2- Clone the automation: cd ~ git clone https://github.com/tmartinx/svauto.git 3- Run the automation to install OpenStack (all-in-one) cd ~/svauto ./os-deploy.sh --br-mode=LBR --use-dummies --base-os=ubuntu16 --base-os-upgrade=yes --openstack-release=mitaka --openstack-installation --dry-run ansible-playbook -c local site-openstack.yml --extra-vars "openstack_installation=yes" --- NOTE: If you don't use "--dry-run" option, Ansible will be executed automatically by "os-deploy.sh". I am sharing the Ansible playbooks, because it will be easier to see what I am doing. About the relevant configuration blocks, I believe that I have it properly configured (I followed Mitaka docs), like this: * neutron.conf: - https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_neutron_aio/templates/mitaka/neutron.conf - * nova.conf: - https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_aio/templates/mitaka/nova.conf - I already installed OpenStack many, many, many times, since Havana release, I'm confident that I am doing it right but, of course, maybe I did something wrong this time... =P I appreciate any help! Thanks! Thiago >>> >>> Hey guys, >>> >>> I am reviewing everything, to make sure that my automation
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
Martinx, glad to see that you are able to dig into the typo issue. I remember, I had to completely re-re-clean install my virtual setup of OpenStack for a POC back in 2015 , just because I have had miss-configured my neutron.conf's mysql DB connector information. Cheers! Regards, Nasir Mahmood On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ジェームズ wrote: > FIXED!! I knew it was a typo somewhere! LOL > > > https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 > > Thank you guys! > > Sorry about the buzz on TWO mail lists... > > At least, now we know that Nova silent fail on its start up, if somethings > aren't configured according... And there is no verification steps to test > the communication between Nova and Neutron. > > Mitaka is working now on Xenial! YAY!! > > I'm about to commit changes to enable OpenvSwitch with DPDK and multi-node > deployments, fully automated! > > Cheers! > Thiago > > On 17 April 2016 at 21:26, Martinx - ジェームズ > wrote: > >> On 17 April 2016 at 17:39, Martinx - ジェームズ >> wrote: >> >>> Guys, >>> >>> I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the >>> following document: >>> >>> http://docs.openstack.org/mitaka/install-guide-ubuntu >>> >>> Yes, I know, the above document is for installing Mitaka on top of >>> Ubuntu 14.04 but, from what I understand, the only difference is that on >>> Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, since >>> Mitaka is the default on Xenial, so, I can follow that document, right? >>> =) >>> >>> At first, OpenStack installation goes okay, without any errors, all >>> services comes up, etc... However, it is not possible to launch an Instance. >>> >>> *** Errors on launching the Instance: >>> >>> - Right after launching it: >>> >>> https://paste.ubuntu.com/15902503/ >>> >>> - Spawning it, after Glance finishes the download, similar error a >>> second time: >>> >>> https://paste.ubuntu.com/15902556/ >>> >>> What am I missing? >>> >>> Apparently, Nova is not authorized to talk with Neutron but, I am >>> following the docs (maybe it is just a typo somewhere?)... >>> >>> Also, I have an Ansible automation to deploy it, so, it is less error >>> prone. And however can help me, will see how I am deploying it. >>> >>> I see no error on Admin Dashboard, all services are up. >>> >>> NOTE: My Ansible playbooks is in a sense, " >>> docs.openstack.org/mitaka/install-guide-ubuntu fully automated", it is >>> very close to it, step-by-step. >>> >>> How can I debug this? I mean, how can I try to do, what Nova is doing >>> (its connection with Neutron), to make sure that the settings are in place >>> correctly? >>> >>> Here is how I am installing Mitaka on Xenial: >>> >>> --- >>> 1- Install Ubuntu 16.04 server 64-bit on bare-metal; >>> >>>* Configure your /etc/hostname and /etc/hosts. >>> >>>DETAILS: >>> https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md >>> >>> >>> 2- Clone the automation: >>> >>> cd ~ >>> git clone https://github.com/tmartinx/svauto.git >>> >>> >>> 3- Run the automation to install OpenStack (all-in-one) >>> >>> cd ~/svauto >>> >>>./os-deploy.sh --br-mode=LBR --use-dummies --base-os=ubuntu16 >>> --base-os-upgrade=yes --openstack-release=mitaka --openstack-installation >>> --dry-run >>> >>>ansible-playbook -c local site-openstack.yml --extra-vars >>> "openstack_installation=yes" >>> --- >>> >>> NOTE: If you don't use "--dry-run" option, Ansible will be executed >>> automatically by "os-deploy.sh". >>> >>> I am sharing the Ansible playbooks, because it will be easier to see >>> what I am doing. >>> >>> About the relevant configuration blocks, I believe that I have it >>> properly configured (I followed Mitaka docs), like this: >>> >>> * neutron.conf: >>> - >>> >>> https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_neutron_aio/templates/mitaka/neutron.conf >>> - >>> >>> * nova.conf: >>> - >>> >>> https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_aio/templates/mitaka/nova.conf >>> - >>> >>> I already installed OpenStack many, many, many times, since Havana >>> release, I'm confident that I am doing it right but, of course, maybe I did >>> something wrong this time... =P >>> >>> I appreciate any help! >>> >>> Thanks! >>> Thiago >>> >> >> Hey guys, >> >> I am reviewing everything, to make sure that my automation matches >> docs.openstack.org/mitaka/install-guide-ubuntu/ in details. >> >> Two things... >> >> --- >> 1- All the verification steps (from official doc) passed >> >> >> http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-verify.html >> - passed >> >> >> http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-openrc.html >> - passed >> >> >> http://docs.openstack.org/mitaka/install-guide-ubuntu/glance-verify.html >> - passed >> >> http://docs.openstack.org/mitaka/install-guide-ubuntu/nova-verify.html >> - passed >> >> >> http://docs.openstack.org/mitaka/install-gui
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
FIXED!! I knew it was a typo somewhere! LOL https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02 Thank you guys! Sorry about the buzz on TWO mail lists... At least, now we know that Nova silent fail on its start up, if somethings aren't configured according... And there is no verification steps to test the communication between Nova and Neutron. Mitaka is working now on Xenial! YAY!! I'm about to commit changes to enable OpenvSwitch with DPDK and multi-node deployments, fully automated! Cheers! Thiago On 17 April 2016 at 21:26, Martinx - ジェームズ wrote: > On 17 April 2016 at 17:39, Martinx - ジェームズ > wrote: > >> Guys, >> >> I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the >> following document: >> >> http://docs.openstack.org/mitaka/install-guide-ubuntu >> >> Yes, I know, the above document is for installing Mitaka on top of >> Ubuntu 14.04 but, from what I understand, the only difference is that on >> Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, since >> Mitaka is the default on Xenial, so, I can follow that document, right? >> =) >> >> At first, OpenStack installation goes okay, without any errors, all >> services comes up, etc... However, it is not possible to launch an Instance. >> >> *** Errors on launching the Instance: >> >> - Right after launching it: >> >> https://paste.ubuntu.com/15902503/ >> >> - Spawning it, after Glance finishes the download, similar error a >> second time: >> >> https://paste.ubuntu.com/15902556/ >> >> What am I missing? >> >> Apparently, Nova is not authorized to talk with Neutron but, I am >> following the docs (maybe it is just a typo somewhere?)... >> >> Also, I have an Ansible automation to deploy it, so, it is less error >> prone. And however can help me, will see how I am deploying it. >> >> I see no error on Admin Dashboard, all services are up. >> >> NOTE: My Ansible playbooks is in a sense, " >> docs.openstack.org/mitaka/install-guide-ubuntu fully automated", it is >> very close to it, step-by-step. >> >> How can I debug this? I mean, how can I try to do, what Nova is doing >> (its connection with Neutron), to make sure that the settings are in place >> correctly? >> >> Here is how I am installing Mitaka on Xenial: >> >> --- >> 1- Install Ubuntu 16.04 server 64-bit on bare-metal; >> >>* Configure your /etc/hostname and /etc/hosts. >> >>DETAILS: >> https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md >> >> >> 2- Clone the automation: >> >> cd ~ >> git clone https://github.com/tmartinx/svauto.git >> >> >> 3- Run the automation to install OpenStack (all-in-one) >> >> cd ~/svauto >> >>./os-deploy.sh --br-mode=LBR --use-dummies --base-os=ubuntu16 >> --base-os-upgrade=yes --openstack-release=mitaka --openstack-installation >> --dry-run >> >>ansible-playbook -c local site-openstack.yml --extra-vars >> "openstack_installation=yes" >> --- >> >> NOTE: If you don't use "--dry-run" option, Ansible will be executed >> automatically by "os-deploy.sh". >> >> I am sharing the Ansible playbooks, because it will be easier to see >> what I am doing. >> >> About the relevant configuration blocks, I believe that I have it >> properly configured (I followed Mitaka docs), like this: >> >> * neutron.conf: >> - >> >> https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_neutron_aio/templates/mitaka/neutron.conf >> - >> >> * nova.conf: >> - >> >> https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_aio/templates/mitaka/nova.conf >> - >> >> I already installed OpenStack many, many, many times, since Havana >> release, I'm confident that I am doing it right but, of course, maybe I did >> something wrong this time... =P >> >> I appreciate any help! >> >> Thanks! >> Thiago >> > > Hey guys, > > I am reviewing everything, to make sure that my automation matches > docs.openstack.org/mitaka/install-guide-ubuntu/ in details. > > Two things... > > --- > 1- All the verification steps (from official doc) passed > > > http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-verify.html > - passed > > > http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-openrc.html > - passed > > http://docs.openstack.org/mitaka/install-guide-ubuntu/glance-verify.html > - passed > > http://docs.openstack.org/mitaka/install-guide-ubuntu/nova-verify.html > - passed > > > http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify.html > - passed > > > http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify-option2.html > - passed > > > http://docs.openstack.org/mitaka/install-guide-ubuntu/horizon-verify.html > - passed (mine doesn't have /horizon) > > http://docs.openstack.org/mitaka/install-guide-ubuntu/cinder-verify.html > - passed but, I'm not using any cinder-volume yet > > > http://docs.openstack.org/mitaka/install-guide-ubuntu/launch-instance-selfservice.html > - "6. Launch the instance" - FAIL > > NOTE:
Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
On 17 April 2016 at 17:39, Martinx - ジェームズ wrote: > Guys, > > I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the > following document: > > http://docs.openstack.org/mitaka/install-guide-ubuntu > > Yes, I know, the above document is for installing Mitaka on top of Ubuntu > 14.04 but, from what I understand, the only difference is that on Xenial, > there is no need to add the Ubuntu Mitaka Cloud Archive, since Mitaka is > the default on Xenial, so, I can follow that document, right?=) > > At first, OpenStack installation goes okay, without any errors, all > services comes up, etc... However, it is not possible to launch an Instance. > > *** Errors on launching the Instance: > > - Right after launching it: > > https://paste.ubuntu.com/15902503/ > > - Spawning it, after Glance finishes the download, similar error a second > time: > > https://paste.ubuntu.com/15902556/ > > What am I missing? > > Apparently, Nova is not authorized to talk with Neutron but, I am > following the docs (maybe it is just a typo somewhere?)... > > Also, I have an Ansible automation to deploy it, so, it is less error > prone. And however can help me, will see how I am deploying it. > > I see no error on Admin Dashboard, all services are up. > > NOTE: My Ansible playbooks is in a sense, " > docs.openstack.org/mitaka/install-guide-ubuntu fully automated", it is > very close to it, step-by-step. > > How can I debug this? I mean, how can I try to do, what Nova is doing > (its connection with Neutron), to make sure that the settings are in place > correctly? > > Here is how I am installing Mitaka on Xenial: > > --- > 1- Install Ubuntu 16.04 server 64-bit on bare-metal; > >* Configure your /etc/hostname and /etc/hosts. > >DETAILS: > https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md > > > 2- Clone the automation: > > cd ~ > git clone https://github.com/tmartinx/svauto.git > > > 3- Run the automation to install OpenStack (all-in-one) > > cd ~/svauto > >./os-deploy.sh --br-mode=LBR --use-dummies --base-os=ubuntu16 > --base-os-upgrade=yes --openstack-release=mitaka --openstack-installation > --dry-run > >ansible-playbook -c local site-openstack.yml --extra-vars > "openstack_installation=yes" > --- > > NOTE: If you don't use "--dry-run" option, Ansible will be executed > automatically by "os-deploy.sh". > > I am sharing the Ansible playbooks, because it will be easier to see what > I am doing. > > About the relevant configuration blocks, I believe that I have it > properly configured (I followed Mitaka docs), like this: > > * neutron.conf: > - > > https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_neutron_aio/templates/mitaka/neutron.conf > - > > * nova.conf: > - > > https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_aio/templates/mitaka/nova.conf > - > > I already installed OpenStack many, many, many times, since Havana > release, I'm confident that I am doing it right but, of course, maybe I did > something wrong this time... =P > > I appreciate any help! > > Thanks! > Thiago > Hey guys, I am reviewing everything, to make sure that my automation matches docs.openstack.org/mitaka/install-guide-ubuntu/ in details. Two things... --- 1- All the verification steps (from official doc) passed http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-verify.html - passed http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-openrc.html - passed http://docs.openstack.org/mitaka/install-guide-ubuntu/glance-verify.html - passed http://docs.openstack.org/mitaka/install-guide-ubuntu/nova-verify.html - passed http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify.html - passed http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify-option2.html - passed http://docs.openstack.org/mitaka/install-guide-ubuntu/horizon-verify.html - passed (mine doesn't have /horizon) http://docs.openstack.org/mitaka/install-guide-ubuntu/cinder-verify.html - passed but, I'm not using any cinder-volume yet http://docs.openstack.org/mitaka/install-guide-ubuntu/launch-instance-selfservice.html - "6. Launch the instance" - FAIL NOTE: I can create Networks, Subnets, Routers... I can see the Linux Namespaces at the Neutron L3 Router (All-in-One) 2- This problem happen no matter if deploying it with Linux Bridges (--br-mode=LBR) or with OpenvSwitch (--br-mode=OVS) --- So, I think that OpenStack should provide more verification steps, specially to test the communication / authentication between its different projects, for example: A- Does Nova can communicate with Neutron? How to test this? B- Can Nova download images from Glance? Etc... Doing more reviews now... Cheers! Thiago ___ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/c
[Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized
Guys, I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using the following document: http://docs.openstack.org/mitaka/install-guide-ubuntu Yes, I know, the above document is for installing Mitaka on top of Ubuntu 14.04 but, from what I understand, the only difference is that on Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive, since Mitaka is the default on Xenial, so, I can follow that document, right?=) At first, OpenStack installation goes okay, without any errors, all services comes up, etc... However, it is not possible to launch an Instance. *** Errors on launching the Instance: - Right after launching it: https://paste.ubuntu.com/15902503/ - Spawning it, after Glance finishes the download, similar error a second time: https://paste.ubuntu.com/15902556/ What am I missing? Apparently, Nova is not authorized to talk with Neutron but, I am following the docs (maybe it is just a typo somewhere?)... Also, I have an Ansible automation to deploy it, so, it is less error prone. And however can help me, will see how I am deploying it. I see no error on Admin Dashboard, all services are up. NOTE: My Ansible playbooks is in a sense, " docs.openstack.org/mitaka/install-guide-ubuntu fully automated", it is very close to it, step-by-step. How can I debug this? I mean, how can I try to do, what Nova is doing (its connection with Neutron), to make sure that the settings are in place correctly? Here is how I am installing Mitaka on Xenial: --- 1- Install Ubuntu 16.04 server 64-bit on bare-metal; * Configure your /etc/hostname and /etc/hosts. DETAILS: https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md 2- Clone the automation: cd ~ git clone https://github.com/tmartinx/svauto.git 3- Run the automation to install OpenStack (all-in-one) cd ~/svauto ./os-deploy.sh --br-mode=LBR --use-dummies --base-os=ubuntu16 --base-os-upgrade=yes --openstack-release=mitaka --openstack-installation --dry-run ansible-playbook -c local site-openstack.yml --extra-vars "openstack_installation=yes" --- NOTE: If you don't use "--dry-run" option, Ansible will be executed automatically by "os-deploy.sh". I am sharing the Ansible playbooks, because it will be easier to see what I am doing. About the relevant configuration blocks, I believe that I have it properly configured (I followed Mitaka docs), like this: * neutron.conf: - https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_neutron_aio/templates/mitaka/neutron.conf - * nova.conf: - https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_aio/templates/mitaka/nova.conf - I already installed OpenStack many, many, many times, since Havana release, I'm confident that I am doing it right but, of course, maybe I did something wrong this time... =P I appreciate any help! Thanks! Thiago ___ 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
