Jump to: navigation, search

Difference between revisions of "Meetings/HeatAgenda"

Line 9: Line 9:
  
 
== Next meeting ==
 
== Next meeting ==
* Wed Nov 28 at 2000 UTC
+
* Wed Dec 5 at 2000 UTC
  
 
=== Agenda ===
 
=== Agenda ===
 
* Review last week's actions
 
* Review last week's actions
** shardy post agenda before meeting
+
** put heatclient in pypi
* Packaging decide priorities/timeline (and look for volunteers to assign the bugs to.. ;)
+
** make a bug to update the ubuntu tdls to install a recent version of boto
** [[PyPi]] (requested by user on IRC)
+
** start running the integration tests
*** https://bugs.launchpad.net/heat/+bug/1083500
+
** ask at next project meeting
* packaging for Ubuntu?
+
<TODO ADD ITEMS>
** https://bugs.launchpad.net/heat/+bug/1083501
+
 
* State of ubuntu host/guest support
+
* Open discussion
** Many (most?) users are using ubuntu, but most of our testing in on Fedora
 
** Many (most?) key-features don't work (easily) with ubuntu guest images (boto version, cloud-init paths ref bug 1072921)
 
** Add ubuntu host/guest as primary targets for integration and pre-release testing?
 
** Need an improved getting started for ubuntu (packaged openstack not devstack)
 
*** https://bugs.launchpad.net/heat/+bug/1083505
 
*** https://bugs.launchpad.net/heat/+bug/1083507
 
* RHEL/CentOS support?
 
** Do we want/need to support RHEL/CentOS (packages via EPEL?) yet?
 
** Getting started for RHEL6+RHOS should hopefully be pretty similar to the existing Fedora one, testing needed
 
* Way forward for integration tests
 
** mentioned last meeting but no conclusion reached - how to get better value from the effort invested in integration tests? Tempest?  Shared responsibility for maintaining/monitoring tests manually?  Email spam on failure? Other?
 
** Have been cleared to request help/advice from the CI team with this
 
* Launchpad issues
 
** Need to start assigning all bugs/blueprints to grizzly milestones
 
** If we're not doing a release for G1 we should delete the milestone and bump everything to G2
 
* jpeeler to update re state of snapshot/prebuild investigation, decide what approach if any should be pursued
 
* FOSDEM 2013 - call for participation, who's going and is anyone keen to present an intro-to-heat talk?
 
  
 
== Previous meetings ==
 
== Previous meetings ==
 
* meeting 01 | 21 nov 12 | [http://eavesdrop.openstack.org/meetings/heat/2012/heat.2012-11-21-20.01.log.html log] | [http://eavesdrop.openstack.org/meetings/heat/2012/heat.2012-11-21-20.01.html summary]  
 
* meeting 01 | 21 nov 12 | [http://eavesdrop.openstack.org/meetings/heat/2012/heat.2012-11-21-20.01.log.html log] | [http://eavesdrop.openstack.org/meetings/heat/2012/heat.2012-11-21-20.01.html summary]  
 +
* meeting 02 | 28 nov 12 | [http://eavesdrop.openstack.org/meetings/heat/2012/heat.2012-11-28-19.59.log.html log] | [http://eavesdrop.openstack.org/meetings/heat/2012/heat.2012-11-28-19.59.html summary]
  
 
== Meeting organizers ==
 
== Meeting organizers ==

Revision as of 12:03, 29 November 2012

Weekly Heat (Orchestration) meeting

The heat Orchestration project team holds a meeting in #openstack-meeting:

Everyone is welcome.

The blueprints that are used as a basis for the heat project can be found at https://blueprints.launchpad.net/heat

Next meeting

  • Wed Dec 5 at 2000 UTC

Agenda

  • Review last week's actions
    • put heatclient in pypi
    • make a bug to update the ubuntu tdls to install a recent version of boto
    • start running the integration tests
    • ask at next project meeting

<TODO ADD ITEMS>

  • Open discussion

Previous meetings

Meeting organizers