Icehouse Design Summit

Right now we use redstack (trove-integration) for all our integration testing needs. How do we move to Tempest so that our tests can be used to gate check-ins. Let's discuss what needs to happen, and how we can go about getting it done.

https://etherpad.openstack.org/p/TroveTempestTesting

(Session proposed by Nikhil)

the Trove heat codepath is currently lacking. It needs to be built out, and support multiple templates and things like cloud init. We need to define a list of criteria we want to support and how we would like to support them.

https://etherpad.openstack.org/p/TroveHeatSupport

(Session proposed by Michael Basnight)

We have defined what we think is a good shot at the clustering api. Lets, as a group, review it and toss out our ideas, and try to blow holes in it.

We also need to gather high level requirements, such as rack awareness, that a Clustering system needs to define.

https://etherpad.openstack.org/p/TroveReplicationClustering

(Session proposed by Michael Basnight)

Go over strategy to upgrade GuestAgent, TaskManager, and API without incurring downtime. Also touch on ensuring version compatibility with RPC versioning.

https://etherpad.openstack.org/p/TroveUpgradesNoDowntime

(Session proposed by Vipul Sabhaya)

The OpenStack ecosystem plays host to a number of guest agents, tiny programs which help manage services or other components on provisioned servers. Trove also makes use of an agent to provision and manage datastores.

There are currently two known agents used for Trove- the so called "reference agent" found in the Trove repository as well as Sneaky Pete which is currently used by Rackspace. Both suffer from architectual issues with how they communicate with Trove (some of which will hopefully be resolved by the work on Conductor).

Let's get together and discuss the way that Trove's relationship with agents as well as the agents themselves can be improved.

https://etherpad.openstack.org/p/TroveGuestAgents

(Session proposed by Michael Basnight)