OpenStack 开发者邮件列表摘要 9 月 2 日 – 8 日

Successbot Says!

摘要

  • Notifications Update Week 36 [3]

更新

  • Summit Free Passes [4]
    • 参加过亚特兰大 PTG 或将参加丹佛 PTG 的人将获得悉尼峰会的 100% 折扣门票。
    • 必须在10月27日之前使用。
  • 峰会门票早鸟截止日期为9月8日 [5]
    • 截止至 6:59 UTC
    • 折扣为您节省 50%
  • 已发布到 pypi 的库,版本为 YYY.X.Z [6]
    • 继续从 Pypi 删除库
    • 移除这些库
      • python-congressclient 2015.1.0
      • python-congressclient 2015.1.0rc1
      • python-designateclient 2013.1.a8.g3a2a320
      • networking-hyperv 2015.1.0
    • 仍在等待 PTL 批准其他项目。
      • mistral-extra
      • networking-odl
      • murano-dashboard
      • networking-midonet
      • sahara-image-elements
      • freezer-api
      • murano-agent
      • mistral-dashboard
      • Sahara-dashboard
  • 统一限制工作停滞 [7]
    • 需要新的领导者
    • Keystone 已合并一个规范 [8]
  • 我们是否应继续为实例主机名提供 FQDN?[9]
    • Nova 网络已弃用基于 FQDN 域的选项。
    • 正努力从 Neutron 获取域信息,而不是 Nova,但这可能不是正确的方向。
    • 我们要在虚拟机内部使用 FQDN 作为主机名吗?
      • 基础架构服务器以 FQDN 作为实例本身来构建。
  • Cinder V1 API 移除 [10]
    • 补丁在此 [11]
  • 从 Devstack 中移除 Screen - RSN
    • 已合并。
    • 一些人对不再拥有 screen 进行调试感到不满。
    • Systemd 文档正在更新,以包含 pdb 路径,以便能够以类似于 screen 的方式进行调试 [12] [13] [14]

PTG 规划

  • 视频访谈 [15]

 

[1] http://eavesdrop.openstack.org/irclogs/%23storyboard/%23storyboard.2017-09-06.log.html#t2017-09-06T22:03:06

[2] http://eavesdrop.openstack.org/irclogs/%23openstack-chef/%23openstack-chef.2017-09-08.log.html#t2017-09-08T13:48:14

[3] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121769.html

[4] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121843.html #Free

[5] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121847.html

[6] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121705.html #YYYY

[7] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121944.html

[8] https://specs.openstack.org/openstack/keystone-specs/specs/keystone/ongoing/unified-limits.html

[9] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121762.html

[10] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121956.html

[11] https://review.openstack.org/#/c/499342/

[12] https://review.openstack.org/#/c/501834/

[13] https://pypi.python.org/pypi/remote-pdb

[14] https://review.openstack.org/#/c/501870/

[15] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121901.html

OpenStack 开发者邮件列表摘要 8 月 26 日 – 9 月 1 日

Succesbot Says!

  • ttx: Pike 已发布![21]
  • ttx: Release automation 使 Pike 的发布过程顺畅无比 [22]

 

PTG 规划

  • Monasca (virtual)[1]
  • Vitrage(virtual)[2]
  • General Info & Price Hike[3]
    • 价格上涨至 150 美元
    • 周二晚上 5-6 点欢乐时光
    • 周四午餐时间事件反馈
  • Queens Goal Tempest Plugin Split [4]
  • Denver City Guide [5]
    • 请添加并审阅
  • ETSI NFV workshop[6][7]

 

摘要

  • TC Update [8]
  • Placement/Resource Providers Update 34 [9]

 

更新

  • Pike 已正式发布![10]
  • Outreachy 招募导师和赞助商![11]
    • 更多信息请见此处 [12]
    • 下一轮将于12月5日至3月5日进行。
  • 已发布到 pypi 的库,版本为 YYYY.X.Z[13]
    • 在 Kilo 版本中,当 neutron vendor 分解发生时,几乎所有网络项目的发布版本都设置为 2015.1.0。
    • 主要问题是 networking-hyperv == 2015.1.0 目前在 Pypi 上,当有人通过 pip 升级时,它会“升级”到 2015.1.0,因为它被认为是最新版本。
    • 是否应该取消该版本的发布?
    • 三种选择 [14]
      • 取消发布 - 最简单,但违反了 pypi 永不取消发布的政策。
        • tonyb 的 +1,列出了其他人需要与 PTL 确认才能转交给 infra 取消发布 [15]
      • 重命名 - 对下游来说工作量很大,但比取消发布干净。
      • 回滚 - 从 3000 或其他数字开始新版本,但非常hacky且丑陋。
    • dhellman、ttx 和 fungi 认为从 pypi 中删除是最简单的路线,尽管这不是处理事情的典型推荐方式。
  • 从 devstack 中移除 Screen - RSN[16]
    • 将 devstack 仅设置为一种执行模式的工作——自动化 QA 和本地之间相同——已接近完成!
    • 希望在 PTG 之前合并。
    • 在合并之前,针对此补丁测试您的 devstack 插件。
    • 补丁 [17]
  • 发布倒计时,用于 R+1 和 R+2 周 [18]
    • 仍有发布后的可交付成果需要处理。
    • 需要在周期性发布截止日期(9月14日)之前发布其 Pike 最终版本。
    • 如果您有疑问,请加入 #openstack-release。
    • ttx 将 RelMgmgt 的衣钵传给 smcginnis。

 

Pike Retrospectives

  • Nova [19]
  • QA [20]

 

[1] https://etherpad.openstack.org/p/monasca_queens_midcycle

[2] https://etherpad.openstack.org/p/vitrage-ptg-queens

[3] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121637.html

[4] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121715.html

[5] https://wiki.openstack.org/wiki/PTG/Queens/CityGuide

[6] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121494.html

[7] https://etherpad.openstack.org/p/etsi-nfv-openstack-gathering-denver

[8] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121711.html

[9] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121734.html

[10]  http://lists.openstack.org/pipermail/openstack-dev/2017-August/121647.html

[11] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121656.html

[12] https://wiki.openstack.org/wiki/Outreachy/Mentors

[13] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121598.html

[14] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121602.html

[15] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121623.html

[16] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121681.html

[17] https://review.openstack.org/#/c/499186/

[18] http://lists.openstack.org/pipermail/openstack-dev/2017-September/121706.html

[19] https://etherpad.openstack.org/p/nova-pike-retrospective

[20] https://etherpad.openstack.org/p/qa-pike-retrospective

[21] http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2017-08-30.log.html#t2017-08-30T16:07:24

[22] http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2017-08-30.log.html#t2017-08-30T16:08:07

OpenStack 开发者邮件列表摘要 8 月 19 日 – 25 日

SuccessBot 说

  • rosmaita: Glance 今天正在疯狂合并!欢迎回来 jokke_,以及感谢 flaper87、mfedosin、abhishekk 和 smcginnis [1]
  • coolsvap: 开发者们,PyCharm 订阅的社区支持已延长一年!请享用 [2]
  • Rosmaita: Glance Pike RC-2 现已发布![3]

 

PTG 规划

  • Skip Level Upgrades[12]
  • Cyborg [13]
  • Keystone 有一些事情想与 Baremetal/VM SIG 分享 [14]
  • CI Squad week 34 [24]

 

摘要

  • TC Report 34[4]
  • api-sig/news [5]
  • TC Update- Aug 25th [15]
  • placement/resource providers update 33 [16]

 

更新

  • Magnum 将于8月22日起每周二16:00 UTC恢复每周会议。
  • Updating the Docs Mission Statement  [17]
    • Thierry 提议 [18]
      • 文档团队提供指导、协助、工具和风格指南。
        使 OpenStack 项目团队能够生成一致、准确且
        高质量的文档。
    • 观点转向从零开始——在措辞之前,先看看文档团队实际做什么/做什么 [19]
    • 讨论很可能在 PTG 继续。
  • Microversion Parse Growth [20]
    • cdent 提交了一个补丁,该补丁开始清理并将 microversion 相关函数从 placement 服务移至 microversion-parse 库 [21]
    • 仍有更多工作要做——基于 microversion 的同名函数装饰器,用于根据 microversion 匹配引发状态码响应的实用方法等。
    • cdent 希望就如何进行获得意见。
  • Custom Resource Classes, Bare Metal Scheduling and You [22]
    • 如果您运行第三方 CI——这很重要。
    • 在 Pike 中,Nova 提供了一种基于自定义资源类的新型裸金属调度方式。
    • 旧方法已被弃用,但在 Queens 中将不可用。
    • 所有运行 ironic 的操作员必须在升级到 Pike 之前设置资源类字段,并在升级到 Queens 之前更改 flavor。
    • Nova 中的 ironic virt driver 将在 Pike 中自动迁移现有实例中嵌入的 flavor [23]
    • nova-compute 服务中的一个周期性任务
      将自动在 Placement 服务中创建 ironic 节点中的任何自定义资源类,如果它尚不存在。
      Placement 服务中。
  • Install Guide Testing [25]
    • Docs 团队需要志愿者来测试和验证安装说明 [26]
    • 如果您发现需要修改的地方,请在此处添加 [27]
    • 特别需要注意的团队
      • Cinder
      • Keystone
      • Horizon
      • Neutron
      • Nova
      • Glance
  • Reducing Code Complexity as a to-5 goal [6]
    • 与以往的方法不同——cdent 提议优先考虑一些简单的经验法则。
      • 提取方法
      • 保持方法简短
      • 避免副作用
      • 保持模块简短
    • Cdent 提议了一个补丁 [7]
    • Current Top 5 list [8]
  • CleanUp Oslo Deprecated Stuff [9]
    • Queens 中有很多东西需要清理,这些东西在 Oslo 中已被弃用 [10]
    • 如果您有疑问,请在 PTG 的 oslo helproom 咨询。
    • 通用的 gerrit topic 将是 ‘oslo-debt-cleanup’,以帮助跟踪与此技术债务相关的 review。
  • Marking <= mitaka EOL[11]
    • 有许多旧的 stable/* 分支需要清理。
    • 如果您参与以下项目,请发言!
      • QA
      • Group-based-policy
      • Zaqar
      • Packaging-deb
      • Fuel
      • networking-*
    • 移除定于 PTG 进行。

 

[1] http://eavesdrop.openstack.org/irclogs/%23openstack-glance/%23openstack-glance.2017-08-21.log.html#t2017-08-21T13:53:36

[2] http://eavesdrop.openstack.org/irclogs/%23openstack-dev/%23openstack-dev.2017-08-22.log.html#t2017-08-22T10:14:47

[3] http://eavesdrop.openstack.org/irclogs/%23openstack-glance/%23openstack-glance.2017-08-24.log.html#t2017-08-24T13:53:16

[4] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121383.html

[5] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121462.html

[6] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121445.html

[7] https://review.openstack.org/#/c/496404/

[8] https://governance.openstack.org/tc/reference/top-5-help-wanted.html

[9] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121345.html

[10] https://etherpad.openstack.org/p/oslo-queens-tasks

[11] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121432.html

[12] https://etherpad.openstack.org/p/queens-PTG-skip-level-upgrades

[13] https://etherpad.openstack.org/p/cyborg-queens-ptg

[14] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121468.html

[15] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121484.html

[16] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121490.html

[17] http://lists.openstack.org/pipermail/openstack-dev/2017-August/120744.html

[18] http://lists.openstack.org/pipermail/openstack-dev/2017-August/120796.html

[19] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121361.html

[20] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121384.html

[21] https://review.openstack.org/#/c/496212

[22] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121380.html

[23] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121385.html

[24] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121502.html

[25] http://lists.openstack.org/pipermail/openstack-dev/2017-August/121482.html

[26]  https://docs.openstack.org/install-guide/

[27] https://wiki.openstack.org/wiki/Documentation/PikeDocTesting

用户组新闻通讯 2017 年 8 月

悉尼峰会

不要错过您的早鸟票,销售将于 9 月 8 日 PT 时间晚上 11:59 截止。在此峰会指南中查找您需要了解的所有信息。

它包括有关住宿地点、特邀演讲嘉宾、峰会时间表等信息。

关于旅行的重要通知。所有非澳大利亚居民都需要签证才能前往澳大利亚(包括美国公民)。点击此处了解更多信息

完成用户调查的最后机会!

如果您还没有机会完成 OpenStack 用户调查,截止日期已延长至本周五,8月18日。如果您运行 OpenStack,这是您匿名分享反馈的机会。

在此处填写调查表。

OpenDev

对边缘计算感兴趣?加入我们参加 OpenDev,这是一项于 9 月 7-8 日在旧金山 DogPatch Studios 举行的新的协作工作活动。为期两天的活动门票仅为 100 美元,请在此处注册

 

活动将展示来自 Verizon、AT&T 和 eBay 的真实边缘用例演示,以及来自行业先驱的更新,包括卡内基梅隆大学的 Satya,他正在进行前沿研究。计划委员会包括 Beth Cohen (Verizon)、Kandan Kathirvel (AT&T)、Chris Price (Ericsson)、Andrew Mitry (Walmart) 和 Gregory Katsaros (Inmarsat)。参与的开放技术组织包括 OpenStack、Open Edge Computing、ETSI MEC、OPNFV、Kubernetes 等。

 

随着云架构的不断发展,计算正在向电信、零售、研究和其他行业的边缘推送。这为开放基础设施带来了巨大的机遇,因此我们正在开会讨论如何组装和集成满足边缘需求所需的组件。该活动旨在促进技术层面的协作,通过富有成效的工作组讨论以及关于边缘用例的闪电演讲。将有一系列协作式会议,由主持人深入探讨特定主题。在此处查看日程安排

 

有问题?请联系 events [at] openstack.org

OpenStack 日

查看全球即将举行的 OpenStack Days!在此处查看完整日历

好消息!OpenStack Upstream Institute 将在 OpenStack Days UKOpenStack Nordic 活动中举行。

 

CFP 即将截止!

 

  • CloudNativeCon/KubeCon
  • OpenStack Days Canada

 

 

Marketing Portal Content

OpenStack Foundation 的一些精彩内容可在 Marketing Portal 上找到。

这包括以下材料:

  • OpenStack 101 幻灯片
  • 2017 OpenStack 亮点与统计数据演示文稿
  • 活动宣传材料(贴纸和 T 恤设计)

 

Superuser 最新消息

 

过去几周发布了一些精彩的文章,其中一些介绍了您,即用户组!请在下方查看:

OpenStack 的 7 岁生日

 

OpenStack 用户组聚焦:Phoenix

 

OpenStack 用户组聚焦:Canada

 

如何在开放、多元的社区中驾驭新文化

 

OpenStack 用户聚焦:CERN

 

Learn OpenStack:一个社区新网站

 

为用户组新闻通讯做出贡献。

如果您想为下一期提交新闻,请提交到此 etherpad

提交的项目可能会因长度、风格和适用性而被编辑。

OpenStack 开发人员邮件列表摘要 7月22-28日

摘要

  • Nova placement/resource providers update 30 1
  • TC Report 30 2
  • POST /api-wg/news 3
  • Release countdown for week R-4, July 28 – Aug 4 4
  • Technical Committee Status update, July 28 5

Project Team Gathering Planning

  • Nova 6
  • Keystone 7
  • Sahara 8
  • Cinder 9
  • Oslo 10
  • Neutron 11
  • Documentation 12

Oslo DB Network Database 命名空间贯穿 OpenStack 项目

  • Mike Bayer 正在与 Octave Oregon 合作,为 oslo.db 模块添加 mysql 的网络数据库存储引擎,以便其他项目可以利用它。Mike Bayer 指出:
    • 代码审查 13
    • Nova 中的支持 14
    • Neutron 中的支持 15
  • 新数据类型,映射到 NDB 命名空间中的类型。
    • oslo_db.sqlalchemy.types.SmallString
    • oslo_db.sqlalchemy.types.String
  • 完整线程:16
  1. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120290.html
  2. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120112.html
  3. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120245.html
  4. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120304.html
  5. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120280.html
  6. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120020.html
  7. http://lists.openstack.org/pipermail/openstack-dev/2017-July/119299.html
  8. http://lists.openstack.org/pipermail/openstack-dev/2017-July/119352.html
  9. http://lists.openstack.org/pipermail/openstack-dev/2017-July/119358.html
  10. http://lists.openstack.org/pipermail/openstack-dev/2017-July/119462.html
  11. http://lists.openstack.org/pipermail/openstack-dev/2017-July/120270.html
  12. http://lists.openstack.org/pipermail/openstack-dev/2017-July/119990.html
  13. https://review.openstack.org/#/c/427970/
  14. https://review.openstack.org/#/c/446643
  15. https://review.openstack.org/#/c/446136/
  16. http://lists.openstack.org/pipermail/openstack-dev/2017-July/thread.html#120037

用户组 Newsletter – 2017年7月

悉尼峰会

随着悉尼峰会的临近,我们感到非常兴奋。不要错过您的早鸟票,销售将于 9 月 1 日截止。在此峰会袖珍指南中查找您的峰会袖珍指南。它包括有关住宿地点、特邀演讲嘉宾、峰会时间表、OpenStack Academy 等信息。

关于旅行的重要通知所有非澳大利亚居民都需要签证才能前往澳大利亚(包括美国公民)。点击此处了解更多信息 

旅行支持计划

需要旅行支持?您可以申请旅行支持计划Superuser 有一篇很棒的文章,提供了一些有用的技巧来帮助您完成申请。在此处找到 Superuser 文章。 

Superuser Awards

Superuser Awards 旨在表彰那些利用 OpenStack 有意义地改进业务、在竞争激烈的行业中脱颖而出,并同时为社区做出贡献的团队。悉尼峰会 Superuser Awards 的提名现已开放,并将接受至太平洋时间 9 月 8 日午夜。请在此篇 Superuser 文章中了解更多信息。 

用户调查

在用户调查中发出您的声音。有 7 种语言(繁体和简体中文、日语、韩语、德语、印度尼西亚语)。提交截止日期为 8 月 11 日。在此处完成。 

User Committee Elections

User Committee 选举即将举行。邀请活跃的用户贡献者(AUC)——包括运营商、贡献者、活动组织者和工作组(WG)成员——申请。提名于 7 月 31 日开始,于 8 月 11 日截止。在此篇 Superuser 文章中了解您需要知道的一切。 

波士顿峰会回顾

我们希望您都喜欢 5 月的波士顿峰会。通过 OpenStack Foundation 的 YouTube 频道,回顾您未能参加的会议。

Certified OpenStack Administrator exam

随着全球数千家公司采用并产品化 OpenStack,OpenStack 技能的需求量很大。COA 是 OpenStack Foundation 提供的第一个专业认证。它旨在帮助公司识别行业顶尖人才,并帮助求职者展示他们的技能。有关更多信息,请访问 COA 网站。您还可以查看此视频。 

征稿通知

有许多即将举行的活动征集论文。

OpenStack 日

今年全球将有许多 OpenStack Days 活动。 在此处查看完整日历

New User Groups

欢迎我们的新用户组!

正在寻找您当地的用户组或想在您所在地区建立一个?前往群组门户

Looking for speakers?

如果您正在为即将举行的活动或聚会寻找演讲嘉宾,请查看 OpenStack Speakers Bureau。它包含一个精彩的联系人存储库,其中包含他们的过往演讲、所讲语言、国家/地区和旅行偏好等信息。

Jobs Portal

通过 OpenStack Jobs Portal 寻找下一个绝佳机会。

您是否关注基金会在社交媒体上的动态?今天就查看我们的每个频道。

Twitter, Linkedin, Facebook, YouTube

 

为用户组新闻通讯做出贡献。

如果您想为下一期提交新闻,请提交到此 etherpad

提交的项目可能会因长度、风格和适用性而被编辑。

OpenStack 开发者邮件列表摘要 7月1-8日

重要日期

  • 2017年7月14日 23:59 OpenStack Summit Sydney Call for Presentations 截止 1
  • R-3 和 R-4 周(2017年7月31日-8月11日)期间 PTL 选举 2
  • All 3

摘要

  • TC status update by Thierry 4
  • API Working Group new 5
  • Nova placement/resource providers update 6

SuccessBot 说

  • pabelanger on openstack-infra 7: opensuse-422-infracloud-chocolate-8977043 由 nodepool 启动。
  • clark on openstack-infra 8: infra 将 citycloud 添加到测试节点池。
  • fungi on openstack-infra 9: OpenStack 的通用邮件列表存档(2010 年 7 月至 2013 年 7 月)已导入到当前 lists.openstack.org 上的通用存档中。
  • adreaf on openstack-qa: 10 Tempest ssh 验证默认在 master 的 gate 中运行。
  • All 11

Most Supported Goals And Improving Goal Completion

  • 全社区范围的目标讨论在 OpenStack Forum 开始,然后是邮件列表和 IRC,对于那些无法参加 Forum 的人。
    • 这些讨论有助于 TC 决定哪些目标将用于发布。
  • Potential goals
    • Split Tempest plugins into separate repos/projects 12
    • Move policy and docs into code 13
  • Pike 中的目标尚未真正实现。
  • 会议中提出的一个想法是创建一个名为“Champions”的角色,他们是推动目标完成的宣传者,通过帮助项目跟踪状态,有时进行代码补丁。
  • 对所选目标及其实现有深入了解并希望成为可信赖的人的志愿者。
  • 从线程中的讨论来看,我们似乎大多同意 Champion 的想法。
    • 我们有一位志愿者负责将 tempest 插件拆分到 repos/projects 中。
  • Full thread 14

 

  1. https://openstack.org/summit/sydney-2017/call-for-presentations/
  2. http://lists.openstack.org/pipermail/openstack-dev/2017-July/119359.html
  3. https://openstack.org/community/events/
  4. http://lists.openstack.org/pipermail/openstack-dev/2017-July/thread.html#119378
  5. http://lists.openstack.org/pipermail/openstack-dev/2017-July/119350.html
  6. http://lists.openstack.org/pipermail/openstack-dev/2017-July/thread.html#119388
  7. http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2017-05-24.log.html
  8. http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2017-05-24.log.html
  9. http://eavesdrop.openstack.org/irclogs/%23openstack-qa/%23openstack-qa.2017-05-28.log.html
  10. http://eavesdrop.openstack.org/irclogs/%23openstack-qa/%23openstack-qa.2017-05-28.log.html
  11. https://wiki.openstack.org/wiki/Successes
  12. http://lists.openstack.org/pipermail/openstack-dev/2017-July/thread.html#119378
  13. https://www.mail-archive.com/[email protected]/msg106392.html
  14. http://lists.openstack.org/pipermail/openstack-dev/2017-June/thread.html#118808

#openstack #openstack-dev-digest

OpenStack 开发者邮件列表摘要 6月10-16日

摘要

  • TC report 24 by Chris Dent 1
  • Release countdown for week R-10 and R-9, June 16-30 by Thierry 2
  • TC Status Update by Thierry 3.

Making Fuel a Hosted Project

  • Fuel originated from Mirantis as their OpenStack installer.
  • Approved as an official OpenStack project November 2015.
  • The goal was to get others involved to make one generic OpenStack installer.
  • In Mitaka and Newton it represented more commits than Nova.
  • While the Fuel team embraced open collaboration, it failed to attract other organizations.
  • Since October 2016 Fuel’s activity dropped from it’s main sponsor.
    • 68% drop between 2016 and 2017.
    • Project hasn’t held a meeting for three months.
    • Activity dropped from ~990 commits/month (April 2016, August 2016) to 52 commits in April 2017 and 25 commits May 2017.
  • Full thread: 4

Moving Away from “big tent” Terminology

  • Back in 2014 our integrated release was not really integrated, too big to be installed by everyone, yet too small to accommodate the growing interest in other forms of “open infrastructure”.
  • Incubation process created catch-22’s.
  • Project structure reform 4 discussions switched us to a simpler model: project teams would be approved based on how well they’d it the OpenStack overall mission and community principles rather than maturity.
    • Nick named the big tent 5
  • It ended up mostly creating confusion due to various events and mixed messages which we’re still struggling with today.
  • This was discussed during a TC office hour in channel openstack-tc 6
  • There is still no agreement on how to distinguish official and unofficial projects. The feedback in this thread will be used to assist the TC+UC+Board sub group on better communicating what is OpenStack.
  • Full thread: 7

 

[1] – http://lists.openstack.org/pipermail/openstack-dev/2017-June/118314.html

[2] – http://lists.openstack.org/pipermail/openstack-dev/2017-June/118476.html

[3] – http://lists.openstack.org/pipermail/openstack-dev/2017-June/118480.html

[4] – https://governance.openstack.org/tc/resolutions/20141202-project-structure-reform-spec.html

[5] – http://inaugust.com/posts/big-tent.html

[6] – http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-06-15.log.html#t2017-06-15T13:00:53

[7] – http://lists.openstack.org/pipermail/openstack-dev/2017-June/thread.html#118368

#openstack #openstack-dev-digest

OpenStack 开发者邮件列表摘要 6月3-9日

SuccessBot 说

  • fungi 1: OpenStack 的通用邮件列表存档(2010 年 7 月至 2013 年 7 月)已导入到当前 lists.openstack.org 上的通用存档中。
  • andreaf 2: Tempest ssh 验证默认在 master 的 gate 中运行。

etcd as a Base Service Update

  • Update to base service resolution from the TC 3
  • Projects wanting to use etc v3 API grpc 4
  • Projects that depend on eventlet, use the etcd3 v3 alpha HTTP API 5
  • If you use too, there are two driver choices 67
  • Oslo.cache driver 8
  • Devstack uses etcd3 by default 9
  • Cinder points to it 10
  • Keystone using etcd3 for caching 11
  • oslo.config to store configurations in etcd3 12
  • Full thread: 13

Global Request ID Progress

  • oslo.context / oslo.middleware – everything DONE
  • devstack logging additional globalrequestid – DONE
  • cinder
    • client supports globalrequestid – DONE
    • Cinder calls Nova with globalrequestid – TODO (waiting on Novaclient release)
    • Cinder calls Glance with globalrequestid – TODO
  • neutron
    • client supports globalrequestid – IN PROGRESS (this landed, released, but the neutron client release had to be blocked for unrelated issues).
    • Neutron calls Nova with globalrequestid – TODO (waiting on Novaclient release)
  • nova
    • Convert to oslo.middleware (to accept globalrequestid) – DONE
    • client supports globalrequestid – IN PROGRESS (waiting for release here 14)
    • Nova calls cinder with globalrequestid – DONE
    • Nova calls neutron with globalrequestid – TODO (waiting on working neutronclient release)
    • Nova calls Glance with global request id – IN PROGRESS (review needs final +2 here 15)
  • glance
    • client supports globalrequestid – DONE
    • Glance supports setting globalrequestid – IN REVIEW 16 *(some debate on this).
  • Full thread: 17

Unreleased Libraries

  • Several teams with library deliverables that haven’t see any release this cycle
    • glance-store
    • instack
    • pycadf
    • python-barbicanclient
    • python-congressclient
    • python-designateclient
    • python-searchlightclient
    • python-swiftclient
    • python-tackerclient
    • requestsexceptions
  • Full thread 18

POST /api-wg/news

  • 冻结指南提案
    • Add guideline about consuming endpoints from catalog 19.
    • Add support for historical service type aliases 20.
    • Describe the publication of service-types-authority data 21.
  • Guidelines Under Review
    • Microversions: add nextminversion field in version body 22.
    • A suite of several documents about doing version discovery 23
    • WIP: microversion architecture archival doc (very early; not yet ready for review) 24
  • Full thread: 25

TC Report 23

  • Chris Dent already does a wonderful summary 26.

Project Teams Gathering – Denver September 11-15th

  • What: Second Project Team Gathering
  • When: September 11-15
  • Where Denver Coloradoat the Renaissance Hotel 27
  • 日程
    • How long: PTG will run for 5 days Monday – Friday, September 11-15th
    • Inter-project team work: Monday – Tuesday
    • Single project meetings: Wednesday-Friday
  • Check with PTL’s before booking travel as some teams may not meet all three days。
  • Work in progress schedule 28
  • The OpenStack Foundation has reserved a block of discounted rooms at $149/night USD. Rooms will be available 27 until August 20 or until they sell out。
  • Check if you need a visa 29
  • Requests for invitation letters can be submitted here 30, and must be received by Friday, August 25, 2017。
  • Travel support program first round starts July 2nd. Apply now 31
  • Full thread: 32

[1] – http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2017-05-26.log.html

[2] – http://eavesdrop.openstack.org/irclogs/%23openstack-qa/%23openstack-qa.2017-05-28.log.html

[3] – https://governance.openstack.org/tc/reference/base-services.html

[4] – https://pypi.python.org/pypi/etcd3

[5] – https://pypi.python.org/pypi/etcd3gw

[6] – https://github.com/openstack/tooz/blob/master/setup.cfg#L29

[7] – https://github.com/openstack/tooz/blob/master/setup.cfg#L30

[8] – https://github.com/openstack/oslo.cache/blob/master/setup.cfg#L33

[9] – http://git.openstack.org/cgit/openstack-dev/devstack/tree/lib/etcd3

[10] – http://git.openstack.org/cgit/openstack-dev/devstack/tree/lib/cinder#n356

[11] – https://review.openstack.org/#/c/469621/

[12] – https://review.openstack.org/#/c/454897/

[13] – http://lists.openstack.org/pipermail/openstack-dev/2017-June/thread.html#117967

[14] – https://review.openstack.org/#/c/471323/

[15] – https://review.openstack.org/#/c/467242/

[16] – https://review.openstack.org/#/c/468443/

[17] – http://lists.openstack.org/pipermail/openstack-dev/2017-June/thread.html#117924

[18] – http://lists.openstack.org/pipermail/openstack-dev/2017-June/118146.html

[19] – https://review.openstack.org/#/c/462814/

[20] – https://review.openstack.org/#/c/460654/

[21] – https://review.openstack.org/#/c/462815/

[22] – https://review.openstack.org/#/c/446138/

[23] – https://review.openstack.org/#/c/459405/

[24] – https://review.openstack.org/#/c/444892/

[25] – http://lists.openstack.org/pipermail/openstack-dev/2017-June/118069.html

[26] – http://lists.openstack.org/pipermail/openstack-dev/2017-June/117950.html

[27] – http://www.marriott.com/meeting-event-hotels/group-corporate-travel/groupCorp.mi?resLinkData=the%20OpenStack%20Project%20Teams%20Gathering%5Edensa%60fntfnta%60149.00%60USD%60false%604%609/7/17%609/19/17%608/20/17&app=resvlink&stop_mobi=yes

[28] – https://docs.google.com/spreadsheets/d/1xmOdT6uZ5XqViActr5sBOaz_mEgjKSCY7NEWcAEcT-A/edit?usp=sharing

[29] – http://travel.state.gov/content/visas/en/general/visa-wizard.html

[30] – https://openstackfoundation.formstack.com/forms/visa_form_denver_ptg

[31] – https://openstackfoundation.formstack.com/forms/travelsupportptg_denver

[32] – http://lists.openstack.org/pipermail/openstack-dev/2017-June/118002.html

OpenStack 开发人员邮件列表摘要 5 月 20-26 日

SuccessBot 说

  • clarkb 1 : infra added city cloud to the pool of test nodes。
  • pabelanger 2 : opensuse-422-infracloud-chocolate-8977043 launched by nodepool。
  • All: 3

etcd 3.x as a Base Service

  • A devstack review 4 that adds a new etcd3 service.
  • Two options to enable the DLM use case with Tooz (for eventless based services) 5 6
  • Full thread: 7

Do We Want to be Publishing Binary Container Images?

  • During the Forum, the discussion on collaboration between various teams building or consuming container images。
  • Decide how to publish images from the various teams to docker hub or other container registries。
  • The community has refrained from publishing binary packages in other formats such as debs and RPMs. Instead we have left this to the responsibility of the downstream consumers to build production packages.
  • This would require more tracking of upstream issues (bugs, CVEs, etc) to ensure the images are updated as needed。
    • Given our security and stable team resources, this might not be a good idea at this time。
  • Kolla is interested in doing this for daily builds. Everything is licensed with ASL which gives no guarantees。
    • Even if you mark something to not be used in production, people still use it. Take the recent user survey with DevStack being used in production。
    • Kolla today publishes build instructions. Manually every release they provide built containers。
    • Built containers would run through our CI gate, so others don’t have to have a local CI build pipeline。
  • Things we publish to Pypi are different from this proposal
    • The formats published by pypi are source formats (sdist) and developer friend but production ready format (wheel)。
    • Most of our services are not packaged and published to PyPi. The libraries are to make them easy to consume in our CI。
    • The artifacts in PyPi contain references to dependencies, the dependencies are not built into the packages themselves。
  • Iterating on the infra-spec review for publishing to DockerHub has started 8
  • Full thread: 9

RFC Cross Project Request ID Tracking

  • In the logging Forum session, it was brought up how much effort operators are having to put into reconstructing flows for things like server boot when they go wrong。
    • Jumping from service to service, the request-id is reset to something new。
    • Being able to query in elastic search for the same request-id in communication between services would be useful。
  • There is a concern of trusting the request-id on the wire, because it’s coming from a random user。
    • We have a new concept of “service users” which are set of higher privilege services that we are using to wrap user requests。
  • Basic idea is
    • services will optionally take an inbound X-OpenStack-Request-ID which we’ll strongly validate req-$uuid format。
      • They will continue to generate one as well。
      • When the context is built we’ll check the service user was involved, and if not, reset the request-id to the local generated one。
      • Both request-ids will be logged。
    • Python clients and callers will need to be augmented to pass the request-id in on requests。
    • Servers will opt into calling other services this way。
  • Oslo spec for this has been merged 10
  • Full thread: 11

Can We Stop Global Requirements Update (Cont.)

  • Gnocchi has gate issues with Babel this time. Julien plans to remove all oslo dependencies over the next few months。
  • The project Cotyledon was presented at some summit ago as an alternative to oslo.service and getting rid of eventless. The library lives under the telemetry umbrella for now。
    • The project doesn’t live under oslo so that it’s encouraged for the greater python ecosystem to adopt and help maintain it。
  • Octavia is also using Cotyledon。
  • Full thread: 12

Revised Postgresql Deprecation Patch for Governance

  • In the Forum session we agreed to the following
    • Explicitly warn in operator facing documentation Postresql is less supported than MySQL。
    • Sure is the process of investigating migration from Postgresql to Gallera for future versions of OpenStack products。
    • TC governance patch is updated 13
  • Current sticking points
    • It’s important that the operator community largely is already in one camp or not。
    • Future items listed that are harder are important enough to justify a strict trade off here。
    • It’s ok to have the proposal have a firm lean in tone, even though it’s set of concrete actions are pretty reversible and don’t commit to future removal of Postgresql。
  • What has been raised as being hard by an abstraction layer like SQLAlchemy
    • OpenStack services taking a more active role in managing DBMS。
      • See Active or passive role with our database layer summary below for this discussion。
    • The ability to have zero down time upgrade for services such as Keystone。
      • Expand/contract with code and carefully dancing around the existence of two schema concepts simultaneously (e.g. Nova and Neutron)。
      • This shouldn’t be a problem because we use alembic or sqlalchemy-migrate to abstract away ALTER TABLE types。
      • Expand/contract using server side triggers to reconcile the two schema. This is more difficult because there is no abstraction layer that exists in SQLAlchemy. It could be feasible to build one specific to OpenStack.
    • Consistent UTF-8 4 & 5 byte support in our APIs
      • Unicode itself only needs 4 bytes and that is as far as any database supports right now. This problem has been solved by SQLAlchemy well before Python 3 existed。
    • The requirement that Postgresql libraries are compiled for new users trying to just run unit tests。
      • New developers who aren’t concerned with Postgresql don’t have to run these tests。
      • OpenStack went all the way with Kilo using the native python-MySQL driver which required compiling。
      • This is OpenStack. We are the glue to thousands of c-compiled libraries and packages。
    • Consistency around case sensitivity collation。
      • MySQL is defaulting to case-insensitive。
      • Postgresql almost has no support for case-insensitive。
      • SQLAlchemy supports things like ilike().
      • String datatype in SQLAlchemy guarantees case-insensitive。
  • Top concerns that remain
    • A1) Do not surprise users late by them only finding out they are on less traveled once they are so deeply committed. It’s fine for users to choose the path, as long as they are informed they are going to need to be more self reliant。
    • A2) Do not prevent features like zero downtime in Keystone making forward progress with a MySQL only solution。
  • Orthogonal concerns
    • B1) Postgresql was chosen by people in the past, maybe more than we realized, that’s real users we don’t want to throw under the bus. Whole sale delete is off the table. There’s no clear path off and missing data of who’s on it。
    • B2) The upstream code isn’t so irreparably changed (e.g. delete the SQLAlchemy layer) that it’s not possible to have alternative database backends。
  • The current proposal 13 addresses A1 and B1。
  • Full thread: 14

[1] – http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2017-05-24.log.html

[2] – http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2017-05-24.log.html

[3] – https://wiki.openstack.org/wiki/Successes

[4] – https://review.openstack.org/#/c/445432/

[5] – https://review.openstack.org/#/c/466098/

[6] – https://review.openstack.org/#/c/466109/

[7] – http://lists.openstack.org/pipermail/openstack-dev/2017-May/thread.html#117370

[8] – https://review.openstack.org/447524

[9] – http://lists.openstack.org/pipermail/openstack-dev/2017-May/thread.html#116677

[10] – https://review.openstack.org/#/c/464746/

[11] – http://lists.openstack.org/pipermail/openstack-dev/2017-May/thread.html#116619

[12] – http://lists.openstack.org/pipermail/openstack-dev/2017-May/thread.html#116736

[13] – https://review.openstack.org/#/c/427880/

[14] – http://lists.openstack.org/pipermail/openstack-dev/2017-May/thread.html#116642