)]}' { "log": [ { "commit": "49933804c9d151ce4a220c188ba4301afa0bf98c", "tree": "30189da4a613ae9a6f8eedff60d5a9c295a3dd75", "parents": [ "14f60b951aa03ded3779057c7fef28f6c3ee15cc" ], "author": { "name": "Stephen Finucane", "email": "stephenfin@redhat.com", "time": "Tue Aug 27 12:08:23 2024 +0100" }, "committer": { "name": "Stephen Finucane", "email": "stephenfin@redhat.com", "time": "Tue Oct 01 11:54:35 2024 +0100" }, "message": "docs: Expand SSH guide further\n\nsmooney noted that using your DevStack host as a jump host is yet\nanother reasonable option. Add this option also.\n\nChange-Id: I24887c254e131a8979653a7d17e64a708acf294a\nSigned-off-by: Stephen Finucane \u003cstephenfin@redhat.com\u003e\n" }, { "commit": "14f60b951aa03ded3779057c7fef28f6c3ee15cc", "tree": "f685f652d9482034608698b294c4a0e151aabfde", "parents": [ "3362be9edabb7c882ae9948d210a18fadd25ebda" ], "author": { "name": "Stephen Finucane", "email": "stephenfin@redhat.com", "time": "Mon Aug 26 11:56:31 2024 +0100" }, "committer": { "name": "Stephen Finucane", "email": "stephenfin@redhat.com", "time": "Tue Oct 01 11:54:35 2024 +0100" }, "message": "docs: Expand SSH guide\n\nDetail how one can SSH into guests running on a remote DevStack host.\n\nChange-Id: I9f988b1193d67859b129f05d08b32a23e50aee49\nSigned-off-by: Stephen Finucane \u003cstephenfin@redhat.com\u003e\n" }, { "commit": "3362be9edabb7c882ae9948d210a18fadd25ebda", "tree": "9e016b910e0096571afdb412241a1a3142393631", "parents": [ "6512f0140c9a312f9455bfe420462c64635fd622" ], "author": { "name": "Stephen Finucane", "email": "stephenfin@redhat.com", "time": "Thu Aug 22 16:24:21 2024 +0100" }, "committer": { "name": "Stephen Finucane", "email": "stephenfin@redhat.com", "time": "Tue Oct 01 11:54:35 2024 +0100" }, "message": "docs: Add SSH guide\n\nThis is really easy win for people using DevStack for the first time.\n\nChange-Id: I8de2d4d115d34e9d87dd461016b5b894d3f000e7\nSigned-off-by: Stephen Finucane \u003cstephenfin@redhat.com\u003e\n" }, { "commit": "c3b58f5335fb3545bf49b5d542ef9ed702de43c8", "tree": "9ed8e63216a6033fab7377cbea4336d3a65e0f80", "parents": [ "0d6234b4b196ef34aaaf0ddf2a7182dbeafa6cd6" ], "author": { "name": "Jens Harbott", "email": "j.harbott@x-ion.de", "time": "Mon Jun 08 11:58:29 2020 +0200" }, "committer": { "name": "Jens Harbott", "email": "j.harbott@x-ion.de", "time": "Mon Jun 08 11:58:29 2020 +0200" }, "message": "Fix typos in networking document\n\nThe FLOATING_RANGE variable should specify the network address of the\nused prefix for clarity.\n\nChange-Id: I547bd42d8bdc5f0f2001d47f2d5b43729773b1bc\nCloses-Bug: 1870204\n" }, { "commit": "64edfd47caba71a0c351269663dd457fd911fcac", "tree": "8b4f483c4a2f1921ad51f8a207a6b3192e14b076", "parents": [ "b93fd6fc5c8d9ab23251c45b427ccad4caeb79e1" ], "author": { "name": "John L. Villalovos", "email": "john.l.villalovos@intel.com", "time": "Thu Aug 17 13:21:25 2017 -0700" }, "committer": { "name": "John L. Villalovos", "email": "john.l.villalovos@intel.com", "time": "Thu Aug 17 13:21:25 2017 -0700" }, "message": "Correct spelling for \u0027lose\u0027 from \u0027loose\u0027\n\nWe can \u0027lose\u0027 networking configuration, not \u0027loose\u0027 it.\n\nChange-Id: I538270c05da6fce63340cc75ec53c3834efcecfe\n" }, { "commit": "0dab8d63b3e5431bd5edb562f466296478285251", "tree": "638b09e98ff527d14c9ea39a5f1a72bf7b06c7ae", "parents": [ "5dbb826a547195b3cc33ff4f30f6d79d0ae08045" ], "author": { "name": "Peter Stachowski", "email": "peter@tesora.com", "time": "Mon Nov 21 20:36:31 2016 +0000" }, "committer": { "name": "Peter Stachowski", "email": "peter@tesora.com", "time": "Thu Nov 24 22:10:54 2016 +0000" }, "message": "(doc) Fixed references to FIXED_RANGE_V6\n\nIn the \u0027Private Network Addressing\u0027 section of the doc,\nthere are references to FIXED_RANGE when referring to V6\nnetworks. These have been changed to FIXED_RANGE_V6.\n\nAlso fixed a few typos and grammatical errors when\ngiving the doc a quick read-through looking for more\nreferences to FIXED_RANGE.\n\nChange-Id: Iaa530c476ce2b36a3f616945ddd2e24fa599a16c\n" }, { "commit": "4bfbc291eefd92d8b7885f36275b7ff541e067ab", "tree": "ca0bc6b51fde649f8d47880e48fd115a63deafb6", "parents": [ "7976f31fb956dcb1cbeea92906f5609f0b43acc4" ], "author": { "name": "Kevin Benton", "email": "kevin@benton.pub", "time": "Tue Nov 15 17:26:05 2016 -0800" }, "committer": { "name": "Kevin Benton", "email": "kevin@benton.pub", "time": "Wed Nov 16 05:26:03 2016 +0000" }, "message": "Derive IP ranges from new ADDRS_SAFE_TO_USE vars\n\nThe switch to using subnetpools caused quite a bit of confusion\nbecause it didn\u0027t respect the value of FIXED_RANGE. This caused\nconflicts in the gate with it\u0027s default IPv4 value of 10.0.0.0/8.\n\nThis patch does a few things to address the issue:\n* It introduces the IPV4_ADDRS_SAFE_TO_USE and IPV6_ADDRS_SAFE_TO_USE\n values and adjusts all of the FIXED_RANGE and SUBNETPOOL_PREFIX values\n to dervive from them by default.\n * This addresses the concern that was raised about implying that\n SUBNETPOOL_PREFIX and FIXED_RANGE are equivalent when setting\n SUBNETPOOL_PREFIX\u003dFIXED_RANGE by default. Now we have a new value\n for the operator specify a chunk of addresses that are safe to\n use for private networks without implementation implications.\n * Backwards compatibility is maintained by alloing users to override\n override all of these values.\n* The default for IPV4_ADDRS_SAFE_TO_USE uses /22 instead of /24\n * Because we want to be able to use subnetpools for auto allocated\n topologies and we want to be able to have a large chunk of\n instances on each network, we needed a little more breathing room\n in the default v4 network size.\n* SUBNET_POOL_SIZE_V4 default is changed from 24 to 26\n * In conjuction with this change and the one above, the default\n subnetpool will support up to 16 64-address allocations.\n * This should be enough to cover any regular gate scenarios.\n * If someone wants a bigger/smaller subnet, they can ask for that\n in the API request, change this value themselves, or use a different\n network entirely.\n* FIXED_RANGE_V6 defaults to a max prefix of /64 from IPV6_ADDRS_SAFE_TO_USE\n * This avoids the private subnet in the non-subnetpool case from being\n larger than /64 to avoid issues identified in rfc 7421.\n * Users can still explicitly set this value to whatever they want.\n This \u0027max\u0027 behavior is only for the default.\n * This allows IPV6_ADDRS_SAFE_TO_USE to default to a /56, which leaves\n tons of room for v6 subnetpools.\n\nCloses-Bug: #1629133\nChange-Id: I7b32804d47bec743c0b13e434e6a7958728896ea\n" }, { "commit": "bc883df1c23fab66f681f2c4fe9c0d3affadc671", "tree": "9ea2e092dcb5d642239519a61f7e61704610f6b3", "parents": [ "9b8b922872a6a19d5bc78383a2d484580871f833" ], "author": { "name": "Sean Dague", "email": "sean@dague.net", "time": "Fri Aug 12 07:21:59 2016 -0400" }, "committer": { "name": "Sean Dague", "email": "sean@dague.net", "time": "Fri Aug 12 07:21:59 2016 -0400" }, "message": "add networking write up for devstack\n\nThis explains the current state of networking in devstack, and a\ncouple of scenarios that people might want to try out for local\ntesting.\n\nChange-Id: I2be35f4345bf9306c981ef6f0186b48da7d06772\n" } ] }