Age | Commit message (Collapse) | Author |
|
indeed masking the new migration stuff. yamltest now runs migrations
as part of setting up test CAs; still need to decide whether running
migrations in production is something that should be handled
explicitly via rpki-manage or should be bundled into rpki-sql-setup.
Old settings.configure() code still present as a trail of breadcrumbs
to follow when backing out the rest of the tortuous startup sequence
required by the old way of doing things.
svn path=/branches/tk713/; revision=5950
|
|
but it sails blithely along, suggesting that I've forgotten some bit
of startup voodoo that it's doing. Regardless, the migration should
be harmless, and now we know that South thinks it can read the IRDB
models, which is progress.
The current requirement to have a valid rpki.conf before one can run
rpki-manage schemamigration etc is a bit of a pain, may need to do
something about that.
svn path=/branches/tk713/; revision=5949
|
|
svn path=/branches/tk713/; revision=5948
|
|
svn path=/trunk/; revision=5945
|
|
May have finally gotten the right balance of indexes for basic use.
Use various optimizations to let us load large data sets before the
heat death of the universe. Some of these optimizations are
dangerous, in the sense that if this script crashes while constructing
the database, you'll have to rebuild the database from scratch.
Probably ought to offer both this and the slow-but-safe approach as
command line options, but:
- The speed improvements look to be worth at least an order of
magnitude in the runtime,
- The speed improvements also prevent all the fsync() calls in the
safe approach from turning the underlying filesystem into cream
cheese while the script is running, and
- This script is just a research anlysis tool to begin with.
So I think the risk is justified in this case.
svn path=/trunk/; revision=5934
|
|
seconds-since-epoch.
svn path=/trunk/; revision=5933
|
|
svn path=/trunk/; revision=5930
|
|
svn path=/trunk/; revision=5928
|
|
svn path=/trunk/; revision=5927
|
|
work of extracting and parsing before discovering that we've hit a
duplicate. Not sure what equivalent would be for Maildir (maybe
Message-ID?) so deferring that for now.
svn path=/trunk/; revision=5925
|
|
analysis.
svn path=/trunk/; revision=5923
|
|
svn path=/trunk/; revision=5921
|
|
svn path=/trunk/; revision=5909
|
|
svn path=/trunk/; revision=5908
|
|
svn path=/trunk/; revision=5902
|
|
svn path=/trunk/; revision=5895
|
|
svn path=/trunk/; revision=5894
|
|
multiple protocol versions. Not tested yet.
svn path=/trunk/; revision=5893
|
|
svn path=/trunk/; revision=5890
|
|
svn path=/trunk/; revision=5886
|
|
svn path=/trunk/; revision=5885
|
|
expiration date hasn't changed and we'd just be doing the same thing
again on the next cron cycle. See #704.
svn path=/trunk/; revision=5873
|
|
svn path=/trunk/; revision=5872
|
|
and mode FreeBSD has started whacking on every upgrade. See #702.
svn path=/trunk/; revision=5871
|
|
svn path=/trunk/; revision=5870
|
|
svn path=/trunk/; revision=5869
|
|
See #701
svn path=/trunk/; revision=5868
|
|
svn path=/trunk/; revision=5867
|
|
a quick hack to get router keys into BIRD while waiting for rtrlib.
svn path=/trunk/; revision=5866
|
|
svn path=/trunk/; revision=5865
|
|
svn path=/trunk/; revision=5864
|
|
svn path=/trunk/; revision=5863
|
|
svn path=/trunk/; revision=5862
|
|
affect anything the RPKI code does, but it's easiest to stay current.
svn path=/trunk/; revision=5861
|
|
not yet documented, but allows detailed logging configuration down to
the class level, and flexible enough to allow runtime configuration if
we decide we need that.
svn path=/trunk/; revision=5860
|
|
standard.
svn path=/trunk/; revision=5859
|
|
svn path=/trunk/; revision=5858
|
|
missed these.
svn path=/trunk/; revision=5857
|
|
svn path=/trunk/; revision=5856
|
|
svn path=/trunk/; revision=5855
|
|
asyncore.dispatcher.socket.setsockopt(), per deprecation warning.
svn path=/trunk/; revision=5854
|
|
svn path=/trunk/; revision=5853
|
|
svn path=/trunk/; revision=5852
|
|
logging handlers up front to the argparse stage, thereby also giving
the application more control over the default logging configuration.
svn path=/trunk/; revision=5851
|
|
svn path=/trunk/; revision=5850
|
|
svn path=/trunk/; revision=5849
|
|
svn path=/trunk/; revision=5848
|
|
svn path=/trunk/; revision=5847
|
|
svn path=/trunk/; revision=5846
|
|
svn path=/trunk/; revision=5845
|