Re: [openstack-dev] [openstack-infra][jacket]request to be added to the groups in gerrit

[Kevin.ZhangSen]

Thanks a lot.

Best regards,
Keivn(Sen Zhang)









At 2016-04-28 10:57:29, "Elizabeth K. Joseph"  wrote:
>On Wed, Apr 27, 2016 at 7:21 PM, Kevin.ZhangSen  wrote:
>> Hi Infra Team,
>>
>> We will start working on the new project. Could you please add me to
>> jacket-core and jacket-release in gerrit, so that I can add others.
>> Thanks a lot.
>
>No problem, done. You can now add others to these teams.
>
>For reference, the corresponding change by Kevin (Sen Zhang) to add
>this project is here: https://review.openstack.org/#/c/263500/
>
>-- 
>Elizabeth Krumbach Joseph || Lyz || pleia2
>
>__
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] Deploying kolla from a container?

[Michał Jastrzębski]

Hey,

So privileged containers are required by stuff like libvirt, and there
isn't much we can do about it. Shared /run is required by openvswitch
afair. We didn't try to run Kolla with swarm, but I'm afraid that
privileged container and network host are unfortunately a must. OpenStack
wasn't really build to be run in containers, so we had to make sacrifices
here and there. We are experimenting with kubernates now, as it supports
both priv containers and net host.

Let me know what if I can be any help.


Michal
On Apr 27, 2016 5:27 PM, "Jamie Hannaford" 
wrote:

> Hi,
>
>
> Is it possible to deploy Kolla from a container rather than an
> ubuntu/centos VM? I have a Swarm cluster, so I don't really want to leave
> that ecosystem and start creating other cloud resources.
>
>
> I got quite far with the dev guide, but the step which seems to throw a
> spanner in the works is setting the ​MountFlags. You recommend either
> systemd (15.04+) or `mount --make-shared /run` (14.04), both of which
> require a container running in privileged mode, which I can't do on my
> swarm cluster. Is there any workaround here?
>
>
> Alternatively, is it possible to run a privileged container locally in
> virtualbox and have it deploy to a remote Swarm cluster?
>
>
> Any advice you have here would be really appreciated. Kolla looks like a
> great project!
>
>
> Jamie
>
> --
> Rackspace International GmbH a company registered in the Canton of Zurich,
> Switzerland (company identification number CH-020.4.047.077-1) whose
> registered office is at Pfingstweidstrasse 60, 8005 Zurich, Switzerland.
> Rackspace International GmbH privacy policy can be viewed at
> www.rackspace.co.uk/legal/swiss-privacy-policy - This e-mail message may
> contain confidential or privileged information intended for the recipient.
> Any dissemination, distribution or copying of the enclosed material is
> prohibited. If you receive this transmission in error, please notify us
> immediately by e-mail at ab...@rackspace.com and delete the original
> message. Your cooperation is appreciated.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-infra][jacket]request to be added to the groups in gerrit

[Elizabeth K. Joseph]

On Wed, Apr 27, 2016 at 7:21 PM, Kevin.ZhangSen  wrote:
> Hi Infra Team,
>
> We will start working on the new project. Could you please add me to
> jacket-core and jacket-release in gerrit, so that I can add others.
> Thanks a lot.

No problem, done. You can now add others to these teams.

For reference, the corresponding change by Kevin (Sen Zhang) to add
this project is here: https://review.openstack.org/#/c/263500/

-- 
Elizabeth Krumbach Joseph || Lyz || pleia2

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [horizon] How to paginate Data Table to display only 5 rows every page ?

[严超]

Can we hard code only one table to 5 rows limit default ? And leave other
tables not touched.
Thank you very much !

严超 于2016年4月28日周四 上午6:58写道：

> Oh, sorry, I mean, can we hard code only one table to 5 rows default ? And
> leave others not touched.
> Thank you very much !
>
> *Best Regards！*
>
>
> *Chao Yan--About me ： http://about.me/chao_yan
> *
>
> *My twitter： @yanchao727 *
> *My Weibo： http://weibo.com/herewearenow *
> *--*
>
> 2016-04-28 1:51 GMT+08:00 Timur Sufiev :
>
>> Definitely, yes
>>
>> See how it's done for Images:
>> https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/images/views.py#L35
>>
>> Also, limit of items per table page is set in User Settings
>> (->Settings at top right corner of the dashboard), it's not
>> hard-coded. Once you set it, all tables which support pagination (see the
>> pattern above) display the specified number of items per page.
>>
>> On Wed, Apr 27, 2016 at 1:00 PM 严超  wrote:
>>
>>> Hi, Everyone:
>>> Is there a possible way to paginate DataTable to display only 5
>>> rows every page ?
>>> I'm very grateful for reply.
>>>
>>> *Best Regards！*
>>>
>>>
>>> *Chao Yan--About me ： http://about.me/chao_yan
>>> *
>>>
>>> *My twitter： @yanchao727 *
>>> *My Weibo： http://weibo.com/herewearenow *
>>> *--*
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack-infra][jacket]request to be added to the groups in gerrit

[Kevin.ZhangSen]

Hi Infra Team,


We will start working on the new project. Could you please add me to 
jacket-core and jacket-release in gerrit, so that I can add others.
Thanks a lot.


Best regards,
Kevin(Sen Zhang)__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Block Device Mapping is Invalid

[Nathan Stratton]

I only get this with cinder v2, any ideas?


><>
nathan stratton

On Mon, Apr 25, 2016 at 7:53 PM, Nathan Stratton 
wrote:

> I just upgraded to RDO Kilo and no longer can boot volumes. I never see
> anything hit cinder, so I think the issue is inside of nova. I have been
> banging my head on this one all day, would love any help anyone can provide.
>
> [root@openstack nova(keystone)]# nova --debug boot --flavor 2
> --boot-volume 5c69b767-5c35-4acf-984f-5a6c3b3ddac8 dns2 --nic
> net-id=b2324538-26ee-4d06-bccd-0ef2f6778f6b,v4-fixed-ip=10.71.0.130 --nic
> net-id=38353702-811a-42a0-9d90-10a6019d22a7,v4-fixed-ip=50.205.128.46
> --availability-zone nova:virt05b.broadsoftlabs.net
> DEBUG (session:195) REQ: curl -g -i -X GET http://10.71.0.218:5000/v2.0/
> -H "Accept: application/json" -H "User-Agent: python-keystoneclient"
> INFO (connectionpool:213) Starting new HTTP connection (1): 10.71.0.218
> DEBUG (connectionpool:393) "GET /v2.0/ HTTP/1.1" 200 337
> DEBUG (session:224) RESP: [200] Content-Length: 337 Vary: X-Auth-Token
> Connection: keep-alive Date: Mon, 25 Apr 2016 23:47:45 GMT Content-Type:
> application/json X-Openstack-Request-Id:
> req-ff89e645-514c-4c13-b2cb-4f383d93d4ce
> RESP BODY: {"version": {"status": "stable", "updated":
> "2014-04-17T00:00:00Z", "media-types": [{"base": "application/json",
> "type": "application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0",
> "links": [{"href": "http://10.71.0.218:5000/v2.0/;, "rel": "self"},
> {"href": "http://docs.openstack.org/;, "type": "text/html", "rel":
> "describedby"}]}}
>
> DEBUG (v2:76) Making authentication request to
> http://10.71.0.218:5000/v2.0/tokens
> DEBUG (connectionpool:393) "POST /v2.0/tokens HTTP/1.1" 200 3070
> DEBUG (session:195) REQ: curl -g -i -X GET
> http://10.71.0.218:8774/v2/0ebcdedac0a3480ca81050bfedd97cf1/flavors/2 -H
> "User-Agent: python-novaclient" -H "Accept: application/json" -H
> "X-Auth-Token: {SHA1}5804468e0111677dc7e4165fecfa44f4c9e88994"
> INFO (connectionpool:213) Starting new HTTP connection (1): 10.71.0.218
> DEBUG (connectionpool:393) "GET
> /v2/0ebcdedac0a3480ca81050bfedd97cf1/flavors/2 HTTP/1.1" 200 423
> DEBUG (session:224) RESP: [200] Date: Mon, 25 Apr 2016 23:47:46 GMT
> Connection: keep-alive Content-Type: application/json Content-Length: 423
> X-Compute-Request-Id: req-4bf327b3-9b03-4437-bd18-3e799b6d69f0
> RESP BODY: {"flavor": {"name": "m1.small", "links": [{"href": "
> http://10.71.0.218:8774/v2/0ebcdedac0a3480ca81050bfedd97cf1/flavors/2;,
> "rel": "self"}, {"href": "
> http://10.71.0.218:8774/0ebcdedac0a3480ca81050bfedd97cf1/flavors/2;,
> "rel": "bookmark"}], "ram": 2048, "OS-FLV-DISABLED:disabled": false,
> "vcpus": 2, "swap": "", "os-flavor-access:is_public": true, "rxtx_factor":
> 1.0, "OS-FLV-EXT-DATA:ephemeral": 0, "disk": 32, "id": "2"}}
>
> DEBUG (session:195) REQ: curl -g -i -X POST
> http://10.71.0.218:8774/v2/0ebcdedac0a3480ca81050bfedd97cf1/os-volumes_boot
> -H "User-Agent: python-novaclient" -H "Content-Type: application/json" -H
> "Accept: application/json" -H "X-Auth-Token:
> {SHA1}5804468e0111677dc7e4165fecfa44f4c9e88994" -d '{"server": {"name":
> "dns2", "imageRef": "", "availability_zone": "nova:
> virt05b.broadsoftlabs.net", "block_device_mapping_v2": [{"source_type":
> "volume", "delete_on_termination": false, "boot_index": 0, "uuid":
> "5c69b767-5c35-4acf-984f-5a6c3b3ddac8", "destination_type": "volume"}],
> "flavorRef": "2", "max_count": 1, "min_count": 1, "networks": [{"fixed_ip":
> "10.71.0.130", "uuid": "b2324538-26ee-4d06-bccd-0ef2f6778f6b"},
> {"fixed_ip": "50.205.128.46", "uuid":
> "38353702-811a-42a0-9d90-10a6019d22a7"}]}}'
> DEBUG (connectionpool:393) "POST
> /v2/0ebcdedac0a3480ca81050bfedd97cf1/os-volumes_boot HTTP/1.1" 400 135
> DEBUG (session:224) RESP:
> DEBUG (shell:914) Block Device Mapping is Invalid: failed to get volume
> 5c69b767-5c35-4acf-984f-5a6c3b3ddac8. (HTTP 400) (Request-ID:
> req-a7974c64-fbd6-49de-a34b-ea2e3672cd67)
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/novaclient/shell.py", line 911,
> in main
> OpenStackComputeShell().main(argv)
>   File "/usr/lib/python2.7/site-packages/novaclient/shell.py", line 838,
> in main
> args.func(self.cs, args)
>   File "/usr/lib/python2.7/site-packages/novaclient/v2/shell.py", line
> 500, in do_boot
> server = cs.servers.create(*boot_args, **boot_kwargs)
>   File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line
> 900, in create
> **boot_kwargs)
>   File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line
> 523, in _boot
> return_raw=return_raw, **kwargs)
>   File "/usr/lib/python2.7/site-packages/novaclient/base.py", line 161, in
> _create
> _resp, body = self.api.client.post(url, body=body)
>   File "/usr/lib/python2.7/site-packages/keystoneclient/adapter.py", line
> 176, in post
> return self.request(url, 'POST', **kwargs)
>   File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 96,
> 

Re: [openstack-dev] [horizon] How to paginate Data Table to display only 5 rows every page ?

[严超]

Oh, sorry, I mean, can we hard code only one table to 5 rows default ? And
leave others not touched.
Thank you very much !

*Best Regards！*


*Chao Yan--About me ： http://about.me/chao_yan
*

*My twitter： @yanchao727 *
*My Weibo： http://weibo.com/herewearenow *
*--*

2016-04-28 1:51 GMT+08:00 Timur Sufiev :

> Definitely, yes
>
> See how it's done for Images:
> https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/images/views.py#L35
>
> Also, limit of items per table page is set in User Settings
> (->Settings at top right corner of the dashboard), it's not
> hard-coded. Once you set it, all tables which support pagination (see the
> pattern above) display the specified number of items per page.
>
> On Wed, Apr 27, 2016 at 1:00 PM 严超  wrote:
>
>> Hi, Everyone:
>> Is there a possible way to paginate DataTable to display only 5 rows
>> every page ?
>> I'm very grateful for reply.
>>
>> *Best Regards！*
>>
>>
>> *Chao Yan--About me ： http://about.me/chao_yan
>> *
>>
>> *My twitter： @yanchao727 *
>> *My Weibo： http://weibo.com/herewearenow *
>> *--*
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc project f2f2 meet-up place and time

[Stephen Wong]

Hi Cathy,

A technical discussion on networking-sfc tomorrow? Really? When and
where? Is this going to be the same one as the common flow classifier
discussion?

Thanks,
- Stephen

On Wed, Apr 27, 2016 at 3:55 PM, Cathy Zhang 
wrote:

> We will have a technical discussion tomorrow and record our meeting
> minutes in the etherpad.
> Tuesday is more a f2f social meet-up.
>
> Thanks,
> Cathy
>
> -Original Message-
> From: Elzur, Uri [mailto:uri.el...@intel.com]
> Sent: Wednesday, April 27, 2016 12:42 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc
> project f2f2 meet-up place and time
>
> Can you pls add more detailed minutes as to emerging
> agreements/understandings?
>
> Thx
>
> Uri ("Oo-Ree")
> C: 949-378-7568
>
>
> -Original Message-
> From: Akihiro Motoki [mailto:amot...@gmail.com]
> Sent: Tuesday, April 26, 2016 11:50 AM
> To: OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc
> project f2f2 meet-up place and time
>
> 2016-04-26 12:31 GMT-05:00 Henry Fourie :
> > All,
> >Please use the networking-sfc etherpad to record discussions at the
> > meetups:
> >
> > https://etherpad.openstack.org/p/networking-sfc-austin-summit-meeting
> >
> >  - Louis
> >
> > -Original Message-
> > From: Paul Carver [mailto:pcar...@paulcarver.us]
> > Sent: Tuesday, April 26, 2016 10:20 AM
> > To: openstack-dev@lists.openstack.org
> > Subject: Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc
> > project f2f2 meet-up place and time
> >
> > On 4/26/2016 00:35, Akihiro Motoki wrote:
> >> Hi Cathy and folks interested in SFC and classifers!
> >>
> >> Can't we use a different room like Salon D?
> >> Salon C is a lunch room and at that time there are no sessions in other
> rooms.
> >> It would be great if we can use Salon D or E (after looking at the
> >> first day's session) I think we can gather more easily and
> >> concentrate the discussion if we use some different space.
> >> Thought?
> >>
> >
> > Akihiro,
> >
> > Unless I've misunderstood the emails, the plan for Tuesday is a social
> lunch for the SFC team to get together. The plan for Wednesday is a working
> lunch to discuss flow classifiers in various projects and figure out how to
> converge on a single flow classifier API/model that can be shared by
> everything that needs to specify flows.
> >
> > If that's correct, then meeting in Salon C for lunch on Tuesday makes
> sense. For Wednesday we probably ought to grab boxed lunches and find a
> quiet room.
>
> I was confused with networking-sfc f2f meeting and flow classifier one.
> My previous mail is a suggestion for wednesday flow classifier meeting.
> Thanks for point it out.
>
> Akihiro
>
>
> >
> >
> > __
> >  OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> > __
> >  OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [kolla] Deploying kolla from a container?

[Jamie Hannaford]

Hi,


Is it possible to deploy Kolla from a container rather than an ubuntu/centos 
VM? I have a Swarm cluster, so I don't really want to leave that ecosystem and 
start creating other cloud resources.


I got quite far with the dev guide, but the step which seems to throw a spanner 
in the works is setting the ?MountFlags. You recommend either systemd (15.04+) 
or `mount --make-shared /run` (14.04), both of which require a container 
running in privileged mode, which I can't do on my swarm cluster. Is there any 
workaround here?


Alternatively, is it possible to run a privileged container locally in 
virtualbox and have it deploy to a remote Swarm cluster?


Any advice you have here would be really appreciated. Kolla looks like a great 
project!


Jamie



Rackspace International GmbH a company registered in the Canton of Zurich, 
Switzerland (company identification number CH-020.4.047.077-1) whose registered 
office is at Pfingstweidstrasse 60, 8005 Zurich, Switzerland. Rackspace 
International GmbH privacy policy can be viewed at 
www.rackspace.co.uk/legal/swiss-privacy-policy - This e-mail message may 
contain confidential or privileged information intended for the recipient. Any 
dissemination, distribution or copying of the enclosed material is prohibited. 
If you receive this transmission in error, please notify us immediately by 
e-mail at ab...@rackspace.com and delete the original message. Your cooperation 
is appreciated.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] OSC transition

[reedip banerjee]

>From my point of view, I would suggest discussing it once during the
NeutronClient session/OSC sessions on Thursday or once in the design meetup
on Friday. I feel we can see at it once more.
Currently I feel that the definition which is mentioned in the github is
not completely clear.

For the projects which already use clientcommand extension, the
implementation needs to be done in the project repo.
For "CORE" Resources, the implementation needs to be done in python-osc.
However, for the new resources/projects,  the implementation needs to be
clear because IMHO there is currently no clear definition as to which
resources should implement clientcommandextension( which means implement
the client code in the own repo) vs which resources can be added as simple
extensions to NeutronClient(I.e. which can reside in the NeutronClient
repo). However this is IMO, and if you have any guidelines which tells a
developer if a project needs to be a clientcommand extension for
NeutronClient ( or not) , please share the same.
On Apr 26, 2016 21:10, "Vikram Choudhary"  wrote:

+1 for keeping neutron-dynamic-routing CLI's in neutronclient repo like
other *aaS services.

Thanks
Vikram

On Tue, Apr 26, 2016 at 7:47 PM, Richard Theis  wrote:

> Hi,
>
> The latest devref [1] would place it in python-neutronclient as Henry
> noted. But stay tuned for results from the summit session.
>
> [1]
> https://github.com/openstack/python-neutronclient/blob/master/doc/source/devref/transition_to_osc.rst
>
> - Richard
>
>
> "Na Zhu"  wrote on 04/26/2016 08:29:21 AM:
>
> > From: "Na Zhu" 
> > To: hen...@gessau.net
> > Cc: "OpenStack Development Mailing List \(not for usage questions\)"
> > 
> > Date: 04/26/2016 08:34 AM
> > Subject: Re: [openstack-dev] [neutron] OSC transition
> >
> > Hi Henry,
> >
> > Thanks your information, why you think neutron-dynamic-routing CLI
> > should live in python-neutronclient?
> > From this link http://docs.openstack.org/developer/python-
> > neutronclient/devref/transition_to_osc.htmlsection "Where does my CLI
> belong?
> > ", *aas CLI belongs to their own project, not project python-
> > neutronclient. BGP is also service like *aas, so I think BGP CLIs
> > should live in neutron-dynamic-routing, or a separate repo named
> > python-*client. Pls correct me if I am wrong, thanks.
> >
> >
> >
> > Regards,
> > Juno Zhu
> > IBM China Development Labs (CDL) Cloud IaaS Lab
> > Email: na...@cn.ibm.com
> > 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong
> > New District, Shanghai, China (201203)
> >
> >
> >
> > From:Henry Gessau 
> > To:"OpenStack Development Mailing List (not for usage
> > questions)" 
> > Date:2016/04/26 21:09
> > Subject:Re: [openstack-dev] [neutron] OSC transition
> >
> >
> >
> > Adding the [neutron] tag.
> >
> > I believe that the OSC extension for neutron-dynamic-routing should live
> in
> > the python-neutronclient repo. Keep in touch with Richard Theis as he is
> the
> > one leading the transition to OSC. He is rtheis on IRC.
> >
> > See:
> >
> http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html
>
> > https://review.openstack.org/309587
> >
> >
> > Na Zhu  wrote:
> > > Dear All,
> > >
> > >
> > > I have a question about OSC transition, recently, the community
> approves
> > > moving bgp out of neutron, as a service like other *aas. The BGP
> > CLIs need be
> > > removed from neutronclient. Because of OSC transition, I can not
> > just move the
> > > BGP CLIs code from python-neutronclient repo to neutron-dynamic-
> > routing repo.
> > > I have to refactor the code and do transition to OSC plugin system.
> > >
> > > From the
> > > link _http://docs.openstack.org/developer/python-openstackclient/
> > plugins.html_, the
> > > client has a separate repo, take designate as example, the CLI repo is
> > > python-designateclient, the project repo is designate. So for BGP,
> should I
> > > create a repo for CLI, or leverage project repo
> neutron-dynamic-routing?
> > >
> > >
> > >
> > >
> > > Regards,
> > > Juno Zhu
> > > IBM China Development Labs (CDL) Cloud IaaS Lab
> > > Email: na...@cn.ibm.com
> > > 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New
> > > District, Shanghai, China (201203)
> > >
> > >
> > >
> __
> > > OpenStack Development Mailing List (not for usage questions)
> > > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> >
> >
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> 

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

[Cathy Zhang]

Hi Miguel,

No worry. Today is just a meeting for lunch to get to know each other although 
we touched some technical points.
We will recap and do the technical discussion at Room 400 at 3:10pm Thursday.

Cathy

From: Miguel Angel Ajo Pelayo [mailto:majop...@redhat.com]
Sent: Wednesday, April 27, 2016 10:50 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS 
Agent extension for Newton cycle


Trying to find you folks. I was late
El 27/4/2016 12:04, "Paul Carver" 
> escribió:
SFC team and anybody else dealing with flow selection/classification (e.g. QoS),

I just wanted to confirm that we're planning to meet in salon C today 
(Wednesday) to get lunch but then possibly move to a quieter location to 
discuss the common flow classifier ideas.

On 4/21/2016 19:42, Cathy Zhang wrote:
I like Malini’s suggestion on meeting for a lunch to get to know each
other, then continue on Thursday.

So let’s meet at "Salon C" for lunch from 12:30pm~1:50pm on Wednesday
and then continue the discussion at Room 400 at 3:10pm Thursday.

Since Salon C is a big room, I will put a sign “Common Flow Classifier
and OVS Agent Extension” on the table.

I have created an etherpad for the discussion.
https://etherpad.openstack.org/p/Neutron-FC-OVSAgentExt-Austin-Summit


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc project f2f2 meet-up place and time

[Cathy Zhang]

We will have a technical discussion tomorrow and record our meeting minutes in 
the etherpad. 
Tuesday is more a f2f social meet-up. 

Thanks,
Cathy

-Original Message-
From: Elzur, Uri [mailto:uri.el...@intel.com] 
Sent: Wednesday, April 27, 2016 12:42 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc project 
f2f2 meet-up place and time

Can you pls add more detailed minutes as to emerging agreements/understandings?

Thx

Uri ("Oo-Ree")
C: 949-378-7568


-Original Message-
From: Akihiro Motoki [mailto:amot...@gmail.com]
Sent: Tuesday, April 26, 2016 11:50 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc project 
f2f2 meet-up place and time

2016-04-26 12:31 GMT-05:00 Henry Fourie :
> All,
>Please use the networking-sfc etherpad to record discussions at the
> meetups:
>
> https://etherpad.openstack.org/p/networking-sfc-austin-summit-meeting
>
>  - Louis
>
> -Original Message-
> From: Paul Carver [mailto:pcar...@paulcarver.us]
> Sent: Tuesday, April 26, 2016 10:20 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc 
> project f2f2 meet-up place and time
>
> On 4/26/2016 00:35, Akihiro Motoki wrote:
>> Hi Cathy and folks interested in SFC and classifers!
>>
>> Can't we use a different room like Salon D?
>> Salon C is a lunch room and at that time there are no sessions in other 
>> rooms.
>> It would be great if we can use Salon D or E (after looking at the 
>> first day's session) I think we can gather more easily and 
>> concentrate the discussion if we use some different space.
>> Thought?
>>
>
> Akihiro,
>
> Unless I've misunderstood the emails, the plan for Tuesday is a social lunch 
> for the SFC team to get together. The plan for Wednesday is a working lunch 
> to discuss flow classifiers in various projects and figure out how to 
> converge on a single flow classifier API/model that can be shared by 
> everything that needs to specify flows.
>
> If that's correct, then meeting in Salon C for lunch on Tuesday makes sense. 
> For Wednesday we probably ought to grab boxed lunches and find a quiet room.

I was confused with networking-sfc f2f meeting and flow classifier one.
My previous mail is a suggestion for wednesday flow classifier meeting.
Thanks for point it out.

Akihiro


>
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [kolla] Ubuntu build is broken

[Michał Jastrzębski]

Hey,

I'm sorry to say that we can't currently build ubuntu with default
options. This will be addressed by this review:
https://review.openstack.org/#/c/310574/1

There is a workaround for that and that is building with either
--base-tag=14.04 or change in /etc/kolla/kolla_build.conf :

base_tag = 14.04

Cheers,
Michal

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] backwards compatibility followup

[Brian Demers]

On Tue, Apr 26, 2016 at 10:55 PM, Robert Collins 
wrote:

> On 26 April 2016 at 18:41, Ian Cordasco  wrote:
> >
> >> On Apr 26, 2016, at 6:32 PM, Perry, Sean  wrote:
> >>
> >> What if we update the docs and tell people to put any services on a
> shared system into independent virtualenvs?
> >>
> >> If a box only runs neutron or whatever all is well. The issue happens
> when you mix and match services on a single host. Which is exactly what
> virtualenv was intended to fix.
> >
> > Except that a fair portion of respondents to the OpenStack User Survey
> talk about using packages provided by the distribution of Linux they happen
> to be on. Those cannot be installed into virtual environments.
>
> Right. The specific situation is 'same python environment' - so distro
> packages all land in the same python environment. You can make
> packages of virtualenvs and other such things - and folk wanting to be
> able to do same-node-no-container-distro-package in-place upgrade
> solutions would be looking at such things if we decide we don't want
> to support/enable this.
>
> Some distros were in the room, and e.g. I believe it was Dan that said
> RH don't support - in their packaging - mixed versions: upgrade nova,
> and neutron would be upgraded too in the given example. So its
> possible that while some folk aspire to it, many other folk are either
> accepting downtime, or running their control plane on isolated
> operating system instances (whether physical, VM or containers is
> irrelevant).
>
> At the party tonight I ran into Brian Demers and a colleague whose
> name I have forgotten :(

Sam Betts

> - but they have a backwards compat use case
> we hadn't touched on in the session: running their Neutron plugin
> against both stable and master of Neutron.
>
> This is a classic colocation situation. There are a few possible scenarios:
>  - run stable branches of the plugin and backport everything
> - tricky if new oslo features are needed, but the existing pattern.
> - also tricky for users, since there would be lots of releases of
> both stable and master
>  - run master against stable neutron using stable neutron oslo
>  - means they can't use any new oslo features, and they would
> depend on oslo not breaking any API's they use in master - so depends
> on oslo API compat
>  - or they have to provide backports within their tree and monkey
> patch them into place, of new/changed things from oslo
>  - run master against stable neutron using master oslo
> - means neutron would have to work with master oslo - so the same
> compat story, just from the other side
>

Thanks for following up Rob.

Related to this, (and not to steer this off on a tangent) is the frequency
of major version changes in libraries, more specifically API breaking
changes.

The items mentioned in this thread would be difficult at best unless we
have stable [backwards compatible] APIs.

-Brian
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] Social at the summit

[Tidwell, Ryan]

+1

-Original Message-
From: Kyle Mestery [mailto:mest...@mestery.com] 
Sent: Monday, April 25, 2016 11:07 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [neutron] Social at the summit

OK, there is enough interest, I'll find a place on 6th Street for us and get a 
reservation for Thursday around 7 or so.

Thanks folks!

On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:
> +1 :)
>
> Han Zhou
> Irc: zhouhan
>
>
> On Monday, April 25, 2016, Korzeniewski, Artur 
>  wrote:
>>
>> Sign me up :)
>>
>> Artur
>> IRC: korzen
>>
>> -Original Message-
>> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
>> Sent: Monday, April 25, 2016 7:19 PM
>> To: OpenStack Development Mailing List (not for usage questions) 
>> 
>> Subject: Re: [openstack-dev] [neutron] Social at the summit
>>
>> Count me in!
>> Will be good to meet all you guys!
>>
>> Darek (dasm) Smigiel
>>
>> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley 
>> >  wrote:
>> >
>> >
>> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
>> >> 
>> >> wrote:
>> >>
>> >> WAT???
>> >>
>> >> It was never supposed to be core only. Everyone is welcome!
>> >
>> > +2
>> >
>> > irony intended.
>> >
>> > Socials are not controlled by gerrit ACLs.  :-)
>> >
>> > doug
>> >
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On 25 Apr 2016, at 11:56, Edgar Magana 
>> >>> wrote:
>> >>>
>> >>> Would you extend it to ex-cores?
>> >>>
>> >>> Edgar
>> >>>
>> >>>
>> >>>
>> >>>
>>  On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
>> 
>>  Ihar, Henry and I were talking and we thought Thursday night 
>>  makes sense for a Neutron social in Austin. If others agree, 
>>  reply on this thread and we'll find a place.
>> 
>>  Thanks!
>>  Kyle
>> 
>>  
>>  ___ ___ OpenStack Development Mailing List (not for usage
>>  questions)
>>  Unsubscribe:
>>  openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-de
>>  v
>> >>> _
>> >>> ___ __ OpenStack Development Mailing List (not for usage 
>> >>> questions)
>> >>> Unsubscribe:
>> >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>
>> >> __
>> >> ___ _ OpenStack Development Mailing List (not for usage 
>> >> questions)
>> >> Unsubscribe:
>> >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> >
>> > ___
>> > ___  OpenStack Development Mailing List (not for usage 
>> > questions)
>> > Unsubscribe:
>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> _
>> _ OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> _
>> _ OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [horizon] How to paginate Data Table to display only 5 rows every page ?

[Timur Sufiev]

Definitely, yes

See how it's done for Images:
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/images/views.py#L35

Also, limit of items per table page is set in User Settings
(->Settings at top right corner of the dashboard), it's not
hard-coded. Once you set it, all tables which support pagination (see the
pattern above) display the specified number of items per page.

On Wed, Apr 27, 2016 at 1:00 PM 严超  wrote:

> Hi, Everyone:
> Is there a possible way to paginate DataTable to display only 5 rows
> every page ?
> I'm very grateful for reply.
>
> *Best Regards！*
>
>
> *Chao Yan--About me ： http://about.me/chao_yan
> *
>
> *My twitter： @yanchao727 *
> *My Weibo： http://weibo.com/herewearenow *
> *--*
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

[Miguel Angel Ajo Pelayo]

Please add me to whatsapp or telegram if you use that : +34636522569
El 27/4/2016 12:50, majop...@redhat.com escribió:

> Trying to find you folks. I was late
> El 27/4/2016 12:04, "Paul Carver"  escribió:
>
>> SFC team and anybody else dealing with flow selection/classification
>> (e.g. QoS),
>>
>> I just wanted to confirm that we're planning to meet in salon C today
>> (Wednesday) to get lunch but then possibly move to a quieter location to
>> discuss the common flow classifier ideas.
>>
>> On 4/21/2016 19:42, Cathy Zhang wrote:
>>
>>> I like Malini’s suggestion on meeting for a lunch to get to know each
>>> other, then continue on Thursday.
>>>
>>> So let’s meet at "Salon C" for lunch from 12:30pm~1:50pm on Wednesday
>>> and then continue the discussion at Room 400 at 3:10pm Thursday.
>>>
>>> Since Salon C is a big room, I will put a sign “Common Flow Classifier
>>> and OVS Agent Extension” on the table.
>>>
>>> I have created an etherpad for the discussion.
>>> https://etherpad.openstack.org/p/Neutron-FC-OVSAgentExt-Austin-Summit
>>>
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

[Miguel Angel Ajo Pelayo]

Trying to find you folks. I was late
El 27/4/2016 12:04, "Paul Carver"  escribió:

> SFC team and anybody else dealing with flow selection/classification (e.g.
> QoS),
>
> I just wanted to confirm that we're planning to meet in salon C today
> (Wednesday) to get lunch but then possibly move to a quieter location to
> discuss the common flow classifier ideas.
>
> On 4/21/2016 19:42, Cathy Zhang wrote:
>
>> I like Malini’s suggestion on meeting for a lunch to get to know each
>> other, then continue on Thursday.
>>
>> So let’s meet at "Salon C" for lunch from 12:30pm~1:50pm on Wednesday
>> and then continue the discussion at Room 400 at 3:10pm Thursday.
>>
>> Since Salon C is a big room, I will put a sign “Common Flow Classifier
>> and OVS Agent Extension” on the table.
>>
>> I have created an etherpad for the discussion.
>> https://etherpad.openstack.org/p/Neutron-FC-OVSAgentExt-Austin-Summit
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Devstack liberty with keystone v3

[kiran vemuri UH]

Hello ZhiQiang Fan,

I am able to fetch v3 catalog by using the openstack commands. But, as I
mentioned earlier, I am trying to setup a multi node setup using devstack
stable/liberty. I am using the documentation at
http://docs.openstack.org/developer/devstack/configuration.html#multi-region-setup
as reference.

I have the first node up and running without any issues.. and I think it
has keystone v2 used for authentication of all services and keystone v3
running alongside.(Because when I fetch v2 catalog, I am getting all the
endpoints and when I fetch v3 catalog, I see no endpoints)

Now when I deploy node2 with the local.conf changes suggested, everytime
stack.sh is failing at the same error as shown below:
--

16-04-27 02:54:59.101 | + local kernel_id= ramdisk_id=

2016-04-27 02:54:59.101 | + '[' -n
/devstack/devstack/files/images/cirros-0.3.4-x86_64-uec/cirros-0.3.4-x86_64-vmlinuz
']'

2016-04-27 02:54:59.104 | ++ openstack --os-cloud=devstack-admin image
create cirros-0.3.4-x86_64-uec-kernel --public --container-format aki
--disk-format aki

2016-04-27 02:54:59.104 | ++ grep ' id '

2016-04-27 02:54:59.106 | ++ get_field 2

2016-04-27 02:54:59.107 | ++ local data field

2016-04-27 02:54:59.107 | ++ read data

2016-04-27 02:55:01.273 | 500 Internal Server Error: The server has either
erred or is incapable of performing the requested operation. (HTTP 500)

2016-04-27 02:55:01.313 | + kernel_id=

2016-04-27 02:55:01.313 | + '[' -n
/devstack/devstack/files/images/cirros-0.3.4-x86_64-uec/cirros-0.3.4-x86_64-initrd
']'

2016-04-27 02:55:01.316 | ++ grep ' id '

2016-04-27 02:55:01.316 | ++ openstack --os-cloud=devstack-admin image
create cirros-0.3.4-x86_64-uec-ramdisk --public --container-format ari
--disk-format ari

2016-04-27 02:55:01.316 | ++ get_field 2

2016-04-27 02:55:01.318 | ++ local data field

2016-04-27 02:55:01.319 | ++ read data

2016-04-27 02:55:03.470 | 500 Internal Server Error: The server has either
erred or is incapable of performing the requested operation. (HTTP 500)

2016-04-27 02:55:03.512 | + ramdisk_id=

2016-04-27 02:55:03.513 | + openstack --os-cloud=devstack-admin image
create cirros-0.3.4-x86_64-uec --public --container-format ami
--disk-format ami

2016-04-27 02:55:05.631 | 500 Internal Server Error: The server has either
erred or is incapable of performing the requested operation. (HTTP 500)

2016-04-27 02:55:05.671 | + exit_trap

2016-04-27 02:55:05.671 | + local r=1

2016-04-27 02:55:05.673 | ++ jobs -p

2016-04-27 02:55:05.675 | + jobs=

2016-04-27 02:55:05.675 | + [[ -n '' ]]

2016-04-27 02:55:05.675 | + kill_spinner

2016-04-27 02:55:05.675 | + '[' '!' -z '' ']'

2016-04-27 02:55:05.675 | + [[ 1 -ne 0 ]]

2016-04-27 02:55:05.675 | + echo 'Error on exit'

2016-04-27 02:55:05.676 | Error on exit

2016-04-27 02:55:05.676 | + generate-subunit 1461720901 4804 fail

2016-04-27 02:55:06.079 | + [[ -z /opt/stack/logs ]]

2016-04-27 02:55:06.079 | + /devstack/devstack/tools/worlddump.py -d
/opt/stack/logs

2016-04-27 02:55:06.536 | + exit 1
--

I was hoping I could get some help on getting this up and running. Do I
have to disable v2 and have the node with pure v3 for this to be possible?

Thanks, Kiran Vemuri
kiran vemuri
www.kiranvemuri.info
Tel: (832)-701-8281
kkvem...@uh.edu
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

[Paul Carver]

SFC team and anybody else dealing with flow selection/classification 
(e.g. QoS),


I just wanted to confirm that we're planning to meet in salon C today 
(Wednesday) to get lunch but then possibly move to a quieter location to 
discuss the common flow classifier ideas.


On 4/21/2016 19:42, Cathy Zhang wrote:

I like Malini’s suggestion on meeting for a lunch to get to know each
other, then continue on Thursday.

So let’s meet at "Salon C" for lunch from 12:30pm~1:50pm on Wednesday
and then continue the discussion at Room 400 at 3:10pm Thursday.

Since Salon C is a big room, I will put a sign “Common Flow Classifier
and OVS Agent Extension” on the table.

I have created an etherpad for the discussion.
https://etherpad.openstack.org/p/Neutron-FC-OVSAgentExt-Austin-Summit




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [api] [docs] WADL migration sign-up

[Anne Gentle]

Hi all,
Thanks to all those who groaned with me through the API docs working
session. :) I patched the instructions:
https://review.openstack.org/#/c/310514/

As promised, I've created this wiki page for people to sign up for a
migration task:

https://wiki.openstack.org/wiki/Documentation/Migrate#API_Reference_Plan

I've subscribed to changes on the page so I can keep track of who wants to
work on which services. Thanks so much!

Anne

-- 
Anne Gentle
www.justwriteclick.com
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] Social at the summit

[Kosnik, Lubosz]

+1 from me also :)


> On Apr 27, 2016, at 10:29 AM, Thomas Morin  wrote:
> 
> +1 !
> 
> Mon Apr 25 2016 10:55:33 GMT-0500 (CDT), Kyle Mestery:
>> Ihar, Henry and I were talking and we thought Thursday night makes sense for 
>> a Neutron social in Austin. If others agree, reply on this thread and we'll 
>> find a place.
>> 
>> Thanks!
>> Kyle
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] Social at the summit

[Thomas Morin]

+1 !

Mon Apr 25 2016 10:55:33 GMT-0500 (CDT), Kyle Mestery:

Ihar, Henry and I were talking and we thought Thursday night makes sense for a 
Neutron social in Austin. If others agree, reply on this thread and we'll find 
a place.

Thanks!
Kyle

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

[Michał Jastrzębski]

On 26 April 2016 at 13:51, Tomasz Pa  wrote:
> Hey Steven,
>
> answers inline.
>
> On Mon, Apr 25, 2016 at 9:27 AM, Steven Dake (stdake)  
> wrote:
>>
>> I disagree with your assertion.  You are gaming your data to provide the
>> worst possible container (nova) because the RPMs pull in libvirt.  Kolla
>> has no control over how Red Hat choses to package RDO, and at this time
>> they choose to package libvirt as a dependency thereof.  Obviously it
>> would be more optimal in a proper container system not to include libvirt
>> in the dependencies installed with Nova.  If you really want that, use
>> from source installs.  Then you could shave 1 minute off your upgrade time
>> of a 64 node cluster.
>
> Look here: http://paste.openstack.org/show/495459/ . As you can see
> there're no libvirt dependencies there. It's only python-nova deps
> there.
>>
>> A DSL does not solve this problem unless the DSL contains every dependency
>> to install (from binary).  I don't see this as maintainable.
>
> Agree being to detailed within the DSL can make the maintenance a
> nightmare. I was thinking about some build automation which can
> extract
> dependencies (ie: repoquery --requires python-nova) and put each one
> into a separate layer. We will just need a basic DSL with same
> complexity as we have now in Dockerfiles which will be building
> Dockerfiles dynamically.
>
> Other approach could be setting a dedicated image for each of the
> dependency and bind them together into the single image during build.
>
> I'm also having Alpine linux in mind, this together with bazel can
> make images really small.
>>
>> Just as a conclusion, deploying each dependency in a separate layer is an
>> absolutely terrible idea.  Docker performance atleast is negatively
>> affected by large layer counts, and aufs has a limit of 42 layers, so your
>> idea is not viable asp resented.
>
> This limit was 127 back in 2013.

Hard limit, but it stops working properly before. Around 40-50 layers.
We need to be careful about our layering. Even 127 layers is not
enough if you'd want to install every single dependency as a new
layer. RKT with it's image squashing might help, but we don't run RKT
(yet).

As for Alpine linux goes, how exactly would you install things like
galera (we don't really need galera for k8s, but we do for ansible and
we will not kill ansible.)? Rabbitmq? Ceph? Stuff that are not from
pip?

We need reliable repos that are well maintained and publicly
available, can you provide that for Alpine? Centos community /
Canonical have dedicated people to package stuff and they still
struggle (and do amazing job, thanks guys!), can Alpine community
provide us same level of maintenance?

Galera https://bugs.alpinelinux.org/issues/4646 is not available
Ceph https://bugs.alpinelinux.org/issues/4646 is not available (not even librbd)

That was 5 minutes of research.

Bottom line, we can't deploy Alpine because we don't have packages. We
can't create our own repo for it because we don't have hardware nor
human resources to support it, this is big job.

Having thin images is a noble goal and we all want to do it, we
appreciate any input/help, but as you see there are good (I think)
reasons why we did what we did.

Cheers,
Michal

> --
> Tomasz Paszkowski
> SS7, Asterisk, SAN, Datacenter, Cloud Computing
> +48500166299
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Dhvanan Shah]

Hi,

Problem resolved.

curl 10.16.37.221:5000 returned access denied. So I added a no proxy for
the host ip in the browser after which it began returning the JSON data.
After this I exported the same in my keystone_adminrc file as Chinmaya
pointed out. That solved the problem and it no longer gives the forbidden
error.

But the funny thing here is that I have had this setup running for quite
some time now and I have not added a no_proxy for the host ip and I also
haven't faced this issue before. So I am not sure what triggered this error
here now.

Thanks a lot for your inputs.

On Wed, Apr 27, 2016 at 5:30 PM, Dolph Mathews 
wrote:

>
> On Wed, Apr 27, 2016 at 6:53 AM, Dhvanan Shah  wrote:
>
>> Hi,
>>
>> Enabling the debug flag didn't give any additional information.
>>
>> 2 node Cluster means that I have one controller that also runs the
>> compute and an additional compute node, thus 2 node OpenStack Cluster.
>>
>> The problem here is not with the password as I am able to log in through
>> the dashboard. Any action performed gives a Forbidden error and
>> authorization failed for keystone.
>>
>> Any other things that I could look at?
>>
>
> Another long shot, but you might have an unintended surprise in your
> environment.
>
>   $ env | grep ^OS_
>
> More likely though, I'm guessing you don't actually have the "admin" role
> on the "admin" tenant that you're expecting. The 403 is indicating that you
> are authenticated successfully (your password is correct), but you don't
> have authorization to make the request (listing users, for example). You'd
> be able to login to horizon and spin up a VM, or do the same from the CLI,
> but not make the requests you're using to exercise the cloud admin role.
>
>
>> On Wed, Apr 27, 2016 at 4:55 PM, Dolph Mathews 
>> wrote:
>>
>>> Depending on which release of keystone you're running, try enabling
>>> either insecure_debug (more recent releases) or debug (older releases) to
>>> true in keystone.conf to get more detailed error messages from keystone.
>>>
>>>
>>> https://github.com/openstack/keystone/blob/3c4fe622ac5da00b04ccc8bc4e207a2e9ab0f863/etc/keystone.conf.sample#L87-L91
>>>
>>> That said, your configuration looks entirely correct to me, so I'm
>>> curious what the outcome is here. The only other red flag I see is that you
>>> mentioned a "2 node OpenStack cluster", and I'm not sure what that means in
>>> this context, exactly. How are the 2 nodes utilized?
>>>
>>> On Wed, Apr 27, 2016 at 5:43 AM, Dhvanan Shah  wrote:
>>>
 keystone --debug user-list gives this:

 /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
 DeprecationWarning: The keystone CLI is deprecated in favor of
 python-openstackclient. For a Python library, continue using
 python-keystoneclient.
   'python-keystoneclient.', DeprecationWarning)
 DEBUG:keystoneclient.auth.identity.v2:Making authentication request to
 http://10.16.37.221:5000/v2.0/tokens
 INFO:requests.packages.urllib3.connectionpool:Starting new HTTP
 connection (1): proxy.serc.iisc.ernet.in
 DEBUG:requests.packages.urllib3.connectionpool:"POST
 http://10.16.37.221:5000/v2.0/tokens HTTP/1.1" 403 3370
 DEBUG:keystoneclient.session:Request returned failure status: 403
 Authorization Failed: Forbidden (HTTP 403)

 nova --debug user list gives this:

 DEBUG (session:195) REQ: curl -g -i -X GET
 http://10.16.37.221:5000/v2.0 -H "Accept: application/json" -H
 "User-Agent: python-keystoneclient"
 INFO (connectionpool:203) Starting new HTTP connection (1):
 proxy.serc.iisc.ernet.in
 DEBUG (connectionpool:383) "GET http://10.16.37.221:5000/v2.0
 HTTP/1.1" 403 3275
 DEBUG (session:224) RESP:
 DEBUG (session:396) Request returned failure status: 403
 WARNING (base:133) Discovering versions from the identity service
 failed when creating the password plugin. Attempting to determine version
 from URL.
 DEBUG (v2:76) Making authentication request to
 http://10.16.37.221:5000/v2.0/tokens
 DEBUG (connectionpool:383) "POST http://10.16.37.221:5000/v2.0/tokens
 HTTP/1.1" 403 3370
 DEBUG (session:396) Request returned failure status: 403
 DEBUG (shell:914) Forbidden (HTTP 403)
 Forbidden: Forbidden (HTTP 403)
 ERROR (Forbidden): Forbidden (HTTP 403)



 On Wed, Apr 27, 2016 at 3:12 PM, Dhvanan Shah 
 wrote:

> On running openstack-status this is what I get (all the services are
> running, so not included that here)
>
> == Keystone users ==
> /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
> DeprecationWarning: The keystone CLI is deprecated in favor of
> python-openstackclient. For a Python library, continue using
> python-keystoneclient.
>   'python-keystoneclient.', DeprecationWarning)
> Authorization 

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Dolph Mathews]

On Wed, Apr 27, 2016 at 6:53 AM, Dhvanan Shah  wrote:

> Hi,
>
> Enabling the debug flag didn't give any additional information.
>
> 2 node Cluster means that I have one controller that also runs the compute
> and an additional compute node, thus 2 node OpenStack Cluster.
>
> The problem here is not with the password as I am able to log in through
> the dashboard. Any action performed gives a Forbidden error and
> authorization failed for keystone.
>
> Any other things that I could look at?
>

Another long shot, but you might have an unintended surprise in your
environment.

  $ env | grep ^OS_

More likely though, I'm guessing you don't actually have the "admin" role
on the "admin" tenant that you're expecting. The 403 is indicating that you
are authenticated successfully (your password is correct), but you don't
have authorization to make the request (listing users, for example). You'd
be able to login to horizon and spin up a VM, or do the same from the CLI,
but not make the requests you're using to exercise the cloud admin role.


> On Wed, Apr 27, 2016 at 4:55 PM, Dolph Mathews 
> wrote:
>
>> Depending on which release of keystone you're running, try enabling
>> either insecure_debug (more recent releases) or debug (older releases) to
>> true in keystone.conf to get more detailed error messages from keystone.
>>
>>
>> https://github.com/openstack/keystone/blob/3c4fe622ac5da00b04ccc8bc4e207a2e9ab0f863/etc/keystone.conf.sample#L87-L91
>>
>> That said, your configuration looks entirely correct to me, so I'm
>> curious what the outcome is here. The only other red flag I see is that you
>> mentioned a "2 node OpenStack cluster", and I'm not sure what that means in
>> this context, exactly. How are the 2 nodes utilized?
>>
>> On Wed, Apr 27, 2016 at 5:43 AM, Dhvanan Shah  wrote:
>>
>>> keystone --debug user-list gives this:
>>>
>>> /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
>>> DeprecationWarning: The keystone CLI is deprecated in favor of
>>> python-openstackclient. For a Python library, continue using
>>> python-keystoneclient.
>>>   'python-keystoneclient.', DeprecationWarning)
>>> DEBUG:keystoneclient.auth.identity.v2:Making authentication request to
>>> http://10.16.37.221:5000/v2.0/tokens
>>> INFO:requests.packages.urllib3.connectionpool:Starting new HTTP
>>> connection (1): proxy.serc.iisc.ernet.in
>>> DEBUG:requests.packages.urllib3.connectionpool:"POST
>>> http://10.16.37.221:5000/v2.0/tokens HTTP/1.1" 403 3370
>>> DEBUG:keystoneclient.session:Request returned failure status: 403
>>> Authorization Failed: Forbidden (HTTP 403)
>>>
>>> nova --debug user list gives this:
>>>
>>> DEBUG (session:195) REQ: curl -g -i -X GET http://10.16.37.221:5000/v2.0
>>> -H "Accept: application/json" -H "User-Agent: python-keystoneclient"
>>> INFO (connectionpool:203) Starting new HTTP connection (1):
>>> proxy.serc.iisc.ernet.in
>>> DEBUG (connectionpool:383) "GET http://10.16.37.221:5000/v2.0 HTTP/1.1"
>>> 403 3275
>>> DEBUG (session:224) RESP:
>>> DEBUG (session:396) Request returned failure status: 403
>>> WARNING (base:133) Discovering versions from the identity service failed
>>> when creating the password plugin. Attempting to determine version from URL.
>>> DEBUG (v2:76) Making authentication request to
>>> http://10.16.37.221:5000/v2.0/tokens
>>> DEBUG (connectionpool:383) "POST http://10.16.37.221:5000/v2.0/tokens
>>> HTTP/1.1" 403 3370
>>> DEBUG (session:396) Request returned failure status: 403
>>> DEBUG (shell:914) Forbidden (HTTP 403)
>>> Forbidden: Forbidden (HTTP 403)
>>> ERROR (Forbidden): Forbidden (HTTP 403)
>>>
>>>
>>>
>>> On Wed, Apr 27, 2016 at 3:12 PM, Dhvanan Shah  wrote:
>>>
 On running openstack-status this is what I get (all the services are
 running, so not included that here)

 == Keystone users ==
 /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
 DeprecationWarning: The keystone CLI is deprecated in favor of
 python-openstackclient. For a Python library, continue using
 python-keystoneclient.
   'python-keystoneclient.', DeprecationWarning)
 Authorization Failed: Forbidden (HTTP 403)
 == Glance images ==
 Forbidden (HTTP 403)
 == Nova managed services ==
 No handlers could be found for logger
 "keystoneclient.auth.identity.generic.base"
 ERROR (Forbidden): Forbidden (HTTP 403)
 == Nova networks ==
 No handlers could be found for logger
 "keystoneclient.auth.identity.generic.base"
 ERROR (Forbidden): Forbidden (HTTP 403)
 == Nova instance flavors ==
 No handlers could be found for logger
 "keystoneclient.auth.identity.generic.base"
 ERROR (Forbidden): Forbidden (HTTP 403)
 == Nova instances ==
 No handlers could be found for logger
 "keystoneclient.auth.identity.generic.base"
 ERROR (Forbidden): Forbidden (HTTP 403)


 On Wed, Apr 27, 2016 at 3:09 PM, 

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Chinmaya Bharadwaj]

Hi,

Looks like its connecting to proxy first,

Starting new HTTP connection (1): proxy.serc.iisc.ernet.in



​Try
export no_proxy= ​

#Chinmaya

On 27 April 2016 at 17:23, Dhvanan Shah  wrote:

> Hi,
>
> Enabling the debug flag didn't give any additional information.
>
> 2 node Cluster means that I have one controller that also runs the compute
> and an additional compute node, thus 2 node OpenStack Cluster.
>
> The problem here is not with the password as I am able to log in through
> the dashboard. Any action performed gives a Forbidden error and
> authorization failed for keystone.
>
> Any other things that I could look at?
>
> On Wed, Apr 27, 2016 at 4:55 PM, Dolph Mathews 
> wrote:
>
>> Depending on which release of keystone you're running, try enabling
>> either insecure_debug (more recent releases) or debug (older releases) to
>> true in keystone.conf to get more detailed error messages from keystone.
>>
>>
>> https://github.com/openstack/keystone/blob/3c4fe622ac5da00b04ccc8bc4e207a2e9ab0f863/etc/keystone.conf.sample#L87-L91
>>
>> That said, your configuration looks entirely correct to me, so I'm
>> curious what the outcome is here. The only other red flag I see is that you
>> mentioned a "2 node OpenStack cluster", and I'm not sure what that means in
>> this context, exactly. How are the 2 nodes utilized?
>>
>> On Wed, Apr 27, 2016 at 5:43 AM, Dhvanan Shah  wrote:
>>
>>> keystone --debug user-list gives this:
>>>
>>> /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
>>> DeprecationWarning: The keystone CLI is deprecated in favor of
>>> python-openstackclient. For a Python library, continue using
>>> python-keystoneclient.
>>>   'python-keystoneclient.', DeprecationWarning)
>>> DEBUG:keystoneclient.auth.identity.v2:Making authentication request to
>>> http://10.16.37.221:5000/v2.0/tokens
>>> INFO:requests.packages.urllib3.connectionpool:Starting new HTTP
>>> connection (1): proxy.serc.iisc.ernet.in
>>> DEBUG:requests.packages.urllib3.connectionpool:"POST
>>> http://10.16.37.221:5000/v2.0/tokens HTTP/1.1" 403 3370
>>> DEBUG:keystoneclient.session:Request returned failure status: 403
>>> Authorization Failed: Forbidden (HTTP 403)
>>>
>>> nova --debug user list gives this:
>>>
>>> DEBUG (session:195) REQ: curl -g -i -X GET http://10.16.37.221:5000/v2.0
>>> -H "Accept: application/json" -H "User-Agent: python-keystoneclient"
>>> INFO (connectionpool:203) Starting new HTTP connection (1):
>>> proxy.serc.iisc.ernet.in
>>> DEBUG (connectionpool:383) "GET http://10.16.37.221:5000/v2.0 HTTP/1.1"
>>> 403 3275
>>> DEBUG (session:224) RESP:
>>> DEBUG (session:396) Request returned failure status: 403
>>> WARNING (base:133) Discovering versions from the identity service failed
>>> when creating the password plugin. Attempting to determine version from URL.
>>> DEBUG (v2:76) Making authentication request to
>>> http://10.16.37.221:5000/v2.0/tokens
>>> DEBUG (connectionpool:383) "POST http://10.16.37.221:5000/v2.0/tokens
>>> HTTP/1.1" 403 3370
>>> DEBUG (session:396) Request returned failure status: 403
>>> DEBUG (shell:914) Forbidden (HTTP 403)
>>> Forbidden: Forbidden (HTTP 403)
>>> ERROR (Forbidden): Forbidden (HTTP 403)
>>>
>>>
>>>
>>> On Wed, Apr 27, 2016 at 3:12 PM, Dhvanan Shah  wrote:
>>>
 On running openstack-status this is what I get (all the services are
 running, so not included that here)

 == Keystone users ==
 /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
 DeprecationWarning: The keystone CLI is deprecated in favor of
 python-openstackclient. For a Python library, continue using
 python-keystoneclient.
   'python-keystoneclient.', DeprecationWarning)
 Authorization Failed: Forbidden (HTTP 403)
 == Glance images ==
 Forbidden (HTTP 403)
 == Nova managed services ==
 No handlers could be found for logger
 "keystoneclient.auth.identity.generic.base"
 ERROR (Forbidden): Forbidden (HTTP 403)
 == Nova networks ==
 No handlers could be found for logger
 "keystoneclient.auth.identity.generic.base"
 ERROR (Forbidden): Forbidden (HTTP 403)
 == Nova instance flavors ==
 No handlers could be found for logger
 "keystoneclient.auth.identity.generic.base"
 ERROR (Forbidden): Forbidden (HTTP 403)
 == Nova instances ==
 No handlers could be found for logger
 "keystoneclient.auth.identity.generic.base"
 ERROR (Forbidden): Forbidden (HTTP 403)


 On Wed, Apr 27, 2016 at 3:09 PM, Dhvanan Shah 
 wrote:

> Hi Jens,
>
> The password is correct when I echo $OS_PASSWORD.
> I downloaded the admin-openrc.sh file from the dashboard and sourced.
> I ran a nova list after that:
> No handlers could be found for logger
> "keystoneclient.auth.identity.generic.base"
> ERROR (Forbidden): Forbidden (HTTP 403)
>
> It still gives the error 

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Jens Rosenboom]

2016-04-27 12:43 GMT+02:00 Dhvanan Shah :
> keystone --debug user-list gives this:
>
> /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
> DeprecationWarning: The keystone CLI is deprecated in favor of
> python-openstackclient. For a Python library, continue using
> python-keystoneclient.
>   'python-keystoneclient.', DeprecationWarning)
> DEBUG:keystoneclient.auth.identity.v2:Making authentication request to
> http://10.16.37.221:5000/v2.0/tokens
> INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection
> (1): proxy.serc.iisc.ernet.in

After taking another look, this line looks suspicous, where does this
proxy get configured? It seems like it might be blocking access to
your keystone service. What is the output if you do a "curl
http://10.16.37.221:5000/v2.0;?

> DEBUG:requests.packages.urllib3.connectionpool:"POST
> http://10.16.37.221:5000/v2.0/tokens HTTP/1.1" 403 3370
> DEBUG:keystoneclient.session:Request returned failure status: 403
> Authorization Failed: Forbidden (HTTP 403)
>
> nova --debug user list gives this:
>
> DEBUG (session:195) REQ: curl -g -i -X GET http://10.16.37.221:5000/v2.0 -H
> "Accept: application/json" -H "User-Agent: python-keystoneclient"
> INFO (connectionpool:203) Starting new HTTP connection (1):
> proxy.serc.iisc.ernet.in
> DEBUG (connectionpool:383) "GET http://10.16.37.221:5000/v2.0 HTTP/1.1" 403
> 3275
> DEBUG (session:224) RESP:
> DEBUG (session:396) Request returned failure status: 403
> WARNING (base:133) Discovering versions from the identity service failed
> when creating the password plugin. Attempting to determine version from URL.
> DEBUG (v2:76) Making authentication request to
> http://10.16.37.221:5000/v2.0/tokens
> DEBUG (connectionpool:383) "POST http://10.16.37.221:5000/v2.0/tokens
> HTTP/1.1" 403 3370
> DEBUG (session:396) Request returned failure status: 403
> DEBUG (shell:914) Forbidden (HTTP 403)
> Forbidden: Forbidden (HTTP 403)
> ERROR (Forbidden): Forbidden (HTTP 403)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Dhvanan Shah]

Hi,

Enabling the debug flag didn't give any additional information.

2 node Cluster means that I have one controller that also runs the compute
and an additional compute node, thus 2 node OpenStack Cluster.

The problem here is not with the password as I am able to log in through
the dashboard. Any action performed gives a Forbidden error and
authorization failed for keystone.

Any other things that I could look at?

On Wed, Apr 27, 2016 at 4:55 PM, Dolph Mathews 
wrote:

> Depending on which release of keystone you're running, try enabling either
> insecure_debug (more recent releases) or debug (older releases) to true in
> keystone.conf to get more detailed error messages from keystone.
>
>
> https://github.com/openstack/keystone/blob/3c4fe622ac5da00b04ccc8bc4e207a2e9ab0f863/etc/keystone.conf.sample#L87-L91
>
> That said, your configuration looks entirely correct to me, so I'm curious
> what the outcome is here. The only other red flag I see is that you
> mentioned a "2 node OpenStack cluster", and I'm not sure what that means in
> this context, exactly. How are the 2 nodes utilized?
>
> On Wed, Apr 27, 2016 at 5:43 AM, Dhvanan Shah  wrote:
>
>> keystone --debug user-list gives this:
>>
>> /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
>> DeprecationWarning: The keystone CLI is deprecated in favor of
>> python-openstackclient. For a Python library, continue using
>> python-keystoneclient.
>>   'python-keystoneclient.', DeprecationWarning)
>> DEBUG:keystoneclient.auth.identity.v2:Making authentication request to
>> http://10.16.37.221:5000/v2.0/tokens
>> INFO:requests.packages.urllib3.connectionpool:Starting new HTTP
>> connection (1): proxy.serc.iisc.ernet.in
>> DEBUG:requests.packages.urllib3.connectionpool:"POST
>> http://10.16.37.221:5000/v2.0/tokens HTTP/1.1" 403 3370
>> DEBUG:keystoneclient.session:Request returned failure status: 403
>> Authorization Failed: Forbidden (HTTP 403)
>>
>> nova --debug user list gives this:
>>
>> DEBUG (session:195) REQ: curl -g -i -X GET http://10.16.37.221:5000/v2.0
>> -H "Accept: application/json" -H "User-Agent: python-keystoneclient"
>> INFO (connectionpool:203) Starting new HTTP connection (1):
>> proxy.serc.iisc.ernet.in
>> DEBUG (connectionpool:383) "GET http://10.16.37.221:5000/v2.0 HTTP/1.1"
>> 403 3275
>> DEBUG (session:224) RESP:
>> DEBUG (session:396) Request returned failure status: 403
>> WARNING (base:133) Discovering versions from the identity service failed
>> when creating the password plugin. Attempting to determine version from URL.
>> DEBUG (v2:76) Making authentication request to
>> http://10.16.37.221:5000/v2.0/tokens
>> DEBUG (connectionpool:383) "POST http://10.16.37.221:5000/v2.0/tokens
>> HTTP/1.1" 403 3370
>> DEBUG (session:396) Request returned failure status: 403
>> DEBUG (shell:914) Forbidden (HTTP 403)
>> Forbidden: Forbidden (HTTP 403)
>> ERROR (Forbidden): Forbidden (HTTP 403)
>>
>>
>>
>> On Wed, Apr 27, 2016 at 3:12 PM, Dhvanan Shah  wrote:
>>
>>> On running openstack-status this is what I get (all the services are
>>> running, so not included that here)
>>>
>>> == Keystone users ==
>>> /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
>>> DeprecationWarning: The keystone CLI is deprecated in favor of
>>> python-openstackclient. For a Python library, continue using
>>> python-keystoneclient.
>>>   'python-keystoneclient.', DeprecationWarning)
>>> Authorization Failed: Forbidden (HTTP 403)
>>> == Glance images ==
>>> Forbidden (HTTP 403)
>>> == Nova managed services ==
>>> No handlers could be found for logger
>>> "keystoneclient.auth.identity.generic.base"
>>> ERROR (Forbidden): Forbidden (HTTP 403)
>>> == Nova networks ==
>>> No handlers could be found for logger
>>> "keystoneclient.auth.identity.generic.base"
>>> ERROR (Forbidden): Forbidden (HTTP 403)
>>> == Nova instance flavors ==
>>> No handlers could be found for logger
>>> "keystoneclient.auth.identity.generic.base"
>>> ERROR (Forbidden): Forbidden (HTTP 403)
>>> == Nova instances ==
>>> No handlers could be found for logger
>>> "keystoneclient.auth.identity.generic.base"
>>> ERROR (Forbidden): Forbidden (HTTP 403)
>>>
>>>
>>> On Wed, Apr 27, 2016 at 3:09 PM, Dhvanan Shah  wrote:
>>>
 Hi Jens,

 The password is correct when I echo $OS_PASSWORD.
 I downloaded the admin-openrc.sh file from the dashboard and sourced. I
 ran a nova list after that:
 No handlers could be found for logger
 "keystoneclient.auth.identity.generic.base"
 ERROR (Forbidden): Forbidden (HTTP 403)

 It still gives the error of forbidden access.
 I think the password is not the issue. Forbidden access might be
 something else. Do you want me to share anything else?

 On Wed, Apr 27, 2016 at 2:56 PM, Jens Rosenboom 
 wrote:

> 2016-04-27 10:30 GMT+02:00 Dhvanan Shah :
> > UPDATE:
> > I 

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Dolph Mathews]

Depending on which release of keystone you're running, try enabling either
insecure_debug (more recent releases) or debug (older releases) to true in
keystone.conf to get more detailed error messages from keystone.

https://github.com/openstack/keystone/blob/3c4fe622ac5da00b04ccc8bc4e207a2e9ab0f863/etc/keystone.conf.sample#L87-L91

That said, your configuration looks entirely correct to me, so I'm curious
what the outcome is here. The only other red flag I see is that you
mentioned a "2 node OpenStack cluster", and I'm not sure what that means in
this context, exactly. How are the 2 nodes utilized?

On Wed, Apr 27, 2016 at 5:43 AM, Dhvanan Shah  wrote:

> keystone --debug user-list gives this:
>
> /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
> DeprecationWarning: The keystone CLI is deprecated in favor of
> python-openstackclient. For a Python library, continue using
> python-keystoneclient.
>   'python-keystoneclient.', DeprecationWarning)
> DEBUG:keystoneclient.auth.identity.v2:Making authentication request to
> http://10.16.37.221:5000/v2.0/tokens
> INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection
> (1): proxy.serc.iisc.ernet.in
> DEBUG:requests.packages.urllib3.connectionpool:"POST
> http://10.16.37.221:5000/v2.0/tokens HTTP/1.1" 403 3370
> DEBUG:keystoneclient.session:Request returned failure status: 403
> Authorization Failed: Forbidden (HTTP 403)
>
> nova --debug user list gives this:
>
> DEBUG (session:195) REQ: curl -g -i -X GET http://10.16.37.221:5000/v2.0
> -H "Accept: application/json" -H "User-Agent: python-keystoneclient"
> INFO (connectionpool:203) Starting new HTTP connection (1):
> proxy.serc.iisc.ernet.in
> DEBUG (connectionpool:383) "GET http://10.16.37.221:5000/v2.0 HTTP/1.1"
> 403 3275
> DEBUG (session:224) RESP:
> DEBUG (session:396) Request returned failure status: 403
> WARNING (base:133) Discovering versions from the identity service failed
> when creating the password plugin. Attempting to determine version from URL.
> DEBUG (v2:76) Making authentication request to
> http://10.16.37.221:5000/v2.0/tokens
> DEBUG (connectionpool:383) "POST http://10.16.37.221:5000/v2.0/tokens
> HTTP/1.1" 403 3370
> DEBUG (session:396) Request returned failure status: 403
> DEBUG (shell:914) Forbidden (HTTP 403)
> Forbidden: Forbidden (HTTP 403)
> ERROR (Forbidden): Forbidden (HTTP 403)
>
>
>
> On Wed, Apr 27, 2016 at 3:12 PM, Dhvanan Shah  wrote:
>
>> On running openstack-status this is what I get (all the services are
>> running, so not included that here)
>>
>> == Keystone users ==
>> /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
>> DeprecationWarning: The keystone CLI is deprecated in favor of
>> python-openstackclient. For a Python library, continue using
>> python-keystoneclient.
>>   'python-keystoneclient.', DeprecationWarning)
>> Authorization Failed: Forbidden (HTTP 403)
>> == Glance images ==
>> Forbidden (HTTP 403)
>> == Nova managed services ==
>> No handlers could be found for logger
>> "keystoneclient.auth.identity.generic.base"
>> ERROR (Forbidden): Forbidden (HTTP 403)
>> == Nova networks ==
>> No handlers could be found for logger
>> "keystoneclient.auth.identity.generic.base"
>> ERROR (Forbidden): Forbidden (HTTP 403)
>> == Nova instance flavors ==
>> No handlers could be found for logger
>> "keystoneclient.auth.identity.generic.base"
>> ERROR (Forbidden): Forbidden (HTTP 403)
>> == Nova instances ==
>> No handlers could be found for logger
>> "keystoneclient.auth.identity.generic.base"
>> ERROR (Forbidden): Forbidden (HTTP 403)
>>
>>
>> On Wed, Apr 27, 2016 at 3:09 PM, Dhvanan Shah  wrote:
>>
>>> Hi Jens,
>>>
>>> The password is correct when I echo $OS_PASSWORD.
>>> I downloaded the admin-openrc.sh file from the dashboard and sourced. I
>>> ran a nova list after that:
>>> No handlers could be found for logger
>>> "keystoneclient.auth.identity.generic.base"
>>> ERROR (Forbidden): Forbidden (HTTP 403)
>>>
>>> It still gives the error of forbidden access.
>>> I think the password is not the issue. Forbidden access might be
>>> something else. Do you want me to share anything else?
>>>
>>> On Wed, Apr 27, 2016 at 2:56 PM, Jens Rosenboom 
>>> wrote:
>>>
 2016-04-27 10:30 GMT+02:00 Dhvanan Shah :
 > UPDATE:
 > I am able to log into Horizon and perform all actions without any
 issue but
 > on my terminal, I am not able to do the same. The password that I
 thought
 > was wrong is not the issue as I logged in with the same password.
 > My keystone_adminrc file looks like this:
 >
 > unset OS_SERVICE_TOKEN OS_SERVICE_ENDPOINT
 > export OS_USERNAME=admin
 > export OS_PASSWORD=
 > export OS_AUTH_URL=http://10.16.37.221:35357/v2.0
 > export PS1='[\u@\h \W(keystone_admin)]\$ '
 >
 > export OS_TENANT_NAME=admin
 > export OS_REGION_NAME=RegionOne
 >
 >

Re: [openstack-dev] KVM Forum 2016: Call For Participation

[Daniel P. Berrange]

This is just a followup to remind people that the KVM Forum
CFP deadline of May 1st is rapidly approaching.

All the CFP information is here:

  http://events.linuxfoundation.org/events/kvm-forum/program/cfp

Regards,
Daniel (on behalf of the KVM Forum 2016 Program Committee)

On Thu, Mar 10, 2016 at 06:19:36PM +, Daniel P. Berrange wrote:
> =
> KVM Forum 2016: Call For Participation
> August 24-26, 2016 - Westin Harbor Castle - Toronto, Canada
> 
> (All submissions must be received before midnight May 1, 2016)
> =
> 
> KVM Forum is an annual event that presents a rare opportunity
> for developers and users to meet, discuss the state of Linux
> virtualization technology, and plan for the challenges ahead. 
> We invite you to lead part of the discussion by submitting a speaking
> proposal for KVM Forum 2016.
> 
> At this highly technical conference, developers driving innovation
> in the KVM virtualization stack (Linux, KVM, QEMU, libvirt) can
> meet users who depend on KVM as part of their offerings, or to
> power their data centers and clouds.
> 
> KVM Forum will include sessions on the state of the KVM
> virtualization stack, planning for the future, and many
> opportunities for attendees to collaborate. As we celebrate ten years
> of KVM development in the Linux kernel, KVM continues to be a
> critical part of the FOSS cloud infrastructure.
> 
> This year, KVM Forum is joining LinuxCon and ContainerCon in Toronto, 
> Canada. Selected talks from KVM Forum will be presented on Wednesday
> August 24 to the full audience of LinuxCon and ContainerCon. Also,
> attendees of KVM Forum will have access to all of the LinuxCon and
> ContainerCon talks on Wednesday.
> 
> http://events.linuxfoundation.org/cfp
> 
> Suggested topics:
> 
> KVM and Linux
> * Scaling and optimizations
> * Nested virtualization
> * Linux kernel performance improvements
> * Resource management (CPU, I/O, memory)
> * Hardening and security
> * VFIO: SR-IOV, GPU, platform device assignment
> * Architecture ports
> 
> QEMU
> * Management interfaces: QOM and QMP
> * New devices, new boards, new architectures
> * Scaling and optimizations
> * Desktop virtualization and SPICE
> * Virtual GPU
> * virtio and vhost, including non-Linux or non-virtualized uses
> * Hardening and security
> * New storage features
> * Live migration and fault tolerance
> * High availability and continuous backup
> * Real-time guest support
> * Emulation and TCG
> * Firmware: ACPI, UEFI, coreboot, u-Boot, etc.
> * Testing
> 
> Management and infrastructure
> * Managing KVM: Libvirt, OpenStack, oVirt, etc.
> * Storage: glusterfs, Ceph, etc.
> * Software defined networking: Open vSwitch, OpenDaylight, etc.
> * Network Function Virtualization
> * Security
> * Provisioning
> * Performance tuning
> 
> 
> ===
> SUBMITTING YOUR PROPOSAL
> ===
> Abstracts due: May 1, 2016
> 
> Please submit a short abstract (~150 words) describing your presentation
> proposal. Slots vary in length up to 45 minutes. Also include the proposal
> type -- one of:
> - technical talk
> - end-user talk
> 
> Submit your proposal here:
> http://events.linuxfoundation.org/cfp
> Please only use the categories "presentation" and "panel discussion"
> 
> You will receive a notification whether or not your presentation proposal
> was accepted by May 27, 2016.
> 
> Speakers will receive a complimentary pass for the event. In the instance
> that your submission has multiple presenters, only the primary speaker for a
> proposal will receive a complementary event pass. For panel discussions, all
> panelists will receive a complimentary event pass.
> 
> TECHNICAL TALKS
> 
> A good technical talk should not just report on what has happened over
> the last year; it should present a concrete problem and how it impacts
> the user and/or developer community. Whenever applicable, focus on
> work that needs to be done, difficulties that haven't yet been solved,
> and on decisions that other developers should be aware of. Summarizing
> recent developments is okay but it should not be more than a small
> portion of the overall talk.
> 
> END-USER TALKS
> 
> One of the big challenges as developers is to know what, where and how
> people actually use our software. We will reserve a few slots for end
> users talking about their deployment challenges and achievements.
> 
> If you are using KVM in production you are encouraged submit a speaking
> proposal. Simply mark it as an end-user talk. As an end user, this is a
> unique opportunity to get your input to developers.
> 
> HANDS-ON / BOF SESSIONS
> 
> We will reserve some time for people to get together and discuss
> strategic decisions as well as other topics that are best solved within
> smaller groups.
> 
> These sessions will be announced during the event. If you are interested
> in organizing such a session, please 

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Dhvanan Shah]

keystone --debug user-list gives this:

/usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
DeprecationWarning: The keystone CLI is deprecated in favor of
python-openstackclient. For a Python library, continue using
python-keystoneclient.
  'python-keystoneclient.', DeprecationWarning)
DEBUG:keystoneclient.auth.identity.v2:Making authentication request to
http://10.16.37.221:5000/v2.0/tokens
INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection
(1): proxy.serc.iisc.ernet.in
DEBUG:requests.packages.urllib3.connectionpool:"POST
http://10.16.37.221:5000/v2.0/tokens HTTP/1.1" 403 3370
DEBUG:keystoneclient.session:Request returned failure status: 403
Authorization Failed: Forbidden (HTTP 403)

nova --debug user list gives this:

DEBUG (session:195) REQ: curl -g -i -X GET http://10.16.37.221:5000/v2.0 -H
"Accept: application/json" -H "User-Agent: python-keystoneclient"
INFO (connectionpool:203) Starting new HTTP connection (1):
proxy.serc.iisc.ernet.in
DEBUG (connectionpool:383) "GET http://10.16.37.221:5000/v2.0 HTTP/1.1" 403
3275
DEBUG (session:224) RESP:
DEBUG (session:396) Request returned failure status: 403
WARNING (base:133) Discovering versions from the identity service failed
when creating the password plugin. Attempting to determine version from URL.
DEBUG (v2:76) Making authentication request to
http://10.16.37.221:5000/v2.0/tokens
DEBUG (connectionpool:383) "POST http://10.16.37.221:5000/v2.0/tokens
HTTP/1.1" 403 3370
DEBUG (session:396) Request returned failure status: 403
DEBUG (shell:914) Forbidden (HTTP 403)
Forbidden: Forbidden (HTTP 403)
ERROR (Forbidden): Forbidden (HTTP 403)



On Wed, Apr 27, 2016 at 3:12 PM, Dhvanan Shah  wrote:

> On running openstack-status this is what I get (all the services are
> running, so not included that here)
>
> == Keystone users ==
> /usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
> DeprecationWarning: The keystone CLI is deprecated in favor of
> python-openstackclient. For a Python library, continue using
> python-keystoneclient.
>   'python-keystoneclient.', DeprecationWarning)
> Authorization Failed: Forbidden (HTTP 403)
> == Glance images ==
> Forbidden (HTTP 403)
> == Nova managed services ==
> No handlers could be found for logger
> "keystoneclient.auth.identity.generic.base"
> ERROR (Forbidden): Forbidden (HTTP 403)
> == Nova networks ==
> No handlers could be found for logger
> "keystoneclient.auth.identity.generic.base"
> ERROR (Forbidden): Forbidden (HTTP 403)
> == Nova instance flavors ==
> No handlers could be found for logger
> "keystoneclient.auth.identity.generic.base"
> ERROR (Forbidden): Forbidden (HTTP 403)
> == Nova instances ==
> No handlers could be found for logger
> "keystoneclient.auth.identity.generic.base"
> ERROR (Forbidden): Forbidden (HTTP 403)
>
>
> On Wed, Apr 27, 2016 at 3:09 PM, Dhvanan Shah  wrote:
>
>> Hi Jens,
>>
>> The password is correct when I echo $OS_PASSWORD.
>> I downloaded the admin-openrc.sh file from the dashboard and sourced. I
>> ran a nova list after that:
>> No handlers could be found for logger
>> "keystoneclient.auth.identity.generic.base"
>> ERROR (Forbidden): Forbidden (HTTP 403)
>>
>> It still gives the error of forbidden access.
>> I think the password is not the issue. Forbidden access might be
>> something else. Do you want me to share anything else?
>>
>> On Wed, Apr 27, 2016 at 2:56 PM, Jens Rosenboom 
>> wrote:
>>
>>> 2016-04-27 10:30 GMT+02:00 Dhvanan Shah :
>>> > UPDATE:
>>> > I am able to log into Horizon and perform all actions without any
>>> issue but
>>> > on my terminal, I am not able to do the same. The password that I
>>> thought
>>> > was wrong is not the issue as I logged in with the same password.
>>> > My keystone_adminrc file looks like this:
>>> >
>>> > unset OS_SERVICE_TOKEN OS_SERVICE_ENDPOINT
>>> > export OS_USERNAME=admin
>>> > export OS_PASSWORD=
>>> > export OS_AUTH_URL=http://10.16.37.221:35357/v2.0
>>> > export PS1='[\u@\h \W(keystone_admin)]\$ '
>>> >
>>> > export OS_TENANT_NAME=admin
>>> > export OS_REGION_NAME=RegionOne
>>> >
>>> >
>>> > Please suggest what I could do!
>>>
>>> Does your password contain special characters that might get mangled
>>> by the shell? You could compare the output of "echo $OS_PASSWORD" to
>>> verify.
>>>
>>> Otherwise, if the dashboard is working for you, you can go to
>>> Project/Compute/Access/API Access and use the "Download
>>> OpenStack RC File" link there.
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>>
>> --
>> Dhvanan Shah
>>
>
>
>
> --
> Dhvanan Shah
>



-- 
Dhvanan Shah

Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes

[Kai Qiang Wu]

Hi Mike,

Since right now, we have also support bay-update (node_count)

I am thinking the following case:

1>  baymodel-create have default flavor, and extra labels specify the(other
node flavors) requirements,

if (other node flavors) count <= bay(node_count), the extra nodes would be
created use default flavor

if (other node flavors) count  > bay(node_count), it should pop error,
since it not quite clear why flavor to use

2> magnum bay-update k8sbay replace node_count < existed node_count,  it
should be OK. same as old behavior
 if node_count > existed node_count, all new nodes would use default
flavor_id, (if not, we need to find what's the better policy to handle
that)

Refer:
https://github.com/openstack/magnum/blob/master/doc/source/dev/quickstart.rst





What do you think ?



Thanks


Best Wishes,

Kai Qiang Wu (吴开强  Kennan）
IBM China System and Technology Lab, Beijing

E-mail: wk...@cn.ibm.com
Tel: 86-10-82451647
Address: Building 28(Ring Building), ZhongGuanCun Software Park,
 No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China
100193

Follow your heart. You are miracle!



From:   "Ma, Wen-Tao (Mike, HP Servers-PSC-BJ)" 
To: "openstack-dev@lists.openstack.org"

Date:   27/04/2016 03:10 pm
Subject:Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to
provision minion nodes



Hi Hong bin,
Thanks very much. It’s good suggestion, I think it is a good way by using
labels for extra flavors. But I notice that there is not the �Cnode-count
parameter in baymodel.
So I think it doesn’t need specify minion-flavor-0 counts by �Cnode-count.
We can specify all of the flavor id and count ratio in the labels. It will
check the minion node count with this ratio of labels when creating magnum
bay that specified total minion node count . If the node-count in baycreate
doesn’t match with the flavor ratio, it will return the ratio match error
message.   If there is not the multi-flavor-ratio key in lables, it will
just use  minion-flavor-0  to create 10 minion nodes.
$ magnum baymodel-create --name k8sbaymodel --flavor-id minion-flavor-0
--labels multi-
flavor-ratio=minion-flavor-0:3,minions-flavor-1:5,minion-flavor-2:2
$  magnum bay-create --name k8sbay --baymodel k8sbaymodel --node-count 10
Do you think about it?

> -Original Message-
> From: Ma, Wen-Tao (Mike, HP Servers-PSC-BJ) [mailto:wentao...@hpe.com]
> Sent: April-26-16 3:01 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to
> provision minion nodes
>
> Hi Hongbin, Ricardo
> This is mike, I am working with Gary now.
> Thanks for Ricardo's good suggestion. I have tried the "map/index"
> method ,  we can use it to passed the minion_flavor_map and the index
> into the minion cluster stack. It does work well.
> I think we can update magnum baymodel-create to set the N minion
> flavors in the minion_flavor_map and assign minion counts for each
> flavor.
> For example :
> magnum baymodel-create --name k8s-bay-model  --flavor-id minion-flavor-
> 0:3,minion-flavor-1:5, minion-flavor-2:2. It will create 3 types flavor

The suggested approach seems to break the existing behaviour. I think it is
better to support this feature in a backward-compatible way. How about
using labels:

$ magnum baymodel-create --name k8sbaymodel --flavor-id minion-flavor-0
--node-count 3 --labels
extra-flavor-ids=minions-flavor-1:5,minion-flavor-2:2

> minion node and total minion nodes  count is 10. The magnum baymode.py
> will parse  this  dictionary and pass them to the heat template
> parameters minion_flavor_map, minion_flavor_count_map. Then the heat
> stack will work well.
>
> kubecluster-fedora-ironic.yaml
> parameters:
>   minion_flavor_map:
> type: json
> default:
>   '0': minion-flavor-0
>   '1': minion-flavor-1
>   '2': minion-flavor-2
>
>   minion_flavor_count_map:
> type: json
> default:
>   '0': 3
>   '1': 5
>   '2': 2
>
> resources:
> kube_minions_flavors:
> type: OS::Heat::ResourceGroup
> properties:
>   count: { get_param: minion_flavors_counts }
>   resource_def:
> type: kubecluster-minion-fedora-ironic.yaml
> properties:
>   minion_flavor_map: {get_param: minion_flavor_map}
>   minion_flavor_count_map: {get_param: minion_flavor_count_map}
>   minion_flavor_index: '%index%'
>
> How do you think about this interface in magnum baymodel to support N
> falvor to provision minion nodes? Do you have any comments about this
> design for this feature?
>
> Thanks && Regards
> Mike Ma
> HP Servers Core Platform Software China Email wentao...@hpe.com
>
> -Original Message-
> From: Duan, Li-Gong (Gary, HPServers-Core-OE-PSC)
> 

[openstack-dev] [horizon] How to paginate Data Table to display only 5 rows every page ?

[严超]

Hi, Everyone:
Is there a possible way to paginate DataTable to display only 5 rows
every page ?
I'm very grateful for reply.

*Best Regards！*


*Chao Yan--About me ： http://about.me/chao_yan
*

*My twitter： @yanchao727 *
*My Weibo： http://weibo.com/herewearenow *
*--*
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Dhvanan Shah]

On running openstack-status this is what I get (all the services are
running, so not included that here)

== Keystone users ==
/usr/lib/python2.7/site-packages/keystoneclient/shell.py:65:
DeprecationWarning: The keystone CLI is deprecated in favor of
python-openstackclient. For a Python library, continue using
python-keystoneclient.
  'python-keystoneclient.', DeprecationWarning)
Authorization Failed: Forbidden (HTTP 403)
== Glance images ==
Forbidden (HTTP 403)
== Nova managed services ==
No handlers could be found for logger
"keystoneclient.auth.identity.generic.base"
ERROR (Forbidden): Forbidden (HTTP 403)
== Nova networks ==
No handlers could be found for logger
"keystoneclient.auth.identity.generic.base"
ERROR (Forbidden): Forbidden (HTTP 403)
== Nova instance flavors ==
No handlers could be found for logger
"keystoneclient.auth.identity.generic.base"
ERROR (Forbidden): Forbidden (HTTP 403)
== Nova instances ==
No handlers could be found for logger
"keystoneclient.auth.identity.generic.base"
ERROR (Forbidden): Forbidden (HTTP 403)


On Wed, Apr 27, 2016 at 3:09 PM, Dhvanan Shah  wrote:

> Hi Jens,
>
> The password is correct when I echo $OS_PASSWORD.
> I downloaded the admin-openrc.sh file from the dashboard and sourced. I
> ran a nova list after that:
> No handlers could be found for logger
> "keystoneclient.auth.identity.generic.base"
> ERROR (Forbidden): Forbidden (HTTP 403)
>
> It still gives the error of forbidden access.
> I think the password is not the issue. Forbidden access might be something
> else. Do you want me to share anything else?
>
> On Wed, Apr 27, 2016 at 2:56 PM, Jens Rosenboom 
> wrote:
>
>> 2016-04-27 10:30 GMT+02:00 Dhvanan Shah :
>> > UPDATE:
>> > I am able to log into Horizon and perform all actions without any issue
>> but
>> > on my terminal, I am not able to do the same. The password that I
>> thought
>> > was wrong is not the issue as I logged in with the same password.
>> > My keystone_adminrc file looks like this:
>> >
>> > unset OS_SERVICE_TOKEN OS_SERVICE_ENDPOINT
>> > export OS_USERNAME=admin
>> > export OS_PASSWORD=
>> > export OS_AUTH_URL=http://10.16.37.221:35357/v2.0
>> > export PS1='[\u@\h \W(keystone_admin)]\$ '
>> >
>> > export OS_TENANT_NAME=admin
>> > export OS_REGION_NAME=RegionOne
>> >
>> >
>> > Please suggest what I could do!
>>
>> Does your password contain special characters that might get mangled
>> by the shell? You could compare the output of "echo $OS_PASSWORD" to
>> verify.
>>
>> Otherwise, if the dashboard is working for you, you can go to
>> Project/Compute/Access/API Access and use the "Download
>> OpenStack RC File" link there.
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> --
> Dhvanan Shah
>



-- 
Dhvanan Shah
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Dhvanan Shah]

Hi Jens,

The password is correct when I echo $OS_PASSWORD.
I downloaded the admin-openrc.sh file from the dashboard and sourced. I ran
a nova list after that:
No handlers could be found for logger
"keystoneclient.auth.identity.generic.base"
ERROR (Forbidden): Forbidden (HTTP 403)

It still gives the error of forbidden access.
I think the password is not the issue. Forbidden access might be something
else. Do you want me to share anything else?

On Wed, Apr 27, 2016 at 2:56 PM, Jens Rosenboom 
wrote:

> 2016-04-27 10:30 GMT+02:00 Dhvanan Shah :
> > UPDATE:
> > I am able to log into Horizon and perform all actions without any issue
> but
> > on my terminal, I am not able to do the same. The password that I thought
> > was wrong is not the issue as I logged in with the same password.
> > My keystone_adminrc file looks like this:
> >
> > unset OS_SERVICE_TOKEN OS_SERVICE_ENDPOINT
> > export OS_USERNAME=admin
> > export OS_PASSWORD=
> > export OS_AUTH_URL=http://10.16.37.221:35357/v2.0
> > export PS1='[\u@\h \W(keystone_admin)]\$ '
> >
> > export OS_TENANT_NAME=admin
> > export OS_REGION_NAME=RegionOne
> >
> >
> > Please suggest what I could do!
>
> Does your password contain special characters that might get mangled
> by the shell? You could compare the output of "echo $OS_PASSWORD" to
> verify.
>
> Otherwise, if the dashboard is working for you, you can go to
> Project/Compute/Access/API Access and use the "Download
> OpenStack RC File" link there.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Dhvanan Shah
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Fuel] Fuel 9.0 is released

[Roman Prykhodchenko]

Jeremy,

Thanks for checking! Probably that is missing in the the release checklist.

- romcheg
> 26 квіт. 2016 р. о 17:35 Jeremy Stanley  написав(ла):
> 
> On 2016-04-26 17:29:40 +0200 (+0200), Roman Prykhodchenko wrote:
>> I still don’t see python-fuelclient-9.0.0 on PyPi: 
>> https://pypi.python.org/pypi/python-fuelclient 
>> 
>> 
>> Shouldn’t someone investigate this?
> 
> It hasn't been tagged yet as far as I can tell (no 9.0.0 in the git
> repo for openstack/python-fuelclient).
> --
> Jeremy Stanley
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Jens Rosenboom]

2016-04-27 10:30 GMT+02:00 Dhvanan Shah :
> UPDATE:
> I am able to log into Horizon and perform all actions without any issue but
> on my terminal, I am not able to do the same. The password that I thought
> was wrong is not the issue as I logged in with the same password.
> My keystone_adminrc file looks like this:
>
> unset OS_SERVICE_TOKEN OS_SERVICE_ENDPOINT
> export OS_USERNAME=admin
> export OS_PASSWORD=
> export OS_AUTH_URL=http://10.16.37.221:35357/v2.0
> export PS1='[\u@\h \W(keystone_admin)]\$ '
>
> export OS_TENANT_NAME=admin
> export OS_REGION_NAME=RegionOne
>
>
> Please suggest what I could do!

Does your password contain special characters that might get mangled
by the shell? You could compare the output of "echo $OS_PASSWORD" to
verify.

Otherwise, if the dashboard is working for you, you can go to
Project/Compute/Access/API Access and use the "Download
OpenStack RC File" link there.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Dhvanan Shah]

UPDATE:
I am able to log into Horizon and perform all actions without any issue but
on my terminal, I am not able to do the same. The password that I thought
was wrong is not the issue as I logged in with the same password.
My keystone_adminrc file looks like this:

unset OS_SERVICE_TOKEN OS_SERVICE_ENDPOINT
export OS_USERNAME=admin
export OS_PASSWORD=
export OS_AUTH_URL=http://10.16.37.221:35357/v2.0
export PS1='[\u@\h \W(keystone_admin)]\$ '

export OS_TENANT_NAME=admin
export OS_REGION_NAME=RegionOne


Please suggest what I could do!

On Wed, Apr 27, 2016 at 1:41 PM, Dhvanan Shah  wrote:

> All the services are running properly, it is just that the any action
> performed says I am not authenticated or Forbidden (403) which means that
> there is an authorization problem. In my keystone_adminrc file I have
> exported all the environment variables and also set the admin password. Can
> it be the case that this admin password is wrong because of which it is not
> authenticating the admin right. If so how can I change the admin password?
>
> On Wed, Apr 27, 2016 at 12:05 PM, Dhvanan Shah  wrote:
>
>> http://10.16.37.221:35357/v2.0/tokens/34e4b79b157a4526bc8ebb80b82cbf62
>>
>> This link corresponding to the above token shows this error message -
>>
>> {"error": {"message": "The request you have made requires authentication.", 
>> "code": 401, "title": "Unauthorized"}}
>>
>>
>> So there is a problem in authentication from the keystone.I haven't changed 
>> the admin password.
>>
>>
>> On Wed, Apr 27, 2016 at 12:01 PM, Dhvanan Shah  wrote:
>>
>>> Hi,
>>>
>>> I have a 2 node OpenStack cluster setup running on CentOS. Due to some
>>> reason now I'm unable to perform any actions as it is not able to authorize
>>> me, it shows an error message saying "Authorization Failed: Forbidden (HTTP
>>> 403)" for Keystone when I run the command openstack-status and for
>>> nova-managed services it says "No handlers could be found for logger
>>> "keystoneclient.auth.identity.generic.base"
>>> ERROR (Forbidden): Forbidden (HTTP 403)".
>>>
>>> The keystone logs at /var/log/keystone show no problem that might have
>>> occured.
>>> The nova api logs show this :
>>> 2016-04-27 04:18:31.279 4314 DEBUG keystoneclient.session [-] REQ: curl
>>> -g -i -X GET
>>> http://10.16.37.221:35357/v2.0/tokens/34e4b79b157a4526bc8ebb80b82cbf62
>>> -H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H
>>> "X-Auth-Token: {SHA1}9d202e0a726633f660321097015cd9d67ac4df19"
>>> _http_log_request
>>> /usr/lib/python2.7/site-packages/keystoneclient/session.py:195
>>> 2016-04-27 04:18:31.290 4314 DEBUG keystoneclient.session [-] RESP:
>>> _http_log_response
>>> /usr/lib/python2.7/site-packages/keystoneclient/session.py:224
>>> 2016-04-27 04:18:31.290 4314 DEBUG keystoneclient.session [-] Request
>>> returned failure status: 404 request
>>> /usr/lib/python2.7/site-packages/keystoneclient/session.py:396
>>> 2016-04-27 04:18:31.290 4314 WARNING keystonemiddleware.auth_token [-]
>>> Authorization failed for token
>>> 2016-04-27 04:18:31.290 4314 WARNING keystonemiddleware.auth_token [-]
>>> Identity response: {"error": {"message": "Could not find token:
>>> 34e4b79b157a4526bc8ebb80b82cbf62", "code": 404, "title": "Not Found"}}
>>> 2016-04-27 04:18:31.290 4314 WARNING keystonemiddleware.auth_token [-]
>>> Authorization failed for token
>>>
>>>
>>> Could someone please help me out as to how I could debug this issue.
>>>
>>> Thanks,
>>> Dhvanan Shah
>>>
>>
>>
>>
>> --
>> Dhvanan Shah
>>
>
>
>
> --
> Dhvanan Shah
>



-- 
Dhvanan Shah
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Dhvanan Shah]

All the services are running properly, it is just that the any action
performed says I am not authenticated or Forbidden (403) which means that
there is an authorization problem. In my keystone_adminrc file I have
exported all the environment variables and also set the admin password. Can
it be the case that this admin password is wrong because of which it is not
authenticating the admin right. If so how can I change the admin password?

On Wed, Apr 27, 2016 at 12:05 PM, Dhvanan Shah  wrote:

> http://10.16.37.221:35357/v2.0/tokens/34e4b79b157a4526bc8ebb80b82cbf62
>
> This link corresponding to the above token shows this error message -
>
> {"error": {"message": "The request you have made requires authentication.", 
> "code": 401, "title": "Unauthorized"}}
>
>
> So there is a problem in authentication from the keystone.I haven't changed 
> the admin password.
>
>
> On Wed, Apr 27, 2016 at 12:01 PM, Dhvanan Shah  wrote:
>
>> Hi,
>>
>> I have a 2 node OpenStack cluster setup running on CentOS. Due to some
>> reason now I'm unable to perform any actions as it is not able to authorize
>> me, it shows an error message saying "Authorization Failed: Forbidden (HTTP
>> 403)" for Keystone when I run the command openstack-status and for
>> nova-managed services it says "No handlers could be found for logger
>> "keystoneclient.auth.identity.generic.base"
>> ERROR (Forbidden): Forbidden (HTTP 403)".
>>
>> The keystone logs at /var/log/keystone show no problem that might have
>> occured.
>> The nova api logs show this :
>> 2016-04-27 04:18:31.279 4314 DEBUG keystoneclient.session [-] REQ: curl
>> -g -i -X GET
>> http://10.16.37.221:35357/v2.0/tokens/34e4b79b157a4526bc8ebb80b82cbf62
>> -H "User-Agent: python-keystoneclient" -H "Accept: application/json" -H
>> "X-Auth-Token: {SHA1}9d202e0a726633f660321097015cd9d67ac4df19"
>> _http_log_request
>> /usr/lib/python2.7/site-packages/keystoneclient/session.py:195
>> 2016-04-27 04:18:31.290 4314 DEBUG keystoneclient.session [-] RESP:
>> _http_log_response
>> /usr/lib/python2.7/site-packages/keystoneclient/session.py:224
>> 2016-04-27 04:18:31.290 4314 DEBUG keystoneclient.session [-] Request
>> returned failure status: 404 request
>> /usr/lib/python2.7/site-packages/keystoneclient/session.py:396
>> 2016-04-27 04:18:31.290 4314 WARNING keystonemiddleware.auth_token [-]
>> Authorization failed for token
>> 2016-04-27 04:18:31.290 4314 WARNING keystonemiddleware.auth_token [-]
>> Identity response: {"error": {"message": "Could not find token:
>> 34e4b79b157a4526bc8ebb80b82cbf62", "code": 404, "title": "Not Found"}}
>> 2016-04-27 04:18:31.290 4314 WARNING keystonemiddleware.auth_token [-]
>> Authorization failed for token
>>
>>
>> Could someone please help me out as to how I could debug this issue.
>>
>> Thanks,
>> Dhvanan Shah
>>
>
>
>
> --
> Dhvanan Shah
>



-- 
Dhvanan Shah
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] Social at the summit

[Hong Hui Xiao]

+1 :)

HongHui Xiao(肖宏辉) PMP®
OpenStack Network development, Beijing, China



From:   Kyle Mestery 
To: "OpenStack Development Mailing List (not for usage questions)"

Date:   2016-04-25 下午 01:13
Subject:Re: [openstack-dev] [neutron] Social at the summit



OK, there is enough interest, I'll find a place on 6th Street for us
and get a reservation for Thursday around 7 or so.

Thanks folks!

On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:
> +1 :)
>
> Han Zhou
> Irc: zhouhan
>
>
> On Monday, April 25, 2016, Korzeniewski, Artur
>  wrote:
>>
>> Sign me up :)
>>
>> Artur
>> IRC: korzen
>>
>> -Original Message-
>> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
>> Sent: Monday, April 25, 2016 7:19 PM
>> To: OpenStack Development Mailing List (not for usage questions)
>> 
>> Subject: Re: [openstack-dev] [neutron] Social at the summit
>>
>> Count me in!
>> Will be good to meet all you guys!
>>
>> Darek (dasm) Smigiel
>>
>> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley
>> >  wrote:
>> >
>> >
>> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
>> >> wrote:
>> >>
>> >> WAT???
>> >>
>> >> It was never supposed to be core only. Everyone is welcome!
>> >
>> > +2
>> >
>> > irony intended.
>> >
>> > Socials are not controlled by gerrit ACLs.  :-)
>> >
>> > doug
>> >
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On 25 Apr 2016, at 11:56, Edgar Magana 
>> >>> wrote:
>> >>>
>> >>> Would you extend it to ex-cores?
>> >>>
>> >>> Edgar
>> >>>
>> >>>
>> >>>
>> >>>
>>  On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
>> 
>>  Ihar, Henry and I were talking and we thought Thursday night makes
>>  sense for a Neutron social in Austin. If others agree, reply on
this thread
>>  and we'll find a place.
>> 
>>  Thanks!
>>  Kyle
>> 
>>  ___
>>  ___ OpenStack Development Mailing List (not for usage
>>  questions)
>>  Unsubscribe:
>>  openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>> 
>> >>> __ OpenStack Development Mailing List (not for usage questions)
>> >>> Unsubscribe:
>> >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>
>> >> _
>> >> _ OpenStack Development Mailing List (not for usage questions)
>> >> Unsubscribe:
>> >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> >
>> > __
>> >  OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
__
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
__
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
__
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc project f2f2 meet-up place and time

[Elzur, Uri]

Can you pls add more detailed minutes as to emerging agreements/understandings?

Thx

Uri ("Oo-Ree")
C: 949-378-7568


-Original Message-
From: Akihiro Motoki [mailto:amot...@gmail.com] 
Sent: Tuesday, April 26, 2016 11:50 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc project 
f2f2 meet-up place and time

2016-04-26 12:31 GMT-05:00 Henry Fourie :
> All,
>Please use the networking-sfc etherpad to record discussions at the 
> meetups:
>
> https://etherpad.openstack.org/p/networking-sfc-austin-summit-meeting
>
>  - Louis
>
> -Original Message-
> From: Paul Carver [mailto:pcar...@paulcarver.us]
> Sent: Tuesday, April 26, 2016 10:20 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc 
> project f2f2 meet-up place and time
>
> On 4/26/2016 00:35, Akihiro Motoki wrote:
>> Hi Cathy and folks interested in SFC and classifers!
>>
>> Can't we use a different room like Salon D?
>> Salon C is a lunch room and at that time there are no sessions in other 
>> rooms.
>> It would be great if we can use Salon D or E (after looking at the 
>> first day's session) I think we can gather more easily and 
>> concentrate the discussion if we use some different space.
>> Thought?
>>
>
> Akihiro,
>
> Unless I've misunderstood the emails, the plan for Tuesday is a social lunch 
> for the SFC team to get together. The plan for Wednesday is a working lunch 
> to discuss flow classifiers in various projects and figure out how to 
> converge on a single flow classifier API/model that can be shared by 
> everything that needs to specify flows.
>
> If that's correct, then meeting in Salon C for lunch on Tuesday makes sense. 
> For Wednesday we probably ought to grab boxed lunches and find a quiet room.

I was confused with networking-sfc f2f meeting and flow classifier one.
My previous mail is a suggestion for wednesday flow classifier meeting.
Thanks for point it out.

Akihiro


>
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] Social at the summit

[Vikram Hosakote (vhosakot)]

Well, neutron is needed by most OpenStack projects :)

If it is open to non-neutron cores and non-neutron devs, I'd like to attend and
know what is happening is neutron in Newton.

And, yes, Bangers on Rainey St has great IPA ;)

Regards,
Vikram Hosakote
IRC: vhosakot

From: Darek Smigiel 
>
Reply-To: 
"openstack-dev@lists.openstack.org" 
>
Date: Wednesday, April 27, 2016 at 12:41 AM
To: 
"openstack-dev@lists.openstack.org" 
>
Subject: Re: [openstack-dev] [neutron] Social at the summit

Great idea Kyle,
This place looked awesome.

FYI, I've sent request for reservation. Just in case if Thursday would be 
crowded, especially that a lot of teams could have the same idea.

Thanks,
Darek

On Apr 26, 2016, at 8:27 PM, Kyle Mestery 
> wrote:
I propose we meet at Bangers on Rainey St. at 6PM. I don't have a reservation 
but it should be able to hold 50+ people. See y'all at 6PM Thursday!
Kyle
On Apr 25, 2016, at 1:07 PM, Kyle Mestery 
> wrote:
OK, there is enough interest, I'll find a place on 6th Street for us
and get a reservation for Thursday around 7 or so.
Thanks folks!
On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han 
> wrote:
+1 :)
Han Zhou
Irc: zhouhan
On Monday, April 25, 2016, Korzeniewski, Artur
> wrote:
Sign me up :)
Artur
IRC: korzen
-Original Message-
From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
Sent: Monday, April 25, 2016 7:19 PM
To: OpenStack Development Mailing List (not for usage questions)
>
Subject: Re: [openstack-dev] [neutron] Social at the summit
Count me in!
Will be good to meet all you guys!
Darek (dasm) Smigiel
On Apr 25, 2016, at 12:13 PM, Doug Wiegley
> wrote:
On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
>
wrote:
WAT???
It was never supposed to be core only. Everyone is welcome!
+2
irony intended.
Socials are not controlled by gerrit ACLs.  :-)
doug
Sent from my iPhone
On 25 Apr 2016, at 11:56, Edgar Magana 
>
wrote:
Would you extend it to ex-cores?
Edgar
On 4/25/16, 10:55 AM, "Kyle Mestery" 
> wrote:
Ihar, Henry and I were talking and we thought Thursday night makes
sense for a Neutron social in Austin. If others agree, reply on this thread
and we'll find a place.
Thanks!
Kyle
___
___ OpenStack Development Mailing List (not for usage
questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__ OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_
_ OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
 OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack 

Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes

[Ma, Wen-Tao (Mike, HP Servers-PSC-BJ)]

Hi Hong bin,

Thanks very much. It's good suggestion, I think it is a good way by using 
labels for extra flavors. But I notice that there is not the -node-count 
parameter in baymodel.

So I think it doesn't need specify minion-flavor-0 counts by -node-count. We 
can specify all of the flavor id and count ratio in the labels. It will check 
the minion node count with this ratio of labels when creating magnum bay that 
specified total minion node count . If the node-count in baycreate doesn't 
match with the flavor ratio, it will return the ratio match error message.   If 
there is not the multi-flavor-ratio key in lables, it will just use  
minion-flavor-0  to create 10 minion nodes.

$ magnum baymodel-create --name k8sbaymodel --flavor-id minion-flavor-0  
--labels 
multi-flavor-ratio=minion-flavor-0:3,minions-flavor-1:5,minion-flavor-2:2

$  magnum bay-create --name k8sbay --baymodel k8sbaymodel --node-count 10

Do you think about it?



> -Original Message-

> From: Ma, Wen-Tao (Mike, HP Servers-PSC-BJ) [mailto:wentao...@hpe.com]

> Sent: April-26-16 3:01 AM

> To: 
> openstack-dev@lists.openstack.org

> Subject: Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to

> provision minion nodes

>

> Hi Hongbin, Ricardo

> This is mike, I am working with Gary now.

> Thanks for Ricardo's good suggestion. I have tried the "map/index"

> method ,  we can use it to passed the minion_flavor_map and the index

> into the minion cluster stack. It does work well.

> I think we can update magnum baymodel-create to set the N minion

> flavors in the minion_flavor_map and assign minion counts for each

> flavor.

> For example :

> magnum baymodel-create --name k8s-bay-model  --flavor-id minion-flavor-

> 0:3,minion-flavor-1:5, minion-flavor-2:2. It will create 3 types flavor



The suggested approach seems to break the existing behaviour. I think it is 
better to support this feature in a backward-compatible way. How about using 
labels:



$ magnum baymodel-create --name k8sbaymodel --flavor-id minion-flavor-0 
--node-count 3 --labels extra-flavor-ids=minions-flavor-1:5,minion-flavor-2:2



> minion node and total minion nodes  count is 10. The magnum baymode.py

> will parse  this  dictionary and pass them to the heat template

> parameters minion_flavor_map, minion_flavor_count_map. Then the heat

> stack will work well.

>

> kubecluster-fedora-ironic.yaml

> parameters:

>   minion_flavor_map:

> type: json

> default:

>   '0': minion-flavor-0

>   '1': minion-flavor-1

>   '2': minion-flavor-2

>

>   minion_flavor_count_map:

> type: json

> default:

>   '0': 3

>   '1': 5

>   '2': 2

>

> resources:

> kube_minions_flavors:

> type: OS::Heat::ResourceGroup

> properties:

>   count: { get_param: minion_flavors_counts }

>   resource_def:

> type: kubecluster-minion-fedora-ironic.yaml

> properties:

>   minion_flavor_map: {get_param: minion_flavor_map}

>   minion_flavor_count_map: {get_param: minion_flavor_count_map}

>   minion_flavor_index: '%index%'

>

> How do you think about this interface in magnum baymodel to support N

> falvor to provision minion nodes? Do you have any comments about this

> design for this feature?

>

> Thanks && Regards

> Mike Ma

> HP Servers Core Platform Software China Email 
> wentao...@hpe.com

>

> -Original Message-

> From: Duan, Li-Gong (Gary, HPServers-Core-OE-PSC)

> Sent: Monday, April 25, 2016 3:37 PM

> To: OpenStack Development Mailing List (not for usage questions)

> >

> Cc: Ma, Wen-Tao (Mike, HP Servers-PSC-BJ) 
> >

> Subject: RE: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to

> provision minion nodes

>

> Hi Ricardo,

>

> This is really good suggestion. I'd like to see whether we can use

> "foreach"/"repeat" in ResourceGroup in Heat.

>

> Regards,

> Gary Duan

>

> -Original Message-

> From: Ricardo Rocha [mailto:rocha.po...@gmail.com]

> Sent: Thursday, April 21, 2016 3:49 AM

> To: OpenStack Development Mailing List (not for usage questions)

> >

> Subject: Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to

> provision minion nodes

>

> Hi Hongbin.

>

> On Wed, Apr 20, 2016 at 8:13 PM, Hongbin Lu 
> >

> wrote:

> >

> >

> >

> >

> > From: Duan, Li-Gong (Gary, HPServers-Core-OE-PSC)

> > [mailto:li-gong.d...@hpe.com]

> > Sent: April-20-16 3:39 AM

> > To: OpenStack Development Mailing List (not for usage questions)

> > Subject: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to

> > provision minion nodes

> >

> >

> >

> > Hi Folks,

> >

> >

> >

> > We are 

Re: [openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Dhvanan Shah]

http://10.16.37.221:35357/v2.0/tokens/34e4b79b157a4526bc8ebb80b82cbf62

This link corresponding to the above token shows this error message -

{"error": {"message": "The request you have made requires
authentication.", "code": 401, "title": "Unauthorized"}}


So there is a problem in authentication from the keystone.I haven't
changed the admin password.


On Wed, Apr 27, 2016 at 12:01 PM, Dhvanan Shah  wrote:

> Hi,
>
> I have a 2 node OpenStack cluster setup running on CentOS. Due to some
> reason now I'm unable to perform any actions as it is not able to authorize
> me, it shows an error message saying "Authorization Failed: Forbidden (HTTP
> 403)" for Keystone when I run the command openstack-status and for
> nova-managed services it says "No handlers could be found for logger
> "keystoneclient.auth.identity.generic.base"
> ERROR (Forbidden): Forbidden (HTTP 403)".
>
> The keystone logs at /var/log/keystone show no problem that might have
> occured.
> The nova api logs show this :
> 2016-04-27 04:18:31.279 4314 DEBUG keystoneclient.session [-] REQ: curl -g
> -i -X GET
> http://10.16.37.221:35357/v2.0/tokens/34e4b79b157a4526bc8ebb80b82cbf62 -H
> "User-Agent: python-keystoneclient" -H "Accept: application/json" -H
> "X-Auth-Token: {SHA1}9d202e0a726633f660321097015cd9d67ac4df19"
> _http_log_request
> /usr/lib/python2.7/site-packages/keystoneclient/session.py:195
> 2016-04-27 04:18:31.290 4314 DEBUG keystoneclient.session [-] RESP:
> _http_log_response
> /usr/lib/python2.7/site-packages/keystoneclient/session.py:224
> 2016-04-27 04:18:31.290 4314 DEBUG keystoneclient.session [-] Request
> returned failure status: 404 request
> /usr/lib/python2.7/site-packages/keystoneclient/session.py:396
> 2016-04-27 04:18:31.290 4314 WARNING keystonemiddleware.auth_token [-]
> Authorization failed for token
> 2016-04-27 04:18:31.290 4314 WARNING keystonemiddleware.auth_token [-]
> Identity response: {"error": {"message": "Could not find token:
> 34e4b79b157a4526bc8ebb80b82cbf62", "code": 404, "title": "Not Found"}}
> 2016-04-27 04:18:31.290 4314 WARNING keystonemiddleware.auth_token [-]
> Authorization failed for token
>
>
> Could someone please help me out as to how I could debug this issue.
>
> Thanks,
> Dhvanan Shah
>



-- 
Dhvanan Shah
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Keystone Authorization Failed: Forbidden (HTTP 403)

[Dhvanan Shah]

Hi,

I have a 2 node OpenStack cluster setup running on CentOS. Due to some
reason now I'm unable to perform any actions as it is not able to authorize
me, it shows an error message saying "Authorization Failed: Forbidden (HTTP
403)" for Keystone when I run the command openstack-status and for
nova-managed services it says "No handlers could be found for logger
"keystoneclient.auth.identity.generic.base"
ERROR (Forbidden): Forbidden (HTTP 403)".

The keystone logs at /var/log/keystone show no problem that might have
occured.
The nova api logs show this :
2016-04-27 04:18:31.279 4314 DEBUG keystoneclient.session [-] REQ: curl -g
-i -X GET
http://10.16.37.221:35357/v2.0/tokens/34e4b79b157a4526bc8ebb80b82cbf62 -H
"User-Agent: python-keystoneclient" -H "Accept: application/json" -H
"X-Auth-Token: {SHA1}9d202e0a726633f660321097015cd9d67ac4df19"
_http_log_request
/usr/lib/python2.7/site-packages/keystoneclient/session.py:195
2016-04-27 04:18:31.290 4314 DEBUG keystoneclient.session [-] RESP:
_http_log_response
/usr/lib/python2.7/site-packages/keystoneclient/session.py:224
2016-04-27 04:18:31.290 4314 DEBUG keystoneclient.session [-] Request
returned failure status: 404 request
/usr/lib/python2.7/site-packages/keystoneclient/session.py:396
2016-04-27 04:18:31.290 4314 WARNING keystonemiddleware.auth_token [-]
Authorization failed for token
2016-04-27 04:18:31.290 4314 WARNING keystonemiddleware.auth_token [-]
Identity response: {"error": {"message": "Could not find token:
34e4b79b157a4526bc8ebb80b82cbf62", "code": 404, "title": "Not Found"}}
2016-04-27 04:18:31.290 4314 WARNING keystonemiddleware.auth_token [-]
Authorization failed for token


Could someone please help me out as to how I could debug this issue.

Thanks,
Dhvanan Shah
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev