Schlagwort: openstack

OpenStack Developer Mailing List Digest March 11-17

SuccessBot Says

Dims [1]: Nova now has a python35 based CI job in check queue running Tempest tests (everything running on py35)
jaypipes [2]: Finally got a good functional test created that stresses the Ironic and Nova integration and migration from Newton to Ocata.
Lbragstad [3]: the #OpenStack-Ansible project has a test environment that automates rolling upgrade performance testing
annegentle [4]: Craig Sterrett and the App Dev Enablement WG: New links to more content for the appdev docs [5]
jlvillal [6]: Ironic team completed the multi-node grenade CI job
Tell us yours via OpenStack IRC channels with message “#success <message>”

All: [7]

Pike Release Management Communication

The release liaison is responsible for:

Coordinating with the release management team.
Validating your team release team requests.
Ensure release cycle deadlines are met.
It&#8217;s encouraged to nominate a release liaison. Otherwise this tasks falls back to the PTL.

Ensure the releaase liaison has time and ability to handle the communication necessary.

Failing to follow through on a needed process step may block you from meeting deadlines or releasing as our milestones are date-based, not feature-based.

Three primary communication tools:

Email for announcements and asynchronous communication

“[release]” topic tag on the openstack-dev mailing list.
This includes the weekly release countdown emails with details on focus, tasks, and upcoming dates.

IRC for time sensitive interactions

With more than 50 teams, the release team relies on your presence in the freenode openstack-release channel.

Written documentation for relatively stable information

The release team has published the schedule for the Pike cycle [8]
You can add the schedule to your own calendar [9]

Things to do right now:

Update your release liaisons [10].
Make sure your IRC and email address listed in projects.yaml [11].

Update your mail filters to look for “[release]” in the subject line.
Full thread [12]

OpenStack Summit Boston Schedule Now Live!

Main conference schedule [13]
Register now [14]
Hotel discount rates for attendees [15]
Stackcity party [16]
Take the certified OpenStack Administrator exam [17]
City guide of restaurants and must see sites [18]
Full thread [19]

Some Information About the Forum at the Summit in Boston

“Forum” proper

3 medium sized fishbowl rooms for cross-community discussions.
Selected and scheduled by a committee formed of TC and UC members, facilitated by the Foundation staff members.
Brainstorming for topics [20]

“On-boarding” rooms

Two rooms setup classroom style for projects teams and workgroups who want to on-board new team members.
Examples include providing introduction to your codebase for prospective new contributors.
These should not be tradiitonal “project intro” talks.

Free hacking/meetup spaces

Four to five rooms populated with roundtables for ad-hoc discussions and hacking.

Full thread [21]

 
The Future of the App Catalog

Created early 2015 as a market place of pre-packaged applications [22] that you can deploy using Murano.
This has grown to 45 Glance images, 13 Heat templates and 6 Tosca templates. Otherwise did not pick up a lot of steam.
~30% are just thin wrappers around Docker containers.
Traffic stats show 100 visits per week, 75% of which only read the index page.
In parallel, Docker developed a pretty successful containerized application marketplace (Docker Hub) with hundreds or thousands regularly updated apps.

Keeping the catalog around makes us look like we are unsuccessfully trying to compete with that ecosystem, while OpenStack is in fact complimentary.

In the past, we have retired projects that were dead upstream.

The app catalog is however has an active maintenance team.
If we retire the app catalog, it would not be a reflection on that team performance, but that the beta was arguably not successful in build an active market place and a great fit from a strategy perspective.

Two approaches for users today to deploy docker apps in OpenStack:

Container-native approach using “docker run” after using Nova or K8s cluster using Magnum.
OpenStack Native approach “zun create nginx”.

Full thread [23][24]

ZooKeeper vs etcd for Tooz/DLM

Devstack defaults to ZooKeeper and is opinionated about it.
Lots of container related projects are using etcd [25], so do we need to avoid both ZooKeeper and etcd?
For things like databases and message queues, it&8217;s more than time for us to contract on one solution.

For DLMs ZooKeepers gives us mature/ featureful angle. Etcd covers the Kubernetes cooperation / non-java angle.

OpenStack interacts with DLM&8217;s via the library Tooz. Tooz today only supports etcd v2, but v3 is planned which would support GRPC.
The OpenStack gate will begin to default to etcd with Tooz.
Full thread [26]

Small Steps for Go

An etherpad [27] has been started to begin tackling the new language requirements [28] for Go.
An golang-commons repository exists [29]
Gopher cloud versus having a golang-client project is being discussed in the etherpad. Regardless we need support for os-client-config.
Full thread [30]

POST /api-wg/news

Guidelines under review:

Add API capabilities discovery guideline [31]
Refactor and re-validate API change guidelines [32]
Microversions: add next_min_version field in version body [33]
WIP: microversion architecture archival doc [34]

Full thread [35]

Proposal to Rename Castellan to oslo.keymanager

Castellan is a python abstraction to different keymanager solutions such as Barbican. Implementations like Vault could be supported, but currently is not.
The rename would emphasize the Castellan is an abstraction layer.

Similar to oslo.db supporting MySQL and PostgreSQL.

Instead of oslo.keymanager, it can be rolled into the oslo umbrella without a rename. Tooz sets the precedent of this.
Full thread [36]

Release Countdown for week R-23 and R-22

Focus:

Specification approval and implementation for priority features for this cycle.

Actions:

Teams should research how they can meet the Pike release goals [37][38].
Teams that want to change their release model should do so before end of Pike-1 [39].

Upcoming Deadlines and Dates

Boston Forum topic formal submission period: March 20 &#8211; April 2
Pike-1 milestone: April 13 (R-20 week)
Forum at OpenStack Summit in Boston: May 8-11

Full thread [40]

Deployment Working Group

Mission: To collaborate on best practices for deploying and configuring OpenStack in production environments.
Examples:

OpenStack Ansible and Puppet OpenStack have been collaborating on Continuous Integration scenarios but also on Nova upgrades orchestration
TripleO and Kolla share the same tool for container builds.
TripleO and Fuel share the same Puppet OpenStack modules.
OpenStack and Kubernetes are interested in collaborating on configuration management.
Most of tools want to collect OpenStack parameters for configuration management in a common fashion.

Wiki [41] has been started to document how the group will work together. Also an etherpad [42] for brainstorming.

 
Quelle: openstack.org

OpenStack Developer Mailing List Digest January 21-27

SuccessBot Says

dims [1] : Nova now has a python35 based CI job in check queue running Tempest tests (everything running on py35)
markvoelker [2]: Newly published Foundation annual report starts off with interoperability right in the chairman&#8217;s note [3]
Tell us yours via #OpenStack IRC channels with message “#success <message>”
All: [4]

Get Active in Upstream Training

There is a continuous effort in helping newcomers join our community by organizing upstream contribution trainings [5][6] before every summit.

1.5 &#8211; 2 days of hands-on steps of becoming an active OpenStack contributor.

Like everything else, this is a community effort.

In preparation for the Boston summit and the upcoming PTG in Atlanta, we are looking for coaches and mentors to help us make the training better.
If you’re interested in helping contact:

Ildiko Vancsa IRC freenode at ildikov or email [7]
Kendall Nelson IRC freenode at diablo_rojo or email [8]

Full thread: [9]

Project Team Gathering Coordination Tool

No central scheduling, beyond assigned rooms to teams and days.

Each team arranges their time in their room.
List of etherpads [10]

We still need centralized communication beyond each room:

An event IRC channel: openstack-ptg on free node IRC

Do public service announcements
Pings from room to room.

An EtherCalc spreadsheet powered dynamic schedule with extra rooms available:

One fishbowl
A few dark rooms with projectors and screens (not all will have a/v equipment due to budget).
Infra is working on setting up EtherCalc

Full thread: [11]

POST /api-wg/news

API Guidelines proposed for freeze:

Add guidelines on usage of state vs. status [12]
Clarify the status values in versions [13]
Add guideline for invalid query parameters [14]

Guidelines currently under review:

Add guidelines for boolean names [15]
Define pagination guidelines [16]
Add API capabilities discovery guideline [17 ]

Full thread: [18]

Lots of Teams Without PTL Candidates

We are reaching close to the end of the PTL nominations (Jan 29, 2017 23:45 UTC), but have projects that are leaderless:
Community App Catalog
Ec2 API
Fuel
Karbor
Magnum
Monasca
OpenStackClient
OpenStackUX
Packaging Prm
Rally
RefStack
Requirements
Senlin
Stable Branch Maintenance
Vitrage
Zun
Full thread [19]

 
Quelle: openstack.org

OpenStack Developer Mailing List Digest December 31 – January 6

SuccessBot Says

Dims &#8211; Keystone now has Devstack based functional test with everything running under python3.5.
Tell us yours via #OpenStack IRC channels with message &#8220;#success <message>&#8221;
All

Time To Retire Nova-docker

nova-docker has lagged behind the last 6 months of nova development.
No longer passes simple CI unit tests.

There are patches to at least get the unit tests work 1 .

If the core team no longer has time for it, perhaps we should just archive it.
People ask about it on openstack-nova about once or twice a year, but it’s not recommended as it’s not maintained.
It’s believed some people are running and hacking on it outside of the community.
The Sun project provides lifecycle management interface for containers that are started in container orchestration engines provided with Magnum.
Nova-lxc driver provides an ability of treating containers like your virtual machines. 2

Not recommended for production use though, but still better maintained than nova-docker 3.

Nova-lxd also provides the ability of treating containers like virtual machines.
Virtuozzo which is supported in Nova via libvirt provides both a virtual machine and OS containers similar to LXC.

These containers have been in production for more than 10 years already.
Well maintained and actually has CI testing.

A proposal to remove it 4 .
Full thread

Community Goals For Pike

A few months ago the community started identifying work for OpenStack-wide goals to “achieve visible common changes, push for basic levels of consistency and user experience, and efficiently improve certain areas where technical debt payments have become to high &8211; across all OpenStack projects.”
First goal defined 5 to remove copies of incubated Oslo code.
Moving forward in Pike:

Collect feedback of our first iteration. What went well and what was challenging?
Etherpad for feedback 6

Goals backlog 7

New goals welcome
Each goal should be achievable in one cycle. If not, it should be broken up.
Some goals might require documentation for how it could be achieved.

Choose goals for Pike

What is really urgent? What can wait for six months?
Who is available and interested in contributing to the goal?

Feedback was also collected at the Barcelona summit 8
Digest of feedback:

Most projects achieved the goal for Ocata, and there was interest in doing it on time.
Some confusion on acknowledging a goal and doing the work.
Some projects slow on the uptake and reviewing the patches.
Each goal should document where the “guides” are, and how to find them for help.
Achieving multiple goals in a single cycle wouldn’t be possible for all team.

The OpenStack Product Working group is also collecting feedback for goals 9
Goals set for Pike:

Split out Tempest plugins 10
Python 3 11

TC agreeements from last meeting:

2 goals might be enough for the Pike cycle.
The deadline to define Pike goals would be Ocata-3 (Jan 23-27 week).

Full thread

POST /api-wg/news

Guidelines current review:

Add guidelines on usage of state vs. status 12
Add guidelines for boolean names 13
Clarify the status values in versions 14
Define pagination guidelines 15
Add API capabilities discovery guideline 16

Full thread

 
Quelle: openstack.org

OpenStack Developer Mailing List Digest December 31 – January 6

SuccessBot Says

Dims &#8211; Keystone now has Devstack based functional test with everything running under python3.5.
Tell us yours via #OpenStack IRC channels with message &#8220;#success <message>&#8221;
All

Time To Retire Nova-docker

nova-docker has lagged behind the last 6 months of nova development.
No longer passes simple CI unit tests.

There are patches to at least get the unit tests work 1 .

If the core team no longer has time for it, perhaps we should just archive it.
People ask about it on openstack-nova about once or twice a year, but it’s not recommended as it’s not maintained.
It’s believed some people are running and hacking on it outside of the community.
The Sun project provides lifecycle management interface for containers that are started in container orchestration engines provided with Magnum.
Nova-lxc driver provides an ability of treating containers like your virtual machines. 2

Not recommended for production use though, but still better maintained than nova-docker 3.

Nova-lxd also provides the ability of treating containers like virtual machines.
Virtuozzo which is supported in Nova via libvirt provides both a virtual machine and OS containers similar to LXC.

These containers have been in production for more than 10 years already.
Well maintained and actually has CI testing.

A proposal to remove it 4 .
Full thread

Community Goals For Pike

A few months ago the community started identifying work for OpenStack-wide goals to “achieve visible common changes, push for basic levels of consistency and user experience, and efficiently improve certain areas where technical debt payments have become to high &8211; across all OpenStack projects.”
First goal defined 5 to remove copies of incubated Oslo code.
Moving forward in Pike:

Collect feedback of our first iteration. What went well and what was challenging?
Etherpad for feedback 6

Goals backlog 7

New goals welcome
Each goal should be achievable in one cycle. If not, it should be broken up.
Some goals might require documentation for how it could be achieved.

Choose goals for Pike

What is really urgent? What can wait for six months?
Who is available and interested in contributing to the goal?

Feedback was also collected at the Barcelona summit 8
Digest of feedback:

Most projects achieved the goal for Ocata, and there was interest in doing it on time.
Some confusion on acknowledging a goal and doing the work.
Some projects slow on the uptake and reviewing the patches.
Each goal should document where the “guides” are, and how to find them for help.
Achieving multiple goals in a single cycle wouldn’t be possible for all team.

The OpenStack Product Working group is also collecting feedback for goals 9
Goals set for Pike:

Split out Tempest plugins 10
Python 3 11

TC agreeements from last meeting:

2 goals might be enough for the Pike cycle.
The deadline to define Pike goals would be Ocata-3 (Jan 23-27 week).

Full thread

POST /api-wg/news

Guidelines current review:

Add guidelines on usage of state vs. status 12
Add guidelines for boolean names 13
Clarify the status values in versions 14
Define pagination guidelines 15
Add API capabilities discovery guideline 16

Full thread

 
Quelle: openstack.org