Cathy has been co-leading the service function chaining work in
Neutron, and is a co-author of the SFC spec [1]. I'm adding here
her to officially recognize the work she's doing in Neutron.
[1] https://review.openstack.org/#/c/192933/
Change-Id: Ibff11ed41b4f1acd835ea89608f8738f5de966ec
Signed-off-by: Kyle Mestery <mestery@mestery.com>
This change adds puppet-murano to the OpenStack Puppet
Modules project, which will contain the module necessary to configure
and manage Murano with Puppet.
Change-Id: Id846941c9002194e76a6ac31c1979d410aa25fb9
Depends-On: Ia7e917b3032ef5ea56b33cf92e6b7c2d62674f6a
After discussing with the Barbican team we decided to change the project
from being a "Key Management Service" to being a "Key Manager Service".
This is to have a more uniform reference to Barbican.
Change-Id: I4ef6f1f5843d656ad1192f2cf050d9cafd755805
Add to docs tox target a check that reference/projects.yaml is sorted
alphabetically and display entries that are not sorted.
Change-Id: Ia86b50622e2fac5fdf791d57c884d2d8a9ec6c44
As per the guidelines here [1], moving stackforge/neutron-powervm
to networking-powervm in Neutron.
[1] https://review.openstack.org/#/c/175952/5
Change-Id: Id971c75e28c7b7ca3081555b195278a40627bcb5
Kolla spent 4 IRC meeting hours defining the Kolla mission here [1].
Our mission is clear and well defined.
Kolla provides production-ready containers and deployment tools for
operating OpenStack clouds.
The project uses the ASL 2.0 as declared in the code base [2].
The PTL was chosen by election to be Steven Dake using the standard
OpenStack mechanism [3].
The #kolla IRC channel on freenode is logged and the channel is
notified of such logging [4]. Our public meeting schedule was
decided by vote at [5] and all meeting logs are stored at our wiki.
The project uses public code reviews on the OpenStack infrastructure.
Kolla has been using the +2/+A process requiring two unique core
reviewers to review a patch since project inception. Our project
does not permit exceptions to the +2/+A process and we have never
approved a patch without two core reviews.
Our gating runs pep8, bashate, and other YAML/JSON syntax checking.
The Kolla team builds all images as a functional CI job to validate
our builds. In nearly every IRC meeting for the Liberty cycle
continuous integration has been our second topic of discussion.
The PTL serves as liaison between the Kolla community and other
projects for example coordinating our container content with James
Slagle, the TripleO PTL. Because Kolla deploys most OpenStack
namespaced server projects, we must coordinate and cooperate with
nearly every server project in OpenStack.
The project has openly worked with members of the TripleO community
to integrate kolla/containers into TripleO. Several PoC patches
exist demonstrating TripleO and Kolla integration [6].
During Paris ODS, we had a one hour design session recorded here [7].
The Kolla team had an open design session at Vancouver ODS during
Ansible Collaboration day. TripleO hosted several Kolla design
sessions at Vancouver ODS. We discuss all work in the open, mostly
using IRC. Based upon open communication between the Kolla core
reveiwer and developement team, the PTL presented the long-term
vision for Kolla during Liberty ODS [8].
Kolla uses IRC very heavily because everyone is very active on IRC.
As a result the Kolla core reviewer team often makes quick decisions.
Our core reviewer team is distributed around the world, so we use the
mailing list to communicate long term planning objectives. A recent
example of such is the recently held Kolla-Palooza midcycle meetup
on July 28th and July 29th, 2015. We use the mailing list by
prefixing e-mails to openstack-dev@lists.openstack.org with [kolla]
for long term planning rather than short term decision making.
Kolla has a high degree of diversity in both reviews [9] and
commits [10] with our largest percentage of contributions
originating from unaffiliated contributors.
[1] https://etherpad.openstack.org/p/kolla-manifesto
[2] https://github.com/stackforge/kolla/blob/master/LICENSE
[3] https://wiki.openstack.org/wiki/Kolla/PTL_Elections_March_2015
[4] http://eavesdrop.openstack.org/irclogs/%23kolla/
[5] https://wiki.openstack.org/wiki/Meetings/Kolla
[6] https://review.openstack.org/#/c/178840/
[7] https://etherpad.openstack.org/p/kolla-design
[8] https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/thanks-docker-the-pro-and-039s-and-con-and-039s-of-containerizing-your-openstack-services
[9] http://stackalytics.com/?project_type=all&module=kolla
[10] http://stackalytics.com/?project_type=all&module=kolla&metric=commits
Change-Id: If6e30574235e61ea6850e364d5ac7d11bc0ee2b4
RefStack is a test result collection and reporting service to
support the DefCore testing process. As the Refstack server is
being intergrated as an infra service[1], Restack project
should be relocated to openstack-infra.
[1] https://review.openstack.org/#/c/188207/
Change-Id: I6929fc738d0eaeef4571c6a907d9ba0c66e659a4
We recently approved an infra-spec to host trystack.o.o[1]; as such we
need to import the current trystack.org website bits into infra.
NOTE: this request does not affect how or where the sandbox
environments runs. This is outside the scope of this repo.
[1] http://specs.openstack.org/openstack-infra/infra-specs/specs/trystack-site.html
Change-Id: I1651f35353705ba8c869bf245dbfc6bbb9588e27
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
The library will be used by the DRAC driver in Ironic. The current
driver code will be refactored and most of it will move to the library.
The reason behind the move is that it has been difficult for
ironic-cores to review vendor specific code and it also requires an
actual hardware to test it.
Depends-On: I60983b269a5cab715183deec7f3c99feac642403
Change-Id: I11a58f047eb99352dbde7f403b11172de82d2e0d
Since we generate a giant merge conflict with the introduction of
"deliverables" in the previous commit, take the opportunity to
reorder the file alphabetically. This will reduce future conflicts
when new projects add themselves at the end of the file.
Change-Id: I762d2874a8cb6e809b0d07452cbbd5e858eec67c
Group the list of tags with some descriptive sub-headings to make it
easier to understand what they are.
Clean up a couple of tag page headings at the same time.
Change-Id: I5d9b92d1aea12e55d00fd791d6e453ce35b6339f
Our current projects.yaml file lists project teams and git
repositories associated to those. However, things we publish
as a single "thing" may be represented by multiple code
repositories. For example, a "neutron" release is actually made
of openstack/neutron and openstack/neutron-*aas. A "sahara"
release is actually made of openstack/sahara, openstack/sahara-extra
and openstack/sahara-image-elements. Those are all tagged at the
same time with the same version number, and published together
as a single "deliverable".
This change proposes to encode this layer in the projects.yaml file.
It also proposes to apply tags to the deliverable level rather than
at git repository level. Tags are meant to apply to things that are
consumed by our users, not to the technical pieces that help us
build those things. Note that for most projects have single-repo
deliverables and won't really look different. See Sahara and Neutron
in the proposed file to see examples of multi-repo deliverables.
Since this introduces a breaking change in the file format, we also
take the opportunity to simplify the YAML format: since tags no
longer have attributes they can be listed as an array rather than
as a dictionary, sparing us the useless "name:" part.
Change-Id: I2aa729d1b4278743a5e99b41178dc2d11b3e1348
This adds a resolution to retire the stackforge/ namespace in
favor of allowing all projects to use the openstack/ namespace.
This facilitates project development lifecycle transitions between
Stackforge and Openstack.
Change-Id: I6a895af592545b56293947b91579bfc7e6d4385a
With the change to big tent, many new projects are entering the big
tent with only one corporate contributor composing the core team.
An example that causes this script to break in Congress. This
patch produces the desired statistical results without crashing.
Change-Id: I0cae8a6864918d4f65e78829dc48f1af092ca7e8
The full project proposal can be found at
https://wiki.openstack.org/wiki/UX/ProgramProposal
The mission of the UX Program is to support and
facilitate cross-project efforts to improve the overall
user experience of OpenStack.
We provide user research to help teams identify any issues
preventing adoption of their services as well as help the
projects validate design and development efforts to address
those issues. In addition, we help the project teams create
solutions to address customer needs and pain points.
Finally, we will provide the OpenStack community with
visibility into any user experience issues related to
inconsistency across projects.
The UX team is not prescriptive; our goal is to collaborate
with OpenStack’s projects to create better experiences.
Contribution
Member contribution to the UX Project would be measured on
three metrics:
* No. of mock submissions to Invision
* No. of reviews/comments in Invision
* No. of UX studies conducted on behalf of the community
Invision is being provided to OpenStack at no charge as long as
the projects are shared within the open source community.Invision’s
concern was that folks might use our platform for internal
proprietary projects, which is not allowed.
We have 12 administers and 104 managers in Invision that
can add users and create projects from companies including
IBM, Mirantis, HP, and Redhat. We were very careful to
make sure that no single person or company had complete
control of the platform.
We are constantly looking for open source alternatives including
phabricator (phabricator.org), which is being discussed for
adoption by the community as a code review tool. Phabricator
also includes a design review that enables users to leave comments
on an image uploaded to the system. An added benefit is that
both code and UX review would be integrated into the same tool.
It is also important to note that projects can be downloaded from
Invision as PDF files that include both images and any comments
from users. If the community moves away from Invision, the plan
would be to make the PDFs available on the OpenStack UX wiki.
Project Communication
UX meetings were scheduled to occur every other week on IRC
but eventually slowed-down because most of the design efforts
were specifically focused on improving Horizon. That will
eventually change as the UX team engages additional projects.
In addition, IRC is a bit difficult to use within a discipline that is
largely aesthetic.
An additional way to get quick feedback or have a discussion with
the UX group is to join the IRC channel on freenode
(#openstack-ux).
There is a design review that occurs every other week were
community members are invited to share their design work
with the community. These meetings occur via virtual room
rather than IRC because the reviews require the participants to
“see” the designs in order to provide feedback.
A user panel was formed about two months ago in order to
provide feedback to the community from actual users. In
some ways, the user panel is intended to provide an alternative
“voice” to the development community.
The panel is struggling somewhat because we haven’t agreed
on a format for the meetings. For example, one suggestion was
to have a panel members talk about their specific challenges
during a session.
Panel members include users from NSA, Cisco, Pacific Northwest
National Labs, Orange and Yahoo.
Interim PTL
Until we have elections, Pieter Kruithof will be the PTL for delux.
Piet is currently a Sr UX Architect with HP Helion Cloud and
specifically focuses on improving the user experience of OpenStack.
This includes tactical activities such as proposing new designs in
addition to more strategic efforts such as providing platforms that
help enable collaboration within the community.
Piet was also a former Director with the Board of Certification in
Professional Ergonomics (BCPE). The board was established in
1990 as an independent nonprofit organization and is the certifying
body for individuals whose education and experience indicate broad
expertise in the practice of human factors, ergonomics and
user experience research.
Team members include engineers from IBM, Cisco, RackSpace,
HP and Mirantis.
Links
UX wiki
https://wiki.openstack.org/wiki/UX#Horizon_Proposals
User Research wiki
https://wiki.openstack.org/wiki/HorizonUsability_Testing
OpenStack UX patterns
https://wiki.openstack.org/wiki/UX/PatternsLibrary
OpenStack Invision Community
https://openstack.invisionapp.com
Change-Id: I4672d15a8e91190f05ba59086cc3b15f114d5f04
