Re: [openstack-dev] [nova] nova API meeting schedule
Glad to hear that the API meeting is happening again, I would also love to join. On Mon, Jun 11, 2018 at 10:49 AM Ghanshyam wrote: > Hi All, > > As you might know, we used to have Nova API subteam meeting on Wed [1] but > we did not continue that this year due to unavailability of members. > > As per discussion with melanie , we would like to continue the API meeting > either on meeting channel (openstack-meeting-4) or as office hour on Nova > channel. We have 2 options for that: > > 1. If there are members from USA/Europe TZ would like to join API meeting > regularly then, we will continue the meeting on meeting channel with more > suitable time considering Asia TZ also. I will initiate the doodle vote to > select the time suitable for all interested members. > > 2. If no member from USA/Europe TZ then, myself and Alex will conduct the > API meeting as office hour on Nova channel during our day time (something > between UTC+1 to UTC + 9). There is not much activity on Nova channel > during our TZ so it will be ok to use Nova channel. In this case, we will > release the current occupied meeting channel. > > Please let us know who all would like to join API meeting so that we can > pursue accordingly. > > [1] https://wiki.openstack.org/wiki/Meetings/NovaAPI > > -Nova API Subteam > > > > > > __ > 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] [requirements][daisycloud][freezer][fuel][solum][tatu][trove] pycrypto is dead and insecure, you should migrate part 2
These project seem dies. On Mon, Jun 11, 2018 at 5:48 AM, Matthew Thode wrote: > On 18-06-04 14:06:24, Matthew Thode wrote: > > On 18-05-13 12:22:06, Matthew Thode wrote: > > > This is a reminder to the projects called out that they are using old, > > > unmaintained and probably insecure libraries (it's been dead since > > > 2014). Please migrate off to use the cryptography library. We'd like > > > to drop pycrypto from requirements for rocky. > > > > > > See also, the bug, which has most of you cc'd already. > > > > > > https://bugs.launchpad.net/openstack-requirements/+bug/1749574 > > > > > > > ++-- > ---+--+- > --+ > > | Repository | Filename > | Line | Text > | > > ++-- > ---+--+- > --+ > > | daisycloud-core| code/daisy/requirements.txt >| 17 | pycrypto>=2.6 # Public > Domain | > > | freezer| requirements.txt > | 21 | pycrypto>=2.6 # Public > Domain | > > | fuel-dev-tools | > > contrib/fuel-setup/requirements.txt >|5 | pycrypto==2.6.1 >| > > | fuel-web | nailgun/requirements.txt > | 24 | pycrypto>=2.6.1 > | > > | solum | requirements.txt > | 24 | pycrypto # Public Domain > | > > | tatu | requirements.txt > |7 | pycrypto>=2.6.1 > | > > | tatu | test-requirements.txt >|7 | pycrypto>=2.6.1 >| > > | trove | integration/scripts/files/ > requirements/fedora-requirements.txt | 30 | pycrypto>=2.6 # > Public Domain| > > | trove | integration/scripts/files/ > requirements/ubuntu-requirements.txt | 29 | pycrypto>=2.6 # > Public Domain| > > | trove | requirements.txt > | 47 | pycrypto>=2.6 # Public > Domain | > > ++-- > ---+--+- > --+ > > > > In order by name, notes follow. > > > > daisycloud-core - looks like AES / random functions are used > > freezer - looks like AES / random functions are used > > solum - looks like AES / RSA functions are used > > trove - has a review!!! https://review.openstack.org/# > /c/560292/ > > > > The following projects are not tracked so we won't wait on them. > > fuel-dev-tools, fuel-web, tatu > > > > so it looks like progress is being made, so we have that going for us, > > which is nice. What can I do to help move this forward? > > > > It does not look like the projects (other than trove) are moving forward > on this. > > -- > Matthew Thode (prometheanfire) > > __ > 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 > > -- Shake Chen __ 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] [ovs] [neutron] openvswitch flows firewall driver
Hello everybody, I'm cross-posting this with operators list. The openvswitch flows-based stateful firewall driver which uses the conntrack support in Linux kernel >= 4.3 (iirc) has been marked as experimental for several releases now, is there any information about flaws in this and why it should not be used in production? It's still marked as experimental or missing documentation in the networking guide [1]. And to operators; is anybody running the OVS stateful firewall in production? (firewall_driver = openvswitch) Appreciate any feedback :) Best regards [1] https://docs.openstack.org/neutron/queens/admin/config-ovsfwdriver.html __ 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] [nova] nova API meeting schedule
Hi All, As you might know, we used to have Nova API subteam meeting on Wed [1] but we did not continue that this year due to unavailability of members. As per discussion with melanie , we would like to continue the API meeting either on meeting channel (openstack-meeting-4) or as office hour on Nova channel. We have 2 options for that: 1. If there are members from USA/Europe TZ would like to join API meeting regularly then, we will continue the meeting on meeting channel with more suitable time considering Asia TZ also. I will initiate the doodle vote to select the time suitable for all interested members. 2. If no member from USA/Europe TZ then, myself and Alex will conduct the API meeting as office hour on Nova channel during our day time (something between UTC+1 to UTC + 9). There is not much activity on Nova channel during our TZ so it will be ok to use Nova channel. In this case, we will release the current occupied meeting channel. Please let us know who all would like to join API meeting so that we can pursue accordingly. [1] https://wiki.openstack.org/wiki/Meetings/NovaAPI -Nova API Subteam __ 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] [nova][osc] Documenting compute API microversion gaps in OSC
On Fri, 08 Jun 2018 17:16:01 +0900 Sylvain Bauza wrote > > > On Fri, Jun 8, 2018 at 3:35 AM, Matt Riedemann wrote: > I've started an etherpad [1] to identify the compute API microversion gaps > in python-openstackclient. > > It's a small start right now so I would appreciate some help on this, even > just a few people looking at a couple of these per day would get it done > quickly. > > Not all compute API microversions will require explicit changes to OSC, for > example 2.3 [2] just adds some more fields to some API responses which might > automatically get dumped in "show" commands. We just need to verify that the > fields that come back in the response are actually shown by the CLI and then > mark it in the etherpad. > > Once we identify the gaps, we can start talking about actually closing > those gaps and deprecating the nova CLI, which could be part of a community > wide goal - but there are other things going on in OSC right now (major > refactor to use the SDK, core reviewer needs) so we'll have to figure out > when the time is right. > > [1] https://etherpad.openstack.org/p/compute-api-microversion-gap-in-osc > [2] > https://docs.openstack.org/nova/latest/reference/api-microversion-history.html#maximum-in-kilo > > > Good idea, Matt. I think we could maybe discuss with the First Contact SIG > because it looks to me some developers could help us for that, while it > doesn't need to be a Nova expert. +1. We have FirstContact SIG meeting on Wed[1] and i will put this as one of the contribution item for new developers. As of now, there is no new contributor who contacted FirstContact sig but we keep tracking the same and will help this item as soon as we find any new developers. [1] https://wiki.openstack.org/wiki/First_Contact_SIG#Meeting_Agenda > > I'll also try to see how I can help on this. > -Sylvain > > -- > > Thanks, > > Matt > > __ > 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] [requirements][daisycloud][freezer][fuel][solum][tatu][trove] pycrypto is dead and insecure, you should migrate part 2
On 18-06-04 14:06:24, Matthew Thode wrote: > On 18-05-13 12:22:06, Matthew Thode wrote: > > This is a reminder to the projects called out that they are using old, > > unmaintained and probably insecure libraries (it's been dead since > > 2014). Please migrate off to use the cryptography library. We'd like > > to drop pycrypto from requirements for rocky. > > > > See also, the bug, which has most of you cc'd already. > > > > https://bugs.launchpad.net/openstack-requirements/+bug/1749574 > > > > ++-+--+---+ > | Repository | Filename > | Line | Text > | > ++-+--+---+ > | daisycloud-core| code/daisy/requirements.txt > | 17 | pycrypto>=2.6 # Public Domain > | > | freezer| requirements.txt > | 21 | pycrypto>=2.6 # Public Domain > | > | fuel-dev-tools | > contrib/fuel-setup/requirements.txt |5 | > pycrypto==2.6.1 | > | fuel-web | nailgun/requirements.txt > | 24 | pycrypto>=2.6.1 > | > | solum | requirements.txt > | 24 | pycrypto # Public Domain > | > | tatu | requirements.txt > |7 | pycrypto>=2.6.1 > | > | tatu | test-requirements.txt > |7 | pycrypto>=2.6.1 > | > | trove | > integration/scripts/files/requirements/fedora-requirements.txt | 30 | > pycrypto>=2.6 # Public Domain| > | trove | > integration/scripts/files/requirements/ubuntu-requirements.txt | 29 | > pycrypto>=2.6 # Public Domain| > | trove | requirements.txt > | 47 | pycrypto>=2.6 # Public Domain > | > ++-+--+---+ > > In order by name, notes follow. > > daisycloud-core - looks like AES / random functions are used > freezer - looks like AES / random functions are used > solum - looks like AES / RSA functions are used > trove - has a review!!! https://review.openstack.org/#/c/560292/ > > The following projects are not tracked so we won't wait on them. > fuel-dev-tools, fuel-web, tatu > > so it looks like progress is being made, so we have that going for us, > which is nice. What can I do to help move this forward? > It does not look like the projects (other than trove) are moving forward on this. -- Matthew Thode (prometheanfire) signature.asc Description: PGP signature __ 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
