-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 27/09/14 18:05, Alan Pevec wrote:
can we have draft release notes page created so that we may start to fill it?
It's a wiki :) https://wiki.openstack.org/wiki/ReleaseNotes/2014.1.3#Neutron
Sure. Do we have the draft somewhere to copy-paste from? Or do you copy-paste it from the previous one manually removing unneeded lines?
""" We could also update the release notes indicating that existing deployments will need to manually modify their schema if they're already at Icehouse. """ [1]: https://review.openstack.org/#/c/110642/
Hmm, what was the outcome of discussion about backporting db migrations with Alembic? Isn't there a way to insert db migration so that admin could just run neutron-db-manage upgrade ?
I think there is no way to introduce trees in migration chains until the following alembic is implemented and released: https://bitbucket.org/zzzeek/alembic/issue/167/multiple-heads-branch-resolut... Mike, is it correct?
In any case, exact commands to run need to be documented, like similar example from the past: https://wiki.openstack.org/wiki/ReleaseNotes/2013.2.2#Keystone
The SQL statement for this is: "ALTER TABLE agents ADD CONSTRAINT uniq_agents0agent_type0host UNIQUE (agent_type, host);" Will it be enough, or should we instead implement some script using sqlalchemy to stay on portable side (and maybe even place it in tools/ directory shipping with the package)? [Note: I have no idea how portable the statement above is.]
Cheers, Alan
-----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iQEbBAEBCgAGBQJUKUFHAAoJEC5aWaUY1u57QJQH9REs0S3R0Vrx4/m25XrzjqI3 WN50ko2SpygzlDySvJZuOddVvG7RfK98aidkF46O8wU/4NovDF9G0JKwRBbBLIAr OhHCT/RHFVM/ng/zcUuF1/DPfkTQTRDGLY0kUksFVstPGPlr9uLtLPJNlX/5fMsV xE1VRXtEhnDUTzXsbeSovUeKfvu3K3FHN8RpcxxMJiiU3h1TXzSA6ox7lcVqL2jv k1s3rTUtHvTaiYdnD1JTGG+pqANo/CavPHIqauPb9Hz1mECYaE9e2fCv0kvKj7mY 1/xsMgHVr87bnJeSgRIB1LfqdaE15Tn5HF3gBl4307NCh5o1YpCU5UwjjSbq5A== =FUYv -----END PGP SIGNATURE-----