This would be fantastic if it can be written. On Mon, Aug 10, 2015 at 1:17 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote:
> Norbert, I haven't begun to think about it. including dev@ to gather > ideas. > The db structure is based on updates since 4.0. A new install will be a 4.0 > DB which will then undergo a series of upgrade steps. A validation of the > db could be divided in a basic part and an incremental part, maybe. > > A good tactic might be to start a collection of smaller checks that > validate only individual parts. An example would be orphaned volumes, or > removed volumes that are still attached to VMs. completeness of link tables > is another one. > > This is not going to be caught in a single story, i'm afraid. > > On Mon, Aug 10, 2015 at 2:03 PM, Norbert Klein < > norbert.kl...@infosecprojects.net> wrote: > > > Do you have any idea where to start? (I am not a developer). If there is > > no script avaible > > I think a developer has to do it or at least I need the criterias from > > them. Without knowing > > the internal CS structure I don't know exactly what to check. > > > > Am 10.08.2015 um 13:51 schrieb Daan Hoogland: > > > Good point Norbert, I don't think there is. would be a great addition > > > though. You want to take this on or at least create a ticket for it in > > > jira? > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK > > > > > > On Mon, Aug 10, 2015 at 1:48 PM, Norbert Klein < > > > norbert.kl...@infosecprojects.net> wrote: > > > > > >> Hi all, > > >> > > >> what is the best way to check the cloudstack database consistency? > > >> Is there any tool or script available which we could use to make sure > > >> the database structure and content > > >> is in a valid state? (for example after manual changes). > > >> > > >> Thx > > >> Norbert > > >> > > >> > > > > > > > > > -- > Daan >
