[openstack-dev] [Neutron][Dragonflow] IRC Meeting tomorrow (1/4) - 0900 UTC

[Gal Sagie]

Hello All,

We will have an IRC meeting tomorrow (Monday, 1/4) at 0900 UTC
in #openstack-meeting-4

Please review the expected meeting agenda here:
https://wiki.openstack.org/wiki/Meetings/Dragonflow

You can view last meeting action items and logs here:
http://eavesdrop.openstack.org/meetings/dragonflow/2015/dragonflow.2015-12-28-09.00.html

Please update the agenda if you have any subject you would like to discuss
about.

We would like to hear from anyone that wishes to attend the meetings but
cant
due to time zone differences, if you would like to attend please let us
know and we will
consider adding alternating meeting time.

Thanks
Gal.
__
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-ansible]

[Kevin Carter]

@Duck,


Is this an offline install or have you retried since posting the message? I ask 
because I'm not able to reproduce the problem. Its possible that the Ansible 
Galaxy API was down but its hard to say.

?
--

Kevin Carter
IRC: cloudnull


From: Duck Euler 
Sent: Friday, December 18, 2015 7:06 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [openstack-ansible]


when running openstack ansible quick start ( curl 
https://raw.githubusercontent.com/openstack/openstack-ansible/master/scripts/run-aio-build.sh
 | sudo bash )

it will halt with the following error.

++ ansible-galaxy install --role-file=ansible-role-requirements.yml 
--ignore-errors --force
- the API server (galaxy.ansible.com) is not 
responding, please try again later.

It just started happening in the last day.

I found if I comment out the following roles in the requirements file, that 
command runs to completion.

- src: evrardjp.keepalived
  name: keepalived
  version: '1.3'
- src: mattwillsher.sshd
  name: sshd

seeking advice or help on this issue.


__
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] Versioning of the fwaas API

[Brandon Logan]

On Sat, 2016-01-02 at 22:23 +, Sean M. Collins wrote:
> I was on Twitter and got linked to this blog post[1], and then got
> linked over to Terraform's docs, and of course I went and checked out
> its support for OpenStack.
> 
> Well, what do you know? It has support for Firewall[2]! Yay!
> 
> Based on the fact that we have a spec for a v2 API - the question
> becomes - how do we not break all this?
> 
> I see that LBaaS went the route of
> 
> v1 api = "/lb"
> v2 api = "/lbaas"
> 
> https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/extensions/loadbalancer.py#L32
> 
> https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/extensions/loadbalancerv2.py#L34
> 

Yeah, this was kind of a best bad option at the time.

> So - I guess we take the same route with FwaaS - maybe have the endpoint
> at "/fwaas" and then hopefully we can implement microversioning[3]? That
> way, we never have to make another endpoint like "/firewall" if we come up 
> with a v3 API in the 2020s.

I hope too that microversioning will fix this as well, but I'm not so
sure it will as it is proposed.  I might be overlooking something but I
can't seem how a neutron microversion can handle both neutron's api and
a fwaas/lbaas/vpnaas api that may or may not be enabled.

Definitely needs more discussion though, because it would be nice if it
does solve this problem.

> 
> [1]: http://tech.paulcz.net/2016/01/openstacks-and-ecosystems/
> 
> [2]: https://terraform.io/docs/providers/openstack/r/fw_firewall_v1.html
> 
> [3]: 
> http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/api-microversions.html
> 

Thanks,
Brandon
__
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] [Neutron] Versioning of the fwaas API

[Sean M. Collins]

I was on Twitter and got linked to this blog post[1], and then got
linked over to Terraform's docs, and of course I went and checked out
its support for OpenStack.

Well, what do you know? It has support for Firewall[2]! Yay!

Based on the fact that we have a spec for a v2 API - the question
becomes - how do we not break all this?

I see that LBaaS went the route of

v1 api = "/lb"
v2 api = "/lbaas"

https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/extensions/loadbalancer.py#L32

https://github.com/openstack/neutron-lbaas/blob/master/neutron_lbaas/extensions/loadbalancerv2.py#L34

So - I guess we take the same route with FwaaS - maybe have the endpoint
at "/fwaas" and then hopefully we can implement microversioning[3]? That
way, we never have to make another endpoint like "/firewall" if we come up with 
a v3 API in the 2020s.

[1]: http://tech.paulcz.net/2016/01/openstacks-and-ecosystems/

[2]: https://terraform.io/docs/providers/openstack/r/fw_firewall_v1.html

[3]: 
http://specs.openstack.org/openstack/nova-specs/specs/kilo/implemented/api-microversions.html

-- 
Sean M. Collins

__
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