[Openstack] [Keystone Middleware] Deprecate in-process token cache

[Kuo Hugo]

Hi Keystone Team,

We aware this deprecation information in keystone middleware. I got couple
of questions.

https://github.com/openstack/keystonemiddleware/blob/6e58f8620ae60eb4f26984258d15a9823345c310/releasenotes/notes/deprecate-caching-tokens-in-process-a412b0f1dea84cb9.yaml

We may need to update the document for Swift.

I want to clarify that if Keystone team plan to deprecate support for the
EnvCache (!?) or just the in-memory non-memcache option if you don't set
*neither* memcached_servers *nor* env_cache .

Thanks // Hugo
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

[Openstack] Horizon - CSRF verification failed

[Jagga Soorma]

Hi Guys,

We have a new kilo based openstack environment with ssl enabled.  On most
browsers when accessing the https link to horizon when users login they get
the following error:

--
Forbidden (403)
CSRF verification failed. Request aborted.
You are seeing this message because this site requires a CSRF cookie when
submitting forms. This cookie is required for security reasons, to ensure
that your browser is not being hijacked by third parties.
If you have configured your browser to disable cookies, please re-enable
them, at least for this site, or for 'same-origin' requests.
--

Is there something that can be done to permanently clear this up?  Either
from the browser (besides remove the cookie each time) or from openstack
itself?

Thanks!
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized

[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 am reviewing everything, to make sure that my automation 

[Openstack] April 19 Deadline for Registration Codes - OpenStack Summit Austin

[Kendall Waters]

Hi everyone,

This is a reminder that all registration codes (Speaker, Sponsor, ATC, etc.) 
for the OpenStack Summit in Austin must be redeemed by tomorrow, April 19 by 
11:59pm PT (April 20 at 6:59 UTC).

April 19 is also the last day to request refunds and transfers. 

Please direct any Summit related questions to sum...@openstack.org 
.

Cheers,
Kendall

Kendall Waters
OpenStack Marketing
kend...@openstack.org


___
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

Re: [Openstack] Xenial / Mitaka = Instance failed network setup / nova.compute.manager Unauthorized

[Nasir Mahmood]

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

[Openstack] Metadata Usage

[Jean-Pierre Ribeauville]

Hi,

My goal is to add a Unix channel device in all  VM images .

As I found nothing similar to VDSM hook , Is it possible to achieve it by using 
metadata ?


Thx for help.

Regards,

Jean-Pierre RIBEAUVILLE

+33 1 4717 2049

[axway_logo_tagline_87px]

___
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