Age | Commit message (Collapse) | Author |
|
smoketest hasn't worked since we converted to Tornado and Django ORM.
xml-parse-test hasn't worked since we ripped out the massively
redundant XML layer and went to using lxml.etree directly.
old_irdbd hasn't worked since we converted to Django ORM.
rpki.adns hasn't worked since we converted to Tornado.
Various tests in ca/Makefile.in haven't worked since all of the above
happened.
Some day we may want to resurrect a few bits (in particular, the
post-initialization scripting capabilities from smoketest) but for the
moment it just confuses people, so away with it.
|
|
for XML. Apparently we were carefully changing just the XML files to
use a single "-" to work around this. Enough already, just convert
all copyright year ranges to single "-" and have done with this.
svn path=/branches/tk705/; revision=6427
|
|
svn path=/branches/tk705/; revision=6426
|
|
svn path=/branches/tk705/; revision=6391
|
|
and logging setup. Most programs now use the unified mechanism,
although there are still a few holdouts: the GUI, which is a special
case because it has no command line, and the rpki-rtr program, which,
for historical reasons has its own implementation of the logging setup
infrastructure.
svn path=/branches/tk705/; revision=6390
|
|
new scheme. Rewrite pubd code which was whacking top-level
certificate files with names other than "root.cer".
svn path=/branches/tk705/; revision=6380
|
|
svn path=/branches/tk705/; revision=6377
|
|
worker CA and going straight from the root to certifying children,
which is wrong. However...this is far enough along that we can now
remove all the rootd glorp, which is a worthwhile simplification in
its own right, so checkpoint here, remove rootd glorp, then figure out
what's wrong with the internal certificate hierarchy.
rcynic does validate the current output, given a manually constructed
TAL, even if the current output isn't quite what it should be. So we
should also be able to sort out the new TAL generation code now.
Yes, checking in a version that works for the wrong reasons is weird,
but the current sort-of-broken state lets us confirm that the lower
levels of the tree are still correct as we go, which would be much
harder if the poor thing just sat there and whimpered until we had
the new internal CA code completely finished.
svn path=/branches/tk705/; revision=6376
|
|
left-right schema. Not really using of this stuff yet, but haven't
broken existing code yet either.
svn path=/branches/tk705/; revision=6371
|
|
I think Subversion's merge tracking data is turning into cream cheese.
svn path=/branches/tk705/; revision=6360
|
|
svn path=/branches/tk705/; revision=6352
|
|
svn path=/branches/tk705/; revision=6269
|
|
Whack CA tools with a club until rcynicng works with our CA RRDP
implementation.
Add makemigrations target to top-level Makefile; this is a bit of a
kludge, but sure beats doing this by hand.
svn path=/branches/tk705/; revision=6230
|
|
svn path=/branches/tk705/; revision=6217
|
|
understands Django's exotic metaclasses, which in turn allows us to
re-enable a number of pylint checks we had disabled. While we were at
this, stripped out a bunch of old pylint pragmas, then added back the
subset that were really needed. As usual with pylint, this turned up
a few real bugs along with an awful lot of noise.
svn path=/branches/tk705/; revision=6162
|
|
svn path=/branches/tk705/; revision=6160
|
|
under yamltest. No obvious way to tell Django's CSRF protection to
allow this, not entirely sure we'd want to do so even if we could.
svn path=/branches/tk705/; revision=6154
|
|
running with new code base. Now working with
$ yamltest.py --sql mysql --gui smoketest.1.yaml
svn path=/branches/tk705/; revision=6153
|
|
or commenting conventions should be shot. If it so happens that it is
inconvenient to shoot him, then he is to be politely requested to recode
his program in adherence to the above standard."
-- Michael Spier, Digital Equipment Corporation
svn path=/branches/tk705/; revision=6152
|
|
backend. Switch yamltest's default database configuration to sqlite3.
MySQL still has character set issues, which are almost certainly to do
with the communication channel rather than the database tables. It's
possible that one of the newer DB API drivers for MySQL fixes this,
might be worth trying one of them at some point (see the "MySQL notes"
discussion of MySQL DB API drivers in the Django documentation).
svn path=/branches/tk705/; revision=6149
|
|
so on a faster machine.
svn path=/branches/tk705/; revision=6141
|
|
quite working perfectly yet (cron is a bit wonky) but manages to
produce an initial set of ROAs without thowing any exceptions, and
code is already much cleaner than the old callback-based horror.
svn path=/branches/tk705/; revision=6139
|
|
svn path=/branches/tk705/; revision=6136
|
|
bad choice for something implemented in Python, holdover from an older
specification, but Django ORM's troubles with "self" as a keyword
argument were the last straw. Enough already. Backwards
compatability should be a straightforward data migration.
svn path=/branches/tk705/; revision=6134
|
|
svn path=/branches/tk705/; revision=6130
|
|
Django ORM. Duct tape and bailing wire everywhere, much clean-up left
to do, but basic "make yamltest" suite runs. Much of the clean-up
isn't worth doing until after revamping the I/O system, as it'll all
change again at that point anyway.
svn path=/branches/tk705/; revision=6127
|
|
svn path=/branches/tk705/; revision=6123
|
|
left-right protocol and irdb and rpkidb models.
Not fully working yet, RRDP URI isn't yet showing up everywhere it
should, but this is probably more an indication that the previous hack
was incomplete than that the replacement broke something.
svn path=/branches/tk705/; revision=6120
|
|
clean up some of the corresponding mess.
svn path=/branches/tk705/; revision=6105
|
|
A few old test programs were still using this, those will require
upgrade or retirement.
svn path=/branches/tk705/; revision=6102
|
|
incomprehensible advance depreciation warnings for Django 1.9.
svn path=/branches/tk705/; revision=6100
|
|
particular programs (see #713).
svn path=/branches/tk705/; revision=6098
|
|
svn path=/branches/tk705/; revision=6094
|
|
svn path=/branches/tk705/; revision=6083
|
|
This needs rewriting, but doing it properly requires a minor database
schema change, and I'm trying to get a test case running by tomorrow
morning.
svn path=/branches/tk705/; revision=6015
|
|
delta rather than a range.
svn path=/branches/tk705/; revision=6010
|
|
svn path=/branches/tk705/; revision=5979
|
|
smoketest temporarily broken as it doesn't know anything about Django.
svn path=/branches/tk705/; revision=5961
|
|
with all its tedious setup actions.
svn path=/branches/tk705/; revision=5957
|
|
svn path=/branches/tk705/; revision=5956
|
|
might be due to some kind of CSRF problem, might be worth figuring out
how to disable that for debugging but not terribly urgent.
svn path=/branches/tk713/; revision=5955
|
|
Result sometimes hangs with browser waiting for response, not sure
why, might be ancient abandoned bug #116.
Logging control is a bit screwy, everything uses Python's logging
library but we have multiple ways of configuring it.
svn path=/branches/tk713/; revision=5954
|
|
startup procedure. This may be temporary, as processing --help
without a configuration file may require deferring all Django imports
until late enough that --config would work too. Defer for now.
svn path=/branches/tk713/; revision=5953
|
|
svn path=/branches/tk713/; revision=5952
|
|
svn path=/branches/tk713/; revision=5951
|
|
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
|
|
svn path=/branches/tk713/; revision=5948
|
|
svn path=/branches/tk705/; revision=5942
|
|
svn path=/branches/tk705/; revision=5915
|
|
that smoketest.py uses an obsolete BPKI model which requires different
configuration than modern code. Real fix is several different major
refactoring jobs (merging rootd into rpkid, merging all three
YAML-based test tools...). As usual, not today.
svn path=/branches/tk705/; revision=5914
|