2007 Commits

Author SHA1 Message Date
Jenkins
f727d91dd6 Merge "Add Ceph FS Charm" 2016-11-08 10:50:00 +00:00
Armando Migliaccio
f9971a8a6c Acknowledge remove-incubated-oslo-code for neutron
Change-Id: I417c4c1e27f19f634bb284171abc8f64c930e0e0
2016-11-08 04:30:06 +00:00
Ian Y. Choi
28b06858f1 Add i18n-specs repo
I18n wants to create and use a specification repository
for more detail and concrete descriptions with formalized
specs.

Change-Id: Ic794bc2c49851fe753d01619ce1ad51b45d78b3a
Depends-On: I0acff205689bb23c0007e679c9d52834ea73e315
2016-11-08 08:47:45 +09:00
Masayuki Igawa
a6b2bcf5be Add coverage2sql to Quality Assurance
Change-Id: I2b6ec416f1dd0320e0e5336917a786ef36f957ab
Depends-On: I8b0aa6c70f79d8552cc3113d5714e53587b08866
2016-11-07 15:00:42 +09:00
Brian Rosmaita
c5ac15b55e Acknowledge remove-incubated-oslo-code for Glance
Adds the URL of the Launchpad bug being used to track this work
in Glance to the appropriate governance doc.

Change-Id: I0573be8965b36f2e81883dbfc9fd870aa1608460
2016-11-05 21:30:27 -04:00
Matt Riedemann
b072f4492f Acknowledge that nova doesn't use oslo-incubator
Nova removed the last usage of oslo-incubator in the
Newton release.

Change-Id: I2855610214386eb81ece3ee37e40a213ba706bab
2016-11-05 13:41:30 -04:00
Andreas Jaeger
03c24cfc51 Add searchlight IRC channel
The team has registered this channel, add it to projects.yaml.

Change-Id: I90298e789967c83f20f8d58715759189ab1a253e
2016-11-04 12:49:31 +01:00
Jenkins
cf30221858 Merge "Update email address for Saggi Mizrahi" 2016-11-04 09:15:16 +00:00
Jenkins
afb9632527 Merge "Add deb-python-pyldap" 2016-11-04 08:59:15 +00:00
Jenkins
fd1d444e35 Merge "Update Ironic remove-incubated-oslo-code goal status" 2016-11-04 08:58:40 +00:00
Jenkins
88f4dfa342 Merge "Acknowledge remove-incubated-oslo-code for Manila" 2016-11-04 08:58:29 +00:00
yanyanhu
f945bd984c Acknowledge remove-incubated-oslo-code for Senlin
Change-Id: If4385bf11e3d5b00bf43f90854e2791174dacbd9
2016-11-03 22:02:43 -04:00
Jeremy Stanley
d40a788b5e Link to story for remove-incubated-oslo-code
The story for removal of obsolete incubated openstack-common code
covers remove-incubated-oslo-code goal work in the Infrastructure
team's openstack-infra/python-storyboardclient and
openstack-infra/storyboard deliverables.

Change-Id: I5d8818080308e0f52edfbb98d8c1c40ba69dfe14
2016-11-03 19:32:20 +00:00
Ben Swartzlander
76622496d0 Add manila-test-image to governance
Manila-test-image is an infrastructure project for test
and development of Manila. It's part of the Manila project
but not intended to ship with Manila.

Change-Id: I76ab79d1b92000aee08775a2b535273424aeb828
2016-11-03 12:48:18 -04:00
Richard Jones
f8d0e44dca Add xstatic-angular-ui-router project
Change-Id: Id6578f91791f3a5ad8217278e0de57c7544c0671
Depends-On: I3d0a15d3f9e94575b1402d0d625f5b410444fc2a
2016-11-03 13:37:22 +11:00
Amrith Kumar
00f9cbface Acknowledge remove-incubated-oslo-code for Trove
This commit acknowledges the acceptance of the Ocata goal of removing
oslo incubated code from the trove project.

Change-Id: I2ebc08072c30b6e4e659fda52c3e386a8de04e35
2016-11-02 13:24:09 -04:00
Saggi Mizrahi
d55b946a75 Update email address for Saggi Mizrahi
Saggi changed is email address so the registry should refer to the
updated email for PTL communication.

Change-Id: I1117305734b204145a6289766281e4dbd634760c
2016-11-02 14:09:28 +02:00
Armando Migliaccio
20f95dd947 Revisit list of governed neutron projects
Initiatives that fall short of the requirements for neutron project
inclusion and that have no proactive team ready to address the
identified gaps are removed from the neutron governance.

This patch takes neutron-vpnaas, networking-l2gw and networking-onos
out of the governance list for the Ocata release.

Change-Id: I4100079659f4a30729e3c2e16c1e39c2a067a974
Depends-on: Ibe5f167d2d54415d2cdd672a22c4c52793035ebe
Depends-on: I13548815c4522da109d342d868ef57a69adbf9e9
Depends-on: I1fea9e95393ec1ec3c4109759d2abb839373e1c6
2016-11-01 16:05:53 -07:00
Jenkins
5fd98db9e2 Merge "Tighten up langauge in "Contribution Is Our Currency"" 2016-11-01 20:31:53 +00:00
Jenkins
fe919e721e Merge "Update QA's extra-atc" 2016-11-01 20:27:27 +00:00
Jenkins
e03e7122c0 Merge "Overdue update of mission statement in charter" 2016-11-01 20:26:07 +00:00
Steve Martinelli
56315cf9b8 Acknowledge remove-incubated-oslo-code for keystone
Change-Id: I69261a28f851edbabd1b56905a2890966b5a65bb
2016-11-01 15:58:45 -04:00
Doug Hellmann
8bfae5a660 add release management response to goal-remove-incubated-oslo-code
Change-Id: I29d89e2c70c764ca399d4d2c5c6551b557ec62af
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2016-11-01 15:04:40 -04:00
Doug Hellmann
56b200b868 remove expired entries for extra-atcs
Remove extra-atc entries with expires-on dates that have passed.

Change-Id: I73c289a88f852c977ddca400ff69badfca47d9b0
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2016-11-01 14:00:58 -04:00
Vinay Potluri
a420eea8c0 Adding syntribos-payloads project to governance
In order to maintain the consistency within all syntribos projects we
have decided to change it to independent since it does not depend on
the release cycles.

Partially implements: syntribos-repos-templates-payloads
Depends-On: Iced984ff658a50e3c37adf578a7f26c7c0c7c7c3

Change-Id: I366e9bcf058bde01dba51e427f6716471ed79dd9
2016-10-31 17:01:34 -05:00
John Trowbridge
638e69b2bb Add tripleo-quickstart-extras to tripleo-quickstart deliverable
The tripleo-quickstart-extras will contain composable ansible roles that
will be used as the tool set for tripleo ci. For more details see the
related blueprint [1]

[1] https://goo.gl/R5yR7T

Depends-On: Ifc109b8e880f43b4526a543f7d931594ff6f951c
Change-Id: I37a5075a208a0280b7e61ccdd5d754a69a813070
2016-10-31 18:53:57 +00:00
Ryan Beisner
493ac6994e Add nova-compute-proxy and tempest charms
Include charm-nova-compute and charm-tempest in governances as
official OpenStack Charms.

Change-Id: I8209dc4faf357fb675ac5455e7fe5895aa7a6bfd
Depends-On: I9202938ab2111c1d8911ea613be3c7688cb67352
2016-10-31 10:53:09 +00:00
Jenkins
c19bf66360 Merge "Fix minor capital about PTLs" 2016-10-31 09:26:40 +00:00
Jenkins
69ec1872d7 Merge "Move incomplete OpenStack-Ansible projects to release:none" 2016-10-31 09:24:57 +00:00
Jenkins
1788e74bad Merge "Move os_trove into OSA deliverable" 2016-10-31 09:24:51 +00:00
Jenkins
6ffd160761 Merge "Remove neutron-pd-driver from neutron reference list" 2016-10-31 09:23:58 +00:00
Jenkins
8a878c9a79 Merge "Adding new repo to governance repository" 2016-10-31 09:23:53 +00:00
Jenkins
a19859d7f1 Merge "Add charm-manila-generic and interface" 2016-10-31 09:23:47 +00:00
Jenkins
872df7cbfc Merge "fix a typo" 2016-10-31 09:22:19 +00:00
Anne Gentle
8bb1893eed Adds API reference link to developer.openstack.org for barbican
Change-Id: I142b7c93e12d40c500e6683e30bfb85b6957db06
2016-10-28 11:45:00 +02:00
Graham Hayes
7d56e71ee6 Acknowledge remove-incubated-oslo-code for Designate
Change-Id: I2d10b16ed4b7a3e152fa19a16cbedb44d3b38733
2016-10-27 17:45:04 +02:00
Thomas Goirand
46c1cf637e Add deb-python-pyldap
DependsOn: I37374101443f5f1498bb376026df74a1d7eb80cf
Change-Id: Ic06581d8c97d617531afb95acb16ddfa5f6913e2
2016-10-27 16:51:57 +02:00
Ben Nemec
5b919d6e4d Provide artifacts for TripleO oslo-incubator cleanup
Change-Id: I0825f1eb4b045c2164511336ea2ced0665bb7c2d
2016-10-26 11:47:24 +00:00
Sam Betts
84729a9c63 Update Ironic remove-incubated-oslo-code goal status
Ironic doesn't have any openstack/common artifacts so this patch
updates the project's status on the goal page to reflect this.

Change-Id: Ic14574ee16cc4034cfb5b09808f6ebfc1312796c
2016-10-26 11:02:18 +01:00
Ben Swartzlander
01a97cda0c Acknowledge remove-incubated-oslo-code for Manila
There is no work to do in Manila for the
remove-incubated-oslo-code goal so state this fact explicitly.

Change-Id: Ie6a36cecd997103841c497a27feabaf9b10f9c34
2016-10-26 05:52:16 -04:00
Chris Holcombe
5848db19de Add Ceph FS Charm
Adding a Ceph FS charm to the charm collection.
This will enable users to easily deploy Ceph's MDS
server to their cluster.

Change-Id: If0c6e917960f8bdb244f07dbe446dc601d7fea6a
2016-10-24 14:57:34 -07:00
KATO Tomoyuki
09060254d2 Fix minor capital about PTLs
Change-Id: Id149d023c1d2102ec9c8f4cc4042676756e19191
2016-10-23 23:01:51 +09:00
Chris Dent
21041fe8c6 Tighten up langauge in "Contribution Is Our Currency"
Discussion of I876f95ccbbf71f4f512275af110690888449e093 indicated
that while there was general agreement with the spirit of the
content, there were some issues with redundancy and lack of
active voice. This change tries to address some of those issues
by paring the message down to its distillation.

As I started making changes I realized there was a lot of extra
fluff. We can be direct here with what we really mean.

Change-Id: If06a763e18af9fc13e8a67721382904473d8d34b
2016-10-21 14:23:36 +01:00
Thierry Carrez
a04f59322b Overdue update of mission statement in charter
Back in February, the TC proposed a change in the mission statement:
http://governance.openstack.org/resolutions/20160217-mission-amendment.html

That change was approved by the Board on March 29:
https://wiki.openstack.org/wiki/Governance/Foundation/29Mar2016BoardMeeting

As a result, an update of the charter was proposed and merged.
Unfortunately, it used wording from an earlier mission statement
change proposal, and nobody spotted the issue in review:
https://review.openstack.org/#/c/292610/

This change applies the latest (and approved) wording.

Change-Id: Ice1a05f4eaf3c442de823011f20f0214d4872fda
2016-10-21 10:49:41 +02:00
Ken'ichi Ohmichi
3c8377615a Update QA's extra-atc
We continue using Cirros and Scott is maintaining the Cirros as its
maintainer. His work is great for our OpenStack community.
So this patch updates the extra-atc expires-in date.

Change-Id: I0b016ae1ca3f3c497fd5249ed952c0bac1756414
2016-10-20 12:15:36 -07:00
Andy McCrae
b0247afc40 Move incomplete OpenStack-Ansible projects to release:none
The following OpenStack-Ansible repositories that are currently listed
as release:cycle-trailing are not ready for a release cycle, and are
currently in early development or non-functional:

os_barbican
os_cloudkitty
os_designate
os_monasca
os_watcher
os_zaqar

This PR moves these repositories to release:none. These will be moved to
follow a release once these repositories are functional and ready.

Change-Id: I1996302e78a6bda934e67b13e65941e500ecb5e2
2016-10-20 13:11:39 +01:00
Andy McCrae
fd0eb324cc Move os_trove into OSA deliverable
The Trove role is now included as part of the OpenStack-Ansible
integrated deliverable for the Ocata release.
This patch moves the repository entries to reflect this move.

Change-Id: I8bc89f1d4a36ef9db160d015de9176ce65dc4b20
2016-10-20 13:02:19 +01:00
Chaoyi Huang
342ff2010c Add project Tricircle to OpenStack big-tent
Following the directive
http://governance.openstack.org/reference/new-projects-requirements.html

OpenStack Mission Alignment:
The purpose of the Tricircle project is to provide networking automation
across Neutron in multi-region OpenStack clouds deployment.

Use cases for the Tricircle is described in the wiki[1] adn material for
big-tent application[2].

Each OpenStack cloud includes its own Nova, Cinder and Neutron, the
Neutron servers in these OpenStack clouds are called local Neuron
servers, all these local Neutron servers will be configured with the
Tricircle Local Neutron Plugin. A seperate Neutron server will be
installed and run standalone as the coordinator of networking automation
across local Neutron servers, this Neutron server will be configured
with the Tricircle Central Neutron Plugin, and is called central
Neutron server.

Leverage the Tricircle Central Neutron Plugin and the Tricircle Local
Neutron Plugin configured in these Neutron servers, the Tricircle can
ensure the IP address pool, IP/MAC address allocation and network
segment allocation being managed globally without conflict, and the
Tricircle handles tenant oriented data link layer(Layer2) or network
layer(Layer3) networking automation across local Neutron servers,
resources like VMs, bare metal or containers of the tenant can
communicate with each other via Layer2 or Layer3, no matter in which
OpenStack cloud these resources are running on.

Note: There are some our own definitions of Layer2/Layer3 networking
across Neutron. To make sure what they are, please read our design
documentation, especially "6.5 L2 Networking across Neutron"[3].

The Tricircle and multi-region OpenStack clouds will use shared
KeyStone(with centralized or distributed deployment) or federated
KeyStones.

The Tricircle is composed of the followings:
1)Tricircle Local Neutron Plugin
  It runs under local Neutron server in the same process like
  OVN/Dragonflow Neutron plugin, it is a shim layer between real core
  plugin and Neutron server
  The Tricircle Local Neutron Plugin serve for cross Neutron networking
  automation triggering.
2)Tricircle Central Neutron Plugin
  It runs under central Neutron server in the same process like
  OVN/Dragonflow Neutron plugin.
  The Tricircle Central Neutron Plugin serve for tenant level L2/L3
  networking automation across multi-OpenStack instances.
3)Admin API
  A web service introduced by the Tricircle to manage the mappings
  between OpenStack instances and availability zone which is used
  for availability zone hint parameter during network creation in
  central Neutron.
  Retrieve object uuid routing.
  Expose RESTful API for maintenance purpose.
  Running together with central Neutron Server.
4)XJob
  Receive and handle cross Neutron networking functionalities and
  other async jobs from Admin API or the Tricircle Central Neutron
  Plugin through message bus.
  For example, an async. job to configure the extra route in
  different local Neutron servers for L3 networking.
5)Database
  The Tricircle has its own database to store jobs, resource routing
  tables for the Tricircle Central Neutron plugin, Admin API and XJob.
  The Tricircle Neutron Central Plugin will also reuse database of
  central Neutron server to do the global management of tenant's
  resources like IP/MAC/network/router.
  The Tricircle Local Neutron Plugin is a shim layer between real
  core plugin and Neutron server, so Neutron database will be still
  there for local Neutron server and real core plugin.

Following the 4 opens:

Open Source:
- The Tricircle is 100% open source under an Apache 2.0 license[4], everything
  from implementation to design to future features and roadmap are happening
  and shared openly and presented in various meet-ups and documents.
- The Tricircle has no library dependencies which effectively restrict how the
  project may be distributed or deployed. Oslo libraries are used by all
  components where applicable.

Open Community:
- The leadership is chosen by the contributors to the project[5][6][7].
- We are working closely with the community to share use cases and problems
  and decide on future priorities for the project. It is our mission to
  collaborate with as many members/companies in the community as possible
  and we welcome any feedback and any desire to help us shape the Tricircle's
  future.
  This is done using the mailing list, etherpad, IRC, weekly meetings, patches,
  and OpenStack summit sessions[8][9][10][11][12][13][14].
- Contributors of the Tricircle comes from different companies and
  universities[15][16][17][18][19][20], some of them are working as
  independent contributors.

Open Development:
- All the Tricircle code is being code reviewed in OpenStack Gerrit[21].
- The Tricircle has a core team which openly discuss all issues[21][22].
- The Tricircle support gate tests which run unit tests and fullstack
  tests[23][24].
- The Tricircle collaborates other projects such as Neutron and L2GW to
  try and find optimal cross OpenStack L2 networking solutions[8].
- The Tricircle collobarates with Neutron via its plugin mechanism to do
  the cross OpenStack networking automation.
- Bugs are managed by OpenStack launchpad[25].

Open Design:
- All designs and specs of the Tricircle are published for review and managed
  in OpenStack launchpad[26][27].
- The Tricircle conducts a weekly IRC meeting to discuss all designs and
  future roadmap[10].
- The Tricircle repository offers documentation and diagrams to explain the
  current design, code and future roadmap[4].
- Everything is discussed openly either on the review board, the Tricircle
  IRC channel, or the ML, or Google doc[2][3], or etherpad[28][29].

[1] https://wiki.openstack.org/wiki/Tricircle#Use_Cases
[2] https://docs.google.com/presentation/d/1Zkoi4vMOGN713Vv_YO0GP6YLyjLpQ7fRbHlirpq6ZK4/edit?usp=sharing
[3] https://docs.google.com/document/d/1zcxwl8xMEpxVCqLTce2-dUOtB-ObmzJTbV1uSQ6qTsY/
[4] https://github.com/openstack/tricircle
[5] http://lists.openstack.org/pipermail/openstack-dev/2016-May/094019.html
[6] http://lists.openstack.org/pipermail/openstack-dev/2016-May/095317.html
[7] http://lists.openstack.org/pipermail/openstack-dev/2016-September/103925.html
[8] https://review.openstack.org/#/c/282180/
[9] http://eavesdrop.openstack.org/meetings/tricircle/
[10] https://wiki.openstack.org/wiki/Meetings/Tricircle
[11] https://wiki.openstack.org/wiki/Meetings/Tricircle#Announcements
[12] https://www.openstack.org/summit/austin-2016/summit-schedule/events/7480
[13] https://www.openstack.org/summit/austin-2016/summit-schedule/events/9533
[14] https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Tricircle%3A
[15] http://stackalytics.com/?project_type=openstack-others&module=tricircle&metric=marks&release=newton
[16] http://stackalytics.com/?project_type=openstack-others&module=tricircle&metric=patches&release=newton
[17] http://stackalytics.com/?project_type=openstack-others&module=tricircle&metric=loc&release=newton
[18] http://stackalytics.com/?project_type=openstack-others&module=tricircle
[19] http://stackalytics.com/?project_type=openstack-others&module=tricircle&metric=patches
[20] http://stackalytics.com/?project_type=openstack-others&module=tricircle&metric=loc
[21] https://review.openstack.org/#/q/project:openstack/tricircle
[22] https://review.openstack.org/#/admin/groups/441,members
[23] https://github.com/openstack-infra/project-config/search?utf8=%E2%9C%93&q=tricircle
[24] https://review.openstack.org/#/c/375976/
[25] https://bugs.launchpad.net/tricircle
[26] https://blueprints.launchpad.net/tricircle/+specs?show=all
[27] https://github.com/openstack/tricircle/tree/master/specs
[28] https://etherpad.openstack.org/p/TricircleCrossPodL2Networking
[29] https://etherpad.openstack.org/p/TricircleSplitting

Change-Id: I44f0d614dae81004ca31250461b9d4dbe865a13a
2016-10-20 00:05:06 -04:00
Armando Migliaccio
c1872a538f Remove neutron-pd-driver from neutron reference list
This project is being retired as it is superseded by
Neutron built-in dibbler support.

Change-Id: I0bba0e38eb0087185cf63d362e14fe8c080bb029
Depends-on: I77099ba826b8c7d28379a823b4dc74aa65e653d8
2016-10-19 15:57:54 -07:00
Alex Kavanagh
68309085ce Add charm-manila-generic and interface
This patchset adds the charm-manila-generic which is to configure the
manila charm to use the generic interface.  The
charm-interface-manila-plugin which connects backend configuration
charms to manila.

Change-Id: I810d9737fe67a04f63edd9a5d333b34f937f2405
Depends-On: I5e0fbcf4f192905c275f93422841ecce07b114a5
2016-10-19 10:34:33 +00:00