specs/cbc5ca0deb1ac0d2b61557cc401...

979 lines
31 KiB
Plaintext

{
"comments": [
{
"key": {
"uuid": "9fdfeff1_4bd5e1e4",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 3,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "should it be 2019?\nis this the right copyright?\nDoes not seem to be consistent with four Os of OpenStack\n\nSuggest using the same copyright that the rest of OpenStack is using. Better for moving form Pilot to full fledged project for Airship.",
"range": {
"startLine": 2,
"startChar": 16,
"endLine": 3,
"endChar": 26
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_0b2ef9f9",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 26,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "Bifrost?",
"range": {
"startLine": 26,
"startChar": 8,
"endLine": 26,
"endChar": 25
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_4b43a1b0",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 26,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "Please, be more specific.\nExpect that it covers Node setup configuration for specific use case, and node life-cycle.",
"range": {
"startLine": 26,
"startChar": 45,
"endLine": 26,
"endChar": 65
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_66b473f3",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 26,
"author": {
"id": 9542
},
"writtenOn": "2019-02-21T15:56:18Z",
"side": 1,
"message": "nope. bifrost deploys standard ironic from pip onto the system, here we are talking about containerized ironic running in k8s in UCP namespace - similar to how MaaS is currently used by Drydock",
"parentUuid": "9fdfeff1_0b2ef9f9",
"range": {
"startLine": 26,
"startChar": 8,
"endLine": 26,
"endChar": 25
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_4b1c01c1",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 44,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "Since it is dependent on Keystone it is not standalone Ironic.",
"range": {
"startLine": 44,
"startChar": 49,
"endLine": 44,
"endChar": 70
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_c68bdf1b",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 44,
"author": {
"id": 9542
},
"writtenOn": "2019-02-21T15:56:18Z",
"side": 1,
"message": "the whole sentence defines what do we mean here - no Nova, no Neutron, potentially no Glance and no Swift",
"parentUuid": "9fdfeff1_4b1c01c1",
"range": {
"startLine": 44,
"startChar": 49,
"endLine": 44,
"endChar": 70
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_8b50a960",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 47,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "less -\u003e few",
"range": {
"startLine": 47,
"startChar": 12,
"endLine": 47,
"endChar": 16
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_d9de8c0f",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 47,
"author": {
"id": 26449
},
"writtenOn": "2019-03-04T15:44:55Z",
"side": 1,
"message": "Airship",
"range": {
"startLine": 47,
"startChar": 39,
"endLine": 47,
"endChar": 42
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_b11745ee",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 49,
"author": {
"id": 26449
},
"writtenOn": "2019-03-04T15:44:55Z",
"side": 1,
"message": "Airship",
"range": {
"startLine": 49,
"startChar": 27,
"endLine": 49,
"endChar": 30
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_cea79f0b",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 64,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "Ironic provides both inband and outofband management model support. First one depends on ramdisk to operate. While second does not require it and is more flexible. That is more specific to introspection of HW.\n\nSuggest we put both models and see which one fits better.",
"range": {
"startLine": 63,
"startChar": 27,
"endLine": 64,
"endChar": 28
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_c6de7f0f",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 64,
"author": {
"id": 9542
},
"writtenOn": "2019-02-21T15:56:18Z",
"side": 1,
"message": "Drydock\u0027s main goal AFAIU is get the node provisioned in a declarative fashion. The OOB bits are from what I understand an artefact of how MaaS works and needed to bootstrap nodes into MaaS. Besides OOB actions are not really declarative friendly IMO.",
"parentUuid": "9fdfeff1_cea79f0b",
"range": {
"startLine": 63,
"startChar": 27,
"endLine": 64,
"endChar": 28
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_da02f56f",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 81,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "let\u0027s add an item for setting one of the NICs for PXE booting. Some Ironic drivers do support it, but ironic not exposing it. Can be done via ironic pass-thru mechanism.",
"range": {
"startLine": 76,
"startChar": 1,
"endLine": 81,
"endChar": 40
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_5a1cc5c0",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 88,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "suggest splitting it into 3 separate steps.\nOne for setting BIOS, one for setting RAID(s), final one to deploy base image. All specific to node usage function.",
"range": {
"startLine": 82,
"startChar": 0,
"endLine": 88,
"endChar": 75
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_7ad8a9ef",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 93,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "What is Neutron dependency.\nAs long as NIC(s) is setup for PXE booting order we should be good.\nIf we expect auto IP address assignment then that is separate step outside the node but on the same network.\n\nIf there is dependency on VLAN or other overlay then lets be specific.",
"range": {
"startLine": 92,
"startChar": 3,
"endLine": 93,
"endChar": 55
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "5fc1f717_cb873f0f",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 93,
"author": {
"id": 9542
},
"writtenOn": "2019-03-11T18:13:53Z",
"side": 1,
"message": "in order for PXE to work DHCP response must contain proper options for (i)PXE pointing to the TFTP/HTTP server that _particular_ ironic conductor manages (the one that currently manages this given node that is booted).\n\nin integrated case (with Neutron) ironic\u0027s dhcp and networking drivers actively manage DHCP options for PXE (and optionally MAC address) on the neutron port assigned by nova to this given node.\n\nIn standalone case w/o Neutron there must be other way, discussed below.",
"parentUuid": "9fdfeff1_7ad8a9ef",
"range": {
"startLine": 92,
"startChar": 3,
"endLine": 93,
"endChar": 55
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_b472afaf",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 101,
"author": {
"id": 26449
},
"writtenOn": "2019-03-04T15:44:55Z",
"side": 1,
"message": "What is the method of serving this?",
"range": {
"startLine": 101,
"startChar": 42,
"endLine": 101,
"endChar": 51
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "5fc1f717_8b9e1752",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 101,
"author": {
"id": 9542
},
"writtenOn": "2019-03-11T18:13:53Z",
"side": 1,
"message": "for now we propose static nginx/apache with all the required images placed there.",
"parentUuid": "9fdfeff1_b472afaf",
"range": {
"startLine": 101,
"startChar": 42,
"endLine": 101,
"endChar": 51
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_faed798e",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 106,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "agree. This will need deeper discussion.",
"range": {
"startLine": 100,
"startChar": 3,
"endLine": 106,
"endChar": 77
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_d4ead30c",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 106,
"author": {
"id": 26449
},
"writtenOn": "2019-03-04T15:44:55Z",
"side": 1,
"message": "This should be within the design of this spec. Note that Drydock supports a method of putting arbitrary files in place on bootstrapping nodes and enabling systemd units. This functionality will need to be supported, and likely enhanced if there is a need to support non-systemd OSes.",
"range": {
"startLine": 106,
"startChar": 8,
"endLine": 106,
"endChar": 18
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_6e1f9309",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 131,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "is there drydock config file where one specify which driver to use? Or how does Drydock know which Drydock driver to use?\n\nAlso strongly recommend to use Drydock drivers, as word driver is overloaded. Ironic has its own drivers.",
"range": {
"startLine": 129,
"startChar": 0,
"endLine": 131,
"endChar": 70
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "5fc1f717_aa0c243b",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 131,
"author": {
"id": 10366
},
"writtenOn": "2019-03-12T05:28:58Z",
"side": 1,
"message": "Yes the Drydock Node driver can be specified as part of drydock conf file. Configuration parameter to use - https://github.com/openstack/airship-drydock/blob/master/python/drydock_provisioner/config.py#L168",
"parentUuid": "9fdfeff1_6e1f9309",
"range": {
"startLine": 129,
"startChar": 0,
"endLine": 131,
"endChar": 70
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_daa19548",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 147,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "Do we expect Ironic to setup and configure switches?\nBut you need network to make it happen.\nSO there is assumption for 1G(?) control plane to get to all HW form Genesis node to setup?",
"range": {
"startLine": 147,
"startChar": 0,
"endLine": 147,
"endChar": 79
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "5fc1f717_2a5034d4",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 147,
"author": {
"id": 10366
},
"writtenOn": "2019-03-12T05:28:58Z",
"side": 1,
"message": "Ironic is not expected to setup and configure switches. In this step the network subnets, vlans, any dhcp helpers (already configured on switch) information will be passed onto the provisioner, ironic in this case.\nYes the pxe network details need to be part of manifest definitions.",
"parentUuid": "9fdfeff1_daa19548",
"range": {
"startLine": 147,
"startChar": 0,
"endLine": 147,
"endChar": 79
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_5a8da5d1",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 148,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "Ditto for storage.\nThat will work for presetup external storage but not SDS whose nodes need to be setup by Drydock.",
"range": {
"startLine": 148,
"startChar": 0,
"endLine": 148,
"endChar": 78
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_5aa60556",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 152,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "is this really a single function or multiple, with different functions for each piece?",
"range": {
"startLine": 150,
"startChar": 0,
"endLine": 152,
"endChar": 31
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "5fc1f717_aa5ae426",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 152,
"author": {
"id": 10366
},
"writtenOn": "2019-03-12T05:28:58Z",
"side": 1,
"message": "Today this is part of single function. In Drydock Node driver MAAS, firmware updates,RAID configuration is not supported.",
"parentUuid": "9fdfeff1_5aa60556",
"range": {
"startLine": 150,
"startChar": 0,
"endLine": 152,
"endChar": 31
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_ba6a91ea",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 162,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "and clean any previous use configs and setups.",
"range": {
"startLine": 162,
"startChar": 50,
"endLine": 162,
"endChar": 73
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_790a007a",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 203,
"author": {
"id": 26449
},
"writtenOn": "2019-03-04T15:44:55Z",
"side": 1,
"message": "What is the need for a new OOB driver in Drydock? The OOB driver is for Drydock to directly manage a node via the OOB interface. Drydock already supports OOB management via Redfish, IPMI, and virsh. What benefit is there to putting Ironic in the path? If the Ironic deployment model doesn\u0027t require any OOB management of the node, then the manual, or possibly a new no-op, OOB driver can be used.",
"range": {
"startLine": 203,
"startChar": 48,
"endLine": 203,
"endChar": 75
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "5fc1f717_eb2b1be8",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 203,
"author": {
"id": 9542
},
"writtenOn": "2019-03-11T18:13:53Z",
"side": 1,
"message": "fwiw, I\u0027d add an ironic OOB just in case, so that any manipulation with the node are going thru ironic which should be the only authority and single source of truth.\n\nBut also I do need more info re why the need for separate OOB in the first place and whether we can skip it with ironic alltogether",
"parentUuid": "9fdfeff1_790a007a",
"range": {
"startLine": 203,
"startChar": 48,
"endLine": 203,
"endChar": 75
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "5fc1f717_aaf664f8",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 203,
"author": {
"id": 10366
},
"writtenOn": "2019-03-12T05:28:58Z",
"side": 1,
"message": "OOB is used today to set bootdev to pxe mode and do power cycle operations. If Ironic handles them then as per Scott suggestion, we can make OOB driver as noop.",
"parentUuid": "5fc1f717_eb2b1be8",
"range": {
"startLine": 203,
"startChar": 48,
"endLine": 203,
"endChar": 75
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_3a7ea1af",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 206,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "drydock config is needed so it knows which of OOB available drivers to use.",
"range": {
"startLine": 202,
"startChar": 0,
"endLine": 206,
"endChar": 48
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_d963ec40",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 285,
"author": {
"id": 26449
},
"writtenOn": "2019-03-04T15:44:55Z",
"side": 1,
"message": "I see no details on methodology here. Is this done outside of Drydock in an isolated chart? Is the expectation that Drydock is now managing DHCP?",
"range": {
"startLine": 283,
"startChar": 51,
"endLine": 285,
"endChar": 12
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "5fc1f717_8b685721",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 285,
"author": {
"id": 9542
},
"writtenOn": "2019-03-11T18:13:53Z",
"side": 1,
"message": "yes, ironic does not so need to manage IP addresses, but DHCP options for PXE returned with DHCP response\n\nthis could be populated from the HW model which is fed to shipyard as it already contains MAC addresses if I\u0027m not mistaken.",
"parentUuid": "9fdfeff1_d963ec40",
"range": {
"startLine": 283,
"startChar": 51,
"endLine": 285,
"endChar": 12
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_dddd26de",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 290,
"author": {
"id": 22477
},
"writtenOn": "2019-03-03T23:11:42Z",
"side": 1,
"message": "Do you see a dnsmasq-enabled HA mode as part of the initial Ironic NodeDriver implementation, or would it make sense to start out with a non-HA implementation and expand from there?",
"range": {
"startLine": 290,
"startChar": 3,
"endLine": 290,
"endChar": 10
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "5fc1f717_8bd617c3",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 290,
"author": {
"id": 9542
},
"writtenOn": "2019-03-11T18:13:53Z",
"side": 1,
"message": "I would start with non-HA for MVP. To have HA one would either need a DHCP server with remotely configurable settings + a new ironic dhcp driver for it, or the dynamic iPXE config spec implemented in ironic.",
"parentUuid": "9fdfeff1_dddd26de",
"range": {
"startLine": 290,
"startChar": 3,
"endLine": 290,
"endChar": 10
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_d9c8cc22",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 309,
"author": {
"id": 26449
},
"writtenOn": "2019-03-04T15:44:55Z",
"side": 1,
"message": "To be clear, is this spec calling out doing this work as a pre-req or just describing a future feature that can be utilized?",
"range": {
"startLine": 296,
"startChar": 0,
"endLine": 309,
"endChar": 37
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "5fc1f717_cbedff8b",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 309,
"author": {
"id": 9542
},
"writtenOn": "2019-03-11T18:13:53Z",
"side": 1,
"message": "IMO this is one of possible pre-requisites for standalone ironic HA, the other one is remotely configurable DHCP server + ironic dhcp driver for it.\nThe former has an approved spec and an unmerged implementation that was working couple of releases ago, so presumably more realistic to get merged in Train release (too late for Stein already).",
"parentUuid": "9fdfeff1_d9c8cc22",
"range": {
"startLine": 296,
"startChar": 0,
"endLine": 309,
"endChar": 37
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_bde06299",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 312,
"author": {
"id": 22477
},
"writtenOn": "2019-03-03T23:11:42Z",
"side": 1,
"message": "Would the Ironic OOB Driver be needed on day one for Ironic NodeDriver integration, or could we start out with PyghmiDriver and then add an Ironic OOB driver as a second step?",
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_19de54da",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 312,
"author": {
"id": 26449
},
"writtenOn": "2019-03-04T15:44:55Z",
"side": 1,
"message": "As per above, I don\u0027t see a clear need for this.",
"range": {
"startLine": 312,
"startChar": 0,
"endLine": 312,
"endChar": 17
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_ba43716c",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 473,
"author": {
"id": 7160
},
"writtenOn": "2019-02-20T00:05:38Z",
"side": 1,
"message": "not quite standalone as it need to use keystone.",
"range": {
"startLine": 473,
"startChar": 17,
"endLine": 473,
"endChar": 72
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "9fdfeff1_7f5cbf4a",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 473,
"author": {
"id": 9542
},
"writtenOn": "2019-02-25T10:21:06Z",
"side": 1,
"message": "again, it is standalone in the sense of not depending on Glance, Neutron and Swift (keystone is affecting only auth part, but the other services strongly affect how ironic must operate in their presence or absence).\n\nThere are indeed some changes needed to the openstack-helm/ironic chart to support deploying ironic w/o those services, as currently these are pretty entangled.\nProposed change https://review.openstack.org/#/c/636715",
"parentUuid": "9fdfeff1_ba43716c",
"range": {
"startLine": 473,
"startChar": 17,
"endLine": 473,
"endChar": 72
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "5fc1f717_89d8da52",
"filename": "specs/approved/drydock_ironic_integration.rst",
"patchSetId": 4
},
"lineNbr": 473,
"author": {
"id": 7160
},
"writtenOn": "2019-03-18T19:05:05Z",
"side": 1,
"message": "Do we want to change it to Bifrost then?",
"parentUuid": "9fdfeff1_7f5cbf4a",
"range": {
"startLine": 473,
"startChar": 17,
"endLine": 473,
"endChar": 72
},
"revId": "cbc5ca0deb1ac0d2b61557cc4012d50aa6079f20",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
}
]
}