Open Stack

Running through the current priorities list (mostly unchanged so far
from our discussion in Tokyo); let me know if you disagree with
these observations and we can adjust...


Ansible Puppet Apply
--------------------

http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html

This seems to be basically done and in production, modulo some bugs
identified in our session in Austin:

https://etherpad.openstack.org/p/newton-infra-robustify-ansible-puppet

I think it needs to stay on the priority list until these are fixed,
or we need to enumerate those still outstanding as bugs in search of
a fix (and consider the spec implemented just buggy) if they won't
be fixed in the very near future.


Use Diskimage Builder in Nodepool
---------------------------------

http://specs.openstack.org/openstack-infra/infra-specs/specs/dib-nodepool.html

As I understand it, this is complete except for TripleO's images
(yes, irony since DIB is itself a TripleO team project). We'd like
to be able to deprecate and eventually remove snapshot support in
nodepool, so I think this stays on the priority list until TripleO
is no longer an issue (fixed or switched to being a third-party CI
system).


Infra-cloud
-----------

http://specs.openstack.org/openstack-infra/infra-specs/specs/infra-cloud.html

I've unfortunately lost touch with the progress on this since our
hardware was brought back online following the great flood. I assume
it's not done yet, or I would have heard about it. ;)

Given we're still light on available nodes at peak, this ought to
stay on the priority list for now.


Store Build Logs in Swift
-------------------------

http://specs.openstack.org/openstack-infra/infra-specs/specs/logs-in-swift.html

This seems to have taken a break, with our log volume diminishing
significantly in the past year or so and an alternative AFS-based
solution proposed:

https://review.openstack.org/269928

We should remove the original spec from our priority list (since
that's basically already ceased to be an actual priority), and
probably supercede it with the AFS proposal.


maniphest migration
-------------------

http://specs.openstack.org/openstack-infra/infra-specs/specs/maniphest.html

This spec no longer has a volunteer, and the alternative storyboard
proposal has gained steam:

http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html

I think we should swap these in the priority list. However, the
deployment automation work done for maniphest may still be
repurposed for pholio (another component of the phabricator suite),
since the UX team has expressed an interest in having us maintain an
instance of that for them.


Common OpenStack CI Solution
----------------------------

http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html

This seems done, other than the logstash/kibana module migration
which is currently underway. It makes sense to leave this on the
priority list until it's done (which should be very, very soon from
the look of things).


Zuul v3
-------

http://specs.openstack.org/openstack-infra/infra-specs/specs/zuulv3.html

We knew this was likely to be a multi-cycle effort when we first
identified it as a priority, so obviously makes sense to remain on
the list for now. The other spec for zookeeper in nodepool should
likely be lumped in with it at a similar priority level since
they're interrelated:

http://specs.openstack.org/openstack-infra/infra-specs/specs/nodepool-zookeeper-workers.html


Anybody disagree with any of the above? Or have any details to add?
Or want to propose other additions to the priority list for the
current cycle?
-- 
Jeremy Stanley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: Digital signature
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20160605/d37b57f0/attachment.pgp>